Table Of Contents
Using Cisco 3600 and Cisco 2600 Series Routers as H.323 VoIP Gateways
H.323 VoIP Gateway Feature Summary
Additional Keyword for the Session Target Command
Configure Voice Port Parameters
Configure POTS and VoIP Dial Peers
Verify Dial Peer Configuration
Enable VoIP Gateway Functionality
Configure Gateway Interface Parameters
Verify the Gateway Interface Configuration
Using Cisco 3600 and Cisco 2600 Series Routers as H.323 VoIP Gateways
H.323 VoIP Gateway Feature Summary
In previous Cisco IOS Releases, the Cisco AS5300 voice service provider features included enhancements for both the functionality and configuration of gateways and Voice over IP (VoIP) gatekeepers. The architecture of these features provided the Quality of Service (QoS), stability, and functionality necessary for carrier class, real-time IP communications services. In this release, basic gateway Registration, Admission, and Status (RAS) protocol capability is extended to Cisco 3600 and Cisco 2600 series routers. Other features, such as authentication, authorization, and accounting (AAA) enhancements for security and accounting services, interactive voice response (IVR), Integrated Services Digital Network (ISDN) redirect number support, and rotary call pattern support, will be offered in future Cisco IOS releases.
Benefits
•
Carrier-class voice quality
•
•
List of Terms
AAA—Authentication, authorization, and accounting. AAA is a suite of network security services that provides the primary framework through which access control can be set up on your Cisco router or access server.
dial peer—An addressable call endpoint. In Voice over IP (VoIP), there are two types of dial peers: POTS and VoIP.
DNS—Domain name system used in address translation to convert H.323 IDs, URLs, or e-mail IDs to IP addresses. DNS is also used to assist in the location of remote gatekeepers and to reverse-map raw IP addresses to host names of administrative domains.
DNIS—Dialed number identification service (the called number). Feature of trunk lines where the called number is identified; this called number information is used to route the call to the appropriate service.
DSP—Digital signal processor.
DTMF—Dual tone multi-frequency.
E.164—International Telecommunication Union (ITU-T) recommendation for international telecommunication numbering. This recommendation provides the number structure and functionality for the 3 categories of numbers used for international public telecommunication—geographic areas, global services, and networks.
E&M—E&M stands for recEive and transMit (or Ear and Mouth). E&M is a trunking arrangement generally used for two-way switch-to-switch or switch-to-network connections. Cisco's E&M interface is an RJ-48 connector that allows connections to PBX trunk lines (tie lines).
endpoint—An H.323 terminal or gateway. An endpoint can call and be called. It generates and/or terminates the information stream.
gatekeeper—An H.323 entity on the LAN that provides address translation and control access to the LAN for H.323 terminals and gateways. The gatekeeper can provide other services to the H.323 terminals and gateways, such as bandwidth management and locating gateways. A gatekeeper maintains a registry of devices in the multimedia network. The devices register with the gatekeeper at startup, and request admission to a call from the gatekeeper.
gateway—An H.323 endpoint on the LAN that provides real-time, two-way communications between H.323 terminals on the LAN and other ITU-T terminals in the WAN, or to another H.323 gateway. A gateway allows H.323 terminals to communicate with non-H.323 terminals by converting protocols. A gateway is the point at which a circuit-switched call is encoded and repackaged into IP packets.
H.323—An ITU-T standard that describes packet-based video, audio, and data conferencing. H.323 is an umbrella standard that describes the architecture of the conferencing system, and refers to a set of other standards (H.245, H.225.0, and Q.931) to describe its actual protocol.
H.323 RAS—Registration, admission, and status. The RAS signaling protocol performs registration, admissions, bandwidth changes, status and disengage procedures between the VoIP gateway and the gatekeeper.
POTS—Plain Old Telephone Service. Basic telephone service supplying standard single line telephones, telephone lines, and access to the public switched telephone network.
PSTN—Public switched telephone network. PSTN refers to the local telephone company.
QoS—Quality of service, which refers to the measure of service quality provided to the user.
Technology prefix—Discriminators used to distinguish between gateways having specific capabilities within a given zone. In the exchange between the gateway and the gatekeeper, the technology prefix is used to select a gateway after the zone has been selected. Technology prefixes can be used to tell the gatekeeper that a certain technology is associated with a particular call (for example, 15# could mean a fax transmission). No standard defines what the numbers in a technology prefix mean; by convention, technology prefixes are designated by a pound (#) symbol as the last character.
VoIP—Voice over IP. The ability to carry normal telephone-style voice over an IP-based internet with POTS-like functionality, reliability, and voice quality. VoIP is a blanket term that generally refers to Cisco's standards based (for example, H.323) approach to IP voice traffic.
zone—A collection of all terminals, gateways, and multipoint control units (MCUs) managed by a single gatekeeper. A zone includes at least one terminal, and can include gateways or MCUs. A zone has only one gatekeeper. A zone can be independent of LAN topology and can be comprised of multiple LAN segments connected using routers or other devices.
Restrictions
The H.323 gateway feature and supporting software applications in Cisco IOS Release 12.0(2)XD require VCWare version 2.4.
Platforms
This feature is supported on the following platforms:
•
•
•
Prerequisites
Before you can configure your Cisco 3600 series router to serve as an H.323 VoIP gateway, you must first:
•
•
•
Supported MIBS and RFCs
None.
Functional Description
The Cisco VoIP gateway is a high-performance H.323-compliant gateway optimized for VoIP applications. Supporting up to two T1/E1 digital channels, it connects with existing telephones and fax machines through the Public Switched Telephone Network (PSTN), key systems, and PBXes, so that the process of placing calls over the IP network is transparent to users.
The gateway capability allows a Cisco 3600 or Cisco 2600 series router to function as an H.323 endpoint. Therefore, the gateway provides admission control, and address lookup and translation.
Gateway RAS Implementation
The Registration, Admission, and Status (RAS) signaling protocol performs registration, admissions, status, and disengage procedures between the H.323 VoIP gateway and the H.323 VoIP gatekeeper.
The following additions have been made to basic gateway functionality to implement RAS:
•
Note
Technology Prefixes
Technology prefixes are used to distinguish between gateways having specific capabilities within a given zone. In the exchange between the gateway and the gatekeeper, the technology prefix is used to select a gateway after the zone has been selected. You use the tech-prefix dial-peer configuration command to define technology prefixes.
In most cases, there is a dynamic protocol exchange between the gateway and the gatekeeper that enables the gateway to inform the gatekeeper about technology prefixes and where to forward calls. If, for some reason, that dynamic registry feature is not in effect, you can statically configure the gatekeeper to query the gateway for this information by configuring the gw-type-prefix command on the gatekeeper. Use the show gatekeeper gw-type-prefix to display how the gatekeeper has mapped the technology prefixes to local gateways.
For more information about configuring H.323 gateways, refer to Cisco IOS Release 11.3(6)NA 2 Configuring H.323 VoIP Gateway for Cisco Access Platforms. For more information about configuring H.323 gatekeepers, refer to Cisco IOS Release 11.3(6) 2 Configuring H.323 VoIP Gatekeeper for Cisco Access Platforms.
Additional Keyword for the Session Target Command
The session target dial-peer command indicates the address of the remote gateway where the call is terminated. A new keyword has been added to the session target command to indicate that the RAS protocol is being used—meaning that a gatekeeper will be consulted to translate the E.164 address to an IP address.
You can now define the address of a remote gateway in the following ways:
•
•
•
For more information about this revised command, refer to the Command Reference section.
Configuration Task List
To configure a Cisco 3600 or Cisco 2600 series router to perform as an H.323 VoIP gateway using RAS, perform the following tasks:
•
Configure Voice Port Parameters
To configure voice port parameters for an E&M voice port, use the following commands:
For more information about configuring voice ports, refer to the "Configuring Voice Ports" chapter in the Cisco IOS Release 12.0 Voice, Video, and Home Applications Configuration Guide.
Verify Voice Port Parameters
To verify voice port parameters, use the show voice port command.
The following is sample output from the show voice port command for an E&M voice port on the Cisco 3600 series:
router# show voice port 1/0/0E&M Slot is 1, Sub-unit is 0, Port is 0Type of VoicePort is E&MOperation State is UPAdministrative State is UP<--snip-->Voice card specific Info Follows:Signal Type is wink-startOperation Type is 4-wireImpedance is set to 600r OhmE&M Type is 5Dial Type is dtmf<--snip-->For more information about the show voice port command, refer to the Cisco IOS Release 12.0 Voice, Video, and Home Applications Command Reference.
Configure the H.323 Gateway
To configure the H.323 Gateway, you need to perform the following tasks:
•
•
•
Configure POTS and VoIP Dial Peers
The first step in configuring the H.323 gateway is to define the applicable POTS and VoIP dial peers. The POTS dial peer informs the system which voice port to direct incoming VoIP calls to and (optionally) defines that RAS-initiated calls will have a technology prefix prepended to the destination telephone number. The VoIP dial peer defines how to direct calls that originate from a local voice port into the VoIP cloud to the session target. The session target indicates the address of the remote gateway where the call is terminated. As mentioned, there are several different ways to define the destination gateway address: by statically configuring the IP address of the gateway, by defining the DNS of the gateway, or by using RAS. If you use RAS, that gateway determines the destination target by querying the RAS gatekeeper.
To configure POTS dial peer for the H.323 gateway, use the following commands:
For more information about POTS dial peers, refer to the Cisco IOS Release 12.0 Voice, Video, and Home Applications Configuration Guide. For more information about any of the commands used to configure VoIP dial peers, refer to the Cisco IOS Release 12.0 Voice, Video, and Home Applications Command Reference.
To configure VoIP dial peer for the H.323 gateway, use the following commands:
For more information about POTS dial peers, refer to the Cisco IOS Release 12.0 Voice, Video, and Home Applications Configuration Guide. For more information about any of the commands used to configure POTS dial peers, refer to the Cisco IOS Release 12.0 Voice, Video, and Home Applications Command Reference.
Verify Dial Peer Configuration
Verify the POTS and VoIP dial-peer configuration by using the show dial-peer voice command.
The following example shows output from the show dial-peer voice command for a VoIP dial peer using RAS:
5300-1# show dial-peer voice 1234VoiceOverIpPeer1234tag = 1234, destination-pattern = 1234',answer-address = ',group = 1234, Admin state is up, Operation state is up,incoming called-number = ', connections/maximum = 0/unlimited,application associated:type = voip, session-target = ras',technology prefix: 8#ip precedence = 0, UDP checksum = disabled,session-protocol = cisco, req-qos = controlled-load,acc-qos = best-effort,fax-rate = voice, codec = g729r8,Expect factor = 10, Icpif = 30,VAD = enabled, Poor QOV Trap = disabled,<--snip-->Enable VoIP Gateway Functionality
The next step in configuring an H.323 gateway is to enable VoIP gateway functionality by using the gateway command.
To enable gateway functionality, use the following commands:
1
configure terminal
Enter global configuration mode.
2
gateway
Enable the VoIP gateway.
Configure Gateway Interface Parameters
The next step in configuring an H.323 gateway is to configure the gateway interface parameters. First define which interface will be presented to the VoIP network as this gateway's H.323 interface. Only one interface is allowed to be the gateway interface. You can select either the interface that is connected to the gatekeeper or a loopback interface. The interface that is connected to the gatekeeper is usually a LAN interface (for example, Fast Ethernet, Ethernet, FDDI, or Token Ring).
After you define the gateway interface, configure the gateway to discover the gatekeeper either through multicasting or by directing it to a specific host. Then configure the gateway's H.323 identification number and any technology prefixes that this gateway should register with the gatekeeper.
To define the interface to be used as the H.323 gateway interface and configure the H.323 gateway interface parameters, use the following commands, beginning in global configuration mode:
Verify the Gateway Interface Configuration
•
In the following example, gateway GW13.cisco.com has successfully registered itself with gatekeeper GK15.cisco.com:
hostname#show gatewayGateway GW13.cisco.com is registered to Gatekeeper GK15.cisco.com•
In the following example, gatekeeper 'GK15.cisco.com' has 4 technology prefixes. Prefix 31# is statically defined on the gatekeeper, while 23#, 22#, and 13# have been dynamically registered by gateways.
hostname#show gatekeeper gw-type-prefixGATEWAY TYPE PREFIX TABLE=========================Prefix:31#*Statically-configured gateways (not necessarily currently registered):1.9.53.13:1720Zone:GK15.cisco.com Registered gateways for this prefix:1.9.53.13:1720 GW13Prefix:23#*Zone:GK15.cisco.com Registered gateways for this prefix:1.9.74.23:1720 GW23-c2611Prefix:22#*Zone:GK15.cisco.com Registered gateways for this prefix:1.9.74.22:1720 GW22-c2611Prefix:13#*Zone:GK15.cisco.com Registered gateways for this prefix:1.9.53.13:1720 GW13Tips
•
In the following example, gateway GW13.cisco.com sends a RAS registration request message (RRQ) to gatekeeper GK15.cisco.com at IP address 1.9.53.15. GW13.cisco.com then receives a registration confirmation (RCF) message from the gatekeeper. If there is no response, it could mean that the gatekeeper is offline or improperly addressed. If you receive a reject message (RRJ), it could mean that the gatekeeper is unable to handle another gateway or that the registration information is incorrect.
hostname#debug ras*Mar 13 19:53:34.231: RASlib::ras_sendto:msg length 105 from1.9.53.13:8658 to 1.9.53.15:1719*Mar 13 19:53:34.231: RASLib::RASSendRRQ:RRQ (seq# 36939) sentto 1.9.53.15*Mar 13 19:53:34.247: RASLib::RASRecvData:successfully rcvdmessage of length 105 from 1.9.53.15:1719*Mar 13 19:53:34.251: RASLib::RASRecvData:RCF (seq# 36939) rcvdfrom [1.9.53.15:1719] on sock [0x6168356C•
In the following example, the debug h225 asn1 command displays the actual contents of the RAS registration message exchange between gateway GW13.cisco.com and gatekeeper GK15.cisco.com. The debug h225 asn1 command also displays the technology prefixes that gateway GW13.cisco.com is registering:
hostname#debug h225 asn1H.225 ASN1 Messages debugging is on3640GW.13#value RasMessage ::= registrationRequest :*Mar 13 20:16:45.295: {*Mar 13 20:16:45.295: requestSeqNum 037001,*Mar 13 20:16:45.295: protocolIdentifier { 0 0 8 2250 0 1 },*Mar 13 20:16:45.295: discoveryComplete TRUE,*Mar 13 20:16:45.295: callSignalAddress*Mar 13 20:16:45.295: {*Mar 13 20:16:45.295: ipAddress :*Mar 13 20:16:45.295: {*Mar 13 20:16:45.295: ip '0109350D'H,*Mar 13 20:16:45.295: port 01720*Mar 13 20:16:45.295: }*Mar 13 20:16:45.295: },*Mar 13 20:16:45.295: rasAddress*Mar 13 20:16:45.295: {*Mar 13 20:16:45.295: ipAddress :*Mar 13 20:16:45.295: {*Mar 13 20:16:45.295: ip '0109350D'H,*Mar 13 20:16:45.299: port 04635*Mar 13 20:16:45.299: }*Mar 13 20:16:45.299: },*Mar 13 20:16:45.299: terminalType*Mar 13 20:16:45.299: {*Mar 13 20:16:45.299: gateway*Mar 13 20:16:45.299: {*Mar 13 20:16:45.299: protocol*Mar 13 20:16:45.299: {*Mar 13 20:16:45.299: voice :*Mar 13 20:16:45.299: {*Mar 13 20:16:45.299: supportedPrefixes*Mar 13 20:16:45.299: {*Mar 13 20:16:45.299: {*Mar 13 20:16:45.299: prefix e164 :"13#"*Mar 13 20:16:45.299: }*Mar 13 20:16:45.299: }*Mar 13 20:16:45.299: }*Mar 13 20:16:45.299: }*Mar 13 20:16:45.299: },*Mar 13 20:16:45.299: mc FALSE,*Mar 13 20:16:45.299: undefinedNode FALSE*Mar 13 20:16:45.299: },*Mar 13 20:16:45.299: terminalAlias*Mar 13 20:16:45.303: {*Mar 13 20:16:45.303: h323-ID :"GW13.cisco.com"*Mar 13 20:16:45.303: },*Mar 13 20:16:45.303: gatekeeperIdentifier "GK15.cisco.com",*Mar 13 20:16:45.303: endpointVendor*Mar 13 20:16:45.303: {*Mar 13 20:16:45.303: vendor*Mar 13 20:16:45.303: {*Mar 13 20:16:45.303: t35CountryCode 0181,*Mar 13 20:16:45.303: t35Extension 00,*Mar 13 20:16:45.303: manufacturerCode 018*Mar 13 20:16:45.303: }*Mar 13 20:16:45.303: }*Mar 13 20:16:45.303: }*Mar 13 20:16:45.303:0CC09088 06000891 4A000180 01000109 350D06B8 01000109 350D121B 0880013C05050100 40460000 01400D00 47005700 31003300 40006300 69007300 63006F002E006300 6F006D1A 0047004B 00310035 002E0063 00690073 0063006F 002E0063006F006D 00B50000 1210C09088 06000891 4A000100 01400D00 47005700 31003300 40006300 6900730063006F00 2E006300 6F006D1A 0047004B 00310035 002E0063 00690073 0063006F002E0063 006F006D 1E003600 30004400 37004500 37003300 43003000 3000300030003000 30003000 46value RasMessage ::= registrationConfirm :*Mar 13 20:16:45.335: {*Mar 13 20:16:45.335: requestSeqNum 037001,*Mar 13 20:16:45.335: protocolIdentifier { 0 0 8 2250 0 1 },*Mar 13 20:16:45.335: callSignalAddress*Mar 13 20:16:45.335: {*Mar 13 20:16:45.335: },*Mar 13 20:16:45.335: terminalAlias*Mar 13 20:16:45.335: {*Mar 13 20:16:45.335: h323-ID :"GW13.cisco.com"*Mar 13 20:16:45.339: },*Mar 13 20:16:45.339: gatekeeperIdentifier "GK15.cisco.com",*Mar 13 20:16:45.339: endpointIdentifier "60D7E73C0000000F"*Mar 13 20:16:45.339: }*Mar 13 20:16:45.339:3640GW.13#Configuration Examples
This section contains the following configuration examples:
Configuring an H.323 Gateway
The following example shows how to configure a Cisco 3600 series router as an H.323 gateway:
! Configure the voice-port parameters.! This voice-port is an analog E&M-wink port using 4-wire, type 5 interface!voice-port 2/0/0operation 4-wiretype 5!! Setup a pots dial peer to direct calls incoming VoIP calls to the voice-port.! This dial peer defines that the RAS initiated call will be received with a tech! prefix of 13#!dial-peer voice 13200 potsdestination-pattern 13#13200port 2/0/0!! Setup a VoIP dial-peer to direct calls originated from a local voice-port! into the VoIP cloud. In this example, the session target indicates! that the destination target is determined by querying the RAS gatekeeper.! The tech-prefix command means that the H.323 gateway will ask the RAS gatekeeper to! direct calls using the technology prefix of 14#.!dial-peer voice 14 voipdestination-pattern 14...tech-prefix 14#session target ras!! Enable Gateway functionality with global config command.!gateway!! Choose an interface to be this gateway's H.323 interface. In this example, the! gateway is directed toward a specific host. Then define this gateway's H.323 ID, and! configure any tech prefixes that this gateway should register with the gatekeeper.! In this example, gateway GW13 tells gatekeeper GK15 to route any calls with a pattern! than begins with 13# to GW13. Dial-peer 14 expects that some other gateway has! register tech-prefix 14#.!interface Ethernet0/0ip address 172.9.53.13 255.255.255.0h323-gateway voip interfaceh323-gateway voip id GK15.cisco.com ipaddr 172.9.53.15 1719h323-gateway voip h323-id GW13@cisco.comh323-gateway voip tech-prefix 13#!Configuring a RAS Gatekeeper
For RAS to work on an H.323 gateway, you need to configure a corresponding RAS gatekeeper. The following example configures a Cisco 3600 series router as a RAS gatekeeper. For more information about configuring gatekeepers, refer to the Cisco IOS Release 11.3(6)NA2 document, Configuring the Cisco AS5300 for Voice Service Provider Features.
! Define this Ethernet port as the RAS gatekeeper.interface Ethernet0/0ip address 172.9.53.15 255.255.255.0!gatekeeper!! Specify the name of the local zone that this gatekeeper managers. Specify the IP! address that the gatekeeper advertises.zone local GK15.cisco.com cisco.com 172.9.53.15!! Statically define a remote zone and the associated gatekeeper's IP address.zone remote GK21.cisco.com cisco.com 172.9.74.21 1719!! Statically define the E.164 prefixes that a remote zone handles. This causes GK15 to! direct any call with a called number that matches 22* (22 and any number of trailing! digits) to GK21. This is not the same as a tech prefix. If a call comes in with an! E.164 pattern of (220) 555-1234, it will be routed to GK21 because the pattern! matches 22*.zone prefix GK21.cisco.com 22*zone prefix GK21.cisco.com 23*!! Statically define a tech prefix routing. Any call that comes in to the gatekeeper! with a technology prefix of 88# (the * catches any following E.164 address), is! directed to the gateway at IP address 172.9.53.13. This is a static technology prefix! definition. The gateway can also dynamically register its tech-prefixes with the! gatekeeper.gw-type-prefix 88#* gw ipaddr 172.9.53.13 1720!! Activate the gatekeeper function by activating the port.no shutdown!Command Reference
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command reference.
•
•
•
•
•
•
•
•
gateway
To enable the H.323 VoIP gateway, use the gateway global configuration command. Use the no form of this command to cancel the registration of this gateway with the gatekeeper.
gateway
no gatewaySyntax Description
This command has no keywords or arguments.
Default
The gateway is not registered.
Command Mode
Global configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(6)NA2.
Use the gateway command to enable H.323 VoIP gateway functionality. After you enable the gateway, it will attempt to discover a gatekeeper by using the H.323 RAS GRQ message. If you enter the no gateway command, the H.323 VoIP gateway will cancel this registration with the gatekeeper using the H.323 RAS URQ message.
Example
The following example enables the H.323 gateway:
configure terminalgatewayh323-gateway voip h.323-id
To configure the H.323 name of the gateway identifying this gateway to its associated gatekeeper, use the h323-gateway voip h.323-id interface configuration command. Use the no form of this command to disable this defined gateway name.
h323-gateway voip h323-id interface-id
no h323-gateway voip h323-id interface-idSyntax Description
Default
No gateway identification is defined.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(6)NA2.
Example
The following example configures Ethernet interface 0/0 as the gateway interface. In this example, the gateway ID is GW13@cisco.com.
interface Ethernet0/0ip address 172.9.53.13 255.255.255.0h323-gateway voip interfaceh323-gateway voip id GK15.cisco.com ipaddr 172.9.53.15 1719h323-gateway voip h323-id GW13@cisco.comh323-gateway voip tech-prefix 13#Related Commands
h323-gateway voip id
h323-gateway voip interface
h323-gateway voip tech-prefixh323-gateway voip id
To define the name and location of the gatekeeper for this gateway, use the h323-gateway voip id interface configuration command. Use the no form of this command to disable this gatekeeper identification.
h323-gateway voip id gatekeeper-id {ipaddr ip-address [port-number] | multicast}
no h323-gateway voip id gatekeeper-id {ipaddr ip-address [port-number] | multicast}Syntax Description
Default
No gatekeeper identification is defined.
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(6)NA2.
This command tells the H.323 gateway associated with this interface which H.323 gatekeeper to talk to and where to locate it. The gatekeeper ID configured here must exactly match the gatekeeper ID in the gatekeeper configuration.
Example
The following example configures Ethernet interface 0/0 as the gateway interface. In this example, the gatekeeper ID is GK15.cisco.com and its IP address is 172.9.53.15 (using port 1719).
interface Ethernet0/0ip address 172.9.53.13 255.255.255.0h323-gateway voip interfaceh323-gateway voip id GK15.cisco.com ipaddr 172.9.53.15 1719h323-gateway voip h323-id GW13@cisco.comh323-gateway voip tech-prefix 13#Related Commands
h323-gateway voip h323-id
h323-gateway voip interface
h323-gateway voip tech-prefixh323-gateway voip interface
To configure this interface as an H.323 interface, use the h323-gateway voip interface interface configuration command. Use the no form of this command to disable H.323 functionality for this interface.
h323-gateway voip interface
no h323-gateway voip interfaceSyntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(6)NA 2.
Example
The following example configures Ethernet interface 0/0 as the gateway interface. In this example, the h323-gateway voip interface command configures this interface as an H.323 interface.
interface Ethernet0/0ip address 172.9.53.13 255.255.255.0h323-gateway voip interfaceh323-gateway voip id GK15.cisco.com ipaddr 172.9.53.15 1719h323-gateway voip h323-id GW13@cisco.comh323-gateway voip tech-prefix 13#Related Commands
h323-gateway voip h323-id
h323-gateway voip id
h323-gateway voip tech-prefixh323-gateway voip tech-prefix
To define the technology prefix that the gateway will register with the gatekeeper, use the h323-gateway voip tech-prefix interface configuration command. Use the no form of this command to disable this defined technology prefix.
h323-gateway voip tech-prefix prefix
no h323-gateway voip tech-prefix prefixSyntax Description
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(6)NA2.
This command defines a technology prefix that the gateway will then register with the gatekeeper. Technology prefixes can be used as a discriminator so that the gateway can tell the gatekeeper that a certain technology is associated with a particular call (for example, 15# could mean a fax transmission), or it can be used like an area code for more generic routing. No standard currently defines what the numbers in a technology prefix mean. By convention, technology prefixes are designated by a pound (#) symbol as the last character.
Note
Example
The following example configures Ethernet interface 0/0 as the gateway interface. In this example, the technology prefix is defined as 13#.
interface Ethernet0/0ip address 172.9.53.13 255.255.255.0h323-gateway voip interfaceh323-gateway voip id GK15.cisco.com ipaddr 172.9.53.15 1719h323-gateway voip h323-id GW13@cisco.comh323-gateway voip tech-prefix 13#Related Commands
h323-gateway voip id
h323-gateway voip interface
h323-gateway voip h323-idsession target
To specify a network-specific address for a specified dial peer, use the session target dial-peer configuration command. Use the no form of this command to disable the specified target address.
For the Cisco 3600 series Voice over IP:
session target {ipv4:destination-address | dns:[$s$. | $d$. | $e$. | $u$.] host-name | loopback:rtp | loopback:compressed | loopback:uncompressed | ras}
no session targetSyntax Description
Default
The default for this command is enabled with no IP address or domain name defined.
Command Mode
Dial-peer configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(1)T.
Use the session target command to specify a network-specific address or domain name for a dial peer. Whether you select a network-specific address or a domain name depends on the session protocol you select.
The session target loopback command is used for testing the voice transmission path of a call. The loopback point will depend on the call origination and the loopback type selected.
The session target dns command can be used with or without the specified wildcards. Using the optional wildcards can reduce the number of VoIP dial-peer session targets you need to configure if you have groups of numbers associated with a particular router.
Use the session target ras command to specify that the RAS protocol is being used to determine the IP address of the session target.
Examples
The following example configures a session target using DNS for a host, "voice_router," in the domain "cisco.com:"
dial-peer voice 10 voipsession target dns:voice_router.cisco.comThe following example configures a session target using DNS, with the optional $u$. wildcard. In this example, the destination pattern has been configured to allow for any 4-digit extension, beginning with the numbers 1310222. The optional wildcard $u$. indicates that the router will use the unmatched portion of the dialed number—in this case, the 4-digit extension, to identify the dial peer. As in the previous example, the domain is "cisco.com."
dial-peer voice 10 voipdestination-pattern 1310222....session target dns:$u$.cisco.comThe following example configures a session target using dns, with the optional $d$. wildcard. In this example, the destination pattern has been configured for 13102221111. The optional wildcard $d$. indicates that the router will use the destination pattern to identify the dial peer in the "cisco.com" domain.
dial-peer voice 10 voipdestination-pattern 13102221111session target dns:$d$.cisco.comThe following example configures a session target using DNS, with the optional $e$. wildcard. In this example, the destination pattern has been configured for 12345. The optional wildcard $e$. indicates that the router will reverse the digits in the destination pattern, add periods between the digits, and then use this reverse-exploded destination pattern to identify the dial peer in the "cisco.com" domain.
dial-peer voice 10 voipdestination-pattern 12345session target dns:$e$.cisco.comThe following example configures a session target using RAS:
dial-peer voice 11 vofrdestination-pattern 13102221111session target rasRelated Commands
destination-pattern
session protocolshow gateway
To display the current H.323 VoIP gateway status, use the show gateway privileged EXEC command.
show gateway
Syntax Description
This command has no keywords or arguments.
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(6)NA2.
Example Output
The following is sample output from the show gateway command. This sample output shows that gateway voip2@vm1lab is enabled and registered to gatekeeper gk1vm1lab.
router#show gatewayGateway voip2@vm1lab is registered to Gatekeeper gk1.vm1labtech-prefix
To specify a particular technology prefix to be prepended to the destination pattern of a specific dial peer, use the tech-prefix dial-peer configuration command. Use the no form of this command to disable the defined technology prefix for this dial peer.
tech-prefix number
no tech-prefix numberSyntax Description
Default
No technology prefix is defined.
Command Mode
Dial-peer configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(6)NA2.
Technology prefixes are used to distinguish between gateways having specific capabilities within a given zone. In the exchange between the gateway and the gatekeeper, the technology prefix is used to select a gateway after the zone has been selected. Use the tech-prefix command to define technology prefixes.
Technology prefixes can be used as a discriminator so that the gateway can tell the gatekeeper that a certain technology is associated with a particular call (for example, 15# could mean a fax transmission), or it can be used like an area code for more generic routing. No standard defines what the numbers in a technology prefix mean; by convention, technology prefixes are designated by a pound (#) symbol as the last character.
In most cases, there is a dynamic protocol exchange between the gateway and the gatekeeper that enables the gateway to inform the gatekeeper about technology prefixes and where to forward calls. If, for some reason, that dynamic registry feature is not in effect, you can statically configure the gatekeeper to query the gateway for this information by configuring the gw-type-prefix command on the gatekeeper. Use the show gatekeeper gw-type-prefix to display how the gatekeeper has mapped the technology prefixes to local gateways.
Note
The gateway prepends the technology prefix to the called number that matches the VoIP dial peer's destination pattern. It prepends the technology prefix when an admission request is made to the gatekeeper and when a subsequent call setup match is sent to the endpoint identified by the gatekeeper. This is why the technology prefix configured for a dial peer must match the technology prefix on the terminating gateway.
Examples
The following example defines a technology prefix of 14# for the specified dial peer. In this example, the technology prefix means that the H.323 gateway will ask the RAS gatekeeper to direct calls using the technology prefix of 14#.
dial-peer voice 10 voipdestination-pattern 14...tech-prefix 14#Related Commands
gw-type-prefix
show gatekeeper gw-type-prefixDebug Commands
This section describes the following debug commands:
•
•
debug cch323 h225
Use the debug cch323 h225 command to trace the state transition of the H.225 state machine based on the processed events. Use the no form of this command to disable debugging output.
debug cch323 h225
no debug cch323 h225Syntax Description
This command has no keywords or arguments.
Default
Disabled
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(6)NA2.
Sample Output
The following output shows a series of states and events for the H.225 state machine:
20:59:17:Set new event H225_EVENT_SETUP20:59:17:H225 FSM:received event H225_EVENT_SETUP while at state H225_IDLE20:59:17:Changing from H225_IDLE state to H225_SETUP state20:59:17:cch323_h225_receiver:received msg of type SETUPCFM_CHOSEN20:59:17:H225 FSM:received event H225_EVENT_SETUP_CFM_IND while at stateH225_SETUP20:59:17:Changing from H225_SETUP state to H225_ACTIVE state20:59:17:Set new event H225_EVENT_H245_SUCCESS20:59:17:H225 FSM:received event H225_EVENT_H245_SUCCESS while at stateH225_ACTIVE20:59:20:Set new event H225_EVENT_RELEASE20:59:20:H225 FSM:received event H225_EVENT_RELEASE while at stateH225_ACTIVE20:59:20:Changing from H225_ACTIVE state to H225_WAIT_FOR_DRQ state20:59:20:Set new event H225_EVENT_RAS_SUCCESS20:59:20:H225 FSM:received event H225_EVENT_RAS_SUCCESS while at stateH225_WAIT_FOR_DRQ20:59:20:Changing from H225_WAIT_FOR_DRQ state to H225_IDLE stateState Descriptions
Definitions of the different states of the H.225 state machine are as follows:
•
•
•
•
•
•
•
•
Events Description
Definitions of the different events of the H.225 state machine are as follows:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
debug cch323 h245
Use the debug cch323 h245 command to trace the state transition of the H.245 state machine based on the processed events. Use the no form of this command to disable debugging output.
debug cch323 h245
no debug cch323 h245Syntax Description
This command has no keywords or arguments.
Default
Disabled
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(6)NA2.
The H.245 state machines include the following 3 state machines:
•
•
•
Sample Output
The following output shows a series of states and events for the H.245 state machine:
20:58:23:Changing to new event H245_EVENT_MSD20:58:23:H245 MS FSM:received event H245_EVENT_MSD while at stateH245_MS_NONE20:58:23:changing from H245_MS_NONE state to H245_MS_WAIT state20:58:23:Changing to new event H245_EVENT_CAP20:58:23:H245 CAP FSM:received event H245_EVENT_CAP while at stateH245_CAP_NONE20:58:23:changing from H245_CAP_NONE state to H245_CAP_WAIT state20:58:23:cch323_h245_receiver:received msg of typeM_H245_MS_DETERMINE_INDICATION20:58:23:Changing to new event H245_EVENT_MS_IND20:58:23:H245 MS FSM:received event H245_EVENT_MS_IND while at stateH245_MS_WAIT20:58:23:cch323_h245_receiver:received msg of typeM_H245_CAP_TRANSFER_INDICATION20:58:23:Changing to new event H245_EVENT_CAP_IND20:58:23:H245 CAP FSM:received event H245_EVENT_CAP_IND while at stateH245_CAP_WAIT20:58:23:cch323_h245_receiver:received msg of typeM_H245_MS_DETERMINE_CONFIRM20:58:23:Changing to new event H245_EVENT_MS_CFM20:58:23:H245 MS FSM:received event H245_EVENT_MS_CFM while at stateH245_MS_WAIT20:58:23:changing from H245_MS_WAIT state to H245_MS_DONE state0:58:23:cch323_h245_receiver:received msg of type M_H245_CAP_TRANSFER_CONFIRM20:58:23:Changing to new event H245_EVENT_CAP_CFM20:58:23:H245 CAP FSM:received event H245_EVENT_CAP_CFM while at stateH245_CAP_WAIT20:58:23:changing from H245_CAP_WAIT state to H245_CAP_DONE state20:58:23:Changing to new event H245_EVENT_OLC20:58:23:H245 OLC FSM:received event H245_EVENT_OLC while at stateH245_OLC_NONE20:58:23:changing from H245_OLC_NONE state to H245_OLC_WAIT state20:58:23:cch323_h245_receiver:received msg of typeM_H245_UCHAN_ESTABLISH_INDICATION20:58:23:Changing to new event H245_EVENT_OLC_IND20:58:23:H245 OLC FSM:received event H245_EVENT_OLC_IND while at stateH245_OLC_WAIT20:58:23:cch323_h245_receiver:received msg of type M_H245_UCHAN_ESTAB_ACK20:58:23:Changing to new event H245_EVENT_OLC_CFM20:58:23:H245 OLC FSM:received event H245_EVENT_OLC_CFM while at stateH245_OLC_WAIT20:58:23:changing from H245_OLC_WAIT state to H245_OLC_DONE stateState Definitions
Definitions of the different states of the H.245 state machine are as follows:
•
•
•
•
•
•
•
•
•
Event Definitions
Definitions of the different events of the H.245 state machine are as follows:
•
•
•
•
•
•
•
•
•
•
•
•
debug cch323 ras
Use the debug cch323 ras command to trace the state transition of the RAS state machine based on the processed events. Use the no form of this command to disable debugging output.
debug cch323 ras
no debug cch323 rasSyntax Description
This command has no keywords or arguments.
Default
Disabled
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(6)NA2.
RAS operates in two state machines. One global state machine controls the overall RAS operation of the gateway. The other state machine is a per-call state machine that controls the active calls.
Sample Output
The following output shows a series of states and events for the RAS state machine:
20:58:49:Changing to new event CCH323_RAS_EVENT_SEND_RRQcch323_run_ras_sm:received event CCH323_RAS_EVENT_SEND_RRQ while at CCH323_RAS_STATE_IDLE statecch323_run_ras_sm:changing to CCH323_RAS_STATE_RRQ statecch323_ras_receiver:received msg of type RCF_CHOSENcch323_run_ras_sm:received event CCH323_RAS_EVENT_RCF while at CCH323_RAS_STATE_RRQ statecch323_run_ras_sm:changing to CCH323_RAS_STATE_IDLE state20:58:59:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_NEWCALL while at CCH323_RAS_STATE_IDLE state20:58:59:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_ARQcch323_ras_receiver:received msg of type ACF_CHOSEN20:58:59:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_ACF while atCCH323_RAS_STATE_ARQ state20:58:59:cch323_percall_ras_sm:changing to new stateCCH323_RAS_STATE_ACTIVE20:59:02:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_CALLDISC whileat CCH323_RAS_STATE_ACTIVE state20:59:02:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_DRQcch323_ras_receiver:received msg of type DCF_CHOSEN20:59:02:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_DCF while atCCH323_RAS_STATE_DRQ state20:59:02:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_IDLE20:59:04:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_IRR while atCCH323_RAS_STATE_ACTIVE state20:59:04:cch323_percall_ras_sm:changing to new stateCCH323_RAS_STATE_ACTIVE
State Definitions
Definitions of the different events of the RAS state machine are as follows:
•
•
•
•
•
•
•
•
Event Definitions
Definitions of the different events of the RAS state machine are as follows:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
debug h225
Use the debug h225 command to display additional information about the actual contents of H.225 RAS messages. Use the no form of this command to disable debug output.
debug h225 {asn1 | events}
no debug debug h225 {asn1 | events}Syntax Description
Default
Disabled
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(6)NA2
Both versions of the debug H.225 command display information about H.225 messages. H.225 messages are used to exchange RAS information between gateways and gatekeepers as well as to exchange Q.931 information between gateways.
The debug h225 events command displays key Q.931 events that occur when placing a H.323 call from one gateway to another. Q.931 events are carried in H.225 messages. This command enables you to monitor Q.931 state changes such as setup, alert, connected, and released.
Note
The debug h225 asn1command displays the ASN.1 contents of any H.225 message sent or received that contains ASN.1 content. Not all H.225 messages contain ASN.1 content. Some messages contain both Q.931 information and ASN.1 information; if you enter this command, only ASN.1 information will be displayed.
Sample Output
The following sample output for the debug h225 events command shows a call being placed from gateway GW13 to gateway GW14. Before the call was placed, the gateway exchanged RAS messages with the gatekeeper. Because RAS messages do not contain Q.931 information, these messages do not appear in this output.
3640GW.13# debug h225 eventsH.225 Event Messages debugging is on3640GW.13#*Mar 2 02:47:14.689: H225Lib::h225TConn:connect in progress on socket [2]*Mar 2 02:47:14.689: H225Lib::h225TConn:Q.931 Call State is initialized to be [Null].*Mar 2 02:47:14.697:Hex representation of the SETUP TPKT to send.0300004D080200DC05040380C0A36C0991313323313333303070099131342331343330307E00260500 80060008914A000102004B1F5E5D8990006C0000000005BF7454000C0700000000000000*Mar 2 02:47:14.701:*Mar 2 02:47:14.701: H225Lib::h225SetupRequest:Q.931 SETUP sent from socket [2]*Mar 2 02:47:14.701: H225Lib::h225SetupRequest:Q.931 Call State changed to [Call Initiated].*Mar 2 02:47:14.729:Hex representation of the received TPKT03000021080280DC013401017E0012050340060008914A000100000109350E2B28*Mar 2 02:47:14.729:*Mar 2 02:47:14.729: H225Lib::h225RecvData:Q.931 ALERTING received from socket [2]*Mar 2 02:47:14.729: H225Lib::h225RecvData:Q.931 Call State changed to [Call Delivered].*Mar 2 02:47:17.565:Hex representation of the received TPKT03000034080280DC07040380C0A37E0023050240060008914A0001000109350E2B2802004B1F5E5D899 0006C0000000005BF7454*Mar 2 02:47:17.569:*Mar 2 02:47:17.569: H225Lib::h225RecvData:Q.931 CONNECT received from socket [2]*Mar 2 02:47:17.569: H225Lib::h225RecvData:Q.931 Call State changed to [Active].*Mar 2 02:47:23.273:Hex representation of the received TPKT0300001A080280DC5A080280107E000A050500060008914A0001*Mar 2 02:47:23.273:*Mar 2 02:47:23.273: H225Lib::h225RecvData:Q.931 RELEASE COMPLETE received from socket [2]*Mar 2 02:47:23.273: H225Lib::h225RecvData:Q.931 Call State changed to [Null].*Mar 2 02:47:23.293:Hex representation of the RELEASE COMPLETE TPKT to send.0300001A080200DC5A080280107E000A050500060008914A0001*Mar 2 02:47:23.293:*Mar 2 02:47:23.293: H225Lib::h225TerminateRequest:Q.931 RELEASE COMPLETE sent from socket [2]. Call state changed to [Null].*Mar 2 02:47:23.293: H225Lib::h225TClose:TCP connection from socket [2] closedThe following output shows the same call being placed from gateway GW13 to gateway GW14 using the debug h225 asn1 command. The output is very long but you can track the following information:
•
•
•
•
•
•
•
•
•
3640GW.13# debug h225 asn1H.225 ASN1 Messages debugging is on3640GW.13#value RasMessage ::= admissionRequest :*Mar 2 02:48:18.445: {*Mar 2 02:48:18.445: requestSeqNum 03320,*Mar 2 02:48:18.445: callType pointToPoint :NULL,*Mar 2 02:48:18.445: callModel direct :NULL,*Mar 2 02:48:18.445: endpointIdentifier "60D6BA4C00000001",*Mar 2 02:48:18.445: destinationInfo*Mar 2 02:48:18.445: {*Mar 2 02:48:18.445: e164 :"14#14300"*Mar 2 02:48:18.445: },*Mar 2 02:48:18.449: srcInfo*Mar 2 02:48:18.449: {*Mar 2 02:48:18.449: e164 :"13#13300"*Mar 2 02:48:18.449: },*Mar 2 02:48:18.449: bandWidth 0640,*Mar 2 02:48:18.449: callReferenceValue 0224,*Mar 2 02:48:18.449: conferenceID '4B1F5E5D899000720000000005C067A4'H,*Mar 2 02:48:18.449: activeMC FALSE,*Mar 2 02:48:18.449: answerCall FALSE*Mar 2 02:48:18.449: }*Mar 2 02:48:18.449:25800CF7 00F00036 00300044 00360042 00410034 00430030 00300030 0030003000300030 00310103 80470476 33010380 46046633 40028000 E04B1F5E 5D89900072000000 0005C067 A40029000CF7 40028000 0109350E 06B80077value RasMessage ::= admissionConfirm :*Mar 2 02:48:18.469: {*Mar 2 02:48:18.469: requestSeqNum 03320,*Mar 2 02:48:18.469: bandWidth 0640,*Mar 2 02:48:18.469: callModel direct :NULL,*Mar 2 02:48:18.469: destCallSignalAddress ipAddress :*Mar 2 02:48:18.469: {*Mar 2 02:48:18.469: ip '0109350E'H,*Mar 2 02:48:18.469: port 01720*Mar 2 02:48:18.469: },*Mar 2 02:48:18.469: irrFrequency 0120*Mar 2 02:48:18.473: }*Mar 2 02:48:18.473:value H323-UserInformation ::=*Mar 2 02:48:18.481:{*Mar 2 02:48:18.481: h323-uu-pdu*Mar 2 02:48:18.481: {*Mar 2 02:48:18.481: h323-message-body setup :*Mar 2 02:48:18.481: {*Mar 2 02:48:18.481: protocolIdentifier { 0 0 8 2250 0 1 },*Mar 2 02:48:18.481: sourceInfo*Mar 2 02:48:18.481: {*Mar 2 02:48:18.481: terminal*Mar 2 02:48:18.481: {*Mar 2 02:48:18.481: },*Mar 2 02:48:18.481: mc FALSE,*Mar 2 02:48:18.481: undefinedNode FALSE*Mar 2 02:48:18.481: },*Mar 2 02:48:18.481: activeMC FALSE,*Mar 2 02:48:18.481: conferenceID '4B1F5E5D899000720000000005C067A4'H,*Mar 2 02:48:18.481: conferenceGoal create :NULL,*Mar 2 02:48:18.485: callType pointToPoint :NULL,*Mar 2 02:48:18.485: sourceCallSignalAddress ipAddress :*Mar 2 02:48:18.485: {*Mar 2 02:48:18.485: ip '00000000'H,*Mar 2 02:48:18.485: port 00*Mar 2 02:48:18.485: }*Mar 2 02:48:18.485: }*Mar 2 02:48:18.485: }*Mar 2 02:48:18.485:}*Mar 2 02:48:18.485:00800600 08914A00 0102004B 1F5E5D89 90007200 00000005 C067A400 0C07000000000000 00value H323-UserInformation ::=*Mar 2 02:48:18.525:{*Mar 2 02:48:18.525: h323-uu-pdu*Mar 2 02:48:18.525: {*Mar 2 02:48:18.525: h323-message-body alerting :*Mar 2 02:48:18.525: {*Mar 2 02:48:18.525: protocolIdentifier { 0 0 8 2250 0 1 },*Mar 2 02:48:18.525: destinationInfo*Mar 2 02:48:18.525: {*Mar 2 02:48:18.525: mc FALSE,*Mar 2 02:48:18.525: undefinedNode FALSE*Mar 2 02:48:18.525: },*Mar 2 02:48:18.525: h245Address ipAddress :*Mar 2 02:48:18.525: {*Mar 2 02:48:18.525: ip '0109350E'H,*Mar 2 02:48:18.525: port 011050*Mar 2 02:48:18.525: }*Mar 2 02:48:18.525: }*Mar 2 02:48:18.525: }*Mar 2 02:48:18.525:}*Mar 2 02:48:18.525:value H323-UserInformation ::=*Mar 2 02:48:22.753:{*Mar 2 02:48:22.753: h323-uu-pdu*Mar 2 02:48:22.753: {*Mar 2 02:48:22.753: h323-message-body connect :*Mar 2 02:48:22.753: {*Mar 2 02:48:22.753: protocolIdentifier { 0 0 8 2250 0 1 },*Mar 2 02:48:22.753: h245Address ipAddress :*Mar 2 02:48:22.753: {*Mar 2 02:48:22.753: ip '0109350E'H,*Mar 2 02:48:22.753: port 011050*Mar 2 02:48:22.753: },*Mar 2 02:48:22.753: destinationInfo*Mar 2 02:48:22.753: {*Mar 2 02:48:22.753: terminal*Mar 2 02:48:22.753: {*Mar 2 02:48:22.753: },*Mar 2 02:48:22.757: mc FALSE,*Mar 2 02:48:22.757: undefinedNode FALSE*Mar 2 02:48:22.757: },*Mar 2 02:48:22.757: conferenceID '4B1F5E5D899000720000000005C067A4'H*Mar 2 02:48:22.757: }*Mar 2 02:48:22.757: }*Mar 2 02:48:22.757:}*Mar 2 02:48:22.757:value H323-UserInformation ::=*Mar 2 02:48:27.109:{*Mar 2 02:48:27.109: h323-uu-pdu*Mar 2 02:48:27.109: {*Mar 2 02:48:27.109: h323-message-body releaseComplete :*Mar 2 02:48:27.109: {*Mar 2 02:48:27.109: protocolIdentifier { 0 0 8 2250 0 1 }*Mar 2 02:48:27.109: }*Mar 2 02:48:27.109: }*Mar 2 02:48:27.109:}*Mar 2 02:48:27.109:value RasMessage ::= disengageRequest :*Mar 2 02:48:27.117: {*Mar 2 02:48:27.117: requestSeqNum 03321,*Mar 2 02:48:27.117: endpointIdentifier "60D6BA4C00000001",*Mar 2 02:48:27.117: conferenceID '4B1F5E5D899000720000000005C067A4'H,*Mar 2 02:48:27.121: callReferenceValue 0224,*Mar 2 02:48:27.121: disengageReason normalDrop :NULL*Mar 2 02:48:27.121: }*Mar 2 02:48:27.121:3C0CF81E 00360030 00440036 00420041 00340043 00300030 00300030 0030003000300031 4B1F5E5D 89900072 00000000 05C067A4 00E020400CF8value RasMessage ::= disengageConfirm :*Mar 2 02:48:27.133: {*Mar 2 02:48:27.133: requestSeqNum 03321*Mar 2 02:48:27.133: }*Mar 2 02:48:27.133:value H323-UserInformation ::=*Mar 2 02:48:27.133:{*Mar 2 02:48:27.133: h323-uu-pdu*Mar 2 02:48:27.133: {*Mar 2 02:48:27.133: h323-message-body releaseComplete :*Mar 2 02:48:27.133: {*Mar 2 02:48:27.133: protocolIdentifier { 0 0 8 2250 0 1 }*Mar 2 02:48:27.133: }*Mar 2 02:48:27.133: }*Mar 2 02:48:27.133:}*Mar 2 02:48:27.133:05000600 08914A00 01.debug ras
Use the debug ras command to display the types and addressing of RAS messages sent and received. The debug output lists the message type using mnemonics defined in ITU-T specification H.225. Use the no form of this command to disable debug output.
debug ras
no debug rasSyntax Description
This command has no keywords or arguments.
Default
Disabled
Command Mode
Privileged EXEC
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(6)NA2.
Use the debug ras command to display the types and addressing of RAS messages sent and received. The debug output lists the message type using mnemonics defined in ITU-T specification H.225.
Sample Output
In the following output, gateway GW13.cisco.com sends a RAS registration request message (RRQ) to gatekeeper GK15.cisco.com at IP address 172.9.53.15. GW13.cisco.com then receives a registration confirmation (RCF) message from the gatekeeper. If there is no response, it could mean that the gatekeeper is offline or improperly addressed. If you receive a reject message (RRJ), it could mean that the gatekeeper is unable to handle another gateway or that the registration information is incorrect.
3640GW.13#debug ras*Mar 13 19:53:34.231: RASlib::ras_sendto:msg length 105 from172.9.53.13:8658 to 1.9.53.15:1719*Mar 13 19:53:34.231: RASLib::RASSendRRQ:RRQ (seq# 36939) sentto 172.9.53.15*Mar 13 19:53:34.247: RASLib::RASRecvData:successfully rcvdmessage of length 105 from 172.9.53.15:1719*Mar 13 19:53:34.251: RASLib::RASRecvData:RCF (seq# 36939) rcvdfrom [172.9.53.15:1719] on sock [0x6168356C
Guest
