-
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
-
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=0
