MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

Table Of Contents

MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

Contents

Prerequisites for MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

Restrictions for MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

Information About MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

Benefits of MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways Feature

Feature Design of MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

Supported Endpoints

Supported Call Types

Call Control Components

Supported Gateways, Modules and Voice Interface Cards

How to Configure the MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways Feature

Configuring the SCCP Gateway and Gateway Endpoints on Cisco CallManager

Cisco CallManager Autoconfiguration

Configuring Cisco CallManager Download on Cisco IOS Gateways

Configuring SCCP on Cisco IOS Gateways

Configuring STCAPP on Cisco IOS Gateways

Configuring ISDN BRI Voice Calls

Configuring Modem Pass-Through Calls

Verifying MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

Troubleshooting Tips

Configuration Examples for MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways: Example

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Command Reference

ccm-manager sccp

ccm-manager sccp local

debug ccm-manager

debug voip application stcapp all

debug voip application stcapp error

debug voip application stcapp events

debug voip application stcapp functions

debug voip application stcapp port

debug voip dcapi

show call active voice

show call application voice

show ccm-manager

show stcapp device

show stcapp statistics

stcapp

stcapp ccm-group

stcapp timer

Glossary

MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

First Published: October 30, 2005

Last Updated: June 19, 2006

The MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways feature provides the capability for Cisco IOS voice gateways to present analog and BRI phones to be controlled by the Cisco Unified CallManager and Cisco Unified CallManager Express (Cisco Unified CME) as though they were Cisco IP phones, enabling the following:

•Line-side support for the Multilevel Precedence and Preemption (MLPP) feature under Cisco CallManager control (Cisco Unified CME control is not supported)

•Cisco CallManager registration of analog and BRI endpoints (Cisco Unified CME control is not supported)

•Cisco CallManager endpoint autoconfiguration support

•Modem pass-through support

•Cisco Survivable Remote Site Telephony (SRST) support under Cisco CallManager control

Feature History for the MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

Release

Modification

Cisco IOS Release 12.3(14)T

This feature was introduced.

Cisco IOS Release 12.4(9)T

This feature was implemented on the following platforms: Cisco 2801, Cisco 2811, Cisco 2821, Cisco 2851, Cisco 3825, Cisco 3845, Cisco VG 224.

Feature

Finding Support Information for Platforms and Cisco IOS Software Images

Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.

Contents

•Prerequisites for MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

•Restrictions for MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

•Information About MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

•How to Configure the MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways Feature

•Configuration Examples for MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

•Additional References

•Command Reference

•Glossary

Prerequisites for MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

Make sure that the following tasks have been completed before configuring the MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways feature:

•Skinny Client Control Protocol (SCCP) version 4.0 or higher is enabled.

•Cisco CallManager 4.1 or a later release is running.

•Cisco IOS Release 12.4(9)T or a later release is running.

Restrictions for MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

•Unlike Cisco IP phones, which maintain active communications with all Cisco CallManagers, gateway-controlled endpoints communicate only with the active Cisco CallManager.

•MLPP is not supported in SRST environments or under Cisco Unified CME-control.

•Unlike Cisco IP phones, gateway-controlled phones preempted for reuse and remaining off-hook will not be auto-idled by Cisco CallManager.

•The following supplementary services are not supported:

–Hold

–Callback

–Transfer

–Call Forward

–Redial

•Only a single ISDN B channel is supported for BRI voice calls.

•ISDN circuit-switched or packet-switched data is not supported on BRI calls.

•Fallback to other protocols, such as H.323 or Media Gateway Control Protocol (MGCP), is not supported.

•The MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways feature is supported on the following ISDN switches only:

–National ISDN-1 switches

–NET3 ISDN switches, including Norway NET3, Australia NET3, and New Zealand NET3 switches (covers the Euro-ISDN E-DSS1 signaling system and is European Telecommunications Standards Institute (ETSI)-compliant).

Information About MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

To configure the MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways feature, you should understand the following concepts:

•Benefits of MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways Feature

•Feature Design of MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

Benefits of MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways Feature

