Cisco IOS Voice Command Reference

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 pots

Router(conf-voi-serv)# map q850-cause 21 release-source local tone 3

Router(conf-voi-serv)# map q850-cause 21 release-source remote tone 2

Related Commands

map resp-code

To globally configure a Cisco Unified Border Element (Cisco UBE) to map specific received Session Initiation Protocol (SIP) provisional response messages to a different SIP provisional response message on the outgoing SIP dial peer, use the map resp-code command in voice service SIP configuration mode. To disable mapping of received SIP provisional response messages, use the no form of this command.

map resp-code 181 to 183

no map resp-code 181

Syntax Description

Command Default

Incoming SIP provisional response messages are passed, as is to the outgoing SIP leg.

Command Modes

Voice service SIP configuration (conf-serv-sip)

Command History

Usage Guidelines

Use the map resp-code command in voice service SIP configuration mode to globally enable a Cisco UBE to map incoming SIP 181 provisional response messages to SIP 183 provisional response messages on the outgoing SIP dial peer.

Note If the block command is configured for incoming SIP 181 messages, either globally or at the dial-peer level, the messages may be dropped before they can be passed or mapped to a different message—even when the map resp-code command is enabled. To globally configure whether and when incoming SIP 181 messages are dropped, use the block command in voice service SIP configuration mode (or use the voice-class sip block command in dial peer voice configuration mode to configure drop settings on individual dial peers).

To configure mapping of SIP provisional response messages for an individual dial peer on a Cisco UBE, use the voice-class sip map resp-code command in dial peer voice configuration mode. To disable mapping of SIP 181 message globally on a Cisco UBE, use the no map resp-code command in voice service SIP configuration mode.

As an example, to enable interworking of SIP endpoints that do not support the handling of SIP 181 provisional response messages, you could use the block command to configure a Cisco UBE to drop SIP 181 provisional response messages received on the SIP trunk or you can use the map resp-code command to configure the Cisco UBE to map the incoming messages to and send out, instead, SIP 183 provisional response messages to the SIP line in Cisco Unified Communications Manager Express (Cisco Unified CME).

Note This command is supported only for SIP-to-SIP calls and will have no effect on H.323-to-SIP or time-division multiplexing (TDM)-to-SIP calls.

Examples

The following example shows how to configure mapping of incoming SIP 181 provisional response messages on the Cisco UBE to SIP 183 provisional response messages on the outbound dial peer:

Router> enable

Router# configure terminal

Router(config)# voice service voip

Router(conf-voi-serv)# sip

Router(conf-serv-sip)# map resp-code 181 to 183

Related 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-ca

Router(config-mgcp-profile)# call-agent igloo.northpole.net

Router(config-mgcp-profile)# max1 lookup

Router(config-mgcp-profile)# max1 retries 7

Related 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-ca

Router(config-mgcp-profile)# call-agent igloo.northpole.net

Router(config-mgcp-profile)# max1 lookup

Router(config-mgcp-profile)# max1 retries 7

Related 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-ca

Router(config-mgcp-profile)# call-agent ca1@exp.example.com

Router(config-mgcp-profile)# max2 lookup

Router(config-mgcp-profile)# max2 retries 9

Related 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-ca

Router(config-mgcp-profile)# call-agent igloo.northpole.net

Router(config-mgcp-profile)# max2 retries 9

Related 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 gw15

Router(config-trunk-group)# max-calls any 500

The following example assigns a maximum of 200 data calls and 750 voice calls to trunk group 32:

Router(config)# trunk group 32

Router(config-trunk-group)# max-calls data 200

Router(config-trunk-group)# max-calls voice 750

Related Commands

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

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 voip

 max-conn 5

Related Commands

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 0

 max-connection 10

Related 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-ua

 max-forwards 65

Related 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

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 voip

 max-redirects 2

Related Commands

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

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)# presence

Router(config-presence)# max-subscription 150

Related Commands

maximum buffer-size

To set the maximum size of the file accounting buffer, use the maximum buffer-size command in gateway accounting file configuration mode. To reset to the default, use the no form of this command.

maximum buffer-size kbytes

no maximum buffer-size

