Related Commands

Displays the configuration for all VoIP and POTS dial peers configured on the router.

show voice dsp

Shows the current status of all DSP voice channels.

show voice port

Displays configuration information about a specific voice port.

show voice trunk-conditioning supervisory

Displays the status of trunk supervision and configuration parameters for voice ports.

show voice trunk-conditioning supervisory

To display the status of trunk supervision and configuration parameters for a voice port, use the show voice trunk-conditioning supervisory command in user EXEC or privileged EXEC mode.

show voice trunk-conditioning supervisory [summary| voice-port]

Syntax Description

summary

(Optional) Displays a summary of the status for all voice ports on the router or concentrator.

voice-port

(Optional) Detailed report for a specified voice port.

Command Modes

User EXECPrivileged EXEC

Command History

Release

Modification

12.0(7)XK

This command was introduced on the Cisco 2600 series, Cisco 3600 series, and Cisco MC3810 platforms.

12.1(2)T

This command was integrated into Cisco IOS Release 12.1(2)T.

12.1(3)T

This command was implemented on the Cisco 2600 series and Cisco 3600 series.

12.4(15)T10

The output of thiscommand was modified to report values configured by the signal timing idle suppress-voice command. The values for the suppress-voice and resume-voice keywords are shown as the "idle = seconds" and "idle_off = milliseconds" fields, respectively.

Usage Guidelines

This command displays the trunk supervision and configuration status for analog and digital voice ports.

Examples

The following is sample output from the show voice trunk-conditioning supervisory summary command for all voice ports:

Router# show voice trunk-conditioning supervisory summary

2/0/0 is shutdown

2/0/1 is shutdown

3/0:0 8 is shutdown

3/0:1 1 is shutdown

3/0:2 2 is shutdown

3/0:3 3 is shutdown

3/0:5 5 is shutdown

3/0:6(6) : state : TRUNK_SC_CONNECT, voice : on , signal : on ,master

3/0:7(7) : state : TRUNK_SC_CONNECT, voice : on , signal : on ,master

3/1:0(8) : state : TRUNK_SC_CONNECT, voice : on , signal : on ,master

3/1:1(1) : state : TRUNK_SC_CONNECT, voice : on , signal : on ,master

3/1:3(3) : state : TRUNK_SC_CONNECT, voice : on , signal : on ,master

3/1:5(5) is shutdown

3/1:7(7) is shutdown

The following is sample output from the show voice trunk-conditioning supervisory command for voice port 3/0:6:

Router# show voice trunk-conditioning supervisory 3/0:6

3/0:6(6) : state : TRUNK_SC_CONNECT, voice : on, signal : on, master

status: trunk connected

sequence oos : idle and oos

pattern :rx_idle = 0x0 rx_oos = 0xF

timing : idle = 0, restart = 0, standby = 0, timeout = 40

supp_all = 0, supp_voice = 0, keep_alive = 5

timer: oos_ais_timer = 0, timer = 0

The following shows a sample trunk conditioning setting for the voice class permanent command and sample output from the show voice trunk-conditioning supervisory command that shows the values for the timeout timing field:

Related Commands

show voip htsp

To display the voip and hybrid transport switching protocol(HTSP) connections active in the router, use the show voip htsp command in privileged EXEC mode.

show voip htsp info [controller[T1slot-number]]

Syntax Description

info

Displays htsp related information.

controller

(Optional) Displays information about controllers such as DS3,T1,and E1.

T1

(Optional) Displays information about T1 controller.

slot-number

(Optional) controller slot number.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

15.0(1)M

This command was introduced in a release earlier than Cisco IOS Release 15.0(1)M.

Usage Guidelines

Use theshow voip htsp command to display the voip and hybrid transport switching protocol(HTSP) connections active in the router.

Examples

The following is sample output from the show voip htsp command:

Router# show voip htsp

NOTE: '-' means Not Applicable for that signalling type

