-
Cisco IOS Voice, Video, and Fax Command Reference, Release 12.2
-
Read me
-
About Cisco IOS Software Documentation
-
Using Cisco IOS Software
-
Cisco IOS Voice, Video, and Fax Commands: A through C
-
Cisco IOS Voice, Video, and Fax Commands: D through F
-
Cisco IOS Voice, Video, and Fax Commands: G through P
-
Cisco IOS Voice, Video, and Fax Commands: R through Sh
-
Cisco IOS Voice, Video, and Fax Commands: Si through Z
-
Index
-
Feedback
Table Of Contents
Cisco IOS Voice, Video, and Fax Commands:
R Through Shrtsp client session history duration
rtsp client session history records
session protocol (Voice over Frame Relay)
sgcp quarantine-buffer disable
show backhaul-session-manager group
show backhaul-session-manager session
show backhaul-session-manager set
show call history video record
show call history voice record
show call resource voice stats
show call resource voice threshold
show gatekeeper gw-type-prefix
show voice trunk-conditioning signaling
show voice trunk-conditioning supervisory
Cisco IOS Voice, Video, and Fax Commands:
R Through Sh
This chapter presents the commands to configure and maintain Cisco IOS voice, video, and fax applications. The commands are presented in alphabetical order beginning with R. Some commands required for configuring voice, video, and fax may be found in other Cisco IOS command references. Use the command reference master index or search online to find these commands.
For detailed information on how to configure these applications and features, refer to the Cisco IOS Voice, Video, and Fax Configuration Guide.
register e164
To configure a gateway to register or deregister (remove the registration for) a fully qualified plain old telephone service (POTS) dial-peer E.164 address with a gatekeeper, use the register e164 command in dial-peer configuration mode. To deregister an E.164 address, use the no form of this command.
register e164
no register e164
Syntax Description
This command has no keywords or arguments.
Defaults
No E.164 addresses are registered until you enter this command.
Command Modes
Dial-peer configuration
Command History
12.0(5)T
This command was introduced on the Cisco AS5300 universal access server.
Usage Guidelines
Use this command to register the E.164 address of an analog telephone line attached to a Foreign Exchange Station (FXS) port on a router. The gateway automatically registers fully qualified E164 addresses. Use the no register e164 command to deregister an address. Use the register e164 command to register a deregistered address.
Before you automatically or manually register an E.164 address with a gatekeeper, you must create a dial peer (using the dial-peer command), assign an FXS port to the peer (using the port command), and assign an E.164 address (using the destination-pattern command). The E.164 address must be a fully qualified address. For example, +5551212, 5551212, and 4085551212 are fully qualified addresses; 408555.... is not a fully qualified address. E.164 addresses are registered only for active interfaces—those that are not shut down. If an FXS port or its interface is shut down, the corresponding E.164 address is deregistered.
Tips
You can use the show gateway command to find out if the gateway is connected to a gatekeeper and if a fully qualified E.164 address is assigned to the gateway. Use the zone-prefix command at the gatekeeper to define prefix patterns, such as 408555...., that apply to one or more gateways.
Examples
The following command sequence places the gateway in dial-peer configuration mode, assigns an E.164 address to the interface, and registers that address with the gatekeeper:
dial-peer voice 111 potsport 1/0/0destination-pattern 5551212register e164The following commands deregister an address with the gatekeeper:
dial-peer voice 111 potsno register e164The following example shows that you must have a connection to a gatekeeper and define a unique E.164 address before you can register an address:
dial-peer voice 222 potsport 1/0/0destination 919555....register e164ERROR-register-e164:Dial-peer destination-pattern is not a full E.164 numberno gatewaydial-peer voice 111 potsregister e164ERROR-register-e164:No gatekeeperRelated Commands
registered-caller ring
To configure the Nariwake service registered caller ring cadence, use the registered-caller ring command in dial-peer configuration mode.
registered-caller ring cadence
Syntax Description
Defaults
The default Nariwake service registered caller ring cadence is ring 1.
Command Modes
Dial-peer configuration
Command History
12.1.(2)XF
The command registered-caller ring was introduced on the Cisco 800 series routers.
Usage Guidelines
If your ISDN line is provisioned for the I Number or dial-in services, you must also configure a dial peer by using the destination-pattern not-provided command. Either port 1 or port 2 can be configured under this dial peer. The router then forwards the incoming call to voice port 1. (See the "Examples" section below.
If more than one dial peer is configured with the destination-pattern not-provided command, the router uses the first configured dial peer for the incoming calls. To display the Nariwake ring cadence setting, use the show run command.
Examples
The following example sets the ring cadence for registered callers to 2.
pots country jpdial-peer voice 1 potsregistered-caller ring 2req-qos
To specify the desired quality of service to be used in reaching a specified dial peer, use the req-qos command in dial-peer configuration mode. To restore the default value for this command, use the no form of this command.
req-qos {best-effort | controlled-load | guaranteed-delay}
no req-qos
Syntax Description
Defaults
best-effort
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
This command is applicable only to VoIP dial peers.
Use the req-qos command to request a specific quality of service to be used in reaching a dial peer. Like acc-qos, when you issue this command, the Cisco IOS software reserves a certain amount of bandwidth so that the selected quality of service can be provided. Cisco IOS software uses Resource Reservation Protocol (RSVP) to request quality of service guarantees from the network.
Examples
The following example configures guaranteed-delay as the desired (requested) quality of service to a dial peer:
dial-peer voice 10 voipreq-qos guaranteed-delayRelated Commands
acc-qos
Defines the acceptable QoS for any inbound and outbound call on a VoIP dial peer.
reset
To reset a set of digital signal processors (DSPs), use the reset command in global configuration mode.
reset number
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
12.0(5)XE
This command was introduced on the Cisco 7200 series routers.
12.0(7)T
This command was integrated into the Cisco IOS Release 12.0(7)T.
Examples
The following example displays the reset command configuration for DSP 1:
reset 101:24:54:%DSPRM-5-UPDOWN: DSP 1 in slot 1, changed state to upresource threshold
To configure a gateway to report H.323 resource availability to the its gatekeeper, use the resource threshold command in gateway configuration mode. To disable gateway resource-level reporting, use the no form of this command.
resource threshold [all] [high percentage-value] [low percentage-value]
no resource threshold
Syntax Description
Defaults
Reports low resources when 90 percent of resources are in use, and reports resource availability when resource use drops below 90 percent.
Command Modes
Gateway configuration
Command History
12.0(5)T
This command was introduced on the Cisco AS5300 universal access server.
Usage Guidelines
The resource threshold command defines the resource load levels that trigger Resource Availability Indicator (RAI) messages. To view the monitored resources, enter the show gateway command.
The monitored H.323 resources include digital signal processor (DSP) channels and DS0s. Use the show call resource voice stats command to see the total amount of resources available for H.323 calls.
Note
See the dial-peer configuration commands for details on how to associate a dial peer with a PRI or CAS group.
When any monitored H.323 resources exceed the threshold level defined by the high parameter, the gateway sends an RAI message to the gatekeeper with the AlmostOutOfResources field flagged. This message reports high resource usage.
When all gateway H.323 resources drop below the level defined by the low parameter, the gateway sends the RAI message to the gatekeeper with the AlmostOutOfResources field cleared.
When a gatekeeper can choose between multiple gateways for call completion, the gatekeeper uses internal priority settings and gateway resource statistics to determine which gateway to use. When all other factors are equal, a gateway that has available resources will be chosen over a gateway that has reported limited resources.
Examples
The following command defines the H.323 resource limits for a gateway:
resource threshold high 70 low 60Related Commands
response-timeout
To configure the maximum time to wait for a response from a server, use the response-timeout command in settlement configuration mode. To restore the default value of this command, use the no form of this command.
response-timeout number
no response-timeout number
Syntax Description
Defaults
The default response timeout is one (1) second.
Command Modes
Settlement configuration
Command History
Usage Guidelines
If no response is received within the response-timeout time limit, the current connection ends, and the router attempts to contact the next service point.
Examples
The following example illustrates a response-timeout set to 1 second.
settlement 0response-timeout 1Related Commands
retry-delay
To set the time between attempts to connect with the settlement provider, use the retry-delay command in settlement configuration mode. To restore the default value, use the no form of this command.
retry-delay number
no retry-delay
Syntax Description
number
Length of time (in seconds) between attempts to connect with the settlement provider. The valid range for retry delay is from 1 to 600 seconds.
Defaults
The default retry delay is two seconds.
Command Modes
Settlement configuration
Command History
Usage Guidelines
After exhausting all service points for the provider, the router is delayed for the specified length of time before resuming connection attempts.
Examples
The following example sets a retry value of 15 seconds:
settlement 0relay-delay 15Related Commands
retry-limit
To set the maximum number of attempts to connect to the provider, use the retry-limit command in settlement configuration mode. To restore the default value, use the no form of this command.
retry-limit number
no retry-limit number
Syntax Description
Defaults
The default retry limit is one (1) retry.
Command Modes
Settlement configuration
Command History
Usage Guidelines
If no connection is established after the configured retries, the router ceases connection attempts. The retry limit number does not count the initial connection attempt. A retry limit of one (default) results in a total of two connection attempts to every service point.
Examples
The following example sets the number of retries to 1:
settlement 0retry-limit 1Related Commands
retry (SIP user-agent)
To configure the number of retry attempts for Session Initiation Protocol (SIP) messages, use the retry command in SIP user-agent configuration mode. To reset this command to the default value, use the no form of this command.
retry {invite number | response number | bye number | cancel number}
no retry {invite number | response number | bye number | cancel number}
Syntax Description
Defaults
invite: 6
response: 6
bye: 10
cancel: 10Command Modes
SIP user-agent configuration
Command History
12.1(1)T
This command was introduced on the Cisco 2600 series and Cisco 3600 series routers and on the Cisco AS5300 universal access server.
Usage Guidelines
To reset this command to the default value, you can also use the default command.
Examples
In the following example, the number of invite retries has been set to 5.sip-uaretry invite 5Related Commands
sip-ua
Enables the sip-ua configuration commands, with which you configure the user agent.
ring
To set up a distinctive ring for your connected telephones, fax machines, or modems, use the ring command in interface configuration mode. To disable the specified distinctive ring, use the no form of this command.
ring cadence-number
no ring cadence-number
Syntax Description
Defaults
The default is 0.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to Cisco 800 series routers.
You can specify this command when creating a dial peer. This command will not work if it is not specified within the context of a dial peer. For information on creating a dial peer, refer to the Cisco 800 Series Routers Software Configuration Guide.
Examples
The following example specifies the type 1 distinctive ring:
ring 1Related Commands
ring cadence
To specify the ring cadence for a Foreign Exchange Station (FXS) voice port, use the ring cadence command in voice-port configuration mode. To restore the default value, use the no form of this command.
ring cadence {pattern-number | define pulse interval}
no ring cadence
Syntax Description
Defaults
Ring cadence defaults to the pattern you specify with the cptone command.
Command Modes
Voice-port configuration
Command History
Usage Guidelines
The patternXX keyword provides preset ring cadence patterns for use on any platform. The define keyword allows you to create a custom ring cadence. On the Cisco 2600 and 3600 series routers, only one or two pairs of digits can be entered under the define keyword.
Examples
The following example configures the ring cadence for 1 second on and 4 seconds off on voice port 1/1 on a Cisco MC3810 multiservice concentrator:
voice-port 1/1ring cadence pattern02The following example configures the ring cadence for 1 second on, 1 second off, 1 second on, and
5 seconds off on voice port 1/2 on a Cisco MC3810 multiservice concentrator:voice-port 1/2ring cadence define 10 10 10 50The following example configures the ring cadence for 1 second on and 2 seconds off on voice port 1/0/0 on a Cisco 2600 or 3600 series router:
voice-port 1/0/0ring cadence pattern04Related Commands
ring frequency
Specifies the ring frequency for a specified FXS voice port.
cptone
Specifies the default tone, ring, and cadence settings according to country.
ring frequency
To specify the ring frequency for a specified Foreign Exchange Station (FXS) voice port, use the ring frequency command in voice-port configuration mode. To restore the default value, use the no form of this command.
ring frequency number
no ring frequency number
Syntax Description
number
Ring frequency (hertz) used in the FXS interface. Valid entries on the Cisco 3600 series are 25 and 50. Valid entries on the Cisco MC3810 multiservice concentrator are 20 and 30.
Defaults
25 Hz on the Cisco 3600 series routers and 20 Hz on the Cisco MC3810 multiservice concentrators.
Command Modes
Voice-port configuration
Command History
11.3(1)T
This command was introduced on the Cisco MC3810 multiservice concentrator.
Usage Guidelines
Use the ring frequency command to select a specific ring frequency for an FXS voice port. Use the no form of this command to reset the default value. The ring frequency you select must match the connected equipment. If set incorrectly, the attached phone might not ring or might buzz. In addition, the ring frequency is usually country-dependent. You should take into account the appropriate ring frequency for your area before configuring this command.
This command does not affect ringback, which is the ringing a user hears when placing a remote call.
Examples
The following example configures the ring frequency on the Cisco 3600 series for 25 Hz:
voice-port 1/0/0ring frequency 25The following example configures the ring frequency on the Cisco MC3810 multiservice concentrator for 20 Hz:
voice-port 1/1ring frequency 20Related Commands
ring number
To specify the number of rings for a specified Foreign Exchange Office (FXO) voice port, use the ring number command in voice-port configuration mode. To restore the default value, use the no form of this command.
ring number number
no ring number number
Syntax Description
number
Number of rings detected before answering the call. Valid entries are numbers from 1 to 10. The default is 1.
Defaults
One ring
Command Modes
Voice-port configuration
Command History
Usage Guidelines
Use the ring number command to set the maximum number of rings to be detected before answering a call over an FXO voice port. Use the no form of this command to reset the default value, which is one ring.
Normally, this command should be set to the default so that incoming calls are answered quickly. If you have other equipment available on the line to answer incoming calls, you might want to set the value higher to give the equipment sufficient time to respond. In that case, the FXO interface would answer if the equipment online did not answer the incoming call in the configured number of rings.
This command is not applicable to Foreign Exchange Station (FXS) or E&M interfaces because they do not receive ringing on incoming calls.
Examples
The following example on the Cisco 3600 series sets five rings as the maximum number of rings to be detected before closing a connection over this voice port:
voice-port 1/0/0ring number 5The following example on the Cisco MC3810 multiservice concentrator sets five rings as the maximum number of rings to be detected before closing a connection over this voice port:
voice-port 1/1ring number 5Related Commands
roaming (dial-peer)
To enable the roaming capability for the dial peer, use the roaming command in dial-peer configuration mode. To disable the roaming capability, use the no form of this command.
roaming
no roaming
Syntax Description
This command has no arguments or keywords.
Defaults
No roaming
Command Modes
Dial-peer configuration
Command History
12.1(1)T
This command was introduced on the Cisco 2600 series and Cisco 3600 series routers and on the Cisco AS5300 universal access server`.
Usage Guidelines
Enable the roaming capability of a dial peer if that dial peer can terminate roaming calls. If a dial peer is dedicated to local calls only, disable the roaming capability.
The roaming dial peer must work with a roaming service provider. If the dial peer allows a roaming user to go through, and the service provider is not roaming-enabled, the call fails.
Examples
The following example enables the roaming capability for the dial peer:
dial-peer voice 10 voiproamingRelated Commands
roaming (settlement)
To enable the roaming capability for a settlement provider, use the roaming command in settlement configuration mode. To disable the roaming capability, use the no form of this command.
roaming
no roaming
Syntax Description
This command has no arguments or keywords.
Defaults
No roaming
Command Modes
Settlement configuration
Command History
12.1(1)T
This command was introduced on the Cisco 2600 series and Cisco 3600 series routers and on the Cisco AS5300 universal access server.
Usage Guidelines
Enable roaming capability of a settlement provider if that provider can authenticate a roaming user and route roaming calls.
A roaming call is successful only if both the settlement provider and the outbound dial peer for that call are roaming-enabled.
Examples
The following example enables the roaming capability for the settlement provider:
settlement 0roamingRelated Commands
rtsp client session history duration
To specify how long to keep Real Time Streaming Protocol (RTSP) session history records in memory, use the rtsp client session history duration command in global configuration mode. To set the value to the default, use the no form of this command.
rtsp client session history duration number
no rtsp client session history duration number
Syntax Description
Defaults
10 minutes
Command Modes
Global configuration
Command History
12.1(3)T
This command was introduced on the Cisco AS5300 universal access server.
Examples
The following example sets the RTSP session history to 500 minutes:
rtsp client session history duration 500Related Commands
rtsp client session history records
To configure the number of records to keep in the RTSP client session history, use the rtsp client session history records command in global configuration mode. To set the value to the default, use the no form of this command.
rtsp client session history records number
no rtsp client session history records number
Syntax Description
number
Specifies the number of records to retain in a session history. Values range from 1 to 100000.
Defaults
50 records
Command Modes
Global configuration
Command History
12.1(3)T
This command was introduced on the Cisco AS5300 universal access server.
Examples
The following example sets the RTSP client history to 500 records:
rtsp client session history records 500Related Commands
rule
To apply a translation rule to a calling party number or a called party number for both incoming and outgoing calls, use the rule command in translation-rule configuration mode. To remove the translation rule, use the no form of this command.
rule name-tag input-matched-pattern substituted-pattern [match-type substituted-type]
no rule name-tag input-matched-pattern substituted-pattern [match-type substituted-type]
Syntax Description
Note
Defaults
No default behavior or values.
Command Modes
Translation-rule configuration
Command History
Usage Guidelines
When configuring your dial peers, you are provided with an option called the translation rule. This option applies a translation rule to a calling party number (Automatic Number Identification [ANI]) or a called party number (Dial Number Information Service [DNIS]) for both incoming and outgoing calls within Cisco H.323 voice-enabled gateways. Also, the rule allows translation of the type of number.
Examples
The following example applies a translation rule. If a called number starts with 5552205 or 52205, then translation rule 21 will use the rule command to forward the number to 14085552205 instead.
translation-rule 21rule 1 555.% 1408555 subscriber internationalrule 2 7.% 1408555 abbreviated internationalIn the next example, if a called number is either 14085552205 or 014085552205, then after the execution of the translation rule 345, the forwarding digits will be 52205. If the match type is configured and the type is not "unknown," then the dial peer matching will be required to match input string numbering type.
translation-rule 345rule 1 .%555.% 7 any abbreviatedRelated Commands
security
To enable authentication and authorization on a gatekeeper, use the security command in gatekeeper configuration mode. To disable security, use the no form of this command.
security {any | h323-id | e164} {password default password | password separator character}
no security {any | h323-id | e164} {password default password | password separator character}
Syntax Description
Defaults
No default
Command Modes
Gatekeeper configuration
Command History
11.3(2)NA
This command was introduced on the Cisco 2600 series and Cisco 3600 series routers.
Usage Guidelines
Use the security command to enable identification of registered aliases by RADIUS/TACACS+. If the alias does not exist in RADIUS/TACACS+, the endpoint will not be allowed to register.
A RADIUS/TACACS+ server and encryption key must have been configured in Cisco IOS software for security to work.
Only the first alias of the proper type will be identified. If no alias of the proper type is found, the registration will be rejected.
This command does not allow you to define the password mechanism unless the security type (h323-id or e164 or any) has been defined. Although the no security password command undefines the password mechanism, it leaves the security type unchanged, so security is still enabled. However, the no security command disables security entirely, including removing any existing password definitions.
Examples
The following example enables identification of registrations using the first H.323 ID found in any registration:
security h323idThe following example enables security, authenticating all users by using their H.323-IDs and a password of qwerty2x:
security h323-idsecurity password qwerty2xThe next example enables security, authenticating all users by using their H.323-IDs and the password entered by the user in the H.323-ID alias he or she registers:
security h323-idsecurity password separator !Now if a user registers with an H.323-ID of joe!024aqx, the gatekeeper authenticates user joe with password 024aqx, and if that is successful, registers the user with the H.323-ID of joe. If the exclamation point is not found, the user is authenticated with the default password, or a null password if no default has been configured.
The following example enables security, authenticating all users by using their E.164 IDs and the password entered by the user in the H.323-ID alias he or she registers:
security e164security password separator !Now if a user registers with an E.164 address of 5551212 and an H.323-ID of !hs8473q6, the gatekeeper authenticates user 5551212 and password hs8473q6. Because the H.323-ID string supplied by the user begins with the separator character, no H.323-ID is registered, and the user is known only by the E.164 address.
Related Commands
sequence-numbers
To enable the generation of sequence numbers in each frame generated by the digital signal processor (DSP) for Voice over Frame Relay applications, use the sequence-numbers command in dial-peer configuration mode. To disable the generation of sequence numbers, use the no form of this command.
sequence-numbers
no sequence-numbers
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
Sequence numbers on voice packets allow the digital signal processor (DSP) at the playout side to detect lost packets, duplicate packets, or out-of-sequence packets. This helps the DSP to mask out occasional drop-outs in voice transmission at the cost of one extra byte per packet. The benefit of using sequence numbers versus the cost in bandwidth of adding an extra byte to each voice packet on the Frame Relay network must be weighed to determine whether to disable this function for your application.
Another factor to consider is that this command does not affect codecs that require a sequence number, such as G.726. If you are using a codec that requires a sequence number, the DSP will generate one regardless of the configuration of this command.
Examples
The following example shows how to disable the generation of sequence numbers for VoFR frames on a Cisco 2600 series or 3600 series router or on a Cisco MC3810 multiservice concentrator for VoFR dial peer 200, starting from global configuration mode:
dial-peer voice 200 vofrno sequence-numbersRelated Commands
server (RLM)
To identify an RLM server, use the server RLM configuration command. To remove the identification, use the no form of this command
server name-tag
no server name-tag
Syntax Description
name-tag
Name to identify the server configuration so that multiple entries of server configuration can be entered.
Defaults
Disabled
Command Modes
RLM configuration
Command History
Usage Guidelines
Each server can have multiple entries of IP addresses or aliases.
Examples
The following example identifies the RLM server and defines the associated IP addresses:
rlm group 1
server r1-server
link address 10.1.4.1 source Loopback1 weight 4
link address 10.1.4.2 source Loopback2 weight 3
Related Commands
server registration-port
To configure the listener port for the server to establish a connection with the gatekeeper, use the server registration-port command in gatekeeper configuration mode. To force the gatekeeper to close the listening socket so that no more new registration takes place, use the no form of this command.
server registration-port port number
no server registration-port port number
Syntax Description
port number
Specifies a single range of values from 1 through 65535 for the port number on which the gatekeeper listens for external server connections.
Defaults
The registration port of the gatekeeper is not configured, so no external server can register with this gatekeeper.
Command Modes
Gatekeeper configuration
Command History
Usage Guidelines
Use this command to configure a server registration port to poll for servers that want to establish connections with the gatekeeper on this router.
Note
Examples
The following example shows how a listener port for a server is established for connection with a gatekeeper:
server registration-port 20000Related Commands
server trigger
Configure static server triggers for specific RAS messages to be forwarded to a specified server.
server trigger
To configure a static server trigger for external applications, use the server trigger command in gatekeeper configuration mode. To remove a single statically configured trigger entry, use the no form of this command. To remove every static trigger you configured if you want to delete them all, use the all keyword.
server trigger {arq | lcf | lrj | lrq | rrq | urq} gkid priority server-id server-ipaddress server-port
no server trigger {arq | lcf | lrj | lrq | rrq | urq} gkid priority
no server trigger all
Syntax Description
Defaults
No server triggers are set.
Command Modes
Gatekeeper configuration
Command History
Usage Guidelines
Use this command to configure a static server trigger. There are six different server triggers—one for each of the RAS messages. To configure a trigger, go to its submode where a set of subcommands are used to trigger a condition. See the following examples.
In ARQ submode, enter the following syntax:
server trigger arq gkid priority server-id server-ipaddress server-portIn LCF submode, enter the following syntax:
server trigger lcf gkid priority server-id server-ipaddress server-portIn LRJ submode, enter the following syntax:
server trigger lrj gkid priority server-id server-ipaddress server-portIn LRQ submode, enter the following syntax:
server trigger lrq gkid priority server-id server-ipaddress server-portIn RRQ submode, enter the following syntax:
server trigger rrq gkid priority server-id server-ipaddress server-portIn URQ submode, enter the following syntax:
server trigger urq gkid priority server-id server-ipaddress server-portThe following options are available in all submodes:
The destination-info argument is under the ARQ, LRQ, LCF, and LRJ submode and has the following options:
The redirect-reason argument is under the ARQ and LRQ submodes and has the following options:
The remote-ext-address argument is under the LCF trigger submode and has the following options:
The endpoint-type argument is under the RRQ and URQ trigger submodes and has the following options:
The supported-prefix keyword is under the RRQ and URQ submodes and has the following options:
supported-prefix
Configure the gateway technology prefix to trigger on.
word
Enter a word within the set of "0123456789#*" when configuring the E.164 pattern for a gateway technology prefix.
Entering the no form of the server trigger command removes the trigger definition from the Cisco IOS gatekeeper with all statically configured conditions under that trigger.
Examples
The following example configures a server trigger on gatekeeper sj.xyz.com to notify external server "Server-123" of any call to an E.164 number that starts with 1800 followed by any 7 digits (1800551212, for example):
Gatekeeperserver trigger arq sj.xyz.com 1 Server-123 1.14.93.130 1751destination-info e164 1800.......exitRelated Commands
session
To associate a transport session with a specified session-group, use the session group command in backhaul session manager configuration mode. It is assumed that the server is located on a remote machine. To delete the session, use the no form of this command.
session group group-name remote_ip remote_port local_ip local_port priority
no session group group-name remote_ip remote_port local_ip local_port priority
Syntax Description
Defaults
No default behavior or values.
Command Modes
Backhaul session manager configuration
Command History
12.1(1)T
This command was introduced.
12.2(2)XB1
This command was implemented on the Cisco AS5850 platform.
Examples
To associate a transport session with the session-group Group5 and specify the parameters described above, see the following example:
Router(config-bsm)# session group group5 161.44.2.72 5555 172.18.72.198 5555 1session protocol
To specify a session protocol for calls between the local and remote routers using the packet network, use the session protocol command in dial-peer configuration mode. To reset the default value for this command, use the no form of this command.
session protocol {cisco | sipv2 | aal2-trunk | smtp}
no session protocol
Syntax Description
Defaults
No default behaviors or values.
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
The keyword cisco is applicable only to VoIP on the Cisco 3600 series routers. The keyword aal2-trunk is applicable only to VoATM on the Cisco MC3810 multiservice concentrator.
This command applies to both on-ramp and off-ramp store-and-forward fax functions.
Examples
The following is an example of configuring a VoIP dial peer for H.323 or SIP as the session protocol for VoIP call signaling:
dial-peer voice 102 voipsession protocol sipv2The following example selects AAL2 trunking as the session protocol on a Cisco MC3810 multiservice concentrator:
dial-peer voice 10 voatmsession protocol aal2-trunkThe following example selects Cisco Session Protocol as the session protocol on a Cisco 3600 series router:
dial-peer voice 20 voipsession protocol ciscoThe following example selects SMTP as the session protocol:
dial-peer voice 10 mmoipsession protocol smtpRelated Commands
session protocol (Voice over Frame Relay)
To establish a Voice over Frame Relay protocol for calls between the local and remote routers via the packet network, use the session protocol command in dial-peer configuration mode. To reset the default value, use the no form of this command.
session protocol {cisco-switched | frf11-trunk}
no session protocol
Syntax Description
cisco-switched
Specifies proprietary Cisco VoFR session protocol. (This is the only valid session protocol for the Cisco 7200 series.)
frf11-trunk
Specifies FRF.11 session protocol.
Defaults
cisco-switched
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
For Cisco-to-Cisco dial peer connections, Cisco recommends that you use the default session protocol because of the advantages it offers over a pure FRF.11 implementation. When connecting to FRF.11-compliant equipment from other vendors, use the FRF.11session protocol.
Note
Examples
The following example shows how to configure the FRF.11 session protocol on a Cisco 2600 series or 3600 series router for VoFR dial peer 200:
dial-peer voice 200 vofrsession protocol frf11-trunkcalled-number 5552150The following example shows how to configure the FRF.11 session protocol on a Cisco MC3810 multiservice concentrator for VoFR dial peer 200:
dial-peer voice 200 vofrsession protocol frf11-trunkRelated Commands
session protocol aal2
To enter the voice-service-session configuration mode and specify AAL2 trunking on a Cisco MC3810 multiservice concentrator, use the session protocol aal2 command in voice-service configuration mode.
session protocol aal2
Syntax Description
This command has no keywords or arguments.
Defaults
There is no default setting for this command.
Command Modes
Voice-service configuration
Command History
12.1(1)XA
This command was introduced on the Cisco MC3810 multiservice concentrator.
12.1(2)T
This command was integrated into the 12.1(2)T release.
Usage Guidelines
This command applies to VoATM on the MC3810 multiservice concentrator.
In the voice-service-session configuration mode for AAL2, you can configure only AAL2 features, such as call admission control and subcell multiplexing.
Examples
The following example shows how to access the voice-service-session configuration mode, beginning in global configuration mode:
voice service voatmsession protocol aal2session protocol multicast
To set the session protocol as multicast, use the session protocol multicast command dial-peer configuration mode. To negate this command and return to the Cisco default session protocol, use the no version of this command.
session protocol multicast
no session protocol multicast
Syntax Description
There are no keywords or arguments.
Defaults
When this command is not implemented, the default session protocol is cisco.
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
Use the session protocol multicast dial-peer configuration command for voice conferencing in a
Hoot and Holler networking implementation. This command allows more than two ports to join the same session simultaneously. It is supported on Cisco 2600 and Cisco 3600 series routers.Examples
The following example shows the use of the session protocol multicast dial-peer configuration command in context with its accompanying commands:
dial-peer voice 111 voipdestination-pattern 111session protocol multicastsession target ipv4:237.111.0.111:22222ip precedence 5codec g711ulawRelated Commands
session target ipv4
Assigns the session target for voice-multicasting dial peers.
session target (VoATM)
To specify a network-specific address for a specified VoATM dial peer, use the session target command in dial-peer configuration mode. To restore default values for this parameter, use the no form of this command.
Cisco 3600 Series Routers Voice over ATM Dial Peers
session target interface pvc {name | vpi/vci | vci}
no session target
Cisco MC3810 Multiservice Concentrator Voice over ATM Dial Peers
session target {serial | atm} interface pvc {word | vpi/vci | vci} cid
no session target
Syntax Description
Defaults
The default for this command is enabled with no IP address or domain name defined.
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
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 syntax of this command complies with the simple syntax of mailto: as described in RFC 1738.
The session target loopback command is used for testing the voice transmission path of a call. The loopback point will depend on the call origin and the loopback type selected.
This command applies to on-ramp store-and-forward fax functions.
You must enter the session protocol aal2-trunk dial-peer configuration command before you can specify a cid for a dial peer for VoATM on the Cisco MC3810 multiservice concentrator.
Note
Examples
The following example configures a session target for Voice over ATM on a Cisco MC3810 multiservice concentrator. The session target is sent to ATM interface 0, and for a PVC with a VCI of 20.
dial-peer voice 12 voatmdestination-pattern 13102221111session target atm0 pvc 20The following example delivers fax-mail to multiple recipients:
dial-peer voice 10 mmoipsession target marketing-information@mailer.example.comAssuming that mailer.example.com is running sendmail, you can put the following information into its /etc/aliases file:
marketing-information:john@example.com,fax=+14085551212@sj-offramp.example.com
The following example displays configuring a session target for Voice over ATM on the Cisco 3600 series. The session target is sent to ATM interface 0, and is for a PVC with a VPI/VCI of 1/100.
dial-peer voice 12 voatmdestination-pattern 13102221111session target atm1/0 pvc 1/100Related Commands
session target (VoFR)
To specify a network-specific address for a specified VoFR dial peer, use the session target command in dial-peer configuration mode. To restore default values for this parameter, use the no form of this command.
Cisco 2600 and 3600 Series Routers Voice over Frame Relay Dial Peers
session target interface dlci [cid]
no session target
Cisco MC3810 Multiservice Concentrator Voice over Frame Relay Dial Peers
session target interface dlci [cid]
no session target
Cisco 7200 Series Routers Voice over Frame Relay Dial Peers
session target interface dlci
no session target
Syntax Description
Defaults
The default for this command is enabled with no IP address or domain name defined.
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
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 syntax of this command complies with the simple syntax of mailto: as described in RFC 1738.
The session target loopback command is used for testing the voice transmission path of a call. The loopback point will depend on the call origin and the loopback type selected.
For VoFR dial peers, the cid option is not allowed when the cisco-switched option for the session protocol command is used.
Examples
The following example configures a session target for Voice over Frame Relay on a Cisco MC3810 multiservice concentrator with a session target on serial port1 and a DLCI of 200:
dial-peer voice 11 vofrdestination-pattern 13102221111session target serial1 200The following example shows how to configure serial interface 1/0, DLCI 100 as the session target for VoFR dial peer 200 (an FRF.11 dial peer) on a Cisco 2600 series or 3600 series router, starting from global configuration mode and using the FRF.11 session protocol:
dial-peer voice 200 vofrdestination-pattern 13102221111called-number 5552150session protocol frf11-trunksession target serial 1/0 100 20The following example delivers fax-mail to multiple recipients:
dial-peer voice 10 mmoipsession target marketing-information@mailer.example.comAssuming that mailer.example.com is running sendmail, you can put the following information into its /etc/aliases file:
marketing-information:john@example.com,fax=+14085551212@sj-offramp.example.com
Related Commands
session target (VoIP)
To specify a network-specific address for a specified VoIP dial peer, use the session target command in dial-peer configuration mode. To restore default values for this parameter, use the no form of this command.
Cisco 2600 and Cisco 3600 Series Routers and Cisco MC8310 Multiservice Concentrator Voice over IP Dial Peers
session target {ipv4:destination-address | dns:[$s$. | $d$. | $e$. | $u$.] host-name | loopback:rtp | loopback:compressed | loopback:uncompressed | ras | settlement}
no session target
Cisco AS5300 Universal Access Server Voice over IP Dial Peers
session target {ipv4:destination-address | dns:[$s$. | $d$. | $e$. | $u$.] host-name | loopback:rtp | loopback:compressed | loopback:uncompressed | mailto: | {name | $d$}@domain-name | ipv4:destination-address | dns:[$s$. | $d$. | $u$. | $e$.] host-name}
no session target
Cisco AS5800 Universal Access Server Voice over IP Dial Peers
session target {ipv4:destination-address | dns:[$s$. | $d$. | $e$. | $u$.] host-name | loopback:rtp | loopback:compressed | loopback:uncompressed}
no session target
Syntax Description
Defaults
The default state for this command is enabled, with no IP address or domain name defined.
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
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 origin 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 must 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.
In Cisco IOS Release 12.1(1)T the session target command configuration cannot combine the target of RAS with the settle-call command. When configuring the VoIP dial peers for a settlement server, if session target type is settlement, the provider-number parameter in the session target and settle-call commands should be identical.
When the VoIP dial peers are configured for a settlement server, if the session target type is settlement, the provider-number parameter in the session target and settle-call commands should be identical.
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 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 preceding 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 voipdestination-pattern 13102221111session target rasThe following example configures a session target using settlement:
session target settlement:0Related Commands
session transport
To configure the VoIP dial peer to use TCP or User Datagram Protocol (UDP) as the underlying transport layer protocol for Session Initiation Protocol (SIP) messages, use the session transport command in dial-peer configuration mode. To reset the value to the default, use the no form of this command.
session transport {udp | tcp }
Syntax Description
udp
Configure the SIP dial peer to use the UDP transport layer protocol. This is the default.
tcp
Configure the SIP dial peer to use the TCP transport layer protocol.
Defaults
The SIP dial peer uses UDP.
Note
Command Modes
Dial-peer configuration
Command History
12.1(1)T
This command was introduced on the Cisco 2600 series and Cisco 3600 series routers and on the Cisco AS5300 universal access server.
Usage Guidelines
Use show sip-ua status to ensure that the transport protocol that you set using the session transport command matches the protocol set using the transport command.
Examples
The following example shows a VoIP dial peer configured to use UDP as the underlying transport layer protocol for SIP messages:dial-peer voice 102 voipsession transport udpset
To create a fault-tolerant or non-fault-tolerant session-set with the client or server option, use the set command in backhaul session manager configuration mode. To delete the set, use the no form of this command.
set set-name { client | server } { ft | nft }
no set set-name { client | server } { ft | nft }
Syntax Description
Defaults
No default behavior or values.
Command Modes
Backhaul session manager configuration
Command History
Usage Guidelines
There can be multiple groups associated with a session-set.
The session-set should only be configured for the client for backhaul (not the server).
A set cannot be deleted unless the groups associated with the set are deleted first.
Examples
To specify the client set named Set1 to fault-tolerant, see the following example:
Router(config-bsm)# set set1 client ftsettle-call
To force a call to be authorized with a settlement server that uses the address resolution method specified in the session target type command, use the settle-call command in dial-peer configuration mode. To make sure that no authorization will be performed by a settlement server, use the no form of this command.
settle-call provider-number
no settle-call provider-number
Syntax Description
Defaults
No default behavior or values.
Command Modes
Dial-peer configuration
Command History
12.1(1)T
This command was introduced on the Cisco 2600 series and Cisco 3600 series routers and on the Cisco AS5300 universal access server.
Usage Guidelines
Using the session target command, a dial peer can determine the address of the terminating gateway through the ipv4, dns, ras, and settlement keywords.
If the session target is not settlement, and the settle-call provider-number argument is set, the gateway resolves the terminating gateway's address using the specified method and then requests the settlement server to authorize that address and create a settlement token for that particular address. If the server cannot authorize the terminating gateway address suggested by the gateway, the call fails.
Do not combine the session target types ras and settle-call. Combination of session target types is not supported in Cisco IOS Release 12.1(1)T.
Examples
The following example sets a call to be authorized with a settlement server that uses the address resolution method specified in the session target:
dial-peer voice 10 voipdestination-pattern 1408.......session target ipv4:172.22.95.14settle-call 0Related Commands
settlement
To enter settlement configuration mode and specify the attributes specific to a settlement provider, use the settlement command in global configuration mode. To disable the settlement provider, use the no form of this command.
settlement provider-number
no settlement provider-number
Syntax Description
provider-number
Specifies a digit that defines a particular settlement server. The only valid entry is 0.
Defaults
0
Command Modes
Global configuration
Command History
Usage Guidelines
The variable provider-number defines a particular settlement provider. For Cisco IOS Release 12.1, only one clearinghouse per system is allowed, and the only valid value for provider-number is 0.
Examples
This example shows how to enter settlement configuration mode:
settlement 0Related Commands
settlement roam-pattern
To configure a pattern that must be matched to determine if a user is roaming, use the settlement roam-pattern command in global configuration mode. To delete a particular pattern, use the no form of this command.
settlement provider-number roam-pattern pattern {roaming | no roaming}
no settlement provider-number roam-pattern pattern {roaming | no roaming}
Syntax Description
provider-number
Digit defining the ID of particular settlement server. The only valid entry is 0.
pattern
Specifies a user account pattern.
roaming | no roaming
Determines whether a user is roaming.
Defaults
No default pattern
Command Modes
Global configuration
Command History
12.1(1)T
This command was introduced on the Cisco 2600 series and Cisco 3600 series routers and on the Cisco AS5300 universal access server.
Usage Guidelines
Multiple "roam patterns" could be entered on one gateway.
Examples
The following example will configure a pattern that determines if a user is roaming:
settlement 0 roam-pattern 1222 roamsettlement 0 roam-pattern 1333 noroamsettlement roam-pattern 1444 roamsettlement roam-pattern 1555 noroamRelated Commands
roaming (settlement)
Enables the roaming capability for a settlement provider.
settlement
Enters settlement configuration mode.
sgcp
To start and allocate resources for the Simple Gateway Control Protocol (SGCP) daemon, use the sgcp command in global configuration mode. To terminate all calls, release all allocated resources, and kill the SGCP daemon, use the no form of this command.
sgcp
no sgcp
Syntax Description
This command has no arguments or keywords.
Defaults
The SGCP daemon is not enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
When the SGCP daemon is not active, all SGCP messages are ignored.
When you enter the no sgcp command, the SGCP process is removed.
Note
Examples
The following example shows the SGCP daemon being enabled:
sgcpThe following example shows the SGCP daemon being disabled:
no sgcpRelated Commands
sgcp call-agent
To define the IP address of the default Simple Gateway Control Protocol (SGCP) call agent in the router configuration file, use the sgcp call-agent command in global configuration mode. To remove the IP address of the default SGCP call agent from the router configuration, use the no form of this command.
sgcp call-agent ipaddress [:udp port]
no sgcp call-agent ipaddress
Syntax Description
ipaddress
Specifies the IP address or hostname of the call agent.
:udp port
(Optional) Specifies the UDP port of the call agent.
Defaults
No IP address is configured.
Command Modes
Global configuration
Command History
Usage Guidelines
Setting this command defines the IP address of the default SGCP call agent to which the router sends an initial RSIP (Restart In Progress) packet when the router boots up. This is used for initial boot-up only before the SGCP call agent contacts the router acting as the gateway.
When you enter the no sgcp call-agent command, only the IP address of the default SGCP call agent is removed.
Examples
The following example shows SGCP being enabled and the IP address of the call agent being specified:
sgcpsgcp call-agent 209.165.200.225Related Commands
sgcp graceful-shutdown
To block all new calls and gracefully terminate all existing calls (wait for the caller to end the call), use the sgcp graceful-shutdown command in global configuration mode. To unblock all calls and allow new calls to go through, use the no form of this command.
sgcp graceful-shutdown
no sgcp graceful-shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
Once you issue this command, all requests for new connections (CreateConnection requests) are denied. All existing calls are maintained until users terminate them, or until you enter the no sgcp command. When the last active call is terminated, the SGCP daemon is terminated, and all resources allocated to it are released.
Examples
The following example shows all new calls being blocked and existing calls being terminated:
sgcp graceful-shutdownRelated Commands
sgcp max-waiting-delay
To set the Simple Gateway Control Protocol (SGCP) maximum waiting delay to prevent restart avalanches, use the sgcp max-waiting-delay command in global configuration mode. To restore the default value, use the no form of this command.
sgcp max-waiting-delay delay
no sgcp max-waiting-delay delay
Syntax Description
delay
Sets the maximum waiting delay (MWD) value in milliseconds. The valid range is from 0 to 600,000. The default is 3000.
Defaults
3,000 milliseconds
Command Modes
Global configuration
Command History
Examples
The following example shows the maximum wait delay value set to 40 milliseconds:
sgcp max-waiting-delay 40Related Commands
sgcp modem passthru
To enable Simple Gateway Control Protocol (SGCP) modem or fax pass-through, use the sgcp modem passthru command in global configuration mode. To disable SGCP modem or fax pass-through, use the no form of this command.
sgcp modem passthru {ca | cisco | nse}
no sgcp modem passthru {ca | cisco | nse}
Syntax Description
ca
Uses the call agent controlled modem upspeed method violation message.
cisco
Uses a Cisco-proprietary upspeed method based on the protocol.
nse
Uses the NSE-based modem upspeed method.
Defaults
SGCP modem or fax pass-through is disabled by default.
Command Modes
Global configuration.
Command History
Usage Guidelines
You can use this command for fax pass-through because the answer tone can come from either modem or fax transmissions. The upspeed method is the method used to dynamically change the codec type and speed to meet network conditions.
If you use the nse option, you must also configure the sgcp tse payload command.
Examples
The following example shows SGCP modem pass-through configured using the call agent upspeed method:
sgcp modem passthru caThe following example shows SGCP modem pass-through configured using the proprietary Cisco upspeed method:
sgcp modem passthru ciscoThe following example shows SGCP modem pass-through configured using the NSE-based modem upspeed:
sgcp modem passthru nsesgcp tse payload 110Related Commands
sgcp quarantine-buffer disable
To disable the Simple Gateway Control Protocol (SGCP) quarantine buffer, use the sgcp quarantine-buffer disable command in global configuration mode. To reenable the SGCP quarantine buffer, use the no form of this command.
sgcp quarantine-buffer disable
no sgcp quarantine-buffer disable
Syntax Description
This command has no arguments or keywords.
Defaults
The SGCP quarantine buffer is enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
The SGCP quarantine buffer is the mechanism for buffering the SGCP events between two RQNT messages.
Examples
The following example shows the SGCP quarantine buffer being disabled:
sgcp quarantine-buffer disableRelated Commands
sgcp request retries
To specify the number of times to retry sending "notify" and "delete" messages to the Simple Gateway Control Protocol (SGCP) call agent, use the sgcp request retries command in global configuration mode. To restore the default value, use the no form of this command.
sgcp request retries count
no sgcp request retries
Syntax Description
count
Specifies the number of times a "notify" and "delete" message is retransmitted to the SGCP call agent before it is dropped. The valid range is from 1 to 100. The default is 3.
Defaults
The default for the number of times a "notify" and "delete" message is retransmitted to the SGCP call agent before it is dropped is 3
Command Modes
Global configuration
Command History
Usage Guidelines
The actual retry count may be different from the value you enter for this command. The retry count is also limited by the call agent. If there is no response from the call agent after 30 seconds, the gateway will not retry anymore, even though the number set using the sgcp request retries command has not been reached.
The router will stop sending retries after 30 seconds, regardless of the setting for this command.
Examples
The following example shows the system configured to send the sgcp command 10 times before dropping the request:
sgcp request retries 10Related Commands
sgcp request timeout
To specify how long the system should wait for a response to a request, use the sgcp request timeout command in global configuration mode. To restore the default value, use the no form of this command.
sgcp request timeout timeout
no sgcp request timeout
Syntax Description
timeout
Specifies the number of milliseconds to wait for a response to a request. Valid range is from 1 to 10,000.
Defaults
500 milliseconds
Command Modes
Global configuration
Command History
Usage Guidelines
This command is used for "notify" and "delete" messages, which are sent to the SGCP call agent.
Examples
The following example shows the system configured to wait 40 milliseconds for a reply to a request:
sgcp request timeout 40Related Commands
sgcp restart
To trigger the router to send a Restart in Progress (RSIP) message to the Simple Gateway Control Protocol (SGCP) call agent indicating that the T1 controller is up or down so that the call agent can synchronize with the T1 controller, use the sgcp restart command in global configuration mode. To restore the default value, use the no form of this command.
sgcp restart {delay delay | notify}
no sgcp restart {delay delay | notify}
Syntax Description
Defaults
Zero (0)
Command Modes
Global configuration
Command History
Usage Guidelines
This command is used to send RSIP messages from the router to the SGCP call agent. The RSIP messages are used to synchronize the router and the call agent. RSIP messages are also sent when the sgcp command is entered to enable the SGCP daemon.
You must enter the notify option to enable RSIP messages to be sent.
Examples
The following example shows the system configured to wait 40 milliseconds before restarting SGCP:
sgcp restart delay 40The following example shows the system configured to send an RSIP notification to the SGCP call agent when the T1 controller state changes:
sgcp restart notifyRelated Commands
sgcp retransmit timer
To configure the Simple Gateway Control Protocol (SGCP) retransmission timer to use a random algorithm, use the sgcp retransmit timer command in global configuration mode. To restore the default value, use the no form of this command.
sgcp retransmit timer {random}
no sgcp retransmit timer {random}
Syntax Description
Defaults
The SGCP retransmission timer does not use the random algorithm.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to enable the random algorithm component of the retransmission timer. For example, if the retransmission timer is set to 200 milliseconds, the first retransmission timer is 200 milliseconds, but the second retransmission timer picks up a timer value randomly between either 200 or 400. The third retransmission timer picks up a timer value randomly of 200, 400, or 800 as shown below:
•
•
•
•
•
After 30 seconds, the retransmission timer no longer retries.
Examples
The following example shows the retransmission timer set to use the random algorithm:
sgcp retransmit timer randomRelated Commands
sgcp timer
To configure how the gateway detects the Real-Time Transport Protocol (RTP) stream lost, use the sgcp timer command in global configuration mode. To restore the default value, use the no form of this command.
sgcp timer {receive-rtcp timer | rtp-nse timer}
no sgcp timer {receive-rtcp timer | rtp-nse timer}
Syntax Description
Defaults
Default for receive-rtcp timer is 5.
Default for rtp-nse timer is 200.
Command Modes
Global configuration
Command History
Usage Guidelines
The RTP NSE timer is used for proxy ringing (the ringback tone is provided at the originating gateway).
Examples
The following example shows the receive-rtcp timer set to 100 milliseconds:
sgcp timer receive-rtcp 100The following example shows the rtp-nse timer set to 1000 milliseconds:
sgcp timer rtp-nse 1000Related Commands
sgcp tse payload
To enable Inband Telephony Signaling Events (TSE) for fax and modem operation, use the sgcp tse payload command in global configuration mode. To restore the default value, use the no form of this command.
sgcp tse payload type
no sgcp tse payload type
Syntax Description
type
Sets the TSE payload type. The valid range is from 96 to 119. The default is 0, meaning that the command is disabled.
Defaults
Zero (0)
Command Modes
Global configuration
Command History
Usage Guidelines
Because this command is disabled by default, you must specify a TSE payload type.
If you configure the sgcp modem passthru command to the nse value, then you must configure this command.
Examples
The following example shows the Simple Gateway Control Protocol (SGCP) modem pass-through set using the NSE-based modem upspeed and the Inband Telephony Signaling Events payload value set to 110:
sgcp modem passthru nsesgcp tse payload 110Related Commands
show aal2 profile
To display the ATM adaptation layer 2 (AAL2) profiles configured on the system, use the show aal2 profile command in privileged EXEC mode.
show aal2 profile all | {itut profile-number | custom profile-number | atmf profile-number}
Syntax Description
Command Modes
Privileged EXEC
Command History
12.1(1)XA
This command was introduced on the Cisco MC3810 multiservice concentrator.
12.1(2)T
This command was integrated into the 12.1(2)T release.
Usage Guidelines
This command applies to AAL2 Voice over ATM (VoATM) applications on the Cisco MC3810 multiservice concentrator.
Use the show aal2 profile EXEC command to display the AAL2 profiles configured in the system.
Examples
The following is sample output from the show aal2 profile command for displaying all the profiles configured in the system:
Router# show aal2 profile allPrinting all the Profiles in the systemProfile Type: ITUT Profile Number: 1 SID Support: 0Red enable: 1 Num entries: 1Coding type: g711ulaw Packet length: 40 UUI min: 0 UUI max: 15Profile Type: ITUT Profile Number: 2 SID Support: 1Red enable: 1 Num entries: 1Coding type: g711ulaw Packet length: 40 UUI min: 0 UUI max: 15Profile Type: custom Profile Number: 100 SID Support: 1Red enable: 1 Num entries: 2Coding type: g711ulaw Packet length: 40 UUI min: 0 UUI max: 7Coding type: g726r32 Packet length: 40 UUI min: 8 UUI max: 15Profile Type: ITUT Profile Number: 7 SID Support: 1Red enable: 1 Num entries: 2Coding type: g711ulaw Packet length: 40 UUI min: 0 UUI max: 15Coding type: g729ar8 Packet length: 10 UUI min: 0 UUI max: 15Profile Type: custom Profile Number: 110 SID Support: 1Red enable: 1 Num entries: 3Coding type: g711ulaw Packet length: 40 UUI min: 0 UUI max: 7Coding type: g726r32 Packet length: 40 UUI min: 8 UUI max: 15Coding type: g729ar8 Packet length: 30 UUI min: 8 UUI max: 15Table 26 provides an alphabetical listing of the fields in this output and a description of each field.
Related Commands
show atm video-voice address
To display the network service access point (NSAP) address for the ATM interface, enter the show atm video-voice address command in privileged EXEC mode.
show atm video-voice address
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(5)XK
This command was introduced for the Cisco MC3810 multiservice concentrator.
12.0(7)T
Cisco IOS Release 12.0(5)XK was integrated into Cisco IOS Release 12.0(7)T.
Usage Guidelines
Enter this command to review ATM interface NSAP addresses that have been assigned with the atm video aesa command and to ensure that ATM management is confirmed for those addresses.
Examples
On a Cisco MC3810 multiservice concentrator, the following example displays ATM interface NSAP addresses:
Router# show atm video-voice addressnsap address type ilmi status47.0091810000000002F26D4901.00107B4832E1.FE VOICE_AAL5 Confirmed47.0091810000000002F26D4901.00107B4832E1.C8 VIDEO_AAL1 ConfirmedRelated Commands
show backhaul-session-manager group
To display status, statistics, or configuration information for all available session-groups, use the show backhaul-session-manager group command in privileged EXEC mode.
show backhaul-session-manager group { status | stats | cfg } { all | name group-name }
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following displays statistics for all session-groups:
Router# show backhaul-session-manager group stats allSession-Group grp1 statisticsSuccessful Fail-Overs :0Un-Successful Fail-Over attempts:0Active Pkts receive count :0Standby Pkts receive count :0Total PDUs dispatch err :0The following displays the current configuration for all session-groups:
Router# show backhaul-session-manager group cfg allSession-GroupGroup Name :grp1Set Name :set1Sessions :3Dest:10.5.0.3 8304 Local:10.1.2.15 8304 Priority:0Dest:10.5.0.3 8300 Local:10.1.2.15 8300 Priority:2Dest:10.5.0.3 8303 Local:10.1.2.15 8303 Priority:2RUDP Optionstimer cumulative ack :100timer keepalive :1000timer retransmit :300timer transfer state :2000receive max :32cumulative ack max :3retrans max :2out-of-sequence max :3auto-reset max :5The following displays the current status of all session-groups. This group named grp1 belongs to the set named set1.
The Status will be either Group-OutOfService (no session in the group has been established) or Group-Inservice (at least one session in the group has been established).
The Status(use) will be either Group-Standby (the VSC connected to the other end of this group will go into standby mode), Group-Active (the VSC connected to the other end of this group will be the active VSC), or Group-None (the VSC has not declared its intent yet).
Router# show backhaul-session-manager group status allSession-GroupGroup Name :grp1Set Name :set1Status :Group-OutOfServiceStatus (use) :Group-NoneRelated Commands
show backhaul-session-manager session
To display various information for about a session or sessions, use the show backhaul-session-manager session command in privileged EXEC mode.
show backhaul-session-manager session { all | ip ip_address }
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
To display information for all available sessions, see the following example.
The State will be OPEN (the connection is established), OPEN_WAIT (the connection is awaiting establishment), OPEN_XFER (session failover is in progress for this session, which is a transient state), or CLOSE (this session is down, also a transient state). The session will move to OPEN_WAIT after waiting a fixed amount of time.
The Use-status field indicates whether PRI signaling traffic is currently being transported over this session . The field will be either OOS (this session is not being used to transport signaling traffic) or IS (this session is being used currently to transport all PRI signaling traffic). OOS does not indicate if the connection is established and IS indicates that the connection is established.
Router# show backhaul-session-manager session allSession information --Session-id:35Group:grp1 /*this session belongs to the group named 'grp1' */Configuration:Local:10.1.2.15 , port:8303Remote:10.5.0.3 , port:8303Priority:2RUDP Option:Client, Conn Id:0x2State:Status:OPEN_WAIT, Use-status:OOS, /*see explanation below */Statistics:# of resets:0# of auto_resets 0# of unexpected RUDP transitions (total) 0# of unexpected RUDP transitions (since last reset) 0Receive pkts - Total:0 , Since Last Reset:0Recieve failures - Total:0 ,Since Last Reset:0Transmit pkts - Total:0, Since Last Reset:0Transmit Failures (PDU Only)Due to Blocking (Not an Error) - Total:0, Since Last Reset:0Due to causes other than Blocking - Total:0, Since LastReset:0Transmit Failures (NON-PDU Only)Due to Blocking(Not an Error) - Total:0, Since Last Reset:0Due to causes other than Blocking - Total:0, Since LastReset:0RUDP statisticsOpen failures:0Not ready failures:0Conn Not Open failures:0Send window full failures:0Resource unavailble failures:0Enqueue failures:0Related Commands
show backhaul-session-manager set
To display session-groups associated with a specified session-set or all session-sets, use the show backhaul-session-manager set command in privileged EXEC mode.
show backhaul-session-manager set { all | name session-set-name }
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
To show session groups associated with all session-sets, see the following example:
Router# show backhaul-session-manager set allRelated Commands
show call active
To display active call information for voice calls or fax transmissions in progress, use the show call active command in user EXEC or privileged EXEC mode.
show call active {voice | fax}[brief]
Syntax Description
Defaults
No default behavior or values.
Command Modes
User EXEC or
Privileged EXECCommand History
Usage Guidelines
Use the show call active command to display the contents of the active call table. This command displays information about call times, dial peers, connections, quality of service, and other status and statistical information. If you use the voice keyword, information is displayed about all voice calls currently connected through the router or access server. If you use the fax keyword, information is displayed about all fax calls currently connected.
This command applies to both on-ramp and off-ramp store-and-forward fax functions.
See Table 19 for a listing of the information types associated with this command.
Examples
The following is sample output from the show call active voice command:
Router# show call active voiceGENERIC:SetupTime=104443 msIndex=1PeerAddress=50110PeerSubAddress=PeerId=100PeerIfIndex=104LogicalIfIndex=10ConnectTime=104964CallDuration=00:02:43CallState=4CallOrigin=2ChargedUnits=0InfoType=2TransmitPackets=15720TransmitBytes=2362904ReceivePackets=15670ReceiveBytes=2737904TELE:ConnectionId=[0x4B091A27 0x3EDD0003 0x0 0xFEFD4]TxDuration=155310 msVoiceTxDuration=155310 msFaxTxDuration=0 msCoderTypeRate=g711ulawNoiseLevel=-75ACOMLevel=11OutSignalLevel=-13InSignalLevel=-22InfoActivity=2ERLLevel=27SessionTarget=ImgPages=0GENERIC:SetupTime=104648 msIndex=1PeerAddress=55240PeerSubAddress=PeerId=2PeerIfIndex=105LogicalIfIndex=0ConnectTime=104964CallDuration=00:02:47CallState=4CallOrigin=1ChargedUnits=0InfoType=2TransmitPackets=16026TransmitBytes=2608248ReceivePackets=16075ReceiveBytes=2609164VOIP:ConnectionId[0x4B091A27 0x3EDD0003 0x0 0xFEFD4]RemoteIPAddress=1.14.82.14RemoteUDPPort=18202RoundTripDelay=2 msSelectedQoS=best-efforttx_DtmfRelay=inband-voiceFastConnect=TRUESessionProtocol=ciscoSessionTarget=ipv4:1.14.82.14OnTimeRvPlayout=40GapFillWithSilence=0 msGapFillWithPrediction=0 msGapFillWithInterpolation=0 msGapFillWithRedundancy=0 msHiWaterPlayoutDelay=67 msLoWaterPlayoutDelay=67 msReceiveDelay=67 msLostPackets=0 msEarlyPackets=0 msLatePackets=0 msVAD = enabledCoderTypeRate=g729r8CodecBytes=20SignalingType=casModem passthrough signaling method is nse:Buffer Fill Events = 0Buffer Drain Events = 0Percent Packet Loss = 0Consecutive-packets-lost Events = 0Corrected packet-loss Events = 0Last Buffer Drain/Fill Event = 157secTime between Buffer Drain/Fills = Min 0sec Max 0secThe following is sample output from the show call active voice brief command:
Router# show call active voice brief<ID>: <start>hs.<index> +<connect> pid:<peer_id> <dir> <addr> <state>dur hh:mm:ss tx:<packets>/<bytes> rx:<packets>/<bytes>IP <ip>:<udp> rtt:<time>ms pl:<play>/<gap>ms lost:<lost>/<early>/<late>delay:<last>/<min>/<max>ms <codec>MODEMPASS <method> buf:<fills>/<drains> loss <overall%> <multipkt>/<corrected>last <buf event time>s dur:<Min>/<Max>sFR <protocol> [int dlci cid] vad:<y/n> dtmf:<y/n> seq:<y/n>sig:<on/off> <codec> (payload size)ATM <protocol> [int vpi/vci cid] vad:<y/n> dtmf:<y/n> seq:<y/n>sig:<on/off> <codec> (payload size)Tele <int>: tx:<tot>/<v>/<fax>ms <codec> noise:<l> acom:<l> i/o:<l>/<l> dBm3 : 104443hs.1 +521 pid:100 Answer 50110 activedur 00:03:28 tx:20151/3036404 rx:20102/3517936Tele 0:D:1: tx:199630/199630/0ms g711ulaw noise:-75 acom:11 i/0:-22/-13 dBm3 : 104648hs.1 +316 pid:2 Originate 55240 activedur 00:03:28 tx:20102/3276712 rx:20151/3277628IP 1.14.82.14:18202 rtt:3ms pl:40/0ms lost:0/0/0 delay:67/67/67ms g729r8MODEMPASS nse buf:0/0 loss 0% 0/0 last 195s dur:0/0sThe following is sample output from the show call active fax command:
Router# show call active faxGENERIC:SetupTime=22021 msIndex=1PeerAddress=wook songPeerSubAddress=PeerId=0PeerIfIndex=0LogicalIfIndex=0ConnectTime=24284CallState=4CallOrigin=2ChargedUnits=0InfoType=10TransmitPackets=0TransmitBytes=0ReceivePackets=0ReceiveBytes=41190MMOIP:ConnectionId[0x37EC7F41 0xB0110001 0x0 0x35C34]RemoteIPAddress=0.0.0.0SessionProtocol=SMTPSessionTarget=MessageId=AccountId=ImgEncodingType=MHImgResolution=fineAcceptedMimeTypes=2DiscardedMimeTypes=1Notification=NoneGENERIC:SetupTime=23193 msIndex=1PeerAddress=527....PeerSubAddress=PeerId=3469PeerIfIndex=157LogicalIfIndex=30ConnectTime=24284CallState=4CallOrigin=1ChargedUnits=0InfoType=10TransmitPackets=5TransmitBytes=6513ReceivePackets=0ReceiveBytes=0TELE:ConnectionId=[0x37EC7F41 0xB0110001 0x0 0x35C34]TxDuration=24010 msFaxTxDuration=10910 msFaxRate=14400NoiseLevel=-1ACOMLevel=-1OutSignalLevel=0InSignalLevel=0InfoActivity=0ERLLevel=-1SessionTarget=ImgPages=0The following is sample output from the show call active fax brief command:
Router# show call active fax brief<ID>: <start>hs.<index> +<connect> pid:<peer_id> <dir> <addr> <state> \tx:<packets>/<bytes> rx:<packets>/<bytes> <state>IP <ip>:<udp> rtt:<time>ms pl:<play>/<gap>ms lost:<lost>/<early>/<late>delay:<last>/<min>/<max>ms <codec>FR <protocol> [int dlci cid] vad:<y/n> dtmf:<y/n> seq:<y/n>sig:<on/off> <codec> (payload size)Tele <int>: tx:<tot>/<v>/<fax>ms <codec> noise:<l> acom:<l> i/o:<l>/<l> dBm1 : 22021hs.1 +2263 pid:0 Answer wook song activetx:0/0 rx:0/41190IP 0.0.0.0 AcceptedMime:2 DiscardedMime:11 : 23193hs.1 +1091 pid:3469 Originate 527.... activetx:10/13838 rx:0/0Tele : tx:31200/10910/20290ms noise:-1 acom:-1 i/0:0/0 dBmTable 27 provides an alphabetical listing of the fields displayed in the output from the show call active command and a description of each field.
Related Commands
show call application voice
To define the names of the audio files that the interactive voice response (IVR) script will play, the operation of the abort keys, the prompts that are used, and caller interaction, use the show call application voice command in EXEC mode.
show call application voice [name | summary]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
11.3(6)NA2
This command was introduced on the Cisco 2500 series and Cisco 3600 series routers and the Cisco AS5300 universal access server.
Usage Guidelines
If the name of a specific application is entered, it will give information about that application.
If the summary keyword is entered, a one-line summary will be displayed about each application.
If the command is entered without the summary, a detailed description of the entered IVR application is displayed.
Examples
This example shows the output for the clid_authen_collect IVR script:
Router# show call application voice clid_authen_collectApplication clid_authen_collect has 10 states with 0 calls activeState start has 1 actions and 5 eventsDo Action IVR_ACT_AUTHENTICATE. accountName=ani, pinName=dnisIf Event IVR_EV_DEFAULT goto state endIf Event IVR_EV_CALL_DIGIT do nothingIf Event IVR_EV_CALL_SETUP_IND do action IVR_ACT_CALL_SETUP_ACKand goto state startIf Event IVR_EV_AAA_SUCCESS goto state collect_destIf Event IVR_EV_AAA_FAIL goto state get_accountState end has 1 actions and 3 eventsDo Action IVR_ACT_END.If Event IVR_EV_DEFAULT goto state endIf Event IVR_EV_CALL_DIGIT do nothingIf Event IVR_EV_CALL_DISCONNECT_DONE do action IVR_ACT_CALL_DESTROYand do nothingState get_account has 4 actions and 7 eventsDo Action IVR_ACT_PLAY.URL: flash:enter_account.auallowInt=1, pContent=0x60E4C564Do 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 endIf Event IVR_EV_CALL_DIGIT do nothingIf Event IVR_EV_PAT_COL_SUCCESS goto state get_pinpatName=accountIf Event IVR_EV_ABORT goto state get_accountIf Event IVR_EV_PLAY_COMPLETE do nothingIf Event IVR_EV_TIMEOUT goto state get_account count=0If Event IVR_EV_PAT_COL_FAIL goto state get_accountState get_pin has 4 actions and 7 eventsDo Action IVR_ACT_PLAY.URL: flash:enter_pin.auallowInt=1, pContent=0x0Do 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 endIf Event IVR_EV_CALL_DIGIT do nothingIf Event IVR_EV_PAT_COL_SUCCESS goto state authenticatepatName=pinIf Event IVR_EV_PLAY_COMPLETE do nothingIf Event IVR_EV_ABORT goto state get_accountIf Event IVR_EV_TIMEOUT goto state get_pin count=0If Event IVR_EV_PAT_COL_FAIL goto state get_pinState authenticate has 1 actions and 5 eventsDo Action IVR_ACT_AUTHENTICATE. accountName=account, pinName=pinIf Event IVR_EV_DEFAULT goto state endIf Event IVR_EV_CALL_DIGIT do nothingIf Event IVR_EV_AAA_SUCCESS goto state collect_destIf Event IVR_EV_TIMEOUT do nothing count=0If Event IVR_EV_AAA_FAIL goto state authenticate_failState collect_dest has 4 actions and 8 eventsDo Action IVR_ACT_PLAY.URL: flash:enter_destination.auallowInt=1, pContent=0x0Do 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 endIf Event IVR_EV_CALL_DIGIT do nothingIf Event IVR_EV_PLAY_COMPLETE do nothingIf Event IVR_EV_ABORT goto state collect_destIf Event IVR_EV_TIMEOUT goto state collect_dest count=0If Event IVR_EV_DIAL_COL_SUCCESS goto state place_callIf Event IVR_EV_DIAL_COL_FAIL goto state collect_destIf Event IVR_EV_TIMEOUT goto state collect_dest count=0State place_call has 1 actions and 4 eventsDo Action IVR_ACT_PLACE_CALL.destination= called=calling= account=If Event IVR_EV_DEFAULT goto state endIf Event IVR_EV_CALL_DIGIT do nothingIf Event IVR_EV_CALL_UP goto state activeIf Event IVR_EV_CALL_FAIL goto state place_failState active has 0 actions and 2 eventsIf Event IVR_EV_DEFAULT goto state endIf Event IVR_EV_CALL_DIGIT do nothingState authenticate_fail has 1 actions and 2 eventsDo Action IVR_ACT_PLAY.URL: flash:auth_failed.auallowInt=0, pContent=0x0If Event IVR_EV_DEFAULT goto state endIf Event IVR_EV_CALL_DIGIT do nothingState place_fail has 1 actions and 2 eventsDo Action IVR_ACT_PLAY_FAILURE_TONE.If Event IVR_EV_DEFAULT goto state endIf Event IVR_EV_CALL_DIGIT do nothingRouter# show call application voice clid_authen_collectApplication clid_authen_collect has 10 states with 0 calls activeState start has 1 actions and 5 eventsDo Action IVR_ACT_AUTHENTICATE. accountName=ani, pinName=dnisIf Event IVR_EV_DEFAULT goto state endIf Event IVR_EV_CALL_DIGIT do nothingIf Event IVR_EV_CALL_SETUP_IND do action IVR_ACT_CALL_SETUP_ACKand goto state startIf Event IVR_EV_AAA_SUCCESS goto state collect_destIf Event IVR_EV_AAA_FAIL goto state get_accountState end has 1 actions and 3 eventsDo Action IVR_ACT_END.If Event IVR_EV_DEFAULT goto state endIf Event IVR_EV_CALL_DIGIT do nothingIf Event IVR_EV_CALL_DISCONNECT_DONE do action IVR_ACT_CALL_DESTROYand do nothingState get_account has 4 actions and 7 eventsDo Action IVR_ACT_PLAY.URL: flash:enter_account.auallowInt=1, pContent=0x60E4C564Do 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 endIf Event IVR_EV_CALL_DIGIT do nothingIf Event IVR_EV_PAT_COL_SUCCESS goto state get_pinpatName=accountIf Event IVR_EV_ABORT goto state get_accountIf Event IVR_EV_PLAY_COMPLETE do nothingIf Event IVR_EV_TIMEOUT goto state get_account count=0If Event IVR_EV_PAT_COL_FAIL goto state get_accountState get_pin has 4 actions and 7 eventsDo Action IVR_ACT_PLAY.URL: flash:enter_pin.auallowInt=1, pContent=0x0Do 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 endIf Event IVR_EV_CALL_DIGIT do nothingIf Event IVR_EV_PAT_COL_SUCCESS goto state authenticatepatName=pinIf Event IVR_EV_PLAY_COMPLETE do nothingIf Event IVR_EV_ABORT goto state get_accountIf Event IVR_EV_TIMEOUT goto state get_pin count=0If Event IVR_EV_PAT_COL_FAIL goto state get_pinState authenticate has 1 actions and 5 eventsDo Action IVR_ACT_AUTHENTICATE. accountName=account, pinName=pinIf Event IVR_EV_DEFAULT goto state endIf Event IVR_EV_CALL_DIGIT do nothingIf Event IVR_EV_AAA_SUCCESS goto state collect_destIf Event IVR_EV_TIMEOUT do nothing count=0If Event IVR_EV_AAA_FAIL goto state authenticate_failState collect_dest has 4 actions and 8 eventsDo Action IVR_ACT_PLAY.URL: flash:enter_destination.auallowInt=1, pContent=0x0Do 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 endIf Event IVR_EV_CALL_DIGIT do nothingIf Event IVR_EV_PLAY_COMPLETE do nothingIf Event IVR_EV_ABORT goto state collect_destIf Event IVR_EV_TIMEOUT goto state collect_dest count=0If Event IVR_EV_DIAL_COL_SUCCESS goto state place_callIf Event IVR_EV_DIAL_COL_FAIL goto state collect_destIf Event IVR_EV_TIMEOUT goto state collect_dest count=0State place_call has 1 actions and 4 eventsDo Action IVR_ACT_PLACE_CALL.destination= called=calling= account=If Event IVR_EV_DEFAULT goto state endIf Event IVR_EV_CALL_DIGIT do nothingIf Event IVR_EV_CALL_UP goto state activeIf Event IVR_EV_CALL_FAIL goto state place_failState active has 0 actions and 2 eventsIf Event IVR_EV_DEFAULT goto state endIf Event IVR_EV_CALL_DIGIT do nothingState authenticate_fail has 1 actions and 2 eventsDo Action IVR_ACT_PLAY.URL: flash:auth_failed.auallowInt=0, pContent=0x0If Event IVR_EV_DEFAULT goto state endIf Event IVR_EV_CALL_DIGIT do nothingState place_fail has 1 actions and 2 eventsDo Action IVR_ACT_PLAY_FAILURE_TONE.If Event IVR_EV_DEFAULT goto state endIf Event IVR_EV_CALL_DIGIT do nothingRelated Commands
show call fallback cache
To see the current Calculated Planning Impairment Factor (ICPIF) estimates for all IP addresses in cache, use the show call fallback cache command in EXEC mode.
show call fallback cache [ip-address]
Syntax Description
Defaults
This command is not configured by default.
Command Modes
EXEC
Command History
12.1(3)T
This command was introduced on the Cisco 2600 series and Cisco 3600 series routers and on the Cisco MC3810 multiservice concentrator.
Usage Guidelines
To clear all entries in the cache, use the clear call fallback cache command.
Examples
The following example displays output from the show call fallback cache command:
Router# show call fallback cacheProbe IP Address Codec Delay Loss ICPIF Reject Accept----- ---------- ----- ----- ---- ----- ------ ------1 1.1.1.4 g729r8 40 0 0 0 92 122.24.56.25 g729r8 148 10 5 1 42 active probesField Description------- ------------Probe Probe numberIP Address IP Address to which the probe is sentCodec Codec Type of the probeDelay Delay in milliseconds that the probe incurredLoss Loss in % that the probe incurredICPIF Computed ICPIF value for the probeReject Number of times that calls of Codec Type <Codec>were rejected to the IP AddressAccept Number of times that calls of Codec Type <Codec>were accepted to the IP Addressactive probes Number of destinations being probedRouter# show call fallback cache 10.14.115.53Probe IP Address Codec ICPIF Reject Accept----- ---------- ----- ----- ------ ------1 10.14.115.53 g729r8 0 0 21 active probesRelated Commands
show call fallback config
To display the call fallback configuration, use the show call fallback config command in EXEC mode.
show call fallback config
Syntax Description
This command has no arguments or keywords.
Defaults
This command is not configured by default.
Command Modes
EXEC
Command History
12.1(3)T
This command was introduced on the Cisco 2600 series and Cisco 3600 series routers and on the Cisco MC3810 multiservice concentrator.
Examples
The following example displays output from the show call fallback config command:
Router# show call fallback configVoIP fallback config:Fallback is ONUsing ICPIF threshold:ICPIF value timeout:20 secondsICPIF threshold:20Number of packets in a probe:20IP precedence of probe packets:2Fallback cache size:2 entriesFallback cache timeout:240 secondsInstantaneous value weight:65MD5 Keychain:secretRelated Commands
show call fallback stats
To display the call fallback statistics, use the show call fallback stats command in EXEC mode.
show call fallback stats
Syntax Description
This command has no arguments or keywords.
Defaults
This command is not configured by default.
Command Modes
EXEC
Command History
12.1(3)T
This command was introduced on the Cisco 2600 series and Cisco 3600 series routers and on the Cisco MC3810 multiservice concentrator.
Usage Guidelines
To remove all values, use the clear call fallback stats command.
Examples
The following example displays output from the show call fallback stats command:
Router# show call fallback statsVOIP Fallback Stats:Total accepted calls:3Total rejected calls:1Total cache overflows:1Field Description------- ------------Total accepted calls Number of times that calls were successful over IP.Total rejected calls Number of times that calls were rejected over IP.Total cache overflows Number of times that the fallback cache overflowed and requied pruning.Related Commands
clear call fallback stats
Clears the call fallback statistics.
show call fallback cache
Displays the current ICPIF estimates for all IP addresses in the cache.
show call history
To display the call history table for voice calls or fax transmissions, use the show call history command in user EXEC or privileged EXEC mode.
show call history {voice | fax}[last number | brief]
Syntax Description
Defaults
No default behavior or values.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The show call history command displays a call history table containing a list of voice or fax calls connected through the router in descending time order. The maximum number of calls contained in the table can be set to a number between 0 and 500 using the dial-control-mib command in global configuration mode. The default maximum number of table entries is 50. Each call record is aged out of the table after a configurable number of minutes has elapsed, also specified by the dial-control-mib command. The default timer value is 15 minutes.
You can display subsets of the call history table by using specific keywords. To display the last calls connected through this router, use the keyword last, and define the number of calls to be displayed with the number argument.
To display a truncated version of the call history table, use the brief keyword.
When using the fax keyword, this command applies to both on-ramp and off-ramp store-and-forward fax functions.
Examples
The following is sample output from the show call history voice command:
Router# show call history voiceGENERIC:SetupTime=104648 msIndex=1PeerAddress=55240PeerSubAddress=PeerId=2PeerIfIndex=105LogicalIfIndex=0DisconnectCause=10DisconnectText=normal call clearing.ConnectTime=104964DisconectTime=143329CallDuration=00:06:23CallOrigin=1ChargedUnits=0InfoType=speechTransmitPackets=37668TransmitBytes=6157536ReceivePackets=37717ReceiveBytes=6158452VOIP:ConnectionId[0x4B091A27 0x3EDD0003 0x0 0xFEFD4]RemoteIPAddress=1.14.82.14RemoteUDPPort=18202RoundTripDelay=2 msSelectedQoS=best-efforttx_DtmfRelay=inband-voiceFastConnect=TRUESessionProtocol=ciscoSessionTarget=ipv4:1.14.82.14OnTimeRvPlayout=40GapFillWithSilence=0 msGapFillWithPrediction=0 msGapFillWithInterpolation=0 msGapFillWithRedundancy=0 msHiWaterPlayoutDelay=67 msLoWaterPlayoutDelay=67 msReceiveDelay=67 msLostPackets=0 msEarlyPackets=0 msLatePackets=0 msVAD = enabledCoderTypeRate=g729r8CodecBytes=20cvVoIPCallHistoryIcpif=0SignalingType=casModem passthrough signaling method is nseBuffer Fill Events = 0Buffer Drain Events = 0Percent Packet Loss = 0Consecutive-packets-lost Events = 0Corrected packet-loss Events = 0Last Buffer Drain/Fill Event = 373secTime between Buffer Drain/Fills = Min 0sec Max 0secGENERIC:SetupTime=104443 msIndex=2PeerAddress=50110PeerSubAddress=PeerId=100PeerIfIndex=104LogicalIfIndex=10DisconnectCause=10DisconnectText=normal call clearing.ConnectTime=104964DisconectTime=143330CallDuration=00:06:23CallOrigin=2ChargedUnits=0InfoType=speechTransmitPackets=37717TransmitBytes=5706436ReceivePackets=37668ReceiveBytes=6609552TELE:ConnectionId=[0x4B091A27 0x3EDD0003 0x0 0xFEFD4]TxDuration=375300 msVoiceTxDuration=375300 msFaxTxDuration=0 msCoderTypeRate=g711ulawNoiseLevel=-75ACOMLevel=11SessionTarget=ImgPages=0The following is sample output from the show call history voice brief command:
Router# show call history voice brief<ID>: <start>hs.<index> +<connect> +<disc> pid:<peer_id> <direction> <addr>dur hh:mm:ss tx:<packets>/<bytes> rx:<packets>/<bytes> <disc-cause>(<text>)IP <ip>:<udp> rtt:<time>ms pl:<play>/<gap>ms lost:<lost>/<early>/<late>delay:<last>/<min>/<max>ms <codec>MODEMPASS <method> buf:<fills>/<drains> loss <overall%> <multipkt>/<corrected>last <buf event time>s dur:<Min>/<Max>sFR <protocol> [int dlci cid] vad:<y/n> dtmf:<y/n> seq:<y/n>sig:<on/off> <codec> (payload size)ATM <protocol> [int vpi/vci cid] vad:<y/n> dtmf:<y/n> seq:<y/n>sig:<on/off> <codec> (payload size)Telephony <int>: tx:<tot>/<voice>/<fax>ms <codec> noise:<lvl>dBm acom:<lvl>dBmThe following is sample output from the show call history fax command:
Router# show call history faxGENERIC:SetupTime=23193 msIndex=1PeerAddress=527....PeerSubAddress=PeerId=3469PeerIfIndex=157LogicalIfIndex=30DisconnectCause=10DisconnectText=normal call clearing.: Normal connectionConnectTime=24284DisconectTime=31288CallOrigin=1ChargedUnits=0InfoType=faxTransmitPackets=62TransmitBytes=88047ReceivePackets=0ReceiveBytes=0TELE:ConnectionId=[0x37EC7F41 0xB0110001 0x0 0x35C34]TxDuration=80950 msFaxTxDuration=10910 msFaxRate=14400NoiseLevel=-1ACOMLevel=-1SessionTarget=ImgPages=3GENERIC:SetupTime=22021 msIndex=2PeerAddress=wook songPeerSubAddress=PeerId=0PeerIfIndex=0LogicalIfIndex=0DisconnectCause=10DisconnectText=normal call clearing.ConnectTime=24284DisconectTime=31545CallOrigin=2ChargedUnits=0InfoType=faxTransmitPackets=0TransmitBytes=0ReceivePackets=0ReceiveBytes=41190MMOIP:ConnectionId[0x37EC7F41 0xB0110001 0x0 0x35C34]RemoteIPAddress=0.0.0.0SessionProtocol=SMTPSessionTarget=MessageId=AccountId=ImgEncodingType=MHImgResolution=fineAcceptedMimeTypes=2DiscardedMimeTypes=1Notification=NoneThe following is sample output from the show call history fax brief command:
Router# show call history fax brief<ID>: <start>hs.<index> +<connect> +<disc> pid:<peer_id> <direction> <addr>tx:<packets>/<bytes> rx:<packets>/<bytes> <disc-cause>(<text>)IP <ip>:<udp> rtt:<time>ms pl:<play>/<gap>ms lost:<lost>/<early>/<late>delay:<last>/<min>/<max>ms <codec>Telephony <int>: tx:<tot>/<voice>/<fax>ms <codec> noise:<lvl>dBm acom:<lvl>dBm2 : 5996450hs.25 +-1 +3802 pid:100 Answer 408tx:0/0 rx:0/0 1F (T30 T1 EOM timeout)Telephony : tx:38020/38020/0ms g729r8 noise:0dBm acom:0dBm2 : 5996752hs.26 +-1 +3500 pid:110 Originate uut1@linux2.allegro.comtx:0/0 rx:0/0 3F (The e-mail was not sent correctly. Remote SMTP server said: 354 )IP 14.0.0.1 AcceptedMime:0 DiscardedMime:03 : 6447851hs.27 +1111 +3616 pid:310 Originate 576341.tx:11/14419 rx:0/0 10 (Normal connection)Telephony : tx:36160/11110/25050ms g729r8 noise:115dBm acom:-14dBm3 : 6447780hs.28 +1182 +4516 pid:0 Answertx:0/0 rx:0/0 10 (normal call clearing.)IP 0.0.0.0 AcceptedMime:0 DiscardedMime:04 : 6464816hs.29 +1050 +3555 pid:310 Originate 576341.tx:11/14413 rx:0/0 10 (Normal connection)Telephony : tx:35550/10500/25050ms g729r8 noise:115dBm acom:-14dBm4 : 6464748hs.30 +1118 +4517 pid:0 Answertx:0/0 rx:0/0 10 (normal call clearing.)IP 0.0.0.0 AcceptedMime:0 DiscardedMime:05 : 6507900hs.31 +1158 +2392 pid:100 Answer 4085763413tx:0/0 rx:3/3224 10 (Normal connection)Telephony : tx:23920/11580/12340ms g729r8 noise:0dBm acom:0dBm5 : 6508152hs.32 +1727 +2140 pid:110 Originate uut1@linux2.allegro.comtx:0/2754 rx:0/0 3F (service or option not available, unspecified)IP 14.0.0.4 AcceptedMime:0 DiscardedMime:06 : 6517176hs.33 +1079 +3571 pid:310 Originate 576341.tx:11/14447 rx:0/0 10 (Normal connection)Telephony : tx:35710/10790/24920ms g729r8 noise:115dBm acom:-14dBm6 : 6517106hs.34 +1149 +4517 pid:0 Answertx:0/0 rx:0/0 10 (normal call clearing.)IP 0.0.0.0 AcceptedMime:0 DiscardedMime:07 : 6567382hs.35 +1054 +3550 pid:310 Originate 576341.tx:11/14411 rx:0/0 10 (Normal connection)Telephony : tx:35500/10540/24960ms g729r8 noise:115dBm acom:-14dBm7 : 6567308hs.36 +1128 +4517 pid:0 Answertx:0/0 rx:0/0 10 (normal call clearing.)IP 0.0.0.0 AcceptedMime:0 DiscardedMime:0Table 28 provides an alphabetical listing of the fields displayed in the output from the show call history command and a description of each field.
Related Commands
show call history video record
To display information about video calls, use the show call history video record command in privileged EXEC mode.
show call history video record
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to review statistics about recent incoming and outgoing video calls.
Examples
On a Cisco MC3810 multiservice concentrator, the following example displays information about two video calls:
Router# show call history video recordCallId = 4CalledNumber = 221CallDuration = 39006 secondsDisconnectText = remote hangupSVC: call ID = 8598630Remote NSAP = 47.0091810000000002F26D4901.00107B09C645.C8Local NSAP = 47.0091810000000002F26D4901.00107B4832E1.C8vcd = 414, vpi = 0, vci = 158SerialPort = Serial0VideoSlot = 1, VideoPort = 0CallId = 3CalledNumber = 221CallDuration = 557 secondsDisconnectText = local hangupSVC: call ID = 8598581Remote NSAP = 47.0091810000000002F26D4901.00107B09C645.C8Local NSAP = 47.0091810000000002F26D4901.00107B4832E1.C8vcd = 364, vpi = 0, vci = 108SerialPort = Serial0VideoSlot = 1, VideoPort = 0show call history voice record
To display Call Detail Record (CDR) events in the call history table, use the show call history voice record command in privileged EXEC mode.
show call history voice record
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example displays a sample of voice call history records showing a local call between two telephones attached to the same Cisco MC3810 multiservice concentrator:
Router# show call history voice recordConnectionId=[0x2C7AEFDC 0x59830001 0x0 0xB0AAA3]Media=TELE, TxDuration= 1418 msCallingNumber=2001SetupTime=1157801 x 10msConnectTime=1158046 x 10msDisconectTime=1158188 x 10msDisconnectText=local onhookConnectionId=[0x2C7AEFDC 0x59830001 0x0 0xB0AAA3]Media=TELE, TxDuration= 1422 msCalledNumber=2002SetupTime=1157802 x 10msConnectTime=1158046 x 10msDisconectTime=1158188 x 10msDisconnectText=remote onhookTable 29 describes the significant fields shown in the display.
Related Commands
show call resource voice stats
To display resource statistics for an H.323 gateway, use the show call resource voice stats command in privileged EXEC mode.
show call resource voice stats
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(5)T
This command was introduced on the Cisco AS5300 universal access server.
Usage Guidelines
This command displays the H.323 resources that are monitored when the resource threshold command is used to configure and enable resource threshold reporting.
Examples
The following example shows the resource statistics for an H.323 gateway:
Router# show call resource voice statsResource Monitor - Dial-up Resource Statistics Information:DSP Statistics:Utilization: 0 percentTotal channels: 48Inuse channels: 0Disabled channels 0:Pending channels: 0Free channels: 48DS0 Statistics:Total channels: 0Addressable channels: 0Inuse channels: 0Disabled channels: 0Free channels: 0Table 30 describes the significant fields shown in the display.
Related Commands
show call resource voice threshold
To display the threshold configuration settings and status for an H.323 gateway, use the show call resource voice threshold command in privileged EXEC mode.
show call resource voice threshold
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(5)T
This command was introduced on the Cisco AS5300 univeral access server.
Usage Guidelines
This command displays the H.323 resource thresholds that are configured with the resource threshold command.
Examples
The following example shows the resource threshold settings and status for an H.323 gateway:
Router# show call resource voice thresholdResource Monitor - Dial-up Resource Threshold Information:DS0 Threshold:Client Type: h323High Water Mark: 70Low Water Mark: 60Threshold State: initDSP Threshold:Client Type: h323High Water Mark: 70Low Water Mark: 60Threshold State: low_threshold_hitRelated Commands
show call rsvp-sync conf
To display the configuration settings for Resource Reservation Protocol (RSVP) synchronization, use the show call rsvp-sync conf command in privileged EXEC mode.
show call rsvp-sync conf
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows sample output from the show call rsvp-sync conf command:
Router# show call rsvp-sync confVoIP QoS: RSVP/Voice Signaling Synchronization config:Overture Synchronization is ONReservation Timer is set to 10 secondsTable 31 describes the significant fields shown in the display
Related Commands
show call rsvp-sync stats
To display statistics for calls that attempted Resource Reservation Protocol (RSVP) reservation, use the show call rsvp-sync stats command in privileged EXEC mode.
show call rsvp-sync stats
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.1(3)XI1
This command was introduced.
12.1(5)T
This command was integrated into
Cisco IOS Release 12.1(5)T.
Examples
The following example shows sample output from the show call rsvp-sync stats command:
Router# show call rsvp-sync statsVoIP QoS:Statistics Information:Number of calls for which QoS was initiated : 18478Number of calls for which QoS was torn down : 18478Number of calls for which Reservation Success was notified : 0Total Number of PATH Errors encountered : 0Total Number of RESV Errors encountered : 0Total Number of Reservation Timeouts encountered : 0Table 32 describes the significant fields shown in the display.
Related Commands
show cdapi
To display the Call Distributor Application Programming Interface (CDAPI), use the show cdapi command in privileged EXEC mode.
show cdapi
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(7)T
This command was introduced on the Cisco AS5300 universal access server.
Usage Guidelines
CDAPI is the internal application programming interface (API) that provides an interface between signaling stacks and applications.
Examples
The following is output for the show cdapi command:
Router# show cdapiRegistered CDAPI Applications/Stacks====================================Application TSP CDAPI ApplicationApplication Type(s) Voice Facility SignalingApplication Level TunnelApplication Mode EnblocSignaling Stack ISDNInterface Se023Signaling Stack ISDNInterface Se123Active CDAPI Calls==================Interface Se023No active calls.Interface Se123Call ID = 0x39, Call Type = VOICE, Application = TSP CDAPI ApplicationCDAPI Message Buffers=====================Used Msg Buffers 0, Free Msg Buffers 1600Used Raw Buffers 1, Free Raw Buffers 799Used Large-Raw Buffers 0, Free Large-Raw Buffers 80scarlatti1#Related Commands
show ces clock-select
To display the setting of the network clock for the specified port, use the show ces clock-select command in privileged EXEC mode.
show ces slot/port clock-select
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show ces clock-select command for slot 1, port 0:
Router# show ces 1/0 clock-selectPriority 1 clock source:not configuredPriority 2 clock source:not configuredPriority 3 clock source:ATM1/0 UPPriority 4 clock source:Local oscillatorCurrent clock source:ATM1/0, priority:3Related Commands
clock-select
Establishes the sources and priorities of the requisite clocking signals for the OC-3/STM-1 ATM Circuit Emulation Service network module.
show connect
To display configuration information about drop-and-insert connections that have been configured on a router, enter the show connect command in privileged EXEC mode.
show connect {all | elements | name | id | port {T1 | E1} slot/port}}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command shows drop-and-insert connections on the Cisco 2600 and 3600 series.
The command displays different information in different formats, depending on the keyword that you use.
Examples
The following examples show how the same tabular information appears when you enter different keywords:
Router# show connect allID Name Segment 1 Segment 2 State========================================================================1 Test -T1 1/0 01 -T1 1/1 02 ADMIN UP2 Test2 -T1 1/0 03 -T1 1/1 04 ADMIN UPRouter# show connect id 1-2ID Name Segment 1 Segment 2 State========================================================================1 Test -T1 1/0 01 -T1 1/1 02 ADMIN UP2 Test2 -T1 1/0 03 -T1 1/1 04 ADMIN UPRouter# show connect port t1 1/1ID Name Segment 1 Segment 2 State========================================================================1 Test -T1 1/0 01 -T1 1/1 02 ADMIN UP2 Test2 -T1 1/0 03 -T1 1/1 04 ADMIN UPThe following examples show details about specific connections, including the number of time slots in use and the switching elements:
Router# show connect id 2Connection: 2 - Test2Current State: ADMIN UPSegment 1: -T1 1/0 03TDM timeslots in use: 14-18 (5 total)Segment 2: -T1 1/1 04TDM timeslots in use: 14-18Internal Switching Elements: VIC TDM SwitchRouter# show connect name TestConnection: 1 - TestCurrent State: ADMIN UPSegment 1: -T1 1/0 01TDM timeslots in use: 1-13 (13 total)Segment 2: -T1 1/1 02TDM timeslots in use: 1-13Internal Switching Elements: VIC TDM SwitchRelated Commands
show controllers rs366
To display information about the RS-366 video interface on the video dialing module (VDM), use the show controllers rs366 command in privileged EXEC mode.
show controllers rs366 slot port
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
On a Cisco MC3810 multiservice concentrator, the following example displays information about the RS-366 controller:
Router# show controller rs366 0 1RS366:driver is initialized in slot 1, port 0:STATUS STATE LSR LCR ICSR EXT T1 T2 T3 T4 T50x02 0x01 0x00 0x50 0xE0 0x00 5000 5000 5000 20000 10000Dial string:121CTable 33 describes the significant fields shown in the display.
show controllers timeslots
To show the channel-associated signaling (CAS) and ISDN PRI state in detail, use the show controllers timeslots command in privileged EXEC mode.
show controllers t1/e1 controller-number timeslots timeslot-range
Syntax Description
Defaults
No default
Command Modes
Privileged EXEC
Command History
10.0
This command was introduced.
12.1(3)T
The timeslots keyword was added.
12.1(5)T
Support for Cisco AS5400 universal access servers was added.
Usage Guidelines
Use the show controllers t1/e1 timeslots command to display the CAS and ISDN PRI channel state in detail. This command shows whether the DS0 channels of a controller are in idle, in-service, maintenance, or busyout states. Enter the show controllers t1/e1 command to display statistics about the T1 or E1 links.
Examples
The following example shows that the CAS state is enabled on the Cisco AS5300 universal access server with a T1 PRI card:
Router# show controllers timeslotsT1 1 is up:Loopback: NONEDS0 Type Modem <-> Service Channel Rx TxState State A B C D A B C D-----------------------------------------------------------------------------------------1 cas-modem 1 in insvc connected 1 1 1 1 1 1 1 12 cas - - insvc idle 0 0 0 0 0 0 0 03 cas - - insvc idle 0 0 0 0 0 0 0 04 cas - - insvc idle 0 0 0 0 0 0 0 05 cas - - insvc idle 0 0 0 0 0 0 0 06 cas - - insvc idle 0 0 0 0 0 0 0 07 cas - - insvc idle 0 0 0 0 0 0 0 08 cas - - insvc idle 0 0 0 0 0 0 0 09 cas - - insvc idle 0 0 0 0 0 0 0 010 cas - - maint static-bo 0 0 0 0 1 1 1 111 cas - - maint static-bo 0 0 0 0 1 1 1 112 cas - - maint static-bo 0 0 0 0 1 1 1 113 cas - - maint static-bo 0 0 0 0 1 1 1 114 cas - - maint static-bo 0 0 0 0 1 1 1 115 cas - - maint static-bo 0 0 0 0 1 1 1 116 cas - - maint static-bo 0 0 0 0 1 1 1 117 cas - - maint static-bo 0 0 0 0 1 1 1 118 cas - - maint static-bo 0 0 0 0 1 1 1 119 cas - - maint dynamic-bo 0 0 0 0 1 1 1 120 cas - - maint dynamic-bo 0 0 0 0 1 1 1 121 cas - - maint dynamic-bo 0 0 0 0 1 1 1 122 unused23 unused24 unusedThe following example shows that the ISDN PRI state is enabled on the Cisco AS5300 universal access server with a T1 PRI card:
T1 2 is up:Loopback: NONEDS0 Type Modem <-> Service Channel Rx TxState State A B C D A B C D---------------------------------------------------------------------------1 pri - - insvc idle2 pri - - insvc idle3 pri - - insvc idle4 pri - - insvc idle5 pri - - insvc idle6 pri - - insvc idle7 pri - - insvc idle8 pri - - insvc idle9 pri - - insvc idle10 pri - - insvc idle11 pri - - insvc idle12 pri - - insvc idle13 pri - - insvc idle14 pri - - insvc idle15 pri - - insvc idle16 pri - - insvc idle17 pri - - insvc idle18 pri - - insvc idle19 pri - - insvc idle20 pri - - insvc idle21 pri-modem 2 in insvc busy22 pri-modem 1 out insvc busy23 pri-digi - in insvc busy24 pri-sig - - outofsvc reservedshow controllers voice
To display information about voice-related hardware, use the show controllers voice command in privileged EXEC mode.
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays interface status information that is specific to voice-related hardware, such as the registers of the TDM switch, the host port interface of the digital signal processor (DSP), and the DSP firmware versions. The information displayed is generally useful only for diagnostic tasks performed by technical support.
Examples
The following is an example of the output from the show controllers voice command:
Router# show controllers voiceEPIC Switch registers:STDA 0xFF STDB 0xFF SARA 0xAD SARB 0xFF SAXA 0xFF SAXB 0x0 STCR 0x3FMFAIR 0x3FSTAR 0x65 OMDR 0xE2 VNSR 0x0 PMOD 0x4C PBNR 0xFF POFD 0xF0 POFU 0x18PCSR 0x1 PICM 0x0 CMD1 0xA0 CMD2 0x70 CBNR 0xFF CTAR 0x2 CBSR 0x20 CSCR0x0DSP 0 Host Port Interface:HPI Control Register 0x202InterfaceStatus 0x2A MaxMessageSize 0x80RxRingBufferSize 0x6 TxRingBufferSize 0x9pInsertRx 0x4 pRemoveRx 0x4 pInsertTx 0x6 pRemoveTx 0x6Rx Message 0:packet_length 100 channel_id 2 packet_id 0 process id 0x10000: 0000 4AC7 5F08 91D1 0000 0000 7DF1 69E5 63E1 63E20020: 6E7C ED67 DE5D DB5C DC60 EC7E 6BE1 58D3 50CD 4DCE0040: 50D2 5AE5 7868 DA52 CE4A C746 C647 C94B D25A EAF40060: 5DD7 4FCD 4ACA 4ACC 4FD3 5DE8 F769 DC58 D352 D2530080: D65B E573 6CDF 59D3 4ECF 4FD0Rx Message 1:packet_length 100 channel_id 1 packet_id 0 process id 0x10000: 0000 1CDD 3E48 3B74 0000 0000 3437 3D4C F0C8 BBB50020: B2B3 B7BF D25B 4138 3331 3339 435F CFBD B6B2 B1B40040: BBC8 7E48 3B34 3131 363D 4FDE C3B9 B3B1 B3B8 C2DB0060: 533F 3833 3235 3B48 71CC BDB7 B4B5 B8BF CF67 483D0080: 3836 383C 455B DAC6 BDB9 B9BBRx Message 2:packet_length 100 channel_id 2 packet_id 0 process id 0x10000: 0000 4AC8 5F08 9221 0000 0000 54DA 61F5 EF60 DA530020: CF4F CD4E D256 DB63 FCEE 5FDA 55D1 50CF 4FD3 56D80040: 5DE1 6E7C EC60 DC59 D655 D456 D85D DF6A F4F4 69E20060: 5CDD 5BDC 5BDE 61E9 6DF1 FF76 F16D E96A E566 EA6A0080: EB6F F16D EF79 F776 F5F5 73F0Rx Message 3:packet_length 100 channel_id 1 packet_id 0 process id 0x10000: 0000 1CDE 3E48 3BC4 0000 0000 C0CC EC54 453E 3C3C0020: 3F47 56F3 D1C7 C1BF C0C6 CEE1 6752 4A46 4648 4E590040: 6FE4 D6CF CDCE D2DA E57E 675E 5B5B 5E62 6B76 FCF60060: F6FA 7D75 7373 7BF5 EAE1 DCDA DADD E6FE 6559 514D0080: 4D4E 5563 EFD9 CDC8 C5C6 CAD1Rx Message 4:packet_length 100 channel_id 2 packet_id 0 process id 0x10000: 0000 4AC6 5F08 9181 0000 0000 DD5B DC5E E161 E4680020: FAFD 6CE1 5AD3 53D1 53D7 61EC EA59 CF4A C644 C3440040: CA4E D86C 60D0 48C2 3EBD 3CBD 3EC0 47CF 5976 DF4F0060: C945 C242 C146 C94E D668 73DB 54CE 4DCC 4DCE 53DB0080: 64F9 ED63 DC59 DA58 DC5D E46CRx Message 5:packet_length 100 channel_id 1 packet_id 0 process id 0x10000: 0000 1CDC 3E48 3B24 0000 0000 5B5B 5D62 6A76 FCF50020: F5F9 7D78 7374 7CF5 EAE1 DDDA DBDD E7FE 6559 514E0040: 4D4F 5663 EFD8 CDC8 C6C6 CAD1 E760 4E46 403F 40470060: 5173 D5C7 BFBC BCBE C5D4 6D4C 3F3B 3939 3D46 5ADB0080: C5BC B7B6 B8BD C8E8 4F3F 3835Tx Message 0:packet_length 100 channel_id 1 packet_id 0 process id 0x10000: 0000 4AC6 5F08 9181 0000 003C DD5B DC5E E161 E4680020: FAFD 6CE1 5AD3 53D1 53D7 61EC EA59 CF4A C644 C3440040: CA4E D86C 60D0 48C2 3EBD 3CBD 3EC0 47CF 5976 DF4F0060: C945 C242 C146 C94E D668 73DB 54CE 4DCC 4DCE 53DB0080: 64F9 ED63 DC59 DA58 DC5D E46CTx Message 1:packet_length 100 channel_id 2 packet_id 0 process id 0x10000: 0000 1CDC 3E48 3B24 0000 003C 5B5B 5D62 6A76 FCF50020: F5F9 7D78 7374 7CF5 EAE1 DDDA DBDD E7FE 6559 514E0040: 4D4F 5663 EFD8 CDC8 C6C6 CAD1 E760 4E46 403F 40470060: 5173 D5C7 BFBC BCBE C5D4 6D4C 3F3B 3939 3D46 5ADB0080: C5BC B7B6 B8BD C8E8 4F3F 3835Tx Message 2:packet_length 100 channel_id 1 packet_id 0 process id 0x10000: 0000 4AC7 5F08 91D1 0000 003C 7DF1 69E5 63E1 63E20020: 6E7C ED67 DE5D DB5C DC60 EC7E 6BE1 58D3 50CD 4DCE0040: 50D2 5AE5 7868 DA52 CE4A C746 C647 C94B D25A EAF40060: 5DD7 4FCD 4ACA 4ACC 4FD3 5DE8 F769 DC58 D352 D2530080: D65B E573 6CDF 59D3 4ECF 4FD0Tx Message 3:packet_length 100 channel_id 2 packet_id 0 process id 0x10000: 0000 1CDD 3E48 3B74 0000 003C 3437 3D4C F0C8 BBB50020: B2B3 B7BF D25B 4138 3331 3339 435F CFBD B6B2 B1B40040: BBC8 7E48 3B34 3131 363D 4FDE C3B9 B3B1 B3B8 C2DB0060: 533F 3833 3235 3B48 71CC BDB7 B4B5 B8BF CF67 483D0080: 3836 383C 455B DAC6 BDB9 B9BBTx Message 4:packet_length 100 channel_id 1 packet_id 0 process id 0x10000: 0000 4AC8 5F08 9221 0000 003C 54DA 61F5 EF60 DA530020: CF4F CD4E D256 DB63 FCEE 5FDA 55D1 50CF 4FD3 56D80040: 5DE1 6E7C EC60 DC59 D655 D456 D85D DF6A F4F4 69E20060: 5CDD 5BDC 5BDE 61E9 6DF1 FF76 F16D E96A E566 EA6A0080: EB6F F16D EF79 F776 F5F5 73F0Tx Message 5:packet_length 100 channel_id 2 packet_id 0 process id 0x10000: 0000 1CDE 3E48 3BC4 0000 003C C0CC EC54 453E 3C3C0020: 3F47 56F3 D1C7 C1BF C0C6 CEE1 6752 4A46 4648 4E590040: 6FE4 D6CF CDCE D2DA E57E 675E 5B5B 5E62 6B76 FCF60060: F6FA 7D75 7373 7BF5 EAE1 DCDA DADD E6FE 6559 514D0080: 4D4E 5563 EFD9 CDC8 C5C6 CAD1Tx Message 6:packet_length 100 channel_id 2 packet_id 0 process id 0x10000: 0000 1CDA 3E48 3A84 0000 003C E75F 4E46 403F 41470020: 5174 D5C7 BFBC BCBE C5D4 6C4C 3F3B 3939 3D46 5BDA0040: C5BC B7B6 B8BD C8E9 4F3F 3834 3437 3D4C EEC8 BBB50060: B2B3 B8BF D35A 4138 3331 3339 435F CEBD B6B1 B1B40080: BBC9 7C48 3B34 3131 363D 4FDETx Message 7:packet_length 100 channel_id 1 packet_id 0 process id 0x10000: 0000 4AC5 5F08 9131 0000 003C 66DE 66EB 67EE FE6E0020: F7E7 6B68 E068 EE6A DF5C DF62 EDF1 6FF2 7A78 67DC0040: 5EDF 62E7 64E6 66E0 7071 EA69 F86E E260 DE5D E6650060: EB75 F0FB 6DE9 64E4 69E3 66EA 67E9 6DF9 F177 EC6E0080: EB6E F876 F875 7D6E E966 E05DTx Message 8:packet_length 100 channel_id 2 packet_id 0 process id 0x10000: 0000 1CDB 3E48 3AD4 0000 003C C2B9 B3B1 B3B8 C2DC0020: 523F 3733 3235 3C49 72CB BDB7 B4B5 B8BF CF67 483C0040: 3836 373C 455C DAC6 BDB9 B9BB C0CC EE54 453E 3C3C0060: 3F47 56F1 D1C7 C1BF C0C6 CEE1 6651 4A46 4648 4D590080: 70E3 D6CF CDCE D2D9 E67E 675EBootloader 1.8, Appn 3.1Application firmware 3.1.8, Built by claux on Thu Jun 17 11:00:05 1999VIC Interface Foreign Exchange Station 0/0, DSP instance (0x19543C0)Singalling channel num 128 Signalling proxy 0x0 Signaling dsp 0x19543C0tx outstanding 0, max tx outstanding 32ptr 0x0, length 0x0, max length 0x0dsp_number 0, Channel ID 1received 0 packets, 0 bytes, 0 gaint packets0 drops, 0 no buffers, 0 input errors 0 input overruns650070 bytes output, 4976 frames output, 0 output errors, 0 outputunderrun0 unaligned framesVIC Interface Foreign Exchange Station 0/1, DSP instance (0x1954604)Singalling channel num 129 Signalling proxy 0x0 Signaling dsp 0x1954604tx outstanding 0, max tx outstanding 32ptr 0x0, length 0x0, max length 0x0dsp_number 0, Channel ID 2received 0 packets, 0 bytes, 0 gaint packets0 drops, 0 no buffers, 0 input errors 0 input overruns393976 bytes output, 3982 frames output, 0 output errors, 0 outputunderrun0 unaligned framesRelated Commands
show csm
To display the call switching module (CSM) statistics for a particular digital signal processor (DSP) channel or all DSP channels or for a specific modem or DSP channel, use the show csm command in privileged EXEC mode.
Cisco AS5300 Universal Access Server
show csm {modem [slot/port | modem-group-number] | voice [slot/dspm/dsp/dsp-channel]}
Cisco AS5800 Universal Access Server
show csm voice [shelf/slot/port]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command shows the information related to CSM, which includes the DSP channel, the start time of the call, the end time of the call, and the channel on the controller used by the call.
Use the show csm modem command to display the CSM call statistic information for a specific modem, for a group of modems, or for all modems. If a slot/port argument is specified, then CSM call statistics are displayed for the specified modem. If the modem-group-number argument is specified, the CSM call statistics for all of the modems associated with that modem group are displayed. If no keyword is specified, CSM call statistics for all modems on the Cisco AS5300 universal access server are displayed.
Use the show csm voice command to display CSM statistics for a particular DSP channel. If the slot/dspm/dsp/dsp-channel or shelf/slot/port argument is specified, the CSM call statistics for calls using the identified DSP channel will be displayed. If no argument is specified, all CSM call statistics for all DSP channels will be displayed.
Examples
The following is sample output from the Cisco AS5300 universal access server for the show csm voice command:
Router# show csm voice 2/4/4/0slot 2, dspm 4, dsp 4, dsp channel 0,slot 2, port 56, tone, device_status(0x0002): VDEV_STATUS_ACTIVE_CALL.csm_state(0x0406)=CSM_OC6_CONNECTED, csm_event_proc=0x600E2678, current call thru PRI lineinvalid_event_count=0, wdt_timeout_count=0wdt_timestamp_started is not activatedwait_for_dialing:False, wait_for_bchan:Falsepri_chnl=TDM_PRI_STREAM(s0, u0, c22), tdm_chnl=TDM_DSP_STREAM(s2, c27)dchan_idb_start_index=0, dchan_idb_index=0, call_id=0xA003, bchan_num=22csm_event=CSM_EVENT_ISDN_CONNECTED, cause=0x0000ring_no_answer=0, ic_failure=0, ic_complete=0dial_failure=0, oc_failure=0, oc_complete=3oc_busy=0, oc_no_dial_tone=0, oc_dial_timeout=0remote_link_disc=0, stat_busyout=0oobp_failure=0call_duration_started=00:06:53, call_duration_ended=00:00:00, total_call_duration=00:00:44The calling party phone number = 408The called party phone number = 5271086total_free_rbs_timeslot = 0, total_busy_rbs_timeslot = 0, total_dynamic_busy_rbs_timeslot = 0, total_static_busy_rbs_timeslot = 0,total_sw56_rbs_timeslot = 0, total_sw56_rbs_static_bo_ts = 0,total_free_isdn_channels = 21, total_busy_isdn_channels = 0,total_auto_busy_isdn_channels = 0,min_free_device_threshold = 0The following is sample output from the Cisco AS5800 for the show csm voice command:
Router# show csm voice 1/8/19shelf 1, slot 8, port 19VDEV_INFO:slot 8, port 19vdev_status(0x00000401):VDEV_STATUS_ACTIVE_CALL.VDEV_STATUS_HASLOCK.csm_state(0x00000406)=CSM_OC6_CONNECTED, csm_event_proc=0x60868B8C, currentcall thru PRI lineinvalid_event_count=0, wdt_timeout_count=0watchdog timer is not activatedwait_for_bchan:Falsepri_chnl=(T1 1/0/0:22), vdev_chnl=(s8, c19)start_chan_p=0, chan_p=62436D58, call_id=0x800D, bchan_num=22The calling party phone number =The called party phone number = 7511ring_no_answer=0, ic_failure=0, ic_complete=0dial_failure=0, oc_failure=0, oc_complete=1oc_busy=0, oc_no_dial_tone=0, oc_dial_timeout=0remote_link_disc=0, busyout=0, modem_reset=0call_duration_started=3d16h, call_duration_ended=00:00:00,total_call_duration=00:00:00Table 34 describes the significant fields shown in the display.
Related Commands
show dial-peer video
To display dial-peer configuration, use the show dial-peer video command in privileged EXEC mode.
show dial-peer video [number] [summary]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to review video dial peer configuration.
Examples
On a Cisco MC3810 multiservice concentrator, the following example displays detailed information about all configured video dial peers:
Router# show dial-peer videoVideo Dial-Peer 1type = videocodec, destination-pattern = 111port signal = 1/0, port media = Serial1nsap = 47.0091810000000050E201B101.00107B09C6F2.C8Video Dial-Peer 2type = videoatm, destination-pattern = 222session-target = ATM0 svc nsap 47.0091810000000050E201B101.00E01E92ADC2.C8Video Dial-Peer 3type = videoatm, destination-pattern = 333session-target = ATM0 pvc 70/70show dial-peer voice
To display configuration information for dial peers, use the show dial-peer voice command in privileged EXEC mode.
show dial-peer voice [number] [summary]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the show dial-peer voice privileged EXEC command to display the configuration for all Voice over IP (VoIP) and plain old telephone service (POTS) dial peers configured for the router. To show configuration information for only one specific dial peer, use the argument number to identify the dial peer.
Examples
The following is sample output from the show dial-peer voice command for a POTS dial peer:
Router# show dial-peer voice 1VoiceEncapPeer1tag = 1, dest-pat = `+14085291000',answer-address = `',group = 0, Admin state is up, Operation state is downPermission is Both,type = pots, prefix = `',session-target = `', voice port =Connect Time = 0, Charged Units = 0Successful Calls = 0, Failed Calls = 0Accepted Calls = 0, Refused Calls = 0Last Disconnect Cause is ""Last Disconnect Text is ""Last Setup Time = 0The following is sample output from the show dial-peer voice command for a VoIP dial peer:
Router# show dial-peer voice 10VoiceOverIpPeer10tag = 10, dest-pat = `',incall-number = `+14087',group = 0, Admin state is up, Operation state is downPermission is Answer,type = voip, session-target = `',sess-proto = cisco, req-qos = bestEffort,acc-qos = bestEffort,fax-rate = voice, codec = g729r8,Expect factor = 10,Icpif = 30, VAD = disabled, Poor QOV Trap = disabled,Connect Time = 0, Charged Units = 0Successful Calls = 0, Failed Calls = 0Accepted Calls = 0, Refused Calls = 0Last Disconnect Cause is ""Last Disconnect Text is ""Last Setup Time = 0Table 35 provides an alphabetical listing of the show dial-peer voice output fields and a description of each field.
Related Commands
show dialplan incall number
To show which plain old telephone service (POTS) dial peer is matched for a specific calling number or voice port, use the show dialplan incall number command in privileged EXEC mode.
show dialplan incall voice-port number calling-number [timeout]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(1)T
This command was introduced on the Cisco 3600 series router.
12.2(8)T
The timeout keyword was added.
Usage Guidelines
Use the show dialplan incall number command as a troubleshooting tool to determine which POTS dial peer is matched for an incoming call, for the selected calling number and voice port. When using the show dialplan incall number command, the router attempts to match these items in the order listed:
1.
2.
3.
The router first attempts to match a dial peer based on the calling number (ANI). If the router is unable to match a dial peer based on the calling number, it matches the call to a POTS dial peer based on the selected voice interface. If more than one dial peer uses the same voice port, the router selects the first matching dial peer. Use the timeout keyword to enable matching variable-length destination patters associated with dial peers. This can increase you r chances of finding a match for the dial peer number you specify.
Note
Examples
The following example shows that an incoming call from interface 1/0/0:D with a calling number of 12345 is matched to POTS dial peer 10:
Router# show dialplan incall 1/0/0:D number 12345Macro Exp.: 12345VoiceEncapPeer10information type = voice,tag = 10, destination-pattern = `123..',answer-address = `', preference=0,numbering Type = `unknown'group = 10, Admin state is up, Operation state is up,incoming called-number = `', connections/maximum = 0/unlimited,DTMF Relay = disabled,huntstop = disabled,in bound application associated: DEFAULTout bound application associated:permission :bothincoming COR list:maximum capabilityoutgoing COR list:minimum requirementtype = pots, prefix = `',forward-digits defaultsession-target = `', voice-port = `1/0/0:D',direct-inward-dial = disabled,digit_strip = enabled,register E.164 number with GK = TRUEConnect Time = 0, Charged Units = 0,register E.164 number with GK = TRUEConnect Time = 0, Charged Units = 0,Successful Calls = 0, Failed Calls = 0,Accepted Calls = 0, Refused Calls = 0,Last Disconnect Cause is "",Last Disconnect Text is "",Last Setup Time = 0.Matched: 12345 Digits: 3Target:The following example shows that if no dial peer has a destination pattern or answer address that matches the calling number of 888, the incoming call is matched to POTS dial peer 99, because the call comes in on voice port 1/0/1:D, which is the voice port configured for this dial peer:
Router# show dialplan incall 1/0/1:D number 888Macro Exp.: 888VoiceEncapPeer99information type = voice,tag = 99, destination-pattern = `99...',answer-address = `', preference=1,numbering Type = `national'group = 99, Admin state is up, Operation state is up,incoming called-number = `', connections/maximum = 0/unlimited,DTMF Relay = disabled,huntstop = disabled,in bound application associated: DEFAULTout bound application associated:permission :bothincoming COR list:maximum capabilityoutgoing COR list:minimum requirementtype = pots, prefix = `5',forward-digits 4session-target = `', voice-port = `1/0/1:D',direct-inward-dial = enabled,digit_strip = enabled,register E.164 number with GK = TRUEConnect Time = 0, Charged Units = 0,Successful Calls = 0, Failed Calls = 0,Accepted Calls = 0, Refused Calls = 0,Last Disconnect Cause is "",Last Disconnect Text is "",Last Setup Time = 0.Matched: Digits: 0Target:Table 36 describes the significant fields shown in the display.
Related Commands
show dial peer voice
Displays the configuration information for dial peers.
show dialplan number
Displays which dial peer is matched for a particular telephone number.
show dialplan number
To show which dial peer is reached when a particular telephone number is dialed, use the show dialplan number command in privileged EXEC mode.
show dialplan number dial string [huntstop] [timeout]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(1)T
This command was introduced on the Cisco 3600 series router.
12.2(1)
The huntstop keyword was added.
12.2(8)T
The timeout keyword was added.
Usage Guidelines
The show dialplan number command is used to test whether the dial plan configuration is valid and working as expected. Use the timeout keyword to enable matching variable-length destination patters associated with dial peers. This can increase you r chances of finding a match for the dial peer number you specify.
Examples
The following example shows sample output from the show dialplan number command using the destination pattern of 1001:
Router# show dialplan number 1001Macro Exp.: 1001VoiceEncapPeer1003information type = voice,tag = 1003, destination-pattern = `1001',answer-address = `', preference=0,numbering Type = `unknown'group = 1003, Admin state is up, Operation state is up,incoming called-number = `', connections/maximum = 0/unlimited,DTMF Relay = disabled,huntstop = enabled,type = pots, prefix = `',forward-digits defaultsession-target = `', voice-port = `1/1',direct-inward-dial = disabled,Connect Time = 0, Charged Units = 0,Successful Calls = 0, Failed Calls = 0, Incomplete Calls = 0Accepted Calls = 0, Refused Calls = 0,Last Disconnect Cause is "",Last Disconnect Text is "",Last Setup Time = 0.Matched: 1001 Digits: 4Target:VoiceEncapPeer1004information type = voice,tag = 1004, destination-pattern = `1001',answer-address = `', preference=0,numbering Type = `unknown'group = 1004, Admin state is up, Operation state is up,...Matched: 1001 Digits: 4Target:VoiceEncapPeer1002information type = voice,tag = 1002, destination-pattern = `1001',answer-address = `', preference=0,numbering Type = `unknown'group = 1002, Admin state is up, Operation state is up,...Matched: 1001 Digits: 4Target:VoiceEncapPeer1001information type = voice,tag = 1001, destination-pattern = `1001',answer-address = `', preference=0,numbering Type = `unknown'group = 1001, Admin state is up, Operation state is up,...Matched: 1001 Digits: 4Target:The following example shows sample output from the show dialplan number command using the destination pattern of 1001 and the huntstop keyword:
Router# show dialplan number 1001 huntstopMacro Exp.: 1001VoiceEncapPeer1003information type = voice,tag = 1003, destination-pattern = `1001',answer-address = `', preference=0,numbering Type = `unknown'group = 1003, Admin state is up, Operation state is up,incoming called-number = `', connections/maximum = 0/unlimited,DTMF Relay = disabled,huntstop = enabled,type = pots, prefix = `',forward-digits defaultsession-target = `', voice-port = `1/1',direct-inward-dial = disabled,Connect Time = 0, Charged Units = 0,Successful Calls = 0, Failed Calls = 0, Incomplete Calls = 0Accepted Calls = 0, Refused Calls = 0,Last Disconnect Cause is "",Last Disconnect Text is "",Last Setup Time = 0.Matched: 1001 Digits: 4Target:Table 37 explains the significant fields shown in this example.
Related Commands
show dialplan incall number
Pairs different voice ports and telephone numbers together for troubleshooting Voice over IP.
show frame-relay vofr
To display information about the FRF.11 subchannels being used on Voice over Frame Relay (VoFR) data link connection identifiers (DLCIs), use the show frame-relay vofr command in privileged EXEC mode.
show frame-relay vofr [interface [dlci [cid]]]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If this command is entered without a specified interface, FRF.11 subchannel information will be displayed for all VoFR interfaces and DLCIs configured on the router.
Note
Examples
The following is sample output from the show frame-relay vofr command when an interface is not specified:
Router# show frame-relay vofrinterface vofr-type dlci cid cid-typeSerial0/0.1 VoFR 16 4 dataSerial0/0.1 VoFR 16 5 call-controlSerial0/0.1 VoFR 16 10 voiceSerial0/1.1 VoFR cisco 17 4 dataThe following is sample output from the show frame-relay vofr command when an interface is specified:
Router# show frame-relay vofr serial0interface vofr-type dlci cid cid-typeSerial0 VoFR 16 4 dataSerial0 VoFR 16 5 call-controlSerial0 VoFR 16 10 voiceThe following is sample output from the show frame-relay vofr command when an interface and a DLCI are specified:
Router# show frame-relay vofr serial0 16VoFR Configuration for interface Serial0dlci vofr-type cid cid-type input-pkts output-pkts dropped-pkts16 VoFR 4 data 0 0 016 VoFR 5 call-control 85982 86099 016 VoFR 10 voice 2172293 6370815 0The following is sample output from the show frame-relay vofr command when an interface, a DLCI, and a CID are specified:
Router# show frame-relay vofr serial0 16 10VoFR Configuration for interface Serial0 dlci 16vofr-type VoFR cid 10 cid-type voiceinput-pkts 2172293 output-pkts 6370815 dropped-pkts 0Table 38 describes the significant fields shown in the display.
Related Commands
show gatekeeper calls
To show the status of each ongoing call of which a gatekeeper is aware, use the show gatekeeper calls command in privileged EXEC mode.
show gatekeeper calls
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the show gatekeeper calls command to show all active calls currently being handled by a particular MCM gatekeeper. If you have forced a disconnect for either a particular call or all calls associated with a particular MCM gatekeeper by using the clear h323 gatekeeper call command, the system will not display information about those calls.
Examples
The following is sample output from the show gatekeeper calls command:
Router# show gatekeeper callsTotal number of active calls = 1.GATEKEEPER CALL INFO====================LocalCallID Age(secs) BW12-3339 94 768(Kbps)Endpt(s):Alias E.164Addr CallSignalAddr Port RASSignalAddr Portsrc EP:epA 90.0.0.11 1720 90.0.0.11 1700dst EP:epB@zoneB.comsrc PX:pxA 90.0.0.01 1720 90.0.0.01 24999dst PX:pxB 172.21.139.90 1720 172.21.139.90 24999Table 39 describes the significant fields shown in the display.
Related Commands
clear h323 gateway call
Forces a specific call or all calls currently active on the gatekeeper to disconnect.
show gatekeeper endpoints
To display the status of all registered endpoints for a gatekeeper, use the show gatekeeper endpoints command in EXEC mode.
show gatekeeper endpoints
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
11.3(2)NA
This command was introduced.
12.0(5)T
The display format was modified for H.323 Version 2.
Usage Guidelines
Use this command to display the status of all registered endpoints for a gatekeeper.
Examples
The following is sample output from the show gatekeeper endpoints command:
Router# show gatekeeper endpointsCallsignalAddr Port RASSignalAddr Port Zone Name Type F--------------- ---- ------------- ----- ---------- ----- --172.21.127.8 1720 172.21.127.8 24999 sj-gk MCU H323-ID:joe@cisco.com172.21.13.88 1720 172.21.13.88 1719 sj-gk VOIP-GW O H323-ID:la-gwTable 40 describes the significant fields shown in the display.
Related Commands
show gatekeeper gw-type-prefix
To display the gateway technology prefix table, use the show gatekeeper gw-type-prefix command in privileged EXEC mode.
show gatekeeper gw-type-prefix
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(2)NA
This command was introduced.
12.0(5)T
The display format was modified for H.323 Version 2.
Usage Guidelines
Use the show gatekeeper gw-type-prefix command to display the gateway technology prefix table.
Examples
The following is sample output for a gatekeeper that is controlling two local zones, sj-gk and la-gk:
Router# show gatekeeper gw-type-prefixGATEWAY TYPE PREFIX TABLE===========================Prefix:12#* (Default gateway-technology)Zone sj-gk master gateway list:172.21.13.11:1720 sj-gw1172.21.13.22:1720 sj-gw2 (out-of-resources)172.21.13.33:1720 sj-gw3Zone sj-gk prefix 408....... priority gateway list(s):Priority 10:172.21.13.11:1720 sj-gw1Priority 5:172.21.13.22:1720 sj-gw2 (out-of-resources)172.21.13.33:1720 sj-gw3Prefix:7#* (Hopoff zone la-gk)Statically-configured gateways (not necessarily currently registered):1.1.1.1:17202.2.2.2:1720Zone la-gk master gateway list:171.69.127.11:1720 la-gw1171.69.127.22:1720 la-gw2Table 41 describes the fields contained in the show gatekeeper gw-type-prefix sample output.
Related Commands
show gatekeeper servers
To see a list of currently registered and statically configured triggers on this gatekeeper router, enter the show gatekeeper servers command in EXEC mode.
show gatekeeper servers [gkid]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
Enter this command to show all server triggers (whether dynamically registered from the external servers or statically configured from the command line interface) on this gatekeeper. If gkid is specified, only triggers applied to the specified gatekeeper zone appear. If the gkid argument is not specified, server triggers for all local gatekeeper zones on this router appear.
Examples
This example shows the operating information of the specified gk102 server:
Router# show gatekeeper servers gk102GATEKEEPER SERVERS STATUS=========================Gatekeeper Server listening port:20000Gatekeeper-ID:gk102--------------------RRQ Priority:1Server-ID:sj-serverServer IP address:1.14.93.28:42387Server type:dynamically registeredConnection Status:activeTrigger Information:Supported Prefix:10#Supported Prefix:3#RRQ Priority:2Server-ID:sf-serverServer IP address:1.14.93.43:3820Server type:CLI-configuredConnection Status:inactiveTrigger Information:Endpoint-type:MCUEndpoint-type:VOIP-GWSupported Prefix:99#ARQ Priority:1Server-ID:sj-serverServer IP address:1.14.93.28:42387Server type:dynamically registeredConnection Status:activeTrigger Information:Destination Info:M:nilkant@zone14.comDestination Info:E:1800.......Redirect Reason:Call forwarded no replyRedirect Reason:Call deflectionRelated Commands
show gatekeeper status
To show overall gatekeeper status, including authorization and authentication status, zone status, and so on, use the show gatekeeper status command in EXEC mode.
show gatekeeper status
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
11.3(2)NA
This command was introduced.
12.0(3)T
The command introduced in Cisco IOS Release 11.3(2)NA was integrated into Cisco IOS Release 12.0(3)T.
Examples
The following is sample output from the show gatekeeper status command:
Router# show gatekeeper statusGatekeeper State: UPZone Name: gk-px4.cisco.comAccounting: DISABLEDSecurity: DISABLEDTable 42 describes the significant fields shown in the display.
show gatekeeper zone prefix
To display the zone prefix table, use the show gatekeeper zone prefix command in privileged EXEC mode.
show gatekeeper zone prefix
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following is an example of output from the show gatekeeper zone prefix command:
Router# show gatekeeper zone prefixZONE PREFIX TABLE=================GK-NAME E164-PREFIX------- -----------gk.zone13 212.......gk.zone14 415.......gk.zone14 408.......Table 43 describes the significant fields shown in the display.
show gatekeeper zone status
To display the status of zones related to a gatekeeper, use the show gatekeeper zone status command in privileged EXEC mode.
show gatekeeper zone status
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(2)NA
This command was introduced on the Cisco 2600 series and Cisco 3600 series routers.
12.0(5)T
This display format was modified for H.323 Version 2.
Usage Guidelines
Use this command to display the status of all zones related to a gatekeeper.
Examples
The following is an example of output from the show gatekeeper zone status command:
Router# show gatekeeper zone statusGATEKEEPER ZONES================GK name Domain Name RAS Address PORT FLAGS MAX-BW CUR-BW(kbps) (kbps)------- ----------- ----------- ---- ----- ------ ------sj.xyz.com xyz.com 1.14.93.85 1719 LS 0SUBNET ATTRIBUTES :All Other Subnets :(Enabled)PROXY USAGE CONFIGURATION :inbound Calls from germany.xyz.com :to terminals in local zone sj.xyz.com :use proxyto gateways in local zone sj.xyz.com :do not use proxyOutbound Calls to germany.xyz.comfrom terminals in local zone germany.xyz.com :use proxyfrom gateways in local zone germany.xyz.com :do not use proxyInbound Calls from all other zones :to terminals in local zone sj.xyz.com :use proxyto gateways in local zone sj.xyz.com :do not use proxyOutbound Calls to all other zones :from terminals in local zone sj.xyz.com :do not use proxyfrom gateways in local zone sj.xyz.com :do not use proxytokyo.xyz.co xyz.com 172.21.139.89 1719 RS 0milan.xyz.co xyz.com 171.69.57.90 1719 RS 0Table 44 describes the significant fields shown in the display.
Related Commands
show gateway
To display the current gateway status, use the show gateway command in privileged EXEC mode.
show gateway
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(6)NA2
This command was introduced on the Cisco 2600 series and Cisco 3600 series routers.
12.0(5)T
This display format was modified for H.323 V2.
Usage Guidelines
This command displays the current gateway status.
Examples
The following example shows the report that appears when the gateway is not registered with a gatekeeper:
Router# show gatewayGateway gateway1 is not registered to any gatekeeperGateway alias listH323-ID gateway1H323 resource thresholding is Enabled but NOT ActiveH323 resource threshold values:DSP: Low threshold 60, High threshold 70DS0: Low threshold 60, High threshold 70This following example indicates that an E.164 address has been assigned to the gateway:
Router# show gateGateway gateway1 is registered to Gatekeeper gk1Gateway alias listE.164 Number 5551212H323-ID gateway1The following example shows the report that appears when the gateway is registered with a gatekeeper and H.323 resource threshold reporting is enabled with the resource threshold command:
Router# show gatewayGateway gateway1 is registered to Gatekeeper gk1Gateway alias listH323-ID gateway1H323 resource thresholding is Enabled and ActiveH323 resource threshold values:DSP: Low threshold 60, High threshold 70DS0: Low threshold 60, High threshold 70The following example shows the report that appears when the gateway is registered with a gatekeeper and H.323 resource threshold reporting is disabled with the no resource threshold command:
Router# show gatewayGateway gateway1 is registered to Gatekeeper gk1Gateway alias listH323-ID gateway1H323 resource thresholding is DisabledRelated Commands
resource threshold
Configures a gateway to report H.323 resource availability to the gatekeeper of the gateway.
show interface dspfarm
To display digital signal processor (DSP) information on the two-port T1/E1 high-density port adapter for the Cisco 7200 series, use the show interface dspfarm command in privileged EXEC mode.
show interface dspfarm [slot/port]
Syntax Description
slot
(Optional) Slot location of the port adapter.
/port
(Optional) Port number on the port adapter.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(5)XE
This command was introduced on the Cisco 7200 series router.
12.1(1)T
This command was integrated into the Cisco IOS 12.1(1)T.
Usage Guidelines
The local time-division multiplexing (TDM) cross-connect map can be displayed.
Examples
The following example is sample output from the show interface dspfarm command for port adapter slot 0 of chassis slot 3, on the Cisco 7200 series router:
Router# show interface dspfarm 3/0DSPfarm3/0 is up, line protocol is upHardware is VXC-2T1/E1MTU 256 bytes, BW 12000 Kbit, DLY 0 usec,reliability 255/255, txload 4/255, rxload 1/255Encapsulation VOICE, loopback not setC549 DSP Firmware Version:MajorRelease.MinorRelease (BuildNumber)DSP Boot Loader:255.255 (255)DSP Application:4.0 (3)Medium Complexity Application:3.2 (5)High Complexity Application:3.2 (5)Total DSPs 30, DSP0-DSP29, Jukebox DSP id 30Down DSPs:noneTotal sig channels 120 used 24, total voice channels 120 used 00 active calls, 0 max active calls, 0 total calls30887 rx packets, 0 rx drops, 30921 tx packets, 0 tx frags0 curr_dsp_tx_queued, 29 max_dsp_tx_queuedLast input never, output never, output hang neverLast clearing of "show interface" counters neverQueueing strategy:fifoOutput queue 0/0, 0 drops; input queue 0/75, 0 drops5 minute input rate 13000 bits/sec, 94 packets/sec5 minute output rate 193000 bits/sec, 94 packets/sec30887 packets input, 616516 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort30921 packets output, 7868892 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped outTable 45 describes the significant fields shown in the display.
show mgcp
To display Media Gateway Control Protocol (MGCP) configuration information, use the show mgcp command in EXEC mode.
show mgcp
Defaults
No defaults
Command Modes
EXEC
Command History
12.1(1)T
This command was introduced for the Cisco AS5300 universal access server.
12.1(3)T
Output was updated to show additional gateway and platform information.
Examples
The following displays an example of the command format and output for show mgcp.
Router# show mgcpMGCP Admin State ACTIVE, Oper State ACTIVE - Cause Code NONEMGCP call-agent: 192.168.10.10 2302 Initial protocol service is MGCPmgcp block-newcalls DISABLEDMGCP dtmf-relay disabled for all codec typesMGCP modem passthru: CAMGCP request timeout 500, MGCP request retries 3MGCP gateway port: 2427, MGCP maximum waiting delay 3000MGCP restart delay 5, MGCP vad DISABLEDMGCP sdp simple DISABLED, MGCP cisco fgdos DISABLEDMGCP codec type g711ulaw, MGCP packetization period 20MGCP JB threshold lwm 30, MGCP JB threshold hwm 150MGCP LAT threshold lwm 150, MGCP LAT threshold hwm 300MGCP PL threshold lwm 1000, MGCP PL threshold hwm 10000MGCP playout mode is adaptive 60, 4, 200 in msecMGCP IP ToS low delay disabled, MGCP IP ToS high throughput disabledMGCP IP ToS high reliability disabled, MGCP IP ToS low cost disabledMGCP IP precedence 3, MGCP default package: trunk-packageMGCP supported packages: gm-package dtmf-package trunk-package rtp-package as-packagescript-packageTable 46 describes the significant fields shown in the display.
Related Commands
show mgcp connection
To display Media Gateway Control Protocol (MGCP) configuration information, use the show mgcp connection command in EXEC mode.
show mgcp connection
Syntax Description
Defaults
No defaults
Command Modes
EXEC
Command History
12.1(1)T
This command was introduced for the Cisco AS5300 universal access server.
12.1(3)T
Output was updated to show additional gateway and platform information.
Examples
Following is an example of an MGCP configuration displaying active MGCP-controlled connections.
Router# show mgcp connectionEndpoint Call_ID(C) Conn_ID(I) (P)ort (M)ode (S)tate (C)odec (E)vent[SIFL] (R)esult[EA]1. S0/DS1-0/1 C=103,23,24 I=0x8 P=16586,16634 M=3 S=4,4 C=5 E=2,0,0,2 R=0,02. S0/DS1-0/2 C=103,25,26 I=0x9 P=16634,16586 M=3 S=4,4 C=5 E=0,0,0,0 R=0,03. S0/DS1-0/3 C=101,15,16 I=0x4 P=16506,16544 M=3 S=4,4 C=5 E=2,0,0,2 R=0,04. S0/DS1-0/4 C=101,17,18 I=0x5 P=16544,16506 M=3 S=4,4 C=5 E=0,0,0,0 R=0,05. S0/DS1-0/5 C=102,19,20 I=0,6 P=16572,16600 M=3 S=4,4 C=5 E=2,0,0,2 R=0,06. S0/DS1-0/6 C=102,21,22 I=0x7 P=16600,16572 M=3 S=4,4 C=5 E=0,0,0,0 R=0,0Total number of active calls 6Table 47 describes the significant fields shown in the display.
Related Commands
show mgcp endpoint
To display Media Gateway Control Protocol (MGCP) configuration information, use the show mgcp endpoint command in EXEC mode.
show mgcp endpoint
Syntax Description
Defaults
No defaults
Command Modes
EXEC
Command History
12.1(1)T
This command was introduced for the Cisco AS5300 universal access server.
12.1(3)T
Output was updated to show additional gateway and platform information.
Examples
The following example shows how endpoints are configured:
Router# show mgcp endpointT1/0 ds0-group 0 timeslots 1-24 type noneT1/1 ds0-group 0 timeslots 1-24 type noneT1/2 ds0-group 0 timeslots 1-24 type noneT1/3 ds0-group 0 timeslots 1-24 type noneRelated Commands
show mgcp statistics
To display Media Gateway Control Protocol (MGCP) configuration information, use the show mgcp statistics command in EXEC mode.
show mgcp statistics
Syntax Description
Defaults
No defaults
Command Modes
EXEC
Command History
12.1(1)T
This command was introduced for the Cisco AS5300 universal access server.
12.1(3)T
Output was updated to show additional gateway and platform information.
Examples
Following is an example of an MGCP configuration displaying MGCP statistics of network messages that have been received and sent.
Router# show mgcp statisticsUDP pkts rx 8, tx 9Unrecognized rx pkts 0, MGCP message parsing errors 0Duplicate MGCP ack tx 0, Invalid versions count 0CreateConn rx 4, successful 0, failed 0DeleteConn rx 2, successful 2, failed 0ModifyConn rx 4, successful 4, failed 0DeleteConn tx 0, successful 0, failed 0NotifyRequest rx 0, successful 4, failed 0AuditConnection rx 0, successful 0, failed 0AuditEndpoint rx 0, successful 0, failed 0RestartInProgress tx 1, successful 1, failed 0Notify tx 0, successful 0, failed 0ACK tx 8, NACK tx 0ACK rx 0, NACK rx 0IP address based Call Agents statistics:IP address 10.24.167.3, Total msg rx 8, successful 8, failed 0Table 48 describes the significant fields shown in the display.
Related Commands
show num-exp
To show the number expansions configured, use the show num-exp command in privileged EXEC mode.
show num-exp [dialed-number]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the show num-exp privileged EXEC command to display all the number expansions configured for this router. To display number expansion for only one number, specify that number by using the dialed-number argument.
Examples
The following is sample output from the show num-exp command:
Router# show num-expDest Digit Pattern = '0...' Translation = '+14085270...'Dest Digit Pattern = '1...' Translation = '+14085271...'Dest Digit Pattern = '3..' Translation = '+140852703..'Dest Digit Pattern = '4..' Translation = '+140852804..'Dest Digit Pattern = '5..' Translation = '+140852805..'Dest Digit Pattern = '6....' Translation = '+1408526....'Dest Digit Pattern = '7....' Translation = '+1408527....'Dest Digit Pattern = '8...' Translation = '+14085288...'Table 49 describes the significant fields shown in the display.
Related Commands
show pots csm
To show the current state of calls and the most recent event received by the call switching module (CSM) on the Cisco 800 series router, use the show pots csm command in EXEC mode.
show pots csm port
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is an example of show pots csm command output:
Router# show pots csm 1POTS PORT: 1CSM Finite State Machine:Call 0 - State: idle, Call Id: 0x0Active: noEvent: CSM_EVENT_NONE Cause: 0Call 1 - State: idle, Call Id: 0x0Active: noEvent: CSM_EVENT_NONE Cause: 0Call 2 - State: idle, Call Id: 0x0Active: noEvent: CSM_EVENT_NONE Cause: 0Related Commands
show pots status
To display the settings of the telephone port physical characteristics and other information on the telephone interfaces of the Cisco 800 series, use the show pots status command in privileged EXEC mode.
show pots status [1 | 2]
Syntax Description
1
(Optional) Display the settings of telephone port 1.
2
(Optional) Display the settings of telephone port 2.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The show pots status command displays the settings and information for both telephone ports.
Examples
The following is sample output from the show pots status command.
Router# show pots statusPOTS Global Configuration:Country: United StatesDialing Method: Overlap, Tone Source: Remote, CallerId Support: YESLine Type: 600 ohm, PCM Encoding: u-law, Disc Type: OSI,Ringing Frequency: 20Hz, Distinctive Ring Guard timer: 0 msecDisconnect timer: 1000 msec, Disconnect Silence timer: 5 secTX Gain: 6dB, RX Loss: -6dB,Filter Mask: 6FAdaptive Cntrl Mask: 0POTS PORT: 1Hook Switch Finite State Machine:State: On Hook, Event: 0Hook Switch Register: 10, Suspend Poll: 0CODEC Finite State Machine:State: Idle, Event: 0Connection: None, Call Type: Two Party, Direction: Rx onlyLine Type: 600 ohm, PCM Encoding: u-law, Disc Type: OSI,Ringing Frequency: 20Hz, Distinctive Ring Guard timer: 0 msecDisconnect timer: 1000 msec, Disconnect Silence timer: 5 secTX Gain: 6dB, RX Loss: -6dB,Filter Mask: 6FAdaptive Cntrl Mask: 0CODEC Registers:SPI Addr: 2, DSLAC Revision: 4SLIC Cmd: 0D, TX TS: 00, RX TS: 00Op Fn: 6F, Op Fn2: 00, Op Cond: 00AISN: 6D, ELT: B5, EPG: 32 52 00 00SLIC Pin Direction: 1FCODEC Coefficients:GX: A0 00GR: 3A A1Z: EA 23 2A 35 A5 9F C2 AD 3A AE 22 46 C2 F0B: 29 FA 8F 2A CB A9 23 92 2B 49 F5 37 1D 01X: AB 40 3B 9F A8 7E 22 97 36 A6 2A AER: 01 11 01 90 01 90 01 90 01 90 01 90GZ: 60ADAPT B: 91 B2 8F 62 31CSM Finite State Machine:Call 0 - State: idle, Call Id: 0x0Active: noCall 1 - State: idle, Call Id: 0x0Active: noCall 2 - State: idle, Call Id: 0x0Active: noPOTS PORT: 2Hook Switch Finite State Machine:State: On Hook, Event: 0Hook Switch Register: 20, Suspend Poll: 0CODEC Finite State Machine:State: Idle, Event: 0Connection: None, Call Type: Two Party, Direction: Rx onlyLine Type: 600 ohm, PCM Encoding: u-law, Disc Type: OSI,Ringing Frequency: 20Hz, Distinctive Ring Guard timer: 0 msecDisconnect timer: 1000 msec, Disconnect Silence timer: 5 secTX Gain: 6dB, RX Loss: -6dB,Filter Mask: 6FAdaptive Cntrl Mask: 0CODEC Registers:SPI Addr: 3, DSLAC Revision: 4SLIC Cmd: 0D, TX TS: 00, RX TS: 00Op Fn: 6F, Op Fn2: 00, Op Cond: 00AISN: 6D, ELT: B5, EPG: 32 52 00 00SLIC Pin Direction: 1FCODEC Coefficients:GX: A0 00GR: 3A A1Z: EA 23 2A 35 A5 9F C2 AD 3A AE 22 46 C2 F0B: 29 FA 8F 2A CB A9 23 92 2B 49 F5 37 1D 01X: AB 40 3B 9F A8 7E 22 97 36 A6 2A AER: 01 11 01 90 01 90 01 90 01 90 01 90GZ: 60ADAPT B: 91 B2 8F 62 31CSM Finite State Machine:Call 0 - State: idle, Call Id: 0x0Active: noCall 1 - State: idle, Call Id: 0x0Active: noCall 2 - State: idle, Call Id: 0x0Active: noTime Slot Control: 0Table 50 describes the significant fields shown in the display.
Related Commands
show proxy h323 calls
To list each active call on the proxy, use the show proxy h323 calls command in privileged EXEC mode.
show proxy h323 calls
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(2)NA
This command was introduced.
12.0(3)T
The command was integrated into Cisco IOS Release 12.0(3)T and supported on the Cisco MC3810 multiservice concentrator.
Examples
The following is sample output from the show proxy h323 calls command:
Router# show proxy h323 callsCall unique key = 1Conference ID = [277B87C0A283D111B63E00609704D8EA]Calling endpoint call signalling address = 55.0.0.41Calling endpoint aliases:H323_ID: ptel11@zone1.comCall state = Media StreamingTime call was initiated = 731146290 msshow proxy h323 detail-call
To display the details of a particular call on a proxy, use the show proxy h323 detail-call command in privileged EXEC mode.
show proxy h323 detail-call call-key
Syntax Description
call-key
Specifies the call you want to display. The call-key argument is derived from the show proxy h323 calls display.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(2)NA
This command was introduced.
12.0(3)T
The command was integrated into Cisco IOS Release 12.0(3)T and supported on the Cisco MC3810 multiservice concentrator.
Usage Guidelines
The show proxy h323 detail-call command can be used with or without the proxy statistics enabled.
Examples
The following is sample output from the show proxy h323 detail-call command without the proxy statistics enabled:
Router# show proxy h323 detail-call 1ConferenceID = [277B87C0A283D111B63E00609704D8EA]Calling endpoint aliases:H323_ID: ptel11@zone1.comCalled endpoint aliases:H323_ID: ptel21@zone2.comPeer proxy call signalling address = 55.0.0.41Time call was initiated = 731146290 msInbound CRV = 144Outbound CRV = 70Call state = Media StreamingH245 logical channels for call leg pte111@zone1.com<->px1@zone.comChannel number = 2Type = VIDEOState = OPENBandwidth = 374 kbpsTime created = 731146317 msChannel number = 1Type = AUDIOState = OPENBandwidth = 81 kbpsTime created = 731146316 msChannel number = 2Type = VIDEOState = OPENBandwidth = 374 kbpsTime created = 731146318 msChannel number = 1Type = AUDIOState = OPENBandwidth = 81 kbpsTime created = 731146317 msH245 logical channels for call leg pte111@zone1.com<->50.0.0.41:Channel number = 2Type = VIDEOState = OPENBandwidth = 374 kbpsTime created = 731146317 msChannel number = 1Type = AUDIOState = OPENBandwidth = 81 kbpsTime created = 731146316 msChannel number = 2Type = VIDEOState = OPENBandwidth = 374 kbpsTime created = 731146318 msChannel number = 1Type = AUDIOState = OPENBandwidth = 81 kbpsTime created = 731146317 msThe following is sample output from the show proxy h323 detail-call command with the proxy statistics enabled:
Router# show proxy h323 detail-call 1ConferenceID = [677EB106BD0D111976200002424F832]Calling endpoint call signalling address = 172.21.127.49Calling endpoint aliases:H323_ID: intel2E164_ID: 2134Called endpoint aliases:H323_ID: mcs@sanjose.cisco.comPeer proxy call signalling address = 171.68.183.199Peer proxy aliases:H323_ID: proxy.sanjose.cisco.comTime call was initiated = 730949651 msInbound CRV = 2505Outbound CRV = 67Call state = H245 open logical channelsH245 logical channels for call leg intel2 <-> cisco7-pxy:Channel number = 259RTP stream from intel2 to cisco7-pxyType = VIDEOState = OPENBandwidth = 225 kbpsTime created = 730949676 msChannel number = 257RTP stream from intel2 to cisco7-pxyType = AUDIOState = OPENBandwidth = 18 kbpsTime created = 730949658 msChannel number = 2RTP stream from cisco7-pxy to intel2Type = VIDEOState = OPENBandwidth = 225 kbpsTime created = 730949664 msRTP Statistics:Packet Received Count = 3390Packet Dropped Count = 0Packet Out of Sequence Count = 0Number of initial packets used for Arrival-Spacing bin setup = 200min_arrival_spacing = 0(ms) max_arrival_spacing = 856(ms)Average Arrival Rate = 86(ms)Arrival-Spacing(ms) Packet-Count0 211626 48752 2678 0104 0130 1156 0182 1208 0234 4260 99286 315312 154338 8364 0390 2416 10442 73468 51494 43==============================Min Jitter = 34(ms) Max Jitter = 408(ms)Average Jitter Rate = 117Jitter Rate(ms) Packet-Count0 041 51482 2117Number of initial packets used for Arrival-Spacing bin setup = 200min_arrival_spacing = 32(ms) max_arrival_spacing = 96(ms)Average Arrival Rate = 60(ms)Arrival-Spacing(ms) Packet-Count32 3534 036 17738 040 5642 044 1046 048 2750 052 54154 056 264258 160 106962 064 77 068 670 257==============================Min Jitter = 0(ms) Max Jitter = 28(ms)Average Jitter Rate = 5Jitter Rate(ms) Packet-Count0 10693 27206 09 80412 2715 1018 021 5624 17727 35H245 logical channels for call leg cisco7-pxy <->proxy.sanjose.cisco.com:Channel number = 259RTP stream from cisco7-pxy to proxy.sanjose.cisco.comType = VIDEOState = OPENBandwidth = 225 kbpsTime created = 730949676 msRTP Statistics:Packet Received Count = 3398Packet Dropped Count = 1Packet Out of Sequence Count = 0Number of initial packets used for Arrival-Spacing bin setup = 200min_arrival_spacing = 0(ms) max_arrival_spacing = 872(ms)Average Arrival Rate = 85(ms)Arrival-Spacing(ms) Packet-Count0 263628 056 084 0112 0140 1168 0196 0224 0252 0280 2308 425336 154364 5392 0420 0448 0476 114504 41532 20==============================Min Jitter = 55(ms) Max Jitter = 447(ms)Average Jitter Rate = 127Jitter Rate(ms) Packet-Count0 045 190 2636135 0180 2225 425270 159315 0360 0405 175Channel number = 257RTP stream from cisco7-pxy to proxy.sanjose.cisco.comType = AUDIOState = OPENBandwidth = 18 kbpsTime created = 730949658 msRTP Statistics:Packet Received Count = 2537Packet Dropped Count = 3Packet Out of Sequence Count = 0Number of initial packets used for Arrival-Spacing bin setup = 200min_arrival_spacing = 0(ms) max_arrival_spacing = 32716(ms)Average Arrival Rate = 112(ms)Arrival-Spacing(ms) Packet-Count0 219172 253144 31216 7288 3360 4432 4504 2576 1648 3720 2792 1864 2936 11008 11080 11152 11224 11296 01368 28==============================Min Jitter = 32(ms) Max Jitter = 1256(ms)Average Jitter Rate = 121Jitter Rate(ms) Packet-Count0 284126 2201252 4378 6504 4630 3756 2882 21008 21134 29Channel number = 2RTP stream from proxy.sanjose.cisco.com to cisco7-pxyType = VIDEOState = OPENBandwidth = 225 kbpsTime created = 730949664 msChannel number = 1RTP stream from proxy.sanjose.cisco.com to cisco7-pxyType = AUDIOState = OPENBandwidth = 18 kbpsTime created = 730949661 msRelated Commands
show proxy h323 status
To display the overall status of a proxy, use the show proxy h323 status command in privileged EXEC mode.
show proxy h323 status
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3(2)NA
This command was introduced.
12.0(3)T
The command was integrated into Cisco IOS Release 12.0(3)T and supported on the Cisco MC3810 multiservice concentrator.
Examples
The following is sample output from the show proxy h323 status command:
Router# show proxy h323 statusH.323 Proxy Status==================H.323 Proxy Mode: EnabledProxy interface = Serial1: UPApplication Specific Routing: DisabledRAS Initialization: CompleteProxy aliases configured:H323_ID: px2Proxy aliases assigned by Gatekeeper:H323_ID: px2Gatekeeper multicast discovery: DisabledGatekeeper:Gatekeeper ID: gk.zone2.comIP address: 70.0.0.31Gatekeeper registration succeededT.120 Mode: BYPASSRTP Statistics: OFFNumber of calls in progress: 1show rawmsg
To show the raw messages owned by the required component, use the show rawmsg command in privileged EXEC mode.
show rawmsg {all | tsp | vtsp | ccapi | h323}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(7)T
This command was introduced on the Cisco AS5300 universal access server.
Usage Guidelines
The number displayed for show rawmsg all should be zero to indicate that there are no memory leaks.
Examples
The following example shows how to display memory leaks from the telephony service provider:
Router# show rawmsg tspRelated Commands
show rlm group statistics
To display the network latency of the Redundant Link Manager (RLM) group, use the show rlm group statistics command in privileged EXEC mode.
show rlm group group-number statistics
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show rlm group group-number statistics command:
Router# show rlm group 1 statisticsRLM Group 1 StatisticsLink_up:last time occurred at 02:45:48.724, total transition=1avg=00:00:00.000, max=00:00:00.000, min=00:00:00.000, latest=00:00:00.000Link_down:last time occurred at 02:42:33.724, total transition=1avg=00:03:15.000, max=00:03:15.000, min=00:00:00.000, latest=00:03:15.000Link_recovered:last time occurred at 00:00:00.000, success=0(0%), failure=0avg=0.000s, max=0.000s, min=0.000s, latest=0.000sLink_switched:last time occurred at 00:00:00.000, success=0(0%), failure=0avg=0.000s, max=0.000s, min=0.000s, latest=0.000sServer_changed:last time occurred at 00:00:00.000 for totally 0 timesServer Link Group[r1-server]:Open the link [10.1.1.1(Loopback1), 10.1.4.1]:last time occurred at 02:43:03.724, success=1(100%), failure=0avg=162.000s, max=162.000s, min=0.000s, latest=162.000sEcho over link [10.1.1.1(Loopback1), 10.1.4.1]:last time occurred at 02:47:15.724, success=91(62%), failure=54avg=0.000s, max=0.000s, min=0.000s, latest=0.000sOpen the link [10.1.1.2(Loopback2), 10.1.4.2]:last time occurred at 02:43:03.724, success=1(100%), failure=0avg=162.000s, max=162.000s, min=0.000s, latest=162.000sEcho over link [10.1.1.2(Loopback2), 10.1.4.2]:last time occurred at 02:47:19.724, success=95(63%), failure=54avg=0.000s, max=0.000s, min=0.000s, latest=0.000sServer Link Group[r2-server]:Open the link [10.1.1.1(Loopback1), 10.1.5.1]:last time occurred at 02:46:06.724, success=0(0%), failure=1avg=0.000s, max=0.000s, min=0.000s, latest=0.000sEcho over link [10.1.1.1(Loopback1), 10.1.5.1]:last time occurred at 02:47:18.724, success=0(0%), failure=85avg=0.000s, max=0.000s, min=0.000s, latest=0.000sOpen the link [10.1.1.2(Loopback2), 10.1.5.2]:last time occurred at 02:46:06.724, success=0(0%), failure=1avg=0.000s, max=0.000s, min=0.000s, latest=0.000sEcho over link [10.1.1.2(Loopback2), 10.1.5.2]:last time occurred at 02:47:18.724, success=0(0%), failure=85avg=0.000s, max=0.000s, min=0.000s, latest=0.000sRouter#Table 51 describes the significant fields shown in the display.
Related Commands
show rlm group status
To display the status of the Redundant Link Manager (RLM) group, use the show rlm group status command in privileged EXEC mode.
show rlm group group-number status
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show rlm group group-number status command:
Router# show rlm group 1 statusRLM Group 1 StatusUser/Port: RLM_MGR/3000Link State: Up Last Link Status Reported: UpNext tx TID: 1 Last rx TID: 0Server Link Group[r1-server]:link [10.1.1.1(Loopback1), 10.1.4.1] = socket[active]link [10.1.1.2(Loopback2), 10.1.4.2] = socket[standby]Server Link Group[r2-server]:link [10.1.1.1(Loopback1), 10.1.5.1] = socket[opening]link [10.1.1.2(Loopback2), 10.1.5.2] = socket[opening]Table 52 describes the significant fields shown in the display.
Related Commands
show rlm group timer
To display the current timer values, use the show rlm group timer command in privileged EXEC mode.
show rlm group group-number timer
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show rlm group group-number timer command:
Router# show rlm group 1 timerRLM Group 1 Timer Valuesopen_wait = 3s force-down = 30srecovery = 12s switch-link = 5sminimum-up = 60s retransmit = 1skeepalive = 1sTable 90 describes the significant fields shown in the display.
Related Commands
show rtsp client session
To display cumulative information about Real Time Streaming Protocol (RTSP) session records, use the show rtsp client session command in privileged EXEC mode. To set the value to the default, use the no form of this command.
show rtsp client session {history | active} [detailed]
no show rtsp client session {history | active} [detailed]
Syntax Description
Defaults
Active (current) stream information is displayed.
Command Modes
Privileged EXEC
Command History
12.1(3)T
This command was introduced on the Cisco AS5300 universal access server.
Usage Guidelines
Use this command to display cumulative information about the session, packet statistics, and general call information such as call ID, session ID, and so on.
Note
A call leg could play several prompts in a session; the "Play Time" refers to the play time associated with a stream or, in other words, a prompt; the cumulative play time is the sum total of all streams (or prompts) played out in a session.
The command output is a stream block that contains information about the stream (URL, packet statistics, current state of the stream, play duration, call ID, session ID, individual RTSP stream URLs, and packet statistics).
Examples
The following output is displayed when the show rtsp client session active command is used during an active session:
Router# show rtsp client session activeRTSP Session ID:0x8 Current Status:RTSP_STATUS_PLAYINGAssociated CallID:0xFActive Request:RTSP_API_REQ_PLAYControl Protocol:TCP Data Protocol:RTPTotal Packets Transmitted:0 (0 bytes)Total Packets Received:708 (226560 bytes)Cumulative Elapsed Play Time:00:00:28.296Cumulative Elapsed Record Time:00:00:00.000Session ID:0x8 State:ACTIVELocal IP Address:1.13.79.45 Local Port 16660Server IP Address:1.13.79.6 Server Port 11046Stream URL:rtsp://rtsp-cisco.cisco.com:554/chinna.au/streamid=0Packets Transmitted:0 (0 bytes)Packets Received:708 (226560 bytes)Elapsed Play Time:00:00:28.296Elapsed Record Time:00:00:00.000ReceiveDelay:85 LostPackets:0The following output is displayed when the show rtsp client session history detailed command is used:
Router# show rtsp client session history detailedRTSP Session ID:0x8Associated CallID:0xFControl Protocol:TCP Data Protocol:RTPTotal Packets Transmitted:0 (0 bytes)Total Packets Received:2398 (767360 bytes)Cumulative Elapsed Play Time:00:01:35.916Cumulative Elapsed Record Time:00:00:00.000Session ID:0x8 State:INACTIVELocal IP Address:1.13.79.45 Local Port 16660Server IP Address:1.13.79.6 Server Port 11046Stream URL:rtsp://rtsp-cisco.cisco.com:554/chinna.au/streamid=0Packets Transmitted:0 (0 bytes)Packets Received:2398 (767360 bytes)Play Time:00:01:35.916Record Time:00:00:00.000OntimeRcvPlayout:93650GapFillWithSilence:0GapFillWithPrediction:70GapFillWithInterpolation:0GapFillWithRedundancy:0HighWaterPlayoutDelay:85LoWaterPlayoutDelay:64ReceiveDelay:85 LostPackets:0EarlyPackets:2 LatePackets:12Related Commands
show rudpv0 failures
To show SS7 Reliable User Datagram Protocol (RUDP) failure statistics, enter the show rudpv0 failures command in privileged EXEC mode.
show rudpv0 failures
Syntax Description
There are no keywords or arguments.
Defaults
There are no default behaviors or values.
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into
Cisco IOS Release 12.1(1)T.
Examples
The following example shows the display of RUDP failures. The fields are self-explanatory.
show rudpv0 failures**** RUDP Failure Stats ****CreateBufHdrsFailure 0CreateConnRecsFailure 0CreateEventsFailure 0NotReadyFailures 0OptionNotSupportedFailures 0OptionRequiredFailures 0GetConnRecFailures 0InvalidConnFailures 0EventUnavailFailures 0EmptyBufferSendFailures 0BufferTooLargeFailures 0ConnNotOpenFailures 0SendWindowFullFailures 0GetBufHdrSendFailures 0GetDataBufFailures 0GetBufHdrFailures 0SendEackFailures 0SendAckFailures 0SendSynFailures 0SendRstFailures 0SendNullFailures 0TimerNullFailures 0FailedRetransmits 0IncomingPktsDropped 0UnknownRudpEvents 0Related Commands
show rudpv0 statistics
To show SS7 Reliable User Datagram Protocol (RUDP) internal statistics, enter the
show rudpv0 statistics privileged EXEC command.show rudpv0 statistics
Syntax Description
There are no keywords or arguments.
Defaults
There are no default behaviors or values.
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
Because the statistics counters are continually updated, the cumulative total may not be exactly equal to individual connection counters. After a connection is reset, previous statistics are lost, so the current connection statistics reflect only this instance of the RUDP connection—since the last reset.
Cumulative statistics reflect counts since the router was rebooted or since the last time the
clear rudpv0 statistics command was issued.Examples
The following example shows the display of RUDP statistics and states for two connections. The fields are self-explanatory.
show rudpv0 statistics*** RUDP Internal Stats ****Connection ID: 811641AC, Current State: OPENRcvdInSeq 1RcvdOutOfSeq 0SoftResets 0SoftResetsRcvd 0TotalPacketsSent 4828TotalPacketsReceived 4826TotalDataBytesSent 0TotalDataBytesReceived 4TotalDataPacketsSent 0TotalDataPacketsReceived 1TotalPacketsRetrans 0TotalPacketsDiscarded 0Connection ID: 81163FD4, Current State: OPENRcvdInSeq 2265RcvdOutOfSeq 0SoftResets 0SoftResetsRcvd 0TotalPacketsSent 7863TotalPacketsReceived 6755TotalDataBytesSent 173690TotalDataBytesReceived 56121TotalDataPacketsSent 2695TotalDataPacketsReceived 2265TotalPacketsRetrans 0TotalPacketsDiscarded 0Cumulative RudpV0 StatisticsRcvdInSeq 2266RcvdOutOfSeq 0SoftResets 0SoftResetsRcvd 0TotalPacketsSent 12691TotalPacketsReceived 11581TotalDataBytesSent 173690TotalDataBytesReceived 56125TotalDataPacketsSent 2695TotalDataPacketsReceived 2266TotalPacketsRetrans 0TotalPacketsDiscarded 0Related Commands
show rudpv1
To display Reliable User Datagram Protocol (RUDP) information, use the show rudpv1 command in privileged EXEC mode.
show rudpv1 { failures | parameters | statistics }
Syntax Description
failures
RUDP failure statistics.
parameters
RUDP connection parameters.
statistics
RUDP internal statistics.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Because the statistics counters are continually updated, the cumulative total may not be exactly equal to individual connection counters. After a connection is reset, previous statistics are lost, so the current connection statistics reflect only this instance of the RUDP connection—since the last reset.
Cumulative statistics reflect counts since the router was rebooted or since the last time the clear rudpv1 statistics command was issued.
Examples
The following example shows sample output for show rudpv1 failures:
Router# show rudpv1 failures**** RUDPV1 Failure Stats ****CreateBufHdrsFailure 0CreateConnRecsFailure 0CreateEventQueueFailure 0OsSpecificInitFailure 0NotReadyFailures 0OptionNotSupportedFailures 0InvalidOptionFailures 0OptionRequiredFailures 0GetConnRecFailures 0InvalidConnFailures 0EventUnavailFailures 0GetConnRecFailures 0FindConnRecFailures 0EmptyBufferSendFailures 0BufferTooLargeFailures 0ConnNotOpenFailures 0SendWindowFullFailures 0GetBufHdrSendFailures 0SendInProgressFailures 0GetDataBufFailures 0GetBufHdrFailures 0SendFailures 0SendEackFailures 0SendAckFailures 0SendSynFailures 0SendRstFailures 0SendTcsFailures 0SendNullFailures 0TimerFailures 0ApplQueueFailures 0FailedRetransmits 0IncomingPktsDropped 0CksumErrors 0UnknownRudpv1Events 0InvalidVersion 0InvalidNegotiation 0The following example shows sample output for show rudpv1 parameters:
Router# show rudpv1 parameters*** RUDPV1 Connection Parameters ***Next Connection Id:61F72B6C, Remote conn id 126000Conn State OPENConn Type ACTIVEAccept Negot params? YesReceive Window 32Send Window 32Receive Seg Size 384Send Seg Size 384Requested NegotiatedMax Auto Reset 5 5Max Cum Ack 3 3Max Retrans 2 2Max OutOfSeq 3 3Cum Ack Timeout 100 100Retrans Timeout 300 300Null Seg Timeout 1000 1000Trans State Timeout 2000 2000Cksum type Hdr HdrNext Connection Id:61F72DAC, Remote conn id 126218Conn State OPENConn Type ACTIVEAccept Negot params? YesReceive Window 32Send Window 32Receive Seg Size 384Send Seg Size 384Requested NegotiatedMax Auto Reset 5 5Max Cum Ack 3 3Max Retrans 2 2Max OutOfSeq 3 3Cum Ack Timeout 100 100Retrans Timeout 300 300Null Seg Timeout 1000 1000Trans State Timeout 2000 2000Cksum type Hdr HdrThe following example shows sample output for show rudpv1 statistics:
Router# show rudpv1 statistics*** RUDPV1 Internal Stats ****Connection ID:61F72B6C, Current State:OPENRcvdInSeq 647RcvdOutOfSeq 95AutoResets 0AutoResetsRcvd 0TotalPacketsSent 1011TotalPacketsReceived 958TotalDataBytesSent 17808TotalDataBytesReceived 17808TotalDataPacketsSent 742TotalDataPacketsReceived 742TotalPacketsRetrans 117TotalPacketsDiscarded 38Connection ID:61F72DAC, Current State:OPENRcvdInSeq 0RcvdOutOfSeq 0AutoResets 0AutoResetsRcvd 0TotalPacketsSent 75TotalPacketsReceived 75TotalDataBytesSent 0TotalDataBytesReceived 0TotalDataPacketsSent 0TotalDataPacketsReceived 0TotalPacketsRetrans 0TotalPacketsDiscarded 0Cumulative RudpV1 StatisticsNumCurConnections 2RcvdInSeq 652RcvdOutOfSeq 95AutoResets 0AutoResetsRcvd 0TotalPacketsSent 1102TotalPacketsReceived 1047TotalDataBytesSent 18048TotalDataBytesReceived 18048TotalDataPacketsSent 752TotalDataPacketsReceived 752TotalPacketsRetrans 122TotalPacketsDiscarded 38Related Commands
clear rudpv1 statistics
Clears the RUDP statistics counters.
debug rudpv1
Displays debugging information for RUDP.
show settlement
To display the configuration for all settlement servers and see the specific provider and transactions, use the show settlement command in privileged EXEC mode. To reset to the default value, use the no form of this command.
show settlement [provider-number [transactions]]
no show settlement [provider-number [transactions]]
Syntax Description
provider-number
(Optional) Displays the attributes of a specific provider.
transactions
(Optional) Displays the transaction status of a specific provider.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows information about all settlement servers configured:
Router# show settlementSettlement Provider 0Type = ospAddress url = https://1.14.115.100:6556/Encryption = all (default)Max Concurrent Connections = 20 (default)Connection Timeout = 3600 (s) (default)Response Timeout = 1 (s) (default)Retry Delay = 2 (s) (default)Retry Limit = 1 (default)Session Timeout = 86400 (s) (default)Customer Id = 1000Device Id = 1000Roaming = Disabled (default)Signed Token = onNumber of Connections = 0Number of Transactions = 7The following example shows transaction and state information about a specific settlement server:
Router# show settlement 0 transactionsTransaction ID=8796304133625270342state=OSPC_GET_DEST_SUCCESS, index=0callingNumber=5710868, calledNumber=15125551212Table 54 describes the significant fields shown in the display. The provider attributes not configured are not shown.
.
Related Commands
show sgcp connection
To see all active SGCP connections on this router, use the show sgcp connection command in EXEC mode.
show sgcp connection [interface number]
Syntax Description
interface
(Optional) Specifies a DS1 interface.
number
(Optional) Specifies the T1 interface (controller) number. Valid values on the Cisco MC3810 multiservice concentrator are from 0 to 1.
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
If you do not specify an interface, this command shows all the active SGCP connections on this host. If you specify an interface, this command shows only those active connections on the specified interface.
Examples
The following example shows the active connections on this router being displayed:
Router# show sgcp connectionEndpoint Call_ID(C) Conn_ID(I) (P)ort (M)ode (S)tate (E)vent[SIFL] (R)esult[EA]1. ds1-0/1@r3810-5 C=1,1,2 I=0x1 P=16492,16476 M=3 S=4 E=3,0,0,3 R=0, 0The following example shows the state of SGCP on the router being displayed:
Router# show sgcp connectionSGCP Admin State DOWN, Oper State DOWNSGCP call-agent: 209.165.200.225 , SGCP graceful-shutdown enabled? FALSESGCP request timeout 40, SGCP request retries 10Table 55 describes the significant fields shown in the display.
Related Commands
show sgcp endpoint
Displays SGCP endpoint information.
show sgcp statistics
Displays global statistics for the SGCP packet count, success, and failure counts.
show sgcp endpoint
To see SGCP endpoints eligible for SGCP management, use the show sgcp endpoint command in EXEC mode.
show sgcp endpoint [interface ds1 [ds0]]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
You can use this command to see SGCP endpoint information for the whole router, or you can see SGCP endpoint information for a specific DS1 interface and, optionally, a specific DS0. If you enter a nonexistent combination of a DS1 and DS0, the following error message appears: "No matching connection found."
Examples
The following command shows SGCP endpoint information being set for a matching connection between DS1 interface 1 and DS0 interface 10:
Router# show sgcp endpoint interface 1 10Related Commands
show sgcp statistics
To see global statistics for the SGCP packet count, success and failure counts, and other information, use the show sgcp statistics command in EXEC mode.
show sgcp statistics
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Examples
The following example shows SGCP packet statistics being displayed:
Router# show sgcp statisticsUDP pkts rx 5, tx 13Unrecognized rx pkts 0, SGCP message parsing errors 0Duplicate SGCP ack tx 0Failed to send SGCP messages 0CreateConn rx 1, successful 1, failed 0DeleteConn rx 0, successful 0, failed 0ModifyConn rx 0, successful 0, failed 0DeleteConn tx 0, successful 0, failed 0NotifyRequest rx 3, successful 3, failed 0Notify tx 3, successful 3, failed 0ACK tx 4, NACK tx 0ACK rx 1, NACK rx 0IP address based Call Agents statistics:IP address 1.4.63.100, Total msg rx 5,successful 5, failed 2The following examples show how you can filter the command return for specific information:
Router# show sgcp statistics | begin FailedFailed to send SGCP messages 0CreateConn rx 0, successful 0, failed 0DeleteConn rx 0, successful 0, failed 0ModifyConn rx 0, successful 0, failed 0DeleteConn tx 0, successful 0, failed 0NotifyRequest rx 0, successful 0, failed 0Notify tx 0, successful 0, failed 0ACK tx 0, NACK tx 0ACK rx 0, NACK rx 0Router# show sgcp statistics | exclude ACKUDP pkts rx 0, tx 0Unrecognized rx pkts 0, SGCP message parsing errors 0Duplicate SGCP ack tx 0Failed to send SGCP messages 0CreateConn rx 0, successful 0, failed 0DeleteConn rx 0, successful 0, failed 0ModifyConn rx 0, successful 0, failed 0DeleteConn tx 0, successful 0, failed 0NotifyRequest rx 0, successful 0, failed 0Notify tx 0, successful 0, failed 0Router# show sgcp statistics | include ACKACK tx 0, NACK tx 0ACK rx 0, NACK rx 0Related Commands
show sgcp connection
Display all the active connections on the host Cisco AS5300 universal access server.
show sgcp endpoint
Displays SGCP endpoint information.
show sip-ua
To display information and settings for the Session Initiation Protocol (SIP) User Agent (UA), use the show sip-ua command in privileged EXEC mode.
show sip-ua {retry | statistics | status | timers}
Syntax Description
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example displays output for the show sip-ua retry command:
Router# show sip-ua retrySIP UA Retry Valuesinvite retry count = 2response retry count = 2bye retry count = 2cancel retry count = 1The following example displays output for the show sip-ua statistics command:
Router# show sip-ua statisticsSIP Response Statistics (Inbound/Outbound)Informational:Trying 0/0, Ringing 0/0,Forwarded 0/0, Queued 0/0,SessionProgress 0/0Success:OkInvite 0/0, OkBye 0/0,OkCancel 0/0, OkOptions 0/0Redirection (Inbound only):MultipleChoice 0, MovedPermanently 0,MovedTemporarily 0, SeeOther 0,UseProxy 0, AlternateService 0Client Error:BadRequest 0/0, Unauthorized 0/0,PaymentRequired 0/0, Forbidden 0/0,NotFound 0/0, MethodNotAllowed 0/0,NotAcceptable 0/0, ProxyAuthReqd 0/0,ReqTimeout 0/0, Conflict 0/0, Gone 0/0,LengthRequired 0/0, ReqEntityTooLarge 0/0,ReqURITooLarge 0/0, UnsupportedMediaType 0/0,BadExtension 0/0, TempNotAvailable 0/0,CallLegNonExistent 0/0, LoopDetected 0/0,TooManyHops 0/0, AddrIncomplete 0/0,Ambiguous 0/0, BusyHere 0/0Server Error:InternalError 0/0, NotImplemented 0/0,BadGateway 0/0, ServiceUnavail 0/0,GatewayTimeout 0/0, BadSipVer 0/0Global Failure:BusyEverywhere 0/0, Decline 0/0,NoExistAnywhere 0/0, NotAcceptable 0/0SIP Total Traffic Statistics (Inbound/Outbound)Invite 0/0, Ack 0/0, Bye 0/0,Cancel 0/0, Options 0/0Retry StatisticsInvite 0, Bye 0, Cancel 0, Response 0The following example displays output for the show sip-ua status command:
Router# show sip-ua statusSIP User Agent StatusSIP User Agent for UDP :ENABLEDSIP User Agent for TCP :ENABLEDSIP max-forwards :6The following example displays output for the show sip-ua timers command:
Router# show sip-ua timersSIP UA Timer Values (millisecs)trying 500, expires 180000, connect 500, disconnect 500Related Commands
sip-ua
Enables the SIP user-agent configuration commands, with which you configure the user agent.
show ss7 mtp2 ccb
To display SS7 MTP 2 Channel Control Block (CCB) information, use the show ss7 mtp2 ccb command in privileged EXEC mode.
show ss7 mtp2 ccb [channel]
Syntax Description
Defaults
The default is set when you first configure the MTP 2 variant. The link must be out of service in order to change the MTP 2 variant.
If you do not specify a channel, the command shows Channel Control Block information for channel 0.
Command Modes
Privileged EXEC
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The application and meaning of the output is dependent on the MTP 2 variant. For example, NTT and TTC only support emergency alignment.
Examples
The following example shows the display of MTP 2 CCB information:
Router# show ss7 mtp2 ccb 0SS7 MTP2 Internal Channel Control Block Info for channel 0Protocol version for channel 0 is Japan NTT Q.703 Version 1-1ModuloSeqNumber = 128 (0x80 )MaxSeqNumber = 127 (0x7F )Unacked-MSUs (MaxInRTB) = 40 (0x28 )MaxProvingAttempts = 5 (0x5 )error_control = BasicLSSU_Len = 1 (0x1 )MSU_Len = 272 (0x110 )SUERM-threshold = 64 (0x40 )SUERM-number-octets = 16 (0x10 )SUERM-number-SUs = 256 (0x100 )Tie-AERM-Emergency = 1 (0x1 )Tin-AERM-Normal = 1 (0x1 )MSU_FISU_Accepted_flag = FALSELSSU_available = TRUEAbnormalBSN_flag = FALSEAbnormalBSN_flag = FALSEUnreasonableBSN = FALSEUnreasonableFSN = FALSEAbnormal_FIBR_flag = FALSEcongestionDiscard = TRUEThisIsA_MSU = FALSElocal_processor_outage = FALSEremote_processor_outage = FALSEprovingEmergencyFlag = FALSERemoteProvingEmergencyFlag = FALSEfurther_proving_required = FALSEForceRetransmitFlag = FALSERetransmissionFlag = FALSElink_present = FALSEDebug Mask = 0x0show ss7 mtp2 state
To display internal SS7 Message Transfer Part level 2 (MTP 2) state machine information, use the show ss7 mtp2 state command in privileged EXEC mode.
show ss7 mtp2 state [channel]
Syntax Description
Defaults
If you do not specify a channel, the command shows state machine information for channel 0.
Command Modes
Privileged EXEC
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Examples
The following examples show the display of MTP 2 state machine information for two different channels. Table 56 explains the fields.
Router# show ss7 mtp2 state 0SS7 MTP2 states for channel 0Protocol version for channel 0 is Japan NTT Q.703 Version 1-1MTP2LSC_OOS MTP2IAC_IDLEMTP2TXC_INSERVICE MTP2RC_IDLEMTP2SUERM_IDLE MTP2AERM_IDLEMTP2CONGESTION_IDLECongestion Backhaul = AbateRemote Processor Outage = FALSERouter# show ss7 mtp2 state 1SS7 MTP2 states for channel 1Protocol version for channel 1 is Japan NTT Q.703 Version 1-1MTP2LSC_OOS MTP2IAC_IDLEMTP2TXC_INSERVICE MTP2RC_IDLEMTP2SUERM_IDLE MTP2AERM_IDLEMTP2CONGESTION_IDLECongestion Backhaul = AbateRemote Processor Outage = FALSE
show ss7 mtp2 stats
To display SS7 MTP 2 operational statistics, use the show ss7 mtp2 stats command in privileged EXEC mode.
show ss7 mtp2 stats [channel]
Syntax Description
Defaults
If you do not specify a channel, the command shows status information for channel 0.
Command Modes
Privileged EXEC
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Examples
The following example shows operations and maintenance (OM) statistics for MTP 2 channel 0. Table 57 explains some of the fields.
Router# show ss7 mtp2 stats 0SS7 MTP2 Statistics for channel 0Protocol version for channel 0 is Japan NTT Q.703 Version 1-1OMIACAlignAttemptCount = 0OMIACAlignFailCount = 0OMIACAlignCompleteCount = 0OMMSU_TO_XMIT_Count = 0OMMSU_XMIT_Count = 0OMMSU_RE_XMIT_Count = 0OMMSU_RCV_Count = 0OMMSU_Posted_Count = 0OMMSU_too_long = 0OMFISU_XMIT_Count = 0OMFISU_RCV_Count = 0OMLSSU_XMIT_Count = 17OMLSSU_XMIT_SINCount = 0OMLSSU_XMIT_SIECount = 0OMLSSU_XMIT_SIOCount = 0OMLSSU_XMIT_SIOSCount = 17OMLSSU_XMIT_SIPOCount = 0OMLSSU_XMIT_SIBCount = 0OMLSSU_RCV_Count = 0OMLSSU_RCV_SINCount = 0OMLSSU_RCV_SIECount = 0OMLSSU_RCV_SIOCount = 0OMLSSU_RCV_SIOSCount = 0OMLSSU_RCV_SIPOCount = 0OMLSSU_RCV_SIBCount = 0OMLSSU_RCV_InvalidCount = 0OMRemote_PO_Count = 0OMRemote_Congestion_Cnt = 0OMtimeINSV (secs) = 0OMtimeNotINSV (secs) = 9550OMMSUBytesTransmitted = 0OMMSUBytesReceived = 0OMTransmitReqCount = 33OMPDU_notAcceptedCount = 0OMPDU_NACK_Count = 0OMunreasonableFSN_rcvd = 0OMunreasonableBSN_rcvd = 0OMT1_TMO_Count = 0OMT2_TMO_Count = 0OMT3_TMO_Count = 0OMT4_TMO_Count = 0OMT5_TMO_Count = 0OMT6_TMO_Count = 0OMT7_TMO_Count = 0OMT8_TMO_Count = 0OMTA_TMO_Count = 0OMTF_TMO_Count = 0OMTO_TMO_Count = 0OMTS_TMO_Count = 477218OMLostTimerCount = 0OMOMLostBackHaulMsgs = 0OMAERMCount = 0OMAERMFailCount = 0OMSUERMCount = 0OMSUERMFailCount = 0OMCongestionCount = 0OMCongestionBackhaulCnt = 0
show ss7 mtp2 timer
To display durations of the SS7 MTP 2 state machine timers, use the show ss7 mtp2 timer command in privileged EXEC mode.
show ss7 mtp2 timer [channel]
Note
Syntax Description
Defaults
If you do not specify a channel, the command shows status information for channel 0.
Command Modes
Privileged EXEC
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
MTP 2 uses eight different timers on each link. Throughout the link state transitions, multiple timers are active. An in-service MTP 2 link requires timers that are constantly started, stopped, and restarted. Use this command to display the configured timer durations.
Note
Examples
The following example shows how to display timer information for channel 0:
Router# show ss7 mtp2 timer 0SS7 MTP2 Timers for channel 0 in millisecondsProtocol version for channel 0 is Japan NTT Q.703 Version 1-1T1 aligned/ready = 15000T2 not aligned = 5000T3 aligned = 3000T4 Emergency Proving = 3000T4 Normal Proving = 3000T5 sending SIB = 200T6 remote cong = 3000T7 excess ack delay = 2000T8 errored int mon = 0TA SIE timer = 20TF FISU timer = 20TO SIO timer = 20TS SIOS timer = 20show ss7 mtp2 variant
To display information about the SS7 MTP 2 protocol variant, use the show ss7 mtp2 variant command in privileged EXEC mode.
show ss7 mtp2 variant [channel]
Syntax Description
Defaults
If you do not specify a channel, the command shows protocol information for channel 0.
Command Modes
Privileged EXEC
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
Each country specifies its own variant of SS7, and the Cisco SLT supports several variants of the MTP 2 protocol. The selected variant can affect the MTP 2 statistics displayed by various commands. The Cisco SLT support the following variants:
•
•
•
•
Each channel can be configured to any one of the protocol variants. When you change from one variant to another, for example from Bellcore to NTT, the MTP 2 parameters default to those specified by NTT. You can then change the defaults as required.
Examples
The following example shows how to display protocol variant information for channel 1:
Router# show ss7 mtp2 variant 1Protocol version for channel 1 is Bellcore GR-246-Core Issue 2, Dec 1997show ss7 sm session
To display information about SS7 Session Manager session, use the show ss7 sm session command in privileged EXEC mode.
show ss7 sm session [session]
Syntax Description
Defaults
If you do not specify a session, the command shows information for both sessions.
Command Modes
Privileged EXEC
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
If no sessions are configured, the message "No Session is configured" appears.
Examples
The following example shows how to display session information for both sessions. Table 58 explains the fields.
Router# show ss7 sm sessionSession[0]: Remote Host 255.255.251.254:8060, Local Host 255.255.255.254:8060retrans_t = 600cumack_t = 300kp_t = 2000m_retrans = 2m_cumack = 3m_outseq = 3m_rcvnum = 32Session[1]: Remote Host 255.255.251.255:8061, Local Host 255.255.255.254:8061retrans_t = 600cumack_t = 300kp_t = 2000m_retrans = 2m_cumack = 3m_outseq = 3m_rcvnum = 32
Related Commands
show ss7 sm set
To display information about the SS7 failover timer, use the show ss7 sm set command in privileged EXEC mode.
show ss7 sm set
Syntax Description
There are no arguments or keywords.
Defaults
There is no default.
Command Modes
Privileged EXEC
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Examples
The following example shows how to display failover timer information; the failover timer is set to the default of 3 seconds:
Router# show ss7 sm setSession Manager Setfailover timer = 3 secondsRelated Commands
show ss7 sm stats
To display SS7 Session Manager session statistics, use the show ss7 sm stats command in privileged EXEC mode.
show ss7 sm stats
Syntax Description
There are no arguments or keywords for this command.
Defaults
The command shows information for both sessions.
Command Modes
Privileged EXEC
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
If no sessions are configured, the message "No Session is configured" appears.
Examples
The following example shows how to display SS7 Session Manager statistics. The fields are self-explanatory and show information about the session state, protocol data units (PDUs) packets sent and received, and SS7 Reliable User Datagram Protocol (RUDP) performance:
Router# show ss7 sm stats-------------------- Session Manager --------------------Session Manager state = SESSION SET STATE-ACTIVESession Manager Up count = 1Session Manager Down count = 0lost control packet count = 0lost PDU count = 0failover timer expire count = 0invalid_connection_id_count = 0Session[0] statistics SM SESSION STATE-STANDBY:Session Down count = 0Open Retry count = 0Total Pkts receive count = 1Active Pkts receive count = 0Standby Pkts receive count = 1PDU Pkts receive count = 0Unknown Pkts receive count = 0Pkts send count = 0Pkts requeue count = 0-Pkts window full count = 0-Pkts resource unavail count = 0-Pkts enqueue fail count = 0PDUs dropped (Large) = 0PDUs dropped (Empty) = 0RUDP Not Ready Errs = 0RUDP Connection Not Open = 0RUDP Invalid Conn Handle = 0RUDP Unknown Errors = 0RUDP Unknown Signal = 0NonActive Receive count = 0Session[1] statistics SM SESSION STATE-ACTIVE:Session Down count = 0Open Retry count = 0Total Pkts receive count = 2440Active Pkts receive count = 1Standby Pkts receive count = 0PDU Pkts receive count = 2439Unknown Pkts receive count = 0Pkts send count = 2905Pkts requeue count = 0-Pkts window full count = 0-Pkts resource unavail count = 0-Pkts enqueue fail count = 0PDUs dropped (Large) = 0PDUs dropped (Empty) = 0RUDP Not Ready Errs = 0RUDP Connection Not Open = 0RUDP Invalid Conn Handle = 0RUDP Unknown Errors = 0RUDP Unknown Signal = 0NonActive Receive count = 0Related Commands
clear ss7 sm-stats
Clears the counters that track Session Manager statistics for the show ss7 sm stats command.
ss7 session
Establishes a session.
show translation-rule
To display the contents of the rules that have been configured for a specific translation name, use the show translation-rule command in privileged EXEC mode.
show translation-rule [name-tag]
Syntax Description
name-tag
(Optional) The tag number by which the rule set will be referenced. This is an arbitrarily chosen number. The range is from 1 through 2,147,483,647.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command gives detailed information about the configured rules under this rule name. If the name tag is not entered, a complete display of all the configured rules will be shown.
Examples
The following example shows output for the show translation-rule command:
Router# show translation-ruleTranslation rule address:0x61AB94F8Tag name:21Translation rule in_used 1**** Xrule rule table *******Rule :1in_used state:1Match pattern:555.%Sub pattern:1408555Match type:subscriberSub type:international**** Xrule rule table *******Rule :2in_used state:1Match pattern:8.%Sub pattern:1408555Match type:abbreviatedSub type:internationalTranslation rule address:0x61C2E6D4Tag name:345Translation rule in_used 1**** Xrule rule table *******Rule :1in_used state:1Match pattern:.%555.%Sub pattern:7Match type:ANYSub type:abbreviatedTable 59 describes the significant fields shown in the display.
Table 59
show translation-rule Field Descriptions
Related Commands
show vfc
To see the entries in the host-name-and-address cache, use the show vfc command in privileged EXEC mode.
show vfc slot-number [technology]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.3 NA
This command was introduced on the Cisco AS5300 universal access server.
12.0(2)XH
The technology keyword was added.
Examples
The following example shows that the card in slot 1 is a C549 DSPM:
Router# show vfc 1 technologyTechnology in VFC slot 1 is C549Related Commands
show vfc cap-list
To show the current list of files on the capability list for this voice feature card (VFC), use the show vfc cap-list command in user EXEC mode.
show vfc slot cap-list
Syntax Description
Defaults
No default behavior or values.
Command Modes
User EXEC
Command History
11.3 NA
This command was introduced on the Cisco AS5300 universal access server.
Usage Guidelines
To identify the specific VFC, enter the number of the slot on the chassis where the VFC resides using the slot argument.
Examples
The following is sample output from the show vfc cap-list command:
Router# show vfc 1 cap-listCapability List for VFC in slot 1:1. fax-vfc-l.0.1.bin2. bas-vfc-l.0.1.bin3. cdc-g729-l.0.1.bin4. cdc-g711-l.0.1.bin5. cdc-g726-l.0.1.bin6. cdc-g728-l.0.1.bin7. cdc-gsmfr-l.0.1.binThe first line in this output is a general description, stating that this is the capability list for the VFC residing in slot 1. Below this is a numbered list, each line of which identifies one currently installed in-service file.
Related Commands
show vfc default-file
To show the default files included in the default file list for a voice feature card (VFC), use the show vfc default-file command in user EXEC mode.
show vfc slot default-file
Syntax Description
Defaults
No default behavior or values.
Command Modes
User EXEC
Command History
11.3 NA
This command was introduced on the Cisco AS5300 universal access server.
Usage Guidelines
Use the show vfc default-file user EXEC command to display a list of all default files for a particular voice feature card. To identify the specific VFC, enter the number of the slot on the chassis where the VFC resides using the slot argument.
Examples
The following is sample output from the show vfc default-file command:
Router# show vfc 1 default-fileDefault List for VFC in slot 1:1. btl-vfc-l.0.13.0.bin2. cor-vfc-l.0.1.bin3. bas-vfc-l.0.1.bin4. cdc-g729-l.0.1.bin5. fax-vfc-l.0.1.bin6. jbc-vfc-l.0.13.0.binThe first line in this output is a general description, stating that this is the default list for the VFC residing in slot 1. Below this is a numbered list, each line of which identifies one default file.
Related Commands
show vfc directory
To show the list of all files residing on a voice feature card (VFC), use the show vfc directory command in user EXEC mode.
show vfc slot directory
Syntax Description
Defaults
No default behavior or values.
Command Modes
User EXEC
Command History
11.3 NA
This command was introduced on the Cisco AS5300 universal access server.
Usage Guidelines
Use the show vfc directory user EXEC command to display a list of all of the files currently stored in Flash memory for a particular VFC. To identify the specific VFC, enter the number of the slot on the chassis where the VFC resides using the slot argument.
Examples
The following is sample output from the show vfc directory command:
Router# show vfc 1 directoryFiles in slot 1 VFC flash:File Name Size (Bytes)1 . vcw-vfc-mz.gsm.VCW 2926282 . btl-vfc-l.0.13.0.bin 41743 . cor-vfc-l.0.1.bin 545604 . jbc-vfc-l.0.13.0.bin 167605 . fax-vfc-l.0.1.bin 642906 . bas-vfc-l.0.1.bin 544527 . cdc-g711-l.0.1.bin 1908 . cdc-g729-l.0.1.bin 210029 . cdc-g726-l.0.1.bin 19010. cdc-g728-l.0.1.bin 2227011. cdc-gsmfr-l.0.1.bin 190Table 60 describes the significant fields shown in the display.
Table 60 show vfc directory Field Descriptions
File Name
Name of the file stored in Flash memory.
Size (Bytes)
Size of the file in bytes.
Related Commands
show vfc version
To show the version of the software residing on a voice feature card (VFC), use the show vfc version command in user EXEC mode.
show vfc slot version {dspware | vcware}
Syntax Description
slot
Identifies the slot where the VFC is installed. Valid values are 0, 1, and 2.
dspware
Defines which DSPWare software to display.
vcware
Defines which VCWare software to display.
Defaults
No default behavior or values.
Command Modes
User EXEC
Command History
11.3 NA
This command was introduced on the Cisco AS5300 universal access server.
Usage Guidelines
Use the show vfc version user EXEC command to display the version of the software (running on either DSP or VFC) currently installed in Flash memory on the VFC.
Examples
The following is sample output from the show vfc version command:
Router# show vfc 0 version dspwareVersion of Dspware in VFC slot 0 is 0.10The output from this command is a simple declarative sentence stating the version number for the selected type of software (in this example, DSPWare) for the VFC residing in the selected slot number (in this example, slot 0).
Related Commands
show video call summary
To display summary information about video calls and the current status of the Video Call Manager (ViCM), use the show video call summary command in privileged EXEC mode.
show video call summary
Syntax Description
There are no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to look quickly at the status of current calls. In Cisco IOS Releases 12.0(5)XK and 12.0(7)T, there can be only one video call in progress.
Examples
On a Cisco MC3810 multiservice concentrator, the following example displays information about the ViCM when no call is in progress on the serial interface that connects to the local video codec:
Router# show video call summarySerial0:ViCM = Idle, Codec ReadyWhen a call is starting, the output looks like this:
Router# show video call summarySerial0:ViCM = Call ConnectedWhen a call is disconnecting, the output looks like this:
Router# show video call summarySerial0:ViCM = IdleRelated Commands
show voice busyout
To display information about the voice busyout state, use the show voice busyout command in privileged EXEC mode.
show voice busyout
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The show voice busyout command lists the following information:
•
•
Examples
The following example displays the busyout information:
Router# show voice busyoutIf following network interfaces are down, voice port will be put into busyout state ATM0 Serial0 The following voice ports are in busyout state 1/1 is forced into busyout state 1/2 is in busyout state caused by network interfaces 1/3 is in busyout state caused by ATM0 1/4 is in busyout state caused by network interfaces 1/5 is in busyout state caused by Serial0Related Commands
show voice call
To show the call status for voice ports on the Cisco router or concentrator, use the show voice call EXEC command.
Cisco 2600 and 3600 series with Analog Voice Ports
show voice call [slot/subunit/port | summary]
Cisco 2600 and 3600 Series with Digital Voice Ports (with T1 Packet Voice Trunk Network Modules)
show voice call [slot/port:ds0-group | summary]
Cisco MC3810 Multiservice Concentrator with Analog Voice Ports
show voice call [slot/port | summary]
Cisco MC3810 Multiservice Concentrator with Digital Voice Ports
show voice call [slot:ds0-group | summary]
Syntax Description
For the Cisco 2600 and 3600 Series with Analog Voice Ports:
For the Cisco 2600 and 3600 Series with Digital Voice Ports:
For the Cisco MC3810 Multiservice Concentrator with Analog Voice Ports:
For the Cisco MC3810 Multiservice Concentrator with Digital Voice Ports:
Command Modes
EXEC
Command History
Usage Guidelines
The show voice call command applies to Voice over Frame Relay, Voice over ATM, and Voice over IP.
This command shows call-processing and protocol state-machine information for a voice port, if it is available. It also shows information on the DSP channel associated with the voice port, if it is available. All real-time information in the DSP channel, such as jitter and buffer overrun for example, is queried to the DSP channel, and asynchronous responses are returned to the host side.
If no call is active on a voice port, the show voice call summary command displays only the VPM (shutdown) state. If a call is active on a voice port, the VTSPS state is shown. For an on-net call or a local call without local-bypass (not cross-connected), the CODEC and VAD fields are displayed. For an off-net call or a local call with local-bypass, the CODEC and VAD fields are not displayed.
CODEC and VAD are not displayed by the show voice call command because this information is in the summary display.
The show voice call command provides the status at these levels of the call handling module:
•
•
•
•
Examples
The following is a sample display from the show voice call summary command for voice ports on a Cisco MC3810 multiservice concentrator, showing two local calls connected without local bypass:
PORT CODEC VAD VTSP STATE VPM STATE======= ======== === ===================== ========================0:17.18 *shutdown*0:18.19 g729ar8 n S_CONNECT FXOLS_OFFHOOK0:19.20 FXOLS_ONHOOK0:20.21 FXOLS_ONHOOK0:21.22 FXOLS_ONHOOK0:22.23 FXOLS_ONHOOK0:23.24 EM_ONHOOK1/1 FXSLS_ONHOOK1/2 FXSLS_ONHOOK1/3 EM_ONHOOK1/4 EM_ONHOOK1/5 FXOLS_ONHOOK1/6 g729ar8 n S_CONNECT FXOLS_CONNECTThe following is a sample display from the show voice call summary command for voice ports on a Cisco MC3810 multiservice concentrator, showing two local calls connected with local bypass:
PORT CODEC VAD VTSP STATE VPM STATE======= ======== === ===================== ========================0:17.18 *shutdown*0:18.19 S_CONNECT FXOLS_OFFHOOK0:19.20 FXOLS_ONHOOK0:20.21 FXOLS_ONHOOK0:21.22 FXOLS_ONHOOK0:22.23 FXOLS_ONHOOK0:23.24 EM_ONHOOK1/1 FXSLS_ONHOOK1/2 FXSLS_ONHOOK1/3 EM_ONHOOK1/4 EM_ONHOOK1/5 FXOLS_ONHOOK1/6 S_CONNECT FXOLS_CONNECTThe following is a sample display from the show voice call command for analog voice ports on a Cisco MC3810 multiservice concentrator:
1/1 vpm level 1 state = FXSLS_ONHOOKvpm level 0 state = S_UP1/2 vpm level 1 state = FXSLS_ONHOOKvpm level 0 state = S_UP1/3 is shutdown1/4 vtsp level 0 state = S_CONNECTvpm level 1 state = S_TRUNKEDvpm level 0 state = S_UP1/5 vpm level 1 state = EM_ONHOOKvpm level 0 state = S_UP1/6 vpm level 1 state = EM_ONHOOKvpm level 0 state = S_UPsys252#show voice call 1/41/4 vtsp level 0 state = S_CONNECTvpm level 1 state = S_TRUNKEDvpm level 0 state = S_UProuter# ***DSP VOICE VP_DELAY STATISTICS***Clk Offset(ms): 1445779863, Rx Delay Est(ms): 95Rx Delay Lo Water Mark(ms): 95, Rx Delay Hi Water Mark(ms): 125***DSP VOICE VP_ERROR STATISTICS***Predict Conceal(ms): 10, Interpolate Conceal(ms): 0Silence Conceal(ms): 0, Retroact Mem Update(ms): 0Buf Overflow Discard(ms): 20, Talkspurt Endpoint Detect Err: 0***DSP VOICE RX STATISTICS***Rx Vox/Fax Pkts: 537, Rx Signal Pkts: 0, Rx Comfort Pkts: 0Rx Dur(ms): 50304730, Rx Vox Dur(ms): 16090, Rx Fax Dur(ms): 0Rx Non-seq Pkts: 0, Rx Bad Hdr Pkts: 0Rx Early Pkts: 0, Rx Late Pkts: 0***DSP VOICE TX STATISTICS***Tx Vox/Fax Pkts: 567, Tx Sig Pkts: 0, Tx Comfort Pkts: 0Tx Dur(ms): 50304730, Tx Vox Dur(ms): 17010, Tx Fax Dur(ms): 0***DSP VOICE ERROR STATISTICS***Rx Pkt Drops(Invalid Header): 0, Tx Pkt Drops(HPI SAM Overflow): 0***DSP LEVELS***TDM Bus Levels(dBm0): Rx -70.3 from PBX/Phone, Tx -68.0 to PBX/PhoneTDM ACOM Levels(dBm0): +2.0, TDM ERL Level(dBm0): +5.6TDM Bgd Levels(dBm0): -71.4, with activity being voiceRelated Commands
show voice dsp
To show the current status of all digital signal processor (DSP) voice channels, use the show voice dsp command in privileged EXEC mode.
show voice dsp
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command when abnormal behavior in the DSP voice channels occurs.
Examples
The following is sample output from the show voice dsp command on a Cisco MC3810 multiservice concentrator:
Router# show voice dspDSP# 0, channel# 0 G729A BUSYDSP# 0, channel# 1 G729A BUSYDSP# 1, channel# 2 FAX IDLEDSP# 1, channel# 3 FAX IDLEDSP# 2, channel# 4 NONE BADDSP# 2, channel# 5 NONE BADDSP# 3, channel# 6 NONE BADDSP# 3, channel# 7 NONE BADDSP# 4, channel# 8 NONE BADDSP# 4, channel# 9 NONE BADDSP# 5, channel# 10 NONE BADDSP# 5, channel# 11 NONE BADTable 61 describes the significant fields shown in the display.
Table 61 show voice dsp Field Descriptions
DSP
Number of the DSP.
Channel
Number of the channel and its status.
The following is sample output from the show voice dsp command on a Cisco 1750 router:
Router# show voice dspDSP#0: state IN SERVICE, 2 channels allocatedchannel#0: voice port 1/0, codec G711 ulaw, state UPchannel#1: voice port 1/1, codec G711 ulaw, state UPDSP#1: state IN SERVICE, 2 channels allocatedchannel#0: voice port 2/0, codec G711 ulaw, state UPchannel#1: voice port 2/1, codec G711 ulaw, state UPDSP#2: state RESET, 0 channels allocatedTable 62 describes the significant fields shown in the display.
Table 62 show voice dsp Field Descriptions
DSP
Number of the DSP.
Channel
Number of the channel and its status.
Related Commands
show voice permanent-call
To display information about the permanent calls on a voice interface, use the show voice permanent-call command in user EXEC or privileged EXEC mode.
show voice permanent-call [voice-port] [summary]
Syntax Description
Defaults
No default behavior or values.
Command Modes
User EXEC
Privileged EXEC
Command History
Usage Guidelines
This command is available only on the Cisco MC3810 multiservice concentrator.
When no parameters are specified with this command, the output displays information for all ports containing permanent calls. When a specific interface is specified, information is displayed about the permanent calls for that interface only.
Examples
The following is sample output for the show voice permanent-call command:
Router# show voice permanent-call 1/11/1 state=connect coding=G729A payload size=30 vad=offec=8 (ms), cng=off fax=on digit_relay=on Seq num = off, VOFR Serial0,dlci = 550,cid = 6TX INFO :slow-mode seq#= 25, sig pkt cnt= 19646, last-ABCD=1101hardware-state ACTIVE signal type is CEPT/MELCASvoice-gate CLOSED,network-path OPEN MASTER1101 1101 1101 1101 1101 1101 1101 1101 1101 11011101 1101 1101 1101 1101 1101 1101 1101 1101 11011101 1101 1101 1101 1101 1101 1101 1101 1101 1101RX INFO :slow-mode, sig pkt cnt= 19648, under-run = 0, over-run = 0missing = 0, out of seq = 0, very late = 0playout depth = 0 (ms), refill count = 1prev-seq#= 25, last-ABCD=1101, slave standby timeout 25000 (ms)max inter-arrival time 0 (ms), current timer 384 (ms)max timeout timer 5016 (ms), restart timeout is 0 (ms)signaling packet fast-mode inter-arrival times (ms)16 24 16 24 16 24 16 24 16 24 16 24 16 24 16 2416 24 16 24 16 24 16 24 0 0 0 0 0 0 0 0signaling playout history1101 1101 1101 1101 1101 1101 1101 1101 1101 11011101 1101 1101 1101 1101 1101 1101 1101 1101 11011101 1101 1101 1101 1101 1101 1101 1101 1101 1101The following is sample output for the show voice permanent-call summary command:
Router# show voice permanent-call summary1/1 state= connect, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 880,cid = 61/2 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1021/3 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1031/4 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1041/5 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1051/6 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1061/7 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1071/8 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1081/9 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1091/10 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1101/11 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1111/12 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1121/13 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1131/14 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1141/15 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1151/17 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1171/18 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1181/19 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1191/20 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1201/21 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1211/22 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1221/23 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1231/24 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 1241/25 state= frf11, coding=G729A, payload size=30, vad=off, ec=64, cng=off, fax=ondigit_relay=off, VOFR Serial0:1,dlci = 990,cid = 125Table 63 describes the fields shown in these displays.
Related Commands
show voice port
To display configuration information about a specific voice port, use the show voice port command in EXEC command.
Cisco 1750 Router
show voice port slot-number/port
Cisco 2600 and 3600 Series Router with Analog Voice Ports
show voice port [slot/subunit/port | summary]
2600 and 3600 Series Router with Digital Voice Ports (with T1 Packet Voice Trunk Network Modules)
show voice port [slot/port:ds0-group | summary]
Cisco MC3810 Multiservice Concentrator with Analog Voice Ports
show voice port [slot/port | summary]
Cisco MC3810 Multiservice Concentrator with Digital Voice Ports
show voice port [slot:ds0-group | summary]
Cisco AS5300 Universal Access Server
show voice port controller number:D
Cisco AS5800 Universal Access Server
show voice port {shelf/slot/port:D} | {shelf/slot/parent:port:D}
Cisco 7200 Series Router
show voice port {slot/port:ds0-group-no} | {slot-number/subunit-number/port}
Syntax Description
For the Cisco 1750 Router:
For the Cisco 2600 and 3600 Series Router with Analog Voice Ports:
For the Cisco 2600 and 3600 Series Router with Digital Voice Ports:
For the Cisco MC3810 Multiservice Concentrator with Analog Voice Ports:
For the Cisco MC3810 Multiservice Concentrator with Digital Voice Ports:
For the Cisco AS5300 Access Server :
controller number
Specifies the T1 or E1 controller.
:D
Indicates the D channel associated with ISDN PRI.
For the Cisco AS5800 Universal Access Server:
For the Cisco 7200 Series Router:
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
Use the show voice port EXEC command to display configuration and voice-interface-card-specific information about a specific port.
This command applies to Voice over IP, Voice over Frame Relay, and Voice over ATM.
The ds0-group command automatically creates a logical voice port that is numbered as follows on Cisco 7200 series routers and the Cisco 2600 and Cisco 3600 series routers: slot/port:ds0-group-no. Although only one voice port is created for each group, applicable calls are routed to any channel in the group.
Examples
The following is sample output from the show voice port summary command for all voice ports on a Cisco MC3810 multiservice concentrator with an analog voice module (AVM):
IN OUT ECHOPORT SIG-TYPE ADMIN OPER IN-STATUS OUT-STATUS GAIN ATTN CANCEL1/1 fxs-ls up up on-hook idle 0 0 y1/2 fxs-ls up up on-hook idle 0 0 y1/3 e&m-wnk up up idle idle 0 0 y1/4 e&m-wnk up up idle idle 0 0 y1/5 fxo-ls up up idle on-hook 0 0 y1/6 fxo-ls up up idle on-hook 0 0 yThe following is sample output from the show voice port summary command on a Cisco MC3810 multiservice concentrator with a digital voice module (DVM):
IN OUTPORT CH SIG-TYPE ADMIN OPER STATUS STATUS EC====== == ========== ===== ==== ======== ======== ==0:17 18 fxo-ls down down idle on-hook y0:18 19 fxo-ls up dorm idle on-hook y0:19 20 fxo-ls up dorm idle on-hook y0:20 21 fxo-ls up dorm idle on-hook y0:21 22 fxo-ls up dorm idle on-hook y0:22 23 fxo-ls up dorm idle on-hook y0:23 24 e&m-imd up dorm idle idle y1/1 -- fxs-ls up dorm on-hook idle y1/2 -- fxs-ls up dorm on-hook idle y1/3 -- e&m-imd up dorm idle idle y1/4 -- e&m-imd up dorm idle idle y1/5 -- fxo-ls up dorm idle on-hook y1/6 -- fxo-ls up dorm idle on-hook yElements :sys/voip/ccvpm vpm_htsp.c (107)sys/voip/ccvtsp vtsp_core.c (167)sys/voip/cli voiceport_action.c (58)receEive and transMit Slot is 1, Sub-unit is 0, Port is 1Type of VoicePort is E&MOperation State is DORMANTAdministrative State is UPNo Interface Down FailureDescription is not setNoise Regeneration is enabledNon Linear Processing is enabledMusic On Hold Threshold is Set to -38 dBmIn Gain is Set to 0 dBOut Attenuation is Set to 0 dBEcho Cancellation is enabledEcho Cancel Coverage is set to 8 msConnection Mode is normalConnection Number is not setInitial Time Out is set to 10 sInterdigit Time Out is set to 10 sRegion Tone is set for USThe following is sample output from the show voice port command for an E&M analog voice port on a Cisco 3600:
E&M Slot is 1, Sub-unit is 0, Port is 0Type of VoicePort is E&MOperation State is unknownAdministrative State is unknownThe Interface Down Failure Cause is 0Alias is NULLNoise Regeneration is disabledNon Linear Processing is disabledMusic On Hold Threshold is Set to 0 dBmIn Gain is Set to 0 dBOut Attenuation is Set to 0 dBEcho Cancellation is disabledEcho Cancel Coverage is set to 16msConnection Mode is NormalConnection Number isInitial Time Out is set to 0 sInterdigit Time Out is set to 0 sAnalog Info Follows:Region Tone is set for northamericaCurrently processing noneMaintenance Mode Set to None (not in mtc mode)Number of signaling protocol errors are 0Voice card specific Info Follows:Signal Type is wink-startOperation Type is 2-wireImpedance is set to 600r OhmE&M Type is unknownDial Type is dtmfIn Seizure is inactiveOut Seizure is inactiveDigit Duration Timing is set to 0 msInterDigit Duration Timing is set to 0 msPulse Rate Timing is set to 0 pulses/secondInterDigit Pulse Duration Timing is set to 0 msClear Wait Duration Timing is set to 0 msWink Wait Duration Timing is set to 0 msWink Duration Timing is set to 0 msDelay Start Timing is set to 0 msDelay Duration Timing is set to 0 msThe following is sample output from the show voice port command for a Foreign Exchange Station (FXS) analog voice port on a Cisco 3600:
Foreign Exchange Station 1/0/0 Slot is 1, Sub-unit is 0, Port is 0Type of VoicePort is FXSOperation State is DORMANTAdministrative State is UPThe Interface Down Failure Cause is 0Alias is NULLNoise Regeneration is enabledNon Linear Processing is enabledMusic On Hold Threshold is Set to 0 dBmIn Gain is Set to 0 dBOut Attenuation is Set to 0 dBEcho Cancellation is enabledEcho Cancel Coverage is set to 16msConnection Mode is NormalConnection Number isInitial Time Out is set to 10 sInterdigit Time Out is set to 10 sAnalog Info Follows:Region Tone is set for northamericaCurrently processing noneMaintenance Mode Set to None (not in mtc mode)Number of signaling protocol errors are 0Voice card specific Info Follows:Signal Type is loopStartRing Frequency is 25 HzHook Status is On HookRing Active Status is inactiveRing Ground Status is inactiveTip Ground Status is inactiveDigit Duration Timing is set to 100 msInterDigit Duration Timing is set to 100 msHook Flash Duration Timing is set to 600 msThe following is sample output from the show voice port command for an FXS analog voice port on a Cisco MC3810 multiservice concentrator:
Voice port 1/2 Slot is 1, Port is 2Type of VoicePort is FXSOperation State is UPAdministrative State is UPNo Interface Down FailureDescription is not setNoise Regeneration is enabledNon Linear Processing is enabledIn Gain is Set to 0 dBOut Attenuation is Set to 0 dBEcho Cancellation is enabledEcho Cancel Coverage is set to 8 msConnection Mode is normalConnection Number is not setInitial Time Out is set to 10 sInterdigit Time Out is set to 10 sCoder Type is g729ar8Companding Type is u-lawVoice Activity Detection is disabledRinging Time Out is 180 sWait Release Time Out is 30 sNominal Playout Delay is 80 millisecondsMaximum Playout Delay is 160 millisecondsAnalog Info Follows:Region Tone is set for northamericaCurrently processing VoiceMaintenance Mode Set to None (not in mtc mode)Number of signaling protocol errors are 0Impedance is set to 600r OhmAnalog interface A-D gain offset = -3 dBAnalog interface D-A gain offset = -3 dBVoice card specific Info Follows:Signal Type is loopStartRing Frequency is 20 HzHook Status is On HookRing Active Status is inactiveRing Ground Status is inactiveTip Ground Status is activeDigit Duration Timing is set to 100 msInterDigit Duration Timing is set to 100 msRing Cadence are [20 40] * 100 msecInterDigit Pulse Duration Timing is set to 500 msThe following is sample output from the show voice port command for an E&M digital voice port on a Cisco 3600:
receEive and transMit Slot is 1, Sub-unit is 0, Port is 1Type of VoicePort is E&MOperation State is DORMANTAdministrative State is UPNo Interface Down FailureDescription is not setNoise Regeneration is enabledNon Linear Processing is enabledMusic On Hold Threshold is Set to -38 dBmIn Gain is Set to 0 dBOut Attenuation is Set to 0 dBEcho Cancellation is enabledEcho Cancel Coverage is set to 8 msConnection Mode is normalConnection Number is not setInitial Time Out is set to 10 sInterdigit Time Out is set to 10 sRegion Tone is set for USThe following is sample output from the show voice port summary command for all voice ports on a Cisco MC3810 multiservice concentrator with an analog voice module (AVM):
IN OUT ECHOPORT SIG-TYPE ADMIN OPER IN-STATUS OUT-STATUS CODEC VAD GAIN ATTN CANCEL1/1 fxs-ls up up on-hook idle 729a n 0 0 y1/2 fxs-ls up up on-hook idle 729a n 0 0 y1/3 e&m-wnk up up idle idle 729a n 0 0 y1/4 e&m-wnk up up idle idle 729a n 0 0 y1/5 fxo-ls up up idle on-hook 729a n 0 0 y1/6 fxo-ls up up idle on-hook 729a n 0 0 yTable 64 explains the fields in the sample output
The following example displays voice port configuration information for the digital voice port 0 located in slot 1, DS0 group 1:
receEive and transMit Slot is 1, Sub-unit is 0, Port is 1Type of VoicePort is E&MOperation State is DORMANTAdministrative State is UPNo Interface Down FailureDescription is not setNoise Regeneration is enabledNon Linear Processing is enabledMusic On Hold Threshold is Set to -38 DBMSIn Gain is Set to 0 dBmOut Attenuation is Set to 0 dBEcho Cancellation is enabledEcho Cancel Coverage is set to 8 msConnection Mode is normalConnection Number is not setInitial Time Out is set to 10 sInterdigit Time Out is set to 10 sRegion Tone is set for USThe following is sample output from the Cisco AS5800 for the show voice port command:
ISDN 1/0/0:DType of VoicePort is ISDNOperation State is DORMANTAdministrative State is UPNo Interface Down FailureDescription is ""Noise Regeneration is enabledNon Linear Processing is enabledMusic On Hold Threshold is Set to -38 dBmIn Gain is Set to 0 dBOut Attenuation is Set to 0 dBEcho Cancellation is enabledEcho Cancel Coverage is set to 16 msConnection Mode is normalConnection Number is not setInitial Time Out is set to 10 sInterdigit Time Out is set to 10 sRegion Tone is set for USTable 65 describes the significant fields shown in the display.
show voice trunk-conditioning signaling
To display the status of trunk-conditioning signaling and timing parameters for a voice port, use the show voice trunk-conditioning signaling command in user EXEC or privileged EXEC mode.
show voice trunk-conditioning signaling [summary | voice-port]
Syntax Description
summary
(Optional) Displays a summary of the status for all voice ports on the router or concentrator.
voice-port
(Optional) Displays a detailed report for a specified voice port.
Command Modes
User EXEC
Privileged EXEC
Command History
Usage Guidelines
The show voice trunk-conditioning signaling command displays the trunk signaling status for analog and digital voice ports on Cisco MC3810 multiservice concentrators and Cisco 2600 and 3600 series routers.
Examples
The following is a sample display from the show voice trunk-conditioning signaling summary command for voice ports on a Cisco MC3810 multiservice concentrator:
Router# show voice trunk-conditioning signaling summary1/1 is shutdown1/4 is shutdown1/5 :TX INFO :slow-mode seq#= 25, sig pkt cnt= 40, last-ABCD=0000hardware-state ACTIVE signal type is NorthamericanCAS signal path is OPENRX INFO :slow-mode, sig pkt cnt= 36, prev-seq#= 25, last-ABCD=0000The following is a sample display from the show voice trunk-conditioning signaling command for voice port 1/5 on a Cisco MC3810 multiservice concentrator:
Router# show voice trunk-conditioning signaling 1/51/5 :TX INFO :slow-mode seq#= 25, sig pkt cnt= 42, last-ABCD=0000hardware-state ACTIVE signal type is NorthamericanCASsignal path is OPEN0000 0000 0000 0000 0000 0000 0000 0000 0000 00000000 0000 0000 0000 0000 0000 0000 0000 0000 00000000 0000 0000 0000 0000 0000 0000 0000 0000 0000RX INFO :slow-mode, sig pkt cnt= 37missing = 0, out of seq = 0, very late = 0playout depth = 0 (ms), refill count = 1prev-seq#= 25, last-ABCD=0000trunk_down_timer = 4212 (ms), idle timer = 0 (sec),tx_oos_timer = 0 (sec), rx_ais_duration = 0 (ms)forced playout signal pattern = NONEsignaling playout history0000 0000 0000 0000 0000 0000 0000 0000 0000 00000000 0000 0000 0000 0000 0000 0000 0000 0000 00000000 0000 0000 0000 0000 0000 0000 0000 0000 0000The following is a sample display from the show voice trunk-conditioning signaling summary command for voice ports on a Cisco 3600 series router:
Router# show voice trunk-conditioning signaling summary2/0/0 is shutdown2/0/1 is shutdown3/0:0 8 is shutdown3/0:1 1 is shutdown3/0:2 2 is shutdown3/0:3 3 is shutdown3/0:5 5 is shutdown3/0:6(6) :status :3/0:7 7 is shutdown3/1:0 8 is shutdown3/1:1 1 is shutdown3/1:3 3 is shutdown3/1:5 5 is shutdown3/1:7 7 is shutdownThe following is a sample display from the show voice trunk-conditioning signaling command for voice port 3/0:6 on a Cisco 3600 series router:
Router# show voice trunk-conditioning signaling 3/0:6hardware-state ACTIVE signal type is NorthamericanCASstatus :forced playout pattern = STOPPEDtrunk_down_timer = 0, rx_ais_duration = 0, idle_timer = 0Table 66 describes the significant fields shown in the display.
Related Commands
show voice trunk-conditioning supervisory
To display the status of trunk supervision and configuration parameters for a voice port, use the show voice trunk-conditioning supervisory command in user EXEC or privileged EXEC mode.
show voice trunk-conditioning supervisory [summary | voice-port]
Syntax Description
summary
(Optional) Displays a summary of the status for all voice ports on the router or concentrator.
voice-port
(Optional) Displays a detailed report for a specified voice port.
Command Modes
User EXEC
Privileged EXEC
Command History
Usage Guidelines
The show voice trunk-conditioning supervisory command displays the trunk supervision and configuration status for analog and digital voice ports.
Examples
The following is a sample display from the show voice trunk-conditioning supervisory summary command for voice ports on a Cisco MC3810 multiservice concentrator:
Router# show voice trunk-conditioning supervisory summary1/1 is shutdown1/4 is shutdown1/5 : state : TRUNK_SC_CONNECT, voice : on , signal : on ,slaveThe following is a sample display from the show voice trunk-conditioning supervisory command for voice port 1/5 on a Cisco MC3810 multiservice concentrator:
Router# show voice trunk-conditioning supervisory 1/51/5 : state : TRUNK_SC_CONNECT, voice : on, signal : on, slavestatus: trunk connectedsequence oos : idle and oospattern :rx_idle = 0x0 rx_oos = 0xF tx_oos = 0xFtiming : idle = 0, restart = 0, standby = 0, timeout = 40supp_all = 50, supp_voice = 0, keep_alive = 5timer: oos_ais_timer = 0, timer = 0The following is a sample display from the show voice trunk-conditioning supervisory summary command for voice ports on a Cisco 3600 series router:
Router# show voice trunk-conditioning supervisory summary2/0/0 is shutdown2/0/1 is shutdown3/0:0 8 is shutdown3/0:1 1 is shutdown3/0:2 2 is shutdown3/0:3 3 is shutdown3/0:5 5 is shutdown3/0:6(6) : state : TRUNK_SC_CONNECT, voice : on , signal : on ,master3/0:7(7) : state : TRUNK_SC_CONNECT, voice : on , signal : on ,master3/1:0(8) : state : TRUNK_SC_CONNECT, voice : on , signal : on ,master3/1:1(1) : state : TRUNK_SC_CONNECT, voice : on , signal : on ,master3/1:3(3) : state : TRUNK_SC_CONNECT, voice : on , signal : on ,master3/1:5(5) is shutdown3/1:7(7) is shutdownThe following is a sample display from the show voice trunk-conditioning supervisory command for voice port 3/0:6 on a Cisco 3600 series router:
Router# show voice trunk-conditioning supervisory 3/0:63/0:6(6) : state : TRUNK_SC_CONNECT, voice : on, signal : on, masterstatus: trunk connectedsequence oos : idle and oospattern :rx_idle = 0x0 rx_oos = 0xFtiming : idle = 0, restart = 0, standby = 0, timeout = 40supp_all = 0, supp_voice = 0, keep_alive = 5timer: oos_ais_timer = 0, timer = 0Table 67 describes the significant fields shown in the display.
Related Commands
show vrm active_calls
To display active-only voice calls either for a specific voice feature card (VFC) or for all VFCs, use the show vrm active_calls command in privileged EXEC mode.
show vrm active_calls {dial-shelf-slot-number | all}
Syntax Description
dial-shelf-slot-number
Slot number of the dial shelf. Valid number is 0 to 13.
all
Lists all active calls for VFC slots.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(7)T
This command was introduced on the Cisco AS5800 universal access server.
Usage Guidelines
Use the show vrm active_calls to display active-only voice calls either for a specific VFC or for all VFCs. Each active call occupies a block of information describing the call. This information provides basically the same information as the show vrm vdevice command.
Examples
The following is sample output from the show vrm active_calls command specifying dial shelf slot number:
Router# show vrm active_calls 6slot = 6 virtual voice dev (tag) = 61 channel id = 2capabilities list map = 9FFFlast/current codec loaded/used = NoneTDM timeslot = 241Resource (vdev_common) status = 401 means :active otherstot ingress data = 24tot ingress control = 1308tot ingress data drops = 0tot ingress control drops = 0tot egress data = 22051tot egress control = 1304tot egress data drops = 0tot egress control drops = 0slot = 6 virtual voice dev (tag) = 40 channel id = 2capabilities list map = 9FFFlast/current codec loaded/used = NoneTDM timeslot = 157Resource (vdev_common) status = 401 means :active othersTable 68 describes the significant fields shown in the display.
Related Commands
show vrm vdevices
Displays detailed information for a specific DSP or a brief summary display for all VFCs.
show vrm vdevices
To display detailed information for a specific digital signal processor (DSP) or a brief summary display for all voice feature cards (VFCs), use the show vrm vdevices command in privileged EXEC mode.
show vrm vdevices {{vfc-slot-number | voice-device-number} | summary}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(7)T
This command was introduced on the Cisco AS5800 universal access server.
Usage Guidelines
Use the show vrm vdevices command to display detailed information for a specific DSP or a brief summary display for all VFCs. The display provides information on the number of channels, channels per DSP, bitmap of DSPMs, version numbers, and so on. This information is useful in monitoring the current state of your VFCs.
The display for a specific DSP provides information on the codec that each channel is using, if active, or last used and if the channel is not currently sending cells. It also displays the state of the resource. In most cases, if there is an active call on that channel, the resource should be marked active. If the resource is marked as reset or bad, this may be an indication of a response loss for the VFC on a reset request. If this condition persists, you might experience a problem with the communication link between the router shelf and the VFC.
Examples
The following is sample output from the show vrm vdevices command specifying dial shelf slot number and DSP number. In this particular example, the call is active so the statistics displayed are for this active call. If no calls are currently active on the device, the statistics would be for the previous (or last active) call.
Router# show vrm vdevices 6 1slot = 6 virtual voice dev (tag) = 1 channel id = 1capabilities list map = 9FFFlast/current codec loaded/used = NoneTDM timeslot = 0Resource (vdev_common) status = 401 means :active otherstot ingress data = 101tot ingress control = 1194tot ingress data drops = 0tot ingress control drops = 0tot egress data = 39722tot egress control = 1209tot egress data drops = 0tot egress control drops = 0slot = 6 virtual voice dev (tag) = 1 channel id = 2capabilities list map = 9FFFlast/current codec loaded/used = NoneTDM timeslot = 1Resource (vdev_common) status = 401 means :active otherstot ingress data = 21tot ingress control = 1167tot ingress data drops = 0tot ingress control drops = 0tot egress data = 19476tot egress control = 1163tot egress data drops = 0tot egress control drops = 0Table 69 describes the significant fields shown in the display.
The following is sample output from the show vrm devices command specifying a summary list. In the "Voice Device Mapping" area, the "C_Ac" column indicates number of active calls for a specific DSP. If there are any nonzero numbers under the "C_Rst" and/or "C_Bad" column, this indicates that a reset request was sent but it was lost; this could mean a faulty DSP.
Router# show vrm vdevices summary*****************************************************************summary of voice devices for all voice cards********************************************************************slot = 6 major ver = 0 minor ver = 1 core type used = 2number of modules = 16 number of voice devices (DSPs) = 96chans per vdevice = 2 tot chans = 192 tot active calls = 178module presense bit map = FFFF tdm mode = 1 num_of_tdm_timeslots = 384auto recovery is onnumber of default voice file (core type images) = 2file 0 maj ver = 0 min ver = 0 core_type = 1trough size = 2880 slop value = 0 built-in codec bitmap = 0loadable codec bitmap = 0 fax codec bitmap = 0file 1 maj ver = 3 min ver = 1 core_type = 2trough size = 2880 slop value = 1440 built-in codec bitmap = 40Bloadable codec bitmap = BFC fax codec bitmap = 7E-------------------Voice Device Mapping------------------------Logical Device (Tag) Module# DSP# C_Ac C_Busy C_Rst C_Bad---------------------------------------------------------------1 1 1 2 0 0 02 1 2 2 0 0 03 1 3 2 0 0 04 1 4 2 0 0 05 1 5 2 0 0 06 1 6 2 0 0 0+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++7 2 1 2 0 0 08 2 2 2 0 0 09 2 3 2 0 0 010 2 4 1 0 0 011 2 5 2 0 0 012 2 6 1 0 0 0+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<information deleted>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++91 16 1 2 0 0 092 16 2 2 0 0 093 16 3 1 0 0 094 16 4 2 0 0 095 16 5 2 0 0 096 16 6 2 0 0 0+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++Total active call channels = 178Total busied out channels = 0Total channels in reset = 0Total bad channels = 0Note :Channels could be in multiple statesTable 70 describes the significant fields shown in the display.
Related Commands
show vrm active_calls
Displays active-only voice calls for either a specific VFC or all VFCs.
shut
To shut down a set of digital signal processors (DSPs) on the Cisco 7200 series router, use the shut command in DSP configuration mode. To put DSPs back in service, use the no form of this command.
shut number
no shut number
Syntax Description
Defaults
no shut
Command Modes
DSP configuration
Command History
12.0(5)XE
This command was introduced on the Cisco 7200 series router.
12.1(1)T
This command was modified to add information about DSP groups.
Usage Guidelines
This command applies to Voice over IP on the Cisco 7200 series routers.
Examples
The following example shuts down two sets of DSPs:
shut 2shutdown (dial-peer)
To change the administrative state of the selected dial peer from up to down, use the shutdown command in dial-peer configuration mode. To change the administrative state of this dial peer from down to up, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
no shutdown
Command Modes
Dial-peer configuration
Command History
11.3(1)T
This command was introduced on the Cisco 3600 series router.
12.1(1)
This command was modified for store-and-forward fax.
Usage Guidelines
When a dial peer is shut down, you cannot initiate calls to that peer.
This command applies to both on-ramp and off-ramp store-and-forward fax functions.
Examples
The following example changes the administrative state of voice telephony (plain old telephone service [POTS]) dial peer 10 to down:
dial-peer voice 10 potsshutdownThe following example changes the administrative state of voice telephony (POTS) dial peer 10 to up:
dial-peer voice 10 potsno shutdownRelated Commands
dial-peer voice
Enters dial-peer configuration mode, defines the type of dial peer, and defines the dial-peer tag number.
shutdown (DS1)
To shut down a DS1 link (send a Blue Alarm), use the shutdown command in controller configuration mode. To activate the DS1 (cancel the sending of the Blue Alarm), use the no form of the command.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
no shutdown
Command Modes
Controller configuration
Command History
Usage Guidelines
This command applies to Voice over Frame Relay and Voice over ATM on the Cisco MC3810 multiservice concentrator.
Examples
The following example shuts down a DS1 link on controller T1 0:
controller T1 0shutdownshutdown (gatekeeper)
To disable the gatekeeper, use the shutdown command in gatekeeper configuration mode. To enable the gatekeeper, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled (shut down)
Command Modes
gatekeeper configuration
Command History
Usage Guidelines
The gatekeeper does not have to be enabled before you can use the other gatekeeper configuration commands. In fact, it is recommended that you complete the gatekeeper configuration before bringing up the gatekeeper because some characteristics may be difficult to alter while the gatekeeper is running, as there may be active registrations or calls.
The no shutdown command enables the gatekeeper, but it does not make the gatekeeper operational. The two exceptions to this are as follows:
•
•
Examples
The following command disables a gatekeeper:
shutdownshutdown (RLM)
To shut down all of the links under the RLM group, use the shutdown command in RLM configuration mode. RLM will not try to reestablish those links until the command is negated. To disable this function, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
RLM configuration
Command History
Related Commands
shutdown (settlement)
To deactivate the settlement provider, use the shutdown command in settlement configuration mode. To activate a settlement provider, use the no shutdown command
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
The default status of a settlement provider is deactivated. The settlement provider is down.
Command Modes
Settlement configuration
Command History
Usage Guidelines
Use the no shutdown command at the end of the configuration of a settlement server to bring up the provider. This command activates the provider. Otherwise, transactions will not go through the provider to be audited and charged. Use the shutdown command to deactivate the provider.
Examples
The following example enables a settlement server:
settlement 0no shutdownThe following example disables a settlement server:
settlement 0shutdownRelated Commands
shutdown (voice-port)
To take the voice ports for a specific voice interface card offline, use the shutdown command in voice-port configuration mode. To put the ports back in service, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
shutdown
Command Modes
Voice-port configuration
Command History
Usage Guidelines
When you enter the shutdown command, all ports on the voice interface card are disabled. When you enter the no shutdown command, all ports on the voice interface card are enabled. A telephone connected to an interface will hear dead silence when a port is shut down.
Examples
The following example takes voice port 1/1/0 on the Cisco 3600 series offline:
voice-port 1/1/0shutdown
Note