Syntax Description

Command Default

Maximum buffer size is 20 kilobytes.

Command Modes

Gateway accounting file configuration (config-gw-accounting-file)

Command History

Usage Guidelines

The file accounting process writes call detail records (CDRs) to a memory buffer instead of writing each record independently to the accounting file. Two buffers are allocated for file accounting and their size is set by this command. After the accounting records in the buffer reach the size limit set by this command, the system flushes the first buffer and writes the records to the accounting file. While the first buffer is busy being flushed, the system uses the second buffer to hold new data. After the flush process, the buffer is available again.

The buffer size must be large enough to accommodate incoming CDRs without the system filling up both buffers completely.

Examples

The following example sets the maximum buffer size to 25 kilobytes:

gw-accounting file

 primary ftp server1/cdrtest1 username bob password temp

 secondary ifs flash:cdrtest2

 maximum buffer-size  25

 maximum retry-count 3

 maximum fileclose-timer 720

 cdr-format compact

Related Commands

maximum cdrflush-timer

To set the maximum time to hold call records in the buffer before appending the records to the accounting file, use the maximum cdrflush-timer command in gateway accounting configuration mode. To reset to the default, use the no form of this command.

maximum cdrflush-timer minutes

no maximum cdrflush-timer

Syntax Description

Command Default

Records are held in the buffer for 60 minutes (1 hour).

Command Modes

Gateway accounting file configuration (config-gw-accounting-file)

Command History

Usage Guidelines

After the time period set with this command expires, the router flushes the buffer and writes the call detail records (CDRs) to the accounting file.

The file accounting process sends CDRs to a memory buffer instead of writing each record independently to the accounting file. The system flushes the buffer automatically either after this timer expires or when the records in the buffer reach the size set by the maximum buffer-size command.

Set this flush timer to at least five minutes less than the file close timer set with the maximum fileclose-timer command.

To manually flush the CDRs from the buffer to the accounting file, use the file-acct flush command.

Examples

The following example shows that call records are held in the accounting file for three hours, after which the records are appended to the accounting file:

gw-accounting file

 primary ftp server1/cdrtest1 username bob password temp

 secondary ifs flash:cdrtest2

 maximum buffer-size  25

 maximum retry-count 3

 maximum fileclose-timer 720

 cdr-format compact

Related Commands

maximum conference-participants

To configure the maximum number of conference participants allowed in each meet-me conference, use the maximum conference-participants command in DSP farm profile configuration mode. To reset the maximum to the default number, use the no form of this command.

maximum conference-participants max-participants [video-cap-class number]

no maximum conference-participants max-participants [video-cap-class number]

Syntax Description

Command Default

The default maximum number of participants for a video conference is 4. The default maximum number of participants for an audio conference is 8.

Command Modes

DSP farm profile configuration (config-dspfarm-profile)

Command History

Usage Guidelines

The maximum number of participants 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 a maximum of 16 participants for hardware conferences using the G.711 codec:

Router(config)# dspfarm profile conference 1

Router(config-dspfarm-profile)# maximum conference-participants 16

Router(config-dspfarm-profile)# codec g711alaw

Related Commands

maximum fileclose-timer

To set the maximum time for writing call detail records (CDRs) to an accounting file before closing the file and creating a new one, use the maximum fileclose-timer command in gateway accounting configuration mode. To reset to the default, use the no form of this command.

maximum fileclose-timer minutes

no maximum fileclose-timer

Syntax Description

Command Default

Records are saved to an accounting file for 1,440 minutes (24 hours).

Command Modes

Gateway accounting file configuration (config-gw-accounting-file)

Command History

Usage Guidelines

After the timer set with this command expires, the current accounting file is closed and a new file with a new time stamp is opened to write CDRs. The name and location of the accounting file is set by the primary command, or the secondary command if in failover mode.

Set this file close timer to at least five minutes longer than the flush timer set with the maximum cdrflush-timer command.

To manually flush the CDRs from the buffer to the accounting file, use the file-acct flush command.

Examples

The following example shows that call records are saved to the currently open accounting file for 12 hours, after which a new accounting file is created:

gw-accounting file

 primary ftp server1/cdrtest1 username bob password temp

 secondary ifs flash:cdrtest2

 maximum buffer-size  25

 maximum retry-count 3

 maximum fileclose-timer 720

 cdr-format compact

Related Commands

maximum retry-count

To set the maximum number of times the router attempts to connect to the primary file device before switching to the secondary device, use the maximum retry-count command in gateway accounting file configuration mode. To reset to the default value, use the no form of this command.

maximum retry-count number

no maximum retry-count

Syntax Description

Command Default

Maximum connection attempts is 2.

Command Modes

Gateway accounting file configuration (config-gw-accounting-file)

Command History

Usage Guidelines

This command specifies the number of times that the router attempts to connect to the primary file device defined in the primary command before it attempts to connect to the backup file device specified with the secondary command.

Examples

The following example shows the maximum retries set to 3:

gw-accounting file

 primary ftp server1/cdrtest1 username bob password temp

 secondary ifs flash:cdrtest2

 maximum buffer-size  25

 maximum retry-count 3

 cdr-format compact

Related Commands

maximum sessions (DSP farm profile)

To specify the maximum number of sessions that are supported by the profile, use the maximum sessions command in DSP farm profile configuration mode. To reset to the default, use the no form of this 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

The maximum number of supported sessions is 0.

Command Modes

DSP farm profile configuration

Command History

Usage Guidelines

When using the MTP service type, you must specify the number of sessions separately for software MTP and hardware MTP. The hardware MTP needs digital signal processor (DSP) resources. Use hardware MTP when the codecs are the same and the packetization period is different.

Active profiles must be shut down before any parameters can be changed.

Note The syntax of the command will vary based on the type of profile that you are configuring. The keywords work only when MTP is configured.

Examples

The following example shows that four sessions are supported by the DSP farm profile:

Router(config-dspfarm-profile)# maximum sessions 

Related 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 mmoip

 mdn

Related Commands

media

To enable media packets to pass directly between the endpoints, without the intervention of the Cisco Unified Border Element (Cisco UBE) and to enable signaling services, enter the media command in dial peer voice, voice class, or voice service configuration mode. To return to the default behavior, use the no form of this command.

media [flow-around | flow-through | forking | monitoring [max-calls] | statistics | transcoder high-density | anti-trombone | sync-streams]

no media [flow-around | flow-through | forking | monitoring [max-calls] | statistics | transcoder high-density | anti-trombone | sync-streams]

Syntax Description

Command Default

The default behavior of the Cisco UBE 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 configuration (config-dial-peer)
Voice class configuration (config-class)
Voice service configuration (config-voi-serv)

Command History

Usage Guidelines

With the default configuration, the Cisco UBE 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 Cisco UBE. The Cisco UBE continues to handle routing and billing functions. Media flow-around for SIP-to-SIP calls is not supported.

Note The Cisco UBE must be running Cisco IOS Release 12.3(1) or a later release to support media flow-around.

You can specify media flow-around for a voice class, all VoIP calls, or individual dial peers.

The transcoder high-density keyword can be enabled in any of the configuration modes with the same command format. If you are configuring the transcoder high-density keyword for dial peers, make sure that the media transcoder high-density command is configured on both the in and Out-Legs.

Note The software does not support configuring the transcoder high-density keyword on any dial peer that is to handle video calls. The following scenarios are not supported:

•Dial peers used for video at any time. Configuring the media transcoder high-density command directly under the dial-peer or a voice-class media configuration mode is not supported.

•Dial peers configured on a Cisco UBE used for video calls at any time. The global configuration of the media transcoder high-density command under voice service configuration mode is not supported.

To enable the media command on a Cisco 2900 or Cisco 3900 series Unified Border Element voice gateway, you must first enter the mode border-element command. This enables the media forking and media monitoring commands. Do not configure the mode border-element command on the Cisco 2800 or Cisco 3800 series platform.

You can specify media anti-trombone for a voice class, all VoIP calls, or individual dial peers.

The anti-trombone keyword can be enabled only when no media interworking is required in both the Out-Legs. Antitrombone will not work if call leg is flow-through and another call leg is flow-around.

Examples