SLOT/ TSP TDM TDM

PORT/ TSP BEAR CONNECT CROSS

CHANNEL HTSPINFO VTSP_CDB CDB CHAN_T DONE CONNECT

========= ========== ========== ========== ========== ======= =======

02/00/01 0x677371E8 0x68905A48 0x67757AA4 0x677371E8 y y

02/00/02 0x67737780 0x00000000 0x00000000 0x00000000 n n

02/00/03 0x67737D18 0x68906548 0x67757584 0x67737D18 y y

02/00/04 0x677382B0 0x68904C88 0x677572F4 0x677382B0 y y

02/00/05 0x67738848 0x00000000 0x00000000 0x00000000 n n

02/00/06 0x67738DE0 0x00000000 0x00000000 0x00000000 n n

02/00/07 0x67739378 0x689054C8 0x67756B44 0x67739378 y y

02/00/08 0x67739910 0x68907888 0x677568B4 0x67739910 y y

02/00/09 0x67739EA8 0x00000000 0x00000000 0x00000000 n n

02/00/10 0x6773A440 0x00000000 0x00000000 0x00000000 n n

02/00/11 0x6773A9D8 0x68906D88 0x67756104 0x6773A9D8 y y

02/00/12 0x6773AF70 0x68908388 0x67755E74 0x6773AF70 y y

02/00/13 0x6773B508 0x00000000 0x00000000 0x00000000 n n

02/00/14 0x6773BAA0 0x00000000 0x00000000 0x00000000 n n

02/00/15 0x6773C038 0x689096C8 0x677556C4 0x6773C038 y y

02/00/17 0x6773C5D0 0x68909148 0x67755434 0x6773C5D0 y y

02/00/18 0x6773CB68 0x00000000 0x00000000 0x00000000 n n

02/00/19 0x6773D100 0x00000000 0x00000000 0x00000000 n n

02/00/20 0x6773D698 0x68905788 0x67754C84 0x6773D698 y y

02/00/21 0x6773DC30 0x68905D08 0x677549F4 0x6773DC30 y y

02/00/22 0x6773E1C8 0x00000000 0x00000000 0x00000000 n n

02/00/23 0x6773E760 0x00000000 0x00000000 0x00000000 n n

02/00/24 0x6773ECF8 0x68906AC8 0x67754244 0x6773ECF8 y y

02/00/25 0x6773F290 0x68907308 0x67753FB4 0x6773F290 y y

02/00/26 0x6773F828 0x00000000 0x00000000 0x00000000 n n

02/00/27 0x6773FDC0 0x00000000 0x00000000 0x00000000 n n

02/00/28 0x67740358 0x689080C8 0x67753804 0x67740358 y y

02/00/29 0x677408F0 0x68908908 0x67753574 0x677408F0 y y

02/00/30 0x67740E88 0x00000000 0x00000000 0x00000000 n n

02/00/31 0x67741420 0x68909408 0x67753054 0x67741420 y y

02/02/01 0x67B88824 0x00000000 0x00000000 - - n

02/02/02 0x67B88DBC 0x00000000 0x00000000 - - n

02/02/03 0x67B89354 0x00000000 0x00000000 - - n

02/02/04 0x67B898EC 0x00000000 0x00000000 - - n

02/02/05 0x67B89E84 0x00000000 0x00000000 - - n

02/02/06 0x67B8A41C 0x00000000 0x00000000 - - n

02/02/07 0x67B8A9B4 0x00000000 0x00000000 - - n

02/02/08 0x67B8AF4C 0x00000000 0x00000000 - - n

02/02/09 0x67B8B4E4 0x00000000 0x00000000 - - n

Related Commands

Command

Description

debug voip vtsp

Displays information about the voice telephony service provider (VTSP).

show voip rtp connections

To display Real-Time Transport Protocol (RTP) named event packets, use the show voip rtp connections command in privileged EXEC mode.

