Cisco IOS Voice Command Reference

Cisco IOS Voice Commands:
H

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 referenefces. Use the command reference master index 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 Guide.

h225 alt-ep hunt

To configure alternate endpoint hunts for failed calls in an IP-to-IP gateway (IPIPGW), use the h225 alt-ep hunt command in H.323 voice-service configuration mode. To control the alternate endpoint hunts based on call disconnect cause codes, use the no form of this command.

h225 alt-ep hunt

no h225 alt-ep hunt [ all | cause-code ]

Syntax Description

Command Default

Alternate endpoint hunt is enabled for all cause codes

Command Modes

H.323 voice-service configuration

Command History

Usage Guidelines

The default behavior of the gateway is to retry all alternate endpoints received from the gatekeeper regardless of the ReasonComplete reason. Only the no alt-ep hunt command will be visible in the configuration. A code returned from the destination router to indicate why an attempted end-to-end call was unsuccessful. If the specified disconnect cause code is returned from the last destination endpoint, dial peer hunting is enabled or disabled. You can enter the keyword, decimal value, or hexadecimal value.

The disconnect cause codes are described in Table 28. The decimal and hexadecimal value of the disconnect cause code follows the description of each possible keyword.

Examples

The following example shows the alternate endpoint hunts with the user-busy disconnect cause code disabled:

Router(conf-serv-h323)# no h225 alt-ep hunt user-busy 

Related Commands

h225 connect-passthru

To immediately pass H.225 connect messages from the trunking gateway to the outgoing gateway via a Cisco Unified Border Element, use the h225 connect-passthru command in voice class or H.323 voice-service configuration mode. To return to the default behavior, use the no form of this command.

h225 connect-passthru

no h225 connect-passthru

Syntax Description

This command has no arguments or keywords.

Command Default

The H.225 messages are not sent to the outgoing gateway until TCS/MSD/OLC negotiation takes place.

Command Modes

H.323 voice-service configuration (conf-serv-h323)
Voice class configuration (config-class)

Command History

Usage Guidelines

Calls placed through a Cisco Unified Border Element may fail to connect when the originating or terminating H.323 device is a non-Cisco IOS VoIP device such as Cisco Unified Communications Manager.

The default behavior of H.323-to-H.323 calls through a Cisco Unified Border Element is to delay sending a H.225 Connect message to the originating H323 device until the H245 TCS/MSD/OLC negotiation takes place. During this process, an H.225 Connect message with an H.245 address present from the terminating H.323 device is changed to an H.225 Progress message, followed by an H.225 Facility message with the embedded H.245 address. This can cause connection failures if the originating H.323 device is waiting for the H.225 Connect message to begin the H245 TCS/MSD/OLC negotiation.

The h225 connect-passthru command is used to immediately pass H.225 connect messages from the trunking gateway to the outgoing gateway via a Cisco Unified Border Element.

Configuring the h225 connect-passthru command in H.323 voice-service configuration is recommended for all calls passed through the Cisco Unified Border Element. This command option will be present only when the allow-connections command is configured.

This command is often configured with the h245 passthru tcsnonstd-passthru command and emptycapability command when interworking is configured between non-Cisco IOS H.323 devices.

Examples

The following example shows the h225 connect-passthru command being configured under H.323 voice-service configuration mode:

Router(conf-serv-h323)# h225 connect-passthru 

The following example shows the h225 connect-passthru command being configured under voice class configuration mode:

Router(config-class)# h225 connect-passthru

Related Commands

h225 display-ie

To allow the Cisco Unified Communication Manager to ignore the H.225 Facility message and process the H.225 Notify message used to display the calling name on the IP Phone, use the h225 display-ie ccm-compatible command in voice service or voice class configuration mode. To return to the default configuration, use the no version of the command.

h225 display-ie ccm-compatible system

no h225 display-ie ccm-compatible system

Syntax Description

Command Default

Disabled. The Cisco Unified Communication Manager ignores the IE and does not display the calling name on the Cisco IP Phone.

Command Modes

H.323 voice-service configuration (conf-serv-h323)
Voice class configuration (config-class)

Command History

Usage Guidelines

When the gateway is interoperating with Cisco Unified Communication Manager, you must enable the h225 display-ie ccm-compatible command to display the IE received in Q931 Facility message is sent out in the H.225 Notify message.

When the h225 display-ie ccm-compatible command is configured, the gateway sends the H.225 Facility message and the H.225 Notify message to the Cisco Unified Communication Manager, which ignores the H.225 Facility message, and processes the H.225 Notify message.

Note While interoperating only with Cisco Unified Connections Manager you must configure the h225 display-ie ccm-compatible command.

Behavior and configuration will vary based on the configuration mode the command is configured:

•When the h225 display-ie ccm-compatible command is configured under voice class, the CLI under voice class takes precedence. Even if the h225 display-ie ccm-compatible command is not configured under global voice service voip, the command configured under voice class takes effect. This means that when a Q931 Facility with calling name is received the gateway sends both H225 Notify and H225 Facility messages with the calling name in the Display IE.

The configured command is visible in the show running-configuration output under voice class.

•When the h225 display-ie ccm-compatible system command is configured under voice class, the command configured under global voice service VoIP takes precedence. If the h225 display-ie ccm-compatible system command is configured under voice service voip, the gateway sends a H225 Notify message. If the h225 display-ie ccm-compatible system command is not configured under voice service voip, the gateway will not send the H225 Notify message.

When the system keyword is configured, the command is not visible in the show running-configuration output.

•Configuring no h225 display-ie ccm-compatible system in voice class configuration mode, the command that is configured under voice class takes precedence. Even when no h225 display-ie ccm-compatible system command is configured under voice service voip, the gateway will not send the H225 Notify message received, and the calling name does not display on the IP Phone.

Use the no version to disable sending H225 Notify message on a particular VoIP dial-peer. The no form of the command is shown under voice class in the show running-configuration.

Examples

The following example shows a gateway being configured to send H.225 Notify message that displays the calling name on an IP Phone.

voice class h323 1

h225 display-ie ccm-compatible system

Related Commands

h225 h245-address

To control sending an H.245 address to a remote site use the h225 h245-address command in H.323 voice service configuration mode or to a H.323 voice class in global configuration mode. To disable the delay in sending H.245 address in H.225 messages, use the no form of this command.

h225 h245-address {facility | listen-on-setup | on-alert | on-progress}

no h225 h245-address

Syntax Description

Defaults

The H.245 address is sent in H.225 Callproceeding message.

Command Modes

