Cisco ATA 186 Fails To Place A Call in A Gatekeeper Based Network........................................................... 1

Cisco − Cisco ATA 186 Fails to Place a Call in a Gatekeeper Based Network
Table of Contents
Cisco ATA 186 Fails to Place a Call in a Gatekeeper Based Network...........................................................1
Introduction.............................................................................................................................................1
Prerequisites............................................................................................................................................1
Requirements....................................................................................................................................1
Components Used.............................................................................................................................1
Conventions......................................................................................................................................1
Problem...................................................................................................................................................1
Solution...................................................................................................................................................2
Related Information................................................................................................................................5
i
Cisco ATA 186 Fails to Place a Call in a Gatekeeper
Based Network
Introduction
Prerequisites
Requirements
Components Used
Conventions
Problem
Solution
Related Information
Introduction
This document describes a problem that often happens in gatekeeper−based networks where the Cisco Analog
Telephone Adapter (ATA) 186 is used as a H.323 terminal. The document includes some background
technical information describing the problem, solution and some basic verification and troubleshooting
strategies. It is important to note that in the configuration below, the router and Cisco ATA 186 are located on
the same LAN. However, in a real implementation, all devices can be in different parts of your network.
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
This document is not restricted to specific software and hardware versions.
Conventions
For more information on document conventions, see the Cisco Technical Tips Conventions.
Problem
The problem can often occur on gatekeeper networks that are already successfully running with gateways. The
administrator tries to add the Cisco ATA 186 as a new device, but calls from the ATA 186 are rejected by the
gatekeeper.
• This problem can occur with any Cisco IOS® based gatekeeper and Cisco ATA 186.
• All Cisco IOS Software releases behave the same way.
To verify if you have this problem, you need to check for the following conditions:
1. Cisco ATA 186 should be registered to the gatekeeper. To check this, use the show gatekeeper
endpoints command.
2. The gatekeeper should reject the incoming call from Cisco ATA 186. To check this, use the debug
ras and debug h225 asn1 commands on the gatekeeper.
Solution
A default configuration for local zone does not allow the H.323 terminals to put calls through directly to the
destination. All terminals should place calls through a H.323 proxy. As the Cisco ATA 186 is a terminal, it
cannot place a call to the default gatekeeper configuration. To change the default behavior of gatekeeper to
terminals, you can alter the configuration using these commands:
no use−proxy gk−zone1.test.com default inbound−to terminal

no use−proxy gk−zone1.test.com default outbound−from terminal
For a description of the use−proxy command, refer to: Cisco IOS Voice, Video, and Fax Commands: Si
Through Z.
Default Gatekeeper ECV−2600−15 − Configuration For Work

With Gateways
!
hostname ECV−2610−15
!
interface Ethernet0/0
ip address 10.52.218.47 255.255.255.0
!
gatekeeper
zone local gk−zone1.test.com test.com
10.52.218.47
!−−− This command defines the local zone − the

!−−− GK name and zone name have the same meaning.
zone remote gk−zone2.test.com test.com 10.52.218.46 1719
!−−− This command defines the name of the remote GK (zone).
zone prefix gk−zone2.test.com 16..
!−−− This command explicitly defines the number length

!−−− with number of dots.
zone prefix gk−zone1.test.com 17.. gw−priority 10 gw_1
!−−− This command explicitly defines which GW will handle

!−−− calls for 17.. numbers.
!−−− This can be done for the local zones only.
gw−type−prefix 1#* default−technology
!−−− This command defines the default technology prefix

!−−− that's necessary for routing decisions.
no shutdown
!−−− This command turns the service up.
!
end
Gatekeeper ECV−2600−15 − Configuration For Work With
Gateways and H323 Terminals Without Proxy
!
hostname ECV−2610−15
!
interface Ethernet0/0
ip address 10.52.218.47 255.255.255.0
!
gatekeeper
zone local gk−zone1.test.com test.com 10.52.218.47
!−−− These two commands define the default terminals behavior

!−−− in the zone.
no shutdown
!
end
This output shows the zone status before and after adding changes to the configuration.
ECV−2610−15#show gatekeeper zone status
!−−− The first step is to check the zone status.
GATEKEEPER ZONES
================
GK name Domain Name RAS Address PORT FLAGS
−−−−−−− −−−−−−−−−−− −−−−−−−−−−− −−−−− −−−−−
gk−zone1.tes test.com 10.52.218.47 1719 LS

BANDWIDTH INFORMATION (kbps) :
Maximum total bandwidth : 0
Current total bandwidth : 0
Maximum interzone bandwidth : 0
Current interzone bandwidth : 0
Maximum session bandwidth : 0
SUBNET ATTRIBUTES :
All Other Subnets : (Enabled)
PROXY USAGE CONFIGURATION :
Inbound Calls from all other zones :
!−−− As the output below shows, terminals can work only

!−−− through proxy by default.
to terminals in local zone gk−zone1.test.com :

use proxy
to gateways in local zone gk−zone1.test.com :
do not use proxy
to MCUs in local zone gk−zone1.test.com :
do not use proxy
Outbound Calls to all other zones :
from terminals in local zone gk−zone1.test.com :
use proxy
from gateways in local zone gk−zone1.test.com :
do not use proxy
from MCUs in local zone gk−zone1.test.com :
do not use proxy
ECV−2610−15#configure terminal
!−−− The second step is to change the configuration.