show voip rtp connections [detail]

Syntax Description

detail

(Optional) Displays the called-party and calling-party numbers associated with a call.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0

This command was introduced.

12.3(7)T

The detail keyword was added.

12.3(14)T

This command was implemented on the Cisco 2800 series and Cisco 3800 series.

12.4(2)T

This command was integrated into Cisco IOS Release 12.4(2)T.

12.4(22)T

Command output was updated to show IPv6 information.

Usage Guidelines

This command displays information about RTP named event packets, such as caller ID number, IP address, and port for both the local and remote endpoints. The output from this command provides an overview of all the connections in the system, and this information can be used to narrow the criteria for debugging. The debug voip rtp command floods the console with voice packet information. You can use the show voip rtp connections command to get caller ID, remote IP address, or remote port identifiers that you can use to limit the output from the debug voip rtp command.

The detail keyword allows you to identify the phone or phones that have connected two RTP call legs to create VoIP-to-VoIP or VoIP-to-POTS hairpins. If the detail keyword is omitted, the output does not display calls that are connected by hairpin call routing.

Examples

Table 222 describes the significant fields shown in the examples. Each line of output under "VoIP RTP active connections" shows information for one call leg. A phone call normally consists of two call legs, one connected to the calling party and one connected to the called party. The router joins (or bridges) the two call legs to make a call. The show voip rtp connections command shows the RTP information for H.323 and Session Initiation Protocol (SIP) calls only; it does not directly show the POTS call legs. The information for the IP phone can be seen using the show ephone offhook command.

The following sample output shows an incoming H.323 call that is being directed to an IP phone attached to a Cisco CallManager Express (CME) system.

Router# show voip rtp connections

VoIP RTP active connections :

No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP

1 21 22 16996 18174 10.4.204.37 10.4.204.24

Found 1 active RTP connections

The following sample output shows the same call as in the previous example, but using the detail keyword with the command. The sample output shows the called number (1509) and calling number (8108) on both call legs (21 and 22); the called and calling numbers are the same on both legs for a simple A-to-B call. Leg 21 is the H.323 segment of the and leg 22 is the POTS segment that goes to the IP phone.

Router#show voip rtp connections detail

VoIP RTP active connections :

No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP

1 21 22 16996 18174 10.4.204.37 10.4.204.24

callId 21 (dir=1):called=1509 calling=8108 redirect=

dest callId 22:called=1509 calling=8108 redirect=

1 context 64FB3358 xmitFunc 6032E8B4

Found 1 active RTP connections

The following example shows the call from the previous example being transferred by extension 1509 to extension 1514. Notice that the dstCallId changed from 22 to 24, but the original call leg (21) for the transferred party is still present. This implies that H.450.2 capability was disabled for this particular call, because if H.450.2 was being used for the transfer, the transfer would have caused the incoming H.323 call leg to be replaced with a new call.

Router# show voip rtp connections

VoIP RTP active connections :

No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP

1 21 24 16996 18174 10.4.204.37 10.4.204.24

Found 1 active RTP connections

The following example shows the detailed output for the same transfer as shown in the previous example. The original incoming call leg is still present (21) and still has the original called and calling numbers. The transferred call leg (24) shows 1509 (the transferring party) as the calling party and 1514 (the transfer destination) as the called party.

Router# show voip rtp connections detail

VoIP RTP active connections :

No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP

1 21 24 16996 18174 10.4.204.37 10.4.204.24

callId 21 (dir=1):called=1509 calling=8108 redirect=

dest callId 24:called=1514 calling=1509 redirect=

1 context 6466E810 xmitFunc 6032E8B4

Found 1 active RTP connections