Voice service H.323 configuration (conf-serv-h323)
H.323 voice class (config-class)

Command History

Usage Guidelines

The h225 h245-address on-alert command controls sending the local H.245 address to the remote side. Configuring the h225 h245-address on-alert command forces the Cisco IOS gateway to send the H.245 address in the H.225 alerting message instead of in the H.225 callproceeding message.

To configure the h225 h245-address on-alert command for a voice class. First create an H.323 voice class that is independent of a dial peer with the voice class h323 command in global configuration mode and configure the allow-connections command.

Note The voice-class h323 command in dial peer configuration mode includes a hyphen and in global configuration mode does not include a hyphen.

Examples

The following example globally delays the sending the H.245 transport address until call alerting happens:

Router(config)# voice service voip

Router(conf-voi-serv)# h323

Router(conf-serv-h323)# h225 h245-address on-alert

The following example shows listen-on-setup capability configured mode after creating a voice class in global configuration mode and configuring the required allow-connections command:

Router> enable

Router# configure terminal

Enter configuration commands, one per line.  End with CNTL/Z.

Router(config)# voice service voip

Router(conf-voi-serv)# allow-connections H323 to h323 

Router(conf-voi-serv)# exit            

Router(config)# voice class h323 5

Router(config-class)# h225 h245-address listen-on-setup

Related Commands

h225 h245-address on-connect (H.323 voice-class)

To enable for an individual dial peer a delay in the exchange of H.225 messages for the relay of H.245 transport addresses until call connections are made, use the h225 h245-address on-connect command in H.323 voice-class configuration mode. To disable the delay of H.225 messages, use the no form of this command.

h225 h245-address on-connect

no h225 h245-address on-connect

Syntax Description

This command has no arguments or keywords.

Command Default

H.225 messages that contain H.245 addresses are delayed until calls are connected.

Command Modes

H.323 voice-class configuration

Command History

Usage Guidelines

The functionality specified by this command allows Cisco CallManager Express 3.1 (Cisco CME 3.1) or later systems to interwork with Cisco CallManager in the same network. This command should always be enabled.

When simple A-to-B calls are made from a Cisco CallManager phone to a Cisco CME IP phone, the Cisco CallManager must play in-band ringback tone locally to the originating phone. The Cisco CallManager stops the tone generation if it receives the call's H.245 address before the call is answered. The h225 h245-address on-connect command ensures that the H.245 address is not sent before the call is answered (connected). This command is enabled by default unless the no form of this command has been used. In addition, the telephony-service ccm-compatible command must also be enabled to detect calls from Cisco CallManager, which is the default.

This command can also be used in an H.323 voice-service definition to globally enable or disable this behavior.

Examples

The following example creates a voice class with the tag of 4, which delays the exchange of H.225 messages for H.245 transport address relay until a call connection is made. Voice class 4 is then applied to dial peer 36.

Router(config)# voice class h323 4

Router(config-voice-class)# h225 h245-address on-connect

Router(config)# dial-peer voice 36 voip

Router(config-dial-peer)# destination-pattern 555....

Router(config-dial-peer)# session target ipv4:10.5.6.7 

Router(config-dial-peer)# voice-class h323 4

Related Commands

h225 h245-address on-connect (H.323 voice-service)

To globally delay the exchange of H.225 messages for the relay of H.245 transport addresses until call connections are made, use the h225 h245-address on-connect command in H.323 voice-service configuration mode. To globally disable the delay, use the no form of this command.

h225 h245-address on-connect

no h225 h245-address on-connect

Syntax Description

This command has no arguments or keywords.

Command Default

H.225 messages that contain H.245 addresses are delayed until calls are connected.

Command Modes

H.323 voice-service configuration

Command History

Usage Guidelines

The functionality specified by this command allows Cisco CallManager Express 3.1 (Cisco CME 3.1) or later systems to interwork with Cisco CallManager in the same network. This command should always be enabled.

When simple A-to-B calls are made from a Cisco CallManager phone to a Cisco CME IP phone, the Cisco CallManager must play in-band ringback tone locally to the originating phone. The Cisco CallManager stops the tone generation if it receives the call's H.245 address before the call is answered. The h225 h245-address on-connect command ensures that the H.245 address is not sent before the call is answered (connected). This behavior is the default when a Cisco CME system detects an incoming call from a Cisco CallManager unless the no form of this command has been used. In addition, the telephony-service ccm-compatible command must also be enabled to detect calls from Cisco CallManager, which is the default.

This command can also be used in an H.323 voice-class definition to enable or disable this behavior for individual dial peers.

Examples

The following example globally delays the exchange of H.225 messages for H.245 transport address relay until a call connection is made.

Router(config)# voice service voip

Router(conf-voi-serv)# h323

Router(conf-serv-h323)# h225 h245-address on-connect

Related Commands

h225 h245-address setup

To allow a gateway to connect to an H.245 address received simultaneously with the H.225 setup message use the h225 h245-address setup command in voice service configuration mode or a H.323 voice class in global configuration mode. To return to the default behavior, use the no form of this command.

h225 h245-address setup

no h225 h245-address setup

Syntax Description

Defaults

This command is disabled by default. The gateway does not connect to the H.245 address received along with the H.225 setup message.

Command Modes

H.323 voice-service configuration (conf-serv-h323)
H.323 Voice class (config-class)

Command History

Usage Guidelines

Configuring the h225 h245-address setup command allows the gateways to receive both the H.225 setup message simultaneously with the H.245 address message.

To configure the h225 h245-address setup command for a voice class. First create an H.323 voice class that is independent of a dial peer with the voice class h323 command in global configuration mode and configure the allow-connections command.

Note The voice-class h323 command in dial peer configuration mode includes a hyphen and in global configuration mode does not include a hyphen.

Examples

The following example shows the gateway globally configured to connect to the H.245 address received along with the H.225 setup message:

Router(config)# voice service voip

Router(conf-voi-serv)# h323

Router(conf-serv-h323)# h225 h245-address setup

The following example shows the gateway configured in a voice-class to connect to the H.245 address received along with H.225 setup message:

Router(config)# voice class h323 12

Router(config-class)# h225 h245-address setup

Related Commands

h225 id-passthru

To enable video call connections to pass through between endpoints regardless of software version, use the h225 id-passthru command in H.323 voice-service configuration mode. To return to the default, use the no form of this command.

h225 id-passthru

no h225 id-passthru

Syntax Description

This command has no arguments or keywords.

Command Default

Video calls are completed on endpoints using the same software version.

Command Modes

H.323 voice-service configuration

Command History

Usage Guidelines

