-
Cisco IOS Voice Command Reference
-
About Cisco IOS Software Documentation
-
Using Cisco IOS Software
-
Commands: A
-
Commands: B
-
Commands:cac master through call application stats
-
Commands: call application voice through call-denial
-
Commands: call fallback through called-number (dial-peer)
-
Commands: caller-id (dial peer) through ccm-manager switchover-to-backup
-
Commands: ccs connect (controller) through clear vsp statistics
-
Commands: clid through cptone
-
Commands: default (MGCP profile) through direct-inward-dial
-
Commands: disable-early-media 180 through dualtone
-
Commands: E
-
Commands: F
-
Commands: G
-
Commands: H
-
Commands: icpif through irq global-request
-
Commands: isdn bind-l3 through ixi transport http
-
Commands: K
-
Commands: L
-
Commands: map q850-cause through mgcp package-capability
-
Commands: mgcp persistent through mmoip aaa send-id secondary
-
Commands: mode (ATM/T1/E1 controller) through mwi-server
-
Commands: N
-
Commands: O
-
Commands: package through pattern
-
Commands: permit hostname through proxy h323
-
Commands: Q
-
Commands: R
-
Commands: sccp through service-type call-check
-
Commands: session through sgcp tse payload
-
Commands: show aal2 profile through show call filter match-list
-
Commands: show call history fax through show debug condition
-
Commands: show dial-peer video through show gatekeeper zone status
-
Commands: show gateway through show modem relay statistics
-
Commands: show mrcp client session active through show sgcp statistics
-
Commands: show sip service through show trunk hdlc
-
Commands: show vdev through show voice statistics memory-usage
-
Commands: show voice translation-profile through shutdown (voice-port)
-
Commands: signal through srv version
-
Commands: ss7 mtp2-variant through switchover method
-
Commands: target carrier-id through threshold noise
-
Commands: timeout (auto-config application) through timing clear-wait
-
Commands:timing delay-duration through type (voice)
-
Commands: U
-
Commands: vad (dial peer) through voice class dualtone-detect-params
-
Commands: voice class h323 through vxml tree memory
-
Commands: W
-
Commands: Z
-
Feedback
Table Of Contents
redirect ip2ip (voice service)
retries (auto-config application)
rtsp client session history duration
rtsp client session history records
Cisco IOS Voice Commands:
R
This chapter contains commands to configure and maintain Cisco IOS voice applications. The commands are presented in alphabetical order. Some commands required for configuring voice 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 Configuration Library.
radius-server attribute 6
To provide for the presence of the Service-Type attribute (attribute 6) in RADIUS Access-Accept messages, use the radius-server attribute 6 command in global configuration mode. To make the presence of the Service-Type attribute optional in Access-Accept messages, use the no form of this command.
radius-server attribute 6 {mandatory | on-for-login-auth | support-multiple | voice value}
no radius-server attribute 6 {mandatory | on-for-login-auth | support-multiple | voice value}
Syntax Description
Command Default
If this command is not configured, the absence of the Service-Type attribute is ignored, and the authentication or authorization does not fail. The default for the voice keyword is 12.
Command Modes
Global configuration
Command History
12.2(11)T
This command was introduced.
12.2(13)T
The mandatory keyword was added.
Usage Guidelines
If this command is configured and the Service-Type attribute is absent in the Access-Accept message packets, the authentication or authorization fails.
The support-multiple keyword allows for multiple instances of the Service-Type attribute to be present in an Access-Accept packet. The default behavior is to disallow multiple instances, which results in an Access-Accept packet containing multiple instances being treated as though an Access-Reject was received.
Examples
The following example shows that the presence of the Service-Type attribute is mandatory in RADIUS Access-Accept messages:
Router(config)# radius-server attribute 6 mandatoryThe following example shows that attribute 6 is to be sent in authentication packets:
Router(config)# radius-server attribute 6 on-for-login-authThe following example shows that multiple Service-Type values are to be supported for each RADIUS profile:
Router(config)# radius-server attribute 6 support-multipleThe following example shows that Service-Type values are to be sent in voice calls:
Router(config)# radius-server attribute 6 voice 1ras retry
To configure the H.323 Registration, Admission, and Status (RAS) message retry counters, use the ras retry command in voice service h323 configuration mode. To set the counters to the default values, use the no form of this command.
ras retry {all | arq | brq | drq | grq | rai | rrq} value
no ras retry {all | arq | brq | drq | grq | rai | rrq}
Syntax Description
Command Default
arq: 2 retries
brq: 2 retries
drq: 9 retries
grq: 2 retries
rai: 9 retries
rrq: 2 retriesCommand Modes
Voice service h323 configuration
Command History
Usage Guidelines
Use this command in conjunction with the ras timeout command. The ras timeout command configures the number of seconds for the gateway to wait before resending a RAS message to a gatekeeper. The ras retry command configures the number of times to resend the RAS message after the timeout period expires. The default values for timeouts and retries are acceptable in most networks. You can use these commands if you are experiencing problems in RAS message transmission between gateways and gatekeepers. For example, if you have gatekeepers that are slow to respond to a type of RAS request, increasing the timeout value and the number of retries increases the call success rate, preventing lost billing information and unnecessary switchover to an alternate gatekeeper.
Examples
The following example shows the GRQ message counter set to 5 and all other RAS message counters set to 10:
Router(conf-serv-h323)# ras retry all 10Router(conf-serv-h323)# ras retry grq 5Related Commands
ras retry lrq
To configure the gatekeeper Registration, Admission, and Status (RAS) message retry counters, use the ras retry lrq command in gatekeeper configuration mode. To set the counters to the default values, use the no form of this command.
ras retry lrq value
no ras retry lrq
Syntax Description
Command Default
The retry counter is set to1.
Command Modes
Gatekeeper configuration
Command History
Usage Guidelines
Use this command in conjunction with the ras timeout lrq command. The ras timeout lrq command configures the number of seconds for the gateway to wait before resending a RAS message to a gatekeeper. The ras retry lrq command configures the number of times to resend the RAS message after the timeout period expires. The default values for timeouts and retries are acceptable in most networks. You can use these commands if you are experiencing problems in RAS message transmission between gateways and gatekeepers. For example, if you have gatekeepers that are slow to respond to a type of RAS request, increasing the timeout value and the number of retries increases the call success rate, preventing lost billing information and unnecessary switchover to an alternate gatekeeper.
Examples
The following example shows the LRQ message counter set to 5:
Router(conf-gk)# ras retry lrq 5Related Commands
ras rrq dynamic prefixes
To enable advertisement of dynamic prefixes in additive registration request (RRQ) RAS messages on the gateway, use the ras rrq dynamic prefixes command in voice service h323 configuration mode. To disable advertisement of dynamic prefixes in additive RRQ messages, use the no form of this command.
ras rrq dynamic prefixes
no ras rrq dynamic prefixes
Syntax Description
This command has no arguments or keywords.
Command Default
In Cisco IOS Release 12.2(15)T, the default was set to enabled. In Cisco IOS Release 12.3(3), the default is set to disabled.
Command Modes
Voice service h323 configuration
Command History
Usage Guidelines
In Cisco IOS Release 12.2(15)T, the default for the ras rrq dynamic prefixes command was set to enabled so that the gateway automatically sent dynamic prefixes in additive RRQ messages to the gatekeeper. Beginning in Cisco IOS Release 12.3(3), the default is set to disabled, and you must specify the command to enable the functionality.
Examples
The following example allows the gateway to send advertisements of dynamic prefixes in additive RRQ messages to the gatekeeper:
Router(conf-serv-h323)# ras rrq dynamic prefixesRelated Commands
rrq dynamic-prefixes-accept
Enables processing of additive RRQ messages and dynamic prefixes on the gatekeeper.
ras rrq ttl
To configure the H.323 Registration, Admission, and Status (RAS) registration request (RRQ) time-to-live value, use the ras rrq ttl command in voice service h323 configuration mode. To set the RAS RRQ time-to-live value to the default value, use the no form of this command.
ras rrq ttl time-to-live seconds [margin seconds]
no ras rrq ttl
Syntax Description
Command Default
time-to-live seconds: 60 seconds
margin seconds: 15 secondsCommand Modes
Voice service h323 configuration
Command History
Usage Guidelines
Use this command to configure the number of seconds that the gateway should be considered active by the gatekeeper. The gateway transmits this value in the RRQ message to the gatekeeper. The margin time keyword and argument allow the gateway to transmit an early RRQ to the gatekeeper before the time-to-live value advertised to the gatekeeper.
Examples
The following example shows the time-to-live seconds value configured to 300 seconds and the margin seconds value configured to 60 seconds:
Router(conf-serv-h323)# ras rrq ttl 300 margin 60ras timeout
To configure the H.323 Registration, Admission, and Status (RAS) message timeout values, use the ras timeout command in voice service h323 configuration mode. To set the timers to the default values, use the no form of this command.
ras timeout {all | arq | brq | drq | grq | rai | rrq} seconds
no ras timeout {all | arq | brq | drq | grq | rai | rrq}
Syntax Description
Command Default
arq: 3 seconds
brq: 3 seconds
drq: 3 seconds
grq: 5 seconds
rai: 3 seconds
rrq: 5 secondsCommand Modes
Voice service h323 configuration
Command History
Usage Guidelines
Use this command in conjunction with the ras retry command. The ras timeout command configures the number of seconds for the gateway to wait before resending a RAS message to a gatekeeper. The ras retry command configures the number of times to resend the RAS message after the timeout period expires. The default values for timeouts and retries are acceptable in most networks. You can use these commands if you are experiencing problems in RAS message transmission between gateways and gatekeepers. For example, if you have gatekeepers that are slow to respond to a type of RAS request, increasing the timeout value and the number of retries increases the call success rate, preventing lost billing information and unnecessary switchover to an alternate gatekeeper.
Examples
The following example shows the GRQ message timeout value set to 10 seconds and all other RAS message timeout values set to 7 seconds:
Router(conf-serv-h323)# ras timeout grq 10Router(conf-serv-h323)# ras timeout all 7Related Commands
ras timeout decisec
To configure the H.323 Registration, Admission, and Status (RAS) message timeout values in deciseconds, use the ras timeout decisec command in voice service h323 configuration mode. To set the timers to the default values, use the no form of this command.
ras timeout {all | arq | brq | drq | grq | rai | rrq} decisec decisecond
no ras timeout {all | arq | brq | drq | grq | rai | rrq} decisec
Syntax Description
Command Default
Timers are set to their default values.
Command Modes
Voice service h323 configuration
Command History
Usage Guidelines
Use this command in conjunction with the ras retry command. The ras timeout decisec command configures the number of deciseconds for the gateway to wait before resending a RAS message to a gatekeeper. The ras retry command configures the number of times to resend the RAS message after the timeout period expires. The default values for timeouts and retries are acceptable in most networks. You can use these commands if you are experiencing problems in RAS message transmission between gateways and gatekeepers. For example, if you have gatekeepers that are slow to respond to a type of RAS request, increasing the timeout value and the number of retries increases the call success rate, preventing lost billing information and unnecessary switchover to an alternate gatekeeper.
Examples
The following example shows the ARQ message timeout value set to 25 deciseconds and all other RAS message timeout values set to 30 deciseconds:
Router(conf-serv-h323)# ras timeout arq decisec 25Router(conf-serv-h323)# ras timeout all decisec 30Related Commands
ras retry
Configures the H.323 RAS message retry counters.
ras timeout
Configures the H.323 RAS message timeout values in seconds.
ras timeout lrq
To configure the Gatekeeper Registration, Admission, and Status (RAS) message timeout values, use the ras timeout lrq command in gatekeeper configuration mode. To set the timers to the default values, use the no form of this command.
ras timeout lrq seconds
no ras timeout lrq
Syntax Description
Command Default
Timers are set to their default value
Command Modes
Gatekeeper configuration
Command History
Usage Guidelines
Use this command in conjunction with the ras retry lrq command. The ras timeout lrq command configures the number of seconds for the zone gatekeeper (ZGK) to wait before resending a RAS message to a directory gatekeeper (DGK). The ras retry lrq command configures the number of times to resend the RAS message after the timeout period expires. The default values for timeouts and retries are acceptable in most networks. You can use these commands if you are experiencing problems in RAS message transmission between gatekeepers. For example, if you have gatekeepers that are slow to respond to a LRQ RAS request, increasing the timeout value and the number of retries increases the call success rate, preventing lost billing information and unnecessary switchover to an alternate gatekeeper.
Examples
The following example shows the LRQ message timeout value set to 4 seconds:
Router(conf-gk)# ras timeout lrq 4Related Commands
rbs-zero
To enable 1AESS switch support for T1 lines on the primary serial interface of an access server, use the rbs-zero command in serial interface configuration mode. To disable IAESS switch support, use the no form of this command.
rbs-zero [nfas-int nfas-int-range]
no rbs-zero [nfas-int nfas-int-range]
Syntax Description
nfas-int nfas-int-range
(Optional) Non-Facility Associated Signaling (NFAS) interface number. Range is from 0 to 32.
Command Default
1AESS switch support is disabled.
Command Modes
Serial interface configuration
Command History
Usage Guidelines
Use this command to configure the primary serial interface of an access server connected to T1 lines to support 1AESS switches for dial-in and dial-out calls. Modem calls of 56K or a lower rate are accepted; 64K calls are rejected.
In IAESS mode, the following occurs:
•
Modem calls are accepted and digital calls are rejected.
•
In non-1AESS mode, modem and digital calls are accepted.
Examples
The following example enables 1AESS switching support on T1 channel 0:
Router(config)# controller t1 1/0Router(config-controller)# framing esfRouter(config-controller)# linecode b8zsRouter(config-controller)# pri-group timeslots 1-24 nfas_d primary nfas_int 0 nfas_group 1Router(config)# interface serial 1/0:23Router(config-if)# no ip addressRouter(config-if)# isdn switch-type primary-niRouter(config-if)# rbs-zero nfas-int 0Related Commands
reason-header override
To enable cause code passing from one SIP leg to another, use the reason-header override command in SIP UA configuration mode. To disable reason-header override, use the no form of this command.
reason-header override
no reason-header override
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
SIP UA configuration
Command History
12.3(8)T
This command was introduced.
12.4(9)T
Usage guidelines were updated to include configuration requirements for SIP-to-SIP configurations.
Usage Guidelines
In an SIP-to-SIP configuration the reason-header override command must be configured to ensure cause code passing from the incoming SIP leg to the outgoing SIP leg.
Examples
The following example, shows the SIP user agent with reason-header override being configured.
Router(config)# sip-uaRouter(config-sip-ua)# reason-header overrideRelated Commands
redial
To designate an SCCP telephony control (STC) application feature speed-dial code to redial the last number dialed, use the redial command in STC application feature speed-dial configuration mode. To return the code to its default, use the no form of this command.
redial keypad-character
no redial
Syntax Description
keypad-character
Single character that can be dialed on a telephone keypad. Default is # (pound sign).
Command Default
The default code for redial is # (pound sign).
Command Modes
STC application feature speed-dial configuration
Command History
Usage Guidelines
This command is used with the STC application, which enables certain features on analog FXS endpoints that use Skinny Client Control Protocol (SCCP) for call control.
Use this command to set the redial code only if you want to change the value from its default, which is # (pound sign).
To use the redial feature on a phone, dial the STC application feature speed-dial (FSD) prefix and the code that has been configured with this command (or the default if this command was not used). For example, if the FSD prefix is * (the default), and you want to redial the phone number most recently dialed from this line, dial *#.
If a call has never been made from a phone, and you dial the redial prefix and code, you hear silence because the call-control system does not have a number to redial and cannot respond.
If you set this code to a value that is already in use for another FSD code, you receive an error message. If you configure a duplicate code, the system implements the first matching feature in the order of precedence shown in the output of the show stcapp feature codes command.
The show running-config command displays nondefault FSD codes only. The show stcapp feature codes command displays all FSD codes.
Examples
The following example sets an FSD code prefix of two pound signs (##) and a redial code of 9. After these values are configured, a phone user presses ##9 on the keypad to redial the last number called from the phone.
Router(config)# stcapp feature speed-dialRouter(stcapp-fsd)# prefix ##Router(stcapp-fsd)# redial 9Router(stcapp-fsd)# exitRelated Commands
redirect contact order
To set the order of contacts in the 300 Multiple Choice message, use the redirect contact order command in SIP configuration mode. To reset the order of contacts to the default, use the no form of this command.
redirect contact order [best-match | longest-match]
no redirect contact order
Syntax Description
Command Default
longest-match
Command Modes
SIP configuration
Command History
12.2(15)ZJ
This command was introduced.
12.3(4)T
This command was integrated into Cisco IOS Release 12.3(4)T.
Usage Guidelines
This command applies when a 300 Multiple Choice message is sent by a SIP gateway indicating that a call has been redirected and that there are multiple routes to the destination.
Enter SIP configuration mode after entering voice service VoIP configuration mode as shown in the following example.
Examples
The following example uses the current system configuration to set the order of contact:
Router(config)# voice service voipRouter(config-voi-srv)# sipRouter(conf-serv-sip)# redirect contact order best-matchRelated Commands
redirect ip2ip (dial peer)
To redirect SIP phone calls to SIP phone calls on a specific VoIP dial peer using the Cisco IOS Voice Gateway, use the redirect ip2ip command in dial peer configuration mode. To disable redirection, use the no form of this command.
redirect ip2ip
no redirect ip2ip
Syntax Description
This command has no arguments or keywords.
Command Default
Redirection is disabled.
Command Modes
Dial peer configuration
Command History
12.2(15)ZJ
This command was introduced.
12.3(4)T
This command was integrated into Cisco IOS Release 12.3(4)T.
Usage Guidelines
The redirect ip2ip command must be configured on the inbound dial peer of the gateway. This command enables, on a per dial peer basis, IP-to-IP call redirection for the gateway.
To enable global IP-to-IP call redirection for all VoIP dial peers, use voice service configuration mode. To specify IP-to-IP call redirection for a specific VoIP dial peer, configure the dial peer in dial peer configuration mode.
Note
Examples
The following example specifies that on VoIP dial peer 99, IP-to-IP redirection is set:
dial-peer voice 99 voipredirect ip2ipRelated Commands
redirect ip2ip (voice service)
Redirects SIP phone calls to SIP phone calls globally on a gateway using the Cisco IOS voice gateway.
redirect ip2ip (voice service)
To redirect SIP phone calls to SIP phone calls globally on a gateway using the Cisco IOS Voice Gateway, use the redirect ip2ip command in voice service configuration mode. To disable redirection, use the no form of this command.
redirect ip2ip
no redirect ip2ip
Syntax Description
This command has no arguments or keywords.
Command Default
Redirection is disabled.
Command Modes
Voice service configuration
Command History
12.2(15)ZJ
This command was introduced.
12.3(4)T
This command was integrated into Cisco IOS Release 12.3(4)T.
Usage Guidelines
Use this command to enable IP-to-IP call redirection globally on a gateway. Use the redirect ip2ip (dial peer) command to configure IP-to-IP redirection on a specific inbound dial peer.
Examples
The following example specifies that all VoIP dial peers use IP-to-IP redirection:
voice service voipredirect ip2ipRelated Commands
redirect ip2ip (dial peer)
Redirects SIP phone calls to SIP phone calls on a specific VoIP dial peer using the Cisco IOS voice gateway.
redirection (SIP)
To enable the handling of 3xx redirect messages, use the redirection command in SIP UA configuration mode. To disable the handling of 3xx redirect messages, use the no form of this command.
redirection
no redirection
Syntax Description
This command has no arguments or keywords.
Command Default
Redirection is enabled.
Command Modes
SIP UA configuration
Command History
Usage Guidelines
The redirection command applies to all Session Initiation Protocol (SIP) VoIP dial peers configured on the gateway.
The default mode of SIP gateways is to process incoming 3xx redirect messages according to RFC 2543. However if redirect handling is disabled with the no redirection command, the gateway treats the incoming 3xx responses as 4xx error class responses. To reset the default processing of 3xx messages, use the redirection command.
Examples
The following example disables processing of incoming 3xx redirection messages:
Router(config)# sip-uaRouter(config-sip-ua)# no redirectionRelated Commands
show sip-ua statistics
Displays response, traffic, and retry SIP statistics.
show sip-ua status
Displays SIP UA status.
refer-ood enable
To enable out-of-dialog refer (OOD-R) processing, use the refer-ood enable command in SIP user-agent configuration mode. To disable OOD-R, use the no form of this command.
refer-ood enable [request-limit]
no refer-ood enable
Syntax Description
request-limit
(Optional) Maximum number of concurrent incoming OOD-R requests that the router can process. Range: 1 to 500. Default: 500.
Command Default
OOD-R processing is disabled.
Command Modes
SIP UA configuration (config-sip-ua)
Command History
12.4(11)XJ
This command was introduced.
12.4(15)T
This command was integrated into Cisco IOS Release 12.4(15)T.
Usage Guidelines
Out of dialog Refer allows applications to establish calls using the SIP gateway or Cisco Unified CME. The application sets up the call and the user does not dial out from their own phone.
Examples
The following example shows how to enable OOD-R:
Router(config)# sip-uaRouter(config-sip-ua)# refer-ood enableRelated Commands
register e164
To configure a gateway to register or deregister a fully-qualified dial-peer E.164 address with a gatekeeper, use the register e164 command in dial peer configuration mode. To deregister the E.164 address, use the no form of this command.
register e164
no register e164
Syntax Description
This command has no arguments or keywords.
Command Default
No E.164 addresses are registered until you enter this command.
Command Modes
Dial peer configuration
Command History
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 E.164 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, +5550112, 5550112, and 4085550112 are fully qualified addresses; 408555.... is not. E.164 addresses are registered only for active interfaces, which are those that are not shut down. If an FXS port or its interface is shut down, the corresponding E.164 address is deregistered.
Tip
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.
gateway1(config)# dial-peer voice 111 potsgateway1(config-dial-peer)# port 1/0/0gateway1(config-dial-peer)# destination-pattern 5550112gateway1(config-dial-peer)# register e164The following commands deregister an address with the gatekeeper.
gateway1(config)# dial-peer voice 111 potsgateway1(config-dial-peer)# no register e164The following example shows that you must have a connection to a gatekeeper and must define a unique E.164 address before you can register an address.
gateway1(config)# dial-peer voice 222 potsgateway1(config-dial-peer)# port 1/0/0gateway1(config-dial-peer)# destination 919555....gateway1(config-dial-peer)# register e164ERROR-register-e164:Dial-peer destination-pattern is not a full E.164 numbergateway1(config-dial-peer)# no gatewaygateway1(config-dial-peer)# dial-peer voice 111 potsgateway1(config-dial-peer)# register 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
Command Default
The default Nariwake service registered caller ring cadence is ring 1.
Command Modes
Dial peer configuration
Command History
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 2Related Commands
destination-pattern not-provided
Specifies the port to receive the incoming calls that have no called-party number.
registrar
To enable Session Initiation Protocol (SIP) gateways to register E.164 numbers on behalf of analog telephone voice ports (FXS), IP phone virtual voice ports (EFXS), and SCCP phones with an external SIP proxy or SIP registrar, use the registrar command in SIP UA configuration mode. To disable registration of E.164 numbers, use the no form of this command.
registrar {dns:address | ipv4:destination-address} aor-domain expires seconds [tcp [tls]] type [secondary] [scheme string]
no registrar [secondary]
Syntax Description
Command Default
Registration is disabled.
Command Modes
SIP UA configuration
Command History
Usage Guidelines
This command enables the gateway to register E.164 telephone numbers with primary and secondary external SIP registrars.
By default, SIP gateways do not generate SIP register messages.
Examples
The following example specifies registration with a primary and secondary registrar server.
...sip-uaretry invite 3retry register 3timers register 150registrar ipv4:10.8.17.40 expires 3600 secondary...The following example specifies an IP address with TCP.
...sip-uaretry invite 3retry register 3timers register 150registrar ipv4:10.8.17.40 tcp...The following example specifies an IP address with TLS over TCP.
...sip-uaretry invite 3retry register 3timers register 150registrar ipv4:10.8.17.40 tcp tls...The following example specifies a URL scheme with SIP security (SIPS).
...sip-uaretry invite 3retry register 3timers register 150registrar ipv4:10.8.17.40 scheme sips...Related Commands
registration retries
To set the number of times that Skinny Client Control Protocol (SCCP) tries to register with a Cisco Unified CallManager, use the registration retries command in SCCP Cisco CallManager configuration mode. To reset this number to the default value, use the no form of this command.
registration retries retry-attempts
no registration retries
Syntax Description
Command Default
3 registration attempts
Command Modes
SCCP Cisco CallManager configuration
Command History
Usage Guidelines
Use this command to control the number of registration retries before SCCP confirms that it cannot register with the Cisco Unified CallManager. When SCCP confirms that it cannot register to the current Cisco Unified CallManager (if the number of registration requests sent without an Ack reaches the registration retries value), SCCP tries to register with the next Cisco Unified CallManager.
Note
Examples
The following example sets the number of registration retries to 15:
Router(config-sccp-ccm)# registration retries 15Related Commands
registration timeout
To set the length of time between registration messages sent from Skinny Client Control Protocol (SCCP) to the Cisco Unified CallManager, use the registration timeout command in SCCP Cisco CallManager configuration mode. To reset the length of time to the default value, use the no form of this command.
registration timeout seconds
no registration timeout
Syntax Description
Command Default
3 seconds
Command Modes
SCCP Cisco CallManager configuration
Command History
Usage Guidelines
Whenever SCCP sends the registration message to the Cisco Unified CallManager, it initiates this timer. Once the timeout occurs, it sends the next registration message unless the number of messages without an Ack reaches the number set by the registration retries command. Use this command to set the Cisco Unified CallManager registration timeout parameter value.
Note
Examples
The following example sets the length of time between registration messages sent from SCCP to the Cisco Unified CallManager to 12 seconds:
Router(config-sccp-ccm)# registration timeout 12Related Commands
rel1xx
To enable all Session Initiation Protocol (SIP) provisional responses (other than 100 Trying) to be sent reliably to the remote SIP endpoint, use the rel1xx command in SIP configuration mode. To reset to the default, use the no form of this command.
rel1xx {supported value | require value | disable}
no rel1xx
Syntax Description
Command Default
supported with the 100rel value
Command Modes
SIP configuration
Command History
Usage Guidelines
The use of resource reservation with SIP requires that the reliable provisional feature for SIP be enabled either at the VoIP dial-peer level or globally on the router.
There are two ways to configure reliable provisional responses:
•
•
The voice-class sip rel1xx command in dial peer configuration mode takes precedence over the rel1xx command in global configuration mode with one exception: If the voice-class sip rel1xx command is used with the system keyword, the gateway uses what was configured under the rel1xx command in global configuration mode.
Enter SIP configuration mode from voice-service VoIP configuration mode as shown in the following example.
Examples
The following example shows use of the rel1xx command with the value 100rel:
Router(config)# voice service voipRouter(config-voi-srv)# sipRouter(conf-serv-sip)# rel1xx supported 100relRelated Commands
sip
Enters SIP configuration mode from voice-service VoIP configuration mode.
voice-class sip rel1xx
Provides provisional responses for calls on a dial peer basis.
remote-party-id
To enable translation of the SIP header Remote-Party-ID, use the remote-party-id command in SIP UA configuration mode. To disable Remote-Party-ID translation, use the no form of this command.
remote-party-id
no remote-party-id
Syntax Description
This command has no arguments or keywords.
Command Default
Remote-Party-ID translation is enabled
Command Modes
SIP UA configuration
Command History
Usage Guidelines
When the remote-party-id command is enabled, one of the following calling information treatments occurs:
•
•
Examples
The following example shows the Remote-Party-ID translation being enabled:
Router(config-sip-ua)# remote-party-idRelated Commands
req-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} [{audio bandwidth | video bandwidth} default | max bandwidth-value]
no req-qos
Syntax Description
Defaults
best-effort
Command Modes
Dial peer configuration
Command History
11.3(1)T
This command was introduced on the Cisco 3600 series routers.
12.3(4)T
Keywords added to support audio and video streams.
Usage Guidelines
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.
This command is applicable only to VoIP dial peers.
Examples
The following example configures guaranteed-delay as the requested quality of service to a dial peer:
dial-peer voice 10 voipreq-qos guaranteed-delayThe following example configures guaranteed-delay and requests a default bandwidth level of 768 kbps for video streams:
dial-peer voice 20 voipreq-qos guaranteed-delay video bandwidth default 768Related Commands
acc-qos
Defines the acceptable QoS for any inbound and outbound call on a VoIP dial peer.
request (XML transport)
To set the XML transport mode request handling parameters, use the request command in XML transport configuration mode. To disable the XML transport request parameter setting, use the no form of this command
request {outstanding number | timeout seconds}
no request
Syntax Description
Command Default
The default for outstanding is 1 and the default for timeout is 0 (no timeout).
Command Modes
XML transport configuration
Command History
Usage Guidelines
Use this command to set the request timeout. A value of 0 seconds specifies no timeout. This timeout applies to the request being processed and not outstanding requests as described below. The specified timeout limits the amount of time between the request being dequeued by the application and the completion of the processing of that request.
Use this command to specify the number of outstanding requests allowed per application for the specified transport mode. The outstanding requests are those requests that are queued at the application for processing but have not yet been processed.
Examples
The following example shows how to enter XML transport configuration mode, set the XML transport request timeout to 10 seconds, and exit XML transport configuration mode:
Router(config)# ixi transport httpRouter(conf-xml-trans)# request timeout 10Related Commands
reset
To reset a set of digital signal processors (DSPs), use the reset command in global configuration mode.
reset number
Syntax Description
Command Default
No default behavior or values.
Command Modes
Global configuration
Command History
12.0(5)XE
This command was introduced on the Cisco 7200 series.
12.0(7)T
This command was integrated into 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 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
Command Default
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
Usage Guidelines
This command defines the resource load levels that trigger 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 channel-associated signaling (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 is chosen over a gateway that has reported limited resources.
Examples
The following example defines the H.323 resource limits for a gateway.
gateway1(config-gateway)# resource threshold high 70 low 60Related Commands
resource-pool (mediacard)
To create a Digital Signal Processor (DSP) resource pool on ad-hoc conferencing and transcoding port adapters, use the resource-pool command in mediacard configuration mode. To remove the DSP resource pool and release the associated DSP resources, use the no form of this command.
resource-pool identifier dsps number
no resource-pool identifier dsps number
Syntax Description
Command Default
No default behavior or values
Command Modes
Mediacard configuration
Command History
Usage Guidelines
The DSP resource pool identifier should be unique across the same Communication Media Module (CMM). Removing a resource pool may cause the profile using that resource pool to be disabled if it is the last resource pool in the profile.
Examples
The following example shows how to create a DSP resource pool:
resource-pool headquarters_location1 dsps 2Related Commands
debug mediacard
Displays debugging information for DSPRM.
show mediacard
Displays information about the selected media card.
response (XML application)
To set XML application response parameters, use the response command in XML application configuration mode. To disable response parameter settings, use the no form of this command.
response {formatted | timeout {-1 | seconds}}
no response {formatted | timeout {-1 | seconds}}
Syntax Description
Command Default
The default for the timeout keyword is -1 indicating not application specified timeout.
Command Modes
XML application configuration
Command History
Usage Guidelines
The response timeout specified in this command, if other than -1 which is the default, overwrites the timeout value specified in the request (XML transport) command that sets the timeout at the transport level.
The same http transport layer could have multiple applications active at the same time. You can set the timeout for each application individually or have all of the applications to use the same timeout value set at transport layer using the request (XML transport) command in XML transport configuration mode.
Examples
The following example shows how to enter XML application configuration mode, set XML response parameters in formatted human readable XML, and exit XML application configuration mode:
Router(config)# ixi application mibRouter(conf-xml-app)# response formattedRelated Commands
ixi application mib
Enters XML application configuration mode.
request (XML transport)
Set the XML transport mode request handling parameters.
response size (XML transport)
To set the response transport fragment size, use the response size command in XML transport configuration mode. To disable the response transport fragment size setting, use the no form of this command.
response size kBps
no response size
Syntax Description
kBps
Size of the fragment in the response buffer in kilobytes. Valid range is 1 to 64 kB. The default is 4 kB.
Command Modes
XML transport configuration
Command History
Usage Guidelines
The fragment size is constrained by the transport type. The CLI help provides input guidelines.
Examples
The following example shows how to enter XML transport configuration mode, set XML transport fragment size to 32 Kbytes, and exit XML transport configuration mode:
Router(config)# ixi transport httpRouter(conf-xml-trans)# response size 32Related 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 reset to the default, use the no form of this command.
response-timeout seconds
no response-timeout seconds
Syntax Description
Command Default
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 sets response timeout to 1 second.
settlement 0response-timeout 1Related Commands
retries (auto-config application)
To set the number of download retry attempts for an auto-configuration application, use the retries command in auto-config application configuration mode. To reset to the default, use the no form of this command.
retries number
no retries
Syntax Description
Command Default
The default value is 2.
Command Modes
Auto-config application configuration
Command History
12.3(8)XY
This command was introduced on the Communication Media Module.
12.3(14)T
This command was integrated into Cisco IOS Release 12.3(14)T.
Examples
The following example shows the retries command used to set the number of retries for an auto-configuration application to 3:
Router(auto-config-app)# retries 3Related Commands
retry bye
To configure the number of times that a BYE request is retransmitted to the other user agent, use the retry bye command in SIP UA configuration mode. To reset to the default, use the no form of this command.
retry bye number
no retry bye number
Syntax Description
Command Default
10 retries
Command Modes
SIP UA configuration
Command History
Usage Guidelines
To reset this command to the default value, you can also use the default command.
Examples
The following example sets the number of BYE retries to 5.sip-uaretry bye 5Related Commands
retry cancel
To configure the number of times that a CANCEL request is retransmitted to the other user agent, use the retry cancel command in SIP UA configuration mode. To reset to the default, use the no form of this command.
retry cancel number
no retry cancel number
Syntax Description
Command Default
10 retries
Command Modes
SIP UA configuration
Command History
Usage Guidelines
To reset this command to the default value, you can also use the default command.
Examples
The following example sets the number of cancel retries to 5.sip-uaretry cancel 5Related Commands
retry comet
To configure the number of times that a COMET request is retransmitted to the other user agent, use the retry comet command in SIP UA configuration mode. To reset to the default, use the no form of this command.
retry comet number
no retry comet
Syntax Description
Command Default
10 retries
Command Modes
SIP UA configuration
Command History
Usage Guidelines
COMET, or conditions met, indicates if preconditions for a given call or session have been met. This command is applicable only with calls (other than best-effort) that involve quality of service (QoS).
Use the default number of 10 retries, when possible. Lower values, such as 1, can lead to an increased chance of the message not being received by the other user agent.
Examples
The following example configures a COMET request to be retransmitted 8 times:
Router(config)# sip-uaRouter(config-sip-ua)# retry comet 8Related Commands
retry interval
To define the time between border element attempts delivery of unacknowledged call-detail-record (CDR) information, use the retry interval command in Annex G neighbor usage configuration mode. To reset to the default, use the no form of this command.
retry interval seconds
no retry interval
Syntax Description
seconds
Retry interval between delivery attempts, in seconds. Range is from 1 to 3600 (1 hour). The default is 900.
Command Default
900 seconds
Command Modes
Annex G neighbor usage configuration
Command History
Usage Guidelines
Use this command to set the interval during which the border element attempts delivery of unacknowledged call-detail-record (CDR) information.
Examples
The following example sets the retry interval to 2700 seconds (45 minutes):
Router(config-nxg-neigh-usg)# retry interval 2700Related Commands
retry invite
To configure the number of times that a Session Initiation Protocol (SIP) INVITE request is retransmitted to the other user agent, use the retry invite command in SIP UA configuration mode. To reset to the default, use the no form of this command.
retry invite number
no retry invite number
Syntax Description
Command Default
6 retries
Command Modes
SIP UA configuration
Command History
Usage Guidelines
To reset this command to the default value, you can also use the default command.
When configuring SIP using SIP user-agent configuration commands such as the retry invite command, the use of the default values for the commands causes the rotary function to not take effect. The rotary function is when you set up more than one VoIP dial peer for the same destination pattern, and the dial peers are assigned to different targets. Assign different targets so that if the call cannot be set up with the first dial peer (preference one), the next dial peer can be tried.
To use the rotary function within SIP, set the retry value for the SIP retry invite command to 4 or less.
Examples
The following example sets the number of invite retries to 5.
sip-uaretry invite 5Related Commands
retry keepalive (SIP)
To set the retry count for keepalive retransmission, use the retry keepalive command in SIP UA configuration mode. To restore the retry count to the default value for keepalive retransmission, use the no form of this command.
retry keepalive count
no retry keepalive count
Syntax Description
Command Default
The default value for the retry keepalive retransmission is 6.
Command Modes
SIP UA configuration
Command History
Usage Guidelines
Sets the keepalive retransmissions retry count.
Examples
The following example sets the retry for the keepalive retransmissions to 8:
sip-uaretry keepalive 8Related Commands
retry notify
To configure the number of times that the notify message is retransmitted to the user agent that initiated the transfer or Refer request, use the retry notify command in SIP UA configuration mode. To reset to the default, use the no form of this command.
retry notify number
no retry notify
Syntax Description
Command Default
10 retries
Command Modes
SIP UA configuration
Command History
Usage Guidelines
A notify message informs the user agent that initiated the transfer or refer request of the outcome of the Session Initiation Protocol (SIP) transaction.
Use the default number of 10 when possible. Lower values such as 1 can lead to an increased chance of the message not being received by the other user agent.
Examples
The following example configures a notify message to be retransmitted 10 times:
Router(config)# sip-uaRouter(config-sip-ua)# retry notify 10Related Commands
retry prack
To configure the number of times that the PRACK request is retransmitted to the other user agent, use the retry prack command in SIP UA configuration mode. To reset to the default, use the no form of this command.
retry prack number
no retry prack
Syntax Description
Command Default
10 retries
Command Modes
SIP UA configuration
Command History
Usage Guidelines
PRACK allows reliable exchanges of Session Initiation Protocol (SIP) provisional responses between SIP endpoints. Use the default number of 10 when possible. Lower values such as 1 can lead to an increased chance of the message not being received by the other user agent.
Examples
The following example configures a PRACK request to be retransmitted 9 times:
Router(config)# sip-uaRouter(config-sip-ua)# retry prack 9Related Commands
retry refer
To configure the number of times that the Refer request is retransmitted, use the retry refer command in SIP UA configuration mode. To reset to the default, use the no form of this command.
retry refer number
no retry refer
Syntax Description
Command Default
10 retries
Command Modes
SIP UA configuration
Command History
Usage Guidelines
A Session Initiation Protocol (SIP) Refer request is sent by the originating gateway to the receiving gateway and initiates call forward and call transfer capabilities.
When configuring the retry refer command, use the default number of 10 when possible. Lower values such as 1 can lead to an increased chance of the message not being received by the receiving gateway.
Examples
The following example configures a Refer request to be retransmitted 10 times:
Router(config)# sip-uaRouter(config-sip-ua)# retry refer 10Related Commands
show sip-ua retry
Displays the SIP retry attempts.
show sip-ua statistics
Displays response, traffic, timer, and retry statistics.
retry register
To set the total number of Session Initiation Protocol (SIP) Register messages that the gateway should send, use the retry register command in SIP UA configuration mode. To reset this number to the default, use the no form of this command.
retry register retries
no retry register
Syntax Description
retries
Total number of Register messages that the gateway should send. Range is 1 to 10. Default is 10.
Command Default
10 retries
Command Modes
SIP UA configuration
Command History
12.2(15)ZJ
This command was introduced.
12.3(4)T
This command was integrated into Cisco IOS Release 12.3(4)T.
Usage Guidelines
Use the default number of 10 when possible. Lower values such as 1 can lead to an increased chance of the message not being received by the other user agent.
Examples
The following example specifies that the gateway sends nine Register messages.
sip-uaretry invite 9retry register 9timers register 150Related Commands
retry rel1xx
To configure the number of times that the reliable 1xx response is retransmitted to the other user agent, use the retry rel1xx command in SIP UA configuration mode. To reset to the default, use the no form of this command.
retry rel1xx number
no retry rel1xx
Syntax Description
Command Default
6 retries
Command Modes
SIP UA configuration
Command History
Usage Guidelines
Use the default number of 6 when possible. Lower values such as 1 can lead to an increased chance of the message not being received by the other user agent.
Examples
The following example configures the reliable 1xx response to be retransmitted 7 times:
Router(config)# sip-uaRouter(config-sip-ua)# retry rel1xx 7Related Commands
retry response
To configure the number of times that the response message is retransmitted to the other user agent, use the retry response command in SIP UA configuration mode. To reset to the default, use the no form of this command.
retry response number
no retry response
Syntax Description
Command Default
6 retries
Command Modes
SIP UA configuration
Command History
Usage Guidelines
To reset this command to the default value, you can also use the default command.
Examples
The following example sets the number of response retries to 5.
sip-uaretry response 5Related Commands
retry subscribe
To configure the number of times that a SIP SUBSCRIBE message is retransmitted to the other user agent, use the retry subscribe command in SIP UA configuration mode. To reset to the default, use the no form of this command.
retry subscribe number
no retry subscribe number
Syntax Description
Command Default
10 retries
Command Modes
SIP UA configuration
Command History
Usage Guidelines
Use the retry timer command to configure retry intervals for this command. The default value for retry timer is 1000 ms, and the range is 10 to 100. Setting the timer to lower values can cause the application to get a failure response more quickly.
Examples
The following example sets the number of subscribe retries to 5:
sip-uaretry subscribe 5Related Commands
retry window
To define the total time for which a border element attempts delivery, use the retry window command in Annex G neighbor usage configuration mode. To reset to the default, use the no form of this command.
retry window window-value
no retry window
Syntax Description
window-value
Window value, in minutes. Range is from 1 to 65535. Default is 1440 minutes (24 hours).
Command Default
1440 minutes (24 hours)
Command Modes
Annex G neighbor usage configuration
Command History
Usage Guidelines
Use this command to set the total time during which a border element attempts delivery of unacknowledged call-detail-record (CDR) information.
Examples
The following example sets the retry window to 15 minutes:
Router(config-nxg-neigh-usg)# retry window 15Related 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 reset to the default, use the no form of this command.
retry-delay seconds
no retry-delay
Syntax Description
seconds
Interval, in seconds, between attempts to connect with the settlement provider. Range is from 1 to 600.
Command Default
2 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 reset to the default, use the no form of this command.
retry-limit number
no retry-limit number
Syntax Description
Command Default
1 retry
Command Modes
Settlement configuration
Command History
Usage Guidelines
If no connection is established after the configured number of retries has been attempted, 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
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 ring, use the no form of this command.
ring cadence-number
no ring cadence-number
Syntax Description
Command Default
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 does not work if it is not specified within the context of a dial peer. For information on creating a dial peer, see 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 reset to the default, use the no form of this command.
ring cadence {pattern-number | define pulse interval}
no ring cadence
Syntax Description
Command Default
Ring cadence defaults to the pattern that 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 Cisco 3600 series routers, only one or two pairs of digits can be entered under the define keyword.
Examples
The following example sets the ring cadence to 1 second on and 2 seconds off on voice port 1/0/0:
voice-port 1/0/0ring cadence pattern04Related Commands
cptone
Specifies the default tone, ring, and cadence settings according to country.
ring frequency
Specifies the ring frequency for a specified FXS voice port.
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 reset to the default, use the no form of this command.
ring frequency hertz
no ring frequency hertz
Syntax Description
hertz
Ring frequency, in hertz, used in the FXS interface. Valid entries are as follows:
•
Command Default
Cisco 3600 series routers: 25 Hz
Command Modes
Voice-port configuration
Command History
Usage Guidelines
Use this 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 sets the ring frequency on the voice port to 25 Hz:
voice-port 1/0/0ring frequency 25Related Commands
ring cadence
Specifies the ring cadence for an FXS voice port.
ring number
Specifies the number of rings for a specified FXO voice port.
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 reset to the default, use the no form of this command.
ring number number
no ring number number
Syntax Description
Command Default
1 ring
Command Modes
Voice port configuration
Command History
Usage Guidelines
Use this 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 sets 5 as the maximum number of rings to be detected before closing a connection over this voice port:
voice-port 1/0/0ring number 5Related Commands
roaming (dial peer)
To enable roaming capability for a dial peer, use the roaming command in dial peer configuration mode. To disable roaming capability, use the no form of this command.
roaming
no roaming
Syntax Description
This command has no arguments or keywords.
Command Default
No roaming
Command Modes
Dial peer configuration
Command History
12.1(1)T
This command was introduced on the following platforms: Cisco 2600 series, Cisco 3600 series, and Cisco AS5300.
Usage Guidelines
Use this command to enable 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 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 roaming capability for a dial peer:
dial-peer voice 10 voiproamingRelated Commands
roaming (settlement)
To enable roaming capability for a settlement provider, use the roaming command in settlement configuration mode. To disable roaming capability, use the no form of this command.
roaming
no roaming
Syntax Description
This command has no arguments or keywords.
Command Default
No roaming
Command Modes
Settlement configuration
Command History
12.1(1)T
This command was introduced on the following platforms: Cisco 2600 series, Cisco 3600 series, and Cisco AS5300.
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 roaming capability for a settlement provider:
settlement 0roamingRelated Commands
rrq dynamic-prefixes-accept
To enable processing of additive registration request (RRQ) RAS messages and dynamic prefixes on the gatekeeper, use the rrq dynamic-prefixes-accept command in gatekeeper configuration mode. To disable processing of additive RRQ messages and dynamic prefixes, use the no form of this command.
rrq dynamic-prefixes-accept
no rrq dynamic-prefixes-accept
Syntax Description
This command has no arguments or keywords.
Command Default
In Cisco IOS Release 12.2(15)T, the default was set to enabled. In Cisco IOS Release 12.3(3), the default is set to disabled.
Command Modes
Gatekeeper configuration
Command History
Usage Guidelines
In Cisco IOS Release 12.2(15)T, the default for the rrq dynamic-prefixes-accept command was set to enabled so that the gatekeeper automatically received dynamic prefixes in additive RRQ messages from the gateway. Beginning in Cisco IOS Release 12.3(3), the default is set to disabled, and you must specify the command to enable the functionality.
Examples
The following example allows the gatekeeper to process additive RRQ messages and dynamic prefixes from the gateway:
Router(config-gk)# rrq dynamic-prefixes-acceptRelated Commands
ras rrq dynamic prefixes
Enables advertisement of dynamic prefixes in additive RRQ messages on the gateway.
rsvp
To enable RSVP support on a transcoding or MTP device, use the rsvp command in DSP farm profile configuration mode. To disable RSVP support, use the no form of this command.
rsvp
no rsvp
Syntax Description
This command has no arguments or keywords.
Command Default
Disabled
Command Modes
DSP farm profile configuration
Command History
Usage Guidelines
This command enables a transcoder or MTP device to register as RSVP-capable with Cisco Unified CallManager. The SCCP device acts as an RSVP agent under the control of Cisco Unified CallManager. To support RSVP, you must also enable the codec pass-through command.
Note
Examples
The following example enables RSVP support on the transcoding device defined by profile 200:
Router(config)# dspfarm profile 200 transcodeRouter(config-dspfarm-profile)# rsvpRouter(config-dspfarm-profile)# codec pass-throughRelated Commands
rtp payload-type
To identify the payload type of a Real-Time Transport Protocol (RTP) packet, use the rtp payload-type command in dial peer voice configuration mode. To remove the RTP payload type, use the no form of this command.
rtp payload-type {cisco-cas-payload number | cisco-clear-channel number | cisco-codec-fax-ack number | cisco-codec-fax-ind number | cisco-codec-gsmamrnb number | cisco-codec-ilbc number | cisco-codec-video-h263+ number | cisco-codec-video-h264 number | cisco-fax-relay number | cisco-pcm-switch-over-alaw number | cisco-pcm-switch-over-ulaw number | cisco-rtp-dtmf-relay number | nte number | nse number} [comfort-noise {13 | 19}]
no rtp payload-type {cisco-cas-payload number | cisco-clear-channel number | cisco-codec-fax-ack number | cisco-codec-fax-ind number | cisco-codec-gsmamrnb number | cisco-codec-ilbc number | cisco-codec-video-h263+ number | cisco-codec-video-h264 number | cisco-fax-relay number | cisco-pcm-switch-over-alaw number | cisco-pcm-switch-over-ulaw number | cisco-rtp-dtmf-relay number | nte number | nse number} [comfort-noise {13 | 19}]
Syntax Description
Command Default
No RTP payload type is configured.
Command Modes
Dial peer voice configuration (config-dial-peer)
Command History
Usage Guidelines
Use this command to identify the payload type of an RTP. Use this command after the dtmf-relay command is used to choose the NTE method of DTMF relay for a Session Initiation Protocol (SIP) call.
Configured payload types of NSE and NTE exclude certain values that have been previously hard-coded with Cisco-proprietary meanings. Do not use the following numbers, which have preassigned values: 96, 97, 100, 117, 121 to 123, and 125 to 127.
Use of these values results in an error message when the command is entered. You must first reassign the value in use to a different unassigned number, for example:
rtp payload-type cisco-codec-ilbc 100ERROR: value 100 in use!rtp payload-type nse 105rtp payload-type cisco-codec-ilbc 100Examples
The following example identifies the RTP payload type as GSMAMR-NB124:
Router(config-dial-peer)# rtp payload-type cisco-codec-gsmamrnb 124The following example identifies the RTP payload type as NTE 99:
Router(config-dial-peer)# rtp payload-type nte 99The following example identifies the RTP payload type for the iLBC as 100:
Router(config-dial-peer)# rtp payload-type cisco-codec-ilbc 100Related Commands
dtmf-relay
Specifies how an H.323 or SIP gateway relays DTMF tones between telephony interfaces and an IP network.
rtsp client session history duration
To specify how long to keep Real Time Streaming Protocol (RTSP) client history records in memory, use the rtsp client session history duration command in global configuration mode. To reset to the default, use the no form of this command.
rtsp client session history duration minutes
no rtsp client session history duration
Syntax Description
Command Default
10 minutes
Command Modes
Global configuration
Command History
Examples
The following example sets the duration for 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 Real Time Streaming Protocol (RTSP) client session history, use the rtsp client session history records command in global configuration mode. To reset 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
Command Default
50 records
Command Modes
Global configuration
Command History
Examples
The following example specifies that a total of 500 records are to be kept in the RTSP client history:
rtsp client session history records 500Related Commands
rtsp client timeout connect
To set the number of seconds allowed for the router to establish a TCP connection to a Real -Time Streaming Protocol (RTSP) server, use the rtsp client timeout connect command in global configuration mode. To reset to the default, use the no form of this command.
rtsp client timeout connect seconds
no rtsp client timeout connect
Syntax Description
seconds
How long, in seconds, the router waits to connect to the server before timing out. Range is 1 to 20.
Command Default
3 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
This command determines when the router abandons its attempt to connect to an RTSP server and declares a timeout error, if a connection cannot be established after the specified number of seconds.
Examples
The following example sets the connection timeout to 10 seconds:
rtsp client timeout connect 10Related Commands
rtsp client timeout message
To set the number of seconds that the router waits for a response from a Real -Time Streaming Protocol (RTSP) server, use the rtsp client timeout message command in global configuration mode. To reset to the default, use the no form of this command.
rtsp client timeout message seconds
no rtsp client timeout message
Syntax Description
seconds
How long, in seconds, the router waits for a response from the server after making a request. Range is 1 to 20.
Command Default
3 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
This command sets how long the router waits for the RTSP server to respond to a request before declaring a timeout error.
Examples
The following example sets the request timeout to 10 seconds:
rtsp client timeout message 10Related Commands
rule (ENUM configuration)
To define a rule for an ENUM match table, use the rule command in ENUM configuration mode. To delete the rule, use the no form of this command.
rule rule-number preference /match-pattern/ /replacement-rule /domain-name
no rule rule-number preference /match-pattern/ /replacement-rule /domain-name
Syntax Description
Command Default
No default behavior or values
Command Modes
ENUM configuration
Command History
Usage Guidelines
Table 31 shows examples of match patterns, input strings, and result strings for the rule (voice translation-rule) command.
Rules are entered in any order, but their preference number determines the sequence in which they are used for matching against the input string, which is a called number. A lower preference number is used before a higher preference number.
If a match is found, the input string is modified according to the replacement rule, and the E.164 domain name is attached to the modified number. This longer number is sent to a Domain Name System (DNS) server to determine a destination for the call. The server returns one or more URLs as possible destinations. The originating gateway tries to place the call using each URL in order of preference. If a call cannot be completed using any of the URLs, the call is disconnected.
Examples
The following example defines ENUM rule number 3 with preference 2. The beginning of the call string is checked for digits 9011; when a match is found, 9011 is replaced with 1408 and the call is sent out as an e164.arpa number.
Router(config)# voice enum-match-table numberRouter(config-enum)# rule 3 2 /^9011\(.*\)//+1408\1/ arpaRelated Commands
rule (voice translation-rule)
To define a translation rule, use the rule command in voice translation-rule configuration mode. To delete the translation rule, use the no form of this command.
Match and Replace Rule
rule precedence /match-pattern/ /replace-pattern/
[type {match-type replace-type} [plan {match-type replace-type}]]no rule precedence
Reject Rule
rule precedence reject /match-pattern/ [type match-type [plan match-type]]
no rule precedence
Syntax Description
Command Default
No default behavior or values
Command Modes
Voice translation-rule configuration
Command History
12.2(11)T
This command was introduced with a new syntax in voice-translation-rule configuration mode.
Usage Guidelines
Note
A translation rule applies to a calling party number (automatic number identification [ANI]) or a called party number (dialed number identification service [DNIS]) for incoming, outgoing, and redirected calls within Cisco H.323 voice-enabled gateways.
Number translation occurs several times during the call routing process. In both the originating and terminating gateways, the incoming call is translated before an inbound dial peer is matched, before an outbound dial peer is matched, and before a call request is set up. Your dial plan should account for these translation steps when translation rules are defined.
Table 32 shows examples of match patterns, input strings, and result strings for the rule (voice translation-rule) command.
The software verifies that a replacement pattern is in a valid E.164 format that can include the permitted special characters. If the format is not valid, the expression is treated as an unrecognized command.
The number type and calling plan are optional parameters for matching a call. If either parameter is defined, the call is checked against the match pattern and the selected type or plan value. If the call matches all the conditions, the call is accepted for additional processing, such as number translation.
Several rules may be grouped together into a translation rule, which gives a name to the rule set. A translation rule may contain up to 15 rules. All calls that refer to this translation rule are translated against this set of criteria.
The precedence value of each rule may be used in a different order than that in which they were typed into the set. Each rule's precedence value specifies the priority order in which the rules are to be used. For example, rule 3 may be entered before rule 1, but the software uses rule 1 before rule 3.
The software supports up to 128 translation rules. A translation profile collects and identifies a set of these translation rules for translating called, calling, and redirected numbers. A translation profile is referenced by trunk groups, source IP groups, voice ports, dial peers, and interfaces for handling call translation.
Examples
The following example applies a translation rule. If a called number starts with 5550105 or 70105, translation rule 21 uses the rule command to forward the number to 14085550105 instead.
Router(config)# voice translation-rule 21Router(cfg-translation-rule)# rule 1 /^5550105/ /14085550105/Router(cfg-translation-rule)# rule 2 /^70105/ /14085550105/In the next example, if a called number is either 14085550105 or 014085550105, after the execution of translation rule 345, the forwarding digits are 50105. If the match type is configured and the type is not "unknown," dial-peer matching is required to match the input string numbering type.
Router(config)# voice translation-rule 345Router(cfg-translation-rule)# rule 1 /^14085550105/ /50105/ plan any nationalRouter(cfg-translation-rule)# rule 2 /^014085550105/ /50105/ plan any nationalRelated Commands
show voice translation-rule
Displays the parameters of a translation rule.
voice translation-rule
Initiates the voice translation-rule definition.