The following sample output shows a cross-linked call with two H.323 call legs. The first line of output shows that the CallID for the first call leg is 7 and that this call leg is associated with another call leg that has a destination CallId of 8. The next line shows that the CallID for the leg is 8 and that it is associated with another call leg that has a destination CallId of 7. This cross-linkage between CallIds 7 and 8 shows that the first call leg is related to the second call leg (and vice versa). From this you can infer that the two call legs are actually part of the same phone call.

In an active system you can expect many lines of output that you would have to sort through to see which ones have this cross-linkage relationship. The lines showing two related call legs are not necessarily listed in adjacent order.

Router# show voip rtp connections

VoIP RTP active connections :

No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP

1 7 8 16586 22346 172.27.82.2 172.29.82.2

2 8 7 17010 16590 172.27.82.2 192.168.1.29

Found 2 active RTP connections

The following example shows RTP information with IPv6 local and remote addresses:

Internal memory address for the control block associated with the call.

xmitFunc

Internal memory address for the transmit function to which incoming RTP packets (on the H.323 and SIP side) are sent; the address for the function that delivers the packets to the ephone.

Related Commands

Command

Description

debug voip rtp

Enables debugging for RTP named event packets.

show ephone offhook

Displays information and packet counts for phones that are currently off hook.

show voip rtp forking

To display the Real-Time Transport Protocol (RTP) media-forking connections, use the show voip rtp forking command in privileged EXEC mode.

show voip rtp forking

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC (#)

Command History

Release

Modification

12.4(24)T

This command was introduced in a release earlier than Cisco IOS Release 12.4(24)T.

Usage Guidelines

The show voip rtp forking command displays information about RTP named event packets, such as type of stream, IP address, and port for both the local and remote endpoints. The output from this command provides an overview of all the media-forking connections in the system, and this information can be used to narrow the criteria for debugging. The debug voip rtp command floods the console with voice packet information. You can use the show voip rtp forking command to display the remote IP address, or remote port identifiers that you can use to limit the output from the debug voip rtp command.

Examples

The following is sample output from the show voip rtp forking command:

Indicates the logical synchronization source (SSRC) for the specified channel.

packets sent

Total number of packets sent from the channel.

packets received

Total number of packets received by the channel.

Related Commands

Command

Description

debug voip rtp

Enables debugging for RTP named event packets.

show vrm active_calls

To display active-only voice calls either for a specific voice feature card (VFC) or for all VFCs, use the show vrm active_calls command in privileged EXEC mode.

show vrm active_calls {dial-shelf-slot-number | all}

Syntax Description

dial-shelf-slot-number

Slot number of the dial shelf. Range is from 0 to 13.

all

Displays list of all active calls for VFC slots.

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)T

This command was introduced on the Cisco AS5800.

Usage Guidelines

Use this command to display active-only voice calls either for a specific VFC or for all VFCs. Each active call occupies a block of information describing the call. This information provides basically the same information as the show vrm vdevice command.

Examples

The following is sample output from this command specifying a dial-shelf slot number:

Command Modes

Privileged EXEC

Command History

Release

Modification

12.0(7)T

This command was introduced on the Cisco AS5800.

12.2(11)T

The alarms keyword and vfc-slot-number-for-alarms argument were added.

Usage Guidelines

Use this command to display detailed information for a specific DSP or a brief summary for all VFCs. The display provides information such as the number of channels, channels per DSP, bitmap of digital signal processor modules (DSPMs), DSP alarm statistics, and version numbers. This information is useful in monitoring the current state of your VFCs.

The display for a specific DSP provides information on the codec that each channel is using, if active, or on the codec that was last used and whether the channel is not currently sending cells. It also displays the state of the resource. In most cases, if there is an active call on that channel, the resource should be marked active. If the resource is marked as reset or bad, this may be an indication of a response loss for the VFC on a reset request. If this condition persists, you might experience a problem with the communication link between the router shelf and the VFC.

Examples

The following is sample output from this command specifying dial-shelf slot number and DSP number. In this particular example, the call is active so the statistics displayed are for this active call. If no calls are currently active on the device, the statistics would be for the previous (or last active) call.

