|
|
Table Of Contents
subscription asnl session history
supervisory disconnect anytone
supervisory disconnect dualtone
supervisory disconnect dualtone voice-class
supervisory dualtone-detect-params
supplementary-service h225-notify cid-update (dial-peer)
supplementary-service h225-notify cid-update (voice-service)
supplementary-service h450.12 (dial-peer)
supplementary-service h450.12 (voice-service)
supplementary-service h450.2 (dial-peer)
supplementary-service h450.2 (voice-service)
supplementary-service h450.3 (dial-peer)
supplementary-service h450.3 (voice-service)
ss7 mtp2-variant
To configure a Signaling System 7 (SS7) signaling link, use the ss7 mtp2-variant command in global configuration mode. To restore the designated default, use the no form of this command.
ss7 mtp2-variant [bellcore channel | itu-white channel | ntt channel | ttc channel] [parameters]
no ss7 mtp2-variant
Syntax Description
bellcore
Configures the router for Telcordia Technologies (formerly Bellcore) standards.
channel
Message Transfer Part Layer 2 (MTP2) serial channel number. Range is from 0 to 3.
itu-white
Configures the SS7 channel with the ITU-white protocol variant.
ntt
Configures the router for NTT (Japan) standards.
Note
This keyword is not available with the PCR feature.
ttc
Configures the router for Japanese Telecommunications Technology Committee (TTC) standards.
Note
parameters
(Optional) Configures a particular standard. See Table 159, Table 160, Table 161, and Table 162 in the "Usage Guidelines" section for accepted parameters.
Defaults
bellcore
Command Modes
Global configuration
Command History
Usage Guidelines
Note
The MTP2 variant has timers and parameters that can be configured using the values listed in the following tables. To restore the designated default, use the no or the default form of the command (see the "Examples" section below).
Examples
The following example configures an SS7 channel (link) for Preventive Cyclic Retransmission (PCR) with forced retransmission initiated. In this example, SS7 channel 0 is configured with the ITU-white protocol variant using the PCR error correction method.
Router# configure terminalRouter(config)# ss7 mtp2-variant itu-white 0Router(config-ITU)# error-correction pcr forced-retransmission enabled N2 1000Router(config-ITU)# endThe following example disables error-correction:
Router(config-ITU)# no error-correction
Related Commands
ss7 mtp2-variant bellcore
To configure the router for Telcordia Technologies (formerly Bellcore) standards, use the ss7 mtp2-variant bellcore command in global configuration mode.
ss7 mtp2-variant bellcore [channel] [parameters]
Syntax Description
channel
(Optional) Channel. Range is from 0 to 3.
parameters
(Optional) Particular Bellcore standard. See Table 159 for descriptions, defaults, and ranges.
Defaults
Bellcore is the default variant if no other is configured.
See Table 159 for default parameters.Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
This MTP2 variant has timers and parameters that can be configured using the values listed in Table 159. To restore the designated default, use the no or the default form of the command (see example below).
Note
Examples
The following example sets the aligned/ready timer duration on channel 0 to 30,000 ms:
ss7 mtp2-variant bellcore 0 T1 30000The following example restores the aligned/ready timer default value of 13,000 ms:
ss7 mtp2-variant bellcore 0 no T1Related Commands
ss7 mtp2-variant itu
Specifies the MTP2-variant as ITU.
ss7 mtp2-variant ntt
Specifies the MTP2-variant as NTT.
ss7 mtp2-variant ttc
Specifies the MTP2-variant as TTC.
ss7 mtp2-variant itu
To configure the router for ITU (International Telecom United) standards, use the ss7 mtp2-variant itu command in global configuration mode.
ss7 mtp-variant itu [channel] [parameters]
Syntax Description
channel
Channel. Range is from 0 to 3.
parameters
(Optional) Particular Bellcore standard. See Table 160 for descriptions, defaults, and ranges.
Defaults
Bellcore is the default variant if no other is configured.
See Table 160 for ITU default parameters.Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The ITU MTP2 variant has timers and parameters that can be configured using the values listed in Table 160. To restore the designated default, use the no or the default form of the command (see the example below).
Examples
The following example sets the emergency proving period on channel 1 to 10,000 ms:
ss7 mtp2-variant itu 1t4-Emergency-Proving 10000The following example restores the emergency proving period default value of 5,000 ms:
ss7 mtp2-variant itu 1default t4-Emergency-ProvingRelated Commands
ss7 mtp2-variant bellcore
Specifies the MTP2-variant as Bellcore.
ss7 mtp2-variant ntt
Specifies the MTP2-variant as NTT.
ss7 mtp2-variant ttc
Specifies the MTP2-variant as TTC.
ss7 mtp2-variant ntt
To configure the router for NTT (Japan) standards, use the ss7 mtp2-variant ntt command in global configuration mode.
ss7 mtp-variant ntt [channel] [parameters]
Syntax Description
channel
Channel. Range is from 0 to 3.
parameters
(Optional) Particular Bellcore standard. See Table 161 for descriptions, defaults, and ranges.
Defaults
Bellcore is the default variant if no other is configured.
See Table 161 for NTT default parameters.Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The NTT MTP2 variant has timers and parameters that can be configured using the values listed in Table 161. To restore the designated default, use the no or the default form of the command (see the example below).
Examples
The following example sets the SUERM error rate threshold on channel 2 to 100:
ss7 mtp2-variant ntt 2SUERM-threshold 100The following example restores the SUERM error rate threshold default value of 64:
ss7 mtp2-variant ntt 2no SUERM-thresholdRelated Commands
ss7 mtp2-variant bellcore
Specifies the MTP2-variant as Bellcore.
ss7 mtp2-variant itu
Specifies the MTP2-variant as ITU.
ss7 mtp2-variant ttc
Specifies the MTP2-variant as TTC.
ss7 mtp2-variant ttc
To configure the router for TTC (Japan Telecom) standards, use the ss7 mtp2-variant ttc command in global configuration mode.
ss7 mtp-variant ttc [channel] [parameters]
Syntax Description
channel
Channel. Range is from 0 to 3.
parameters
(Optional) Particular Bellcore standard. See Table 162 for descriptions, defaults, and ranges.
Defaults
Bellcore is the default variant if no other is configured.
See Table 162 for TTC default parameters.Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The TTC MTP2 variant has timers and parameters that can be configured using the values listed in Table 162. To restore the designated default, use the no or the default form of the command (see the example below).
Examples
The following example sets the maximum number of proving attempts for channel 3 to 3:
ss7 mtp2-variant ttc 3proving-attempts 3The following example restores the maximum number of proving attempts to the default value:
ss7 mtp2-variant ttc 3default proving-attemptsRelated Commands
ss7 mtp2-variant bellcore
Specifies the MTP2-variant as Bellcore.
ss7 mtp2-variant itu
Specifies the MTP2-variant as ITU.
ss7 mtp2-variant ntt
Specifies the MTP2-variant as NTT.
ss7 session
To create a Reliable User Datagram Protocol (RUDP) session and explicitly add an RUDP session to a Signaling System 7 (SS7) session set, use the ss7 session command in global configuration mode. To delete the session, use the no form of this command.
ss7 session session-id address destination-address destinaion-port local-address local-port [session-set session-number]
no ss7 session session-id
Syntax Description
Defaults
No session is configured.
Command Modes
Global configuration
Command History
Usage Guidelines
For the Cisco 2600-based SLT, you can configure a maximum of four sessions, two for each Cisco SLT. In a redundant VSC configuration, session 0 and session 2 are configured to one VSC, and session 1 and session 3 are configured to the other. Session 0/1 and session 2/3 run to the Cisco SLT.
The VSC must be configured to send messages to the local port, and it must be configured to listen on the remote port. You must also reload the router whenever you remove a session or change the parameters of a session.
This command replaces the ss7 session-0 address and ss7 session-1 address commands, which contain hard-coded session numbers. The new command is used for the new dual Ethernet capability.
The new CLI supports both single and dual Ethernet configuration by being backward compatible with the previous session-0 and session-1 commands so that you can configure a single Ethernet instead of two, if needed.
For the Cisco AS5350 and Cisco AS5400-based SLT, you can configure a maximum of two sessions, one for each signaling link. In a redundant MGC configuration, session 0 is configured to one MGC and session 1 is configured to the other.
The MGC must be configured to send messages to the local port, and the MGC must be configured to listen on the remote port.
You must reload the router whenever you remove a session or change the parameters of a session.
By default, each RUDP session must belong to SS7 session set 0. This allows backward compatibility with existing SS7 configurations.
If the session-set keyword is omitted, the session is added to the default SS7 session set 0. This allows backward compatibility with older configurations. Entering the no form of the command is still sufficient to remove the session ID for that RUDP session.
If you want to change the SS7 session set to which a session belongs, you have to remove the entire session first. This is intended to preserve connection and recovery logic.
Examples
The following example sets up two sessions on a Cisco 2611 and creates session set 2:
ss7 session-0 address 172.16.1.0 7000 172.16.0.0 7000 session-set 2ss7 session-1 address 172.17.1.0 7002 172.16.0.0 7001 session-set 2
Note
Related Commands
ss7 session cumack_t
To set the Reliable User Datagram Protocol (RUDP) cumulative acknowledgment timer for a specific SS7 signaling link session, use the ss7 session cumack_t command in global configuration mode. To reset to the default, use the no form of this command.
ss7 session-session number cumack_t milliseconds
no ss7 session-session number cumack_t
Caution
Syntax Description
Defaults
300 ms
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The cumulative acknowledgment timer determines when the receiver sends an acknowledgment. If the timer is not already running, it is initialized when a valid data, null, or reset segment is received. When the cumulative acknowledgment timer expires, the last in-sequence segment is acknowledged. The RUDP typically tries to "piggyback" acknowledgments on data segments being sent. However, if no data segment is sent in this period of time, it sends a standalone acknowledgment.
Examples
The following example sets up two sessions and sets the cumulative acknowledgment timer to 320 ms for each one:
ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7000ss7 session-0 cumack_t 320ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7001ss7 session-1 cumack_t 320Related Commands
ss7 session kp_t
To set the null segment (keepalive) timer for a specific SS7 signaling link session, use the ss7 session kp_t command in global configuration mode. To reset to the default, use the no form of this command.
ss7 session-session number kp_t milliseconds
no ss7 session-session number kp_t
Caution
Syntax Description
Defaults
2000 ms
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The null segment timer determines when a null segment (keepalive) is sent by the client Cisco 2600 series router. On the client, the timer starts when the connection is established and is reset each time a data segment is sent. If the null segment timer expires, the client sends a keepalive to the server to verify that the connection is still functional. On the server, the timer restarts each time a data or null segment is received from the client.
The value of the server's null segment timer is twice the value configured for the client. If no segments are received by the server in this period of time, the connection is no longer valid.
To disable keepalive, set this parameter to 0.
Examples
The following example sets up two sessions and sets a keepalive of 1,800 ms for each one:
ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7000ss7 session-0 kp_t 1800ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7001ss7 session-1 kp_t 1800Related Commands
ss7 session m_cumack
To set the maximum number of segments that can be received before the Reliable User Datagram Protocol (RUDP) sends an acknowledgment in a specific SS7 signaling link session, use the ss7 session m_cumack command in global configuration mode. To reset to the default, use the no form of this command.
ss7 session-session number m_cumack segments
no ss7 session-session number m_cumack
Caution
Syntax Description
Defaults
3 segments
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The cumulative acknowledgment counter records the number of unacknowledged, in-sequence data, null, or reset segments received without a data, null, or reset segment being sent to the transmitter. If this counter reaches the configured maximum, the receiver sends a standalone acknowledgment (a standalone acknowledgment is a segment that contains only acknowledgment information). The standalone acknowledgment contains the sequence number of the last data, null, or reset segment received.
If you set this parameter to 0, an acknowledgment is sent immediately after a data, null, or reset segment is received.
Examples
The following example sets up two sessions and in each session sets a maximum of two segments for receipt before acknowledgment:
ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7001ss7 session-0 m_cumack 2ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7000ss7 session-1 m_cumack 2Related Commands
ss7 session m_outseq
To set the maximum number of out-of-sequence segments that can be received before the Reliable User Datagram Protocol (RUDP) sends an extended acknowledgment in a specific SS7 signaling link session, use the ss7 session m_outseq command in global configuration mode. To reset to the default, use the no form of this command.
ss7 session-session number m_outseq segments
no ss7 session-session number m_outseq
Caution
Syntax Description
Defaults
3 segments
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The out-of-sequence acknowledgment counter records the number of data segments that have arrived out of sequence. If this counter reaches the configured maximum, the receiver sends an extended acknowledgment segment that contains the sequence numbers of the out-of-sequence data, null, and reset segments received. When the transmitter receives the extended acknowledgment segment, it retransmits the missing data segments.
If you set this parameter to 0, an acknowledgment is sent immediately after an out-of-sequence segment is received.
Examples
The following example sets up two sessions and sets a maximum number of four out-of-sequence segments for each session:
ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7001ss7 session-0 m_outseq 4ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7000ss7 session-1 m_outseq 4Related Commands
ss7 session m_rcvnum
To set the maximum number of segments that the remote end can send before receiving an acknowledgment in a specific SS7 signaling link session, use the ss7 session m_rcvnum command in global configuration mode. To reset to the default, use the no form of this command.
ss7 session-session number m_rcvnum segments
no ss7 session-session number m_rcvnum
Caution
Syntax Description
Defaults
32 segments
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The outstanding segments counter is the maximum number of segments that the Cisco IOS software end of the connection can send without getting an acknowledgment from the receiver. The receiver uses the counter for flow control.
Examples
The following example sets up two sessions and for each session sets a maximum of 36 segments for receipt before an acknowledgment:
ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7001ss7 session-0 m_rcvnum 36ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7000ss7 session-1 m_rcvnum 36Related Commands
ss7 session m_retrans
To set the maximum number of times that the Reliable User Datagram Protocol (RUDP) attempts to resend a segment before declaring the connection invalid in a specific SS7 signaling link session, use the ss7 session m_retrans command in global configuration mode. To reset to the default, use the no form of this command.
ss7 session-session number m_retrans number
no ss7 session-session number m_retrans
Caution
Syntax Description
Defaults
2 times
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The retransmission counter is the number of times a segment has been retransmitted. If this counter reaches the configured maximum, the transmitter resets the connection and informs the upper-layer protocol.
If you set this parameter to 0, the RUDP attempts to resend the segment continuously.
Examples
The following example sets up two sessions and for each session sets a maximum number of three times to resend before a session becomes invalid:
ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7001ss7 session-0 m_retrans 3ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7000ss7 session-1 m_retrans 3Related Commands
ss7 session retrans_t
To set the amount of time that the Reliable User Datagram Protocol (RUDP) waits to receive an acknowledgment for a segment in a specific SS7 signaling link session, use the ss7 session retrans_t command in global configuration mode. If the RUDP does not receive the acknowledgment in this time period, the RUDP retransmits the segment. To reset to the default, use the no form of this command.
ss7 session-session number retrans_t milliseconds
no ss7 session-session number retrans_t
Caution
Syntax Description
Defaults
600 ms
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
The retransmission timer is used to determine whether a packet must be retransmitted and is initialized each time a data, null, or reset segment is sent. If an acknowledgment for the segment is not received by the time the retransmission timer expires, all segments that have been transmitted—but not acknowledged—are retransmitted.
This value should be greater than the value configured for the cumulative acknowledgment timer by using the ss7 session cumack_t command.
Examples
The following example sets up two sessions and specifies 550 ms as the time to wait for an acknowledgment for each session:
ss7 session-0 address 255.255.255.251 7000 255.255.255.254 7001ss7 session-0 retrans_t 550ss7 session-1 address 255.255.255.253 7002 255.255.255.254 7000ss7 session-1 retrans_t 550Related Commands
ss7 set
Note
To independently select failover-timer values for each session set and to specify the amount of time that the SS7 Session Manager waits for the active session to recover or for the standby media gateway controller (MGC) to indicate that the Cisco Signaling Link Terminal (SLT) should switch traffic to the standby session, use the ss7 set command in global configuration mode. To restore the restore the failover timer to its default value of 5, use the no form of this command.
ss7 set [session-set session-id] failover-timer ft-value
no ss7 set [session-set session-id] failover-timer
Syntax Description
Defaults
The failover timer is not set.
Command Modes
Global configuration
Command History
12.2(15)T
This command was introduced. This command replaces the ss7 set failover-timer command.
Usage Guidelines
The failover-timer keyword and the ft-value argument specify the number of seconds that the Session Manager waits for the active session to recover or for the standby MGC to indicate that the SLT should switch traffic to the standby session and to make that session the active session. If the failover timer expires without recovery of the original session or if the system fails to get an active message from the standby MGC, the signaling links are taken out of service.
The no form of this command restores the failover timer to its default value of 5. Omitting the optional session-set keyword implicitly selects SS7 session set 0, which is the default.
Examples
The following example sets the failover timer to four seconds without using the session-set option:
ss7 set failover-timer 4The following example sets the failover timer to 10 seconds and sets the SS7 session set value to 5:
ss7 set session-set 5 failover-timer 10Related Commands
ss7 set failover-timer
To specify the amount of time that the SS7 Session Manager waits for the active session to recover or for the standby Media Gateway Controller to indicate that the SLT should switch traffic to the standby session, use the ss7 set failover-timer command in global configuration mode. To reset ti the default, use the no form of this command.
ss7 set failover-timer [seconds]
no ss7 set failover-timer
Syntax Description
seconds
Time, in seconds, that the session manager waits for a session to recover. Range is from 1 to 10. Default is 3.
Defaults
3 seconds
Command Modes
Global configuration
Command History
12.0(7)XR
This command was introduced.
12.1(1)T
This command was integrated into Cisco IOS Release 12.1(1)T.
Usage Guidelines
This command specifies the number of seconds that the session manager waits for the active session to recover or for the standby media gateway controller to indicate that the SLT should switch traffic to the standby session and to make that session the active session. If the timer expires without a recovery of the original session or an active message from the standby media gateway controller, the signaling links are taken out of service.
Examples
The following example sets the failover timer to 4 seconds:
ss7 set failover-timer 4Related Commands
show ss7 sm set
Displays the current failover timer setting.
ss7 session
Establishes a session.
station name
To specify the name that is to be sent as caller ID information and to enable caller ID, use the station name command in voice-port configuration mode at the sending Foreign Exchange Station (FXS) voice port or at a Foreign Exchange Office (FXO) port through which routed caller ID calls pass. To remove the name, use the no form of this command.
station name name
no station name name
Syntax Description
Defaults
The default is no station name.
Command Modes
Voice-port configuration
Command History
12.1(2)XH
This command was introduced on the Cisco 2600 series, Cisco 3600 series, and Cisco MC3810.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T.
Usage Guidelines
This optional command is configured on FXS voice ports that are used to originate on-net calls. The information entered is displayed by the telephone attached to the FXS port at the far end of the on-net call. It can also be configured on the FXO port of a router on which caller ID information is expected to be received from the Central Office (CO), to suit situations in which a call is placed from the CO, then goes through the FXO interface, and continues to a far-end FXS port through an on-net call. In this case, if no caller ID information is received from the CO telephone line, the far-end call recipient receives the information configured on the FXO port.
Note
Do not use this command when the caller ID standard is dual-tone multifrequency (DTMF). DTMF caller ID can carry only the calling number.
If the station name, station number, or a caller-id alerting command is configured on the voice port, caller ID is automatically enabled, and the caller-id enable command is not necessary.
Examples
The following example configures a voice port from which caller ID information is sent:
voice-port 1/0/1cptone USstation name A. Personstation number 4085551111Related Commands
station number
To specify the telephone or extension number that is to be sent as caller ID information and to enable caller ID, use the station number command in voice-port configuration mode at the sending Foreign Exchange Station (FXS) voice port or at a Foreign Exchange Office (FXO) port through which routed caller ID calls pass. To remove the number, use the no form of this command.
station number number
no station number number
Syntax Description
Defaults
The default is no station number.
Command Modes
Voice-port configuration
Command History
12.1(2)XH
This command was introduced on the Cisco 2600 series, Cisco 3600 series, and Cisco MC3810.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T.
Usage Guidelines
This optional command is configured on FXS voice ports that are used to originate on-net calls. The information entered is displayed by the telephone attached to the FXS port at the far end of the on-net call. It can also be configured on the FXO port of a router on which caller ID information is expected to be received from the Central Office (CO), to suit situations in which a call is placed from the CO, then goes through the FXO interface, and continues to a far-end FXS port through an on-net call. In this case, if no caller ID information is received from the CO telephone line, the far-end call recipient receives the information configured on the FXO port.
Within the network, if an originating station does not include configured number information, Cisco IOS software determines the number by using reverse dial-peer search.
Note
If the station name, station number, or a caller-id alerting command is configured on the voice port, caller ID is automatically enabled, and the caller-id enable command is not necessary.
Examples
The following example configures a voice port from which caller ID information is sent:
voice-port 1/0/1cptone USstation name A. Personstation number 4085551111Related Commands
stats
To enable statistics collection for voice applications, use the stats command in application configuration monitor mode. To reset to the default, use the no form of this command.
stats
no stats
Syntax Description
This command has no arguments or keywords.
Defaults
Statistics collection is disabled.
Command Modes
Application configuration monitor
Command History
12.3(14)T
This command was introduced to replace the call application stats command.
Usage Guidelines
To display the application statistics, use the show call application session-level, show call application app-level, or show call application gateway-level command. To reset the application counters in history to zero, use the clear call application stats command.
Examples
The following example enables statistics collection for voice applications:
applicationmonitorstatsRelated Commands
stcapp
To enable the SCCP Telephony Control Application (STCAPP), use the stcapp command in global configuration mode. To disable the STCAPP, use the no form of this command.
stcapp
no stcapp
Syntax Description
This command has no arguments or keywords.
Defaults
The Cisco CallManager does not control Cisco IOS gateway-connected analog and BRI endpoints.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the stcapp command to enable basic Skinny Client Call Control (SCCP) call control features for BRI and foreign exchange stations (FXS) analog ports within Cisco IOS voice gateways. The stcapp command enables the Cisco IOS gateway application to support the following features:
•
•
•
•
•
Examples
The following example shows that STCAPP is enabled:
Router(config)# stcappRelated Commands
stcapp ccm-group
To configure the Cisco CallManager group number for use by the SCCP Telephony Control Application (STCAPP), use the stcapp ccm-group command in global configuration mode. To disable STCAPP Cisco CallManager group number configuration, use the no form of this command.
stcapp ccm-group group-id
no stcapp ccm-group group-id
Syntax Description
Defaults
No Cisco CallManager group number is configured.
Command Modes
Global configuration.,
Command History
Usage Guidelines
The Cisco CallManager group identifier must have been configured for the service provider interface (SPI) using the sccp ccm-group group-id command.
Examples
The following example configures the STCAPP to use Cisco CallManager group 2:
Router(config)# stcapp ccm-group 2Related Commands
stcapp timer
To enable SCCP Telephony Control Application (STCAPP) timer configuration, use the stcapp timer command in global configuration mode. To disable STCAPP timer configuration, use the no form of this command.
stcapp timer roh seconds
no stcapp timer
Syntax Description
roh
Receiver off hook (ROH) tone timeout.
seconds
Duration, in seconds, that the receiver off-key tone is played. Range is 0 to 120 seconds.
Defaults
seconds: 45 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to configure the STCAPP ROH timer for the maximum time that ROH tone is played. ROH tone signals a subscriber that the phone remains off hook when there is no active call.
Examples
The following example configures the receiver off hook timer for 30 seconds:
Router(config)# stcapp timer roh 30Related Commands
show call application voice stcapp
Displays information about the STCAPP.
stcapp
Enables the STCAPP.
subaddress
To configure a subaddress for a POTS port, use the subaddress command in dial-peer voice configuration mode. To disable the subaddress, use the no form of this command.
subaddress number
no subaddress number
Syntax Description
Defaults
No subaddress is available for a POTS port.
Command Modes
Dial-peer voice configuration
Command History
12.2(8)T
This command was introduced on the Cisco 803, Cisco 804, and Cisco 813.
Usage Guidelines
You can use this command for any dial-peer voice POTS port. You can configure only one subaddress for each of the POTS ports. The latest entered subaddress on the dial-peer voice port is stored. To check the status of the subaddress configuration, use the show running-config command.
Examples
The following examples show that a subaddress of 20 has been set for POTS port 1 and that a subaddress of 10 has been set for POTS port 2:
dial-peer voice 1 potsdestination-pattern 5555555port 1no call-waitingring 0volume 4caller-number 1111111 ring 3caller-number 2222222 ring 1caller-number 3333333 ring 1subaddress 20dial-peer voice 2 potsdestination-pattern 4444444port 2no call-waitingring 0volume 2caller-number 6666666 ring 2caller-number 7777777 ring 3subaddress 10subcell-mux
To enable ATM adaption layer 2 (AAL2) common part sublayer (CPS) subcell multiplexing on a Cisco router, use the subcell-mux command in voice-service configuration mode. To reset to the default, use the no form of this command.
subcell-mux time
no subcell-mux time
Syntax Description
time
Timer value, in milliseconds. Range is from 5 to 1000 (1 second). Default is 10. The time argument is implemented for Cisco 3600 routers.
Defaults
10 ms
Subcell multiplexing is offCommand Modes
Voice-service configuration
Command History
Usage Guidelines
Use this command to enable ATM adaption layer 2 (AAL2) common part sublayer (CPS) subcell multiplexing when the Cisco router interoperates with other equipment that uses subcell multiplexing.
Examples
The following example sets AAL2 CPS subcell multiplexing to 15 ms:
Router(conf-voi-serv-sess)# subcell-mux 15Related Commands
voice-service
Specifies the voice encapsulation type and enters voice-service configuration mode.
subscription asnl session history
To specify how long to keep Application Subscribe/Notify Layer (ASNL) subscription history records and how many history records to keep in memory, use the subscription asnl session history command in global configuration mode. To reset to the default, use the no form of this command.
subscription asnl session history {count number | duration minutes}
no subscription asnl session history {count | duration}
Syntax Description
count number
Number of records to retain in a session history.
duration minutes
Duration, in minutes, for which to keep the record.
Defaults
Default duration is 10 minutes. Default number of records is 50.
Command Modes
Global configuration.
Command History
Usage Guidelines
The ASNL layer maintains subscription information. Active subscriptions are retained in the active subscription table in system memory. When subscriptions are terminated, they are moved to the subscription table in system memory.
This command controls the ASNL history table. Use this command to specify how many minutes the history record is retained after the subscription is removed, and to specify how many records are retained at any given time.
Examples
The following example specifies that a total of 100 records are to be kept in the RTSP client history:
subscription asnl session history count 100Related Commands
subscription maximum
To specify the maximum number of outstanding subscriptions to be accepted or originated by a gateway, use the subscription maximum command in voice service voip sip configuration mode. To remove the maximum number of subscriptions specified, use the no form of this command.
subscription maximum {accept | originate} number
no subscription maximum {accept | originate}
Syntax Description
accept
Subscriptions accepted by the gateway.
originate
Subscriptions originated by the gateway.
number
Maximum number of outstanding subscriptions to be accepted or originated by the gateway.
Defaults
The default number of subscriptions is equal to twice the number of dial-peers configured on the platform.
Command Modes
voice service voip sip configuration
Command History
Usage Guidelines
Use this command to configure the maximum number of concurrent SIP subscriptions, up to twice the number of dial-peers configured.
Examples
The following example configures subscription maximums:
Router(config)# voice service voipRouter(conf-voi-serv)# sipRouter(conf-serv-sip)# subscription maximum originate 10Related Commands
supervisory answer dualtone
To enable answer supervision on a Foreign Exchange Office (FXO) voice port, use the supervisory answer dualtone command in voice-port configuration mode. To disable answer supervision on a voice port, use the no form of this command.
supervisory answer dualtone [sensitivity {high | medium | low}]
no supervisory answer dualtone
Syntax Description
Defaults
Answer supervision is not enabled on voice ports.
Command Modes
Voice-port configuration
Command History
12.2(2)T
This command was introduced on the following platforms: Cisco 1750, Cisco 2600 series, Cisco 3600 series, and Cisco MC3810.
Usage Guidelines
This command configures the FXO voice port to detect voice, fax, and modem traffic when calls are answered. If answer supervision is enabled, calls are not recorded as connected until answer supervision is triggered.
This command enables a ring-no-answer timeout that drops calls after a specified period of ringback. The period of ringback can be configured using the timeouts ringing command.
This command automatically enables disconnect supervision in the preconnect mode on the voice port if disconnect supervision is not already enabled with the supervisory disconnect dualtone command.
This command is applicable to analog FXO voice ports with loop-start signaling.
If false answering is detected, decrease the sensitivity setting. If answering detection is failing, increase the sensitivity setting.
Examples
The following example enables answer supervision on voice port 0/1/1:
voice-port 0/1/1supervisory answer dualtoneRelated Commands
supervisory custom-cptone
To associate a class of custom call-progress tones with a voice port, use the supervisory custom-cptone command in voice-port configuration mode. To reset to the default, use the no form of this command.
supervisory custom-cptone cptone-name
no supervisory custom-cptone
Syntax Description
Defaults
U.S. standard call-progress tones are associated with a voice port.
Command Modes
Voice-port configuration
Command History
12.1(5)XM
This command was introduced on the Cisco 2600 series, Cisco 3600 series, and Cisco MC3810.
12.2(2)T
This command was implemented on the Cisco 1750.
Usage Guidelines
This command associates a class of custom call-progress tones, defined by the voice class custom-cptone command, with a voice port.
You can associate the same custom call-progress tones to multiple voice ports.
You can associate only one class of custom call-progress tones with a voice port. If you associate a second class of custom call-progress tones with a voice port, the second class of custom tones replaces the one previously assigned.
This command is applicable to analog Foreign Exchange Office (FXO) voice ports with loop-start signaling.
Examples
The following example associates the class of custom call-progress tones named country-x with voice ports 1/4 and 1/5:
voice-port 1/4supervisory custom-cptone country-xexitvoice-port 1/5supervisory custom-cptone country-xexitRelated Commands
supervisory disconnect
To enable a supervisory disconnect signal on Foreign Exchange Office (FXO) ports, use the supervisory disconnect command in voice-port configuration mode. To disable the signal, use the no form of this command.
supervisory disconnect
no supervisory disconnect
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Voice-port configuration
Command History
Usage Guidelines
This command indicates whether supervisory disconnect signaling is available on the FXO port. Supervisory disconnect signaling is a power denial from the switch lasting at least 350 ms. When this condition is detected, the system interprets this as a disconnect indication from the switch and clears the call.
You should configure no supervisory disconnect on the voice port if there is no supervisory disconnect available from the switch.
Note
Examples
The following example configures supervisory disconnect on a voice port:
voice-port 2/1/0supervisory disconnectsupervisory disconnect anytone
To configure a Foreign Exchange Office (FXO) voice port to go on-hook if the router detects any tone from a PBX or the PSTN before an outgoing call is answered, use the supervisory disconnect anytone command in voice-port configuration mode. To disable the supervisory disconnect function, use the no form of this command.
supervisory disconnect anytone
no supervisory disconnect anytone
Syntax Description
This command has no arguments or keywords.
Defaults
The supervisory disconnect function is not enabled on voice ports.
Command Modes
Voice-port configuration
Command History
Usage Guidelines
Use this command to provide disconnect if the PBX or PSTN does not provide a supervisory tone. Examples of tones that trigger a disconnect include busy tone, fast busy tone, and dial tone.
This command is enabled only during call setup (before the call is answered).
You must enable echo cancellation; otherwise, ringback tone from the router can trigger a disconnect.
This command replaces the no supervisory disconnect signal command. If you enter this command, the supervisory disconnect anytone feature is enabled, and the message
supervisory disconnect anytoneis displayed when show commands are entered.If you enter either the supervisory disconnect anytone command or the no supervisory disconnect signal command, answer supervision is automatically disabled.
Examples
The following example configures voice ports 1/4 and 1/5 to go on-hook if any tone from the PBX or PSTN is detected before the call is answered:
voice-port 1/4supervisory disconnect anytoneexitvoice-port 1/5supervisory disconnect anytoneexitThe following example disables the disconnect function on voice port 1/5:
voice-port 1/5no supervisory disconnect anytoneexitRelated Commands
supervisory disconnect dualtone
To enable disconnect supervision on a Foreign Exchange Office (FXO) voice port, use the supervisory disconnect dualtone command in voice-port configuration mode. To disable the supervisory disconnect function, use the no form of this command.
supervisory disconnect dualtone {mid-call | pre-connect}
no supervisory disconnect dualtone
Syntax Description
mid-call
Disconnect supervision operates throughout the duration of the call.
pre-connect
Disconnect supervision operates during call setup and stops when the called telephone goes off-hook.
Defaults
Disconnect supervision is not enabled on voice ports.
Command Modes
Voice-port configuration
Command History
12.1(5)XM
This command was introduced on the Cisco 2600 series, Cisco 3600 series, and Cisco MC3810.
12.2(2)T
This command was implemented on the Cisco 1750.
Usage Guidelines
This command configures an FXO voice port to disconnect calls when the router detects call-progress tones from a PBX or the PSTN. Disconnection occurs after the wait-release time specified on the voice port.
Disconnect supervision is automatically enabled in the preconnect mode on the voice port if the supervisory answer dualtone command is entered.
This feature is applicable to analog FXO voice ports with loop-start signaling.
Examples
The following example specifies tone detection during the entire call duration:
voice-port 1/5supervisory disconnect dualtone mid-callexitThe following example specifies tone detection only during call setup:
voice-port 0/1/1supervisory disconnect dualtone pre-connectexitRelated Commands
supervisory disconnect dualtone voice-class
To assign a previously configured voice class for Foreign Exchange Office (FXO) supervisory disconnect tone to a voice port, use the supervisory disconnect dualtone voice-class command in voice port configuration mode. To remove a voice class from a voice-port, use the no form of this command.
supervisory disconnect dualtone {mid-call | pre-connect} voice-class tag
no supervisory disconnect dualtone voice-class tag
Syntax Description
Defaults
No voice class is assigned to a voice port.
Command Modes
Voice-port configuration
Command History
12.1(3)T
This command was introduced on the Cisco 2600 series, Cisco 3600 series, and Cisco MC3810.
Usage Guidelines
You can apply an FXO supervisory disconnect tone voice class to multiple voice ports. You can assign only one FXO supervisory disconnect tone voice class to a voice port. If a second voice class is assigned to a voice port, the second voice class replaces the one previously assigned. You cannot assign separate FXO supervisory disconnect tone commands directly to the voice port.
This feature is applicable to analog FXO voice ports with loop-start signaling.
Examples
The following example assigns voice class 70 to FXO voice port 0/1/1 and specifies tone detection during the entire call duration:
voice-port 0/1/1no echo-cancel enablesupervisory disconnect dualtone mid-call voice-class 70The following example assigns voice class 80 to FXO voice port 0/1/1 and specifies tone detection only during call setup:
voice-port 0/1/1no echo-cancel enablesupervisory disconnect dualtone pre-connect voice-class 80Related Commands
supervisory dualtone-detect-params
To associate a class of modified tone-detection tolerance limits with a voice port, use the supervisory dualtone-detect-params command in voice-port configuration mode. To reset to the default, use the no form of this command.
supervisory dualtone-detect-params tag
no supervisory dualtone-detect-params
Syntax Description
Defaults
The default tone-detection tolerance limits are associated with voice ports.
Command Modes
Voice-port configuration
Command History
12.1(5)XM
This command was introduced on the Cisco 2600 series, Cisco 3600 series, and Cisco MC3810.
12.2(2)T
This command was implemented on the Cisco 1750.
Usage Guidelines
This command associates a specific set of modified tone-detection tolerance limits, defined by the voice class dualtone-detect-params command, with a voice port.
You can associate the same class of modified tone-detection tolerance limits to multiple voice ports.
You can associate only one class of modified tone-detection tolerance limits to a voice port. If you associate a second class of modified tone-detection tolerance limits with a voice port, the second class replaces the one previously assigned.
This command is applicable to analog Foreign Exchange Office (FXO) voice ports with loop-start signaling.
Examples
The following example associates the class of modified tone-detection tolerance limits that has tag 70 with voice ports 1/5 and 1/6.
voice-port 1/5supervisory dualtone-detect-params 70exitvoice-port 1/6supervisory dualtone-detect-params 70exitThe following example restores the default tone-detection parameters to voice port 1/5.
voice-port 1/5no supervisory dualtone-detect-paramsexitRelated Commands
supplementary-service h225-notify cid-update (dial-peer)
To enable individual dial peers to send H.225 messages with caller-ID updates, use the supplementary-service h225-notify cid-update command in dial-peer configuration mode. To disable the sending of H.225 messages with caller-ID updates, use the no form of this command.
supplementary-service h225-notify cid-update
no supplementary-service h225-notify cid-update
Syntax Description
This command has no arguments or keywords.
Defaults
H.225 messages with caller-ID updates are enabled.
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
This command specifies that an individual dial peer should provide caller ID updates through H.225 notify messages when a call is transferred or forwarded between Cisco CallManager Express and Cisco CallManager systems. The default is that this behavior is enabled. The no form of the command disables caller-ID updates, which is not recommended. Use the supplementary-service h225-notify cid-update command in voice-service configuration mode to specify this capability globally.
If this command is enabled globally and enabled on a dial peer, the functionality is enabled for that dial peer. This is the default.
If this command is enabled globally and disabled on a dial peer, the functionality is disabled for that dial peer.
If this command is disabled globally and either enabled or disabled on a dial peer, the functionality is disabled for that dial peer.
Examples
The following example globally enables the sending of H.225 messages to transmit caller-ID updates and then disables that capability on dial peer 24.
Router(config)# voice service voipRouter(config-voi-serv)# supplementary-service h225-notify cid-updateRouter(config-voi-serv)# exitRouter(config)# dial-peer voice 24 voipRouter(config-dial-peer)# no supplementary-service h225-notify cid-updateRouter(config-dial-peer)# exitRelated Commands
supplementary-service h225-notify cid-update (voice-service)
To globally enable the sending of H.225 messages with caller-ID updates, use the supplementary-service h225-notify cid-update command in voice-service configuration mode. To disable the sending of H.225 messages with caller-ID updates, use the no form of this command.
supplementary-service h225-notify cid-update
no supplementary-service h225-notify cid-update
Syntax Description
This command has no arguments or keywords.
Defaults
H.225 messages with caller-ID updates are enabled.
Command Modes
Voice-service configuration
Command History
Usage Guidelines
This command globally provides caller ID updates through H.225 notify messages when a call is transferred or forwarded between Cisco CallManager Express and Cisco CallManager systems. The default is that this behavior is enabled. The no form of the command disables caller-ID updates, which is not recommended. Use the supplementary-service h225-notify cid-update command in dial-peer configuration mode to specify this capability for individual dial peers.
If this command is enabled globally and enabled on a dial peer, the functionality is enabled for that dial peer. This is the default.
If this command is enabled globally and disabled on a dial peer, the functionality is disabled for that dial peer.
If this command is disabled globally and either enabled or disabled on a dial peer, the functionality is disabled for that dial peer.
Examples
The following example globally enables the sending of H.225 messages to transmit caller-ID updates and then disables that capability on dial peer 24.
Router(config)# voice service voipRouter(config-voi-serv)# supplementary-service h225-notify cid-updateRouter(config-voi-serv)# exitRouter(config)# dial-peer voice 24 voipRouter(config-dial-peer)# no supplementary-service h225-notify cid-updateRouter(config-dial-peer)# exitRelated Commands
supplementary-service h450.12 (dial-peer)
To enable H.450.12 supplementary services capabilities exchange for call transfers across a VoIP network for an individual dial peer, use the supplementary-service h450.12 command in dial-peer configuration mode. To disable H.450.12 capabilities for an individual dial peer, use the no form of this command.
supplementary-service h450.12
no supplementary-service h450.12
Syntax Description
This command has no arguments or keywords.
Defaults
H.450.12 supplementary services capabilities exchange is disabled.
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
This command specifies use of the H.450.12 standard protocol for call transfers across a VoIP network for calls handled by an individual dial peer. Use the supplementary-service h450.12 command in voice-service configuration mode to specify H.450.12 capabilities at a global level.
If this command is enabled globally and enabled on a dial peer, the functionality is enabled for the dial peer.
If this command is enabled globally and disabled on a dial peer, the functionality is enabled for the dial peer.
If this command is disabled globally and enabled on a dial peer, the functionality is enabled for the dial peer.
If this command is disabled globally and disabled on a dial peer, the functionality is disabled for the dial peer. This is the default.
Examples
The following example enables H.450.12 capabilities on dial peer 37.
Router(config)# dial-peer voice 37 voipRouter(config-dial-peer)# destination-pattern 555....Router(config-dial-peer)# session target ipv4:10.5.6.7Router(config-dial-peer)# supplementary-service h450.12Router(config-dial-peer)# exitRelated Commands
dial-peer voice
Enters dial-peer configuration mode.
supplementary-service h450.12 (voice-service)
Globally enables H.450.12 capabilities.
supplementary-service h450.12 (voice-service)
To globally enable H.450.12 supplementary services capabilities exchange for call transfers across a VoIP network, use the supplementary-service h450.12 command in voice-service configuration mode. To disable H.450.12 capabilities globally, use the no form of this command.
supplementary-service h450.12 [advertise-only]
no supplementary-service h450.12 [advertise-only]
Syntax Description
advertise-only
(Optional) Advertises H.450 capabilities to the remote end but does not require H.450.12 responses.
Defaults
H.450.12 supplementary services capabilities exchange is disabled.
Command Modes
Voice-service configuration
Command History
Usage Guidelines
The H.450.12 standard provides a means to advertise and discover H.450.2 call transfer and H.450.3 call forwarding capabilities in voice gateway endpoints on a call-by-call basis. When H.450.12 is enabled, use of H.450.2 and H.450.3 standards is disabled for call transfers and call forwards unless a positive H.450.12 indication is received from all the other VoIP endpoints involved in the call. If positive H.450.12 indications are received, the router uses the H.450.2 standard for call transfers and the H.450.3 standard for call forwarding. If a positive H.450.12 indication is not received, the router uses the alternative method that you have configured for call transfers and forwards, which, for Cisco CallManager Express (Cisco CME) 3.1 systems, may be either hairpin call routing or an H.450 tandem gateway. This command is useful when you have a mixed network with some endpoints that support H.450.2 and H.450.3 standards and other endpoints that do not support those standards.
This command specifies the global use of the H.450.12 standard protocol for all calls across a VoIP network. Use the supplementary-service h450.12 command in dial-peer configuration mode to specify H.450.12 capabilities for individual dial peers.
If this command is enabled globally and enabled on a dial peer, the functionality is enabled for the dial peer.
If this command is enabled globally and disabled on a dial peer, the functionality is enabled for the dial peer.
If this command is disabled globally and enabled on a dial peer, the functionality is enabled for the dial peer.
If this command is disabled globally and disabled on a dial peer, the functionality is disabled for the dial peer. This is the default.
Use the advertise-only keyword on a Cisco CME 3.1 system when you have only Cisco CME 3.0 systems in your network in addition to Cisco CME 3.1 systems. Cisco CME 3.0 systems can use H.450.2 and H.450.3 standards, but are unable to respond to H.450.12 queries. The advertise-only keyword enables a Cisco CME 3.1 system to bypass the requirement that a system respond to an H.450.12 query in order to use H.450.2 and H.450.3 standards for transferring and forwarding calls.
Examples
The following example enables H.450.12 capabilities at a global level.
Router(config)# voice service voipRouter(config-voi-serv)# supplementary-service h450.12Router(config-voi-serv)# exitThe following example enables H.450.12 capabilities at a global level in advertise-only mode on a Cisco CME 3.1 system to enable call transfers using the H.450.2 standard and call forwards using the H.450.3 standard with Cisco CME 3.0 systems in the network.
Router(config)# voice service voipRouter(config-voi-serv)# supplementary-service h450.12 advertise-onlyRouter(config-voi-serv)# exitRelated Commands
supplementary-service h450.12 (dial-peer)
Enables H.450.12 capabilities for an individual dial peer.
voice-service voip
Enters voice-service configuration mode.
supplementary-service h450.2 (dial-peer)
To enable H.450.2 supplementary services capabilities exchange for call transfers across a VoIP network for an individual dial peer, use the supplementary-service h450.2 command in dial-peer configuration mode. To disable H.450.2 capabilities for an individual dial peer, use the no form of this command.
supplementary-service h450.2
no supplementary-service h450.2
Syntax Description
This command has no arguments or keywords.
Defaults
H.450.2 supplementary services capabilities exchange is enabled.
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
This command specifies the use of the H.450.2 standard protocol for call transfers across a VoIP network for the calls handled by an individual dial peer. Use the supplementary-service h450.2 command in voice-service configuration mode to specify H.450.2 capabilities at a global level.
If this command is enabled globally and enabled on a dial peer, the functionality is enabled for the dial peer. This is the default.
If this command is enabled globally and disabled on a dial peer, the functionality is disabled for the dial peer.
If this command is disabled globally and either enabled or disabled on a dial peer, the functionality is disabled for the dial peer.
Examples
The following example disables H.450.2 services for dial peer 37.
Router(config)# dial-peer voice 37 voipRouter(config-dial-peer)# destination-pattern 555....Router(config-dial-peer)# session target ipv4:10.5.6.7Router(config-dial-peer)# no supplementary-service h450.2Router(config-dial-peer)# exitRelated Commands
dial-peer voice
Enters dial-peer configuration mode.
supplementary-service h450.2 (voice-service)
Globally enables H.450.2 capabilities for call transfers.
supplementary-service h450.2 (voice-service)
To globally enable H.450.2 supplementary services capabilities exchange for call transfers across a VoIP network, use the supplementary-service h450.2 command in voice-service configuration mode. To disable H.450.2 capabilities globally, use the no form of this command.
supplementary-service h450.2
no supplementary-service h450.2
Syntax Description
This command has no arguments or keywords.
Defaults
H.450.2 supplementary services capabilities exchange is enabled.
Command Modes
Voice-service configuration
Command History
Usage Guidelines
This command specifies global use of the H.450.2 standard protocol for call transfers for all calls across a VoIP network. Use the no supplementary-service h450.2 command in dial-peer configuration mode to disable H.450.2 capabilities for individual dial peers.
If this command is enabled globally and enabled on a dial peer, the functionality is enabled for the dial peer. This is the default.
If this command is enabled globally and disabled on a dial peer, the functionality is disabled for the dial peer.
If this command is disabled globally and either enabled or disabled on a dial peer, the functionality is disabled for the dial peer.
Examples
The following example globally disables H.450.2 capabilities.
Router(config)# voice service voipRouter(config-voi-serv)# no supplementary-service h450.2Router(config-voi-serv)# exitRelated Commands
supplementary-service h450.2 (dial-peer)
Enables H.450.2 call transfer capabilities for an individual dial peer.
voice-service voip
Enters voice-service configuration mode.
supplementary-service h450.3 (dial-peer)
To enable H.450.3 supplementary services capabilities exchange for call forwarding across a VoIP network for an individual dial peer, use the supplementary-service h450.3 command in dial-peer configuration mode. To disable H.450.3 capabilities for an individual dial peer, use the no form of this command.
supplementary-service h450.3
no supplementary-service h450.3
Syntax Description
This command has no arguments or keywords.
Defaults
H.450.3 supplementary services capabilities exchange is enabled.
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
This command specifies use of the H.450.3 standard protocol for call forwarding for calls handled by an individual dial peer. Use the supplementary-service h450.3 command in voice-service configuration mode to specify H.450.3 capabilities at a global level.
If this command is enabled globally and enabled on a dial peer, the functionality is enabled for the dial peer. This is the default.
If this command is enabled globally and disabled on a dial peer, the functionality is disabled for the dial peer.
If this command is disabled globally and either enabled or disabled on a dial peer, the functionality is disabled for the dial peer.
Examples
The following example disables H.450.3 capabilities for dial peer 37.
Router(config)# dial-peer voice 37 voipRouter(config-dial-peer)# destination-pattern 555....Router(config-dial-peer)# session target ipv4:10.5.6.7Router(config-dial-peer)# no supplementary-service h450.3Router(config-dial-peer)# exitRelated Commands
dial-peer voice
Enters dial-peer configuration mode.
supplementary-service h450.3 (voice-service)
Globally enables H.450.3 capabilities for call forwarding.
supplementary-service h450.3 (voice-service)
To globally enable H.450.3 supplementary services capabilities exchange for call forwarding across a VoIP network, use the supplementary-service h450.3 command in voice-service configuration mode. To disable H.450.3 capabilities globally, use the no form of this command.
supplementary-service h450.3
no supplementary-service h450.3
Syntax Description
This command has no arguments or keywords.
Defaults
H.450.3 supplementary services capabilities exchange is enabled.
Command Modes
Voice-service configuration
Command History
Usage Guidelines
This command specifies global use of the H.450.3 standard protocol for call forwarding across a VoIP network. Use the no supplementary-service h450.3 command in dial-peer configuration mode to disable H.450.3 capabilities for individual dial peers.
If this command is enabled globally and enabled on a dial peer, the functionality is enabled for the dial peer. This is the default.
If this command is enabled globally and disabled on a dial peer, the functionality is disabled for the dial peer.
If this command is disabled globally and either enabled or disabled on a dial peer, the functionality is disabled for the dial peer.
Examples
The following example globally disables H.450.3 capabilities.
Router(config)# voice service voipRouter(config-voi-serv)# no supplementary-service h450.3Router(config-voi-serv)# exitRelated Commands
supplementary-service h450.3 (dial-peer)
Enables H.450.3 call forwarding capabilities for an individual dial peer.
voice-service voip
Enters voice-service configuration mode.
supported language
To configure Session Initiation Protocol (SIP) Accept-Language header support, use the supported-language command in voice service or dial-peer voice configuration mode. To disable Accept-Language header support, use the no form of this command.
supported-language language-code language-param qvalue
no supported-language language-code
Syntax Description
Defaults
qvalue: 1
Command Modes
Voice service or Dial-peer voice configuration mode
Command History
Usage Guidelines
To include the Accept-Language header in outgoing SIP INVITE messages, and enable Accept-Language header support on specific trunk groups with different language requirements, use dial-peer voice configuration mode, which is enabled by the dial-peer voice command . To enable Accept-Language headers to be included in both SIP INVITE messages and OPTIONS responses, use voice service configuration mode, enabled by the voice service pots command. If both voice service and dial-peer voice mode accept-language support are configured, and there are no dial-peer matches, the outgoing INVITE message contains the voice service specified languages. Otherwise, the INVITE contains the dial-peer configured languages.
The SIP Accept-Language Header Support feature supports 139 languages which are designated by a two-letter ISO-639 country code. The following is a partial list of supported language codes and languages. To display a complete listing use the help command supported-language ?.
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
Examples
The following example configures Italian to be the preferred language, followed by Greek:
supported-language IT language-param .9supported-language EL language-param .8Related Commands
show dial-peer voice
Displays the configuration for all VoIP and POTS dial peers.
suppress
To suppress accounting for a specific call leg, use the suppress command in gateway accounting AAA configuration mode. To reenable accounting for that leg, use the no form of this command.
suppress [pots | rotary | voip]
no suppress [pots | rotary | voip]
Syntax Description
Defaults
Accounting is enabled.
Command Modes
Gateway accounting AAA configuration
Command History
Usage Guidelines
Use this command to turn off accounting for a specific call leg.
If both incoming and outgoing call legs are of the same type, no accounting packets are generated.
Use the rotary keyword to suppress excess start and stop accounting records. This causes only one pair of records to be generated for every connection attempt through a dial peer.
Examples
The following example suppresses accounting for the POTS call leg.
suppress potsRelated Commands
debug suppress rotary
Displays connection attempt statistics.
gw-accounting aaa
Enables VoIP gateway accounting.
suspend-resume (SIP)
To enable SIP Suspend and Resume functionality, use the suspend-resume command in SIP user agent configuration mode. To disable SIP Suspend and Resume functionality, use the no form of this command.
suspend-resume
no suspend-resume
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
SIP user agent configuration
Command History
Usage Guidelines
Session Initiation Protocol (SIP) gateways are now enabled to use Suspend and Resume. Suspend and Resume are basic functions of ISDN and ISDN User Part (ISUP) signaling procedures. A Suspend message temporarily halts communication (call hold), and a Resume message is received after a Suspend message and continues the communication.
Examples
The following example disables Suspend and Resume functionality:
Router(config)# sip-uaRouter(config-sip-ua)# no suspend-resumeRelated Commands
show sip-ua status
Displays SIP UA status.
sip-ua
Enables the SIP user-agent configuration commands.
switchback interval
To set the amount of time that the digital signal processor (DSP) farm waits before polling the primary Cisco CallManager when the current Cisco CallManager switchback connection fails, use the switchback interval command in SCCP Cisco CallManager configuration mode. To reset the amount of time to the default value, use the no form of this command.
switchback interval seconds
no switchback interval
Syntax Description
Defaults
60 seconds
Command Modes
SCCP Cisco CallManager configuration
Command History
Usage Guidelines
The optimum setting for this command depends on the platform and your individual network characteristics. Adjust the switchback interval value to meet your needs.
Examples
The following example sets the length of time the DSP farm waits to before polling the primary Cisco CallManager to 120 seconds (2 minutes):
Router(conf-sccp-ccm)# switchback interval 120Related Commands
switchback method
To set the Cisco CallManager switchback method, use the switchback method command in Skinny SCCP Cisco CallManager configuration mode. To reset to the default value, use the no form of this command.
switchback method {graceful | guard [timeout-guard-value] | immediate | uptime uptime-timeout-value}
no switchback method
Syntax Description
Defaults
Guard is the default switchback method, with a timeout value of 7200 seconds.
Command Modes
SCCP Cisco CallManager configuration
Command History
Usage Guidelines
Use this command to set the Cisco CallManager switchback method. When a switch-over happens with the secondary Cisco CallManager initiates the switchback process with that higher-order Cisco CallManager. The available switchback methods follow:
•
•
•
•
Note
Examples
The following example sets the Cisco CallManager switchback method to happen only after all the active sessions are terminated gracefully.
Router(config-sccp-ccm)# switchback method gracefulRelated Commands
switchover method
To set the switchover method that the Skinny Client Control Protocol (SCCP) client uses when the communication link between the active Cisco CallManager and the SCCP client goes down, use the switchover method command in SCCP Cisco CallManager configuration mode. To reset the switchover method to the default, use the no form of this command.
switchover method {graceful | immediate}
no switchover method
Syntax Description
graceful
Switchover happens only after all the active sessions are terminated gracefully.
immediate
Switches over to any one of the secondary Cisco CallManager immediately.
Defaults
Graceful
Command Modes
SCCP Cisco CallManager configuration
Command History
Usage Guidelines
When the communication link between the active Cisco CallManager and the SCCP client goes down the SCCP client tries to connect to one of the secondary Cisco CallManagers using one of the following switchover methods:
•
•
Note
Examples
The following example sets the switchover method that the SCCP client uses to connect to a secondary Cisco CallManager to happen only after all the active sessions are terminated gracefully:
Router (config-sccp-ccm)# switchover method graceful
Related Commands
Posted: Thu Apr 7 11:24:34 PDT 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
