-
Cisco IOS Voice Command Reference
-
About Cisco IOS Software Documentation
-
Using Cisco IOS Software
-
Commands: A
-
Commands: B
-
Commands:cac master through call application stats
-
Commands: call application voice through call-denial
-
Commands: call fallback through called-number (dial-peer)
-
Commands: caller-id (dial peer) through ccm-manager switchover-to-backup
-
Commands: ccs connect (controller) through clear vsp statistics
-
Commands: clid through cptone
-
Commands: default (MGCP profile) through direct-inward-dial
-
Commands: disable-early-media 180 through dualtone
-
Commands: E
-
Commands: F
-
Commands: G
-
Commands: H
-
Commands: icpif through irq global-request
-
Commands: isdn bind-l3 through ixi transport http
-
Commands: K
-
Commands: L
-
Commands: map q850-cause through mgcp package-capability
-
Commands: mgcp persistent through mmoip aaa send-id secondary
-
Commands: mode (ATM/T1/E1 controller) through mwi-server
-
Commands: N
-
Commands: O
-
Commands: package through pattern
-
Commands: permit hostname through proxy h323
-
Commands: Q
-
Commands: R
-
Commands: sccp through service-type call-check
-
Commands: session through sgcp tse payload
-
Commands: show aal2 profile through show call filter match-list
-
Commands: show call history fax through show debug condition
-
Commands: show dial-peer video through show gatekeeper zone status
-
Commands: show gateway through show modem relay statistics
-
Commands: show mrcp client session active through show sgcp statistics
-
Commands: show sip service through show trunk hdlc
-
Commands: show vdev through show voice statistics memory-usage
-
Commands: show voice translation-profile through shutdown (voice-port)
-
Commands: signal through srv version
-
Commands: ss7 mtp2-variant through switchover method
-
Commands: target carrier-id through threshold noise
-
Commands: timeout (auto-config application) through timing clear-wait
-
Commands:timing delay-duration through type (voice)
-
Commands: U
-
Commands: vad (dial peer) through voice class dualtone-detect-params
-
Commands: voice class h323 through vxml tree memory
-
Commands: W
-
Commands: Z
-
Feedback
Table Of Contents
maximum sessions (DSP Farm profile)
mgcp behavior comedia-check-media-src
mgcp behavior comedia-sdp-force
mgcp modem passthrough voip redundancy
mgcp modem relay voip gateway-xid
mgcp modem relay voip mode sse
mgcp modem relay voip sprt retries
mgcp modem relay voip sprt v14
Cisco IOS Voice Commands:
M
This chapter contains commands to configure and maintain Cisco IOS voice applications. The commands are presented in alphabetical order. Some commands required for configuring voice may be found in other Cisco IOS command references. Use the master index of commands or search online to find these commands.
For detailed information on how to configure these applications and features, refer to the Cisco IOS Voice Configuration Library.
map q850-cause
To play a customized tone to PSTN callers if a call disconnects with a specific Q.850 call-disconnect cause code and release source, use the map q850-cause command in voice-service configuration mode. To disable the code-to-tone mapping, use the no form of this command.
map q850-cause code-id release-source {local | remote | all} tone tone-id
no map q850-cause code-id release-source {local | remote | all} tone tone-id
Syntax Description
Command Default
No mapping occurs.
Command Modes
Voice-service
Command History
Usage Guidelines
Use this command to cause a particular tone to play when a call disconnects for a particular reason.
The tone plays to callers only if the call-disconnect and wait-to-release timers are set to values greater than 0 by entering the timeouts call-disconnect and timeouts wait-release commands.
Examples
The following example maps Q.850 call-disconnect cause code 21 to tone 3 on the local gateway and to tone 2 on the remote gateway:
Router(config)# voice service potsRouter(conf-voi-serv)# map q850-cause 21 release-source local tone 3Router(conf-voi-serv)# map q850-cause 21 release-source remote tone 2Related Commands
max1 lookup
To enable Domain Name System (DNS) lookup for a new call-agent address when the suspicion threshold value is reached, use the max1 lookup command in MGCP profile configuration mode. To disable lookup, use the no form of this command.
max1 lookup
no max1 lookup
Syntax Description
This command has no arguments or keywords.
Command Default
Lookup is enabled.
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
Call-agent redundancy can be provided when call agents are identified by DNS name rather than by IP address in the call-agent command, because each DNS name can have more than one IP address associated with it.
When the active call agent does not respond to a message from the media gateway, the gateway tests to determine whether the call agent is out of service. The gateway retransmits the message to the call agent for the number of times specified in the max1 retries command; this is known as the suspicion threshold. If there is no response and the max1 lookup command is enabled, the gateway examines the DNS lookup table to find the IP address of another call agent. If a second call agent is listed, the gateway retransmits the message to the second call agent until a response is received or the number of retries specified in the max1 retries command is reached.
This process is repeated for each IP address in the DNS table until the final address is reached. For the final address, the number of retries is specified by the max2 retries command; this number is known as the disconnect threshold. If the number of retries specified in the max2 retries command is reached and there is still no response and the max2 lookup command is enabled, the gateway performs one final DNS lookup. If any new IP addresses have been added, the gateway starts the retransmission process again. Otherwise, the gateway places the endpoint in a disconnected state.
Examples
The following example enables DNS lookup and sets the suspicion retransmission counter to 7:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# call-agent igloo.northpole.netRouter(config-mgcp-profile)# max1 lookupRouter(config-mgcp-profile)# max1 retries 7Related Commands
max1 retries
To set the Media Gateway Control Protocol (MGCP) suspicion threshold value (the number of attempts to retransmit messages to a call agent address before performing a new lookup for retransmission), use the max1 retries command in MGCP profile configuration mode. To reset to the default, use the no form of this command.
max1 retries number
no max1 retries
Syntax Description
Command Default
5 attempts
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for an MGCP profile.
Call-agent redundancy can be provided when call agents are identified by Domain Name System (DNS) name rather than by IP address in the call-agent command, because each DNS name can have more than one IP address associated with it.
When the active call agent does not respond to a message from the media gateway, the gateway tests to determine whether the call agent is out of service. The gateway retransmits the message to the call agent for the number of times specified in the max1 retries command; this is known as the suspicion threshold. If there is no response and the max1 lookup command is enabled, the gateway examines the DNS lookup table to find the IP address of another call agent.
If a second call agent is listed, the gateway retransmits the message to the second call agent until a response is received or the number of retries specified in the max1 retries command is reached. This process is repeated for each IP address in the DNS table until the final address is reached. For the final address, the number of retries is specified by the max2 retries command; this is known as the disconnect threshold. If the number of retries specified in the max2 retries command is reached and there is still no response and the max2 lookup command is enabled, the gateway performs one final DNS lookup. If any new IP addresses have been added, the gateway starts the retransmission process again. Otherwise, the gateway places the endpoint in a disconnected state.
Examples
The following example enables DNS lookup and sets the suspicion retransmission counter to 7:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# call-agent igloo.northpole.netRouter(config-mgcp-profile)# max1 lookupRouter(config-mgcp-profile)# max1 retries 7Related Commands
max2 lookup
To enable Domain Name System (DNS) lookup for a new call-agent address after the disconnect threshold timeout value is reached, use the max2 lookup command in MGCP profile configuration mode. To disable DNS lookup, use the no form of this command.
max2 lookup
no max2 lookup
Syntax Description
This command has no arguments or keywords.
Command Default
Lookup is enabled.
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for a Media Gateway Control Protocol (MGCP) profile.
Call-agent redundancy can be provided when call agents are identified by DNS name rather than by IP address in the call-agent command, because each DNS name can have more than one IP address associated with it.
When the active call agent does not respond to a message from the media gateway, the gateway tests to determine whether the call agent is out of service. The gateway retransmits the message to the call agent for the number of times specified in the max1 retries command; this is known as the suspicion threshold. If there is no response and the max1 lookup command is enabled, the gateway examines the DNS lookup table to find the IP address of another call agent. If a second call agent is listed, the gateway retransmits the message to the second call agent until a response is received or the number of retries specified in the max1 retries command is reached.
This process is repeated for each IP address in the DNS table until the final address is reached. For the final address, the number of retries is specified by the max2 retries command; this is known as the disconnect threshold. If the number of retries specified in the max2 retries command is reached and there is still no response and the max2 lookup command is enabled, the gateway performs one final DNS lookup. If any new IP addresses have been added, the gateway starts the retransmission process again. Otherwise, the gateway places the endpoint in a disconnected state.
Examples
The following example enables DNS lookup and sets the disconnect retransmission counter to 9:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# call-agent ca1@exp.example.comRouter(config-mgcp-profile)# max2 lookupRouter(config-mgcp-profile)# max2 retries 9Related Commands
max2 retries
To set the Media Gateway Control Protocol (MGCP) disconnect threshold value (the number of attempts to retransmit messages to a call agent address before performing a new lookup for further retransmission), use the max2 retries command in MGCP profile configuration mode. To disable the disconnect threshold or to return the number of retries to the default, use the no form of this command.
max2 retries number
no max2 retries
Syntax Description
Command Default
7 attempts
Command Modes
MGCP profile configuration
Command History
Usage Guidelines
This command is used when configuring values for an MGCP profile.
Call-agent redundancy can be provided when call agents are identified by Domain Name System (DNS) name rather than by IP address in the call-agent command, because each DNS name can have more than one IP address associated with it.
When the active call agent does not respond to a message from the media gateway, the gateway tests to determine whether the call agent is out of service. The gateway retransmits the message to the call agent for the number of times specified in the max1 retries command; this is known as the suspicion threshold. If there is no response and the max1 lookup command is enabled, the gateway examines the DNS lookup table to find the IP address of another call agent. If a second call agent is listed, the gateway retransmits the message to the second call agent until a response is received or the number of retries specified in the max1 retries command is reached.
This process is repeated for each IP address in the DNS table until the final address is reached. For the final address, the number of retries is specified by the max2 retries command; this is known as the disconnect threshold. If the number of retries specified in the max2 retries command is reached and there is still no response and the max2 lookup command is enabled, the gateway performs one final DNS lookup. If any new IP addresses have been added, the gateway starts the retransmission process again. Otherwise, the gateway places the endpoint in a disconnected state.
Examples
The following example sets the disconnect retransmission counter to 9:
Router(config)# mgcp profile nyc-caRouter(config-mgcp-profile)# call-agent igloo.northpole.netRouter(config-mgcp-profile)# max2 retries 9Related Commands
max-calls
To set the maximum number of calls that a trunk group can handle, use the max-calls command in trunk group configuration mode. To reset to the default, use the no form of this command.
max-calls {any | data | voice} number [direction [in | out]]
no max-calls {any | data | voice} number [direction [in | out]]
Syntax Description
Command Default
No limit when the command is not set.
Command Modes
Trunk group configuration
Command History
Usage Guidelines
Use this command to set the maximum number of calls to be handled by the trunk group. If the command is not set the maximum is infinite.
If the maximum is reached, the trunk group becomes unavailable for more calls. When the number of calls falls below the maximum, the trunk group will accept more calls.
Examples
The following example assigns a maximum number of 500 calls of any type to trunk group gw15:
Router(config)# trunk group gw15Router(config-trunk-group)# max-calls any 500The following example assigns a maximum of 200 data calls and 750 voice calls to trunk group 32:
Router(config)# trunk group 32Router(config-trunk-group)# max-calls data 200Router(config-trunk-group)# max-calls voice 750Related Commands
show trunk group
Displays the configuration of one or more trunk groups.
trunk group
Initiates a trunk group definition.
max-conn (dial peer)
To specify the maximum number of incoming or outgoing connections for a particular Multimedia Mail over IP (MMoIP), plain old telephone service (POTS), Voice over Frame Relay (VoFR), or Voice over IP (VoIP) dial peer, use the max-conn command in dial peer configuration mode. To set an unlimited number of connections for this dial peer, use the no form of this command.
max-conn number
no max-conn
Syntax Description
number
Maximum number of connections for this dial peer. Range is from 1 to 2147483647. Default is an unlimited number of connections.
Command Default
The no form of this command is the default, meaning an unlimited number of connections
Command Modes
Dial peer configuration
Command History
Usage Guidelines
Use this command to define the maximum number of connections used simultaneously to send or receive fax-mail. This command applies to off-ramp store-and-forward fax functions.
Examples
The following example configures a maximum of 5 connections for VoIP dial peer 10:
dial-peer voice 10 voipmax-conn 5Related Commands
mta receive maximum-recipients
Specifies the maximum number of recipients for all SMTP connections.
max-connection
To set the maximum number of simultaneous connections to be used for communication with a settlement provider, use the max-connection command in settlement configuration mode. To reset to the default, use the no form of this command.
max-connection number
no max-connection number
Syntax Description
Command Default
10 connections
Command Modes
Settlement configuration
Command History
Examples
The following command sets the maximum number of simultaneous connections to 10:
settlement 0max-connection 10Related Commands
max-forwards
To globally set the maximum number of hops, that is, proxy or redirect servers that can forward the Session Initiation Protocol (SIP) request, use the max-forwards command in SIP user-agent configuration mode. To reset the default number of hops, use the no form of this command.
max-forwards number-of-hops
no max-forwards number-of-hops
Syntax Description
Command Default
70 hops
Command Modes
SIP user-agent configuration
Command History
Usage Guidelines
To reset this command to the default value, you can also use the default command.
Examples
The following example sets the number of forwarding requests to 65:
sip-uamax-forwards 65Related Commands
max-redirects
To set the maximum number of redirect servers that the n_ allows, use the max-redirects command in dial peer configuration mode. To reset to the default, use the no form of this command.
max-redirects number
no max-redirects
Syntax Description
Maximum number of redirect servers that a call can traverse. Range is from 1 to 10. The default is 1.
Command Default
1 redirect
Command Modes
Dial peer configuration
Command History
Examples
The following is an example of setting the maximum number of redirect servers that the user agent allows:
dial-peer voice 102 voipmax-redirects 2Related Commands
dial-peer voice
Enters dial peer configuration mode and specifies the method of voice-related encapsulation.
max-subscription
To set the maximum number of concurrent watch sessions that are allowed, use the max-subscription command in presence configuration mode. To return to the default, use the no form of this command.
max-subscription number
no max-subscription
Syntax Description
Command Default
Maximum subscriptions is 100.
Command Modes
Presence (config-presence)
Command History
12.4(11)XJ
This command was introduced.
12.4(15)T
This command was integrated into Cisco IOS Release 12.4(15)T.
Usage Guidelines
This command sets the maximum number of concurrent presence subscriptions for both internal and external subscribe requests.
Examples
The following example shows the maximum subscriptions set to 150:
Router(config)# presenceRouter(config-presence)# max-subscription 150Related Commands
maximum conference-party
To configure the maximum number of conference parties allowed in each meet-me conference, use the maximum conference-party command in DSP farm profile configuration mode. To reset this number to the default, use the no form of this command.
maximum conference-party max-parties
no maximum conference-party max-parties
Syntax Description
max-parties
Maximum number of parties allowed in each meet-me conference session. One DSP can support the following maximums:
•
G.711—32 parties
•
The default is 8 parties.
Command Default
8 parties
Command Modes
DSP farm profile configuration (config-dspfarm-profile)
Command History
12.4(11)XJ2
This command was introduced.
12.4(15)T
This command was integrated into Cisco IOS Release 12.4(15)T.
Usage Guidelines
The maximum number of parties allowed for hardware conferencing is dependent on the codec used in the DSP farm profile. Use the codec command in DSP Farm profile configuration mode to specify the codecs supported by the DSP farm profile. Use the show dspfarm profile command to display the DSP farm profile.
Examples
The following example configures a DSP farm profile that has maximum of 16 parties for hardware conferences using the G.711 codec:
Router(config)# dspfarm profile conference1Router(config-dspfarm-profile)# maximum conference-party 16Router(config-dspfarm-profile)# codec g711alawRelated Commands
codec (DSP Farm profile)
Specifies the codecs supported by a DSP farm profile.
show dspfarm profile command
Displays configured DSP farm profile information.
maximum sessions (DSP Farm profile)
To specify the maximum number of sessions that are supported by the profile, use the maximum sessions command in digital signal processor (DSP) farm profile configuration mode. To reset to the default, use the no form of the command.
Command Syntax When Conferencing or Transcoding Is Configured
maximum sessions number
no maximum sessions
Command Syntax When MTP is Configured
maximum sessions {hardware | software} number
no maximum sessions
Syntax Description
Command Default
0 sessions
Command Modes
DSP farm profile configuration
Command History
Usage Guidelines
When using MTP service type, you must specify the number of sessions separately for software MTP and hardware MTP. The hardware MTP needs DSP resources. Use hardware MTP when the codecs are the same and the packetization period is different.
Active profiles must be shut down in order to change any parameters.
Note
Examples
The following example shows that four sessions are supported by the DSP farm profile:
Router(config-dspfarm-profile)# maximum sessions 4Related Commands
mdn
To request that a message disposition notification (MDN) be generated when a message is processed (opened), use the mdn command in dial peer configuration mode. To disable generation of an MDN, use the no form of this command.
mdn
no mdn
Syntax Description
This command has no arguments or keywords.
Command Default
Disabled
Command Modes
Dial peer configuration
Command History
Usage Guidelines
Message disposition notification is an e-mail message that is generated and sent to the sender when the message is opened by the receiver. Use this command to request that an e-mail response message be sent to the sender when the e-mail that contains the fax TIFF image has been opened.
This command applies to on-ramp store-and-forward fax functions.
Examples
The following example requests that a message disposition notification be generated by the recipient:
dial-peer voice 10 mmoipmdnRelated Commands
mta receive generate-mdn
Specifies that the off-ramp gateway process a response MDN from an SMTP server.
mta send return-receipt-to
Specifies the address to which MDNs are sent.
media
To enable media packets to pass directly between the endpoints, without the intervention of the IP-to-IP gateway (IPIPGW), use the media command in dial-peer, voice-class, or voice-service configuration mode. To return to the default IPIPGW behavior, use the no form of this command.
media [flow-around | flow-through | statistics]
no media [flow-around | flow-through | statistics]
Syntax Description
Command Default
The default behavior of the IP-to-IP gateway is to receive media packets from the inbound call leg, terminate them, and then reoriginate the media stream on an outbound call leg.
Command Modes
Dial-peer, voice-class, or voice-service configuration mode (config-dial-peer) (config-class) (config-voi-serv).
Command History
12.3(1)T
This command was introduced.
12.4(11)XJ2
The statistics keyword was introduced.
12.4(15)T
This command was integrated into Cisco IOS Release 12.4(15)T.
Usage Guidelines
With the default configuration, the IPIPGW receives media packets from the inbound call leg, terminates them, and then reoriginates the media stream on an outbound call leg. Media flow-around enables media packets to be passed directly between the endpoints, without the intervention of the IPIPGW. The IPIPGW continues to handle routing and billing functions. Media flow-around for SIP-to-SIP calls is not supported.
Note
You can specify media flow-around for voice-class, all VoIP calls, or individual dial-peers.
Examples
Media Flow-around Examples
The following example show media flow-around being configured on a dial-peer:
Router(config)# dial-peer voice 2 voipRouter(config-dial-peer) media flow-aroundThe following example show media flow-around being configured for all VoIP calls:
Router(config)# voice service voipRouter(config-voi-serv) media flow-aroundThe following example show media flow-around being configured for voice-class calls:
Router(config)# voice class media 1Router(config-class) media flow-aroundMedia Flow-though Examples
The following example show media flow-around being configured on a dial-peer:
Router(config)# dial-peer voice 2 voipRouter(config-dial-peer) media flow-throughThe following example show media flow-around being configured for all VoIP calls:
Router(config)# voice service voipRouter(config-voi-serv) media flow-throughThe following example show media flow-around being configured for voice-class calls:
Router(config)# voice class media 2Router(config-class) media flow-throughMedia Statistics Examples
The following example show media monitoring being configured for all VoIP calls:
Router(config)# voice service voipRouter(config-voi-serv) statisticsThe following example show media monitoring being configured for voice-class calls:
Router(config)# voice class media 1Router(config-class) statisticsRelated Commands
dial-peer voice
Enters dial-peer configuration mode
voice service
Enters voice-service configuration mode
voice class
Enters voice-class configuration mode
mediacard
To enter mediacard configuration mode and configure a Communications Media Module (CMM) media card, use the mediacard command in global configuration mode.
mediacard slot
Syntax Description
Command Default
No default behavior or values
Command Modes
Global configuration mode
Command History
Usage Guidelines
Mediacard configuration mode is used to configure parameters related to the selected media card, such as digital signal processor (DSP) resource pools.
Examples
The following example shows how you configure DSP resources on the media card in slot 1:
mediacard 1Related Commands
debug mediacard
Displays debugging information for Digital Signal Processor Resource Manager (DSPRM).
show mediacard
Displays information about the selected media card.
media-inactivity-criteria
To specify the mechanism for detecting media inactivity (silence) on a voice call, use the media-inactivity-criteria command in gateway configuration mode. To disable detection, use the no form of this command.
media-inactivity-criteria {rtp | rtcp | all}
no media-inactivity-criteria
Syntax Description
rtp
Real-Time Transport Protocol (RTP) (default)
rtcp
RTP Control Protocol (RTCP)
all
Both RTP and RTCP
Command Default
Media-inactivity detection is performed by means of RTP.
Command Modes
Gateway
Command History
Usage Guidelines
Use this command to specify the mechanism for detecting silence on a voice call. After doing so, you can configure silent calls to disconnect by entering the related commands listed below.
Use this command, in conjunction with the application, package callfeature, param, and paramspace commands, to configure callfeature parameters at the package level and to override them as needed for specific applications or dial peers.
The mechanism that you explicitly specify with this command takes precedence over any mechanism that you might implicitly have specified with the ip rtcp report interval command in combination with the timer media-inactive or timer receive-rtcp command.
Examples
The following example specifies the use of RTCP for silence detection:
Router(config)# gatewayRouter(config-gateway)# media-inactivity-criteria rtcpThe following example shows a configuration that might result from the use of this and related commands:
voice service potsmap q850-cause 44 release-source local tone 3applicationpackage callfeatureparam med-inact-disc-cause 44param med-inact-det enableparam med-inact-action disconnectip rtcp report interval 9000dial-peer voice 5 voipdestination-pattern .Tprogress_ind disconnect enable 8session target rascodec g711ulawgatewaymedia-inactivity-criteria rtcptimer media-inactive 5Related Commands
member (dial peer cor list)
To add a member to a dial peer class of restrictions (COR) list, use the member command in dial peer COR list configuration mode. To remove a member from a list, use the no form of this command.
member class-name
no member class-name
Syntax Description
class-name
Class name previously defined in dial peer COR custom configuration mode by using of the name command.
Command Default
No default behavior or values.
Command Modes
Dial peer COR list configuration
Command History
Examples
The following example adds three members to the COR list named list3:
dial-peer cor list list3member 900_callmember 800_callmember catchallRelated Commands
method
To set a specific accounting method list, use the method command in gateway accounting AAA configuration mode.
method acctMethListName
Syntax Description
Command Default
H.323 is the default accounting method list.
Command Modes
Gateway accounting AAA configuration
Command History
12.2(11)T
This command was introduced on the following platforms: Cisco 3660, Cisco AS5300, Cisco AS5350, Cisco AS5400, Cisco AS5800, and Cisco AS5850.
Usage Guidelines
•
•
•
Examples
The following example uses the method list named "klz_aaa6" that was previously defined using the AAA commands.
aaa new-model!aaa group server radius sg6server 1.6.30.70 auth-port 1708 acct-port 1709!aaa authentication login klz_aaa6 group sg6! klz_aaa6 is defined as the method list name.aaa authorization exec klz_aaa6 group sg6aaa accounting connection klz_aaa6 start-stop group sg6!gw-accounting aaamethod klz_aaa6! The same method list named klz_aaa6 is used.Related Commands
aaa accounting
Enables accounting of requested services for billing or security purposes.
gw-accounting aaa
Enables VoIP gateway accounting.
mgcp
To allocate resources for the Media Gateway Control Protocol (MGCP) and start the MGCP daemon, use the mgcp command in global configuration mode. To terminate all calls, release all allocated resources, and stop the MGCP daemon, use the no form of this command.
mgcp [port]
no mgcp
Syntax Description
port
(Optional) User Datagram Protocol (UDP) port for the MGCP gateway. Range is from 1025 to 65535. The default is UDP port 2427.
Command Default
UDP port 2427
Command Modes
Global configuration
Command History
Usage Guidelines
Once you start the MGCP daemon using the mgcp command, you can suspend it (for example, for maintenance) by using the mgcp block-newcalls command. When you are ready to resume normal MGCP operations, use the no mgcp block-newcalls command. Use the no mgcp command only if you intend to terminate all MGCP applications and protocols.
When the MGCP daemon is not active, all MGCP messages are ignored.
If you want to change the UDP port while MGCP is running, you must stop the MGCP daemon using the no mgcp command, and then restart it with the new port number using the mgcp port command.
Examples
The following example initiates the MGCP daemon:
Router(config)# mgcpThe following example enables the MGCP daemon on port 4204:
Router(config)# mgcp 4204Related Commands
mgcp behavior
To configure a gateway to alter the Media Gateway Control Protocol (MGCP) behavior, use the mgcp behavior command in global configuration mode. To resume using the standard protocol version behavior specified in the configuration, use the no form of this command.
mgcp behavior category version
no mgcp behavior category version
Syntax Description
category
MGCP behavior category. See Table 28.
version
MGCP version for the behavior category. See Table 28.
Command Default
The gateway follows the rules and guidelines specified by the configured MGCP protocol version.
Command Modes
Global configuration
Command History
Usage Guidelines
Table 28 describes the MGCP behavior keywords.
Examples
The following example forces the gateway to send MGCP 0.1 responses to AUEP commands:
Router(config)# mgcp behavior auep v0.1The following example forces the gateway to provide MGCP 0.1 treatment of call signaling tones:
Router(config)# mgcp behavior signals v0.1The following example disables the requirement that the RSIP be acknowledged before a call agent command is accepted:
Router(config)# mgcp behavior ack-init-rsip disableThe following example configures the gateway to not demote initial RSIPs based on the service state of the endpoints:
Router(config)# mgcp behavior init-rsip-per-insvc legacyThe following example forces the gateway to turn off all signals on receipt of a DLCX:
Router(config)# mgcp behavior dlcx-clear-signals allThe following examples sets quarantine mode to legacy:
Router(config)# mccp behavior q-mode-enduring legacyThe following example forces the gateway to generate an SDP in the response to an MDCX with SDP:
Router(config)# mgcp behavior mdcx-sdp ack-with-sdpThe following example allows the gateway to generate endpoint ranges for all MGCP versions:
Router(config)# mccp behavior rsip-range allUse the following commands to display the MGCP behavior and versions settings:
Router# show running-config | include behaviormgcp behavior auep v0.1mgcp behavior signals v0.1mgcp behavior ack-init-rsip disablemgcp behavior init-rsip-per-insvc legacymgcp behavior q_mode-enduring legacymgcp behavior dlcx-clear-signals allmgcp behavior mdcx-sdp ack-with-sdpmgcp behavior rsip-range allRouter# show running-config | include call-agentmgcp call-agent ca123.example.net 4040 service-type mgcp version rfc3435-1.0Related Commands
mgcp behavior comedia-check-media-src
To force IP address and port detection from the first RTP packet received for the entire Media Gateway Control Protocol (MGCP) gateway and enable the callback function selected by MGCP, use the mgcp behavior comedia-check-media-src command in global configuration mode.
mgcp behavior comedia-check-media-src {enable | disable}
Syntax Description
Command Default
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Use the mgcp behavior comedia-check-media-src command to force IP address and port detection from the first rtp packet received for the entire MGCP gateway. This command also enables the callback function selected by MGCP, and with the configuration of the mgcp behavior comedia-role command contributes to the determination of whether to populate the SDP direction attribute.
Examples
The following example shows IP address and port detection being enabled for the entire MGCP gateway:
Router(config)# mgcp behavior comedia-check-media-src enableRelated Commands
mgcp behavior comedia-role
To specify the location of the configured Media Gateway Control Protocol (MGCP) gateway, use the mgcp behavior comedia-role command in global configuration mode.
mgcp behavior comedia-role {active | passive | none}
Syntax Description
active
Specifies MGCP gateways located inside NAT.
passive
Specifies MGCP gateways located outside of NAT.
none
Specifies gateway behavior be as in releases prior to Cisco IOS Release 12.4(11)T.
Command Default
none
Command Modes
Global configuration
Command History
Usage Guidelines
This command will specify the location of the configured MGCP gateway and its role in solving the NAT media traversal. A comedia role of active is configured for MGCP gateways inside NAT. For gateways located outside of NAT a comedia role of passive is configured. Configuring the none keyword specifies gateway behavior before the mgcp behavior comedia-role command was introduced.
The mgcp behavior comedia-role and mgcp behavior comedia-check-media-src commands are used to determine when to populate the sdp direction attribute.
Examples
The following example shows the location of the MGCP gateway configured for MGCP gateways inside NAT:
Router(config)# mgcp behavior comedia-role activeRelated Commands
mgcp behavior comedia-sdp-force
To force MGCP to place the direction attribute in the Session Description Protocol (SDP), use the mgcp behavior comedia-sdp-force command in global configuration mode.
mgcp behavior comedia-sdp-force {enable | disable}
Syntax Description}
Command Default
Disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
This command will force the MGCP to always place the direction attribute in the SDP using the mgcp behavior comedia-sdp-force command as a reference. When the mgcp behavior comedia-sdp-force command is configured with the disable keyword, the mgcp behavior comedia-role and mgcp behavior comedia-check-media-src commands and the remote descriptor determine if the direction is added to the SDP. If the role is not configured, this command has no effect.
Examples
The following example configuration forces the direction attribute to be placed in the SDP:
Router(config)# mgcp behavior comedia-sdp-force enableRelated Commands
mgcp bind
To configure the source address for signaling and media packets to the IP address of a specific interface, use the mgcp bind command in global configuration mode. To disable binding, use the no form of this command.
mgcp bind {control | media} source-interface interface-id
no mgcp bind {control | media}
Syntax Description
Command Default
Binding is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
If the mgcp bind command is not enabled, the IP layer still provides the best local address.
A warning message is displayed if any of the following situations occur:
•
•
•
•
•
Examples
The following example shows how the configuration of bind interfaces is shown when show running-config information is viewed:
...mgcp bind control source-interface FastEthernet0mgcp bind media source-interface FastEthernet0...Related Commands
mgcp block-newcalls
To block new calls while maintaining existing calls, use the mgcp block-newcalls command in global configuration mode. To resume media gateway control protocol (MGCP) operation, use the no form of this command.
mgcp block-newcalls
no mgcp block-newcalls
Syntax Description
This command has no arguments or keywords.
Command Default
New call are not blocked.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is valid only if the mgcp command is enabled.
Once you issue this command, all requests for new connections (CreateConnection requests) are denied. All existing calls are maintained until participants terminate them or you use the no mgcp command. When the last active call is terminated, the MGCP daemon is terminated and all resources that are allocated to it are released. The no mgcp block-newcalls command returns the router to normal MGCP operations.
Examples
The following example prevents the gateway from receiving new calls:
Router(config)# mgcp block-newcallsRelated Commands
mgcp call-agent
To configure the address and protocol of the call agent for Media Gateway Control Protocol (MGCP) endpoints on a media gateway, use the mgcp call-agent command in global configuration mode. To reset to the default, use the no form of this command.
mgcp call-agent {host-name | ip-address} [port] [service-type type [version protocol-version]]
no mgcp call-agent
Syntax Description
Command Default
Call-agent UDP port: 2727 for MGCP 1.0, NCS 1.0, and TGCP 1.0
Call-agent UDP port: 2427 for MGCP 0.1 and SGCP
Call-agent UDP port: 2427 for Cisco CallManager
Service type and version: mgcp 0.1
Service type for Cisco CallManager: mgcpCommand Modes
Global configuration
Command History
Usage Guidelines
Global call-agent configuration (with this command) and call-agent configuration for an MGCP profile (with the mgcp profile call-agent command) are mutually exclusive; the first to be configured on an endpoint blocks configuration of the other on the same endpoint.
Identifying call agents by Domain Name System (DNS) name rather than by IP address in the mgcp call-agent and mgcp profile call-agent commands provides call-agent redundancy, because a DNS name can have more than one IP address associated with it. If a call agent is identified by DNS name and a message from the gateway fails to reach the call agent, the max1 lookup and max2 lookup commands enable a search from the DNS lookup table for a backup call agent at a different IP address.
The port argument configures the call-agent port number (the UDP port over which the gateway sends messages to the call agent). The reverse (the gateway port number, or the UDP port over which the gateway receives messages from the call agent) is configured by specifying a port number in the mgcp command.
When the service type is set to mgcp, the call agent processes the restart in progress (RSIP) error messages sent by the gateway if the mgcp sgcp restart notify command is enabled. When the service type is set to sgcp, the call agent ignores the RSIP messages.
Use this command on any platform and media gateway.
The mgcp service type supports the RSIP error messages sent by the gateway if the mgcp sgcp restart notify command is enabled.
Examples
The following examples illustrate several formats for specifying the call agent (use any one of these formats):
Router(config)# mgcp call-agent 209.165.200.225 service-type mgcp version 1.0Router(config)# mgcp call-agent 10.0.0.1 2427 service-type mgcp version rfc3435-1.0Router(config)# mgcp call-agent igloo.northpole.net service-type ncsRouter(config)# mgcp call-agent igloo.northpole.net 2009 service-type sgcp version 1.5Router(config)# mgcp call-agent 209.165.200.225 5530 service-type tgcpRelated Commands
mgcp codec
To select the codec type and its optional packetization period value, use the mgcp codec command in global configuration mode. To set the codec to its default value of G711 u-law, use the no form of this command.
mgcp codec type [packetization-period value]
no mgcp codec
Syntax Description
Command Default
G711 u-law codec
Command Modes
Global configuration
Command History
Examples
The following example specifies the codec type:
Router(config)# mgcp codec g711alawThe following example sets the codec type and packetization period:
Router(config)# mgcp codec g729r8 packetization-period 150Related Commands
mgcp codec gsmamr-nb
To specify the Global System for Mobile Adaptive Multi-Rate Narrow Band (GSMAMR-NB) codec for an MGCP dial peer, use the mgcp codec gsmamr-nb command in dial peer voice configuration mode. To disable the GSMAMR-NB codec, use the no form of this command.
mgcp codec gsmamr-nb [packetization-period 20] [encap rfc3267] [frame-format {bandwidth-efficient | octet-aligned [crc | no-crc]}] [modes modes-value]
no mgcp codec gsmamr-nb
Syntax Description
Command Default
Packetization period is 20 ms.
Encapsulation is rfc3267.
Frame format is octet-aligned.
CRC is no-crc.
Modes value is 0-7.Command Modes
Dial peer voice configuration (config-dial-peer)
Command History
Usage Guidelines
Use the mgcp codec gsmamr-nb command to configure the GSMAMR-NB codec and its parameters on the Cisco AS5350XM and Cisco AS5400XM platforms.
Examples
The following example shows how to set the codec to gsmamr-nb and set the parameters:
Router(config-dial-peer)# mgcp codec gsmamr-nb packetization-period 20 encap rfc3267 frame-format octet-aligned crcRelated Commands
mgcp codec ilbc
To specify the internet Low Bandwidth Codec (iLBC) for an MGCP dial peer, use the mgcp codec ilbc command in dial peer voice configuration mode. To disable the iLBC, use the no form of this command.
mgcp codec ilbc mode frame_size [packetization-period value]
no mgcp codec ilbc
Syntax Description
Command Default
20ms frames for a 15.2 kbps bit rate.
Command Modes
Dial peer voice configuration (config-dial-peer)
Command History
Usage Guidelines
The iLBC is only supported on Cisco AS5350XM and Cisco AS5400XM Universal Gateways with Voice Feature Cards (VFCs) and IP-to-IP gateways with no transcoding and conferencing.
Examples
The following example shows how to set the MGCP codec to ilbc and set the parameters:
Router(config-dial-peer)# mgcp codec ilbc mode 20 packetization-period 60Related Commands
mgcp debug-header
To enable the display of Media Gateway Control Protocol (MGCP) module-dependent information in the debug header, use the mgcp debug-header command in global configuration mode. To disable the MGCP module-dependent information, use the no form of this command.
mgcp debug-header
no mgcp debug-header
Syntax Description
This command has no arguments or keywords.
Command Default
MGCP module-dependent information in the debug header is enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
This command determines whether MGCP module-dependent information is displayed in the standard header for debug output.
Examples
The following example enables MGCP module-dependent information in debug headers:
Router(config)# mgcp debug-headerRelated Commands
mgcp package-capability
To specify MGCP package capability type for a media gateway, use the mgcp package-capability command in global configuration mode. To remove a specific MGCP package capability from the list of capabilities, use the no form of this command.
mgcp package-capability package
no mgcp package-capability package
Syntax Description
Command Default
For residential gateways: line-package
For trunk gateways: trunk-packageCommand Modes
Global configuration
Command History
Usage Guidelines
Events specified in the MGCP messages from the call agent must belong to one of the supported packages. Otherwise, connection requests are refused by the gateway.
By default, certain packages are configured as supported on each platform type. Using this command, you can configure additional package capability only for packages that are supported by your call agent. You can also disable support for a package with the no form of this command. Enter each package you want to add as a separate command.
Note
The md-package is enabled automatically when a T1 interface is configured to use FGD EANA signaling with the ds0-group command.
Use the show mgcp command to display the packages that are supported on the gateway.
Use this command before specifying a default package with the mgcp default-package command. Specify at least one default package.
Packages that are available to be configured with this command vary by platform and type of gateway. Use the CLI help to ascertain the packages available on your gateway. This example shows the CLI help output for a Cisco 3660:
Router# mgcp package-capability ?as-package Select the Announcement Server Packageatm-package Select the ATM Packagedtmf-package Select the DTMF Packagegm-package Select the Generic Media Packagehs-package Select the Handset Packageline-package Select the Line Packagemf-package Select the MF Packageres-package Select the RES Packagertp-package Select the RTP Packagetrunk-package Select the Trunk Package
Note
When the lcs-package keyword is used on the Cisco Integrated Access Device (IAD), the named telephony events (NTEs) associated with the line control signalling (LCS) package are enabled automatically. NTEs are used by a media gateway to transport telephony tones and trunk events across a packet network. See RFC 2833.
Note
Examples
The following example enables the modem relay STE package, trunk package, DTMF package, and script package on the gateway, and then names the trunk package as the default package for the gateway:
Router(config)# mgcp package-capability mdste-packageRouter(config)# mgcp package-capability trunk-packageRouter(config)# mgcp package-capability dtmf-packageRouter(config)# mgcp package-capability script-packageRouter(config)# mgcp default-package trunk-packageRelated Commands
mgcp dtmf-relay
To ensure accurate forwarding of digits on compressed codecs, use the mgcp dtmf-relay command in global configuration mode. To disable this process for uncompressed codecs, use the no form of this command.
Voice over IP (VoIP)
mgcp dtmf-relay voip codec {all | low-bit-rate} mode {cisco | nse | out-of-band | nte-gw | nte-ca}
no mgcp dtmf-relay voip
Voice over AAL2 (VoAAL2)
mgcp dtmf-relay voaal2 codec [all | low-bit-rate]
no mgcp dtmf-relay voaal2
Syntax Description
Command Default
For the Cisco 7200 series router, the command is not enabled.
For all other platforms, noncompressed codecs are disabled.Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to access an announcement server or a voice-mail server that cannot decode RTP packets containing DTMF digits. When the mgcp dtmf-relay command is active, the DTMF digits are removed from the voice stream and carried so that the server can decode the digits.
Only VoIP supports the mode keyword for forwarding digits on codecs.
Examples
The following example removes the DTMF tone from the voice stream and sends FRF.11 with a special payload for the DTMF digits:
mgcp dtmf-relay codec mode ciscoThe following example configures a low-bit-rate codec using VoIP in NSE mode:
mgcp dtmf-relay voip codec low-bit-rate mode nseThe following example configures a codec for VoAAL2:
mgcp dtmf-relay voaal2 codec allThe following example configures a low-bit-rate codec using VoIP in NSE mode:
mgcp dtmf-relay voip codec low-bit-rate mode nseThe following example sets the dtmf-relay codec and mode to gateway:
mgcp dtmf-relay codec mode nte-gwRelated Commands
mgcp endpoint offset
To enable incrementing of the POTS or DS0 portion of an endpoint name when using the Network-based Call Signaling (NCS) 1.0 profile of Media Gateway Control Protocol (MGCP), use the mgcp endpoint offset command in global configuration mode. To reset to the default, use the no form of this command.
mgcp endpoint offset
no mgcp endpoint offset
Syntax Description
This command has no arguments or keywords.
Command Default
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
This command is used with NCS 1.0 to increment the POTS or DS0 portion of an endpoint name by 1 to minimize potential interoperability problems with call agents (media gateway controllers).
NCS 1.0 mandates that the port number of an endpoint be based on 1, and port numbering on some gateway platforms is based on 0.
When this command is configured, it offsets all endpoint names on the gateway. For example, an endpoint with a port number of aaln/0 is offset to aaln/1, and a DS0 group number of 0/0:0 is offset to 0/0:1.
Examples
The following example enables incrementing the port number portion of an endpoint name:
Router(config)# mgcp endpoint offsetRelated Commands
mgcp explicit hookstate
To enable detection of explicit hookstates, use the mgcp explicit hookstate command in global configuration mode. To disable hookstate detection, use the no form of this command.
mgcp explicit hookstate
no mgcp explicit hookstate
Syntax Description
This command has no arguments or keywords.
Command Default
Hookstate detection is enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Explicit hookstate detection is enabled by default. In this state, the gateway returns a "401 endpoint already off hook" or "402 endpoint already on hook" NACK (Not Acknowledged) response to R:hu or R:hd event requests.
If you turn hookstate detection off with the no form of the mgcp explicit hookstate command, the hookstate is not checked when the gateway receives R:hu or R:hd event requests. The gateway acknowledges (ACK) these event requests.
Examples
The following example enables hookstate detection:
Router(config)# mgcp explicit hookstateRelated Commands
mgcp fax rate
To establish the maximum fax rate for Media Gateway Control Protocol (MGCP) T.38 sessions, use the mgcp fax rate command in global configuration mode. To reset MGCP endpoints to their default fax rate, use the no form of this command.
mgcp fax rate {2400 | 4800 | 7200 | 9600 | 12000 | 14400 | voice}
no mgcp fax rate
Syntax Description
Command Default
MGCP fax rate is set to the highest possible transmission speed allowed by the voice codec
(mgcp fax rate voice).Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to specify the maximum fax transmission rate for all MGCP endpoints in the gateway.
The values for this command apply only to the fax transmission speed and do not affect the quality of the fax itself. The higher transmission speed values (14,400 bps) provide a faster transmission speed but use a significantly large portion of the available bandwidth. A lower transmission speed value (2400 bps, for example) provides a slower transmission speed but uses a smaller portion of the available bandwidth.
Note
When the MGCP fax rate is set to the highest possible transmission speed allowed by the voice codec (mgcp fax rate voice), all MGCP endpoints limit T.38 fax calls to this speed. For example, if the voice codec is G.711, fax transmission may occur up to 14,400 bps because 14,400 bps is less than the 64-kbps voice rate. If the voice codec is G.729 (8 kbps), the fax transmission speed is limited to the nearest fax rate of 7200 bps.
Tip
Only values other than the default value appear in the saved gateway configuration.
Examples
The following example configures a maximum fax rate transmission speed of 9600 bps for MGCP T.38 fax relay sessions:
Router(config)# mgcp fax rate 9600The following example configures the maximum fax rate transmission speed to 12,000 bps for MGCP T.38 fax relay sessions:
Router(config)# mgcp fax rate 12000Related Commands
show call active fax
Displays the maximum fax rate for the current T.38 fax session.
show mgcp
Displays the current configuration for the MGCP fax rate.
mgcp fax-relay sg3-to-g3
To enable the fax stream between two Super Group 3 (SG3) fax machines to negotiate down to G3 speeds for Media Gateway Control Protocol (MGCP) fax relay, use the mgcp fax-relay sg3-to-g3 command in global configuration mode. To disable SG3 fax message suppression, use the no form of this command.
mgcp fax-relay sg3-to-g3
no mgcp fax-relay sg3-to-g3
Syntax Description
This command has no arguments or keywords.
Command Default
Disabled
Command Modes
Global configuration
Command History
12.4(4)T
This command was introduced.
12.4(6)T
This feature was implemented on the Cisco 1700 series and Cisco 2800 series.
Usage Guidelines
When this command is entered, the digital signal processor (DSP) fax-relay firmware suppresses the V.8 CM tone and the fax machines negotiate down to G3 speeds for the fax stream.
Examples
The following global configuration output shows V.8 fax CM message suppression being enabled on the voice dial peer for MGCP signaling types:
Router(config)# mgcp fax-relay sg3-to-g3Related Commands
mgcp fax t38
To configure MGCP fax T.38 parameters, use the mgcp fax t38 command in global configuration mode. return a parameter to its default, use the no form of this command.
mgcp fax t38 {ecm | gateway force | hs_redundancy factor | inhibit | ls_redundancy factor | nsf hexcode}
no mgcp fax t38 {ecm | gateway force | hs_redundancy | inhibit | ls_redundancy | nsf}
Syntax Description
Command Default
ecm—disabled
gateway force—disabled
hs_redundancy—0
inhibit—disabled (T.38 is enabled. See note in above table.)
ls_redundancy—0
nsf—not overriddenCommand Modes
Global configuration
Command History
Usage Guidelines
Nonstandard facilities (NSF) are capabilities a particular fax manufacturer has built into a fax machine to distinguish products from each other.
To disable T.38 fax relay, use the mgcp fax t38 inhibit command.
Some MGCP call agents do not properly pass those portions of Session Description Protocol (SDP) messages that advertise T.38 and NSE capabilities. As a result, gateways that are controlled by these call agents are unable to use NSEs to signal T.38 fax relay to other gateways that use NSEs. The mgcp fax t38 gateway force command provides a way to ensure gateway-controlled T.38 fax relay and use of NSEs between an MGCP gateway and another gateway. The other gateway can be an H.323, Session Initiation Protocol (SIP), or MGCP gateway. Both gateways must be configured to use NSEs to signal T.38 fax relay mode switchover. On H.323 and SIP gateways, use the fax protocol t38 nse force command to specify the use of NSEs for T.38 fax relay. On MGCP gateways, use the mgcp fax t38 gateway force command.
Examples
The following example configures the gateway to use NSEs for gateway-controlled T.38 fax relay signaling:
Router(config)# mgcp fax t38 gateway forceThe following example shows that MGCP T.38 fax relay and ECM are enabled, NSF override is disabled, and low- and high-speed redundancy are set to the default value of 0:
Router(config)# mgcp fax t38 ecmRouter(config)# exitRouter# show mgcpMGCP Admin State ACTIVE, Oper State ACTIVE - Cause Code NONEMGCP call-agent: 172.18.195.147 2436 Initial protocol service is MGCP 0.1MGCP block-newcalls DISABLEDMGCP send RSIP for SGCP is DISABLEDMGCP quarantine mode discard/stepMGCP quarantine of persistent events is ENABLEDMGCP dtmf-relay for VoIP disabled for all codec typesMGCP dtmf-relay for VoAAL2 disabled for all codec typesMGCP voip modem passthrough mode: CA, codec: g711ulaw, redundancy: DISABLED,MGCP voaal2 modem passthrough mode: NSE, codec: g711ulawMGCP TSE payload: 119MGCP T.38 Named Signalling Event (NSE) response timer: 200MGCP Network (IP/AAL2) Continuity Test timer: 200MGCP 'RTP stream loss' timer disabledMGCP request timeout 500MGCP maximum exponential request timeout 4000MGCP gateway port: 2427, MGCP maximum waiting delay 3000MGCP restart delay 0, MGCP vad DISABLEDMGCP rtrcac DISABLEDMGCP system resource check DISABLEDMGCP xpc-codec: DISABLED, MGCP persistent hookflash: DISABLEDMGCP persistent offhook: ENABLED, MGCP persistent onhook: DISABLEDMGCP piggyback msg ENABLED, MGCP endpoint offset DISABLEDMGCP simple-sdp DISABLEDMGCP undotted-notation DISABLEDMGCP codec type g729r8, MGCP packetization period 10MGCP JB threshold lwm 30, MGCP JB threshold hwm 150MGCP LAT threshold lmw 150, MGCP LAT threshold hwm 300MGCP PL threshold lwm 1000, MGCP PL threshold hwm 10000MGCP CL threshold lwm 1000, MGCP CL threshold hwm 10000MGCP playout mode is adaptive 60, 4, 200 in msecMGCP IP ToS low delay disabled, MGCP IP ToS high throughput disabledMGCP IP ToS high reliability disabled, MGCP IP ToS low cost disabledMGCP IP RTP precedence 5, MGCP signaling precedence: 3MGCP default package: dt-packageMGCP supported packages: gm-package dtmf-package trunk-package line-packagehs-package rtp-package as-package atm-package ms-packagedt-package mo-package res-package mt-packagedt-package mo-package res-package mt-packageMGCP Digit Map matching order: shortest matchSGCP Digit Map matching order: always left-to-rightMGCP VoAAL2 ignore-lco-codec DISABLEDMGCP T.38 Fax is ENABLEDMGCP T.38 Fax ECM is ENABLEDMGCP T.38 Fax NSF Override is DISABLEDMGCP T.38 Fax Low Speed Redundancy: 0MGCP T.38 Fax High Speed Redundancy: 0The following example shows that NSF is overridden:
MGCP T.38 Fax NSF Override is ENABLED: AC04D3Related Commands
Related Commands
Related CommandsRouter(config)# mgcp ip-tos signaling precedence
mgcp ip-tos
To enable or disable the IP type of service (ToS) for media gateway control protocol (MGCP) connections, use the mgcp ip-tos command in global configuration mode. To restore the default, use the no form of this command.
mgcp ip-tos {high-reliability | high-throughput | low-cost | low-delay | rtp precedence value | signaling precedence value}
no mgcp ip-tos {high-reliability | high-throughput | low-cost | low-delay | rtp precedence value | signaling precedence value}
Syntax Description
Command Default
Services are disabled.
RTP precedence: 3
Signaling precedence: 3Command Modes
Global configuration
Command History
Usage Guidelines
Only one of the keywords in the group high-reliability, high-throughput, low-cost, and low-delay can be enabled at any given time. Enabling one keyword disables any other that was active. Enabling one of these keywords has no effect on the precedence value.
The no form of the mgcp ip-tos command disables the first four keywords and sets the precedence value back to 3.
When you configure a new value for precedence, the old value is erased.
Examples
The following example activates the low-delay keyword and disables the previous three keywords:
Router(config)# mgcp ip-tos high-relRouter(config)# mgcp ip-tos high-throughputRouter(config)# mgcp ip-tos low-costRouter(config)# mgcp ip-tos low-delayRouter(config)# mgcp ip-tos rtp precedence 4Related Commands
Related CommandsRouter(config)# mgcp ip-tos signaling precedence 5
mgcp max-waiting-delay
To specify the media gateway control protocol (MGCP) maximum waiting delay (MWD), use the mgcp max-waiting-delay command in global configuration mode. To reset to the default, use the no form of this command.
mgcp max-waiting-delay milliseconds
no mgcp max-waiting-delay
Syntax Description
milliseconds
Time, in milliseconds, to wait after restart. Range is from 0 to 600000 (600 seconds). The default is 3000 (3 seconds).
Command Default
3000 ms
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to send out an Restart in Progress (RSIP) message to the call agent with the restart method. This command helps prevent traffic bottlenecks caused by MGCP gateways all trying to connect at the same time after a restart.
Examples
The following example sets the MGCP maximum waiting delay to 600 ms:
Router(config)# mgcp max-waiting-delay 600Related Commands
mgcp
Starts the MGCP daemon.
mgcp restart-delay
Configures the graceful teardown method sent in the RSIP message.
mgcp modem passthrough codec
To select the codec that enables the gateway to send and receive modem and fax data in VoIP and VoATM adaptation layer 2 (VoAAL2) configurations, use the mgcp modem passthrough codec command in global configuration mode. To disable support for modem and fax data, use the no form of this command.
mgcp modem passthrough {voip | voaal2} codec {g711alaw | g711ulaw}
no mgcp modem passthrough {voip | voaal2}
Syntax Description
Command Default
The g711 u-law codec for both VOIP and VOAAL2
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command for fax pass-through because the answer tone can come from either modem or fax transmissions. Selecting a codec dynamically changes the codec type and speed to meet network conditions.
Examples
The following example enables a gateway to send and receive VoAAL2 modem or fax data using the G711 a-law codec:
Router(config)# mgcp modem passthrough voaal2 codec g711alawRelated Commands
mgcp modem passthrough mode
To set the method for changing speeds that enables the gateway to send and receive modem and fax data in VoIP and VoATM adaptation layer 2 (VoAAL2) configurations, use the mgcp modem passthrough mode command in global configuration mode. To disable support for modem and fax data, use the no form of this command.
mgcp modem passthrough {voip | voaal2} mode {cisco | nse}
no mgcp modem passthrough {voip | voaal2}
Syntax Description
Command Default
NSE-based method
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command for fax pass-through because the answer tone can come from either modem or fax transmissions.
Upspeed is the method used to change the codec type and speed dynamically to meet network conditions.
If you use the nse keyword, you must also use the mgcp tse payload command.
If you use the default nse keyword and the voip or voaal2 keyword, the show run command does not display the mgcp modem passthrough mode command in the configuration output, although the command is displayed for the cisco keyword. The show mgcp command displays settings for both the nse and cisco keywords.
Examples
The following example enables a gateway to send and receive VoIP modem or fax data using the NSE modem-speed-changing method:
Router(config)# mgcp modem passthrough voip mode nseRelated Commands
mgcp modem passthrough voip redundancy
To enable redundancy on a gateway that sends and receives modem and fax data in VoIP configurations, use the mgcp modem passthrough voip redundancy command in global configuration mode. To disable redundancy, use the no form of this command.
mgcp modem passthrough voip redundancy
no mgcp modem passthrough voip redundancy
Syntax Description
This command has no arguments or keywords.
Command Default
Disabled (no redundancy)
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command for fax pass-through because the answer tone can come from either modem or fax transmissions.
Upspeed is the method used to dynamically change the codec type and speed to meet network conditions.
Examples
The following example enables redundancy for VoIP modem and fax transmissions on a gateway:
Router(config)# mgcp modem passthrough voip redundancyRelated Commands
mgcp modem passthru
To enable the gateway to send and receive modem and fax data, use the mgcp modem passthru command in global configuration mode. To disable support for modem and fax data, use the no form of this command.
mgcp modem passthru {cisco | ca}
no mgcp modem passthru
Syntax Description
Command Default
ca
Command Modes
Global configuration
Command History
12.1(3)T
This command was added to MGCP.
12.2(11)T
This command was implemented on the Cisco AS5850.
Usage Guidelines
When the cisco keyword is activated and the gateway detects a modem/fax tone, the gateway switches the codec to G.711 then sends the analog data to a remote gateway. The remote gateway also switches the codec on its side of the call to G.711 to allow the analog data to pass through.
When the ca keyword is activated and the gateway detects a modem/fax tone, the gateway alerts the call agent to switch the codec to G.711 to allow the analog data to pass through. The call agent must send an MDCX signal to the G.711 codec for successful data pass-through.
Examples
The following example configures a gateway to send and receive modem or fax data:
Router(config)# mgcp modem passthru ciscoRelated Commands
mgcp modem relay voip gateway-xid
To enable 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]
no mgcp modem relay voip gateway-xid
Syntax Description
Command Default
Command: enabled
Compress: both
Dictionary: 1024
String length: 32Command Modes
Global configuration
Command History
12.2(11)T
This command was introduced on the following platforms: Cisco 2600 series, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200 series, and Cisco AS5300.
Usage Guidelines
This command enables XID negotiation for modem relay. By default it is enabled.
This command affects only VoIP calls and not Voice over ATM adaption layer 2 (VoAAL2) calls. This is because MGCP supports VoAAL2 calls for voice and fax/modem, but not for modem relay.
If this command is enabled on both VoIP gateways of a network, the gateways determine whether they need to engage in in-band negotiation of various compression parameters. The remaining keywords in this command specify the negotiation posture of this gateway in the subsequent in-band negotiation (assuming that in-band negotiation is agreed on by the two gateways).
The compress, dictionary, and string-length keywords are digital-signal-processor (DSP)-specific and related to xid negotiation. If this 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, 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
value
Estimated one-way delay across the IP network, in milliseconds. Range is from 100 to 1000. Default is 200.
Command Default
200 ms
Command Modes
Global configuration
Command History
12.2(11)T
This command was introduced on the following platforms: Cisco 2600 series, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200 series, and Cisco AS5300.
Usage Guidelines
Use this command to adjust the retransmission timer of the Simple Packet Relay Transport (SPRT) protocol, if required, by setting the 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 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
mgcp modem relay voip mode sse
To enable State Signaling Event (SSE) based modem relay mode and to configure SSE parameters on the MGCP gateway, use the mgcp modem relay voip mode sse command in global configuration mode. To disable this function, use the no form of this command.
mgcp modem relay voip mode sse [redundancy [{interval number | packet number}]][retries value] [t1 time]
no mgcp modem relay voip mode sse
Syntax Description
Command Default
SSE mode is enabled by default, using default parameter values.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the mgcp modem relay voip mode sse command to configure state signaling events (SSE) parameters for secure MGCP voice and data calls between Secure Telephone Equipment (STE) and IP STE endpoints using the SSE protocol, a subset of the V.150.1 standard for modem relay. SSEs, which are Real-Time Transport Protocol (RTP) encoded event messages, are used to coordinate transitions between the different media states, secure and nonsecure. Before configuring SSE parameters, you must use the mgcp package-capability mdste command to enable modem relay capabilities and SSE protocol support.
Examples
The following examples configure SSE parameters for redundancy interval redindancy packet count, number of retries and the t1 timer interval:
Router(config)# mgcp modem relay voip mode sse redundancy interval 20Router(config)# mgcp modem relay voip mode sse redundancy packet 4Router(config)# mgcp modem relay voip mode sse retries 5Router(config)# mgcp modem relay voip mode sse t1 1000Related Commands
mgcp package-capability mdste
Enables MGCP gateway support for processing events and signals for modem connections over a secure communication path between IP-STE and STE.
mgcp modem relay voip 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 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
value
Maximum number of times that the SPRT protocol tries to send a packet before disconnecting. Range is from 6 to 30. The default is 12.
Command Default
12 times
Command Modes
Global configuration
Command History
12.2(11)T
This command was introduced on the following platforms: Cisco 2600 series, Cisco 3620, Cisco 3640, Cisco 3660, Cisco 7200 series, and Cisco AS5300.
Examples
The following example sets 15 as the maximum number of times that the SPRT protocol tries to send a packet before disconnecting:
mgcp modem relay voip sprt retries 15Related Commands
mgcp modem relay voip sprt v14
To configure V.14 modem relay parameters for packets sent by the Simple Packet Relay Transport (SPRT) protocol, use the mgcp modem relay voip sprt v14 command in global configuration mode. To disable this function, use the no form of this command.
mgcp modem relay voip sprt v14 [receive playback hold-time milliseconds | transmit hold-time milliseconds | transmit maximum hold-count characters]
no mgcp modem relay voip sprt v14
Syntax Description
Command Default
V.14 modem relay parameters are enabled by default, using default parameter values.
Command Modes
Global configuration
Command History
Usage Guidelines
The maximum size of receive buffers is set at 500 characters, a nonprovisionable limit. Use the mgcp modem relay voip sprt v14 receive playback hold-time milliseconds command to configure the minimum holding time before characters can be removed from the receive queue. Characters received on the PSTN or ISDN interface may be collected for a configurable collection period before being sent out on SPRT channel 3, potentially resulting in variable size SPRT packets. To configure V.14 transmit parameters for SPRT packets, use the mgcp modem relay voip sprt v14 transmit hold-time milliseconds and the mgcp modem relay voip sprt v14 transmit maximum hold-count characters commands.
Parameter changes do not take effect during existing calls; they affect new calls only.
SPRT transport channel 1 is not supported.
Examples
The following example sets 200 ms as the receive playback hold time, 25 ms as the transmit hold time, and 10 characters as the transmit hold count parameters:
Router(config)# mgcp modem relay voip sprt v14 receive playback hold-time 200Router(config)# mgcp modem relay voip sprt v14 transmit hold-time 25Router(config)# mgcp modem relay voip sprt v14 transmit maximum hold-count 10Related Commands
mgcp package-capability
To specify MGCP package capability type for a media gateway, use the mgcp package-capability command in global configuration mode. To remove a specific MGCP package capability from the list of capabilities, use the no form of this command.
mgcp package-capability package
no mgcp package-capability package
Syntax Description
Command Default
For residential gateways: line-package
For trunk gateways: trunk-packageCommand Modes
Global configuration
Command History
Usage Guidelines
Events specified in the MGCP messages from the call agent must belong to one of the supported packages. Otherwise, connection requests are refused by the gateway.
By default, certain packages are configured as supported on each platform type. Using this command, you can configure additional package capability only for packages that are supported by your call agent. You can also disable support for a package with the no form of this command. Enter each package you want to add as a separate command.
Note
The md-package is enabled automatically when a T1 interface is configured to use FGD EANA signaling with the ds0-group command.
Use the show mgcp command to display the packages that are supported on the gateway.
Use this command before specifying a default package with the mgcp default-package command. Specify at least one default package.
Packages that are available to be configured with this command vary by platform and type of gateway. Use the CLI help to ascertain the packages available on your gateway. This example shows the CLI help output for a Cisco 3660:
Router# mgcp package-capability ?as-package Select the Announcement Server Packageatm-package Select the ATM Packagedtmf-package Select the DTMF Packagegm-package Select the Generic Media Packagehs-package Select the Handset Packageline-package Select the Line Packagemf-package Select the MF Packageres-package Select the RES Packagertp-package Select the RTP Packagetrunk-package Select the Trunk Package
Note
When the lcs-package keyword is used on the Cisco Integrated Access Device (IAD), the named telephony events (NTEs) associated with the line control signalling (LCS) package are enabled automatically. NTEs are used by a media gateway to transport telephony tones and trunk events across a packet network. See RFC 2833.
Note
Examples
The following example enables the modem relay STE package, trunk package, DTMF package, and script package on the gateway, and then names the trunk package as the default package for the gateway:
Router(config)# mgcp package-capability mdste-packageRouter(config)# mgcp package-capability trunk-packageRouter(config)# mgcp package-capability dtmf-packageRouter(config)# mgcp package-capability script-packageRouter(config)# mgcp default-package trunk-packageRelated Commands