!−−− Enter configuration commands, one per line. End with
!−−− CNTL/Z.
ECV−2610−15(config)#gatekeeper
ECV−2610−15(config−gk)#no use−proxy ?
WORD Local gatekeeper name this proxy usage applies to
ECV−2610−15(config−gk)#no use−proxy gk−zone1.test.com ?

default Proxy usage definition applies to connections
made to or from all other remote zones
remote−zone Proxy usage definition applies to connections
made to or from the specified remote−zone
ECV−2610−15(config−gk)#no use−proxy gk−zone1.test.com

default ?
inbound−to For all incoming calls
outbound−from For all outgoing calls
ECV−2610−15(config−gk)#no use−proxy gk−zone1.test.com default

inbound−to ?
gateway For all incoming calls to gateway(s)
mcu For all incoming calls to H.323 MCU device(s)
terminal For all incoming calls to H.323 terminal(s)
ECV−2610−15(config−gk)#$y gk−zone1.test.com default inbound−to

terminal ?
<cr>
ECV−2610−15(config−gk)#no use−proxy gk−zone1.test.com default

out terminal
ECV−2610−15(config−gk)#^Z
ECV−2610−15#
*Mar 3 10:30:21.522: %SYS−5−CONFIG_I: Configured from console
by console
ECV−2610−15#
ECV−2610−15#show run | b gatekeeper
!−−− Checkup of the new Gatekeeper configuration.
gatekeeper
zone local gk−zone1.test.com test.com 0.52.218.47
no shutdown
!
ECV−2610−15#show gatekeeper zone st
!−− The third step is to check the zone status again.
GATEKEEPER ZONES
================
GK name Domain Name RAS Address PORT FLAGS
−−−−−−− −−−−−−−−−−− −−−−−−−−−−− −−−−− −−−−−
gk−zone1.tes test.com 10.52.218.47 1719 LS

BANDWIDTH INFORMATION (kbps) :
Maximum total bandwidth : 0
Current total bandwidth : 0
Maximum interzone bandwidth : 0
Current interzone bandwidth : 0
Maximum session bandwidth : 0
SUBNET ATTRIBUTES :
All Other Subnets : (Enabled)
PROXY USAGE CONFIGURATION :
Inbound Calls from all other zones :
!−−− As the output below shows, now terminals can work without
!−−− proxy.
to terminals in local zone gk−zone1.test.com : do not

use proxy
to gateways in local zone gk−zone1.test.com : do not
use proxy
to MCUs in local zone gk−zone1.test.com : do not use
proxy
Outbound Calls to all other zones :
from terminals in local zone gk−zone1.test.com : do
not use proxy
from gateways in local zone gk−zone1.test.com : do not
use proxy
from MCUs in local zone gk−zone1.test.com : do not use
proxy
Related Information
• Cisco High−Performance Gatekeeper
• Configuring H.323 Gateways
• Configuring H.323 Gatekeepers and Proxies
• Configuring H.323 Support for Virtual Interfaces
• Voice Technologies
• Voice, Telephony and Messaging Devices
• Voice Software
• Voice, Telephony and Messaging TAC eLearning Solutions
• Recommended Reading: Troubleshooting Cisco IP Telephony
• Technical Support − Cisco Systems
All contents are Copyright © 1992−2003 Cisco Systems, Inc. All rights reserved. Important Notices and Privacy Statement.

Cisco ATA 186 Fails To Place A Call in A Gatekeeper Based Network........................................................... 1

Uploaded by

Copyright:

Available Formats

Cisco ATA 186 Fails To Place A Call in A Gatekeeper Based Network........................................................... 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cisco ATA 186 Fails To Place A Call in A Gatekeeper Based Network........................................................... 1

Uploaded by

Copyright:

Available Formats

Cisco − Cisco ATA 186 Fails to Place a Call in a Gatekeeper Based Network

no use−proxy gk−zone1.test.com default inbound−to terminal

Default Gatekeeper ECV−2600−15 − Configuration For Work

!−−− This command defines the local zone − the

zone remote gk−zone2.test.com test.com 10.52.218.46 1719

!−−− This command defines the name of the remote GK (zone).

zone prefix gk−zone2.test.com 16..

!−−− This command explicitly defines the number length

zone prefix gk−zone1.test.com 17.. gw−priority 10 gw_1

!−−− This command explicitly defines which GW will handle

gw−type−prefix 1#* default−technology

!−−− This command defines the default technology prefix

!−−− This command turns the service up.

!−−− These two commands define the default terminals behavior

ECV−2610−15#show gatekeeper zone status

!−−− The first step is to check the zone status.

gk−zone1.tes test.com 10.52.218.47 1719 LS

!−−− As the output below shows, terminals can work only

to terminals in local zone gk−zone1.test.com :

!−−− The second step is to change the configuration.

ECV−2610−15(config−gk)#no use−proxy gk−zone1.test.com ?

ECV−2610−15(config−gk)#no use−proxy gk−zone1.test.com

ECV−2610−15(config−gk)#no use−proxy gk−zone1.test.com default

ECV−2610−15(config−gk)#$y gk−zone1.test.com default inbound−to

ECV−2610−15(config−gk)#no use−proxy gk−zone1.test.com default

!−−− Checkup of the new Gatekeeper configuration.

ECV−2610−15#show gatekeeper zone st

!−− The third step is to check the zone status again.

gk−zone1.tes test.com 10.52.218.47 1719 LS

to terminals in local zone gk−zone1.test.com : do not

You might also like