Summary of the content on the page No. 1
Configuring and Troubleshooting an ATA 186 with
Cisco IOS Gatekeepers
Document ID: 19084
Introduction
Prerequisites
Requirements
Components Used
Conventions
Network Diagram
Registering the ATA 186 with the Gatekeeper
Adding Security
Authenticate the Endpoint at the Gatekeeper with an H.323 ID
Authenticate the Endpoint at the Gatekeeper with an E.164 Address
Authenticate the Endpoint at the Gatekeeper with an H.323 ID and Password
Authenticate the E
Summary of the content on the page No. 2
Components Used The information in this document is based on these software and hardware versions: • ATA 186 with version 2.12 • Cisco 3640 with Cisco IOS® Software Release 12.1 as a gateway • Cisco 2600 with Cisco IOS Software Release 12.2 as a gatekeeper The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If you are working in a live network, ensure that you u
Summary of the content on the page No. 3
IP addressing can be done statically or dynamically, as explained in the Cisco ATA 186 Basic Configuration document. In the previous screen, the static IP address is used. 2. In the Cisco ATA 186 Configuration window, configure these fields: ♦ UID0 and UID1 Configure the E.164 addresses of voice ports 0 and 1. Both voice ports can not have the same E.164 address, as the ATA 186 can not hunt if one of the ports is busy. If both voice ports are assigned the same E.164 address, the call will always
Summary of the content on the page No. 4
GKOrProxy Configure the IP address of the gatekeeper. ♦ Once this is done, anything that is dialed from the ATA 186 voice ports is sent to the gatekeeper. 3. Click the Apply button and then reload the page. The ATA 186 takes 10 seconds to reconfigure itself. These examples are relevant configurations for the Cisco IOS gatekeeper and gateway: 2610−Gatekeeper interface Ethernet0/0 ip addreinterface Ethernet0/0 ip address 172.16.13.12 255.255.255.224 half−duplex h323 interface h323 h323−id pr
Summary of the content on the page No. 5
destination−pattern 300. session target ras !−−− Dial−peer to send the calls to ATA. ! Adding Security As of ATA software release 2.12, the options in this section are available to add security. Authenticate the Endpoint at the Gatekeeper with an H.323 ID Follow these steps to configure the ATA 186 to register with the H.323 ID: 1. Set the AutMethod field to 0 (the default is 1). The hexadecimal value that is to be configured for this field is 0x0. 2. Set the UseLoginID field to 1. 3. Configure
Summary of the content on the page No. 6
aaa authentication login h323 local aaa session−id common enable password ww ! username atagw1 !−−− Same as the LoginID0 and LoginID1 fields. username atagw2 username 3640 !−−− Same as the H.323 ID configured on the gateway. ! gatekeeper zone local gk2 cisco.com 172.16.13.12 security any !−−− Register after the H.323 ID or E.164 address is authenticated. no shutdown ! Authenticate the Endpoint at the Gatekeeper with an E.164 Address Follow these steps to configure the ATA 186 to register with t
Summary of the content on the page No. 7
Authenticate the Endpoint at the Gatekeeper with an H.323 ID and Password Follow these steps to configure the ATA 186 to register with the H.323 ID and password: 1. Set the AutMethod field to 1 (the default is 1). The hexadecimal value that is to be configured for this field is 0x1. This field is set to indicate that the ATA now looks for the password. 2. Set the UseLoginID field to 1. 3. Configure LoginID0 and LoginID1, with the H.323 IDs for the ATA 186. The ATA 186 registers as two different
Summary of the content on the page No. 8
Authenticate the Endpoint at the Gatekeeper with an E.164 Address and Password Follow these steps to configure the ATA 186 to register with the E.164 ID and password: 1. Set the AutMethod field to 1 (the default is 1). The hexadecimal value that is to be configured for this field is 0x0. This field is set to indicate that the ATA will now look for the password. 2. Set the UseLoginID field to 0. 3. Configure UID0 and UID1 with the E.164 IDs for the ATA 186. The ATA 186 registers as two different
Summary of the content on the page No. 9
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: 1. 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. 2. Set the UseLoginID field to 1. 3. Configure LoginID0 and LoginID1 with the H.323 IDs, followed by the separator and password for the ATA
Summary of the content on the page No. 10
Verify The example in this section shows the gatekeeper endpoint registration. To verify the configuration, issue the show gatekeeper endpoint command. GATEKEEPER ENDPOINT REGISTRATION CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags −−−−−−−−−−−−−− −−−− −−−−−−−−−−−−− −−−− −−−−−−−−− −−−− −−−−− 172.16.13.40 1720 172.16.13.40 50923 gk2 VOIP−GW E164−ID: 1234 H323−ID:
Summary of the content on the page No. 11
Note: The ATA 186 registers for the two voice ports separately. The ATA 186, therefore, gets authenticated twice as different H.323 terminals, as shown in this debug: 4w4d: AAA/AUTHEN/CONT (3800768902): continue_login (user='atagw1') 4w4d: AAA/AUTHEN (3800768902): status = GETPASS 4w4d: AAA/AUTHEN/CONT (3800768902): Method=LOCAL 4w4d: AAA/AUTHEN (3800768902): status = PASS 4w4d: AAA: parse name= idb type=−1 tty=−1 4w4d: AAA/MEMORY: create_user (0x83149EFC) user='atagw2'ruser='NULL'
Summary of the content on the page No. 12
GK−>1: RCF:TTL 300 GK−>0: RCF:TTL 300 SCC−>(0 0) 3000 active @0xab45555a (GK @0xac100d0c) !−−− Call made from voice port 0. [0]DTMF 1 [0]DTMF 2 [0]DTMF 3 [0]DTMF 4 [0]DTMF # Calling 1234 SCC−>(0 0) CLIP\ \SCC−>(0 0) \<0 0> dial<1234> GK<−0: ARQ: 0 GK−>0: ACF:0:direct call IRR in 240 sec CallRasCallBack: 1 33e15eb 33e206b 33e39b0 Connect to <0xac100d28 1720>>.. >>>>>>>> TX CALLER ID : 0x1 0x80 6 Q931<−0:Setup:CRV 25006 Q931−>0:Proceeding Connect H245... H245 TCP
Summary of the content on the page No. 13
write TCP err : 13 −33 [0:0]Rel LBRC Res Q931<−*:ReleaseComplete !−−− ATA side hangs up the call. write TCP err : 12 −33 GK<−0: DRQ:0 !−−− Disconnect request sent by ATA. SCC:ev=13[0:0] 4 0 [0:0]SCC: Disconnected GK−>0: DCF !−−− Disconnect confirm received. SCC−>(0 0) [0]MPT mode 0 No Dial Tone ATA Debug Example Both voice ports need a unique E.164 address, otherwise the ATA receives a Reject from the gatekeeper. During this time, you will see the ATA 186 being registered with one voice
Summary of the content on the page No. 14
• Configuring Voice over IP • Voice Technology Support • Voice and IP Communications Product Support • Recommended Reading: Troubleshooting Cisco IP Telephony • Technical Support & Documentation − Cisco Systems All contents are Copyright © 2006−2007 Cisco Systems, Inc. All rights reserved. Important Notices and Privacy Statement. Updated: Aug 06, 2007 Document ID: 19084