The following is sample output from this command specifying a summary list. In the "Voice Device Mapping" area, the "C_Ac" column indicates the number of active calls for a specific DSP. If there are any nonzero numbers under the "C_Rst" and/or "C_Bad" column, a reset request was sent, but it was lost; this could mean a faulty DSP.

Related Commands

shut

To shut down a set of digital signal processors (DSPs) on the Cisco 7200 series router, use the shut command in DSP configuration mode. To put DSPs back in service, use the no form of this command.

shutnumber

no shut number

Syntax Description

number

Number of DSPs to be shut down.

Command Default

No shut

Command Modes

DSP configuration

Command History

Release

Modification

12.0(5)XE

This command was introduced on the Cisco 7200 series.

12.1(1)T

This command was modified to add information about DSP groups.

Usage Guidelines

This command applies to VoIP on the Cisco 7200 series routers.

Examples

The following example shuts down two sets of DSPs:

shut 2

shutdown (Annex G neighbor)

To disable the service relationships requirement for border elements, use the shutdown command in config-nxg-neigh-srvc mode. To enable the service relationship for border elements, use the no form of this command.

shutdown

no shutdown

Syntax Description

This command has no arguments or keywords.

Command Default

The Annex G neighbor is shut down.

Command Modes

Annex G neighbor service

Command History

Release

Modification

12.2(11)T

This command was introduced.

Usage Guidelines

The no shutdown command verifies that a domain name has been configured and ensures that the border element has been configured to reject messages from unknown "stranger" border elements.

Examples

The following example enables the border element:

Router(config-nxg-neigh-srvc)# no shutdown

Related Commands

Command

Description

access-policy

Requires that a neighbor be explicitly configured.

inbound ttl

Sets the inbound time-to-live value.

outbound retry-interval

Defines the retry period for attempting to establish the outbound relationship between border elements.

retry interval

Defines the time between delivery attempts.

retry window

Defines the total time that a border element attempts delivery.

shutdown (Annex G)

To shut down the Annex G border element (BE), use the shutdowncommand in Annex G configuration mode. To reinstate the Annex G BE, use the no form of this command.

shutdown

no shutdown

Syntax Description

This command has no arguments or keywords.

Command Default

The Annex G border element is not shut down.

Command Modes

Annex G configuration

Command History

Release

Modification

12.2(2)XA

This command was introduced.

12.2(4)T

This command was integrated into Cisco IOS Release 12.2(4)T. This command was not supported on the Cisco AS5300, Cisco AS5350, and Cisco AS5400 in this release.

12.2(2)XB1

This command was implemented on the Cisco AS5850.

12.2(11)T

This command was integrated into Cisco IOS Release 12.2(11)T.

Usage Guidelines

While the Annex G BE is in shutdown state, all Annex G messages received from neighbors are ignored and the colocated gatekeeper does not use the Annex G BE for address resolution.

Examples

The following example shuts the BE down:

Router(config)# call-router h323-annexg be20

Router(config-annexg)# shutdown

Related Commands

Command

Description

call-router

Enables the Annex G border element configuration commands.

show call-router status

Displays the Annex G BE status.

shutdown (dial peer)

To change the administrative state of the selected dial peer from up to down, use the shutdown command in dial peer configuration mode. To change the administrative state of this dial peer from down to up, use the no form of this command.

shutdown

no shutdown

Syntax Description

This command has no arguments or keywords.

Command Default

No shutdown

Command Modes

Dial peer configuration

Command History

Release

Modification

11.3(1)T

This command was introduced on the Cisco 3600 series.

12.1(1)

This command was modified for store-and-forward fax.

Usage Guidelines

When a dial peer is shut down, you cannot initiate calls to that peer.

This command applies to both on-ramp and off-ramp store-and-forward fax functions.

Examples

The following example changes the administrative state of voice telephony (plain old telephone service [POTS]) dial peer 10 to down:

dial-peer voice 10 pots

shutdown

The following example changes the administrative state of voice telephony (POTS) dial peer 10 to up:

dial-peer voice 10 pots

no shutdown

Related Commands

shutdown (DSP Farm profile)

To disable the digital signal processor (DSP) farm profile, use the shutdown command in DSP farm profile configuration mode. To allocate DSP farm resources and associate with the application, use the no form of this command.

shutdown

no shutdown

Syntax Description

This command has no arguments or keywords.

Command Default

Disabled

Command Modes

DSP farm profile configuration

Command History

Release

Modification

12.3(8)T

This command was introduced.

Usage Guidelines

It is essential that the profile be disabled by using the shutdown command before a DSP farm profile is updated.

Examples

The following example allocates DSP farm resources and associates with the application:

Specifies the maximum number of sessions that need to be supported by the profile.

shutdown (gatekeeper)

To disable the gatekeeper, use the shutdown command in gatekeeper configuration mode. To enable the gatekeeper, use the no form of this command.

shutdown

no shutdown

Syntax Description

This command has no arguments or keywords.

Command Default

Disabled (shut down)

Command Modes

Gatekeeper configuration

Command History

Release

Modification

11.3(2)NA

This command was introduced on the Cisco 2500 series and Cisco 3600 series.

12.0(3)T

The command was integrated into Cisco IOS Release 12.0(3)T and implemented on the Cisco MC3810.

Usage Guidelines

The gatekeeper does not have to be enabled before you can use the other gatekeeper configuration commands. In fact, it is recommended that you complete the gatekeeper configuration before bringing up the gatekeeper because some characteristics may be difficult to alter while the gatekeeper is running, as there may be active registrations or calls.

The no shutdown command enables the gatekeeper, but it does not make the gatekeeper operational. The two exceptions to this are as follows:

•If no local zones are configured, a no shutdown command places the gatekeeper in INACTIVE mode waiting for a local zone definition.

•If local zones are defined to use an HSRP virtual address, and the HSRP interface is in STANDBY mode, the gatekeeper goes into HSRP STANDBY mode. Only when the HSRP interface is ACTIVE does the gatekeeper go into the operational UP mode.

Examples

The following command disables a gatekeeper:

shutdown

Related Commands

Command

Description

shutdown (gateway)

Shuts down all VoIP call service on a gateway.

shutdown (gateway)

To shut down all VoIP call service on a gateway, use the shutdown command in voice service configuration mode. To enable VoIP call service, use the no form of this command.

shutdown [forced]

no shutdown

Syntax Description

forced

(Optional) Forces the gateway to immediately terminate all in-progress calls.

Command Default

Call service is enabled

Command Modes

Voice service configuration

Command History

Release

Modification

12.3(1)

This command was introduced.

Examples

The following example shows VoIP call service being shut down on a Cisco gateway:

voice service voip

shutdown

The following example shows VoIP call service being enabled on a Cisco gateway:

voice service voip

no shutdown

Related Commands

Command

Description

shutdown (gatekeeper)

Disables the gatekeeper.

shutdown (mediacard)

To disable a selected media card, use the shutdown command in mediacard configuration mode. To enable a selected media card, use the no form of this command.

shutdown

no shutdown

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

Media card configuration

Command History

Release

Modification

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.

12.4(3)

This command was integrated into Cisco IOS Release 12.4(3).

Usage Guidelines

Use the no shutdown command at the end of media card configuration. If there are any active connections when you disable the media card, the Digital Signal Processor Resource Manager (DSPRM) displays a warning message indicating that the DSP resources allocated on other media cards for some of the resource pool in this media card will be removed or that there are active connections available in this resource pool and prompts you for a response. Profiles that use resources on this card must be brought up separately after using this command.

Examples

The following example shows how to enable a media card:

no shutdown

Related Commands

Command