Video calls complete when the endpoints are operating the same version of software. Use this command to allow connections between video endpoints that are using different software versions.

Examples

The following example allows video calls to connect when the polycom endpoints are using different software versions:

Router(config-serv-h323)# h225 id-passthru

Related Commands

h225 plus-digit passthru

To prefix and pass the plus digit (+) into a phone number on an H.323 trunk, use the h225 plus-digit passthru command in H.323 voice service configuration mode. To stop passing of the plus digit into a phone number, use the no form of this command.

For releases prior to 15.1(3)T

h225 plus-digit-passthru-calling

no h225 plus-digit-passthru-calling

h225 plus-digit-passthru-called

no h225 plus-digit-passthru-called

For 15.1(3)T and later releases

h225 plus-digit passthru {destination | source}

no h225 plus-digit passthru {destination | source}

Syntax Description

Command Default

The plus digit is not prefixed and passed into a called or a calling number on an H.323 trunk.

Command Modes

H.323 voice service configuration (conf-serv-h323)

Command History

Usage Guidelines

When a "+" is prefixed before the dialed digits, the carrier recognizes the call as an International call without the country specific international operator dial string. The leading "+" digit in a dial-peer match pattern is used to match a phone number with a leading "+" E.164 digit. It is not used as a regular expression symbol but is a valid E.164 digit that should be preserved across the VoIP network.

Examples

The following example shows how to add the plus digit for the calling number using the h225 plus-digit passthru source command:

Router(config)# voice service voip

Router(conf-voi-serv)# h323

Router(conf-serv-h323)# h225 plus-digit passthru source

The following example shows how to add the plus digit for the called number using the h225 plus-digit passthru destination command:

Router(config)# voice service voip

Router(conf-voi-serv)# h323

Router(conf-serv-h323)# h225 plus-digit passthru destination

h225 signal overlap

To activate overlap signaling to the destination gateway, use the h225 signal overlap command in H.225 voice-service configuration mode. To stop sending overlap signaling messages, use the no form of this command.

h225 signal overlap

no h225 signal overlap

Syntax Description

This command has no arguments or keywords.

Command Default

H.225 signaling overlap is disabled.

Command Modes

H.323 voice-service configuration

Command History

Usage Guidelines

The terminating gateway is responsible for collecting all the called number digits. This is implemented by the dial peers matching destination patterns. When H.225 signal overlap is configured on the originating gateway, it sends the SETUP to the terminating gateway once a dial-peer match is found. The originating gateway sends all further digits received from user to the terminating gateway using INFO messages until it receives a sending complete from the user. The terminating gateway receives the digits in SETUP and subsequent INFO messages and does a dial-peer match. If a match is found, it sends a SETUP with the collected digits to the PSTN. All subsequent digits are sent to the PSTN using INFO messages at which time the call is complete.

Examples

The following example enables overlap signalling on the H.225 gateway:

Router(config)# voice service voip

Router(conf-voi-serv)# h323

Router(conf-serv-h323)# h225 signal overlap 

Related Commands

h225 start-h245

To hold the H.245 connection procedures until after the H.225 connections are made, use the h225 start-h245 command in H.323 voice-class configuration mode. To disable the connection sequence, use the no form of this command.

h225 start-h245 on-connect

no h225 start-h245 on-connect

Syntax Description

Command Default

By default, h225 start-h245 on-connect is disabled. In case of IP-to-IP gateway (IPIPGW), the outbound gateway echoes the same h245 address and port number sent by the remote endpoint.

Command Modes

H.323 voice-class configuration (config-voice-class)
H.323 voice-service (conf-serv-h323)

Command History

Usage Guidelines

The h225 start-245 on-connect command ensures that the H.245 address is not sent before the call is answered (connected).

Configure this command in H.323 voice-service configuration mode to globally enable or disable the connection behavior.

Examples

The following example shows a voice class with the tag of 4 being created, which delays the exchange of H.225 messages for H.245 transport address relay until a call connection is made.

Router(conf-serv-h323)#h225 start-h245 on-connect 

Related Commands

h225 timeout call-proceeding

To set the H.225 call-proceeding (T310) disconnect timer, use the h225 timeout call-proceeding command in either voice-service or dial peer configuration mode. To revert to the default, use the no form of this command.

h225 timeout call-proceeding duration

no h225 timeout call-proceeding

Syntax Description

Command Default

60 seconds

Command Modes

For all dial peers: Voice-service configuration
For a single dial peer: Dial peer configuration

Command History

Usage Guidelines

Use this command to set a maximum duration for the time between call setup and call connect.

You can use this command in either of two configuration modes:

•For all peers: Use voice-service configuration mode by entering the voice service voip command

•For just a single dial peer: Use dial peer configuration mode for the desired dial peer by entering the voice class h323 command.

Examples

The following example sets the disconnect timer for all dial peers:

Router(config)# voice service voip

Router(config-voi-serv)# h225 timeout call-processing 5

The following example sets the disconnect timer for a single dial peer:

Router(config)# voice class h323 1

Router(config-class)# h225 timeout call-processing 5

Related Commands

h225 timeout keepalive

To disconnect H.323 calls when a TCP keepalive timeout occurs, use the h225 timeout keepalive command in H.323 voice-service configuration mode. To enable H.323 calls to remain active and ignore the TCP keepalive timeout, use the no form of this command.

h225 timeout keepalive

no h225 timeout keepalive

Syntax Description

This command has no arguments or keywords.

Command Default

TCP keepalives are enabled.

Command Modes

H.323 voice-service configuration

Command History

Usage Guidelines

When using the default configuration of the h225 timeout keepalive command, if a TCP timeout occurs on the H.225 channel, all active calls are disconnected and corresponding H.225 TCP sockets are closed.

When the no h225 timeout keepalive command is configured and a timeout occurs, the H.225 TCP socket is closed for all calls; Active TDM-IP calls will be preserved, but IP to IP calls are disconnected. In both cases the H.225 TCP socket is closed.

Note This command is visible in the running configuration only when the user configures the no form of the command.

Examples

The following example enables TCP keepalives on H.225 VoIP call control sessions:

Router(config)# voice service voip

Router(conf-voi-serv)# h323

Router(conf-serv-h323)# h225 timeout keepalive

Related Commands

h225 timeout setup

To configure the timeout value for the response of the outgoing SETUP message, use the h225 timeout setup command in voice class configuration mode. To remove the timeout value, use the no form of this command.

h225 timeout setup seconds

no h225 timeout setup

Syntax Description

Command Default

15 seconds

Command Modes