•Supports the use of existing customer premises equipment (CPE) in voice networks, by allowing legacy analog and BRI phones attached to a Cisco IOS gateway to be controlled by the Cisco CallManager.

•Facilitates replacement of public switched telephone network (PSTN) time-division multiplexing (TDM) infrastructure with VoIP.

Feature Design of MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

Prior to the implementation of the MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways feature, there was no Cisco CallManager support for existing CPE, that is, Cisco IOS gateway-controlled legacy analog and BRI telephony endpoints. There was no capability to translate call control messages between the CPE and Cisco CallManager for calls connecting over the VoIP network to the existing PSTN. The MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways feature provides this support by presenting CPE devices to the Cisco CallManager as though they were Cisco IP phones. The new feature uses Cisco proprietary SCCP to communicate call control messages between the Cisco CallManager and gateway endpoints, which can be foreign exchange station (FXS) analog or BRI ISDN encryption-enabled phones. Cisco implements this support by the use of the SCCP Telephony Control Application (STCAPP) software that runs on existing line-side gateways. The line-side gateway translates call control messages between the Cisco CallManager SCCP and the Call Control Application Programming Interface (CCAPI), allowing the attached analog and BRI phones to be controlled by the Cisco CallManager in the same way that Cisco IP phones are controlled. To the Cisco CallManager, each gateway appears to be a collection of multiple SCCP-controlled IP phones.

The new feature supports the following capabilities:

•Basic call support (supplementary services are not supported).

•Cisco CallManager registration of analog and BRI endpoints.

•Autoconfiguration using TFTP download of extensible markup language (XML) dial-peer configuration files from the Cisco CallManager.

•MLPP support to analog and BRI endpoints. MLPP support enables the voice gateway to interoperate with other MLPP-capable networks for call preemption and precedence.

•Cisco Survivable Remote Site Telephony (SRST), enabling routers to provide call-handling support for Cisco IP phones, analog, and BRI endpoints when connections to remote primary, secondary, or tertiary Cisco CallManager installations are lost, or when the WAN connection is down. For more information on configuring SRST refer to the following:

–Cisco IOS Survivable Remote Site Telephony Version 3.3 System Administrator Guide

–Cisco IOS Survivable Remote Site Telephony Version 3.3 Command Reference

•Modem pass-through allowing secure telephones to use modem signaling to establish secure communications during a call.

Supported Endpoints

The MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways feature provides support for existing CPE, that is legacy analog and BRI telephony endpoints (phones). You may connect the following phone types in a VoIP network where the MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways feature is enabled:

•Analog phones, either standard or encryption enabled.

•ISDN BRI phones, capable of carrying standard or encrypted phone calls.

All these phones appear to the Cisco CallManager as though they were Cisco IP phones, thereby enabling MLPP capability.

Supported Call Types

In addition to basic voice calls, you may make the following calls in a VoIP network where the MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways feature is enabled:

•MLPP calls: MLPP service allows properly validated users to place priority calls, and if necessary, users can preempt lower-priority phone calls. Precedence designates the priority level that is associated with a call. Preemption designates the process of terminating lower-precedence calls that are currently using the target device, (either trunks or stations), so a call of higher precedence can be extended to or through the device. An authenticated user can preempt calls either to targeted stations or through fully subscribed time division multiplexing (TDM) trunks. This capability assures high-ranking personnel of communication to critical organizations and personnel during network stress situations, such as a national emergency or degraded network situations.

•Modem pass-through calls. Modem pass-through, the transport of modem signals through a packet network using pulse code modulation (PCM) encoded packets, uses a Cisco proprietary protocol, Named Signaling Events (NSE), to signal events that are exchanged between gateways, using Real-time Transport Protocol (RTP) packets.

Call Control Components

The MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways feature uses a number of software components to achieve call control. In order for the Cisco CallManager to manage gateway endpoints, that is , phones that are connected to Cisco IOS gateways, the Cisco CallManager exchanges messages with gateways, and the gateways exchange messages with the phones. Call control message exchange involve the following processes:

•Cisco IP Phones communicate with the Cisco CallManager through SCCP, which comprises a messaging set between a skinny client (IP phone) and the Cisco CallManager call-processing server. With the MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways feature enabled, SCCP is enabled on the gateway that sits between endpoints and the Cisco CallManager, thereby allowing endpoints to communicate with the Cisco CallManager as though they were Cisco IP phones.

•The MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways feature implements a new Cisco IOS application, the SCCP Telephony Control Application (STCAPP), to translate SCCP call control messages received from the Cisco CallManager. STCAPP processes messages received from the Cisco Call Manaager by using the Device Control API (DCAPI), a software layer that interfaces STCAPP with SCCP. STCAPP then interfaces with the physical analog and ISDN phones by way of the CCAPI software layer. CCAPI, which provides the interface between the software and the actual FXS and BRI ports on the line-side gateway, tells the physical devices to provide dial-tone, ringing, ringback, digit-collection, and so forth.

Supported Gateways, Modules and Voice Interface Cards

Table 1 provides a list of supported gateways, modules, and voice interface cards (VICs).

Table 1 Supported Gateways, Modules, and VICs for the MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways Feature

Supported Gateways

Supported Extension Modules

Supported Network Modules and Expansion Modules

Supported VICs

•Cisco 2801

•Cisco 2811

•Cisco 2821

•Cisco 2851

•Cisco 3825

•Cisco 3845

—

•NM-HD-1V

•NM-HD-2V

•NM-HD-2VE

•VIC2-2FXS

•VIC-4FXS/DID

•VIC2-2BRI-NT/TE

•Cisco 2801

•Cisco 2821

•Cisco 2851

•Cisco 3825

•Cisco 3845

•EVM-HD

•EVM-HD-8FXS/DID

•EM-3FXS/4FXO

•EM-HDA-8FXS

•EM-4BRI-NT/TE

—

•Cisco 2801

•Cisco 2811

•Cisco 2821

•Cisco 2851

•Cisco 3825

•Cisco 3845

—

•NM-HDV2

•NM-HDV2-1T1/E1

•NM-HDV2-2T1/E1

•VIC2-2FXS

•VIC-4FXS/DID

•VIC2-2BRI-NT/TE

•Cisco VG 224

—

—

—

How to Configure the MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways Feature

This section contains the following procedures:

•Configuring the SCCP Gateway and Gateway Endpoints on Cisco CallManager (required)

•Configuring Cisco CallManager Download on Cisco IOS Gateways, page 9 (required)

•Configuring SCCP on Cisco IOS Gateways (required)

•Configuring STCAPP on Cisco IOS Gateways (optional)

•Configuring ISDN BRI Voice Calls (optional)

•Configuring Modem Pass-Through Calls (optional)

•Verifying MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways (optional)

Configuring the SCCP Gateway and Gateway Endpoints on Cisco CallManager

This task configures the SCCP gateway and SCCP gateway-controlled endpoints on the Cisco CallManager.

Cisco CallManager Autoconfiguration

There are two methods of configuring the MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways feature, either by using Cisco CallManager autoconfiguration or by manually configuring SCCP and STCAPP on the gateway. The first method allows you to configure the SCCP gateway and SCCP gateway controlled endpoints on the Cisco CallManager, then download XML configuration files for the endpoints to the Cisco IOS gateway. The second method requires you to manually enable STCAPP and manually configure gateway endpoints. We recommend the Cisco CallManager autoconfiguration method because it allows you to configure all devices in one place, eliminating endpoint configuration on the gateway.

Perform the following task to use Cisco CallManager autoconfiguration.

SUMMARY STEPS

1. Choose Add a New Device or Add a New Gateway in the Cisco CallManager menu.

2. Choose the new SCCP gateway settings.

3. Configure the gateway MAC address, network modules, voice interface cards, and ports.

4. Save the configuration.

5. Verify the configuration.

DETAILED STEPS

Step 1 In the drop-down list in Cisco CallManager, choose Device > Add a New Device > Gateway (from the Device Type) or choose Device > Gateway > Add a New Gateway.

Step 2 Choose the appropriate settings for the SCCP gateway.

a. Choose the gateway type.

b. Choose the SCCP option for device protocol.

Step 3 Enter the appropriate SCCP gateway MAC address and configure the network modules, voice interface cards, and ports.