Media Flow-around Examples

The following example shows media flow-around configured on a dial peer:

Router(config)# dial-peer voice 2 voip 

Router(config-dial-peer)# media flow-around 

The following example shows media flow-around configured for all VoIP calls:

Router(config)# voice service voip 

Router(config-voi-serv)# media flow-around 

The following example shows media flow-around configured for voice class calls:

Router(config)# voice class media 1

Router(config-class)# media flow-around 

Media Flow-through Examples

The following example shows media flow-through configured on a dial peer:

Router(config)# dial-peer voice 2 voip 

Router(config-dial-peer)# media flow-through 

The following example shows media flow-through configured for all VoIP calls:

Router(config)# voice service voip 

Router(config-voi-serv)# media flow-through 

The following example shows media flow-through configured for voice class calls:

Router(config)# voice class media 2

Router(config-class)# media flow-through

Media Statistics Examples

The following example shows media monitoring configured for all VoIP calls:

Router(config)# voice service voip 

Router(config-voi-serv) media statistics 

The following example shows media monitoring configured for voice class calls:

Router(config)# voice class media 1

Router(config-class) media statistics

Media Transcoder High-density Examples

The following example shows the media transcoder command configured for all VoIP calls:

Router(config)# voice service voip 

Router(conf-voi-serv)# media transcoder high-density 

The following example shows the media transcoder command configured for voice class calls:

Router(config)# voice class media 1

Router(config-voice-class)# media transcoder high-density

The following example shows the media transcoder command configured on a dial peer:

Router(config)# dial-peer voice 36 voip 

Router(config-dial-peer)# media transcoder high-density

Media Monitoring on a Cisco UBE Platform

The following example shows how to configure audio call scoring for a maximum of 100 calls:

mode border-element

media monitoring 100

Media Antitrombone Examples

The following example shows the media anti-trombone command configured for all VoIP calls:

Router(config)# voice service voip

Router(conf-voi-serv)# media anti-trombone

The following example shows the media anti-trombone command configured for voice class calls:

Router(config)# voice class media 1

Router(config-voice-class)# media anti-trombone

The following example shows the media anti-trombone command configured on a dial peer:

Router(config)# dial-peer voice 36 voip 

Router(config-dial-peer)# media anti-trombone

Media Transcoder Examples

The following example specifies that both audio and video RTP streams go through the DSP farms when either audio or video transcoding is needed:

Router(config)# voice service voip 

Router(config-voi-serv)# media transcoder sync-streams 

The following example specifies that both audio and video RTP streams go through the DSP farms when either audio or video transcoding is needed and the RTP streams flow around Cisco Unified Border Element.

Router(config)# voice service voip 

Router(config-voi-serv)# media transcoder high-density sync-streams

Related Commands

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 1

Related Commands

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

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)# gateway

Router(config-gateway)# media-inactivity-criteria rtcp

The following example shows a configuration that might result from the use of this and related commands:

voice service pots

map q850-cause 44 release-source local tone 3

application

 package callfeature

  param med-inact-disc-cause 44

  param med-inact-det enable

  param med-inact-action disconnect

ip rtcp report interval 9000

dial-peer voice 5 voip

destination-pattern .T

 progress_ind disconnect enable 8

 session target ras

 codec g711ulaw

gateway

 media-inactivity-criteria rtcp

 timer media-inactive 5

Related Commands

meetme-conference

To define a feature code for a Feature Access Code (FAC) to initiate an SCCP Meet-Me Conference, use the meetme-conference command in STC application feature access-code configuration mode. To return the feature code to its default, use the no form of this command.

meetme-conference keypad-character

no meetme-conference

Syntax Description

Command Default

The default value of the feature code is 5.

Command Modes

STC application feature access-code configuration (config-stcapp-fac)

Command History

Usage Guidelines

This command changes the value of the feature code for SCCP Meet-Me Conference from the default (5) to the specified value.