Voice class configuration

Command History

Examples

The following example configures a timeout setup value of 10 seconds:

Router(config-class)# h225 timeout setup 10

Related Commands

h225 timeout t302

To set the t302 timer when using overlap signaling, use the h225 timeout t302 command in H.225 voice-service configuration mode. To return to the default overlap signaling setting, use the no form of this command

h225 timeout t302 seconds

no h225 timeout t302 seconds

Syntax Description

Command Default

The t302 timer is disabled.

Command Modes

H.323 voice-service configuration

Command History

Usage Guidelines

Use this command to establish the maximum amount of time allowed to complete the dial-peer match when H.225 signal overlap is configured on the originating gateway.

Examples

The following example allows 15 seconds for the t302 timer to complete the dial-peer match before timing out:

Router(config)# voice service voip

Router(conf-voi-serv)# h323

Router(conf-serv-h323)# h225 timeout t302 15

Related Commands

h225 timeout t304

To set the t304 timer when using overlap signaling, use the h225 timeout t304 command in H.323 voice-service configuration mode. To return to the default overlap signaling setting, use the no form of this command.

h225 timeout t304 seconds

no h225 timeout t304 seconds

Syntax Description

Command Default

The timer is enabled and set to 10 seconds.

Command Modes

H.323 voice-service configuration (conf-serv-h323)

Command History

Usage Guidelines

Use the h225 timeout t304 command to configure the maximum interdigit delay on the originating gateway when H.225 overlap signaling is configured. Configure this command for the H.323 call leg on the originating gateway. If this timer expires, the call is disconnected with a cause code 28 (invalid number).

Examples

The following example allows 12 seconds for the t304 timer to complete the dial-peer match before timing out:

Router(config)# voice service voip

Router(conf-voi-serv)# h323

Router(conf-serv-h323)# h225 timeout t304 12

Related Commands

h225 timeout tcp call-idle (H.323 voice-service)

To set a timer for an idle call connection, use the h225 timeout tcp call-idle command in voice service h323 configuration mode. To reset to the default, use the no form of this command.

h225 timeout tcp call-idle {value value | never}

no h225 timeout tcp call-idle

Syntax Description

Command Default

10 minutes

Command Modes

H.323 voice-service configuration

Command History

Usage Guidelines

This command specifies the time to maintain an established H.225 TCP connection when there are no calls on that connection. If the timer expires, the connection is closed. If the timer is running and any new call is made on that connection, the timer stops. When all the calls are cleared on that connection, the timer starts again.

Examples

The following example sets the timer for an idle call connection to 10 minutes:

Router(conf-voi-serv)# h323

Router(conf-serv-h323)# h225 timeout tcp call-idle value 10

Related Commands

h225 timeout tcp establish

To set the H.225 TCP timeout value for Voice over IP (VoIP) dial peers, use the h225 timeout tcp establish command in voice class configuration mode. To reset to the default, use the no form of this command.

h225 timeout tcp establish seconds

no h225 timeout tcp establish

Syntax Description

Command Default

15 seconds

Command Modes

Voice class configuration

Command History

Examples

The following example sets a timeout of 10 seconds, which is associated with the H.323 voice class labeled 1:

voice class h323 1

 h225 timeout tcp establish 10

Related Commands

h225 timeut ntf

To enable Cisco Unified Communications Manager to interpret the calling name coming in the Display IE of H.225 facility message, use the h225 timeout ntf command in voice service or voice class configuration mode. To return to the default configuration, use the no form of this command.

h225 timeout ntf milliseconds

no h225 timeout ntf milliseconds

Syntax Description

Command Default

Disabled. The Cisco Unified Communications Manager ignores the IE and does not display the calling name on the IP phone.

Command Modes

H.323 voice-service configuration (conf-serv-h323)
Voice class configuration (config-class)

Command History

Usage Guidelines

Configure this command on the gateway to control the Q931 setup message. This command is configured in voice service or voice class configuration mode.

When Cisco Unified Communications Manager (Cisco Unified CM) is interworking with Cisco Gateways, The Cisco Unified CM can interpret the calling name coming in Display IE of H.225 Setup and H.225 Notify messages, and display the calling name on the Cisco IP Phone. Calling names sent in Display IE of the H.225 Facility message are not interpreted by default.

When the h225 timeout ntf command is configured on the Cisco gateway, if a Q931 Setup message with name-to-follow comes, the gateway will not send the H.225 Setup message and buffers it until the ntf timer expires, or a Q931 Facility message is received from ISDN side.

Note In the event the facility is received before the timer expires, the gateway will stop the buffer timer, extract the relevent information and send it to terming endpoint.

When a Cisco gateway is connected to ISDN switches that send name-to-follow in Q931 Setup and the calling name in subsequent Q931 Facility message, configuring the h225 timeout ntf command is recommended.

Examples

The following example shows how to set the ntf buffering time to 60 milliseconds in the voice servides configuration mode:

voice service voip

 h323

  h225 timeout ntf 60

The following example sshows hotto se the ntf buffering time to 1000 milliseconds in the voice class configuration mode:

voice class h323 1

 h225 timeout ntf 1000

h245 address-check

To close the TCP connection of the endpoint with the numerically smaller H.245 address when two endpoints simultaneously initiate separate H.245 connections, use the h245 address-check command in H.323 voice-service configuration mode. To return to the default behavior, use the no form of this command.

h245 address-check

no h245 address-check

Syntax Description

This command has no arguments or keywords.

Command Default

The gateway automatically closes its TCP connection when the remote side TCP connection attempts to overwrite the data on the existing gateway TCP connection.

Command Modes

H.323 voice-service configuration (conf-serv-h323)

Command History

Usage Guidelines

The h245 address-check command causes the gateway to use IP addresses to determine which endpoint to close when TCP connections are opened simultaneously. The gateway TCP connection is closed only if the IP address is smaller.

Examples

The following example shows how to close the TCP connection of the endpoint with the numerically smaller H.245 address when two endpoints simultaneously initiate separate H.245 connections

Router(conf-serv-h323)# h245 address-check

Related Commands

h245 passthru

To allow H.245 calls to pass through to the Cisco Unified CallManager when the IP-to-IP gateway sends an incorrect intercluster trunk (ICT) version, use the h245 passthru command in voice service configuration mode. To disable this command use, the no form of this command.

h245 passthru {all | tcsnonstd-passthru}

no h245 passthru {all | tcsnonstd-passthru}

Syntax Description

Command Default

This command is disabled.

Command Modes

Voice service configuration

Command History

Usage Guidelines