Description

resource-pool

Creates a DSP resource pool on the selected media card.

shutdown (auto-config application)

To disable an auto-configuration application for download, use the shutdown command in auto-config application configuration mode. To enable an auto-configuration application for download, use the no form of this command.

shutdown

no shutdown

Syntax Description

This command has no keywords or arguments.

Command Default

Disabled

Command Modes

Auto-config application configuration

Command History

Release

Modification

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 shutdown command used to enable an auto-configuration application for download:

shutdown (RLM)

To shut down all of the links under the RLM group, use the shutdown command in RLM configuration mode. RLM does not try to reestablish those links until the command is negated. To disable this function, use the no form of this command.

shutdown

no shutdown

Syntax Description

This command has no arguments or keywords.

Command Default

Disabled

Command Modes

RLM configuration

Command History

Release

Modification

11.3(7)

This command was introduced.

Related Commands

Command

Description

clear interface

Resets the hardware logic on an interface.

clear rlm group

Clears all RLM group time stamps to zero.

interface

Defines the IP addresses of the server, configures an interface type, and enters interface configuration mode.

link (RLM)

Specifies the link preference.

protocol rlm port

Reconfigures the port number for the basic RLM connection for the whole rlm-group.

retry keepalive

Allows consecutive keepalive failures a certain amount of time before the link is declared down.

server (RLM)

Defines the IP addresses of the server.

show rlm group statistics

Displays the network latency of the RLM group.

show rlm group status

Displays the status of the RLM group.

show rlm group timer

Displays the current RLM group timer values.

timer

Overwrites the default setting of timeout values.

shutdown (settlement)

To deactivate the settlement provider, use the shutdown command in settlement configuration mode. To activate a settlement provider, use the no version of the command.

shutdown

no shutdown

Syntax Description

This command has no arguments or keywords.

Command Default

The default status of a settlement provider is deactivated. The settlement provider is down.

Command Modes

Settlement configuration

Command History

Release

Modification

12.0(4)XH1

This command was introduced on the Cisco 2500 series, Cisco 3600 series, and Cisco AS5300.

12.1(1)T

This command was integrated into Cisco IOS Release 12.1(1)T.

Usage Guidelines

Use this command at the end of the configuration of a settlement server to bring up the provider. This command activates the provider. Otherwise, transactions do not go through the provider to be audited and charged. Use the shutdown command to deactivate the provider.

Examples

The following example enables a settlement server:

settlement 0

no shutdown

The following example disables a settlement server:

settlement 0

shutdown

Related Commands

Command

Description

connection-timeout

Configures the time that a connection is maintained after completing a communication exchange.

customer-id

Identifies a carrier or ISP with a settlement provider.

device-id

Specifies a gateway associated with a settlement provider.

encryption

Sets the encryption method to be negotiated with the provider.

max-connection

Sets the maximum number of simultaneous connections to be used for communication with a settlement provider.

response-timeout

Configures the maximum time to wait for a response from a server.

retry-delay

Sets the time between attempts to connect with the settlement provider.

session-timeout

Sets the interval for closing the connection when there is no input or output traffic.

settlement

Enters settlement configuration mode and specifies the attributes specific to a settlement provider.

type

Configures an SAA-RTR operation type.

shutdown (voice-port)

To take the voice ports for a specific voice interface card offline, use the shutdown command in voice-port configuration mode. To put the ports back in service, use the no form of this command.

shutdown

no shutdown

Syntax Description

This command has no arguments or keywords.

Defaults

Shutdown

Command Modes

Voice-port configuration

Command History

Release

Modification

11.3(1)T

This command was introduced on the Cisco 3600 series.

12.4(22)T

Support for IPv6 was added.

Usage Guidelines

When you use this command, all ports on the voice interface card are disabled. When you use the no form of the command, all ports on the voice interface card become enabled. A telephone connected to an interface hears silence when a port is shut down.