Downloads |
Table Of Contents
Modem Relay Support on VoIP Platforms
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Cisco 2600 and Cisco 3600 Series Routers
Configuring MGCP Modem Relay for VoIP
Configuring H.323 and SIP Modem Relay for VoIP Globally
Configuring H.323 and SIP Modem Relay for VoIP for a Specific Dial Peer
Verifying Modem Relay over VoIP
Troubleshooting Modem Relay over VoIP
Monitoring and Maintaining Modem Relay over VoIP
Modem Relay for a Cisco AS5300 Using H.323
Modem Relay for a Cisco 2650 Using H.323 CAS
Modem Relay for a Cisco 3810 Using H.323 and ISDN PRI
Modem Relay for a Cisco 3640 Using MGCP and CAS
Modem Relay on the Cisco AS5300 Using SIP (Originating Gateway)
Modem Relay on the Cisco AS5300 Using SIP (Terminating Gateway)
mgcp modem relay voip gateway-xid
mgcp modem relay voip sprt retries
Modem Relay Support on VoIP Platforms
Feature History
12.2(11)T
This feature was introduced on the Cisco 2600, Cisco 2691, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 3725, Cisco 3745, Cisco 7200, and Cisco AS5300.
This document describes the Modem Relay Support on VoIP Platforms feature and contains the following sections:
•
Supported Standards, MIBs, and RFCs
Feature Overview
The Modem Relay Support on VoIP Platforms feature provides support for modem connections across traditional time division multiplexing (TDM) networks. When service providers implement VoIP, they sometimes cannot separate fax or data traffic from voice traffic. These carriers that aggregate voice traffic over VoIP infrastructures require service offerings to carry fax and data as easily as voice.
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 passthrough mode and then, if the call menu (CM) signal is detected, the two gateways switch into modem relay mode.
There are two ways to transport modem traffic over VoIP networks:
•
•
In this implementation, the call starts out as a voice call, then switches into modem passthrough mode, and then into modem relay mode.
This feature significantly reduces the effects that dropped packets, latency and jitter have on the modem session. Compared to modem passthrough, it also reduces the amount of bandwidth used.
Primary applications for this feature are transport of modem dial-up traffic over IP networks.
Modem Tone Detection and Signaling
This implementation of modem relay supports V.34 modulation and the V.42 error correction and link layer protocol with maximum transfer rates of upto 33.6 kbps. It forces higher-rate modems to train down to the supported rates. Signaling support includes the session initiation protocol (SIP), MGCP/SGCP, and H.323:
•
–
–
–
•
–
–
Relay Switchover
When the gateways detect a data modem, both the originating gateway and the terminating gateway switch to modem passthrough mode. This includes the following elements:
•
•
•
•
•
At the end of the modem call, the voice ports revert to the previous configuration and the digital signal processors (DSPs) switch back to the state before switchover. You can configure the codec by selecting the g711alaw or g711ulaw option of the codec command.
Figure 1 Modem Relay over VoIP Scenario
Controlled Redundancy
You can enable payload redundancy so that the modem passthrough over VoIP switchover causes the gateway to send redundant packets. Redundancy can be enabled in one or both of the gateways. When only a single gateway is configured for redundancy, the other gateway receives the packets correctly, but does not produce redundant packets.
Note
Packet Size
When redundancy is enabled, 10-ms sample-sized packets are sent. When redundancy is disabled, 20-ms sample-sized packets are sent.
Clock Slip Buffer Management
When the gateways detect a data modem, both the originating gateway and the terminating gateway switch from dynamic jitter buffers to static jitter buffers of 200-ms depth. The switch from dynamic to static is designed to compensate for Public Switched Telephone Network (PSTN) clocking differences at the originating and terminating gateways. When the modem call is concluded, the voice ports revert to dynamic jitter buffers.
Benefits
The Modem Relay Support on VoIP Platforms feature offers the following benefits:
•
•
•
•
Restrictions
•
•
•
•
•
Related Features and Technologies
For an overview of VoIP and information about Cisco VoIP features, refer to the Cisco IOS Voice, Video, and Fax Configuration Guide, Cisco IOS Release 12.2.
For a complete overview of the Service Assurance Agent (SAA), refer to the document, Network Monitoring Using Cisco Service Assurance Agent.
For an overview of the session initiation protocol, refer to the Guide to Cisco Systems VoIP Infrastructure Solution for SIP.
Related Documents
•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fvvfax_c/index.htm•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/multi_r/index.htm•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t3/dtmodptr.htm•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121sup/121dsqcg/index.htm•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120xr/mgcp1206.pdf•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t3/dtsipgv2.htm•
http://www.cisco.com/univercd/cc/td/doc/product/voice/sipsols/biggulp/bgsipov.htmSupported Platforms
For Cisco IOS Release 12.2(11)T, the following platforms are suported:
•
•
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that are supported on specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
Availability of Cisco IOS Software Images
Platform support for particular Cisco IOS software releases is dependent on the availability of the software images for those platforms. Software images for some platforms may be deferred, delayed, or changed without prior notice. For updated information about platform support and availability of software images for each Cisco IOS software release, refer to the online release notes or, if supported, Cisco Feature Navigator.
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
No new MIBs are supported by this feature.
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
RFCs
No new or modified RFCs are supported by this feature.
Prerequisites
•
•
Configuration Tasks
This section provides the necessary tasks to configure modem relay for VoIP using MGCP, H.323, or SIP.
Note
•
•
•
•
Tip
Configuring Codec Complexity
The following configuration task tables are for the Cisco 2600 , Cisco 3600, and Cisco 7200 routers.
For the Cisco AS5300 access server, codec complexity is determined by the VCWare code that is loaded on the voice feature card (VFC). For modem relay support, the VFC must be loaded with high-complexity code.
Cisco 2600 and Cisco 3600 Series Routers
To configure high codec complexity for the Cisco 2600 and Cisco 3600 series routers on the originating and terminating gateways, follow these steps:
Cisco 7200 Series Routers
On the Cisco 7200 series routers, codec complexity is configured on the DSP interface.
Note
To configure codec complexity on the DSP interface, follow the steps below, beginning in privileged EXEC mode:
The following high complexity codecs are supported for modem relay using MGCP and H.323:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
The following high complexity codecs are supported for modem relay using SIP:
•
•
•
•
•
•
Configuring MGCP Modem Relay for VoIP
For MGCP, the parameters are negotiated between the two gateways and, if set differently, are adjusted for compatibility during negotiation.
Any MGCP command is applicable to the entire gateway. For MGCP calls, dial peers do not affect call handling because call agent takes care of the call routing. When configured, the following CLI commands affect MGCP calls only and not H.323 calls. H.323 and MGCP CLIs must be configured separately. Use the commands in the table below in global configuration mode.
To configure MGCP modem relay for VoIP using PRI, follow steps 1 to 4.
To configure MGCP modem relay for VoIP using CAS, follow steps 1 to 7.
To change modem relay parameters from their default values, follow steps 8 to 10.
: .
This example shows configuring MGCP modem relay for VoIP:
mgcpmgcp modem relay voip mode nse codec g711ulaw redundancymgcp call-agent 209.165.200.225 2000 service-type mgcp version 0.1mgcp tse payload 98mgcp modem relay voip latency 100mgcp modem relay voip sprt retries 15mgcp modem relay voip gw-xid compress forward dictionary 1020 string-length 30Configuring H.323 and SIP Modem Relay for VoIP Globally
Note
H.323 cannot negotiate the value of payload-type for NSE packets. Configure the same value on both gateways, 100 by default.
For H.323 and SIP configurations, modem relay can be configured at two levels:
•
•
The two configuration tasks can be used separately or together. If both are configured, the dial-peer configuration takes precedence over and thus overrides the global configuration. Consequently, a call matching a specific dial peer first tries to apply the modem relay configuration on the dial peer. Then, if a specific dial peer is not configured, the router use the global configuration. This can ease the configuration burden for users. The configuration for modem relay can be made just once on a global basis. Of course, if finer granularity is desired—so that different modem relay or passthrough configurations are used for different calls on the gateway—you must use dial-peer configuration. The default dial-peer configuration is modem relay system, which tells the gateway to use the parameters configured at the global level. Because this is the default behavior, modem relay system does not show up in show running configuration command output.
When using the voice service voip and modem relay nse commands on a terminating gateway to globally set up fax or 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 .To configure modem relay over VoIP for all connections (global) of a Cisco AS5300 gateway, use the following commands beginning in global configuration mode:
Configuring H.323 and SIP Modem Relay for VoIP for a Specific Dial Peer
You can configure H.323 and SIP modem relay over VoIP on a specific dial peer in the following two ways:
•
•
The default behavior for the voice-service configuration mode is no modem relay. This default behavior implies that modem relay is disabled for all dial peers on the gateway by default.
To enable modem relay on the VoIP dial peers on both the originating and terminating gateway, configure modem relay globally or explicitly on the dial peer.
For modem relay to operate, you must define VoIP dial peers on both gateways to match the call, for example, by using a destination pattern. The modem relay parameters associated with those dial peers then will apply to the call.
Note
To configure modem relay over VoIP for a specific dial peer, use the following commands beginning in global configuration mode:
The example here shows configuring modem relay in dial peer mode.
voice service voipmodem relay nse codec g711ulaw redundancydial-peer voice 12 voipmodem relay nse codec g711ulaw redundancyVerifying Modem Relay over VoIP
To verify that modem relay over VoIP is enabled, perform the following steps:
Step 1
Step 2
Troubleshooting Modem Relay over VoIP
You might be able to determine why the modem relay is not working correctly by viewing the gateway digital signal processor (DSP) modem-relay termination codes that display when the debug hpi all command is used. The DSP-to-host messages for the modem relay termination indicate the modem relay session termination time, physical or link layer, and other probable causes of disconnection. On receiving this indication from the DSP, the host can disconnect the call or place the channel in modem passthrough state.
Tip
–
–
–
–
Monitoring and Maintaining Modem Relay over VoIP
To monitor and maintain modem relay over VoIP, use the following commands in privileged EXEC mode:
Configuration Examples
This section provides the following configuration examples:
•
•
•
•
•
•
Modem Relay for a Cisco AS5300 Using H.323
The following example shows a sample configuration for H.323 modem relay over VoIP for the Cisco AS5300 universal access server:
version 12.1service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!voice service voipmodem relay nse codec g711ulaw redundancy maximum-session 5!resource-pool disable!ip subnet-zeroip ftp source-interface Ethernet0ip ftp username labip ftp password labno ip domain-lookup!isdn switch-type primary-5esscns event-service server!mta receive maximum-recipients 0!controller T1 0framing esfclock source line primarylinecode b8zspri-group timeslots 1-24!controller T1 1shutdownclock source line secondary 1!controller T1 2shutdown!controller T1 3shutdown!interface Ethernet0ip address 10.165.201.159no ip route-cacheno ip mroute-cache!interface Serial0:23no ip addressencapsulation pppip mroute-cacheno logging event link-statusisdn switch-type primary-5essisdn incoming-voice modemno peer default ip addressno fair-queueno cdp enableno ppp lcp fast-start!interface FastEthernet0ip address 10.165.201.159 255.0.0.0no ip route-cacheno ip mroute-cacheload-interval 30duplex fullspeed autono cdp enable!ip classlessip route 10.165.201.159.255.0.0 1.1.1.1no ip http server!voice-port 0:D!dial-peer voice 1 potsincoming called-number 55511..destination-pattern 020..direct-inward-dialport 0:Dprefix 020!dial-peer voice 2 voipincoming called-number 020..destination-pattern 55511..modem relay nse codec g711ulaw redundancysession target ipv4:26.0.0.2!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4login!endModem Relay for a Cisco 2650 Using H.323 CAS
version 12.2no service single-slot-reload-enableservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname k-262!no logging bufferedlogging rate-limit console 10 except errors!voice-card 1codec complexity highdspfarm!ip subnet-zero!no ip dhcp-client network-discoverylcp max-session-starts 0!voice service voiph323call start slowmodem relay nse codec g711ulaw redundancy!dial-peer voice 4000 voipdestination-pattern 4......session target ipv4:10.2.00.86playout-delay maximum 300controller T1 1/0framing esflinecode b8zscablelength long gain36 -15dbds0-group 1 timeslots 1 type e&m-wink-start!controller T1 1/1shutdownframing esfclock source internallinecode ami!interface FastEthernet0/0ip address 10.165.201.159 255.255.0.0duplex autospeed autointerface Serial0/0no ip addressshutdownip classlessip route 0.0.0.0 0.0.0.0 1.2.0.1ip http servervoice-port 1/0:1!no mgcp timer receive-rtcp!mgcp profile default!dial-peer cor custom!!dial-peer voice 4201 potsdestination-pattern 4201000port 1/0:1!!line con 0transport input noneline aux 0line vty 0 4loginline vty 5 15login!endModem Relay for a Cisco 3810 Using H.323 and ISDN PRI
version 12.2no service single-slot-reload-enableno service padno service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname k-gw1!no logging bufferedlogging rate-limit console 10 except errors!network-clock base-rate 56kip subnet-zero!no ip finger!no ip dhcp-client network-discoveryisdn switch-type primary-5essisdn voice-call-failure 0!voice service voiph323call start slowmodem relay nse codec g711ulaw!voice-card 0codec complexity high!controller T1 0mode atmframing esflinecode b8zscontroller T1 1framing esfclock source internallinecode b8zspri-group timeslots 1-24!interface Ethernet0ip address 209.165.200.225 255.255.0.0interface Serial1:23no ip addressno logging event link-statusisdn switch-type primary-5essisdn incoming-voice voiceno cdp enableslarp_ip_addr retry 1!...ip classlessip route 0.0.0.0 0.0.0.0 1.1.0.1no ip http servercall rsvp-sync!voice-port 1:23!dial-peer voice 3001 potsdestination-pattern 30.....direct-inward-dialport 1:23!dial-peer voice 400 voipdestination-pattern 4......session target ipv4:1.2.00.86playout-delay maximum 300line con 0transport input noneline aux 0line 2 3line vty 0 4loginModem Relay for a Cisco 3640 Using MGCP and CAS
!version 12.2no service single-slot-reload-enableservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname uut1-3640!logging rate-limit console 10 except errors!voice-card 3codec complexity high!ip subnet-zero!no ip dhcp-client network-discoverylcp max-session-starts 0!controller T1 3/0framing esfclock source internallinecode b8zsds0-group 0 timeslots 1 type e&m-immediate-startds0-group 1 timeslots 2 type e&m-immediate-startcontroller T1 3/1framing sflinecode ami!interface Ethernet0/0ip address 10.165.200.225. 255.255.0.0half-duplex!interface Serial0/0no ip addressshutdownno fair-queue!ip classlessip route 0.0.0.0 0.0.0.0 1.2.0.1ip http serversnmp-server managercall rsvp-sync!voice-port 3/0:0!voice-port 3/0:1mgcpmgcp call-agent 10.3.64.1 service-type mgcp version 0.1mgcp modem relay voip mode nsemgcp modem relay voip gateway-xidno mgcp timer receive-rtcp!mgcp profile default!dial-peer cor custom!dial-peer voice 1001 potsapplication mgcpappport 3/0:0!dial-peer voice 1002 potsapplication mgcpappport 3/0:1!line con 0exec-timeout 0 0transport input noneline aux 0line vty 0 4login!Modem Relay on the Cisco AS5300 Using SIP (Originating Gateway)
show running-configBuilding configuration...Current configuration : 31658 bytes!version 12.2resource-pool disable!ip subnet-zerono ip domain-lookupip host tftps 10.165.200.225ip host tftp 10.165.200.225ip host dir 10.165.200.225!no ip dhcp-client network-discoveryisdn switch-type primary-5ess!voice service voipmodem relay nse codec g711ulaw redundancy!fax interface-type modemmta receive maximum-recipients 1!controller T1 0framing esfclock source line primarylinecode b8zspri-group timeslots 1-24!interface Ethernet0ip address 10.165.201.159.255.0.0!interface FastEthernet0ip address 10.0.0.4 255.255.255.0load-interval 30duplex fullspeed autono cdp enable!voice-port 0:D!voice-port 1:D!no mgcp timer receive-rtcp!mgcp profile default!dial-peer voice 1 potsincoming called-number 5551111destination-pattern 6661111direct-inward-dialport 0:Dprefix 6661111!dial-peer voice 101 voipdescription SIP-testingapplication sessionincoming called-number 6661111destination-pattern 5551111modem relay nse payload-type 101 codec g711ulawmodem relay gateway-xid compress nosession protocol sipv2session target ipv4:10.0.1.3codec g711ulawfax-relay ecm disablefax rate disable!exec-timeout 0 0endModem Relay on the Cisco AS5300 Using SIP (Terminating Gateway)
hostname uut-ter!voice service voipmodem relay nse codec g711ulaw redundancy!fax interface-type modemmta receive maximum-recipients 1!controller T1 0framing esfclock source line primarylinecode b8zspri-group timeslots 1-24!controller T1 1framing esflinecode b8zspri-group timeslots 1-24!interface Ethernet0ip address 10.165.200.225 255.255.0.0no ip route-cacheno ip mroute-cacheload-interval 30!interface Serial0:23no ip addressencapsulation pppip mroute-cacheno logging event link-statusisdn switch-type primary-5essisdn incoming-voice modemno fair-queueno cdp enable!interface FastEthernet0ip address 10.0.1.3 255.255.255.0load-interval 30duplex fullspeed auto!ip default-gateway 1.6.0.1ip classlessip route 10.0.0.0 155.255.255.0 10.0.1.1ip route 10.165.200.225 255.255.255.255 1.6.0.1no ip http server!call rsvp-sync!voice-port 0:D!voice-port 1:D!voice-port 2:D!no mgcp timer receive-rtcp!mgcp profile default!dial-peer voice 1 potsincoming called-number 6661111destination-pattern 5551111direct-inward-dialport 0:Dprefix 5551111!dial-peer voice 101 voipdescription SIP-testingapplication sessionincoming called-number 5551111destination-pattern 6661111modem relay nse payload-type 101 codec g711ulawmodem relay gateway-xid compress nosession protocol sipv2session target ipv4:10.0.0.4codec g711ulawfax-relay ecm disablefax rate disable!line con 0exec-timeout 0 0line aux 0line vty 0 4exec-timeout 0 0password 7 09404F0Blogin local!no scheduler max-task-timescheduler interval 1000endCommand Reference
This section documents new and modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.
New Commands:
•
•
Modified Commands:
debug hpi all
To view the gateway DSP modem relay termination codes, use the debug hpi all command in privileged EXEC mode. To disable the debugging output, use the no form of this command.
debug hpi all
no debug hpi all
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
12.(2)11T
This command was introduced on the Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
Usage Guidelines
Use this command to view gateway DSP modem relay termination codes. The DSP to host messages for the modem relay termination indicate to the host the modem relay session termination time, physical or link layer, and other probable causes for disconnection. On receiving this indication from the DSP, the host can disconnect the call or place the channel in the modem passthrough state.
Examples
A sample output of the debug hpi all command is shown below.
Jan 11 05:29:28.795: packet_len=14 channel_id=609 packet_id=193*Jan 11 05:29:28.795:hpi [0:D:11] hpi_receive_message:tone_detect - Modem CM:*Jan 11 05:29:28.795: packet_len=14 channel_id=609 packet_id=193*Jan 11 05:29:28.795:hpi [0:D:11] hpi_inband_det_ctrl:*Jan 11 05:29:28.795: packet_len=16 channel_id=8801 packet_id=111 signal_type=2 mode=0*Jan 11 05:29:28.795:hpi [0:D:11] hpi_gen_peer_to_peer:rtp:*Jan 11 05:29:28.795: packet_len=22 channel_id=8801 packet_id=103event 203, volume 0x0, duration 0x0disable_redundancy 0, redundancy_interval 20ssrc_hi 0, ssrc_lo 0, payload_type 100*Jan 11 05:29:28.835:hpi [0:D:11] hpi_receive_message:sent peer-to-peer message*Jan 11 05:29:28.947:hpi [0:D:11] hpi_idle_service:*Jan 11 05:29:28.947: packet_len=8 channel_id=8801 packet_id=68*Jan 11 05:29:28.947:hpi [0:D:11] hpi_open_service:setting codec 34*Jan 11 05:29:29.499:hpi [0:D:11] hpi_modemrelay_mode:Role 0, Debug_flags 0x0 latency=200 retries=12 gw_xid=1 dict_size=1024 string_len=32 compress_dir=3*Jan 11 05:29:39.559:hpi [0:D:11] hpi_receive_message:modem_relay_msg:*Jan 11 05:29:39.559: packet_len=34 channel_id=609 packet_id=123function_code=128 CONNECTED. phys=1, ec=1, Modem dict. size=2048, string length=32, compression dir=3,Negotiated dict. size=1024, string length=32,compression dir=3,local Rx/Tx =26400/28800, remote Rx/Tx =33600/31200Related Commands
To view modem relay network errors.
To view the events that may cause failure of the modem relay network.
debug modem relay errors
To view modem relay network errors, use the debug modem relay errors command in privileged EXEC mode. To disable the debugging output, use the no form of this command.
debug modem relay [call-identifier call-setup-time call-index] errors
no debug modem relay [call-identifier call-setup-time call-index] errors
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
12.2(11)T
This command was introduced on the Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
Usage Guidelines
In a stable modem relay network, this command produces little output.
Examples
A sample output of the debug modem relay errors command is shown below.
The output shows the sequence number of the packet, timestamp, direction, layer, and payload-bytes, followed by each byte of the payload in hexadecimal.
Jan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 28 tm 11944 OUT ERR, pb=12, payload: 00 06 00 00 00 00 00 07 00 00 01 DE*Jan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 29 tm 11944 OUT ERR, pb=12, payload: 00 06 00 00 00 00 00 04 00 00 00 BE*Jan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 30 tm 11944 OUT ERR, pb=12, payload: 00 06 00 00 00 00 00 05 FF FF FF FDRelated Commands
To view gateway DSP modem relay termination codes.
To view the events that may cause failure of the modem relay network.
debug modem relay events
To view the events that may cause failure of the modem relay network, use the debug modem relay events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem relay [call-identifier call-setup-time call-index] events
no debug modem relay [call-identifier call-setup-time call-index] events
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
12.2(11)T
This command was introduced on the Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
Usage Guidelines
In a stable modem relay network, this command produces little output.
Examples
A sample output of the debug modem relay events command is shown below.
The output shows the sequence number of the packet, timestamp, direction, layer, and payload-bytes, followed by each byte of the payload in hexadecimal.
Jan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 28 tm 11944 OUT EVNT, pb=12, payload: 00 06 00 00 00 00 00 07 00 00 01 DE*Jan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 29 tm 11944 OUT EVNT, pb=12, payload: 00 06 00 00 00 00 00 04 00 00 00 BE*Jan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 30 tm 11944 OUT EVNT, pb=12, payload: 00 06 00 00 00 00 00 05 FF FF FF FDRelated Commands
To view gateway DSP modem relay termination codes.
To view modem relay network errors.
debug modem relay physical
To view modem relay physical layer packets, use the debug modem relay physical command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem relay [call-identifier call-setup-time call-index] physical
no debug modem relay [call-identifier call-setup-time call-index] physical
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
12.2(11)T
This command was introduced on the Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
Usage Guidelines
Disable console logging and use buffered logging before using this command. Using this command generates a large volume of debugs, which can affect router performance.
Examples
A sample output of the debug modem relay physical command is shown below.
The output shows the sequence number of the packet, timestamp, direction, layer, and payload-bytes, followed by each byte of the payload in hexadecimal.
Jan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 28 tm 11944 OUT PHYS, pb=12, payload: 00 06 00 00 00 00 00 07 00 00 01 DE*Jan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 29 tm 11944 OUT PHYS, pb=12, payload: 00 06 00 00 00 00 00 04 00 00 00 BE*Jan 11 05:35:09.119:ModemRelay pkt[0:D:11]. sqn 30 tm 11944 OUT PHYS, pb=12, payload: 00 06 00 00 00 00 00 05 FF FF FF FDRelated Commands
To view gateway DSP modem relay termination codes.
To view modem relay network errors.
debug modem relay packetizer
To view events occuring in the modem relay packetizer module, use the debug modem relay packetizer command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem relay [call-identifier call-setup-time call-index] packetizer
no debug modem relay [call-identifier call-setup-time call-index] packetizer
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
12.2(11)T
This command was introduced on the Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
Usage Guidelines
Disable console logging and use buffered logging before using this command. Using this command generates a large volume of debugs, which can affect router performance.
Examples
A sample output of the debug modem relay packetizer command is shown below.
The output shows the sequence number of the packet, timestamp, direction, layer, and payload-bytes, followed by each byte of the payload in hexadecimal.
Jan 11 05:33:33.715:ModemRelay pkt[0:D:11]. sqn 8 tm 47610 IN PKTZR, pb=7, payload: 82 38 00 18 03 01 87*Jan 11 05:33:33.727:ModemRelay pkt[0:D:11]. sqn 9 tm 47616 OUT PKTZR, pb=7, payload: 82 20 00 18 03 01 47*Jan 11 05:33:35.719:ModemRelay pkt[0:D:11]. sqn 10 tm 49614 IN PKTZR, pb=7, payload: 82 39 00 18 03 01 87Related Commands
To view gateway DSP modem relay termination codes.
To view modem relay network errors.
debug modem relay sprt
To view modem relay Simple Packet Relay Transport (SPRT) protocol packets, use the debug modem relay sprt command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem relay [call-identifier call-setup-time call-index] sprt
no debug modem relay [call-identifier call-setup-time call-index] sprt
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
12.2(11)T
This command was introduced for Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
Usage Guidelines
Disable console logging and use buffered logging before using this command. Using this command generates a large volume of debugs, which can affect router performance.
Examples
A sample output of the debug modem relay sprt command is shown below.
The output shows the sequence number of the packet, timestamp, direction, layer, and payload-bytes, followed by each byte of the payload in hexadecimal.
Jan 11 05:37:16.151:ModemRelay pkt[0:D:11]. sqn 34 tm 7910 OUT SPRT, pb=4, payload: 02 00 03 71*Jan 11 05:37:16.295:ModemRelay pkt[0:D:11]. sqn 35 tm 8048 IN SPRT, pb=13, payload: 02 00 01 F1 F7 7E FD F5 90 F3 3E 90 55*Jan 11 05:37:16.303:ModemRelay pkt[0:D:11]. sqn 36 tm 8060 IN SPRT, pb=6, payload: 02 00 01 41 04 00Related Commands
To view gateway DSP modem relay termination codes.
To view modem relay network errors.
debug modem relay udp
To view events occurring in the User Datagram Protocol (UDP) stack, use the debug modem relay udp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem relay [call-identifier call-setup-time call-index] udp
no debug modem relay [call-identifier call-setup-time call-index] udp
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
12.2(11)T
This command was introduced on the Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
Usage Guidelines
Disable console logging and use buffered logging before using this command. Using this command generates a large volume of debugs, which can affect router performance.
Examples
A sample output of the debug modem relay udp command is shown below.
The output shows three UDP packets related to modem relay. In the sample output, OUT or IN represent packet direction, UDP indicates the specific layer that reported the packet.
Jan 1 03:39:29.407:ModemRelay pkt[0:D (4)]. sqn 61 tm 3060 OUT UDP, pb=6, payload: 80 00 00 00 00 00*Jan 1 03:39:29.471:ModemRelay pkt[0:D (4)]. sqn 62 tm 3120 IN UDP, pb=6, payload: 40 00 00 00 00 00*Jan 1 03:39:29.471:ModemRelay pkt[0:D (4)]. sqn 63 tm 3120 IN UDP, pb=6, payload: 80 00 00 00 00 00Related Commands
To view gateway DSP modem relay termination codes.
To view modem relay network errors.
debug modem relay v42
To view events occuring in the V.42 layer, use the debug modem relay v42 command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug modem relay [call-identifier call-setup-time call-index] v42
no debug modem relay [call-identifier call-setup-time call-index] v42
Syntax Description
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
12.2(11)T
This command was introduced on the Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
Usage Guidelines
Disable console logging and use buffered logging before using this command. Using this command generates a large volume of debugs, which can affect router performance.
Examples
A sample output of the debug modem relay v42 command is shown below.
The output shows the sequence number of the packet, timestamp, direction, layer, and payload-bytes, followed by each byte of the payload in hexadecimal.
Jan 11 05:42:08.715:ModemRelay pkt[0:D:13]. sqn 3 tm 10104 OUT V42, pb=43, payload: 03 AF 82 80 00 13 03 03 8A 89 00 05 02 03 E0 06 02 03 E0 07 01 08 08 01 08 F0 00 0F 00 03 56 34 32 01 01 03 02 02 04 00 03 01 20*Jan 11 05:42:08.847:ModemRelay pkt[0:D:13]. sqn 4 tm 10236 IN V42, pb=2, payload: 03 7FRelated Commands
To view gateway DSP modem relay termination codes.
To view modem relay network errors.
mgcp modem relay voip mode
To enable modem relay mode support in a gateway for Media Gateway Control Protocol (MGCP) Voice over IP (VoIP) calls, 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] | redundancy]
no mgcp modem relay voip mode
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
12.2(11)T
This command was introduced on the Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
Usage Guidelines
This command enables the modem relay mode for MGCP VoIP calls. By default, modem relay mode is enabled. The remaining part of the CLI is for upspeeding. The keywords in the remaining part of the CLI are included because modem passthrough is an intermediate step while switching from voice calls to modem relay calls.
The mgcp modem relay voip mode command enables MGCP modem relay.
•
•
•
Even if one of the gateways is configured with "redundancy," the calls will go through. DSPs can handle asymmetric (one way) redundancy.
Examples
The following example enables MGCP modem relay and specifies NSE mode for upspeeding, codec g711ulaw, and packet redundancy for modem traffic during modem passthrough phase:
mgcp modem relay voip mode nse codec g711ulaw redundancyRelated Commands
mgcp tse payload
To enable telephony signaling events (TSEs) for communications between gateways as required for modem relay over VoIP using Media Gateway Control Protocol (MGCP), use the mgcp tse payload command in global configuration mode. To disable TSEs, use the no form of this command.
mgcp tse payload payload-value
no mgcp tse payload
Syntax Description
payload-value
Valid range is from 98 through 119. If the value is not configured, the default of 100 is used.
Defaults
Default payload value is 100.
Command Modes
Global configuration
Command History
Usage Guidelines
This command must be enabled for modem-relay over VoIP using MGCP.
Telephony service events (TSE) are also known as named service events (NSEs). TSE is used to communicate telephony events between gateways . They are RTP packets with different payload values that indicate if the packet contains a TSE. Both gateways should have the same payload value field.
Examples
The following example sets the payload value at 98 for the MGCP telephony signaling events:
mgcp tse payload 98Related Commands
mgcp modem relay voip gateway-xid
To set in-band negotiation of compression parameters between two VoIP gateways using Media Gateway Control Protocol (MGCP), use the mgcp modem relay voip gateway-xid command in global configuration mode. To disable this function, use the no form of this command.
mgcp modem relay voip gateway-xid [compress {backward | both | forward | no} [dictionary value [string-length value] | string-length value] | dictionary value [string-length value] | string-length value ]
no mgcp modem relay voip gateway-xid
Syntax Description
Defaults
Enabled
Command Modes
Global configuration
Command History
12.2(11)T
This command was introduced on the Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
Usage Guidelines
XID negotition is a DSP-specific feature used in modem relay. The mgcp modem relay voip gateway-xid command enables this negotiation feature. By default it is enabled.
The parameters compress and dictionary and string-length are DSP-specific and related to xid negotiation. If the mgcp modem relay voip gateway-xid command is disabled, they are all irrelevant. The application (MGCP or H.323) just passes these configured values to the DSPs, and it is the DSP that requires them.
Examples
The following example enables in-band negotiation of compression parameters on the VoIP gateway, with compression in both directions, and dictionary size of 1024 and string length of 32 for the compression algorithm:
mgcp modem relay voip gateway-xid compress both dictionary 1024 string-length 32Related Commands
mgcp modem relay voip latency
To optimize the modem relay transport protocol and the estimated one-way delay across the IP network using Media Gateway Control Protocol (MGCP), use the mgcp modem relay voip latency command in global configuration mode. To disable this function, use the no form of this command.
mgcp modem relay voip latency value
no mgcp modem relay voip latency
Syntax Description
Defaults
Default value is 200.
Command Modes
Global configuration
Command History
12.2(11)T
This command was introduced for the Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
Usage Guidelines
Use this command to adjust the retransmission timer of the SPRT protocol, if required, by setting this value to the estimated one-way delay (in milliseconds) across the IP network. Changing this value may affect the throughput or delay characteristics of the modem relay call. The default value of 200 does not need to be changed for most networks.
Examples
The following example sets the estimated one-way delay across the IP network to 100 ms.
mgcp modem relay voip latency 100Related Commands
mgcp modem relay voip sprt retries
To set the maximum number of times that the SPRT protocol tries to send a packet before disconnecting, use the mgcp modem relay voip sprt retries command in global configuration mode. To disable this function, use the no form of this command.
mgcp modem relay voip sprt retries value
no mgcp modem relay voip sprt retries
Syntax Description
retries value
The maximum number of times that the SPRT protocol tries to send a packet before disconnecting. Range: 6 to 30. Default: 12.
Defaults
Default value is 12.
Command Modes
Global configuration
Command History
12.2(11)T
This command was introduced on the Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
Usage Guidelines
Use this command to set the maximum number of times that the Simple Packet Relay Transport (SPRT) protocol tries to send a packet before disconnecting.
Examples
The following example sets the maximum number of times that the SPRT protocol tries to send a packet before disconnecting to 15:
mgcp modem relay voip sprt retries 15Related Commands
modem relay (dial-peer)
To configure modem relay over Voice over IP (VoIP) for a specific dial peer, use the modem relay command in dial-peer configuration mode. To disable modem relay for a specific dial peer, use the no form of this command.
modem relay {nse {[payload-type number] codec {g711alaw | g711ulaw} [redundancy]} | system}
no modem relay { nse | system}
Syntax Description
Defaults
Disabled
Command Modes
Dial-peer configuration
Command History
12.2(11)T
This command was introduced for the Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
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. g711ulaw codec is required for T1, and g711alaw codec is required for E1.
The redundancy keyword is an optional parameter for sending redundant packets for modem traffic during the passthrough phase.
When the system keyword is enabled, the following parameters are not available: nse, payload-type, codec, and redundancy. 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.
Examples
The following example shows modem relay over VoIP configured for a specific dial peer in dial-peer configuration mode.
modem relay nse codec g711ulaw redundancyRelated Commands
modem relay (voice-service)
To configure modem relay over VoIP for all connections for the Cisco AS5300, use the modem relay command in voice-service configuration mode. To disable modem relay for all connections, use the no form of this command.
modem relay nse [payload-type number] codec {g711ulaw | g711alaw}
[redundancy] [maximum-sessions value]no modem relay nse
Syntax Description
Defaults
Disabled
Command Modes
Voice-service configuration
Command History
12.2(11)T
This command was introduced for the Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
Usage Guidelines
Use this command to configure modem relay over VoIP for the Cisco AS5300. 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 where the dial-peer command is configured.
The payload type is an optional parameter for the nse keyword. Use the same payload-type number for both the originating gateway and the terminating gateway. The payload-type number can be set from 96 to 119. If you do not specify the payload-type number, the number defaults to 100.
Use the same codec type for both the originating gateway and the terminating gateway. g711ulaw codec is required for T1, and g711alaw codec is required for E1.
The redundancy keyword is an optional parameter for sending redundant packets for modem traffic during the passthrough phase.
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 is 16. The value can be set from 1 through 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 fax or 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 modem relay configuration in voice-service configuration mode for NSE payload type 101 using codec G.711:
modem relay nse payload-type 101 codec g711ulaw redundancy maximum-session 1Related Commands
incoming called-number
Defines an incoming called number to match a specific dial peer.
Configures modem relay on a specific VoIP dial peer.
modem relay gateway-xid
To set in-band negotiation of compression parameters between two VoIP gateways, use the modem relay gateway-xid command in dial-peer or voice-service configuration mode. To disable this function, use the no form of this command.
modem relay gateway-xid {[compress [backward | forward | both | no] ] [ dictionary value] [ string-length value ]}
no modem relay gateway-xid
Syntax Description
Defaults
Enabled
Command Modes
Dial-peer configuration
Voice-service configurationCommand History
12.2(11)T
This command was introduced for the Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
Usage Guidelines
If enabled on both gateways, in-band negotiation of compression parameters occurs between the two VoIP gateways. Inband negotiation occurs between the two DSPs on either side of the network. This is not for negotiation of any parameters, but to decide if there will be a negotiation process. The actual parameters are negotiated by the in-band negotiation process and not by the host at a later stage, assuming the two hosts have agreed to do this negotiation, by having their gateway-xid enabled.
The remaining parameters specify the negotiation posture of this gateway in the subsequent inband negotiation step (assuming inband negotiation was agreed on by the two gateways).
xid negotiation is a DSP-specific feature used in modem relay. The modem relay gateway-xid command enables this negotiation feature. By default it is disabled. The parameters compress and dictionary and string-length are DSP-specific and related to xid negotiation. If gateway-xid is disabled, they are all irrelevant. The application passes these configured values to the DSP that needs them.
Examples
The following example enables in-band negotiation of compression parameters on the VoIP gateway, with compression in both directions, and dictionary size of 1024 and string length of 32 for the compression algorithm:
modem relay gateway-xid compress both dictionary 1024 string-length 32Related Commands
modem relay latency
To optimize the modem relay transport protocol and the estimated one-way delay across the IP network, use the modem relay latency command in dial-peer or voice-service configuration mode. To disable this function, use the no form of this command.
modem relay latency value
no modem relay latency
Syntax Description
Defaults
Default value is 200.
Command Modes
Dial-peer configuration
Voice-service configurationCommand History
12.2(11)T
This command was introduced for the Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
Usage Guidelines
Use this command to adjust the retransmission timer of the SPRT protocol, if required, by setting this value to the estimated one-way delay (in milliseconds) across the IP network. Changing this value may affect the throughput or delay characteristics of the modem relay call. The default value of 200 does not need to be changed for most networks.
Examples
The following example sets the estimated one-way delay across the IP network to 100 msec.
Router(config-dial-peer)# modem relay latency 100Related Commands
modem relay sprt retries
To set the maximum number of times that the Simple Packet Relay Transport (SPRT) protocol tries to send a packet before disconnecting, use the modem relay sprt retries command in dial-peer or voice-service configuration mode. To disable this function, use the no form of this command.
modem relay sprt retries value
no modem relay sprt retries
Syntax Description
Defaults
Default value is 12.
Command Modes
Dial-peer configuration
Voice-service configurationCommand History
12.2(11)T
This command was introduced for the Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
Usage Guidelines
Use this dial-peer or voice-service configuration command to set the maximum number of times that the SPRT protocol tries to send a packet before disconnecting.
Examples
The following example sets the maximum number of times that the SPRT protocol tries to send a packet before disconnecting at 15.
modem relay sprt retries 15Related Commands
show call active voice
To show current call information for a call in progress, use the show call active command in privileged EXEC mode.
show call active voice [brief [id value] | compact [duration {less time | more time}] | id value]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Usethis command to display the contents of the active call table. If you use the voice keyword, the active call table displays information about all the voice calls currently connected through the router or access server.
Examples
The following is a brief sample output from the show call active voice brief command:
router# show call active voice brief<ID>:<start>hs.<index> +<connect> pid:<peer_id> <dir> <addr> <state>dur hh:mm:ss tx:<packets>/<bytes> rx:<packets>/<bytes>IP <ip>:<udp> rtt:<time>ms pl:<play>/<gap>ms lost:<lost>/<early>/<late>delay:<last>/<min>/<max>ms <codec>MODEMPASS <method> buf:<fills>/<drains> loss <overall%> <multipkt>/<corrected>last <buf event time>s dur:<Min>/<Max>sFR <protocol> [int dlci cid] vad:<y/n> dtmf:<y/n> seq:<y/n>sig:<on/off> <codec> (payload size)ATM <protocol> [int vpi/vci cid] vad:<y/n> dtmf:<y/n> seq:<y/n>sig:<on/off> <codec> (payload size)Tele <int>:tx:<tot>/<v>/<fax>ms <codec> noise:<l> acom:<l> i/o:<l>/<l> dBmMODEMRELAY info:<rcvd>/<sent>/<resent> xid:<rcvd>/<sent> total:<rcvd>/<sent>/<drops>Proxy <ip>:<audio udp>,<video udp>,<tcp0>,<tcp1>,<tcp2>,<tcp3> endpt:<type>/<manf>bw:<req>/<act> codec:<audio>/<video>tx:<audio pkts>/<audio bytes>,<video pkts>/<video bytes>,<t120 pkts>/<t120 bytes>rx:<audio pkts>/<audio bytes>,<video pkts>/<video bytes>,<t120 pkts>/<t120 bytes>Total call-legs:211E1 :1347833hs.1 +80 pid:50281 Answer 4085260287 activedur 00:00:38 tx:347/14028 rx:336/13640Tele 0:D:5:tx:5070/2340/0ms modem-relay noise:0 acom:0 i/0:0/0 dBmMODEMRELAY info:10/10/0 xid:0/0 total:76/10/011E1 :1347834hs.1 +59 pid:25 Originate 50281 activedur 00:00:39 tx:336/13640 rx:347/12312IP 1.8.84.15:18986 rtt:0ms pl:2380/40ms lost:13/1/0 delay:57/57/70ms g729r8Shown below is a sample output for the show call active voice command:
router# show call active voiceTotal call-legs:2GENERIC:SetupTime=1347833 msIndex=1PeerAddress=40812345677PeerSubAddress=PeerId=50181PeerIfIndex=59LogicalIfIndex=30ConnectTime=1347913CallDuration=00:01:20CallState=4CallOrigin=2ChargedUnits=0InfoType=2TransmitPackets=521TransmitBytes=15072!!SPRTTotalInfoBytesReceived=76SPRTTotalInfoBytesSent=10SPRTPacketDrops=0GENERIC:SetupTime=1347834 msIndex=1PeerAddress=50181PeerSubAddress=PeerId=25PeerIfIndex=58LogicalIfIndex=0ConnectTime=1347893CallDuration=00:01:21CallState=4CallOrigin=1ChargedUnits=0InfoType=2TransmitPackets=515TransmitBytes=14714ReceivePackets=525ReceiveBytes=11244VOIP:ConnectionId[0x99001380 0xBF3411D3 0x800E9165 0x694C2CE8]IncomingConnectionId[0x99001380 0xBF3411D3 0x800E9165 0x694C2CE8]RemoteIPAddress=1.8.84.15RemoteUDPPort=18986RoundTripDelay=0 msSelectedQoS=best-efforttx_DtmfRelay=inband-voiceFastConnect=FALSEAnnexE=FALSESeparate H245 Connection=FALSEH245 Tunneling=FALSESessionProtocol=sipv2SessionTarget=1.8.84.15OnTimeRvPlayout=2380GapFillWithSilence=10 msGapFillWithPrediction=30 msGapFillWithInterpolation=0 msGapFillWithRedundancy=0 msHiWaterPlayoutDelay=70 msLoWaterPlayoutDelay=57 msReceiveDelay=57 msLostPackets=13EarlyPackets=1LatePackets=0VAD = enabledCoderTypeRate=g729r8CodecBytes=20SignalingType=ext-signalCallerName=CallerIDBlocked=FalseTable 2 provides an alphabetical listing of the show call active command fields and a description of each field.
Related Commands
show call history voice
To display the call history table, use the show call history command in privileged EXEC mode.
show call history voice [brief [id value] | compact [duration {less time | more time}] | [id value] | last number]
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display the voice call history table. The call history table contains a listing of all calls connected through this router in descending time order since VoIP was enabled. You can display subsets of the call history table by using specific keywords. To display the last calls connected through this router, use the last keyword, and define the number of calls you want to see with the number argument. To display a truncated version of the call history table, use the brief keyword.
Examples
The following is sample output from the show call history command updated to show modem relay over Voice over IP information:
Router# show call history voiceTotal call-legs:2GENERIC:SetupTime=43003 msIndex=1PeerAddress=50110PeerSubAddress=PeerId=102PeerIfIndex=55LogicalIfIndex=0DisconnectCause=0DisconnectText=ConnectTime=43018DisconnectTime=58646CallDuration=00:02:36CallOrigin=2ChargedUnits=0InfoType=speechTransmitPackets=0TransmitBytes=0ReceivePackets=0ReceiveBytes=0VOIP:ConnectionId[0x29448C7E 0x4F140003 0x0 0x2147B]IncomingConnectionId[0x29448C7E 0x4F140003 0x0 0x2147B]RemoteIPAddress=1.14.82.60RemoteUDPPort=16530RoundTripDelay=0 msSelectedQoS=best-efforttx_DtmfRelay=inband-voiceFastConnect=TRUEAnnexE=FALSESeparate H245 Connection=FALSEH245 Tunneling=FALSESessionProtocol=ciscoSessionTarget=OnTimeRvPlayout=0GapFillWithSilence=0 msGapFillWithPrediction=0 msGapFillWithInterpolation=0 msGapFillWithRedundancy=0 msHiWaterPlayoutDelay=0 msLoWaterPlayoutDelay=0 msReceiveDelay=0 msLostPackets=0EarlyPackets=0LatePackets=0VAD = enabledCoderTypeRate=g711ulawCodecBytes=0cvVoIPCallHistoryIcpif=0SignalingType=casCallerName=50110,Voice/ENACallerIDBlocked=FalseGENERIC:SetupTime=43009 msIndex=2PeerAddress=55250PeerSubAddress=PeerId=101PeerIfIndex=56LogicalIfIndex=54DisconnectCause=10DisconnectText=normal call clearing.ConnectTime=43018DisconnectTime=58647CallDuration=00:02:36CallOrigin=1ChargedUnits=0InfoType=speechTransmitPackets=922TransmitBytes=44779ReceivePackets=1021ReceiveBytes=59857TELE:ConnectionId=[0x29448C7E 0x4F140003 0x0 0x2147B]IncomingConnectionId=[0x29448C7E 0x4F140003 0x0 0x2147B]TxDuration=4790 msVoiceTxDuration=2660 msFaxTxDuration=0 msCoderTypeRate=g711ulawNoiseLevel=0ACOMLevel=0SessionTarget=ImgPages=0CallerName=50110,Voice/ENACallerIDBlocked=FalseSPRTInfoFramesReceived=10SPRTInfoTFramesSent=9SPRTInfoTFramesResent=0SPRTXidFramesReceived=0SPRTXidFramesSent=0SPRTTotalInfoBytesReceived=10SPRTTotalInfoBytesSent=76SPRTPacketDrops=678Table 3 provides an alphabetical listing of the show call history command fields and a description of each field.
show modem relay statistics
To display various statistics for modem relay, use the show modem relay statistics command in privileged EXEC mode.
show modem relay statistics {all | phy | pkt | queue | sprt | timer | v42} [call-identifier call-setup-time call-index]
Syntax Description
Defaults
No statistics are displayed.
Command Modes
Privileged EXEC
Command History
12.2(11)T
This command was introduced for the Cisco 2600, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200, and Cisco AS5300.
Usage Guidelines
Use this command to display various modem relay call statistics, including counts of different types of packets, errors and events, for all modem relay calls.
Display statistics for a specific modem relay call by using the call-identifier keyword and specifying the call setup time and call index of the desired call. Obtain the call setup time and call index values from the SetupTime and Index fields at the start of each call record in the show call active command output.
Examples
Router# show modem relay statistics all call-identifier 43009 1ID:3SPRT Layer Statisticssprt_info_frames_rcvd=10 sprt_xid_frames_rcvd=0sprt_tc0_explicit_acks_rcvd=6 sprt_tc1_explicit_acks_rcvd=122sprt_tc2_explicit_acks_rcvd=126 sprt_destructive_brks_rcvd=0sprt_expedited_brks_rcvd=0sprt_non_expedited_brks_rcvd=0sprt_info_tframes_sent=9 sprt_info_tframes_resent=0sprt_xid_frames_sent=0 sprt_tc0_explicit_acks_sent=8sprt_tc1_explicit_acks_sent=129 sprt_tc2_explicit_acks_sent=132sprt_destructive_brks_sent=0sprt_expedited_brks_sent=0sprt_non_expedited_brks_sent=0sprt_info_tframes_asked_to_consumed=10sprt_info_tframes_consumed=10sprt_info_tframes_failed_to_consume=0sprt_info_bytes_rcvd=10 sprt_info_bytes_sent=76sprt_pkts_dropped_intf_busy=289 sprt_min_rexmit_timeout=500sprt_max_rexmit_timeout=500Queue Statisticssprt_tc1_rcv_qdrops=0 sprt_tc1_xmit_qdrops=0sprt_tc2_rcv_qdrops=0 sprt_tc2_xmit_qdrops=0pktizer_out_qdrops=4 pktizer_in_qdrops=0 v42_xmit_qdrops=0V42 Layer Statisticsvs_chng_dueto_timeouts=0 vs_chng_dueto_rej=0vs_chng_dueto_rnr_resp_f1_set=0 nr_seq_exception=0good_rcvd_lapm_pkts=1385 discarded_rcvd_lapm_pkts=0rejected_rcvd_lapm_pkts=0 v42_rcvd_iframe=9v42_rcvd_rr=1374 v42_rcvd_rnr=0 v42_rcvd_rej=0v42_rcvd_srej=0 v42_rcvd_sabme=0 v42_rcvd_dm=0v42_rcvd_ui=0 v42_rcvd_disc=0 v42_rcvd_ua=1v42_rcvd_frmr=0 v42_rcvd_xid=1 v42_rcvd_test=0v42_rcvd_destructive_brk=0 v42_rcvd_expedited_brk=0v42_rcvd_non_expedited_brk=0 v42_rcvd_brkack=0v42_sent_iframe=10 v42_sent_rr=1464 v42_sent_rnr=0v42_sent_rej=0 v42_sent_srej=0 v42_sent_sabme=1v42_sent_dm=0 v42_sent_ui=0 v42_sent_disc=0v42_sent_ua=0 v42_sent_frmr=0 v42_sent_xid=1v42_sent_test=0 v42_sent_destructive_brk=0v42_sent_expedited_brk=0v42_sent_non_expedited_brk=0v42_sent_brkack=0Physical Layer Statisticsnum_local_retrain=0 num_remote_retrain=0num_local_speed_shift=0 num_remote_speed_shift=0num_sync_loss=0Packetizer Statisticsframes_inprogress=5 good_crc_frames=1385bad_crc_frames=31 frame_aborts=124hdlc_sync_detects=1 hdlc_sync_loss_detects=0bad_frames=0Timer Statisticsxid_timer_cnt=0 sabme_timer_cnt=0 ack_timer_cnt=0chkpnt_timer_cnt=1333Router# show modem relay stat allID:3SPRT Layer Statisticssprt_info_frames_rcvd=10 sprt_xid_frames_rcvd=0sprt_tc0_explicit_acks_rcvd=6 sprt_tc1_explicit_acks_rcvd=155sprt_tc2_explicit_acks_rcvd=158 sprt_destructive_brks_rcvd=0sprt_expedited_brks_rcvd=0sprt_non_expedited_brks_rcvd=0sprt_info_tframes_sent=9 sprt_info_tframes_resent=0sprt_xid_frames_sent=0 sprt_tc0_explicit_acks_sent=8sprt_tc1_explicit_acks_sent=161 sprt_tc2_explicit_acks_sent=165sprt_destructive_brks_sent=0sprt_expedited_brks_sent=0sprt_non_expedited_brks_sent=0sprt_info_tframes_asked_to_consumed=10sprt_info_tframes_consumed=10sprt_info_tframes_failed_to_consume=0sprt_info_bytes_rcvd=10 sprt_info_bytes_sent=76sprt_pkts_dropped_intf_busy=357 sprt_min_rexmit_timeout=500sprt_max_rexmit_timeout=500Queue Statisticssprt_tc1_rcv_qdrops=0 sprt_tc1_xmit_qdrops=0sprt_tc2_rcv_qdrops=0 sprt_tc2_xmit_qdrops=0pktizer_out_qdrops=4 pktizer_in_qdrops=0 v42_xmit_qdrops=0V42 Layer Statisticsvs_chng_dueto_timeouts=0 vs_chng_dueto_rej=0vs_chng_dueto_rnr_resp_f1_set=0 nr_seq_exception=0good_rcvd_lapm_pkts=1910 discarded_rcvd_lapm_pkts=0rejected_rcvd_lapm_pkts=0 v42_rcvd_iframe=9v42_rcvd_rr=1899 v42_rcvd_rnr=0 v42_rcvd_rej=0v42_rcvd_srej=0 v42_rcvd_sabme=0 v42_rcvd_dm=0v42_rcvd_ui=0 v42_rcvd_disc=0 v42_rcvd_ua=1v42_rcvd_frmr=0 v42_rcvd_xid=1 v42_rcvd_test=0v42_rcvd_destructive_brk=0 v42_rcvd_expedited_brk=0v42_rcvd_non_expedited_brk=0 v42_rcvd_brkack=0v42_sent_iframe=10 v42_sent_rr=1988 v42_sent_rnr=0v42_sent_rej=0 v42_sent_srej=0 v42_sent_sabme=1v42_sent_dm=0 v42_sent_ui=0 v42_sent_disc=0v42_sent_ua=0 v42_sent_frmr=0 v42_sent_xid=1v42_sent_test=0 v42_sent_destructive_brk=0v42_sent_expedited_brk=0v42_sent_non_expedited_brk=0v42_sent_brkack=0Physical Layer Statisticsnum_local_retrain=0 num_remote_retrain=0num_local_speed_shift=0 num_remote_speed_shift=0num_sync_loss=0Packetizer Statisticsframes_inprogress=5 good_crc_frames=1910bad_crc_frames=31 frame_aborts=124hdlc_sync_detects=1 hdlc_sync_loss_detects=0bad_frames=0Timer Statisticsxid_timer_cnt=0 sabme_timer_cnt=0 ack_timer_cnt=0chkpnt_timer_cnt=1809Total Modem Relay Call Legs = 1Router# show modem relay stat sprtID:3SPRT Layer Statisticssprt_info_frames_rcvd=10 sprt_xid_frames_rcvd=0sprt_tc0_explicit_acks_rcvd=6 sprt_tc1_explicit_acks_rcvd=177sprt_tc2_explicit_acks_rcvd=180 sprt_destructive_brks_rcvd=0sprt_expedited_brks_rcvd=0sprt_non_expedited_brks_rcvd=0sprt_info_tframes_sent=9 sprt_info_tframes_resent=0sprt_xid_frames_sent=0 sprt_tc0_explicit_acks_sent=8sprt_tc1_explicit_acks_sent=183 sprt_tc2_explicit_acks_sent=187sprt_destructive_brks_sent=0sprt_expedited_brks_sent=0sprt_non_expedited_brks_sent=0sprt_info_tframes_asked_to_consumed=10sprt_info_tframes_consumed=10sprt_info_tframes_failed_to_consume=0sprt_info_bytes_rcvd=10 sprt_info_bytes_sent=76sprt_pkts_dropped_intf_busy=403 sprt_min_rexmit_timeout=500sprt_max_rexmit_timeout=500Total Modem Relay Call Legs = 1Router# show modem relay stat queueID:3Queue Statisticssprt_tc1_rcv_qdrops=0 sprt_tc1_xmit_qdrops=0sprt_tc2_rcv_qdrops=0 sprt_tc2_xmit_qdrops=0pktizer_out_qdrops=4 pktizer_in_qdrops=0 v42_xmit_qdrops=0Total Modem Relay Call Legs = 1Router# show modem relay stat v42ID:3V42 Layer Statisticsvs_chng_dueto_timeouts=0 vs_chng_dueto_rej=0vs_chng_dueto_rnr_resp_f1_set=0 nr_seq_exception=0good_rcvd_lapm_pkts=2442 discarded_rcvd_lapm_pkts=0rejected_rcvd_lapm_pkts=0 v42_rcvd_iframe=9v42_rcvd_rr=2431 v42_rcvd_rnr=0 v42_rcvd_rej=0v42_rcvd_srej=0 v42_rcvd_sabme=0 v42_rcvd_dm=0v42_rcvd_ui=0 v42_rcvd_disc=0 v42_rcvd_ua=1v42_rcvd_frmr=0 v42_rcvd_xid=1 v42_rcvd_test=0v42_rcvd_destructive_brk=0 v42_rcvd_expedited_brk=0v42_rcvd_non_expedited_brk=0 v42_rcvd_brkack=0v42_sent_iframe=10 v42_sent_rr=2539 v42_sent_rnr=0v42_sent_rej=0 v42_sent_srej=0 v42_sent_sabme=1v42_sent_dm=0 v42_sent_ui=0 v42_sent_disc=0v42_sent_ua=0 v42_sent_frmr=0 v42_sent_xid=1v42_sent_test=0 v42_sent_destructive_brk=0v42_sent_expedited_brk=0v42_sent_non_expedited_brk=0v42_sent_brkack=0Total Modem Relay Call Legs = 1Router# show modem relay stat phyID:3Physical Layer Statisticsnum_local_retrain=0 num_remote_retrain=0num_local_speed_shift=0 num_remote_speed_shift=0num_sync_loss=0Total Modem Relay Call Legs = 1Router# show modem relay stat pktID:3Packetizer Statisticsframes_inprogress=5 good_crc_frames=2573bad_crc_frames=61 frame_aborts=150hdlc_sync_detects=1 hdlc_sync_loss_detects=0bad_frames=0Total Modem Relay Call Legs = 1Router# show modem relay stat timerID:3Timer Statisticsxid_timer_cnt=0 sabme_timer_cnt=0 ack_timer_cnt=0chkpnt_timer_cnt=2750Total Modem Relay Call Legs = 1Related Commands
Displays current call information for a call in progress.
show modems
Displays all modem configurations.
voice service voip
To enter voice-service configuration mode and specify the voice encapsulation type, use the voice service command in global configuration mode.
voice service voip
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to switch to voice-service configuration mode from global configuration mode and to specify a voice encapsulation type. Use the exit command to exit voice-service configuration mode and return to global configuration mode.
Examples
The following example shows how to access voice-service configuration mode and specify VoIP voice encapsulation beginning in global configuration mode:
Router(config)# voice service voipRouter(conf-voi-serv)#Related Commands
modem passthrough
Configures modem passthrough over VoIP.
modem relay
Configures modem relay over VoIP.
Glossary
Backhaul—A scheme where telephony signaling is passed from a gateway to a separate control for processing. With such a scheme, the gateway does not need to interpret the signaling information. In the MGCP specification, this is called signal tunneling.
CA—Call agent. Also called the Media Gateway Controller (MGC).
CSR—Call success rate
EC—Echo cancellation
FEC—Forward error correction
DS0—64 kbps channel in a T1/E1 line
Jitter—A VOIP impairment describing the amount of variation from the normal packet rate measured at the receiving gateway.
H.323—A standard that specifies the components, protocols and procedures that provide multimedia communication services--real-time audio, video, and data communications--over packet networks, including internet protocol (IP)-based networks. H.323 is part of a family of ITU-T recommendations called H.32X that provides multimedia communication services over a variety of networks.
LAPM—Link Access Procedure for Modems. This is a link layer and error correcting protocol that detects errors through the use of a Cyclic Redundancy Check (CRC) and corrects them through the use of automatic retransmission of data.
Media Gateway—A PSTN/PBX-VoIP/NAS gateway that is controlled by a call agent using MGCP.
MGC—Media Gateway Controller. Also called the call agent (CA).
MGCP—Media Gateway Control Protocol
MNP—Microcom Networking Protocol. This is a series of protocols for modem communication. MNP4 is an error correction protocol and MNP5 is a compression protocol. They are superseded by LAPM and V.42bis, meaning that they should only be used as a fallback if both sides do not support LAPM and V.42bis
Modem passthrough—Transmits modem tones as a pulse-code modulation (PCM) stream, inhibiting voice processing functions such as compression and echo cancellation.
Modem relay—Decomposes modem tones to digital form and reconstitutes them on the egress gateway.
NSE—Named Signaling Event. Also called a Telephony signaling event (TSE) in RFC 2833. Used to signal codec upspeed.
PCM—Pulse Code Modulation. Transmission of analog information in digital form through sampling and encoding the samples with a fixed number of bits.
SIP— Session Initiation Protocol
SPRT—Simple Packet Relay Transport
SCTP—Simple Control Transmission Protocol
TDM—Time Division Multiplexing. Technique in which information from multiple channels is allocated bandwidth on a single wire based on preassigned time slots. Bandwidth is allocated to each channel regardless of whether the station has data to transmit.
TSE—Telephony Signaling Event. Also called a Named signaling event (NSE) in RFC 2833. Used to signal codec upspeed.
Upspeeding—The method used to dynamically change the codec type and speed to meet network conditions. This means that the modem moves to a faster codec when both voice and data calls are connected, and then slows down when there's only voice traffic. Named signaling events (NSEs)—also called telephone-events in RFC 2833—are used for signaling codec upspeed.
V.34—ITU-T Standard that specifies a serial line protocol. V.34 offers improvements to the V.32 standard, including higher transmission rate (28.8 kbps) and enhanced data compression.
V.42—ITU-T Recommendation for error correction and link layer protocol between modems. This protocol provides a procedure for establishing an error-corrected session and describes LAPM. This is the most common protocol used for high speed modems.
V.42bis—ITU-T Recommendation for data compression using error correction procedures.
VAD—Voice activity detection.
VoIP—Voice over Internet Protocol.
Note