When resuming a call that was placed on hold fails on a Cisco Unified CallManager, generally the call fails on the second Cisco Unified CallManager because the IP-to-IP gateway (IPIPGW) sends an incorrect intercluster trunk (ICT) version for the first Cisco Unified CallManager to the second Cisco Unified CallManager, and because the IPIPGW drops the non-standard fields in the callproc, alert, and connect messages from the second Cisco Unified CallManager to the first Cisco Unified CallManager. To resolve this behavior configure the h245 passthru command

Note For IP-to-IP gateway functionality the allow-connections h323 to h323 command must be configured.

Examples

The following example show how you configure h.245 to pass through to the Cisco Unified CallManager, regardless of the intercluster trunk (ICT) version:

Router(conf-serv-h323)#h245 passthru tcsnonstd-passthru 

Related Commands

h245 timeout olc

To set the timeout value for the OpenLogicalChannel (OLC) message, use the h245 timeout olc command in H.323 voice-service configuration mode. To disable the timeout value for the OLC message, use the no form of this command.

h245 timeout olc timeout value

no h245 timeout olc timeout value

Syntax Description

Command Default

Timeout value for the OLC message is enabled and set to 4 seconds.

Command Modes

H.323 voice-service configuration

Command History

Usage Guidelines

After the originating gateway sends an OLC message during the H.245 procedure, it waits for 4 seconds for the terminating gateway to respond with an OLC acknowledgment. This behavior is enabled by default, and the timeout value of the OLC message is set to 4 seconds.

However, sometimes when a slow link, such as a satellite link, is involved in sending messages, a delay can occur. In that case, 4 seconds are not enough to receive OLC messages, and the call fails even when the terminating gateway had responded with OLC acknowledgment. To avoid the random dropping of VoIP calls, use the h245 timeout olc command to change the length of time that the originating gateway waits for OLC acknowledgment from the terminating gateway.

Examples

The following example sets the timeout value for the OLC message to 20 seconds. It also shows that you can change the setting to 15 seconds:

h245 timeout olc 20

h245 timeout olc 15

The following example sets the timeout value back to the default setting of 4 seconds:

no h245 timeout olc 15

The output of the show run command does not show the default setting; however, it does include the command if the timeout value is modified:

voice service voip 

 h323

  h245 timeout olc 20

Related Commands

h323

To enable the H.323 voice service configuration commands, use the h323 command in voice service configuration mode.

h323

Syntax Description

This command has no arguments or keywords.

Command Default

No default behavior or values

Command Modes

Voice service configuration

Command History

Examples

The following example enters H.323 voice service configuration mode:

Router(conf-voi-serv)# h323

Related Commands

h323 asr

To enable application-specific routing (ASR) and specify the maximum bandwidth for a proxy, use the h323 asr command in interface configuration mode. To remove a bandwidth setting but keep ASR enabled, use no form of this command.

h323 asr [bandwidth max-bandwidth]

no h323 asr [bandwidth max-bandwidth]

Syntax Description

Command Default

ASR is disabled.

Command Modes

Interface configuration

Command History

Usage Guidelines

This command is independent of the h323 interface command.

Note Specifying the no h323 asr bandwidth max-bandwidth command removes the bandwidth setting but leaves ASR enabled. You must enter the no h323 asr command to disable ASR.

Examples

The following example enables ASR and specifies a maximum bandwidth of 10,000 kbps:

h323 asr bandwidth 10000

h323 call start

To force the H.323 Version 2 gateway to use Fast Connect or Slow Connect procedures for all H.323 calls, use the h323 call start command in voice-service configuration mode. To reset to the default, use the no form of this command.

h323 call start {fast | slow}

no h323 call start

Syntax Description

Command Default

fast

Command Modes

Voice-service configuration

Command History

Usage Guidelines

In Cisco IOS Release 12.1(3)XI and later releases, H.323 Voice over IP (VoIP) gateways by default use H.323 Version 2 (Fast Connect) for all calls including those initiating RSVP. Previously, gateways used only Slow Connect procedures for RSVP calls. To enable Cisco IOS Release 12.1(3)XI gateways to be backward compatible with earlier releases of Cisco IOS Release 12.1 T, the h323 call start command forces the originating gateway to initiate calls using Slow Connect.

This h323 call start command is configured as part of the global voice-service configuration for VoIP services. It does not take effect unless the call start system voice-class configuration command is configured in the VoIP dial peer.

Examples

The following example selects Slow Connect procedures for the gateway:

voice service voip

 h323 call start slow

Related Commands

h323 gatekeeper

To specify the gatekeeper associated with a proxy and to control how the gatekeeper is discovered, use the h323 gatekeeper command in interface configuration mode. To disassociate the gatekeeper, use the no form of this command.

h323 gatekeeper [id gatekeeper-id] {ipaddr ipaddr [port] | multicast}

no h323 gatekeeper [id gatekeeper-id] {ipaddr ipaddr [port] | multicast}

Syntax Description

Command Default

No gatekeeper is configured for the proxy

Command Modes

Interface configuration

Command History

Usage Guidelines

You must enter the h323 interface and h323 h323-id commands before using this command. The h323 gatekeeper command must be specified on your Cisco IOS platform or the proxy does not go online. The proxy uses the interface address as its RAS signaling address.

Examples

The following example sets up a unicast discovery to a gatekeeper whose name is unknown:

h323 gatekeeper ipaddr 192.168.5.2

The following example sets up a multicast discovery for a gatekeeper of a particular name:

h323 gatekeeper id gk.zone5.com multicast

Related Commands

h323 h323-id

To register an H.323 proxy alias with a gatekeeper, use the h323 h323-id command in interface configuration mode. To remove an H.323 proxy alias, use the no form of this command.

h323 h323-id h323-id

no h323 h323-id h323-id

Syntax Description

Command Default

No H.323 proxy alias is registered

Command Modes

Interface configuration

Command History

Usage Guidelines

Each entry registers a specified H.323 ID proxy alias to a gatekeeper. Typically, these aliases are either simple text strings or legitimate e-mail IDs.

Note You must enter the h323 interface command before using this command. The h323 h323-id command must be entered on the same interface as the h323 gatekeeper command. The proxy does not go online without the h323 interface command.

Examples

The following example registers an H.323 proxy alias called proxy1@zone5.com with a gatekeeper:

h323 h323-id proxy1@zone5.com

Related Commands

h323 interface

To select an interface whose IP address is used by the proxy to register with the gatekeeper, use the h323 interface command in interface configuration mode. To reset to the default port, use the no version of the command and then the h323 interface command.

