|
|
The Cisco AS5300 voice service provider features include enhancements made to the functionality and configuration of both the gateway and the Voice over IP (VoIP) gatekeeper. The architecture of these features provides the Quality of Service (QoS), stability, and functionality necessary for carrier class, real-time IP communications services.
This document contains a basic description of the H.323 VoIP gateway in addition to features required to implement the applications to run VoIP in a service provider environment. The features address the service provider needs to offer security, billing, scaling, and reliability.
The Cisco AS5300 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 PBXs, making the process of placing calls over the IP network transparent to users.
The gateway capability allows the Cisco AS5300 to function as an H.323 endpoint. Therefore, the gateway provides admission control, address lookup and translation, and accounting services.
AAA---Authentication, Authorization, and Accounting. AAA is a suite of network security services which provides the primary framework through which access control can be set up on your Cisco router or access server.
ANI---Automatic number identification.
ARQ---Admission request.
CAS---Channel associated signaling.
CCAPI---Call control applications programming interface.
CLI---Command line interface.
CO---Central office.
CPE---Customer premises equipment. Terminating equipment, such as terminals, telephones, and modems, supplied by the telephone company, installed at the customer sites, and connected to the telephone company network.
CSM---Call switching module.
dial peer---An addressable call endpoint. In Voice over IP (V0IP), there are two types of dial peers: POTS and VoIP.
DNS---Domain name system used to 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).
DSP---Digital signal processor.
DTMF---Dual tone multi-frequency.
E.164---The international public telecommunications numbering plan. A standard set by ITU-T which addresses telephone numbers.
E&M---Ear and mouth RBS signaling.
endpoint---A H.323 terminal or gateway. An endpoint can call and be called. It generates and/or terminates the information stream.
gatekeeper---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.
The gatekeeper is a H.323 entity on the LAN that provides address translation and control access to the LAN for H.323 terminals and gateways. The gatekeeper may provide other services to the H.323 terminals and gateways, such as bandwidth management and locating gateways.
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.
A H.323 gateway is an 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.
H.323---An International Telecommunication Union (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 function performs registration, admissions, bandwidth changes, status and disengage procedures between the VoIP gateway and the gatekeeper.
HSRP---Hot Standby Routing Protocol. HSRP is a Cisco-proprietary protocol which provides a redundancy mechanism when more than one router is connected to the same segment/subnet of an Ethernet/FDDI/Token Ring network.
IVR---Integrated voice response. When someone dials in, it responds with a prompt to get a personal identification number (PIN), and so on.
LEC---Local exchange carrier.
LRQ---Location request.
MCU---Multipoint control unit
MF---Multi-frequency tones are made of six frequencies that provide 15 two frequency combinations for indication digits 0-9 and KP/ST signals.
multicast---A process of transmitting PDUs from one source to many destinations. The actual mechanism (that is, IP multicast, multi-unicast, and so forth) for this process might be different for LAN technologies.
multipoint-unicast---A process of transferring PDUs (Protocol Data Units) where an endpoint sends more than one copy of a media stream to different endpoints. This might be necessary in networks which do not support multicast.
node---A H.323 entity that uses RAS to communicate with the gatekeeper. For example, an endpoint such as a terminal, proxy, or gateway.
PDU---Protocol data units used by bridges to transfer connectivity information.
POTS---Plain old telephone service. Basic telephone service supplying standard single line telephones, telephone lines, and access to the PSTN.
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.
RAS---Registration, admission, and status protocol. This is the protocol that is used between endpoints and the gatekeeper to perform management functions.
RBS---Robbed bit signaling.
RRQ---Registration request.
SPI---Service provider interface.
TCL---Tool command language.
TDM---Time division multiplexing. Technique in which information from multiple channels can be allocated bandwidth on a single wire based on preassigned time slots. Bandwidth is allocated to each channel regardless of whether the station has data to transmit.
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 which generally refers to Cisco's standards based (for example, H.323) approach to IP voice traffic.
VTSP---Voice telephony service provider.
zone---A collection of all terminals (tx), gateways (GW), and Multipoint Control Units (MCU) managed by a single gatekeeper (GK). A zone includes at least one terminal, and can include gateways or multipoint control units (MCUs). A zone has only one gatekeeper. A zone may be independent of LAN topology and can be comprised of multiple LAN segments which are connected using routes or other devices.
This feature is supported on the following platforms:
Before you can configure your platform to serve as an H.323 VoIP gateway, you must first:
The SNMP MIBS are available on CCO. The CISCO-VOICE-DIAL-CONTROL-MIB supports the QoV and QoS of VoIP calls. Refer to the online support reference listed at the following location:
The functionality of the H.323 VoIP gateway is dependent on the interaction of the following features:
The Registration, Admission, and Status (RAS) signaling function 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:
Two new fields have been added to the dial-peer entry. The gateway relies on Cisco IOS command line interface commands, outside of gateway configuration mode, to configure handling of the AAA servers.
The following additions have been made to basic gateway functionality to implement RAS:
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 aboutconfiguring H.323 gatekeepers, refer to Cisco IOS Release 11.3(6) 2 Configuring H.323 VoIP Gatekeeper for Cisco Access Platforms.
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 E164 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 AAA Accounting section.
To configure a Cisco 3600 or Cisco 2600 series router to perform as an H.323 VoIP gateway using RAS, perform the following tasks:
To configure voice port parameters for an E&M voice port, use the following commands:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| configure terminal | Enter global configuration mode. | ||
| voice-port slot-number/subunit-number/port | Enter voice-port configuration mode to configure parameters for the specified voice port. The voice port is identified by its slot number, subunit number, and port number. | ||
| operation {2-wire | 4-wire} | Specify an E&M cabling scheme for this voice-port. | ||
| type {1 | 2 | 3 | 5} | Specify the E&M port type. |
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.
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&M Operation State is UP Administrative 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.
To configure the H.323 Gateway, you need to perform the tasks:
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:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| configure terminal | Enter global configuration mode. | ||
| dial-peer voice tag-number pots | Enter dial-peer configuration mode to configure parameters for the specified dial peer. The specific dial peer is identified by the tag number. | ||
| [tech-prefix#]destination-pattern [+]string[t] | Specify the telephone number (E.164 or otherwise) associated with this dial peer. Use the tech-prefix argument to define a technology prefix. By adding this technology prefix, you are enabling the system to identify an destination-patterns containing this prefix as RAS-initiated calls. | ||
| port slot-number/subunit-number/port | Specify the voice port through which incoming VoIP calls will be received. | ||
| exit | Exit the dial-peer configuration mode. |
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:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| configure terminal | Enter global configuration mode. | ||
| dial-peer voice tag-number voip | Enter dial-peer configuration mode to configure parameters for the specified dial peer. The specific dial peer is identified by the tag number. | ||
| destination-pattern [+]string[t] | Specify the telephone number (E.164 or otherwise) associated with this dial peer. | ||
| tech-prefix tech-prefix | Specify the technology prefix to be prepended to the destination pattern. | ||
| session-target ras | Specify that the RAS protocol is being used to determine the IP address of the session target---meaning that a gatekeeper will be consulted to translate the E164 address to an IP address. | ||
| exit | Exit the dial-peer configuration mode. |
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 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 1234 VoiceOverIpPeer1234 tag = 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-->
The next step in configuring an H.323 gateway is to enable VoIP gateway functionality. You do this by using the gateway command.
To enable gateway functionality, use the following commands:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| configure terminal | Enter global configuration mode. | ||
| gateway | Enable the VoIP Gateway. |
The next step in configuring an H.323 gateway is configure the gateway interface parameters. You do this by first defining 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, you configure the gateway to discover the gatekeeper either through multicasting or by directing it to a specific host. Finally, you 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:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| interface type slot/port | Enter interface configuration mode to configure parameters for the specified interface. | ||
| ip address ip-address subnet-mask | Specify the IP address for this interface. | ||
| h323-gateway voip interface | Designate this interface as being the H.323 gateway interface. | ||
| h323-gateway voip h323-id interface-id | Specify an H.323 name (ID) for the gateway associated with this interface. This ID is used by this gateway when this gateway communicates with the gatekeeper. Usually, this H.323 ID is the name given to the gateway with the gatekeeper domain name appended to the end. | ||
| h323-gateway voip id gatekeeper {ipaddr ip-address [port]| multicast} | Specify the name (ID) of the gatekeeper associated with this gateway and how the gateway finds the it. The gatekeeper ID configured here must exactly match the gatekeeper ID in the gatekeeper configuration. The gateway determines the location of the gateway in one of two ways: either by a defined IP address or through multicast. | ||
| h323-gateway voip tech-prefix prefix | Specify a technology prefix. A technology prefix is used to identify a type of service that this gateway is capable of providing. Note If a gateway is capable of handling multiple services, specify each service with a tech-prefix command. | ||
| exit | Exit interface configuration mode. | ||
| exit | Exit global configuration mode. |
3640GW.13#show gateway Gateway GW13.cisco.com is registered to Gatekeeper GK15.cisco.com
3640GK.15#show gatekeeper gw-type-prefix GATEWAY TYPE PREFIX TABLE ========================= Prefix:31#* Statically-configured gateways (not necessarily currently registered): 1.9.53.13:1720 Zone:GK15.cisco.com Registered gateways for this prefix: 1.9.53.13:1720 GW13 Prefix:23#* Zone:GK15.cisco.com Registered gateways for this prefix: 1.9.74.23:1720 GW23-c2611 Prefix:22#* Zone:GK15.cisco.com Registered gateways for this prefix: 1.9.74.22:1720 GW22-c2611 Prefix:13#* Zone:GK15.cisco.com Registered gateways for this prefix: 1.9.53.13:1720 GW13
3640GW.13#debug ras
*Mar 13 19:53:34.231: RASlib::ras_sendto:msg length 105 from
1.9.53.13:8658 to 1.9.53.15:1719
*Mar 13 19:53:34.231: RASLib::RASSendRRQ:RRQ (seq# 36939) sent
to 1.9.53.15
*Mar 13 19:53:34.247: RASLib::RASRecvData:successfully rcvd
message of length 105 from 1.9.53.15:1719
*Mar 13 19:53:34.251: RASLib::RASRecvData:RCF (seq# 36939) rcvd
from [1.9.53.15:1719] on sock [0x6168356C
3640GW.13#debug h225 asn1
H.225 ASN1 Messages debugging is on
3640GW.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 0880013C
05050100 40460000 01400D00 47005700 31003300 40006300 69007300 63006F00
2E006300 6F006D1A 0047004B 00310035 002E0063 00690073 0063006F 002E0063
006F006D 00B50000 12
10C09088 06000891 4A000100 01400D00 47005700 31003300 40006300 69007300
63006F00 2E006300 6F006D1A 0047004B 00310035 002E0063 00690073 0063006F
002E0063 006F006D 1E003600 30004400 37004500 37003300 43003000 30003000
30003000 30003000 46
value 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#
This section contains the following configuration examples:
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/0 operation 4-wire type 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 pots destination-pattern 13#13200 port 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 voip destination-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/0 ip address 172.9.53.13 255.255.255.0 h323-gateway voip interface h323-gateway voip id GK15.cisco.com ipaddr 172.9.53.15 1719 h323-gateway voip h323-id GW13@cisco.com h323-gateway voip tech-prefix 13# !
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/0 ip 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 !
Authentication, Authorization, and Accounting (AAA) features are required in the VoIP gateway. The standard Cisco AAA accounting functionality is enhanced to collect digits during the call processing process. Processes such as:
The AAA authentication feature permits RADIUS to be used to authenticate users (typically incoming calls) on the gateway. It is normally used with IVR to check the legitimacy of a prospective gateway user based on an account number (collected by IVR) or based on answer number identification (ANI).
New AAA commands are described in the Command Reference.
Authentication is based on RADIUS and is performed on the gateway (as opposed to the gatekeeper).
User account and PIN information is collected by the IVR application and passed to the AAA interface. The AAA interface then makes a RADIUS authentication request with the given information and returns to the IVR application with a status of success or failure.
RADIUS is an IETF protocol based on UDP. It functions by exchanging a set of attribute/value pairs between the client (for example, a VoIP gateway and a RADIUS server). Standard RADIUS server implementations include CiscoSecure, Cisco UCP, Livingston, and Merit.
An authenticated user is authorized. There is no authorization of specific user capabilities for the service provider voice applications.
Accounting uses a basic start-stop method and standard RADIUS attributes where possible. Attributes that cannot be mapped to standard RADIUS are packed into the Acct-Session-Id attribute field as '/' separated ASCII string.
Data items are collected for each call leg created on the gateway. A call leg is the internal representation of a connection to the gateway. Each call that is made through the gateway consists of two call legs: one incoming and one outgoing. The call leg information that is emitted by the gateway(s) can be correlated by their connection ID, which is the same for all call legs of a connection.
Standard RADIUS attributes supported are as follows:
Nonstandard RADIUS attributes packed into the Acct-Session-Id are as follows:
To take advantage of standard RADIUS implementations that do not support vendor-specific attributes, a new method is defined which embeds the unsupported information elements in the RADIUS Acct-Session-id. The Acct-Session-id field has a maximum length of 256 characters. It is defined to contain the RADIUS account session ID which is a unique identifier that links accounting records associated with the same login session for a user. The internal representation of this field is long; therefore, the value of this session ID can become very large as the number of sessions on a router increases. To support additional fields, we have defined the following string format for this field:
<session id >/<call leg setup time>/<gateway id>/<connection id>/<call origin>/
<call type>/<connect time>/<disconnect time>/<disconnect cause>/<remote ip address>
| Field | Description |
|---|---|
session id | The standard RADIUS account session ID. |
call leg setup time | The Q.931setup time for this connection in NTP format. |
gateway id | The name of the underlying gateway. Name string is in the form "gateway.domain_name." |
connection id | A unique global identifier used to correlate call legs that belong to the same end to end call. The field consists of 4 long words (128 bits). Each long word is displayed as a hexadecimal value and separated by a space character. |
call origin | Indicates origin of the call relative to the gateway. Possible values are originate and answer. |
call type | Indicates call leg type. Possible values are Telephony and VoIP. |
connect time | The Q.931 connect time for this call leg in NTP format. |
disconnect time | The Q.931 disconnect time for this call leg in NTP format. |
disconnect cause | Documented in Q.931 specification. Possible values are from 1 to 160. |
remote IP address | Address of the remote gateway port where the call is connected. |
Usage Guidelines
NTP time formats are displayed as: %H:%M:%S.%k %Z %tw %tn %td %Y where:
%H is hour (00 to 23)
%M is minutes (00 to 59)
%S is seconds (00 to 59)
%k is milliseconds (000 to 999)
%Z is timezone string
%tw is day of week (Saturday through Sunday)
%tn is month name (January through December)
%td is day of month (01 to 31)
%Y is year including century (for example,1998)
Note that because of the limited size of the session id string it is not possible to embed very many information elements in it. Therefore, this feature supports only a limited set of accounting information elements. For implementations that would like to take advantage of more information elements, Cisco's VSA implementation is recommended.
Client-Id = 172.29.248.123 NAS-Port-Type = 0 User-Name = "4004" Called-Station-Id = "+111" Calling-Station-Id = "+222" Acct-Status-Type = Start User-Service-Type = Login-User Acct-Session-Id = "4/23:21:14.078 UTC Sat Jul 18 1998/ak3620-1.cisco.com/859BF275 D7C80001 0 3AFF4/originate/VoIP///" Acct-Delay-Time = 0
Client-Id = 172.29.248.123 NAS-Port-Type = 0 User-Name = "4004" Called-Station-Id = "+111" Calling-Station-Id = "+222" Acct-Status-Type = Stop User-Service-Type = Login-User Acct-Session-Id = "4/23:21:14.078 UTC Sat Jul 18 1998/ak3620-1.cisco.com/859BF275 D7C80001 0 3AFF4/originate/VoIP/23:21:14.093 UTC Sat Jul 18 1998/23:21:23.084 UTC Sat Jul 18 1998/4" Acct-Input-Octets = 8340 Acct-Output-Octets = 8900 Acct-Input-Packets = 417 Acct-Output-Packets = 445 Acct-Session-Time = 9 Acct-Delay-Time = 0
Client-Id = 172.29.248.123 NAS-Port-Type = 0 User-Name = "4004" Called-Station-Id = "+111" Calling-Station-Id = "+222" Acct-Status-Type = 3 User-Service-Type = Login-User Acct-Session-Id = "4/21:54:17.052 UTC Mon Jul 20 1998/ak3620-1.cisco.com/BF1AC9CA 8DE60006 0 5ED24/originate/VoIP///" Acct-Delay-Time = 0
The syslog accounting option exports the information elements associated with each call leg through a system log message. The system log message can be captured by a syslog daemon that is present on the network. The syslog output consists of the following:
server_timestamp gateway_id message_number : message_label : list_of_AV_pairs
| Field | Description |
|---|---|
server timestamp | The timestamp created by the server when it receives the message to log. |
gateway id | The name of the gateway emitting the message. |
message number | The number assigned to the message by the gateway. |
message label | String used to identify the message category. |
list of AV pairs | String consisting of <attribute_name attribute_value> pairs separated by commas. |
%VOIPAAA-5-VOIP_CALL_HISTORY:CallLegType 2,ConnectionId 300094C0 60E0F3A0 60C894C0 60C90000, SetupTime 22:35:22.023UTC Tue Aug 11 1998, PeerAddress 999, PeerSubAddress , DisconnectCause 10 ,DisconnectText normal call clearing., ConnectTime 22:35:24.027 UTC Tue Aug 11 1998, DisconnectTime 22:35:29.028 UTC Tue Aug 11 1998, CallOrigin 1, ChargedUnits 0, InfoType 2,TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0
The authentication command line creates a method list named H.323 with RADIUS being its only member.
Also note that the accounting command line looks like a regular RADIUS accounting command line for connection accounting. Connection accounting has to be globally enabled using this command line. Start-stop or stop only methods may be used.
The Cisco IOS software AAA user interface can be configured to use the H.323 accounting method as follows.
| Step | Command | Purpose |
|---|---|---|
| 1 | 5300>enable Password: <password> 5300# | Enter enable mode. Enter the password. You have entered enable mode when the prompt changes to 5300#. |
| 2 | 5300#config term Enter configuration commands, one per line. End with CNTL/Z. 5300(config)# | Enter global configuration mode. You have entered global configuration mode when the prompt changes to |
| 3 | 5300(config)# aaa new-model | Initiates the AAA script. |
| 4 | 5300(config)# aaa authentication login h323 radius | Configures the router to use the H.323 method list for authentication purposes. |
| 5 | 5300(config)# aaa accounting connection h323 start-stop radius | Tells the system to use connection based accounting and the H.323 service. |
| 6 | 5300(config)# radius-server host 171.69.58.104 auth-port 165 acct-port 1646 | This command sets the server host IP address, and the ports for both the authentication service and the accounting service. |
| 7 | 5300(config)# radius-server key testing123 | Tests the connection accounting service. |
| 8 | 5300(config)# end | Ends the configuration session. |
aaa new-model aaa authentication local-override aaa authentication login default radius ! gw-accounting h323 ! radius-server host 10.90.1.1 auth-port 1645 acct-port 1646 radius-server key gte
This application provides basic Interactive Voice Response (IVR) capabilities necessary to collect caller Personal Identification Numbers (PINs), passwords, and destination phone numbers. IVR consists of simple voice prompting and digit collection to gather caller information for authenticating the user and identifying the destination.
Simple IVR allows the use of one of several interactive voice response scripts which are embedded in Cisco IOS software. The ability to modify the embedded scripts is not yet available. However, the audio files (for the prompts) can be modified for the user.
The user receives a voice-prompt instruction to enter a specific type of information (for example, a PIN number). After playing the voice prompt, the IVR feature starts the process of collecting the pre-determined number of touch tones (digit collection).
The IVR application then specifies a sequence of voice prompts and touch-tone collection instructions. IVR applications can be assigned to specific ports or invoked based on DNIS. An IP/PSTN gateway can have several different IVR applications to accommodate many different gateway services; and the IVR applications can be customized to present different interfaces to the caller. The functionality includes the ability to do the following:
The application field is used to indicate the application to which incoming calls should be delivered. This field is applicable to the dial-peer of the POTS-encapsulation type only. The application field, in the inbound dial-peer, is used to indicate the application that this incoming call should be delivered to. Examples of applications entered in this field are the default session application and the IVR application.
A brief description of the IVR application scripts follow:
Based on authentication of the ANI and DNIS for the call, the user is either denied service (with an appropriate voice message) or prompted for an account number and PIN if authentication fails. If authentication succeeds (or subsequent authentication with the supplied account/PIN succeeds), the user is prompted for the destination phone number, and the call is placed.
Fax hop on/off is a specialized IVR application to support the use of redialer boxes in fax applications. Redialers are small units which connect between a fax machine and a telephone line, intercept the phone number dialed by the fax machine, place an outgoing call to another phone number (in this case, that of the voice gateway), and then forward the destination number intercepted from the fax machine to the gateway when prompted. Optionally, an account number can be included to identify the caller's organization for authentication and billing purposes.
The purpose of this feature is to support the redirecting call feature of the VoIP gateway. The redirecting number is an optional field of the Q.931 Setup message.
When a local exchange carrier (LEC) switch detects an incoming call that is destined for a busy or nonanswering party, the switch formulates a Q.931 Setup message with the Redirecting Number field set to the originally called number, and sends it to the gateway. The called party number of the Setup message is set to one of the service access numbers dialed number identification service (DNIS) of the gateway.
If a redirect number is present on an incoming call, it is used in place of the called number (DNIS).
The dial peer configuration for ISDN redirect involves setting up two audio scripts:
To process incoming ISDN voice calls, incoming dial peers need to be configured. The dialed number identification service (DNIS) number of the incoming call is used to match the DNIS number field of the incoming dial peer. The direct-inward-dial flag of the dial peer determines whether a second dial tone is given to the caller to collect the target destination number. For this Cisco service provider feature, the DNIS is set to the access phone number of the Gateway, and the direct-inward-dial flag is set to TRUE.
The outgoing dial peer is selected based on the DNIS number of the incoming call. The outgoing dial peer indicates the session target of the outgoing call.
remote endpoint/gateway matches outgoing (telephony) dial-peer with destination pattern B
The Rotary Calling Pattern feature provides the ability, under certain circumstances, to route an incoming call arriving via a telephony interface back out via another telephony interface. This is primarily used to continue to provide service during network failures.
Call establishment via Rotary Call Pattern is supported via rotary group support of dial peers, where multiple dial peers may match a given destination phone number, and the dialing number will be selected in sequence. Support for Rotary Call Patterns of calls active at the time of a network failure will not be provided in the first release, which is 11.3(6)NA2.
In prior releases of VoIP, if you wanted the system to search through several destination numbers when a given number was dialed, you needed to configure those dial peers with the same destination pattern. Now with the Rotary Call Pattern feature, if you want the destinations to be tried in a certain order, you can assign order preference (via the preference command) to the dial peers.
For example, if you wish a call processing sequence to go to destination A first, then destination B second, and then to destination C, you would assign preference to the destinations in the following order (0 being the highest priority):
If there are several dial peers that match a particular destination pattern, the system attempts to place a call to the one with the highest preference. If the call cannot be completed because of a system outage (for example, the gatekeeper or gateway cannot be contacted), the Rotary call feature performs the following tasks:
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 11.3 command reference.
The aaa authentication login h323 radius command is used to define a method list called H.323 with RADIUS as a method. Enter the no form of this command to restore the default.
authentication login h323 radiusThis command has no key words or arguments.
[no] authentication login h323 radius.
Global configuration
This command first appeared in Cisco IOS Release 11.3(6)NA2.
This command line registers the H.323 method list (also referred to as h323 service) which has RADIUS as its only method in the router. The VoIP calls send all their authentication requests through the H.323 service. If this line does not exist in the router configuration VoIP authentication will not take place.
A significant difference in the usage of this command is that with Cisco IOS release 11.3(T) the name of the method list is flexible and can be changed by the user. However, when using method list for configuring AAA with the VoIP service provider software, the method list is a specific name that you should not change.
The way method lists work in Cisco IOS software is that a list is defined using the aaa authentication login h323 radius command, and is then applied to an interface. For voice authentication, we never apply this list to any interface. When enabled, using this command applies to all voice interfaces. The function of this command is activated through the IVR application.
This command is used to define the accounting method list "H.323" with RADIUS as a method and with either stop-only or start-stop accounting options.
aaa accounting connection h323 {stop-only | start-stop} radius
stop-only | start-stop | Start-only or stop-only accounting options. |
radius | RADIUS is used as the method. |
[no] aaa accounting connection h323.
aaa accounting connection h323 {none | start-stop | stop-only | wait-start} radius
Global configuration
This command first appeared in Cisco IOS Release 11.3(6)NA2.
The method list has to be called "h323" and is activated for all voice interfaces.
This command line tells the system to create a method list called H.323 which has start-stop radius as its method. The h323 method list is static and is applied by default to all voice interfaces if the gw-accounting h323 command is also activated.
The application command selects the session application for Interactive Voice Response. This command is entered during the configuration of the dial peers.
application name
name | Indicates the name of the IVR script application the call should be handed to |
None. The call will be handed to the predefined session application.
Dial peer configuration mode
This command first appeared in Cisco IOS Release 11.3(6)NA2.
application clid_authen_collect, CallID 90 got event IVR_EV-CALL_SETUP_IND : : ivr action: IVR_ACT_CALL_SETUP_ACK : : ivr action: IVR_ACT_CALL_PROCEEDING : : ivr action: IVR_ACT_CALL_CONNECT : ivr action: IVR_ACT_CALL_PROCEEDING : : ivr action: IVR_ACT_CALL_CONNECT
Use the audio-prompt load command to refresh the .au (audio) file in the memory. This is the file which contains the announcement prompt for the caller. The router will only load the .au file when the script initially plays that prompt, or on the router restart. If the .au file is changed, the user must run this EXEC command to reread the file. This will generate an error message if the file is not accessible, or if there is a format error.
audio-prompt load name
audio-prompt load | Initiates to load selected audio file from Flash memory into RAM. |
name | Indicates the location of the .au file to load. It can be loaded from memory, Flash memory, or an ftp server. Presently, with Cisco IOS Release 11.3(6)NA2, the <URL> pointer refers to the directory where Flash memory is stored. |
None.
Privileged EXEC
This command first appears in Cisco IOS Release 11.3(6)NA2.
To enable the H.323 VoIP gateway, use the gateway global configuration command. Use the no form of this command to unregister this gateway with the gatekeeper.
gatewayThis command has no keywords or arguments.
The gateway is unregistered.
Global configuration
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.
The gw-accounting command is used to enable or disable gateway specific accounting.
gw-accounting [h323 | syslog]
| Field | Description |
|---|---|
h323 | H.323 method uses RADIUS to output accounting CDRs. |
syslog | Syslog uses the system logging facility to output CDRs. |
[no] gw-accounting [h323 | syslog].
Global configuration
This command first appeared in Cisco IOS Release 11.3(6)NA2.
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 gatekeeper name.
h323-gateway voip h323-id interface-id
interface-id | H.323 name (ID) used by this gateway when this gateway communicates with its associated gatekeeper. Usually, this ID is the name of the gateway with the gatekeeper's domain name appended to the end: name@domain-name. |
No gateway identification is defined.
Interface configuration
This command first appeared in Cisco IOS Release 11.3(6)NA2.
The following example configures Ethernet interface 0.0 as the gateway interface. In this example, the gateway ID is GW13@cisco.com.
interface Ethernet0/0 ip address 172.9.53.13 255.255.255.0 h323-gateway voip interface h323-gateway voip id GK15.cisco.com ipaddr 172.9.53.15 1719 h323-gateway voip h323-id GW13@cisco.com h323-gateway voip tech-prefix 13#
h323-gateway voip id
h323-gateway voip interface
h323-gateway voip tech-prefix 13#
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}
gatekeeper-id | Indicates the H.323 identification of the gatekeeper. This value must exactly match the gatekeeper ID in the gatekeeper configuration. The recommended format is name.doman-name. |
ipaddr | Indicates that the gateway will use an IP address to locate the gatekeeper |
ip-address | Defines the IP address used to identify the gatekeeper. |
multicast | Indicates that the gateway will use multicast to locate the gatekeeper. |
No gatekeeper identification is defined.
Interface configuration
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.
The following example configures Ethernet interface 0.0 as the gateway interface. In this example, the gatekeeper ID is GW15.cisco.com and its IP address is 172.9.53.15 (using port 1719).
interface Ethernet0/0 ip address 172.9.53.13 255.255.255.0 h323-gateway voip interface h323-gateway voip id GK15.cisco.com ipaddr 172.9.53.15 1719 h323-gateway voip h323-id GW13@cisco.com h323-gateway voip tech-prefix 13#
h323-gateway voip h323-id
h323-gateway voip interface
h323-gateway voip tech-prefix 13#
To configure this interface as an H.323 interface, use the h323-gateway voip interface configuration command. Use the no form of this command to disable H.323 functionality for this interface.
h323-gateway voip interfaceThis command has no arguments or keywords.
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 11.3(6)NA2.
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/0 ip address 172.9.53.13 255.255.255.0 h323-gateway voip interface h323-gateway voip id GK15.cisco.com ipaddr 172.9.53.15 1719 h323-gateway voip h323-id GW13@cisco.com h323-gateway voip tech-prefix 13#
h323-gateway voip h323-id
h323-gateway voip id
h323-gateway voip tech-prefix 13#
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
prefix | Defines the numbers used as the technology prefix. Each technology prefix can contain up to 11 characters. Although not strictly necessary, a pound (#) symbol is frequently used as the last digit in a technology prefix. Valid characters 0 though 9, the pound (#) symbol, and the asterisk (*). |
Disabled
Interface configuration
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.
The following example configures Ethernet interface 0.0 as the gateway interface. In this example, the technology prefix is defined as 13#.
interface Ethernet0/0 ip address 172.9.53.13 255.255.255.0 h323-gateway voip interface h323-gateway voip id GK15.cisco.com ipaddr 172.9.53.15 1719 h323-gateway voip h323-id GW13@cisco.com h323-gateway voip tech-prefix 13#
h323-gateway voip id
h323-gateway voip interface
h323-gateway voip h323-id
The preference command is used to indicate the preference order for matching dial peers in a rotary group.
preference number
number | Enter an integer value [0..10]. The highest preference equals zero (0). |
No preference is set.
dial-peer configuration mode
The following examples show different dial peer configurations using the preference command:
Dialpeer destpat preference session-target 1 4085271048 0 (highest) jmmurphy-voip 2 408527 0 sj-voip 3 408527 1 (lower) backup-sj-voip 4 .......... 1 0:D (interface) 5 .......... 0 anywhere-voip
Dialpeer destpat preference 1 408527 0 2 4085271048 1 3 4085271 0 4 ..............4085271.........0
The session target command is used to identify the IP address of the destination gatekeeper. The field indicating if the RAS protocol is being used has been added. Enter the no form of this command to restore the default condition.
session target ras
ipv4:destination-address | IP address of the dial peer. |
dns:host-name | Indicates that the domain name server will be used to resolve the name of the IP address. Valid entries for this parameter are characters representing the name of the host device. (Optional) You can use one of the following three wildcards with this keyword when defining the session target for VoIP peers: · $s$.---Indicates that the source destination pattern will be used as part of the domain name. · $d$.---Indicates that the destination number will be used as part of the domain name. · $e$.---Indicates that the digits in the called number will be reversed, periods will be added in-between each digit of the called number, and that this string will be used as part of the domain name. · $u$.---Indicates that the unmatched portion of the destination pattern (such as a defined extension number) will be used as part of the domain name. |
loopback:rtp | Indicates that all voice data will be looped back to the originating source. This is applicable for VoIP peers. |
loopback:compressed | Indicates that all voice data will be looped back in compressed mode to the originating source. This is applicable for POTS peers. |
loopback:uncompressed | Indicates that all voice data will be looped-back in uncompressed mode to the originating source. This is applicable for POTS peers. |
ras | Indicates that the Registration, Admission and Status (RAS) signaling function protocol is being used---meaning that a gatekeeper will be consulted to translate the E.164 address to an IP address. |
The default for this command is enabled with no IP address or domain name defined.
Dial-peer configuration
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.
The following example configures a session target using DNS for a host, "voice_router," in the domain "cisco.com":
dial-peer voice 10 voip session target dns:voice_router.cisco.com
The 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 four-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 four-digit extension, to identify the dial peer. As in the previous example, the domain is "cisco.com."
dial-peer voice 10 voip destination-pattern 1310222.... session target dns:$u$.cisco.com
The 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 voip destination-pattern 13102221111 session target dns:$d$.cisco.com
The 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 voip destination-pattern 12345 session target dns:$e$.cisco.com
The following example configures a session target using RAS:
dial-peer voice 11 vofr destination-pattern 13102221111 session target ras
destination-pattern
session protocol
The show call application voice command defines the names of the audio files the script will play, the operation of the abort keys, what prompts are used and caller interaction.
show call application voice [name | summary]
| Field | Description |
|---|---|
name | The name of the desired IVR application. |
summary | Enter this field to display a one line summary. If the command is entered without summary, a complete detailed description is displayed of the application. |
Privileged EXEC (also called enable mode)
sblab115>show call application voice clid_authen_collect
Application clid_authen_collect has 10 states with 0 calls active
State start has 1 actions and 5 events
Do Action IVR_ACT_AUTHENTICATE. accountName=ani, pinName=dnis
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_SETUP_IND do action IVR_ACT_CALL_SETUP_ACK
and goto state start
If Event IVR_EV_AAA_SUCCESS goto state collect_dest
If Event IVR_EV_AAA_FAIL goto state get_account
State end has 1 actions and 3 events
Do Action IVR_ACT_END.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_DISCONNECT_DONE do action IVR_ACT_CALL_DESTROY
and do nothing
State get_account has 4 actions and 7 events
Do Action IVR_ACT_PLAY.
URL: flash:enter_account.au
allowInt=1, pContent=0x60E4C564
Do Action IVR_ACT_ABORT_KEY. abortKey=*
Do Action IVR_ACT_TERMINATION_KEY. terminationKey=#
Do Action IVR_ACT_COLLECT_PATTERN. Pattern account is .+
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_PAT_COL_SUCCESS goto state get_pin
patName=account
If Event IVR_EV_ABORT goto state get_account
If Event IVR_EV_PLAY_COMPLETE do nothing
If Event IVR_EV_TIMEOUT goto state get_account count=0
If Event IVR_EV_PAT_COL_FAIL goto state get_account
State get_pin has 4 actions and 7 events
Do Action IVR_ACT_PLAY.
URL: flash:enter_pin.au
allowInt=1, pContent=0x0
Do Action IVR_ACT_ABORT_KEY. abortKey=*
Do Action IVR_ACT_TERMINATION_KEY. terminationKey=#
Do Action IVR_ACT_COLLECT_PATTERN. Pattern pin is .+
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_PAT_COL_SUCCESS goto state authenticate
patName=pin
If Event IVR_EV_PLAY_COMPLETE do nothing
If Event IVR_EV_ABORT goto state get_account
If Event IVR_EV_TIMEOUT goto state get_pin count=0
If Event IVR_EV_PAT_COL_FAIL goto state get_pin
State authenticate has 1 actions and 5 events
Do Action IVR_ACT_AUTHENTICATE. accountName=account, pinName=pin
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_AAA_SUCCESS goto state collect_dest
If Event IVR_EV_TIMEOUT do nothing count=0
If Event IVR_EV_AAA_FAIL goto state authenticate_fail
State collect_dest has 4 actions and 8 events
Do Action IVR_ACT_PLAY.
URL: flash:enter_destination.au
allowInt=1, pContent=0x0
Do Action IVR_ACT_ABORT_KEY. abortKey=*
Do Action IVR_ACT_TERMINATION_KEY. terminationKey=#
Do Action IVR_ACT_COLLECT_DIALPLAN.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_PLAY_COMPLETE do nothing
If Event IVR_EV_ABORT goto state collect_dest
If Event IVR_EV_TIMEOUT goto state collect_dest count=0
If Event IVR_EV_DIAL_COL_SUCCESS goto state place_call
If Event IVR_EV_DIAL_COL_FAIL goto state collect_dest
If Event IVR_EV_TIMEOUT goto state collect_dest count=0
State place_call has 1 actions and 4 events
Do Action IVR_ACT_PLACE_CALL.
destination= called=
calling= account=
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_UP goto state active
If Event IVR_EV_CALL_FAIL goto state place_fail
State active has 0 actions and 2 events
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
State authenticate_fail has 1 actions and 2 events
Do Action IVR_ACT_PLAY.
URL: flash:auth_failed.au
allowInt=0, pContent=0x0
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
State place_fail has 1 actions and 2 events
Do Action IVR_ACT_PLAY_FAILURE_TONE.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
sblab115>show call application voice clid_authen_collect
Application clid_authen_collect has 10 states with 0 calls active
State start has 1 actions and 5 events
Do Action IVR_ACT_AUTHENTICATE. accountName=ani, pinName=dnis
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_SETUP_IND do action IVR_ACT_CALL_SETUP_ACK
and goto state start
If Event IVR_EV_AAA_SUCCESS goto state collect_dest
If Event IVR_EV_AAA_FAIL goto state get_account
State end has 1 actions and 3 events
Do Action IVR_ACT_END.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_DISCONNECT_DONE do action IVR_ACT_CALL_DESTROY
and do nothing
State get_account has 4 actions and 7 events
Do Action IVR_ACT_PLAY.
URL: flash:enter_account.au
allowInt=1, pContent=0x60E4C564
Do Action IVR_ACT_ABORT_KEY. abortKey=*
Do Action IVR_ACT_TERMINATION_KEY. terminationKey=#
Do Action IVR_ACT_COLLECT_PATTERN. Pattern account is .+
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_PAT_COL_SUCCESS goto state get_pin
patName=account
If Event IVR_EV_ABORT goto state get_account
If Event IVR_EV_PLAY_COMPLETE do nothing
If Event IVR_EV_TIMEOUT goto state get_account count=0
If Event IVR_EV_PAT_COL_FAIL goto state get_account
State get_pin has 4 actions and 7 events
Do Action IVR_ACT_PLAY.
URL: flash:enter_pin.au
allowInt=1, pContent=0x0
Do Action IVR_ACT_ABORT_KEY. abortKey=*
Do Action IVR_ACT_TERMINATION_KEY. terminationKey=#
Do Action IVR_ACT_COLLECT_PATTERN. Pattern pin is .+
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_PAT_COL_SUCCESS goto state authenticate
patName=pin
If Event IVR_EV_PLAY_COMPLETE do nothing
If Event IVR_EV_ABORT goto state get_account
If Event IVR_EV_TIMEOUT goto state get_pin count=0
If Event IVR_EV_PAT_COL_FAIL goto state get_pin
State authenticate has 1 actions and 5 events
Do Action IVR_ACT_AUTHENTICATE. accountName=account, pinName=pin
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_AAA_SUCCESS goto state collect_dest
If Event IVR_EV_TIMEOUT do nothing count=0
If Event IVR_EV_AAA_FAIL goto state authenticate_fail
State collect_dest has 4 actions and 8 events
Do Action IVR_ACT_PLAY.
URL: flash:enter_destination.au
allowInt=1, pContent=0x0
Do Action IVR_ACT_ABORT_KEY. abortKey=*
Do Action IVR_ACT_TERMINATION_KEY. terminationKey=#
Do Action IVR_ACT_COLLECT_DIALPLAN.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_PLAY_COMPLETE do nothing
If Event IVR_EV_ABORT goto state collect_dest
If Event IVR_EV_TIMEOUT goto state collect_dest count=0
If Event IVR_EV_DIAL_COL_SUCCESS goto state place_call
If Event IVR_EV_DIAL_COL_FAIL goto state collect_dest
If Event IVR_EV_TIMEOUT goto state collect_dest count=0
State place_call has 1 actions and 4 events
Do Action IVR_ACT_PLACE_CALL.
destination= called=
calling= account=
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_UP goto state active
If Event IVR_EV_CALL_FAIL goto state place_fail
State active has 0 actions and 2 events
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
State authenticate_fail has 1 actions and 2 events
Do Action IVR_ACT_PLAY.
URL: flash:auth_failed.au
allowInt=0, pContent=0x0
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
State place_fail has 1 actions and 2 events
Do Action IVR_ACT_PLAY_FAILURE_TONE.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
The show gateway command is used to display the current gateway status.
show gatewayThis command has no keywords or arguments.
no show gateway
Privileged EXEC (also called enable mode)
gte-as5300-2#show gateway Gateway voip2@vm1lab is registered to Gatekeeper gk1.vm1lab
The tech-prefix command is used to specify a particular technology prefix 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 disabled the defined technology prefix for this dial peer.
tech-prefix number
number | Defines the numbers used as the technology prefix. Each technology prefix can contain up to 11 characters. Although not strictly necessary, a pound (#) symbol is frequently used as the last digit in a technology prefix. Valid characters 0 though 9, the pound (#) symbol, and the asterisk (*). |
No technology prefix is defined.
Dial-peer configuration
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.
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 voip destination-pattern 14... tech-prefix 14#
gw-type-prefix
show gatekeeper gw-type-prefix
This section describes the following debug commands:
The debug cch323 h225 command provides the trace of the state transition of the H.225 state machine based on the processed events. The no form of this command disables debugging output.
debug cch323 h225This command has no keywords or arguments.
Disabled
Privileged EXEC
The state definitions of the different states of the H.225 state machine are as follows:
The event definitions of the different events of the H.225 state machine are as follows:
20:59:17:Set new event H225_EVENT_SETUP 20:59:17:H225 FSM:received event H225_EVENT_SETUP while at state H225_IDLE 20:59:17:Changing from H225_IDLE state to H225_SETUP state 20:59:17:cch323_h225_receiver:received msg of type SETUPCFM_CHOSEN 20:59:17:H225 FSM:received event H225_EVENT_SETUP_CFM_IND while at state H225_SETUP 20:59:17:Changing from H225_SETUP state to H225_ACTIVE state 20:59:17:Set new event H225_EVENT_H245_SUCCESS 20:59:17:H225 FSM:received event H225_EVENT_H245_SUCCESS while at state H225_ACTIVE 20:59:20:Set new event H225_EVENT_RELEASE 20:59:20:H225 FSM:received event H225_EVENT_RELEASE while at state H225_ACTIVE 20:59:20:Changing from H225_ACTIVE state to H225_WAIT_FOR_DRQ state 20:59:20:Set new event H225_EVENT_RAS_SUCCESS 20:59:20:H225 FSM:received event H225_EVENT_RAS_SUCCESS while at state H225_WAIT_FOR_DRQ 20:59:20:Changing from H225_WAIT_FOR_DRQ state to H225_IDLE state
The debug cch323 h245 command provides the trace of the state transition of the H.245 state machine based on the processed events. The no form of this command disables debugging output.
debug cch323 h245This command has no keywords or arguments.
Disabled
Privileged EXEC
This command first appeared in Cisco IOS Release 11.3(6)NA2.
The H.245 state machines include the following three state machines:
The definitions are listed:
20:58:23:Changing to new event H245_EVENT_MSD 20:58:23:H245 MS FSM:received event H245_EVENT_MSD while at state H245_MS_NONE 20:58:23:changing from H245_MS_NONE state to H245_MS_WAIT state 20:58:23:Changing to new event H245_EVENT_CAP 20:58:23:H245 CAP FSM:received event H245_EVENT_CAP while at state H245_CAP_NONE 20:58:23:changing from H245_CAP_NONE state to H245_CAP_WAIT state 20:58:23:cch323_h245_receiver:received msg of type M_H245_MS_DETERMINE_INDICATION 20:58:23:Changing to new event H245_EVENT_MS_IND 20:58:23:H245 MS FSM:received event H245_EVENT_MS_IND while at state H245_MS_WAIT 20:58:23:cch323_h245_receiver:received msg of type M_H245_CAP_TRANSFER_INDICATION 20:58:23:Changing to new event H245_EVENT_CAP_IND 20:58:23:H245 CAP FSM:received event H245_EVENT_CAP_IND while at state H245_CAP_WAIT 20:58:23:cch323_h245_receiver:received msg of type M_H245_MS_DETERMINE_CONFIRM 20:58:23:Changing to new event H245_EVENT_MS_CFM 20:58:23:H245 MS FSM:received event H245_EVENT_MS_CFM while at state H245_MS_WAIT 20:58:23:changing from H245_MS_WAIT state to H245_MS_DONE state 0:58:23:cch323_h245_receiver:received msg of type M_H245_CAP_TRANSFER_CONFIRM 20:58:23:Changing to new event H245_EVENT_CAP_CFM 20:58:23:H245 CAP FSM:received event H245_EVENT_CAP_CFM while at state H245_CAP_WAIT 20:58:23:changing from H245_CAP_WAIT state to H245_CAP_DONE state 20:58:23:Changing to new event H245_EVENT_OLC 20:58:23:H245 OLC FSM:received event H245_EVENT_OLC while at state H245_OLC_NONE 20:58:23:changing from H245_OLC_NONE state to H245_OLC_WAIT state 20:58:23:cch323_h245_receiver:received msg of type M_H245_UCHAN_ESTABLISH_INDICATION 20:58:23:Changing to new event H245_EVENT_OLC_IND 20:58:23:H245 OLC FSM:received event H245_EVENT_OLC_IND while at state H245_OLC_WAIT 20:58:23:cch323_h245_receiver:received msg of type M_H245_UCHAN_ESTAB_ACK 20:58:23:Changing to new event H245_EVENT_OLC_CFM 20:58:23:H245 OLC FSM:received event H245_EVENT_OLC_CFM while at state H245_OLC_WAIT 20:58:23:changing from H245_OLC_WAIT state to H245_OLC_DONE state
The debug cch323 ras command provides the trace of the state transition of the RAS state machine based on the processed events.The no form of this command disables debugging output.
debug cch323 rasThis command has no keywords or arguments.
Disabled
Privileged EXEC
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.
The state definitions of the different states of the RAS state machine follow:
These are the event definitions of the different states of the RAS state machine:
20:58:49:Changing to new event CCH323_RAS_EVENT_SEND_RRQ cch323_run_ras_sm:received event CCH323_RAS_EVENT_SEND_RRQ while at CCH323_RAS_STATE_IDLE state cch323_run_ras_sm:changing to CCH323_RAS_STATE_RRQ state cch323_ras_receiver:received msg of type RCF_CHOSEN cch323_run_ras_sm:received event CCH323_RAS_EVENT_RCF while at CCH323_RAS_STATE_RRQ state cch323_run_ras_sm:changing to CCH323_RAS_STATE_IDLE state 20:58:59:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_NEWCALL while at CCH323_RAS_STATE_IDLE state 20:58:59:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_ARQ cch323_ras_receiver:received msg of type ACF_CHOSEN 20:58:59:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_ACF while at CCH323_RAS_STATE_ARQ state 20:58:59:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_ACTIVE 20:59:02:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_CALLDISC while at CCH323_RAS_STATE_ACTIVE state 20:59:02:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_DRQ cch323_ras_receiver:received msg of type DCF_CHOSEN 20:59:02:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_DCF while at CCH323_RAS_STATE_DRQ state 20:59:02:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_IDLE 20:59:04:cch323_percall_ras_sm:received event CCH323_RAS_EVENT_IRR while at CCH323_RAS_STATE_ACTIVE state 20:59:04:cch323_percall_ras_sm:changing to new state CCH323_RAS_STATE_ACTIVE
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}
asn1 | Indicates that only the ASN.1 contents of any H.225 message sent or received will be displayed. |
events | Indicates that key Q.931 events that occur when placing a H.323 call from one gateway to another will be displayed. |
Disabled
Privileged EXEC
This command first appeared in Cisco IOS Release 11.3(6)NA2
Both versions of the debug H225 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.
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.
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 events H.225 Event Messages debugging is on 3640GW.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.0300004D080200DC05040380C0A36C0991313323313333303070099131342331343330307E0026050080060008914A000102004B1F5E5D8990006C0000000005BF7454000C0700000000000000 *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 TPKT03000034080280DC07040380C0A37E0023050240060008914A0001000109350E2B2802004B1F5E5D8990006C0000000005BF7454 *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] closed
The 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 asn1
H.225 ASN1 Messages debugging is on
3640GW.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 00300030
00300030 00310103 80470476 33010380 46046633 40028000 E04B1F5E 5D899000
72000000 0005C067 A400
29000CF7 40028000 0109350E 06B80077
value 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 0C070000
00000000 00
value 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 00300030
00300031 4B1F5E5D 89900072 00000000 05C067A4 00E020
400CF8
value 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
.
Use the debug voip ccapi 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 rasThis command has no keywords or arguments.
Disabled
Privileged EXEC
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.
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 from
172.9.53.13:8658 to 1.9.53.15:1719
*Mar 13 19:53:34.231: RASLib::RASSendRRQ:RRQ (seq# 36939) sent
to 172.9.53.15
*Mar 13 19:53:34.247: RASLib::RASRecvData:successfully rcvd
message of length 105 from 172.9.53.15:1719
*Mar 13 19:53:34.251: RASLib::RASRecvData:RCF (seq# 36939) rcvd
from [172.9.53.15:1719] on sock [0x6168356C
The debug voip aaa command is used to enable or disable debugging messages for gateway aaa to be output to the system console.
debug voip aaaThis command has no keywords or arguments.
global exec
Disabled
Privileged EXEC
The debug voip ccapi command is used for debugging the call control API.
debug voip ccapiThis command has no keywords or arguments.
Disabled
Privileged EXEC
This command first appeared in Cisco IOS Release 11.3(6)NA2.
sblab160#show debug
voip:
voip ccAPI function enter/exit debugging is on
Oct 9 17:39:20.267:cc_api_call_setup_ind (vdbPtr=0x60ED5134,
callInfo={called=3001, calling=4004, fdest=0 peer_tag=1},
callID=0x6104B374)
Oct 9 17:39:20.275:cc_process_call_setup_ind (event=0x60D45CF0) handed
call to app "sess"
Oct 9 17:39:20.279:ccAppInitialize (name=App for callId 3
, appHandle=0x6103DD44)
Oct 9 17:39:20.279:ccCallSetContext (callID=0x3, context=0x6103DD3C)
Oct 9 17:39:20.279:ccCallSetupAck (callID=0x3)
Oct 9 17:39:20.279:ccGenerateTone (callID=0x3 tone=8)
Oct 9 17:39:20.279:ccCallApp (callID=0x3)
Oct 9 17:39:20.279:ccCallSetContext (callID=0x3, context=0x60DC4594)
00:11:31:%RADIUS-6-SERVERALIVE:Radius server 171.69.184.73 is
responding
again (previously dead).
Oct 9 17:39:22.808:cc_api_call_digit (vdbPtr=0x60ED5134, callID=0x3,
digit=1, mode=0)
Oct 9 17:39:23.069:cc_api_call_digit (vdbPtr=0x60ED5134, callID=0x3,
digit=1, mode=0)
Oct 9 17:39:23.399:cc_api_call_digit (vdbPtr=0x60ED5134, callID=0x3,
digit=5, mode=0)
Oct 9 17:39:23.652:cc_api_call_digit (vdbPtr=0x60ED5134, callID=0x3,
digit=1, mode=0)
Oct 9 17:39:24.041:cc_api_call_digit (vdbPtr=0x60ED5134, callID=0x3,
digit=0, mode=0)
Oct 9 17:39:24.294:cc_api_call_digit (vdbPtr=0x60ED5134, callID=0x3,
digit=0, mode=0)
Oct 9 17:39:24.294:ccCallAppReturn (callID=0x3)
Oct 9 17:39:24.294:ccCallApp (callID=0x3)
Oct 9 17:39:24.294:ccCallSetContext (callID=0x3, context=0x6105DC90)
Oct 9 17:39:24.294:ccCallProceeding (callID=0x3, prog_ind=0x0)
Oct 9 17:39:24.294:ccCallSetupRequest (peer=0x60FE4068, dest=,
params=0x6105DB70 mode=0, *callID=0x60D50978)
Oct 9 17:39:24.294:callingNumber=4004, calledNumber=115100,
redirectNumber=
Oct 9 17:39:24.294:accountNumber=, finalDestFlag=0,
guid=3c85.5d28.2861.0004.0000.0000.000a.8dfc
Oct 9 17:39:24.294:peer_tag=115
Oct 9 17:39:24.294:ccIFCallSetupRequest:(vdbPtr=0x60D4A268, dest=,
callParams={called=115100, calling=4004, fdest=0, voice_peer_tag=115},
mode=0x0)
Oct 9 17:39:24.294:ccCallSetContext (callID=0x4, context=0x6105DD78)
Oct 9 17:39:26.350:cc_api_call_alert(vdbPtr=0x60D4A268, callID=0x4,
prog_ind=0x8, sig_ind=0x0)
Oct 9 17:39:26.350:ccCallAlert (callID=0x3, prog_ind=0x8, sig_ind=0x0)
Oct 9 17:39:26.350:ccConferenceCreate (confID=0x60D509C8, callID1=0x3,
callID2=0x4, tag=0x0)
Oct 9 17:39:26.350:cc_api_bridge_done (confID=0x1, srcIF=0x60D4A268,
srcCallID=0x4, dstCallID=0x3, disposition=0, tag=0x0)
Oct 9 17:39:26.350:cc_api_bridge_done (confID=0x1, srcIF=0x60ED5134,
srcCallID=0x3, dstCallID=0x4, disposition=0, tag=0x0)
Oct 9 17:39:26.350:cc_api_caps_ind (dstVdbPtr=0x60D4A268,
dstCallId=0x4,srcCallId=0x3, caps={codec=0x7, fax_rate=0x7F, vad=0x3})
Oct 9 17:39:26.350:cc_api_caps_ind (dstVdbPtr=0x60ED5134,
dstCallId=0x3,srcCallId=0x4, caps={codec=0x4, fax_rate=0x2, vad=0x2})
Oct 9 17:39:26.350:cc_api_caps_ack (dstVdbPtr=0x60ED5134,
dstCallId=0x3,srcCallId=0x4, caps={codec=0x4, fax_rate=0x2, vad=0x2})
Oct 9 17:39:26.350:cc_api_caps_ack (dstVdbPtr=0x60D4A268,
dstCallId=0x4,srcCallId=0x3, caps={codec=0x4, fax_rate=0x2, vad=0x2})
Oct 9 17:39:26.430:cc_api_call_connected(vdbPtr=0x60D4A268,
callID=0x4)
Oct 9 17:39:26.430:ccCallConnect (callID=0x3)
Oct 9 17:39:26.430:ccCallAppReturn (callID=0x3)
Oct 9 17:39:26.430:ccCallSetContext (callID=0x4, context=0x6103DD3C)
Oct 9 17:39:30.683:cc_api_call_disconnected(vdbPtr=0x60D4A268,
callID=0x4, cause=0x10)
Oct 9 17:39:30.683:ccCallDisconnect (callID=0x4, cause=0x10 tag=0x0)
Oct 9 17:39:30.683:ccConferenceDestroy (confID=0x1, tag=0x0)
Oct 9 17:39:30.687:cc_api_bridge_done (confID=0x1, srcIF=0x60D4A268,
srcCallID=0x4, dstCallID=0x3, disposition=0 tag=0x0)
Oct 9 17:39:30.727:cc_api_call_disconnect_done(vdbPtr=0x60D4A268,
callID=0x4, disp=0, tag=0x0)
Oct 9 17:39:30.727:cc_api_bridge_done (confID=0x1, srcIF=0x60ED5134,
srcCallID=0x3, dstCallID=0x4, disposition=0 tag=0x0)
Oct 9 17:39:30.727:ccCallDisconnect (callID=0x3, cause=0x10 tag=0x0)
Oct 9 17:39:30.779:cc_api_call_disconnect_done(vdbPtr=0x60ED5134,
callID=0x3, disp=0, tag=0x0)
00:11:42:%LINK-3-UPDOWN:Interface Serial0:18, changed state to down
The debug voip ivr command is used to debug the IVR application. IVR debug messages will be displayed when a call is being actively handled by the IVR scripts. Error output should only occur if something is not working or an error condition has been raised. States output supplies information about the current status of the IVR script and the different events which are occurring in that state.
debug voip ivr [states | error | all]This command has no keywords or arguments.
Disabled
Privileged EXEC
This command first appeared in Cisco IOS Release 11.3(6)NA2.
There are two types of messages:
Posted: Mon Dec 6 16:38:37 PST 1999
Copyright 1989-1999©Cisco Systems Inc.