![]() |
Table Of Contents
Prerequisites for Cisco Modem Relay
Restrictions for Cisco Modem Relay
Information About Cisco Modem Relay
How to Configure Cisco Modem Relay
Configuring Codec Complexity for TI 549 DSPs
Configuring H.323 and SIP Modem Relay
Configuring Cisco Modem Relay Parameters Globally for H.323 and SIP
Configuring Cisco Modem Relay Parameters for a Specific Dial Peer for H.323 and SIP
Configuration Examples for Cisco Modem Relay
Cisco Modem Relay Enabled for MGCP: Example
Cisco Modem Relay Configured on the VoIP Dial Peer: Example
Cisco Modem Relay
First Published: October 31, 2005Last Updated: February 27, 2006This document describes how to configure Cisco modem relay. This enhanced version of Cisco modem relay adds support for a nonnegotiated, bearer-switched mode for modem transport called gateway-controlled modem relay. The modem transport parameters are configured directly on the gateway by default, instead of being negotiated by the call agent.
History for the Cisco Modem Relay Feature
Release Modification12.4(4)T
This feature was introduced.
12.4(6)T
This feature was implemented on the Cisco 1700 series and Cisco 2800 series.
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.
Note
For more information about this and related Cisco IOS voice features, see the following:
•
Cisco IOS Fax and Modem Services over IP Application Guide
•
Cisco IOS Voice Configuration Library; including library preface and glossary, other feature documents, and troubleshooting documentation.
Contents
•
Prerequisites for Cisco Modem Relay
•
Restrictions for Cisco Modem Relay
•
Information About Cisco Modem Relay
•
How to Configure Cisco Modem Relay
•
Configuration Examples for Cisco Modem Relay
Prerequisites for Cisco Modem Relay
Before you configure Cisco modem relay, you must:
•
Establish a working H.323, Session Intiated Protocol (SIP), or Media Gateway Control Protocol (MGCP) network for voice calls.
•
Ensure that you have a Cisco IOS image that supports gateway-controlled modem relay.
•
Determine network suitability to relay modem traffic. The key attributes are packet loss, delay, and jitter. These characteristics of the network can be determined by using the Cisco IOS Service Assurance Agent (SA Agent) feature.
•
For TI 549 digital signal processors (DSPs), configure high codec complexity for the originating and terminating gateways.
Restrictions for Cisco Modem Relay
Restrictions of Cisco modem relay are as follows:
•
Cisco modem relay does not work with third-party gateways.
•
Cisco modem is supported on TI C5510 and TI C549 DSPs only.
•
Cisco modem relay does not support the V.150.1 signaling standard.
•
Cisco modem relay does not support Skinny Client Control Protocol (SCCP).
•
The originating gateway and the terminating gateway must both be configured for Cisco modem relay. If one gateway is configured for modem pass-through, the call occurs using modem pass-through.
•
Originating and terminating gateways must both be configured for a high or flex codec complexity to use Cisco modem relay. If either the originating or terminating gateway is configured for a medium complexity codec, modem pass-through is used.
•
The named signaling event (NSE) 199 event signal is sent with triple redundancy once from the terminating gateway. If this signal is lost or not recognized, the call occurs using modem pass-through.
•
Gateway-XID is enabled by default when Cisco modem relay is configured.
•
There is no mechanism to indicate that an upspeed has not taken place because of a call admission control (CAC) failure, regardless of tone detection. (Upspeed occurs when the gateway dynamically changes the codec from the codec configured for voice to G.711 with no VAD and no EC for the duration of the session.)
•
Cisco modem relay works only if both modems are high-speed modems (V.34, V.90) that use V.42bis bidirectional compression. For low-speed modems, gateways that carry traffic use modem pass-through.
•
Cisco modem relay works only if both modems use the V.42 error correction protocol and if the error correction layer in both modems is enabled.
•
MGCP, H.323, and SIP can be configured on the same gateway with some restrictions—all calls in a particular T1 or E1 must be handled by the same signaling type. If your gateway has multiple T1 or E1 facilities, calls on some T1s or E1s can be managed by MGCP and others can be managed by H.323 or SIP.
Supported Platforms
The Cisco Modem Relay feature adds support for modem relay functionality on the TI C5510-based analog and digital gateways, network modules, network interface cards (NICs), and the TI C549 DSP. See Table 1 for the list of DSPs, network modules, and platforms supported by this feature.
Information About Cisco Modem Relay
To configure the Cisco Modem Relay feature, you should understand the following concept:
Modes for Modem Transport
Cisco modem relay is a nonnegotiated, bearer-switched mode for modem transport that does not involve call-agent-assisted negotiation during the call setup. Instead, the negotiation parameters are configured directly on the gateway. These gateway-controlled negotiation parameters use NSEs to indicate the switchover from voice, to voice-band data (VBD), to modem relay.
Upon detecting 2100-Hz tone, the terminating gateway sends an NSE 192 to the originating gateway and switches over to modem pass-through. The terminating gateway also sends an NSE 199 to indicate modem relay. If this event is recognized by the originating gateway, the call occurs as modem relay. If the event is not recognized, the call occurs as modem pass-through.
Because Cisco modem relay uses configured parameters, it removes the signaling dependency from the call agent and allows modem relay support independent of call control. Cisco modem relay can be deployed over any call agent that can set up a voice connection between gateways, including Cisco CallManager, Cisco CallManager Express, Cisco PGW 2200 Softswitch, and Cisco BTS 10200 Softswitch.
The gateway-controlled modem relay parameters are enabled by default when Cisco modem relay is configured, and when Cisco modem relay is configured, gateway exchange identification (XID) parameter negotiation is always enabled. Gateway XID parameters are negotiated using the Simple Packet Relay Transport (SPRT) protocol.
How to Configure Cisco Modem Relay
This section describes the tasks required to configure Cisco modem relay for MGCP, H.323, or SIP:
•
Configuring Codec Complexity for TI 549 DSPs
•
Configuring H.323 and SIP Modem Relay
Configuring Codec Complexity for TI 549 DSPs
Codec complexity determines the codec types supported on the DSP.
•
The TI 5510 DSP supports medium, high, and flex complexity. The default is flex complexity.
•
The TI 549 DSP supports only high complexity.
If your platform uses the TI 549 DSP, you must configure high codec complexity.
Note
The VG224 and IAD2430 platforms only support flex complexity.
Supported Codecs
Cisco modem relay for MGCP and H.323 signaling types supports the high complexity codecs listed in Table 2.
Cisco modem relay for SIP supports the high complexity codecs listed in Table 3.
To configure high codec complexity for the Cisco 2600, Cisco 2800, Cisco 3600, Cisco 3700, and Cisco 3800 series routers on the originating and terminating gateways, perform the following steps:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
voice-card slot
4.
codec complexity high
DETAILED STEPS
Configuring MGCP Modem Relay
Note
You must configure Cisco modem relay on the originating and terminating gateways.
MGCP commands apply to the entire gateway. To configure Cisco modem relay for MGCP calls, use the following commands:
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
mgcp modem relay voip mode [nse] codec [g711alaw | g711ulaw] [redundancy] gw-controlled
DETAILED STEPS
Configuring H.323 and SIP Modem Relay
Note
You must configure Cisco modem relay parameters on both the originating and terminating gateways. The NSE payload-type number, codec, and negotiation parameter settings must match.
For H.323 and SIP configurations, Cisco modem relay can be configured at two levels:
•
Under voice-service configuration mode—This configuration is the global, or system-wide configuration that is applied to any VoIP call on the gateway. The default for voice-service configuration mode is no modem relay. See the "Configuring Cisco Modem Relay Parameters Globally for H.323 and SIP" section.
•
Under dial-peer voice configuration mode for VoIP dial peers—This configuration applies only to calls that match a specific dial peer. The default dial-peer configuration is modem relay system, which tells the gateway to use the parameters configured at the global level. See the "Configuring Cisco Modem Relay Parameters for a Specific Dial Peer for H.323 and SIP" section.
The two configuration tasks can be used separately or together. If both are configured, the dial-peer configuration overrides the global configuration.
Configuring Cisco Modem Relay Parameters Globally for H.323 and SIP
To configure Cisco modem relay parameters globally, use the following commands beginning in global configuration mode.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
voice service voip
4.
modem relay nse [payload-type number] codec {g711ulaw | g711alaw}
[redundancy[maximum-sessions value]] gw-controlledDETAILED STEPS
Configuring Cisco Modem Relay Parameters for a Specific Dial Peer for H.323 and SIP
Note
When Cisco modem relay is configured for a specific dial peer, the dial-peer configuration takes precedence over the global configuration.
To configure Cisco modem relay for a specific dial peer, use the following commands beginning in global configuration mode.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
dial-peer voice tag voip
4.
modem relay {nse [payload-type number] codec {g711alaw | g711ulaw} [redundancy] | system} gw-controlled
DETAILED STEPS
Troubleshooting Tips
Before using debug commands to troubleshoot Cisco modem relay, be sure that:
•
You can complete a voice call.
•
Cisco modem relay is configured on both the originating and terminating gateways.
•
Both the originating and terminating gateways have the same NSE payload-type number and codec parameters.
Use the following debug commands to troubleshoot Cisco modem relay:
•
To verify that parameter negotiation has occurred, use these debug commands:
–
debug mgcp packet—Use to check that modem relay parameters are not sent in the session definition protocol (SDP) for MGCP calls.
–
debug h245 ans1—Use to check that modem relay parameters are not sent as part of H.245 messaging.
–
debug ccsip calls—Use to check SIP messages.
•
The following are additional debug commands for troubleshooting:
–
debug voip hpi all—Use to check for event 199.
–
debug voip dsmp all—Use to check for event 199 and for modem relay parameters.
–
debug voip dsmp session—Use to see if event 199 has been implemented for this session.
Note
See the Cisco IOS Debug Command Reference for additional modem relay debug commands.
The following show commands can be used to verify Cisco modem relay configurations.
•
show call active voice—Displays call information for voice calls in progress. Use the brief keyword to display a truncated version.
•
show dial-peer voice tag summary—Displays information for voice dial peers. Use the tag argument to get information about a specific dial peer. Use the summary keyword to display a short summary of each dial peer
•
show call history voice—Displays the history table for voice calls. Use the brief keyword to display a truncated version.
•
show modem relay statistics—Displays various statistics for modem relay.
DSP Modem Relay Termination Codes
Table 4 lists the gateway DSP modem relay termination codes that display when you enter the debug hpi all command. The DSP-to-host messages for the modem relay termination indicate modem relay session termination time, physical or link layer, and other causes for disconnection. On receiving this indication from the DSP, the host can disconnect the call or place the channel in modem pass-through state.
Configuration Examples for Cisco Modem Relay
This section provides the following configuration examples for Cisco modem relay:
•
Cisco Modem Relay Enabled for MGCP: Example
•
Cisco Modem Relay Configured on the VoIP Dial Peer: Example
Cisco Modem Relay Enabled for MGCP: Example
The following example shows an MGCP configuration with modem relay enabled, the named signaling event and redundant packets parameters set:
version 12.3service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname Router!boot-start-markerboot system flash:c2800nm-ipvoice-mz.cisco_0224boot-end-marker!card type t1 1 1logging buffered 10000000 debuggingenable password lab!no aaa new-model!resource manager!clock timezone PST -8clock summer-time PDT recurringnetwork-clock-participate slot 1ip subnet-zero!ip cefno ip dhcp use vrf connected!ip domain list cisco.comno ip domain lookupip domain name cisco.comip host ccm 10.3.102.99no ftp-server write-enableisdn switch-type primary-qsig!voice-card 0codec complexity highdspfarm!voice-card 1dspfarm!voice service pots!voice service voipno fax-relay sg3-to-g3h323modem relay nse codec g711ulaw gw-controlled!voice service voatm!controller T1 1/0framing esfclock source internallinecode b8zspri-group timeslots 1-12,16,24!controller T1 1/1framing esfclock source internallinecode b8zspri-group timeslots 1-8,16,24 service mgcp!interface GigabitEthernet0/0ip address 10.2.109.103 255.255.0.0duplex autospeed autono clns route-cache!interface GigabitEthernet0/1no ip addressshutdownduplex autospeed auto!interface Serial1/0:23no ip addressno logging event link-statusisdn switch-type primary-qsigisdn incoming-voice voiceno cdp enable!interface Serial1/1:23no ip addressno logging event link-statusisdn switch-type primary-qsigisdn incoming-voice voiceisdn bind-l3 ccm-managerno cdp enable!ip default-gateway 10.2.0.1ip classlessip route 10.0.0.0 255.0.0.0 10.2.0.1ip route 192.168.254.254 255.255.255.255 GigabitEthernet0/0!ip http server!control-plane!voice-port 0/0/0!voice-port 0/0/1!voice-port 1/0:23connection plar 2000!voice-port 1/1:23!ccm-manager mgcpccm-manager music-on-holdccm-manager config server 10.3.102.99!mgcpmgcp call-agent ccm service-type mgcp version 0.1mgcp dtmf-relay voip codec all mode out-of-bandmgcp rtp unreachable timeout 1000 action notifymgcp modem relay voip mode nse redundancy gw-controlled
mgcp package-capability rtp-packageno mgcp package-capability res-packagemgcp package-capability sst-packageno mgcp package-capability fxr-packagemgcp package-capability pre-packageno mgcp timer receive-rtcpmgcp sdp simplemgcp fax t38 inhibitno mgcp fax-relay sg3-to-g3mgcp rtp payload-type g726r16 static!mgcp profile default!dial-peer voice 2000 voipdestination-pattern 2...session target ipv4:10.2.109.104!dial-peer voice 3000 voipdestination-pattern 3...modem relay nse codec g711ulaw gw-controlledsession protocol sipv2session target ipv4:10.2.109.104!dial-peer voice 2 potsincoming called-number 2...no digit-stripport 1/1:23!dial-peer voice 3 potsincoming called-number 3...no digit-stripport 1/0:23!dial-peer voice 5000 voip!dial-peer voice 10001 pots!dial-peer voice 10002 voip!dial-peer voice 1000 pots!dial-peer voice 6000 pots!!line con 0exec-timeout 0 0line aux 0line vty 0 4exec-timeout 0 0password lablogin!scheduler allocate 20000 1000ntp clock-period 17180156ntp server 10.2.0.1 prefer!endCisco Modem Relay Configured on the VoIP Dial Peer: Example
In this example, dial peer 2000 is configured with modem relay enabled, the G.711 a-law codec specified, and redundant packets enabled:
version 12.3service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname Router!boot-start-markerboot system flash:c2691-ipvoice-mz.cisco_0224boot-end-marker!logging buffered 100000 debuggingenable password lab!no aaa new-model!resource manager!memory-size iomem 25clock timezone PST -8clock summer-time PDT recurringno network-clock-participate slot 1voice-card 1codec complexity highdspfarm!ip subnet-zeroip cef!no ip dhcp use vrf connected!no ip domain lookupno ftp-server write-enable!voice service voipfax protocol pass-through g711ulawsip!controller T1 1/0framing sflinecode ami!controller T1 1/1framing sflinecode ami!interface FastEthernet0/0ip address 10.2.109.104 255.255.0.0duplex autospeed auto!interface FastEthernet0/1no ip addressshutdownduplex autospeed auto!ip default-gateway 10.2.0.1ip classlessip route 10.0.0.0 255.255.255.255 10.2.0.1!no ip http server!control-plane!dial-peer voice 2000 voip
modem relay nse codec g711alaw redundancy gw-controlled
fax rate disablefax protocol pass-through g711alaw!line con 0exec-timeout 0 0line aux 0line vty 0 1exec-timeout 0 0password labloginline vty 2 4login!ntp clock-period 17180780ntp server 192.168.254.253 prefer!endAdditional References
The following sections provide references related to Cisco modem relay.
Related Documents
Related Topic Document TitleModem relay configuration information
Cisco IOS Voice Configuration Library, including library preface and glossary, other feature documents, and troubleshooting documentation.
Cisco IOS command references
•
Cisco IOS Debug Command Reference
Cisco MGCP configuration information
Cisco SIP configuration information
Standards
MIB
RFCs
RFC TitleNo new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
Technical Assistance
Command Reference
This section documents the following modified commands:
mgcp modem relay voip mode
To enable named signaling event (NSE) based modem relay mode for VoIP calls on a Media Gateway Control Protocol (MGCP) gateway, use the mgcp modem relay voip mode command in global configuration mode. To disable this function, use the no form of this command.
mgcp modem relay voip mode [nse] codec [g711alaw | g711ulaw] [redundancy] gw-controlled
no mgcp modem relay voip mode
Syntax Description
Command Default
Modem relay in NSE mode is disabled. All modem calls go through as pass-through calls, which are less reliable and use more bandwidth than modem relay calls, provided that pass-through is enabled.
The G.711 mu-law codec is used for upspeeding.
Redundancy is disabled and no duplicate data packets are sent while the gateway is in modem/fax pass-through mode.Command Modes
Global configuration
Command History
Usage Guidelines
The mgcp modem relay voip mode command enables non secure modem relay mode for MGCP VoIP calls. By default, NSE modem relay mode is disabled. This command configures upspeeding, which is needed because modem pass-through is an intermediate step while the gateway switches from handling voice calls to handling modem relay calls.
The mgcp modem relay voip mode nse command is not supported on the TI C2510 digital signal processor (DSP), formerly known as the TI C5510 DSP; only the TI C549 DSP supports negotiation of NSE parameters. If Cisco CallManager is used as the call agent, the mgcp modem relay voip mode nse command is not supported.
Redundancy causes the gateway to generate duplicate (redundant) data packets for fax/modem pass-through calls as per RFC 2198. For these calls to be more reliable, redundant packets transmission is needed to make up for excessive loss of packets in VoIP networks. Even if one of the gateways is configured with redundancy, calls go through. Gateways can handle asymmetric (one-way) redundancy.
To enable secure voice and data calls between Secure Telephone Equipment (STE) and IP-STE endpoints using the state signaling events (SSE) protocol, use the mgcp modem relay voip mode sse command. Before configuring SSE parameters, you must use the mgcp package-capability mdste command to enable modem relay capabilities and SSE protocol support.
The gw-controlled keyword specifies that modem transport parameters are configured directly on the gateway instead of being negotiated by the call agent.
Examples
The following example enables MGCP modem relay and specifies the following: NSE mode for upspeeding, G.711 mu-law codec, packet redundancy, and gateway-controlled for modem traffic during modem pass-through:
Router(config)# mgcp modem relay voip mode nse codec g711ulaw redundancy gw-controlledRelated Commands
modem relay (dial-peer)
To configure modem relay over VoIP for a specific dial peer, use the modem relay command in dial-peer configuration mode. To disable modem relay over VoIP for a specific dial peer, use the no form of this command.
modem relay {nse [payload-type number] codec {g711alaw | g711ulaw} [redundancy] | system} gw-controlled
no modem relay {nse | system}
Syntax Description
Command Default
Cisco modem relay is disabled.
Payload type: 100Command Modes
Dial-peer configuration
Command History
Usage Guidelines
This command applies to VoIP dial peers. Use this command to configure modem relay over VoIP for a specific dial peer.
Use the same codec type for the originating and terminating gateway, as follows:
•
T1 requires the G.711 mu-law codec.
•
E1 requires the G.711 a-law codec.
The system keyword overrides the configuration for the dial peer, and the values from the modem-relay command in voice-service configuration mode for VoIP are used.
When using the voice service voip and modem relay nse commands on a terminating gateway to globally set up modem relay with NSEs, you must also ensure that each incoming call will be associated with a VoIP dial peer to retrieve the global fax or modem configuration. You associate calls with dial peers by using the incoming called-number command to specify a sequence of digits that incoming calls can match. You can ensure that all calls will match at least one dial peer by using the following commands:
Router(config)# dial-peer voice tag voipRouter(config-dial-peer)# incoming called-number .Examples
The following example shows Cisco modem relay configured for a specific dial peer using the G.711 mu-law codec and enabling redundancy and gateway-controlled negotiation parameters:
Router(config-dial-peer)# modem relay nse codec g711ulaw redundancy gw-controlledRelated Commands
modem relay (voice-service)
To configure modem relay over VoIP for all connections, use the modem relay command in voice-service configuration mode. To disable modem relay over VoIP for all connections, use the no form of this command.
modem relay nse [payload-type number] codec {g711ulaw | g711alaw}
[redundancy[maximum-sessions value]] gw-controlledno modem relay nse
Syntax Description
Command Default
Cisco modem relay is disabled.
Payload type: 100.Command Modes
Voice-service configuration
Command History
Usage Guidelines
Use this command to configure modem relay over VoIP. The default behavior for this command is no modem relay. Configuration of modem relay for VoIP dial peers via the modem relay dial-peer configuration command overrides this voice-service command for the specific VoIP dial peer on which the dial-peer command is configured.
Use the same payload-type number for both the originating and terminating gateways.
Use the same codec type for the originating and terminating gateway, as follows:
•
T1 requires the G.711 mu-law codec.
•
E1 requires the G.711 a-law codec.
The maximum-sessions keyword is an optional parameter for the modem relay command. This parameter determines the maximum number of redundant, simultaneous modem relay sessions. The recommended value for the maximum-sessions keyword is 16. The value can be set from 1 to 10000. The maximum-sessions keyword applies only if the redundancy keyword is used.
When using the voice service voip and modem relay nse commands on a terminating gateway to globally set up modem relay with NSEs, you must also ensure that each incoming call will be associated with a VoIP dial peer to retrieve the global fax or modem configuration. You associate calls with dial peers by using the incoming called-number command to specify a sequence of digits that incoming calls can match. You can ensure that all calls will match at least one dial peer by using the following commands:
Router(config)# dial-peer voice tag voipRouter(config-dial-peer)# incoming called-number .Examples
The following example shows Cisco modem relay enabled with NSE payload type 101 using the G.711 mu-law codec, enabling redundancy and gateway-controlled negotiation parameters:
Router(conf-voi-serv)# modem relay nse payload-type 101 codec g711ulaw redundancy maximum-sessions 1 gw-controlledRelated Commands
Command Descriptionincoming called-number
Defines an incoming called number to match a specific dial peer.
modem relay (dial-peer)
Configures modem relay on a specific VoIP dial peer.
Glossary
CM—call menu signal. A V.8 signal transmitted from the call DCE to indicate modulation modes available in the call DCE. CM consists of a repeating sequence of bits, modulated using a V.21 low-band channel. See joint menu signal (JM).
DSMP—Distributed Stream Media Processor. The software component that controls the DSP on behalf of the media service provider that handles conference calls. The DSMP also manages packet transmission and reception in fast switching.
JM—joint menu signal. A V.8 signal transmitted from the answer DCE to indicate modulation modes available jointly in the call and answer DCE. JM consists of a repeating sequence of bits, modulated using a V.21 high-band channel. See call menu signal (CM).
modem pass-through—The transport of modem signals through an IP network using pulse code modulation (PCM)-encoded packets.
modem relay—Modem relay demodulates a modem signal at one voice gateway and passes it as packet data to another voice gateway, where the signal is remodulated and sent to a receiving modem. On detection of the modem answer tone, the gateways switch into modem pass-through mode, and then, if the call menu (CM) signal is detected, the two gateways switch into modem relay mode.
VBD—voice band data. The transport of modem signals over a voice channel of an IP network with the appropriate encoding for modem signals.
Note
See Internetworking Terms and Acronyms for terms not included in this glossary.
Copyright © 2006 Cisco Systems, Inc. All rights reserved.