h323 interface [port-number]

no h323 interface [port-number]

Syntax Description

Command Default

Default port number is image dependent as described in the Syntax Description.

Command Modes

Interface configuration

Command History

Usage Guidelines

At proxy startup, Cisco IOS software checks for the presence of the VoIP gateway subsystem. If the subsystem is found to be present, the proxy code opens and listens for call setup requests on the new port. The proxy then registers this port with the gatekeeper.

Examples

The following example configures Ethernet interface 0 for incoming call-setup requests:

interface ethernet0

 h323 interface

Related Commands

h323 qos

To enable quality of service (QoS) on the proxy, use the h323 qos command in interface configuration mode. To disable QoS, use the no form of this command.

h323 qos {ip-precedence value | rsvp {controlled-load | guaranteed-qos}}

no h323 qos {ip-precedence value | rsvp {controlled-load | guaranteed-qos}}

Syntax Description

Command Default

No QoS is configured

Command Modes

Interface configuration

Command History

Usage Guidelines

You must execute the h323 interface command before using this command.

Both IP precedence and RSVP QoS can be configured by invoking this command twice with the two different QoS forms.

Examples

The following example enables QoS on the proxy:

interface Ethernet0

 ip address 172.21.127.38 255.255.255.192

 no ip redirects

 ip rsvp bandwidth 7000 7000

 ip route-cache same-interface

 fair-queue 64 256 1000

 h323 interface

 h323 qos rsvp controlled-load

 h323 h323-id px1@zone1.com

 h323 gatekeeper ipaddr 172.21.127.39

Related Commands

h323 t120

To enable the T.120 capabilities on your router and to specify bypass or proxy mode, use the h323 t120 command in interface configuration mode.

h323 t120 {bypass | proxy}

Syntax Description

Command Default

Bypass mode

Command Modes

Interface configuration

Command History

Usage Guidelines

The no form of this command has no function—the only possible commands are h323 t120 bypass and h323 t120 proxy.

Examples

The following example enables T.120 capabilities:

proxy h323

interface ethernet0

 h323 t120 proxy

Related Commands

h323-annexg

To enable the border element (BE) on the gatekeeper and to enter BE configuration mode, use the h323-annexg command in gatekeeper configuration mode. To disable the BE, use the no form of this command.

h323-annexg border-element-id cost cost priority priority

no h323-annexg

Syntax Description

Command Default

Cost: 50
Priority: 50

Command Modes

Gatekeeper configuration

Command History

Usage Guidelines

The Annex G border element must be configured using the call-router command before the gatekeeper can be associated with the Annex G border element. The h323-annexg command associates the gatekeeper with a previously configured Annex G border element and indicates that the gatekeeper should interact with the BE in address resolution.

Examples

The following example enables Annex G configuration for a BE named "be20":

Router(config-gk)# h323-annexg be20 cost 10 priority 40

Router(config-gk-annexg)#

Related Commands

h323-gateway voip bind srcaddr

To designate a source IP address for the voice gateway, use the h323-gateway voip bind srcaddr command in interface configuration mode. To remove the source IP address, use the no form of the command.

h323-gateway voip bind srcaddr ip-address

no h323-gateway voip bind srcaddr

Syntax Description

Command Default

No default behaviors or values

Command Modes

Interface configuration

Command History

Usage Guidelines

You do not have to issue this command on the interface that you defined as the voice gateway interface (although it may be more convenient to do so). Use this command the interface that contains the IP address to which you want to bind.

Examples

The following example assigns a source IP address of 10.1.1.1:

h323-gateway voip bind srcaddr 10.1.1.1

h323-gateway voip h323-id

To configure the H.323 name of the gateway that identifies this gateway to its associated gatekeeper, use the h323-gateway voip h323-id command in interface configuration mode. To disable this defined gateway name, use the no form of this command.

h323-gateway voip h323-id interface-id

no h323-gateway voip h323-id interface-id

Syntax Description

Command Default

No gateway identification is defined

Command Modes

Interface configuration

Command History

Examples

The following example configures Ethernet interface 0.0 as the gateway interface. In this example, the gateway ID is GW13@cisco.com.

interface Ethernet0/0

 ip address 172.16.53.13 255.255.255.0

 h323-gateway voip interface

 h323-gateway voip id GK15.cisco.com ipaddr 172.16.53.15 1719

 h323-gateway voip h323-id GW13@cisco.com

 h323-gateway voip tech-prefix 13#

Related Commands

h323-gateway voip id

To define the name and location of the gatekeeper for a specific gateway, use the h323-gateway voip id command in interface configuration mode. To disable this gatekeeper identification, use the no form of this command.

h323-gateway voip id gatekeeper-id {ipaddr ip-address [port-number] | multicast}
[priority number]

no h323-gateway voip id gatekeeper-id {ipaddr ip-address [port-number] | multicast}
[priority number]

Syntax Description

Command Default

No gatekeeper identification is defined.

Command Modes

Interface configuration

Command History

Usage Guidelines

This command tells the H.323 gateway associated with this interface which H.323 gatekeeper to talk to and where to locate it. The gatekeeper ID configured here must exactly match the gatekeeper ID in the gatekeeper configuration.

You can configure one or two alternate gatekeepers.

The IP address of the gatekeeper does not have to be explicit; you can also use the multicast option. Multicasting saves bandwidth by forcing the network to replicate packets only when necessary. The multicast option, shown below, notifies every gatekeeper in the LAN using a universal address, 224.0.1.41.

h323-gateway voip id GK1 multicast 
h323-gateway voip id GK2 ipaddr 172.18.193.65 1719

Examples

The following example configures Ethernet interface 0.0 as the gateway interface and defines a specific gatekeeper for it. In this example, the gatekeeper ID is GK15.cisco.com, and its IP address is 172.16.53.15 (using port 1719).

interface Ethernet0/0

 ip address 172.16.53.13 255.255.255.0

 h323-gateway voip interface

 h323-gateway voip id GK15.cisco.com ipaddr 172.16.53.15 1719

 h323-gateway voip h323-id GW13@cisco.com

 h323-gateway voip tech-prefix 13#

Related Commands

h323-gateway voip interface

To configure an interface as an H.323 gateway interface, use the h323-gateway voip interface command in interface configuration mode. To disable H.323 gateway functionality for an interface, use the no form of this command.

h323-gateway voip interface

no h323-gateway voip interface

Syntax Description

This command has no arguments or keywords.

Command Default

Disabled

Command Modes

Interface configuration

Command History

Examples