If the length of the keypad-character argument is at least two characters and the leading or ending character of the string is an asterisk (*) or a number sign (#), phone users are not required to dial a prefix to access this feature. Typically, phone users dial a special feature access code (FAC) consisting of a prefix plus a feature code, for example **2. If the feature code is 55#, the phone user dials only 55#, without the FAC prefix, to access the corresponding feature.

In Cisco IOS Release 15.0(1)M and later releases, if the length of the keypad-character argument is three or four digits, phone users are not required to dial a prefix or any special characters to access this feature. Typically, phone users dial a special feature access code (FAC) consisting of a prefix plus a feature code, for example **2. If the feature code is 788, the phone user dials only 788, without the FAC prefix, to access the corresponding feature.

If you attempt to configure this command with a value that is already configured for another FAC, speed-dial code, or the Redial FSD, you receive a message. If you configure a duplicate code, the system implements the first matching feature in the order of precedence shown in the output of the show stcapp feature codes command.

If you attempt to configure this command with a value that precludes or is precluded by another FAC, speed-dial code, or the Redial FSD, you receive a message. If you configure a feature code to a value that precludes or is precluded by another code, the system always executes the call feature with the shortest code and ignores the longer code. For example, #1 will always preclude #12 and #123. You must configure a new value for the precluded code in order to enable phone user access to that feature.

To display a list of all FACs, use the show stcapp feature codes command.

Examples

The following example shows how to change the value of the feature code for SCCP Meet-Me Conference from the default (5). This configuration also changes the value of the prefix for all FACs from the default (**) to ##. With this configuration, a phone user must press ##9 on the phone keypad to cancel all-call forwarding.

Router(config)# stcapp feature access-code

Router(config-stcapp-fac)# prefix ##

Router(config-stcapp-fac)# meetme-conference 9

Router(config-stcapp-fac)# exit

Related 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

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 list3

 member 900_call

 member 800_call

 member catchall

Related 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

Usage Guidelines

•For information on setting AAA network security for your network, including setting method lists, refer to the Authentication, Authorization, and Accounting Cisco IOS Security Configuration Guide, Release 12.2.

•The method command sets the accounting method globally (not for a dial peer). To initially define the AAA method list name for accounting, use the aaa accounting command.

•The method list name used is the same name used to define the method list name under the aaa accounting command.

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 sg6

server 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 sg6

aaa accounting connection klz_aaa6 start-stop group sg6

!

gw-accounting aaa

method klz_aaa6

! The same method list named klz_aaa6 is used.

Related Commands

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

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)# mgcp

The following example enables the MGCP daemon on port 4204:

Router(config)# mgcp 4204

Related 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 that is specified in the configuration, use the no form of this command.

mgcp behavior category version

no mgcp behavior category version

Syntax Description

Command Default

The gateway follows the rules and guidelines that are specified by the configured MGCP protocol version.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

Table 33 describes the MGCP behavior category keywords.

Table 34 describes the MGCP behavior version keywords.

Examples

The following example shows how the gateway sends MGCP 0.1 responses to AUEP commands:

Router(config)# mgcp behavior auep v0.1

The following example shows how the gateway provides MGCP 0.1 treatment of call signaling tones:

Router(config)# mgcp behavior signals v0.1

The following example shows how to disable the requirement that the RSIP be acknowledged before a call agent command is accepted:

Router(config)# mgcp behavior ack-init-rsip disable

The following example show how to configure the gateway to not demote initial RSIPs based on the service state of the endpoints:

Router(config)# mgcp behavior init-rsip-per-insvc legacy

The following example shows how to configure the gateway to turn off all signals on receipt of a DLCX:

Router(config)# mgcp behavior dlcx-clear-signals all

The following examples show how to set quarantine mode to legacy:

Router(config)# mgcp behavior q-mode-enduring legacy

The following example shows how to force the gateway to generate an SDP in the response to an MDCX with SDP:

Router(config)# mgcp behavior mdcx-sdp ack-with-sdp

The following example shows how to force the gateway to generate endpoint ranges for all MGCP versions:

Router(config)# mgcp behavior rsip-range all

The following example shows how to force the gateway not to change the codec payload type when it is dynamically changed in the incoming SDP for all MGCP versions:

Router(config)# mgcp behavior dynamically-change-codec-pt disable

The following example shows how to force the gateway not to disconnect when it receives DLCX:

Router(config)# mgcp behavior fxs-gs emulate-ls-disconnect

The following example shows how forces the gateway to send responses for MGCP messages even if the endpoint is in a transient state:

Router(config)# mgcp behavior transient-state-response enable

The following example shows how to force the gateway to take connection mode M in CRCX:

Router(config)# mgcp behavior mode-attrb-in-sdp disable

The following example shows how to force the outgoing messages to have the configured private-localhost appended to the endpoint ID for MGCP 0.1 and MGCP 1.0 versions:

Router(config)# mgcp behavior private-localhost cisco.com

The following example shows how to force the gateway to play a reorder tone when MGCP is still stuck trying to collect digits:

Router(config)# mgcp behavior digit-collect-stuck play-reorder

The following example shows how to allow the gateway to be aware of NSE capabilities:

Router(config)# mccp behavior negotiate-nse enable

Use the following commands to display the MGCP behavior and versions settings:

Router# show running-config | include behavior

mgcp behavior auep v0.1

mgcp behavior signals v0.1

mgcp behavior ack-init-rsip disable

mgcp behavior init-rsip-per-insvc legacy

mgcp behavior q_mode-enduring legacy

mgcp behavior dlcx-clear-signals all

mgcp behavior mdcx-sdp ack-with-sdp

mgcp behavior rsip-range all

mgcp behaviour dynamically-change-codec-pt disable

mgcp behavior fxs-gs emulate-ls-disconnect

mgcp behavior transient-state-response enable

mgcp behavior mode-attrb-in-sdp-disable

mgcp behavior private-localhost cisco.com

mgcp behavior digit-collect-stuck- play-reorder

mgcp behavior negotiate-nse enable

Router# show running-config | include call-agent

mgcp call-agent ca123.example.net 4040 service-type mgcp version rfc3435-1.0

Related 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 enable

Related 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

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 active

Related 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 enable

Related Commands

mgcp behavior g729-variants static-pt

To change the default from dynamic to static Real-time Transport Protocol (RTP) payload type on G.729 voice codecs, use the mgcp behavior g729-variants static-pt command in global configuration mode. To return the default to dynamic, use the no form of this command.

mgcp behavior g729-variants static-pt

no mgcp behavior g729-variants static-pt

Syntax Description

This command has no arguments or keywords.

Command Default

This command is enabled by default, so the RTP payload type on G.729 voice codecs is static.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

Prior to Cisco IOS Releases 12.4(22)T2 and 12.4(24)T1, the negotiated value (dynamic) payload type was not set in RTP packets. If you upgraded the Cisco IOS software on your network voice gateways (with existing Cisco Unified Communications Manager) and calls were going between Skinny Client Control Protocol (SCCP) phones controlled by Cisco Unified Communications Manager and public switched telephone network (PSTN) phones connected to a Cisco gateway, a condition of "no audio" could occur. The mgcp behavior g729-variants static-pt command changes the default from dynamic to static RTP payload type on G.729 voice codecs and eliminates the "no audio" condition.

Examples

The following example shows how to set the RTP payload type to static for G.729 voice codecs:

Router(config)# mgcp behavior g729-variants static-pt

Related 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:

•When there are active MGCP calls on the gateway, the mgcp bind command is rejected for both control and media.

•If the bind interface is not up, the command is accepted but does not take effect until the interface comes up.

•If the IP address is not assigned on the bind interface, the mgcp bind command is accepted but takes effect only after a valid IP address is assigned. During this time, if MGCP calls are up, the mgcp bind command is rejected.

•When the bound interface goes down, either because of a manual shutdown on the interface or because of operational failure, the bind activity is disabled on that interface.

•When bind is not configured on the media gateway controller (MGC), the IP address used for sourcing MGCP control and media is the best available IP address.

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 FastEthernet0 

mgcp 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-newcalls

Related 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: mgcp

Command 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.0

Router(config)# mgcp call-agent 10.0.0.1 2427 service-type mgcp version rfc3435-1.0

Router(config)# mgcp call-agent igloo.northpole.net service-type ncs

Router(config)# mgcp call-agent igloo.northpole.net 2009 service-type sgcp version 1.5