a. Enter the last ten characters of the MAC address of the interface used to register with the Cisco CallManager. Use the show interface command on the SCCP configured interface on the gateway to determine the gateway MAC address. (This MAC address is the same as the address of the SCCP gateway local interface manually configured in Step 4 of the"DETAILED STEPS" section of "Configuring SCCP in Cisco IOS Gateways."

b. Enter the gateway name.

c. Enter the Cisco CallManager group number.

d. Configure the appropriate network modules, voice interface cards and ports.

Note Gateway VIC port and slot numbers are referred to as Endpoint Identifiers on the Cisco CallManager. For more information on Cisco CallManager gateway configuration, refer to the section "Adding a Cisco IOS SCCP Gateway," in the Cisco CallManager Administration Guide, Release 4.1(2).

Step 4 Click Insert to save a new gateway configuration, or click Update to save an existing gateway configuration.

Step 5 Verify your configuration by displaying the list of configured analog and BRI phones. In the Cisco CallManager menu choose Device > Phone > Find. Analog phone device name begin with "AN" and BRI phone device names begin with "BR".

Configuring Cisco CallManager Download on Cisco IOS Gateways

This task configures automatic download capability of XML dial-peer configuration files from the Cisco CallManager and enables Cisco CallManager autoconfiguration.

Note Although you may manually configure dial peers to work with the MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways feature, we recommend that you use Cisco CallManager autoconfiguration.

SUMMARY STEPS

1. enable

2. configure terminal

3. ccm-manager sccp local interface-type interface-number

4. ccm-manager config [dialpeer-prefix prefix | server {ip-address | name}]

5. ccm-manager sccp

6. exit

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

ccm-manager sccp local interface-type interface-number
Example:

Router(config)# ccm-manager sccp local fastethernet0/0

Selects the local interface that the SCCP application should use to register with Cisco CallManager. This interface must be specified before you enable the autoconfiguration process.

•interface-type—Interface type that the SCCP application uses to register with Cisco CallManager.

•interface-number—Interface number that the SCCP application uses to register with Cisco CallManager.

Step 4

ccm-manager config [dialpeer-prefix prefix | server {ip-address | name}]
Example:

Router(config)# ccm-manager config dialpeer-prefix 888

Enables the download of Cisco CallManager XML configuration files.

•dialpeer prefix prefix—Configures the prefix to use for autogenerated dial peers. Range is 0 to 999999. The default is 999.

Note When manually adding a dial peer-prefix, select a prefix number other than the autoconfigured dial peer prefix (999 by default), to keep manually added dial peers from being deleted from the running configuration when the Cisco CallManager download happens in the gateway.

•server ip-address—Specifies the IP address of the TFTP server from which to download the XML configuration files to the Cisco IOS gateway.

•server name—Specifies the TFTP server name from which the Cisco IOS gateway downloads Cisco CallManager XML configuration files.

Step 5

ccm-manager sccp
Example:

Router(config)# ccm-manager sccp

Enables the autoconfiguration process. This command immediately triggers the TFTP download of the XML configuration file.

Step 6

exit
Example:

Router(config)# exit

Exits the current configuration mode.

Configuring SCCP on Cisco IOS Gateways

This task configures SCCP on the Cisco IOS gateway. SCCP messaging enables Cisco CallManager endpoint call control.

SUMMARY STEPS

1. enable

2. configure terminal

3. sccp ccm {ip-address | dns} identifier identifier-number [port port-number][version version-number]

4. sccp local interface-type interface-number

5. sccp ccm group group-number

6. associate ccm identifier-number priority priortiy-number

7. sccp

8. exit

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

sccp ccm {ip-address | dns} identifier identifier-number [port port-number] [version version-number]
Example:

Router(config)# sccp ccm 10.1.1.1 identifier 5

Adds a Cisco CallManager server to the list of available servers and sets various parameters.

•IP address— Specifies the IP address of the Cisco CallManager server.

•identifier-number—Identifies the Cisco CallManager associated with the Cisco CallManager group-number configured in Step 5 . Valid entries are from 1 to 65535. There is no default value.

Step 4

sccp local interface-type interface-number
Example:

Router(config)# sccp local fastethernet0/0

Selects the local interface that the SCCP application uses to register with Cisco CallManager. (This interface is the interface whose MAC address is specified for SCCP gateway registration using Cisco CallManager autoconfiguration in Step 3 of the "DETAILED STEPS" section.)

•interface-type—Specifies the interface type that the SCCP application uses to register with Cisco CallManager.

•interface-number—Specifies the interface number that the SCCP application uses to register with Cisco CallManager.
Step 5
sccp ccm group group-number
Example:

Router(config)# sccp ccm group 1
Creates a Cisco CallManager group.

•group-number—Associates the Cisco CallManager group with the Cisco CallManager group identifier configured in Step 3. Range is 1 to 65535. There is no default value.
Step 6

associate ccm identifier-number priority priority-number
Example:

Router(config)# associate ccm 5 priority 1

Associates a Cisco CallManager with a Cisco CallManager group.

•identifier-number—Identifies the Cisco CallManager associated with the Cisco CallManager group-number configured in Step 5 . Valid entries are from 1 to 65535. There is no default value.

•priority-number— Priority of the Cisco CallManager within the Cisco CallManager group. Range is 1 to 4. There is no default value. The highest priority is 1.

Step 7

sccp
Example:

Router(config)# sccp

Enables SCCP and its related applications.

Step 8

exit
Example:

Router(config)# exit

Exits the current configuration mode.
Configuring STCAPP on Cisco IOS Gateways

This task manually configures STCAPP on the Cisco IOS gateway. STCAPP translates incoming SCCP call control messages received from the Cisco CallManager.

SUMMARY STEPS

1. enable

2. configure terminal

3. stcapp ccm-group group-id

4. stcapp

5. stcapp timer roh seconds

6. exit

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

stcapp ccm-group group-id
Example:

Router(config)# stcapp ccm-group 1

Specifies the Cisco CallManager group number.

•The ccm-group group-id must match the Cisco CallManager identifier configured for the service- provider interface (SPI) using the sccp ccm-group [group-id] command.

Step 4

stcapp
Example:

Router(config)# stcapp

Enables the STCAPP.

Step 5

stcapp timer roh seconds
Example:

Router(config)# stcapp timer roh 30

(Optional) Configures the STCAPP timer.

•roh—Configures the maximum duration a receiver off hook tone is played. The receiver off hook (ROH) tone signals the subscriber that the phone remains off hook when there is no active call.

•seconds—Specifies the ROH tone timeout duration in seconds. Timeout must be a number in the range from 0 to 120. Default is 45 seconds.

Step 6

exit
Example:

Router(config)# exit

Exits the current configuration mode.

Configuring ISDN BRI Voice Calls

This task configures ISDN BRI ports.

SUMMARY STEPS

1. enable

2. configure terminal

3. isdn switch-type switch-type

4. interface bri slot/port

5. isdn layer1-emulate network

6. isdn protocol-emulate {network | user}

7. isdn point-to-point-setup

8. isdn spid1 spid

9. no shutdown

10. exit

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

isdn switch-type switch-type
Example:

Router(config)# isdn switch-type basic-ni

Configures the telephone-company ISDN switch type. The following ISDN switch types support the MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways feature:

•basic-ni—Specifies national ISDN-1 switches.

•basic-net3— Specifies NET3 ISDN: Norway NET3, Australia NET3, and New Zealand NET3 switches (covers the Euro-ISDN E-DSS1 signaling system and is ETSI-compliant)

Step 4

interface bri slot/port
Example:

Router(config)# interface bri 1/1

Enters interface configuration mode for the specified slot/port (location of voice network module and voice interface card).

Step 5

isdn layer1-emulate network
Example:

Router(config-if)# isdn layer1-emulate network

Configures Layer 1 port mode emulation and clock status for the network.

Step 6

isdn protocol-emulate {network | user}
Example:

Router(config-if)# isdn protocol-emulate network

Configures Layer 2 and Layer 3 port mode emulation and clock status.

•network—Network termination (NT) side, that is, the clock slave.

Step 7

isdn point-to-point-setup
Example:

Router(config-if)# isdn point-to-point-setup

Configures the ISDN port to send SETUP messages on the static terminal endpoint identifier (TEI) point-to-point link.

Note Network-side BRI NI does not support point-to-multipoint topology.

Step 8

isdn spid1 spid1
Example:

Router(config-if)# isdn spid1 40855522220101

Specifies the service-profile identifier (SPID).
Step 9
no shutdown
Example:

Router(config-if)# no shutdown
Turns on the voice port.
Step 10

exit
Example:

Router(config-if)# exit

Exits the current configuration mode.
Configuring Modem Pass-Through Calls

This task configures modem pass-through operation on the gateway.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice service {pots | voatm | vofr | voip}

4. modem passthrough nse [payload-type number] {codec {g711ulaw | g711alaw}} [redundancy [maximum-sessions sessions]]

5. exit

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

voice service {pots | voatm | vofr | voip}
Example:

Router(config)# voice service voip

Enters voice-service configuration mode and specifies a voice-encapsulation type.

•voip—Voice over IP (VoIP) encapsulation.

Step 4

modem passthrough nse [payload-type number] {codec {g711ulaw | g711alaw}} [redundancy [maximum-sessions sessions]]
Example:

Router(config-voi-serv)# modem passthrough nse codec g711ulaw

Enables fax or modem pass-through over VoIP globally for all dial peers.

•nse—Specifies that named signaling events (NSEs) are used to communicate codec switchover between gateways.

•codec—Configures codec selections for upspeeding, the capability to automatically change the voice codec to G.711 if necessary and turn off echo cancellation (EC) and voice activity detection (VAD) for the duration of the call.

•g711ulaw—Specifies codec G.711 mu-law, 64,000 bits per second for T1.

Step 5

exit
Example:

Router(config-voi-serv)# exit

Exits the current configuration mode.

Verifying MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

This task verifies MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways feature configuration.

SUMMARY STEPS

1. show call active voice

2. show call application voice stcapp

3. show ccm-manager config- download

4. show stcapp device voice-port port-number

5. show stcapp device voice-port summary

6. show stcapp statistics all

7. show stcapp statistics voice-port port-number

DETAILED STEPS

Step 1 Use the show call active voice command to display call information for voice calls in progress:
Router# show call active voice
Telephony call-legs: 2
SIP call-legs: 0
H323 call-legs: 0
Call agent controlled call-legs: 2
SCCP call-legs: 0
Multicast call-legs: 0
Total call-legs: 4
 GENERIC:
SetupTime=1557650 ms
Index=1
PeerAddress=
PeerSubAddress=
PeerId=999100
PeerIfIndex=14
LogicalIfIndex=10
ConnectTime=1562040 ms
CallDuration=00:01:01 sec
CallState=4
CallOrigin=2
ChargedUnits=0
InfoType=speech
TransmitPackets=3101
TransmitBytes=519564
ReceivePackets=3094
ReceiveBytes=494572
TELE:
ConnectionId=[0x11B1860C 0x22D711D7 0x8014E4D4 0x8FD15327]
IncomingConnectionId=[0x11B1860C 0x22D711D7 0x8014E4D4 0x8FD15327]
CallID=25
TxDuration=59670 ms
VoiceTxDuration=59670 ms
FaxTxDuration=0 ms
CoderTypeRate=g711ulaw
NoiseLevel=-12
ACOMLevel=22
OutSignalLevel=-12
InSignalLevel=-11
InfoActivity=1
ERLLevel=22
EchoCancellerMaxReflector=2
SessionTarget=
ImgPages=0
CallerName=
CallerIDBlocked=False
OriginalCallingNumber=
OriginalCallingOctet=0x0
OriginalCalledNumber=
OriginalCalledOctet=0x80
OriginalRedirectCalledNumber=
OriginalRedirectCalledOctet=0x0
TranslatedCallingNumber=
TranslatedCallingOctet=0x0
TranslatedCalledNumber=
TranslatedCalledOctet=0x80
TranslatedRedirectCalledNumber=
TranslatedRedirectCalledOctet=0x0
DSPIdentifier=1/1:1
 GENERIC:
SetupTime=1559430 ms
Index=1
PeerAddress=7702
PeerSubAddress=
PeerId=999100
PeerIfIndex=14
LogicalIfIndex=11
ConnectTime=1562020 ms
CallDuration=00:01:03 sec
CallState=4
CallOrigin=1
ChargedUnits=0
InfoType=speech
TransmitPackets=3151
TransmitBytes=528900
ReceivePackets=3158
ReceiveBytes=503876
TELE:
ConnectionId=[0x0 0x0 0x0 0x0]
IncomingConnectionId=[0x0 0x0 0x0 0x0]
CallID=26
TxDuration=60815 ms
VoiceTxDuration=60815 ms
FaxTxDuration=0 ms
CoderTypeRate=g711ulaw
NoiseLevel=-12
ACOMLevel=28
OutSignalLevel=-12
InSignalLevel=-11
InfoActivity=1
ERLLevel=28
EchoCancellerMaxReflector=2
SessionTarget=
ImgPages=0
CallerName=
CallerIDBlocked=False
AlertTimepoint=1559430 ms
OriginalCallingNumber=
OriginalCallingOctet=0x0
OriginalCalledNumber=
OriginalCalledOctet=0x0
OriginalRedirectCalledNumber=
OriginalRedirectCalledOctet=0x0
TranslatedCallingNumber=7701
TranslatedCallingOctet=0x0
TranslatedCalledNumber=7702
TranslatedCalledOctet=0x0
TranslatedRedirectCalledNumber=
TranslatedRedirectCalledOctet=0x0
GwOutpulsedCalledNumber=7702
GwOutpulsedCalledOctet3=0x0
GwOutpulsedCallingNumber=7701
GwOutpulsedCallingOctet3=0x0
GwOutpulsedCallingOctet3a=0x0
DSPIdentifier=1/1:2
 GENERIC:
SetupTime=1562040 ms
Index=1
PeerAddress=
PeerSubAddress=
PeerId=0
PeerIfIndex=0
LogicalIfIndex=0
ConnectTime=0 ms
CallDuration=00:00:00 sec
CallState=2
CallOrigin=1
ChargedUnits=0
InfoType=speech
TransmitPackets=3215
TransmitBytes=512996
ReceivePackets=3208
ReceiveBytes=512812
VOIP:
ConnectionId[0x0 0x0 0x0 0x0]
IncomingConnectionId[0x0 0x0 0x0 0x0]
CallID=27
RemoteIPAddress=0.0.0.0
RemoteUDPPort=17718
RemoteSignallingIPAddress=0.0.0.0
RemoteSignallingPort=0
RemoteMediaIPAddress=10.2.6.10
RemoteMediaPort=17718
RoundTripDelay=0 ms
SelectedQoS=best-effort
tx_DtmfRelay=inband-voice
FastConnect=FALSE
AnnexE=FALSE
Separate H245 Connection=FALSE
H245 Tunneling=FALSE
SessionProtocol=other
ProtocolCallId=
SessionTarget=
OnTimeRvPlayout=60640
GapFillWithSilence=0 ms
GapFillWithPrediction=0 ms
GapFillWithInterpolation=0 ms
GapFillWithRedundancy=0 ms
HiWaterPlayoutDelay=105 ms
LoWaterPlayoutDelay=105 ms
TxPakNumber=3040 
TxSignalPak=0 
TxComfortNoisePak=0 
TxDuration=60815 
TxVoiceDuration=60815 
RxPakNumber=3035 
RxSignalPak=0 
RxDuration=0 
TxVoiceDuration=60690 
VoiceRxDuration=60640 
RxOutOfSeq=0 
RxLatePak=0 
RxEarlyPak=0 
PlayDelayCurrent=105 
PlayDelayMin=105 
PlayDelayMax=105 
PlayDelayClockOffset=-1662143961 
PlayDelayJitter=0 
PlayErrPredictive=0 
PlayErrInterpolative=0 
PlayErrSilence=0 
PlayErrBufferOverFlow=0 
PlayErrRetroactive=0 
PlayErrTalkspurt=0 
OutSignalLevel=-12 
InSignalLevel=-11 
LevelTxPowerMean=0 
LevelRxPowerMean=-115 
LevelBgNoise=0 
ERLLevel=28 
ACOMLevel=28 
ErrRxDrop=0 
ErrTxDrop=0 
ErrTxControl=0 
ErrRxControl=0 
PlayoutMode = undefined
PlayoutInitialDelay=0 ms
ReceiveDelay=105 ms
LostPackets=0
EarlyPackets=0
LatePackets=0
SRTP = off
VAD = disabled
CoderTypeRate=g711ulaw
CodecBytes=160
Media Setting=flow-around
Modem passthrough signaling method is nse:
Buffer Fill Events = 0
Buffer Drain Events = 0
Percent Packet Loss = 0
Consecutive-packets-lost Events = 0
Corrected packet-loss Events = 0
Last Buffer Drain/Fill Event = 0sec
Time between Buffer Drain/Fills = Min 0sec Max 0sec
CallerName=
CallerIDBlocked=False
OriginalCallingNumber=
OriginalCallingOctet=0x0
OriginalCalledNumber=
OriginalCalledOctet=0x0
OriginalRedirectCalledNumber=
OriginalRedirectCalledOctet=0x0
TranslatedCallingNumber=
TranslatedCallingOctet=0x0
TranslatedCalledNumber=
TranslatedCalledOctet=0x0
TranslatedRedirectCalledNumber=
TranslatedRedirectCalledOctet=0x0
MediaInactiveDetected=no
MediaInactiveTimestamp=
MediaControlReceived=
Username=
 GENERIC:
SetupTime=1562040 ms
Index=2
PeerAddress=
PeerSubAddress=
PeerId=0
PeerIfIndex=0
LogicalIfIndex=0
ConnectTime=0 ms
CallDuration=00:00:00 sec
CallState=2
CallOrigin=1
ChargedUnits=0
InfoType=speech
TransmitPackets=3380
TransmitBytes=540332
ReceivePackets=3386
ReceiveBytes=540356
VOIP:
ConnectionId[0x0 0x0 0x0 0x0]
IncomingConnectionId[0x0 0x0 0x0 0x0]
CallID=28
RemoteIPAddress=0.0.0.0
RemoteUDPPort=18630
RemoteSignallingIPAddress=0.0.0.0
RemoteSignallingPort=0
RemoteMediaIPAddress=10.2.6.10
RemoteMediaPort=18630
RoundTripDelay=0 ms
SelectedQoS=best-effort
tx_DtmfRelay=inband-voice
FastConnect=FALSE
AnnexE=FALSE
Separate H245 Connection=FALSE
H245 Tunneling=FALSE
SessionProtocol=other
ProtocolCallId=
SessionTarget=
OnTimeRvPlayout=63120
GapFillWithSilence=0 ms
GapFillWithPrediction=0 ms
GapFillWithInterpolation=0 ms
GapFillWithRedundancy=0 ms
HiWaterPlayoutDelay=105 ms

Hierarchical Navigation

Cisco IOS Software Releases 12.3 T

MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

Downloads

Table Of Contents

MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

Contents

Prerequisites for MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

Restrictions for MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

Information About MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

Benefits of MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways Feature

Feature Design of MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

Supported Endpoints

Supported Call Types

Call Control Components

Supported Gateways, Modules and Voice Interface Cards

How to Configure the MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways Feature

Configuring the SCCP Gateway and Gateway Endpoints on Cisco CallManager

Cisco CallManager Autoconfiguration

SUMMARY STEPS

DETAILED STEPS

Configuring Cisco CallManager Download on Cisco IOS Gateways

SUMMARY STEPS

DETAILED STEPS

Configuring SCCP on Cisco IOS Gateways

SUMMARY STEPS

DETAILED STEPS

Configuring STCAPP on Cisco IOS Gateways

SUMMARY STEPS

DETAILED STEPS

Configuring ISDN BRI Voice Calls

SUMMARY STEPS

DETAILED STEPS

Configuring Modem Pass-Through Calls

SUMMARY STEPS

DETAILED STEPS

Verifying MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways

SUMMARY STEPS

DETAILED STEPS