The following example configures Ethernet interface 0.0 as the gateway interface. In this example, the h323-gateway voip interface command configures this interface as an H.323 interface.

interface Ethernet0/0

 ip address 172.16.53.13 255.255.255.0

 h323-gateway voip interface

 h323-gateway voip id GK15.cisco.com ipaddr 172.16.53.15 1719

 h323-gateway voip h323-id GW13@cisco.com

 h323-gateway voip tech-prefix 13#

Related Commands

h323-gateway voip tech-prefix

To define the technology prefix that the gateway registers with the gatekeeper, use the h323-gateway voip tech-prefix command in interface configuration mode. To disable this defined technology prefix, use the no form of this command.

h323-gateway voip tech-prefix prefix

no h323-gateway voip tech-prefix prefix

Syntax Description

Command Default

Disabled

Command Modes

Interface configuration

Command History

Usage Guidelines

This command defines a technology prefix that the gateway then registers with the gatekeeper. Technology prefixes can be used as a discriminator so that the gateway can tell the gatekeeper that a certain technology is associated with a particular call (for example, 15# could mean a fax transmission), or it can be used like an area code for more generic routing. No standard currently defines what the numbers in a technology prefix mean. By convention, technology prefixes are designated by a pound sign (#) as the last character.

Note Cisco gatekeepers use the asterisk (*) as a reserved character. If you are using Cisco gatekeepers, do not use the asterisk as part of the technology prefix.

Examples

The following example configures Ethernet interface 0.0 as the gateway interface. In this example, the technology prefix is defined as 13#.

interface Ethernet0/0

 ip address 172.16.53.13 255.255.255.0

 h323-gateway voip interface

 h323-gateway voip id GK15.cisco.com ipaddr 172.16.53.15 1719

 h323-gateway voip h323-id GW13@cisco.com

 h323-gateway voip tech-prefix 13#

Related Commands

h323zone-id (voice source group)

To specify the zone identification for an incoming H.323 call, use the h323zone-id command in voice source-group configuration mode. To delete the zone ID, use the no form of this command.

h323zone-id name

no h323zone-id name

Syntax Description

Command Default

No default behavior or values

Command Modes

Voice source-group configuration

Command History

Usage Guidelines

Use this command to specify the zone to use for incoming H.323 calls in the voice source-group definition. The zone ID name matches the source zone ID of an incoming H.323 call.

Note The SIP protocol does not support zone ID functionality.

Examples

The following example associates zone ID "5400-gw1" with incoming calls for source IP group "northcal":

Router(config)# voice source-group northcal

Router(cfg-source-grp)# h323zone-id 5400-gw1

Related Commands

h450 h450-3 timeout

To specify timeout values for call forwarding using the ITU-T H.450.3 standard, use the h450 h450-3 timeout command in H.323 voice service configuration mode. To return to the default, use the no form of this command.

h450 h450-3 timeout T1 milliseconds

no h450 h450-3 timeout T1

Syntax Description

Command Default

T1 timer is 5000 milliseconds.

Command Modes

H323 voice service configuration

Command History

Usage Guidelines

Use this command with Cisco IOS Telephony Service (ITS) V2.1 or a later version.

This command is primarily used when the default setting for this timer does not match your network delay parameters. Refer to the ITU-T H.450.3 specification for more information on these timers.

Examples

The following example defines a T1 timeout of 3000 milliseconds:

Router(config)# voice service voip

Router(conf-voi-serv)# h323

Router(conf-serv-h323)# h450 h450-3 timeout T1 3000

Related Commands

handle-replaces

To configure a Cisco IOS device to handle Session Initiation Protocol (SIP) INVITE with Replaces header messages at the SIP protocol level, use the handle-replaces command in SIP UA configuration mode. To return to the default handling of SIP INVITE with Replaces header messages where messages are handled at the application layer, use the no form of this command.

handle-replaces

no handle-replaces

Syntax Description

This command has no arguments or keywords.

Command Default

Handling of SIP INVITE with Replaces header messages takes place at the application layer.

Command Modes

SIP UA configuration (config-sip-ua)

Command History

Usage Guidelines

On Cisco IOS devices running software earlier than Cisco IOS Release 12.4(22)T, SIP INVITE with Replaces header messages (such as those associated with Call Replacement during a Consult Call transfer scenario) are handled at the SIP protocol level. Beginning with Cisco IOS Release 12.4(22)T, the default behavior is for Cisco IOS devices to handle SIP INVITE with Replaces header messages at the application layer. To configure your Cisco IOS device to handle SIP INVITE with Replaces header messages at the SIP protocol level, use the handle-replaces command in SIP UA configuration mode.

Examples

The following example shows how to configure fallback to legacy handling of SIP INVITE messages:

Router(config)# sip-ua

Router(config-sip-ua)# handle-replaces

Related Commands

hangup-last-active-call

To define a Feature Access Code (FAC) to access the Hangup Last Active Call feature in feature mode on analog phones connected to FXS ports, use the hangup-last-active-call command in STC application feature-mode call-control configuration mode. To return the code to its default, use the no form of this command.

hangup-last-active-call keypad-character

no hangup-last-active-call

Syntax Description

Command Default

The default value is #1.

Command Modes

STC application feature-mode call-control configuration (config-stcapp-fmcode)

Command History

Usage Guidelines

This command changes the value of the FAC for the Hangup Last Active Call feature from the default (#1) to the specified value.

If you attempt to configure this command with a value that is already configured for another FAC in feature mode, you receive a message. This message will not prevent you from configuring the feature code. If you configure a duplicate FAC, the system implements the first feature it matches in the order of precedence as determined by the value for each FAC (#1 to #5).

If you attempt to configure this command with a value that precludes or is precluded by another FAC in feature mode, you receive a message. If you configure a FAC to a value that precludes or is precluded by another FAC in feature mode, 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. These messages will not prevent you from configuring the feature code. You must configure a new value for the precluded code in order to enable phone user access to that feature.

Note For analog phones connected to FXS ports in Cisco Unified Communications Manager Express (CME), the keep-conference drop-last command must be enabled on the Cisco router.

Examples

The following example shows how to change the value of the feature code for the Hangup Last Active Call feature from the default (#1). With this configuration, a phone user must press hook flash during a three-party conference to get the feature tone and then dial 11 to drop the last active call party. The conference becomes a basic call.

Router(config)# stcapp call-control mode feature

Router(config-stcapp-fmcode)# hangup-last-active-call 11

Router(config-stcapp-fmcode)# exit

Related Commands

header-passing

To enable the passing of headers to and from Session Initiation Protocol (SIP) INVITE, SUBSCRIBE, and NOTIFY messages, use the header-passing command in voice service voip sip configuration mode. To disable header passing, use the no form of this command.

header-passing

no header-passing

Syntax Description

This command has no arguments or keywords.

Command Default

Disabled

Command Modes

voice service voip sip configuration

Command History

Usage Guidelines

•This command applies to all SIP VoIP dial peers configured on a gateway. It enables header passing for SIP INVITE, SUBSCRIBE and NOTIFY messages; disabling header passing affects only incoming INVITE messages.

•There is no command to enable header passing on a per-call or per-application basis.

•Enabling header passing results in a slight increase in memory and CPU utilization.

Examples

The following example shows header-passing enabled:

Router(conf-serv-sip)# header-passing

Related Commands

history-info

To enable Session Initiation Protocol (SIP) history-info header support on Cisco IOS gateway at a global level, use the history-info command in voice service voip sip configuration mode. To disable SIP history-info header support, use the no form of this command.

history-info

no history-info

Syntax Description

This command has no keywords or arguments.

Command Default

History-info header support is disabled.

Command Modes

Voice service voip sip configuration (conf-serv-sip)

Command History

Usage Guidelines

Use this command to enable history-info header support at a global level. The history-info header (as defined in RFC 4244) records the call or dialog history. The receiving application uses the history-info header information to determine how and why the call has reached it.

Note The Cisco IOS SIP gateway cannot use the information in the history-info header to make routing decisions.

Examples

The following example enables SIP history-info header support:

Router(config)# voice service voip

Router(conf-voi-serv)# sip

Router(conf-serv-sip)# history-info

Related Commands

history session event-log save-exception-only

To save in history only the event logs for application sessions that have at least one error, use the history session event-log save-exception-only command in application configuration monitor mode. To reset to the default, use the no form of this command.

history session event-log save-exception-only

no history session event-log save-exception-only

Syntax Description

This command has no arguments or keywords.

Command Default

All event logs for sessions are saved to history.

Command Modes

Application configuration monitor

Command History

Usage Guidelines

Application event logs move from active to history after an instance terminates. If you use this command, the voice gateway saves event logs only for instances that had one or more errors. Event logs for normal instances that do not contain any errors are not saved to history.

Note This command does not affect records saved to an FTP server by using the dump event-log command.

Examples

The following example saves an event log in history only if the instance had an error:

application

 monitor

 history session event-log save-exception-only

Related Commands

history session max-records

To set the maximum number of application instance records saved in history, use the history session max-records command in application configuration monitor mode. To reset to the default, use the no form of this command.

history session max-records number

no history session max-records

Syntax Description

Command Default

360

Command Modes

Application configuration monitor

Command History

Usage Guidelines

This command affects the number of records that display when you use the show call application history session-level command.

Examples

The following example sets the maximum record limit to 500:

application

 monitor

 history session max-records 500

Related Commands

history session retain-timer

To set the maximum number of minutes for which application instance records are saved in history, use the history session retain-timer command in application configuration monitor mode. To reset to the default, use the no form of this command.

history session retain-timer minutes

no history session retain-timer

Syntax Description

Command Default

15

Command Modes

Application configuration mode

Command History

Usage Guidelines

This command affects the number of records that display when you use the show call application history session-level command.

To enable event logging for voice applications, use the event-log command.

Examples

The following example sets the maximum time to save history records to 1 hour:

application

 monitor

 history session retain-timer 60

Related Commands

hold-resume

To enable the Hold/Resume STC application supplementary-service feature on an FXS port, use the hold-resume command in supplementary-service voice-port configuration mode. To disable, use the no form of this command.

hold-resume

no hold-resume

Syntax Description

This command has no arguments or keywords.

Command Default

Feature is disabled.

Command Modes

Supplementary-service voice-port configuration (config-stcapp-suppl-serv-port)

Command History

Usage Guidelines

This command enables the Hold/Resume STC application supplementary-service feature on analog endpoints that are connected to FXS ports on a Cisco IOS voice gateway, such as a Cisco integrated services router (ISR) or Cisco VG224 Analog Phone Gateway.

Examples

The following example shows how to enable Hold/Resume on port 2/0 on a Cisco VG 224.

Router(config)# stcapp supplementary-services

Router(config-stcapp-suppl-serv)# port 2/0

Router(config-stcapp-suppl-serv-port)# hold-resume

Router(config-stcapp-suppl-serv-port)# end

Related Commands

hopcount

To specify the maximum number of border element (BE) hops through which an address resolution request can be forwarded, use the hopcount command in Annex G configuration mode. To restore the default, use the no form of this command.

hopcount hopcount-value

no hopcount

Syntax Description

Command Default

7 hops

Command Modes

Annex G configuration

Command History

Examples

The following example sets address-resolution forwarding to a maximum of 10 hops:

Router(config)# call-router h323-annexg be20

Router(config-annexg)# hopcount 10

Related Commands

host (SIP URI)

To match a call based on the host field, a valid domain name, IPv4 address, IPv6 address, or the complete domain name in a Session Initiation Protocol (SIP) uniform resource identifier (URI), use the host command in voice URI class configuration mode. To remove the host match, use the no form of this command.

host {ipv4:ipv4-address | ipv6:ipv6-address | dns:dns-name | hostname-pattern}

no host

Syntax Description

Command Default

The calls are not matched on the host field, IPv4 address, IPv6 address, valid domain name, or complete domain name in the SIP URI.

Command Modes

Voice URI class configuration (config-voice-uri-class)

Command History

Usage Guidelines

You can use this command only in a voice class for SIP URIs.

You cannot use this command if you use the pattern command in the voice class. The pattern command matches on the entire URI, whereas this command matches only a specific field.

You can configure ten instances of the host command by specifying IPv4 addresses, IPv6 addresses, or domain name service (DNS) names for each instance. You can configure the host command specifying the hostname-pattern argument only once.

Examples

The following example defines a voice class that matches on the host field in a SIP URI:

voice class uri r100 sip

 user-id abc123 

 host server1

 host ipv4:10.0.0.0

 host ipv6:[2001:0DB8:0:1:FFFF:1234::5] 

 host dns:example.sip.com

 phone context 408

Related Commands

host-registrar

To populate the sip-ua registrar domain name or IP address value in the host portion of the diversion header and to redirect the contact header of the 302 response, use the host-registrar command in SIP user-agent configuration mode. To remove the sip-ua registrar domain name or IP address from the host portion of the diversion and redirect contact headers, use the no form of this command.

host-registrar