Router(config)# mgcp call-agent 209.165.200.225 5530 service-type tgcp

Related 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 g711alaw

The following example sets the codec type and packetization period:

Router(config)# mgcp codec g729r8 packetization-period 150

Related 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 crc

Related 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 60 

Related Commands

mgcp crypto rfc-preferred

To enable support for the media-level Session Description Protocol (SDP) a=crypto attribute on Cisco IOS Media Gateway Control Protocol (MGCP) gateways, use the mgcp crypto rfc-preferred command in global configuration mode. To disable support for the a=crypto attribute, use the no form of this command.

mgcp crypto rfc-preferred

no mgcp crypto rfc-preferred

Syntax Description

This command has no arguments or keywords.

Command Default

Support for the a=crypto attribute is not enabled on Cisco IOS MGCP gateways.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

Cryptographic parameters for Secure RTP (SRTP) media sessions are signalled and negotiated using the crypto attribute in the SDP. Some versions of the crytpo attribute syntax set the crypto attribute name to the X-crypto keyword (a=X-crypto). RFC 4568 Session Description Protocol (SDP) Security Descriptions for Media Streams, defines the crypto attribute syntax, where the attribute name is set to the crypto keyword (a=crypto). You use the mgcp crypto rfc-preferred command to enable support for the a=crypto attribute on Cisco MGCP gateways.

When support for a=crypto is enabled, the system can choose to use the a=crypto or a=X-crypto notation, depending on the SDP received. By default, if a remote SDP is not present, all SDPs generated by the gateway use the a=crypto notation.

If the command is disabled, the gateway can understand both a=crypto or a=X-crypto in any SDP it receives. However, all SDPs generated by the gateway use the a=X-crypto notation.

You must configure the command based on the notation used by the call agent. For example, the Cisco public switched telephone network (PSTN) gateway (PGW) uses the a=crypto notation and Cisco Unified Call Manager uses the a=X-crypto notation.

Examples

The following example enables support for the SDP a=crypto attribute on the Cisco IOS MGCP gateway:

Router(config)# mgcp crypto rfc-preferred

The following is sample output from the show mgcp command when support for the SDP a=crypto attribute is enabled on the Cisco IOS MGCP gateway:

Router(config)# show mgcp

MGCP rsip-range is enabled for TGCP only.

MGCP Comedia role is NONE

MGCP Comedia check media source is DISABLED

MGCP Comedia SDP force is DISABLED

MGCP Guaranteed scheduler time is DISABLED

MGCP Disconnect delay error recovery DISABLED

MGCP support for a:crypto RFC notation is ENABLED

MGCP DNS stale threshold is 30 seconds

Related Commands

mgcp dns stale threshold

To configure the Media Gateway Control Protocol (MGCP) Domain Name System (DNS) stale threshold, use the mgcp dns stale threshold command in global configuration mode. To disable the stale threshold configuration, use the no form of this command.

mgcp dns stale threshold seconds

no mgcp dns stale threshold

Syntax Description

Command Default

The MGCP DNS threshold value is set to 300 seconds.

Command Modes

Global configuration (config)

Command History

Examples

The following example shows how to set the threshold stale time to 44 seconds:

Router(config)# mgcp dns stale threshold 44

Related 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-header

Related Commands

mgcp default-package

To configure the default package capability type for the media gateway, use the mgcp default-package command in global configuration mode. This command does not have a no form. To change the default package, use the mgcp default-package command with a different, actively supported package.

Residential Gateways

mgcp default-package {dt-package | dtmf-package | fxr-package | gm-package | hs-package | line-package | ms-package | rtp-package}

Business Gateways

mgcp default-package {atm-package | dt-package | dtmf-package | fxr-package | gm-package | hs-package | line-package | ms-package | rtp-package | trunk-package}

Trunking Gateways

mgcp default-package {as-package | atm-package | dt-package | dtmf-package | gm-package | hs-package | md-package | mo-package | ms-package | nas-package | rtp-package | script-package | trunk-package}

Syntax Description

Command Default

For residential gateways: line-package
For trunking gateways: trunk-package

Command Modes

Global configuration

Command History