Authenticate the Endpoint at the Gatekeeper with an H.323 ID and
Password Using the Separator
Follow these steps to configure the ATA 186 to register with the H.323 ID and password:
Set the AutMethod field to 1 (the default is 1).
The hexadecimal value configured for this field is 0x1. This field is set to indicate that the ATA now
looks for the password.
1.
Set the UseLoginID field to 1.2.
Configure LoginID0 and LoginID1 with the H.323 IDs, followed by the separator and password for
the ATA 186.
For example, LoginID0 is atagw1=cisco.
The ATA 186 registers as two different H.323 terminals, one for each port.
Note: The ATA uses the password to generate the token. This token is sent to the gatekeeper for
authentication.
3.
Configure NTPIP with the NTP servers IP address.
The gatekeeper and the ATA must have clocks synchronized to the same NTP server.
4.
Note: The timestamp is used for token generation. For more information, refer to the Gateway to Gatekeeper
(H.235) and Gatekeeper to Gatekeeper (IZCT) Security Troubleshooting Guide.
This is a sample working configuration for the gatekeeper and gateway when using ATA with the H.323 ID
and password authentication method using a separator:
2610−Gatekeeper
aaa authentication login default local
aaa authentication login cisco none
aaa authentication login h323 local
aaa session−id common
enable password ww
!
username atagw1 password cisco
!−−− Same as the LoginID0 and PWD0 fields.
username atagw2 password cisco
!−−− Same as the LoginID1 and PWD1 fields.
!
gatekeeper
zone local gk2 cisco.com 172.16.13.12
security h323−id
security password separator =
!−−− Register after the H.323 ID or E.164 address and token is authenticated.
no shutdown
!
Note: For more information on gatekeeper security, refer to the Gateway to Gatekeeper (H.235) and
Gatekeeper to Gatekeeper (IZCT) Security Troubleshooting Guide.
