Table Of Contents

Configuring Call Transfer and Forwarding

Contents

Information About Call Transfer and Forwarding

Call Forwarding

B2BUA Call Forwarding for SIP Devices

Call Forward All Synchronization for SIP Phones

Call Transfer

H.450.2 and H.450.3 Support

Transfer Method Recommendations by Cisco Unified CME Version

H.450.12 Support

Hairpin Call Routing

H.450 Tandem Gateways

Dial Peers

QSIG Supplementary Services

Disabling SIP Supplementary Services for Call Forward and Call Transfer

Typical Network Scenarios for Call Transfer and Call Forwarding

How to Configure Call Transfer and Forwarding

Enabling Call Transfer and Forwarding at System-Level

SCCP: Enabling Call Forwarding for a Directory Number

SCCP: Enabling Call Transfer for a Directory Number

SCCP: Configuring Call Transfer Options for Phones

SCCP: Verifying Call Transfer

Enabling H.450.12 Capabilities

Enabling H.323-to-H.323 Connection Capabilities

Forwarding Calls Using Local Hairpin Routing

Enabling H.450.7 and QSIG Supplementary Services at a System-Level

Enabling H.450.7 and QSIG Supplementary Services on a Dial Peer

Disabling SIP Supplementary Services for Call Forward and Call Transfer

Enabling Interworking with Cisco Unified Communications Manager

SIP: Configuring SIP-to-SIP Phone Call Forwarding

SIP: Configuring Call-Forwarding-All Soft Key URI

SIP: Specifying Number of 3XX Responses To be Handled

SIP: Configuring Call Transfer

Configuration Examples for Call Transfer and Forwarding

H.450.2 and H.450.3: Example

Basic Call Forwarding: Example

Call Forwarding Blocked for Local Calls: Example

Selective Call Forwarding: Example

Call Transfer: Example

H.450.12: Example

H.450.7 and QSIG Supplementary Services: Example

Cisco Unified CME and Cisco Unified Communications Manager in Same Network: Example

H.450 Tandem Gateway Working with Cisco Unified CME and Cisco Unified Communications Manager: Example

Forwarding Calls to Cisco Unity Express: Example

Where to Go Next

Additional References

Related Documents

Technical Assistance

Feature Information for Call Transfer and Forwarding

Configuring Call Transfer and Forwarding

---

Last Updated: May 23, 2007

This chapter describes call transfer and forwarding features in Cisco Unified Communications Manager Express (Cisco Unified CME) to enable interworking with various network requirements.

Finding Feature Information in This Module

Your Cisco Unified CME version may not support all of the features documented in this module. For a list of the versions in which each feature is supported, see the "Feature Information for Call Transfer and Forwarding" section.

Contents

• Information About Call Transfer and Forwarding

• How to Configure Call Transfer and Forwarding

• Configuration Examples for Call Transfer and Forwarding

• Where to Go Next

• Additional References

• Feature Information for Call Transfer and Forwarding

Information About Call Transfer and Forwarding

To configure transfer and forwarding features, you should understand the following concepts:

• Call Forwarding

• B2BUA Call Forwarding for SIP Devices

• Call Forward All Synchronization for SIP Phones

• Call Transfer

• H.450.2 and H.450.3 Support

• Transfer Method Recommendations by Cisco Unified CME Version

• H.450.12 Support

• Hairpin Call Routing

• H.450 Tandem Gateways

• Dial Peers

• QSIG Supplementary Services

• Disabling SIP Supplementary Services for Call Forward and Call Transfer

• Typical Network Scenarios for Call Transfer and Call Forwarding

Call Forwarding

Call forwarding diverts calls to a specified number under one or more of the following conditions:

•All calls—When all-call call forwarding is activated by a phone user, all incoming calls are diverted. The target destination for diverted calls can be specified in the router configuration or by the phone user with a soft key or feature access code. The most recently entered destination is recognized by Cisco Unified CME, regardless of how it was entered.

•No answer—Incoming calls are diverted when the extension does not answer before the timeout expires. The target destination for diverted calls is specified in the router configuration.

•Busy—Incoming calls are diverted when the extension is busy and call waiting is not active. The target destination for diverted calls is specified in the router configuration.

•Night service—All incoming calls are automatically diverted during night-service hours. The target destination for diverted calls is specified in the router configuration.

A directory number can have all four types of call forwarding defined at the same time with a different forwarding destination defined for each type of call forwarding. If more than one type of call forwarding is active at one time, the order for evaluating the different types is as follows:

1. Call forward night-service

2. Call forward all

3. Call forward busy and call forward no-answer

H.450.3 capabilities are enabled globally on the router by default, and can be disabled either globally or for individual dial peers. You can configure incoming patterns for using the H.450.3 standard. Calling-party numbers that do not match the patterns defined with this command are forwarded using Cisco-proprietary call forwarding for backward compatibility. For information about configuring H.450.3 on a Cisco Unified CME system, see the "SCCP: Enabling Call Forwarding for a Directory Number" section.

Selective Call Forwarding

You can apply call forwarding to a busy or no-answer directory number based on the number that is dialed to reach the directory number: the primary number, the secondary number, or either of those numbers expanded by a dial-plan pattern.

Cisco Unified CME automatically creates one POTS dial peer for each ephone-dn when it is assigned a primary number. If the ephone-dn is assigned a secondary number, it creates a second POTS dial peer. If the dialplan-pattern command is used to expand the primary and secondary numbers for ephone-dns, it creates two more dial peers, resulting in the creation of the following four dial peers for the ephone-dn:

•A POTS dial peer for the primary number

•A POTS dial peer for the secondary number

•A POTS dial peer for the primary number as expanded by the dialplan-pattern command

•A POTS dial peer for the secondary number as expanded by the dialplan-pattern command

Call forwarding is normally applied to all dial peers created for an ephone-dn. Selective call forwarding allows you to apply call forwarding for busy or no-answer calls only for the dial peers you have specified, based on the called number that was used to route the call to the ephone-dn.

For example, the following commands set up a single ephone-dn (ephone-dn 5) with four dial peers:

telephony-service

 dialplan-pattern 1 40855501.. extension-length 4 extension-pattern 50..




ephone-dn 5

 number 5066 secondary 5067




In this example, selective call forwarding can be applied so that calls are forwarded when:

•callers dial the primary number 5066.

•when callers dial the secondary number 5067.

•when callers dial the expanded numbers 4085550166 or 4085550167.

For configuration information, see the "SCCP: Enabling Call Forwarding for a Directory Number" section.

B2BUA Call Forwarding for SIP Devices

Cisco Unified CME 3.4 an d later versions acts as both UA server and UA client; that is, as a B2BUA. Calls into a SIP phone can be forwarded to other SIP or SCCP devices (including Cisco Unity or Cisco Unity Express, third-party voice mail systems, an auto attendant or an IVR system, such as Cisco Unified IPCC and Cisco Unified IPCC Express). In addition, SCCP phones can be forwarded to SIP phones.

Cisco Unity or other voice-messaging systems connected by a SIP trunk or SIP user agent are able to pass an MWI to a SIP phone when a call is forwarded. The SIP phone then displays the MWI when indicated by the voice-messaging system.

The call-forward busy response is triggered when a call is sent to a SIP phone using a VoIP dial peer and a busy response is received back from the phone. SIP-to-SIP call forwarding is invoked only if the phone is dialed directly. Call forwarding is not invoked when the phone number is called through a sequential, longest-idle, or peer hunt group.

You can configure call forwarding for an individual directory number, or for every number on a SIP phone. If the information is configured in both, the information under voice register dn takes precedence over the information configured under voice register pool.

For configuration information, see the "SIP: Configuring SIP-to-SIP Phone Call Forwarding" section.

Call Forward All Synchronization for SIP Phones

The Call Forward All feature allows users to forward all incoming calls to a phone number that they specify. This feature is supported on all SIP phones and can be provisioned from either Cisco Unified CME or the individual SIP phone. Before Cisco Unified CME 4.1, there was no method for exchanging the Call Forward All configuration between Cisco Unified CME and the SIP phone. If Call Forward All was enabled on the phone, the configuration in Cisco Unified CME was not updated; conversely, the configuration in Cisco Unified CME was not sent to the phone.

In Cisco Unified CME 4.1 and later, the following enhancements are supported for the Cisco Unified IP Phone 7911G, 7941G, 7941GE, 7961G, 7961GE, 7970G, and 7971GE to keep the configuration consistent between Cisco Unified CME and the SIP phone:

•When Call Forward All is configured on Cisco Unified CME with the call-forward b2bua all command, the configuration is sent to the phone which updates the CfwdAll soft key to indicate that Call forward All is enabled. Because Call Forward All is configured on a per line basis, the CfwdAll soft key is updated only when Call Forward All is enabled for the primary line.

•When a user enables Call Forward All on a phone using the CfwdAll soft key, the uniform resource identifier (URI) for the service (defined with the call-feature-uri command) and the call forward number (unless Call Forward All is disabled) is sent to Cisco Unified CME. It updates its voice register pool and voice register dn configuration with the call-forward b2bua all command to be consistent with the phone configuration.

•Call Forward All supports KPML so that a user does not need to press the Dial or # key, or wait for the interdigit timeout, to configure the Call Forward All number. Cisco Unified CME collects the Call Forward All digits until it finds a match in the dial peers.

For configuration information, see the "SIP: Configuring Call-Forwarding-All Soft Key URI" section.

Call Transfer

When you are connected to another party, call transfer allows you to shift the connection of the other party to a different number. Call transfer methods must interoperate with systems in the other networks with which you interface. Cisco CME 3.2 and later versions provide full call-transfer and call-forwarding interoperability with call processing systems that support H.450.2, H.450.3, and H.450.12 standards. For call processing systems that do not support H.450 standards, Cisco CME 3.2 and later versions provide VoIP-to-VoIP hairpin call routing.

Call transfers can be blind or consultative. A blind transfer is one in which the transferring extension connects the caller to a destination extension before ringback begins. A consultative transfer is one in which the transferring party either connects the caller to a ringing phone (ringback heard) or speaks with the third party before connecting the caller to the third party.

You can configure blind or consultative transfer on a systemwide basis or for individual extensions. For example, in a system that is set up for consultative transfer, a specific extension with an auto-attendant that automatically transfers incoming calls to specific extension numbers can be set to use blind transfer, because auto-attendants do not use consultative transfer.

Consultative Transfer With Direct Station Select

Direct Station Select (DSS) is a feature that allows a multibutton phone user to transfer calls to an idle monitored line by pressing the Transfer key and the appropriate monitored line button. A monitored line is one that appears on two phones; one phone can use the line to make and receive calls and the other phone simply monitors whether the line is in use. For Cisco CME 3.2 and later versions, consultative transfers can occur during Direct Station Select (transferring calls to idle monitored lines).

If the person sharing the monitored line does not want to accept the call, the person announcing the call can reconnect to the incoming call by pressing the EndCall soft key to terminate the announcement call and pressing the Resume soft key to reconnect to the original caller.

Direct Station Select consultative transfer is enabled with the transfer-system full-consult dss command, which defines the call transfer method for all lines served by the router. The transfer-system full-consult dss command supports the keep-conference command. See "Configuring Conferencing".

Call Transfer Blocking

Transfers to all numbers except those on local phones are automatically blocked by default. During configuration, you can allow transfers to nonlocal numbers. In Cisco Unified CME 4.0 and later versions, you can prevent individual phones from transferring calls to numbers that are globally enabled for transfer. This ensures that individual phones do not incur toll charges by transferring calls outside the Cisco Unified CME system. Call transfer blocking can be configured for individual phones or configured as part of a template that is applied to a set of phones.

Another way to eliminate toll charges on call transfers is to limit the number of digits that phone users can dial when transferring calls. For example, if you specify a maximum of eight digits in the configuration, users who are transferring calls can dial one digit for external access and seven digits more, which is generally enough for a local number but not a long-distance number. In most locations, this plan will limit transfers to nontoll destinations. Long-distance calls, which typically require ten digits or more, will not be allowed. This configuration is only necessary when global transfer to numbers outside the Cisco Unified CME system has been enabled using the transfer-pattern (telephony-service) command. Transfers to numbers outside the Cisco Unified CME system are not permitted by default.

H.450.2 and H.450.3 Support

H.450.2 is a standard protocol for exchanging call-transfer information across a network, and H.450.3 is a standard protocol for exchanging call-forwarding information across a network. Cisco CME 3.0 and later versions support the H.450.2 call-transfer standards and the H.450.3 call-forwarding standards that were introduced in Cisco ITS V2.1. Using the H.450.2 and H.450.3 standards to manage call transfer and forwarding in a VoIP network provides the following benefits:

•The final call path from the transferred party to the transfer destination is optimal, with no hairpinned routes or excessive use of resources.

•Call parameters (for example, codec) can be different for the different call legs.

•This solution is scalable.

•There is no limit to the number of times a call can be transferred.

Considerations for using the H.450.2 and H.450.3 standards include the following:

•Cisco IOS Release 12.2(15)T or a later release is required on all voice gateways in the network.

•Support of H.450.2 and H.450.3 is required on all voice gateways in the network. H.450.2 and H.450.3 are used regardless of whether the transfer-to or forward-to target is on the same Cisco Unified CME system as the transferring party or the forwarding party, so the transferred party must also support H.450.2 and the forwarded party must also support H.450.3. The exception is calls that can be reoriginated through hairpin call routing or through the use of an H.450 tandem gateway.

•Call forwarding over SIP networks uses the 302 Moved Temporarily SIP response, which works in a manner similar to the way in which the H.450.3 standard is used for H.323 networks. To enable call forwarding, you must specify a pattern that matches the calling-party numbers of the calls that you want to be able to forward.

•Cisco Unified CME supports all SIP Refer method call transfer scenarios, but you must ensure that call transfer is enabled using H.450.2 standards.

•H.450 standards are not supported by Cisco Unified Communications Manager, Cisco BTS, or Cisco PGW, although hairpin call routing or an H.450 tandem gateway can be set up to handle calls to and from those types of systems.

The following series of figures depicts a call being transferred using H.450.2 standards. Figure 24 shows A calling B. Figure 25 shows B consulting with C and putting A on hold. Figure 26 shows that B has connected A and C, and Figure 27 shows A and C directly connected, with B no longer involved in the call.

Figure 24 Call Transfer Using H.450.2: A Calls B

Figure 25 Call Transfer Using H.450.2: B Consults with C

Figure 26 Call Transfer Using H.450.2: B Transfers A to C

Figure 27 Call Transfer Using H.450.2: A and C Are Connected

Tips for Using H.450 Standards

Use H.450 standards when a network meets the following conditions:

•The router that you are configuring uses Cisco CME 3.0 or a later version, or Cisco ITS V2.1.

•For Cisco CME 3.0 or Cisco ITS V2.1 systems, all endpoints in the network must support H.450.2 and H.450.3 standards. For Cisco CME 3.1 or later systems, if some of the endpoints do not support H.450 standards (for example, Cisco Unified Communications Manager, Cisco BTS, or Cisco PGW), you can use hairpin call routing or an H.450 tandem gateway to handle transfers and forwards with those endpoints. Also, either you must explicitly disable H.450.2 and H.450.3 on the dial peers that handle those calls or you must enable H.450.12 capability to automatically detect the calls that support H.450.2 and H.450.3 and those calls that do not.

Support for the H.450.2 standard and the H.450.3 standard is enabled by default and can be disabled globally or for individual dial peers. For configuration information, see the "Enabling Call Transfer and Forwarding at System-Level" section.

Transfer Method Recommendations by Cisco Unified CME Version

You must specify the method to use for call transfers: H.450.2 standard signaling or Cisco proprietary signaling, and whether transfers should be blind or allow consultation. Table 29 summarizes transfer method recommendations for all Cisco Unified CME versions.

Table 29 Transfer Method Recommendations  

Cisco Unified CME Version	transfer-system Command Default	transfer-system Keyword to Use	Transfer Method Recommendation
4.0 and later	full-consult	full-consult or full-blind	Use H.450.2 for call transfer, which is the default for this version. You do not need to use the transfer-system command unless you want to use the full-blind or dss keyword. Optionally, you can use the proprietary Cisco method by using the transfer-system command with the blind or local-consult keyword. Use H.450.7 for call transfer using QSIG supplementary services
3.0 to 3.3	blind	full-consult or full-blind	Use H.450.2 for call transfer. You must explicitly configure the transfer-system command with the full-consult or full-blind keyword because H.450.2 is not the default for this version. Optionally, you can use the proprietary Cisco method by using the transfer-system command with the blind or local-consult keyword.
2.1	blind	blind or local-consult	Use the Cisco proprietary method, which is the default for this version. You do not need to use the transfer-system command unless you want to use the local-consult keyword. Optionally, you can use the transfer-system command with the full-consult or full-blind keyword. You must also configure the router with a Tcl script that is contained in the app-h450-transfer.x.x.x.x.zip file. This file is available from the Cisco Unified CME software download website at http://www.cisco.com/cgi-bin/tablebuild.pl/ip-iostsp. For configuration information, see the Cisco IOS Telephony Services Version 2.1 guide.
Earlier than 2.1	blind	blind	Use the Cisco proprietary method, which is the default for this version. You do not need to use the transfer-system command unless you want to use the local-consult keyword.

H.450.12 Support

Cisco CME 3.1 and later versions support the H.450.12 call capabilities standard, which provides a means to advertise and dynamically discover H.450.2 and H.450.3 capabilities in voice gateway endpoints on a call-by-call basis. When discovered, the calls associated with non-H.450 endpoints can be directed to use non-H.450 methods for transfer and forwarding, such as hairpin call routing or H.450 tandem gateway.

When H.450.12 is enabled, H.450.2 and H.450.3 services are disabled for call transfers and call forwards unless a positive H.450.12 indication is received from all other VoIP endpoints involved in the call. If a positive H.450.12 indication is received, the router uses the H.450.2 standard for call transfers and the H.450.3 standard for call forwarding. If a positive H.450.12 indication is not received, the router uses the alternative method that you have configured for call transfers and forwards, either hairpin call routing or an H.450 tandem gateway.

You can have either of the following situations in your network:

•All gateway endpoints support H.450.2 and H.450.3 standards. In this situation, no special configuration is required because support for H.450.2 and H.450.3 standards is enabled on the Cisco CME 3.1 or later router by default. H.450.12 capability is disabled by default, but it is not required because all calls can use H.450.2 and H.450.3 standards.

•Not all gateway endpoints support H.450.2 and H.450.3 standards. Therefore, specify how non-H.450 calls are to be handled by choosing one of the following options:

–Enable the H.450.12 capability in Cisco CME 3.1 and later to dynamically determine, on a call-by-call basis, whether each call has H.450.2 and H.450.3 support. If H.450.12 is enabled and a call is determined to have H.450 support, the call is transferred using H.450.2 standards or forwarded using H.450.3 standards. See the "Enabling H.450.12 Capabilities" section.

Support for the H.450.12 standard is disabled by default and can be enabled globally or for individual dial peers.

If the call does not have H.450 support, it can be handled by a VoIP-to-VoIP connection that you configure using dial peers and the "Enabling H.323-to-H.323 Connection Capabilities" section. The connection can be used for hairpin call routing or routing to an H.450 tandem gateway.

–Explicitly disable H.450.2 and H.450.3 capability on a global basis or by individual dial peer, which forces all calls to be handled by a VoIP-to-VoIP connection that you configure using dial peers and the "Enabling H.323-to-H.323 Connection Capabilities" section. This connection can be used for hairpin call routing or routing to an H.450 tandem gateway.

Hairpin Call Routing

Cisco CME 3.1 and later supports hairpin call routing using a VoIP-to-VoIP connection to transfer and forward calls that cannot use H.450 standards. When a call that originally terminated on a voice gateway is transferred or forwarded by a phone or other application attached to the gateway, the gateway reoriginates the call and routes the call as appropriate, making a VoIP-to-VoIP, or hairpin, connection. This approach avoids any protocol dependency on the far-end transferred-party endpoint or transfer-destination endpoint. Hairpin routing of transferred and forwarded calls also causes the generation of separate billing records for each call leg, so that the transferred or forwarded call leg is typically billed to the user who initiates the transfer or forward.

In Cisco CME 3.2 and later versions, transcoding between G.711 and G.729 is supported when one leg of a VoIP-to-VoIP hairpin call uses G.711 and the other leg uses G.729. For information about transcoding, see "Configuring Transcoding Resources" on page 323.

Hairpin call routing provides the following benefits:

•Call transfer and forwarding is provided to non-H.450 endpoints, such as Cisco Unified Communications Manager, Cisco BTS, or Cisco PGW.

•The network can also contain Cisco CME 3.0 or Cisco ITS 2.1 systems.

Hairpin call routing has the following disadvantages:

•End-to-end signaling and media delay are increased significantly.

•A single hairpinned call uses as much WAN bandwidth as two directly connected calls.

VoIP-to-VoIP hairpin connections can be made using dial peers if the allow-connections h323 to h323 command is enabled and at least one of the following is true:

•H.450.12 is used to detect calls on which H.450.2 or H.450.3 is not supported by the remote system.

•H.450.2 or H.450.3 is explicitly disabled.

•Cisco Unified CME automatically detects that the remote system is a Cisco Unified Communications Manager.

Figure 28 shows a call that is made from A to B. Figure 29 shows that B has forwarded all calls to C. Figure 30 shows that A and C are connected by an H.323 hairpin.

Figure 28 Hairpin with H.323: A Calls B

Figure 29 Hairpin with H.323: Call is Forwarded to C

Figure 30 Hairpin with H.323: A is Connected to C via B

Tips for Using Hairpin Call Routing

Use hairpin call routing when a network meets the following three conditions:

•The router that you are configuring uses Cisco CME 3.1 or a later version.

•Some or all calls require VoIP-to-VoIP routing because they cannot use H.450 standards, which can happen for any of the following reasons:

–H.450 capabilities have been explicitly disabled on the router.

–H.450 capabilities do not exist in the network.

–H.450 capabilities are supported on some endpoints and not supported on other endpoints, including those handled by Cisco Unified Communications Manager, Cisco BTS, and Cisco PGW. When some endpoints support H.450 and others do not, you must enable H.450.12 capabilities on the router to detect which endpoints are H.450-capable or designate some dial peers as H.450-capable. For more information about enabling H.450.12 capabilities, see the "Enabling H.450.12 Capabilities" section.

•No voice gateway is available to act as an H.450 tandem gateway.

For information about configuring Cisco Unified CME to forward calls using local hairpin routing, see the "Forwarding Calls Using Local Hairpin Routing" section.

Support for VoIP-to-VoIP connections is disabled by default and can be enabled globally. For configuration information, see the "Enabling H.323-to-H.323 Connection Capabilities" section.

H.450 Tandem Gateways

H.450 tandem gateways address the limitations of hairpin call routing using a manner similar to hairpin call routing but without the double WAN link traversal created by hairpin connections. An H.450 tandem gateway is an additional voice gateway that serves as a "front-end" for a call processor that does not support the H.450 standards, such as Cisco Unified Communications Manager, Cisco BTS Softswitch (Cisco BTS), or Cisco PSTN Gateway (Cisco PGW). Transferred and forwarded calls that are intended for non-H.450 endpoints are terminated instead on the H.450 tandem gateway and reoriginated there for delivery to the non-H.450 endpoints. The H.450 tandem gateway can also serve as a PSTN gateway.

An H.450 tandem gateway is configured with a dial peer that points to the Cisco Unified Communications Manager or other system for which the H.450 tandem gateway is serving as a front end. The H.450 tandem voice gateway is also configured with dial peers that point to all the Cisco Unified CME systems in the private H.450 network. In this way, Cisco Unified CME and the Cisco Unified Communications Manager are not directly linked to each other, but are instead both linked to an H.450 tandem gateway that provides H.450 services to the non-H.450 platform.

An H.450 tandem gateway can also work as a PSTN gateway for remote Cisco Unified CME systems and for Cisco Unified Communications Manager (or other non-H.450 system). Use different inbound dial peers to separate Cisco Unified Communications Manager-to-PSTN G.711 calls from tandem gateway-to-Cisco Unified CME G.729 calls.

---

Note An H.450 tandem gateway that is used in a network to support non-H.450-capable call processing systems requires the Integrated Voice and Video Services feature license. This feature license, which was introduced in March 2004, includes functionality for H.323 gatekeeper, IP-to-IP Gateway, and H.450 tandem gateway. With Cisco IOS Release 12.3(7)T, an H.323 gatekeeper feature license is required with a JSX Cisco IOS image on the selected router. Consult your Cisco Unified CME SE regarding the required feature license. With Cisco IOS Release 12.3(7)T, you cannot use Cisco Unified CME and H.450 tandem gateway functionality on the same router.

---

VoIP-to-VoIP connections can be made for an H.450 tandem gateway if the allow-connections h323 to h323 command is enabled and one or more of the following is true:

•H.450.12 is used to dynamically detect calls on which H.450.2 or H.450.3 is not supported by the remote VoIP system.

•H.450.2 or H.450.3 is explicitly disabled.

•Cisco CME 3.1 or later automatically detects that the remote system is a Cisco Unified Communications Manager.

For Cisco CME 3.1 and earlier, the only type of VoIP-to-VoIP connection supported by Cisco Unified CME is H.323-to-H.323. For Cisco CME 3.2 and later versions, H.323-to-SIP connections are allowed only for Cisco Unified CME systems running Cisco Unity Express.

Figure 31 shows a tandem voice gateway that is located between the central hub of the network of a CPE-based Cisco CME 3.1 or later network and a Cisco Unified Communications Manager network. This topology would work equally well with a Cisco BTS or Cisco PGW in place of the Cisco Unified Communications Manager.

In the network topology in Figure 31, the following events occur (refer to the event numbers on the illustration):

1. A call is generated from extension 4002 on phone 2, which is connected to a Cisco Unified Communications Manager. The H.450 tandem gateway receives the H.323 call and, acting as the H.323 endpoint, the H.450 tandem gateway handles the call connection to a Cisco Unified IP phone in a CPE-based Cisco CME 3.1 or later network.

2. The call is received by extension 1001 on phone 3, which is connected to Cisco Unified CME 1. Extension 1001 performs a consultation transfer to extension 2001 on phone 5, which is connected to Cisco Unified CME 2.

3. When extension 1001 transfers the call, the H.450 tandem gateway receives an H.450.2 message from extension 1001.

4. The H.450 tandem gateway terminates the call leg from extension 1001 and reoriginates a call leg to extension 2001, which is connected to Cisco Unified CME 2.

5. Extension 4002 is connected with extension 2001.

Figure 31 H.450 Tandem Gateway

Tips for Using H.450 Tandem Gateways

Use this procedure when a network meets the following conditions:

•The router that you are configuring uses Cisco CME 3.1 or a later version.

•Some endpoints in the network are not H.450-capable, including those handled by Cisco Unified Communications Manager, Cisco BTS, and Cisco PGW.

Support for VoIP-to-VoIP connections is disabled by default and can be enabled globally. For more information, see the "Enabling H.323-to-H.323 Connection Capabilities" section.

Use dial peers to set up an H.450 tandem gateway. See the "Dial Peers" section.

Dial Peers

Dial peers describe the virtual interfaces to or from which a call is established. All voice technologies use dial peers to define the characteristics associated with a call leg. Attributes applied to a call leg include specific quality of service (QoS) features, compression/decompression (codec), voice activity detection (VAD), and fax rate. Dial peers are also used to establish the routing paths in your network, including special routing paths such as hairpins and H.450 tandem gateways. Dial peer settings override the global settings for call forward and call transfer. For information about configuring dial peers, see the Dial Peer Configuration on Voice Gateway Routers guide.

QSIG Supplementary Services

QSIG is an intelligent inter-PBX signaling system widely adopted by PBX vendors. It supports a range of basic services, generic functional procedures, and supplementary services. Cisco Unified CME 4.0 introduces supplementary services features that allow Cisco Unified CME phones to seamlessly interwork using QSIG with phones connected to a PBX. One benefit is that IP phones can use a PBX message center with proper MWI notifications. Figure 32 illustrates a topology for a Cisco Unified CME system with some phones under the control of a PBX.

Figure 32 Cisco Unified CME System with PBX

The following QSIG supplementary service features are supported in Cisco Unified CME systems. They follow the standards from the European Computer Manufacturers Association (ECMA) and the International Organization for Standardization (ISO) on PRI and BRI interfaces.

•Basic calls between IP phones and PBX phones.

•Calling Line/Name Identification (CLIP/CNIP) presented on an IP phone when called by a PBX phone; in the reverse direction, such information is provided to the called endpoint.

•Connected Line/Name Identification (COLP/CONP) information provided when a PBX phone calls an IP phone and is connected; in the reverse direction, such information presented on an IP phone.

•Call Forward using QSIG and H.450.3 to support any combination of IP phone and PBX phone, including an IP phone in the Cisco Unified CME system that is connected to a PBX or an IP phone in another Cisco Unified CME system across an H.323 network.

•Call forward to the PBX message center according to the configured policy. The other two endpoints can be a mixture of IP phone and PBX phones.

•Hairpin call transfer, which interworks with a PBX in transfer-by-join mode. Note that Cisco Unified CME does not support the actual signaling specified for this transfer mode (including the involved FACILITY message service APDUs) which are intended for an informative purpose only and not for the transfer functionality itself. As a transferrer (XOR) host, Cisco Unified CME simply hairpins two call legs to create a connection; as a transferee (XEE) or transfer-to (XTO) host, it will not be aware of a transfer that is taking place on an existing leg. As a result, the final endpoint may not be updated with the accurate identity of its peer. Both blind transfer and consult transfer are supported.

•Message-waiting indicator (MWI) activation or deactivation requests are processed from the PBX message center.

•The PBX message center can be interrogated for the MWI status of a particular ephone-dn.

•A user can retrieve voice messages from a PBX message center by making a normal call to the message center access number.

For information about enabling QSIG supplementary services, see the "Enabling H.450.7 and QSIG Supplementary Services at a System-Level" section and "Enabling H.450.7 and QSIG Supplementary Services on a Dial Peer" section.

For more information about configuring Cisco Unified CME to integrate with voice-mail systems, see "Integrating Voice Mail" on page 375.

Disabling SIP Supplementary Services for Call Forward and Call Transfer

If a destination gateway does not support supplementary services, you can disable REFER messages for call transfers and redirect responses for call forwarding from being sent by Cisco Unified CME or Cisco Unified SRST.

Disabling supplementary services is supported if all endpoints use SCCP or all endpoints use SIP. It is not supported for a mix of SCCP and SIP endpoints.

Typical Network Scenarios for Call Transfer and Call Forwarding

In a mixed network that involves two or more types of call agents or call-control systems, there can be communication protocol discrepancies and dependencies, and therefore the opportunity for interoperability errors. These discrepancies show up most often when a call is being transferred or forwarded. This section provides descriptions of the specific mixed-network scenarios you might encounter when configuring a router running Cisco CME 3.1 or a later version. Each of the following sections point to the configuration instructions necessary to ensure call transfer and forwarding capabilities throughout the network.

• Cisco CME 3.1 or Later and Cisco IOS Gateways

• Cisco CME 3.0 or an Earlier Version and Cisco IOS Gateways

• Cisco CME 3.1 or Later, Non-H.450 Gateways, and Cisco IOS Gateways

• Cisco Unified CME, Non-H.450 Gateways, and Cisco IOS Gateways

• Cisco CME 3.1 or Later, Cisco Unified Communications Manager, and Cisco IOS Gateways

• Cisco CME 3.0 or an Earlier Version, Cisco Unified Communications Manager, and Cisco IOS Gateways

---

Note Cisco Communications Manager Express 3.2 (Cisco CME 3.2) and later versions provide full call-transfer and call-forwarding with call processing systems on the network that support H.450.2, H.450.3, and H.450.12 standards. For interoperability with call processing systems that do not support H.450 standards, Cisco CME 3.2 and later versions provide VoIP-to-VoIP hairpin call routing without requiring the special Tool Command Language (Tcl) script that was needed in earlier versions of Cisco Unified CME.

---

Cisco CME 3.1 or Later and Cisco IOS Gateways

In a network with Cisco CME 3.1 or a later version and Cisco IOS gateways, all systems that might participate in calls that involve call transfer and call forwarding are capable of supporting the H.450.2, H.450.3, and H.450.12 standards. This is the simplest environment for operating the Cisco CME 3.1 or later features.

Configuration for this type of network consists of:

1. Setting up call-transfer and call-forwarding parameters for transfers and forwards that are initiated on this router (H.450.2 and H.450.3 capabilities for transferred parties, transfer destinations, forwarded parties, and forwarding destinations are enabled by default). See the "Enabling Call Transfer and Forwarding at System-Level" section.

2. Enabling H.450.12 globally to detect any calls on which H.450.2 and H.450.3 standards are not supported. Although this step is optional, we recommend it. See the "Enabling H.450.12 Capabilities" section.

3. Optionally setting up VoIP-to-VoIP connections (hairpin call routing or H.450 tandem gateway) to route calls that do not support H.450.2 or H.450.3 standards. See the "Enabling H.323-to-H.323 Connection Capabilities" section.

4. Setting up dial peers to manage call legs within the network. See Dial Peer Configuration on Voice Gateway Routers.

Cisco CME 3.0 or an Earlier Version and Cisco IOS Gateways

Before Cisco CME 3.1, H.450.2 and H.450.3 standards are used for all calls by default and routers do not support the H.450.12 standard.

Configuration for this type of network consists of:

1. Setting up call-transfer and call-forwarding parameters for transfers and forwards that are initiated on this router (H.450.2 and H.450.3 capabilities for transferred parties, transfer destinations, forwarded parties, and forwarding destinations are enabled by default). See the "Enabling Call Transfer and Forwarding at System-Level" section.

2. Enabling H.450.12 in advertise-only mode on Cisco CME 3.1 or later systems. As each Cisco CME 3.0 system is upgraded to Cisco CME 3.1 or later, enable H.450.12 in advertise-only mode. Note that no checking for H.450.2 or H.450.3 support is done in advertise-only mode. When all Cisco CME 3.0 systems in the network have been upgraded to Cisco CME 3.1 or later, remove the advertise-only restriction. See the "Enabling H.450.12 Capabilities" section.

3. Optionally setting up VoIP-to-VoIP connections (hairpin call routing or H.450 tandem gateway) to route calls that cannot use H.450.2 or H.450.3 standards. See the "Enabling H.323-to-H.323 Connection Capabilities" section.

4. Setting up dial peers to manage call legs within the network. See Dial Peer Configuration on Voice Gateway Routers.

Cisco CME 3.1 or Later, Non-H.450 Gateways, and Cisco IOS Gateways

In a network with Cisco CME 3.1 or later, non-H.450 gateways, and Cisco IOS gateways, the H.450.2 and H.450.3 services are provided only to calling endpoints that use H.450.12 to explicitly indicate that they are capable of H.450.2 and H.450.3 operations. Because the Cisco BTS and Cisco PGW do not support the H.450.12 standard, calls to and from these systems that involve call transfer or forwarding are handled using H.323-to-H.323 hairpin call routing.

Configuration for this type of network consists of:

1. Setting up call-transfer and call-forwarding parameters for transfers and forwards that are initiated on this router (H.450.2 and H.450.3 capabilities for transferred parties, transfer destinations, forwarded parties, and forwarding destinations are enabled by default). Optionally disable H.450.2 and H.450.3 capabilities on dial peers that point to non-H.450-capable systems such as Cisco Unified Communications Manager, Cisco BTS, or Cisco PGW. See the "Enabling Call Transfer and Forwarding at System-Level" section.

2. Enabling H.450.12 to detect any calls on which H.450.2 and H.450.3 standards are not supported, either globally or for specific dial peers. See the "Enabling H.450.12 Capabilities" section.

3. Setting up VoIP-to-VoIP connections (hairpin call routing or H.450 tandem gateway) to route calls that do not support H.450.2 or H.450.3 standards. See the "Enabling H.323-to-H.323 Connection Capabilities" section.

4. Setting up dial peers to manage call legs within the network. See Dial Peer Configuration on Voice Gateway Routers.

---

Note If your network contains a Cisco Unified Communications Manager, also see the instructions in the "Enabling Interworking with Cisco Unified Communications Manager" section.

---

Cisco Unified CME, Non-H.450 Gateways, and Cisco IOS Gateways

---

Note Cisco CME 3.0 and Cisco ITS V2.1 systems do not have H.450.12 capabilities.

---

In a network that contains a mix of Cisco Unified CME versions and at least one non-H.450 gateway, the simplest configuration approach is to globally disable all H.450.2 and H.450.3 services and force H.323-to-H.323 hairpin call routing for all transferred and forwarded calls. In this case, you would enable H.450.12 detection capabilities globally. Alternatively, you could select to enable H.450.12 capability for specific dial peers. In this case, you would not configure H.450.12 capability globally; you would leave it in its default disabled state.

Configuration for this type of network consists of:

1. Setting up call-transfer and call-forwarding parameters for transfers and forwards that are initiated on this router (H.450.2 and H.450.3 capabilities for transferred parties, transfer destinations, forwarded parties, and forwarding destinations are enabled by default). See the "Enabling Call Transfer and Forwarding at System-Level" section.

2. Enabling H.450.12 to detect any calls on which H.450.2 and H.450.3 standards are not supported, either globally or on specific dial peers. See the "Enabling H.450.12 Capabilities" section.

3. Setting up VoIP-to-VoIP connections (hairpin call routing or H.450 tandem gateway) to route all transferred and forwarded calls. See the "Enabling H.323-to-H.323 Connection Capabilities" section.

4. Setting up dial peers to manage call legs within the network. See Dial Peer Configuration on Voice Gateway Routers.

---

Note If your network contains a Cisco Unified Communications Manager, also see the instructions in the "Enabling Interworking with Cisco Unified Communications Manager" section.

---

Cisco CME 3.1 or Later, Cisco Unified Communications Manager, and Cisco IOS Gateways

In a network with Cisco CME 3.1 or later, Cisco Unified Communications Manager, and Cisco IOS gateways, Cisco CME 3.1 and later versions support automatic detection of calls to and from Cisco Unified Communications Manager using proprietary signaling elements that are included with the standard H.323 message exchanges. The Cisco CME 3.1 or later system uses these detection results to determine the H.450.2 and H.450.3 capabilities of calls rather than using H.450.12 supplementary services capabilities exchange, which Cisco Unified Communications Manager does not support. If a call is detected to be coming from or going to a Cisco Unified Communications Manager endpoint, the call is treated as a non-H.450 call. All other calls in this type of network are treated as though they support H.450 standards. Therefore, this type of network should contain only Cisco CME 3.1 or later and Cisco Unified Communications Manager call-processing systems.

Configuration for this type of network consists of:

1. Setting up call-transfer and call-forwarding parameters for transfers and forwards that are initiated on this router (H.450.2 and H.450.3 capabilities for transferred parties, transfer destinations, forwarded parties, and forwarding destinations are enabled by default). See the "Enabling Call Transfer and Forwarding at System-Level" section.

2. Enabling H.450.12 to detect any calls on which H.450.2 and H.450.3 standards are not supported, either globally or on specific dial peers. See the "Enabling H.450.12 Capabilities" section.

3. Setting up VoIP-to-VoIP connections (hairpin call routing or H.450 tandem gateway) to route all transferred and forwarded calls that are detected as being to or from Cisco Unified Communications Manager. See the "Enabling H.323-to-H.323 Connection Capabilities" section.

4. Setting up specific parameters for Cisco Unified Communications Manager. See the instructions in the "Enabling Interworking with Cisco Unified Communications Manager" section.

5. Setting up dial peers to manage call legs within the network. See Dial Peer Configuration on Voice Gateway Routers.

Cisco CME 3.0 or an Earlier Version, Cisco Unified Communications Manager, and Cisco IOS Gateways

Calls between the Cisco Unified Communications Manager and the older Cisco CME 3.0 or Cisco ITS V2.1 networks need special consideration. Because Cisco CME 3.0 and Cisco ITS V2.1 systems do not support automatic Cisco Unified Communications Manager detection and also do not natively support H.323-to-H.323 call routing, alternative arrangements are required for these systems.

To configure call transfer and forwarding on the Cisco CME 3.0 router, you can select from the following three options:

•Use a Tcl script to handle call transfer and forwarding by invoking Tcl-script-based H.323-to-H.323 hairpin call routing (app-h450-transfer.2.0.0.9.tcl or a later version). Enable this script on all VoIP dial peers and also under telephony-service mode, and set the local-hairpin script parameter to 1. See the configuration instructions in the "Configuring Call Transfer" chapter of the Cisco CallManager Express 3.0 System Administrator Guide.

•Use a loopback-dn mechanism. See "Configuring Loopback Call Routing".

•Configure a loopback call path using router physical voice ports.

All three options force use of H.323-to-H.323 hairpin call routing for all calls regardless of whether the call is from a Cisco Unified Communications Manager or other H.323 endpoint (including Cisco CME 3.1 or later).

In addition to the special considerations above, configuration of the Cisco CME 3.1 or later router for this type of network consists of:

1. Setting up call-transfer and call-forwarding parameters for transfers and forwards that are initiated on this router (H.450.2 and H.450.3 capabilities for transferred parties, transfer destinations, forwarded parties, and forwarding destinations are enabled by default). See the "Enabling Call Transfer and Forwarding at System-Level" section.

2. Leaving H.450.12 capability in its default disabled state. For more information, see the "Enabling H.450.12 Capabilities" section.

3. Setting up VoIP-to-VoIP connections (hairpin call routing or H.450 tandem gateway) to route all transferred and forwarded calls that are detected as being to or from Cisco Unified Communications Manager. See the "Enabling H.323-to-H.323 Connection Capabilities" section.

4. Setting up specific parameters for Cisco Unified Communications Manager. See the instructions in the "Enabling Interworking with Cisco Unified Communications Manager" section.

5. Setting up dial peers to manage call legs within the network. See Dial Peer Configuration on Voice Gateway Routers.

How to Configure Call Transfer and Forwarding

This section contains the following procedures:

SCCP

• Enabling Call Transfer and Forwarding at System-Level (required)

• SCCP: Enabling Call Forwarding for a Directory Number (required)

• SCCP: Enabling Call Transfer for a Directory Number (required)

• SCCP: Configuring Call Transfer Options for Phones (optional))

• SCCP: Verifying Call Transfer (optional)

• Enabling H.450.12 Capabilities (optional)

• Enabling H.323-to-H.323 Connection Capabilities (optional)

• Forwarding Calls Using Local Hairpin Routing (optional)

• Enabling H.450.7 and QSIG Supplementary Services at a System-Level (optional)

• Enabling H.450.7 and QSIG Supplementary Services on a Dial Peer (optional)

• Disabling SIP Supplementary Services for Call Forward and Call Transfer (optional)

• Enabling Interworking with Cisco Unified Communications Manager (optional)

SIP B2BUA

• SIP: Configuring SIP-to-SIP Phone Call Forwarding (required)

• SIP: Configuring Call-Forwarding-All Soft Key URI (optional)

• SIP: Specifying Number of 3XX Responses To be Handled (optional)

• SIP: Configuring Call Transfer (required)

• Disabling SIP Supplementary Services for Call Forward and Call Transfer (optional)

Enabling Call Transfer and Forwarding at System-Level

To enable H.450 call transfers and forwards for transferring or forwarding parties; that is, to allow transfers and forwards to be initiated from a Cisco Unified CME system, perform the following steps.

---

Note H.450.2 and H.450.3 capabilities are enabled by default for transferred or forwarded parties and transfer-destination or forward-destination parties. Dial peer settings override the global setting.

---

Prerequisites

Cisco CME 3.0 or a later version, or Cisco ITS V2.1.

Restrictions

•Call transfers are handled differently depending on the Cisco Unified CME version. See Table 29 for recommendations on selecting a transfer method for your Cisco Unified CME version.

•The transfer-system local-consult command is not supported if the transfer-to destination is on the Cisco ATA, Cisco VG224, or a SCCP-controlled FXS port.

•The H.450.2 and H.450.3 standards are not supported by Cisco Unified Communications Manager, Cisco BTS, or Cisco PGW.

SUMMARY STEPS

1. enable

2. configure terminal

3. telephony-service

4. transfer-system {blind | full-blind | full-consult [dss] | local-consult}

5. transfer-pattern transfer-pattern [blind]

6. call-forward pattern pattern

7. exit

8. voice service voip

9. supplementary-service h450.2

10. supplementary-service h450.3

11. exit

12. dial-peer voice tag voip

13. supplementary-service h450.2

14. supplementary-service h450.3

15. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	telephony-service Example: Router(config)# telephony-service	Enters telephony-service configuration mode.
Step 4	transfer-system {blind | full-blind | full-consult [dss] | local-consult} Example: Router(config-telephony)# transfer-system full-consult	Specifies the call transfer method. •Cisco CME 3.0 and later versions—Use only the full-blind or full-consult keyword. •Before Cisco CME 3.0—Use the local-consult or blind keyword. (Cisco ITS 2.1 can use the full-blind or full-consult keyword by also using the Tcl script in the file called app-h450-transfer.x.x.x.x.zip.) •blind—Calls are transferred without consultation with a single phone line using the Cisco proprietary method. This is the default in Cisco CME versions earlier than 4.0. •full-blind—Calls are transferred without consultation using H.450.2 standard methods. •full-consult—Calls are transferred with consultation using H.450.2 standard methods and a second phone line if available. Calls fall back to full-blind if the second line is unavailable. This is the default in Cisco Unified CME 4.0 and later versions. •dss—(Optional) Calls are transferred with consultation to idle monitored lines. All other call-transfer behavior is identical to full-consult. •local-consult—Calls are transferred with local consultation using a second phone line if available. The calls fall back to blind for nonlocal consultation or nonlocal transfer target. Not supported if transfer-to destination is on the Cisco ATA, Cisco VG224, or a SCCP-controlled FXS port.
Step 5	transfer-pattern transfer-pattern [blind] Example: Router(config-telephony)# transfer-pattern .T	Allows transfer of telephone calls by Cisco Unified IP phones to specified phone number patterns. If no transfer pattern is set, the default is that transfers are permitted only to other local IP phones. •transfer-pattern—String of digits for permitted call transfers. Wildcards are allowed. A pattern of .T transfers all calling parties using the H.450.2 standard. •blind—(Optional) When H.450.2 consultative call transfer is configured, forces transfers that match the pattern specified in this command to be executed as blind transfers. Overrides settings made using the transfer-system and transfer-mode commands. Note For transfers to nonlocal numbers, transfer-pattern digit matching is performed before translation-rule operations. Therefore, you should specify in this command the digits actually entered by phone users before they are translated. For more information, see "Configuring Dialing Plans" on page 287.
Step 6	call-forward pattern pattern Example: Router(config-telephony)# call-forward pattern .T	Specifies the H.450.3 standard for call forwarding. •Calling-party numbers that do not match the patterns defined with this command are forwarded using Cisco proprietary call forwarding for backward compatibility, as described in the "Configuring Call Forwarding" chapter in the Cisco IOS Telephony Services Version  2.1 guide. •pattern—Digits to match for call forwarding using the H.450.3 standard. If an incoming calling-party number matches the pattern, it can be forwarded using the H.450.3 standard. A pattern of .T forwards all calling parties using the H.450.3 standard. Note For forwards to nonlocal numbers, pattern matching is performed before translation-rule operations. Therefore, you should specify in this command the digits actually entered by phone users before they are translated. For more information, see "Configuring Dialing Plans" on page 287.
Step 7	exit Example: Router(config-telephony)# exit	Exits telephony-service configuration mode.
Step 8	voice service voip Example: Router(config)# voice service voip	(Optional) Enters voice-service configuration mode to establish global call transfer and forwarding parameters.
Step 9	supplementary-service h450.2 Example: Router(conf-voi-serv)# supplementary-service h450.2	(Optional) Enables H.450.2 supplementary services capabilities globally. •Default is enabled. Use the no form of this command to disable H.450.2 capabilities globally. •You can also use this command in dial-peer configuration mode to enable H.450.2 services for a single dial peer.
Step 10	supplementary-service h450.3 Example: Router(conf-voi-serv)# supplementary-service h450.3	(Optional) Enables H.450.3 supplementary services capabilities globally. •Default is enabled. Use the no form of this command to disable H.450.3 capabilities globally. •You can also use this command in dial-peer configuration mode to enable H.450.3 services for a single dial peer.
Step 11	exit Example: Router(conf-voi-serv)# exit	(Optional) Exits voice-service configuration mode.
Step 12	dial-peer voice tag voip Example: Router(config)# dial-peer voice 1 voip	(Optional) Enters dial-peer configuration mode.
Step 13	supplementary-service h450.2 Example: Router(config-dial-peer)# no supplementary-service h450.2	(Optional) Enables H.450.2 supplementary services capabilities for an individual dial peer. •Default is enabled. You can also use this command in voice-service configuration mode to enable H.450.2 services globally. •If this command is enabled globally and enabled on a dial peer, the functionality is enabled for the dial peer. This is the default. •If this command is enabled globally and disabled on a dial peer, the functionality is disabled for the dial peer. •If this command is disabled globally and either enabled or disabled on a dial peer, the functionality is disabled for the dial peer.
Step 14	supplementary-service h450.3 Example: Router(config-dial-peer)# no supplementary-service h450.3	(Optional) Enables H.450.3 supplementary services capabilities exchange for an individual dial peer. •Default is enabled. You can also use this command in voice-service configuration mode to enable H.450.3 services globally. •If this command is enabled globally and enabled on a dial peer, the functionality is enabled for the dial peer. This is the default. •If this command is enabled globally and disabled on a dial peer, the functionality is disabled for the dial peer. •If this command is disabled globally and either enabled or disabled on a dial peer, the functionality is disabled for the dial peer.
Step 15	end Example: Router(config-dial-peer)# end	Returns to privileged EXEC mode.

SCCP: Enabling Call Forwarding for a Directory Number

To define the conditions and target numbers for call forwarding for individual ephone-dns, and set other restrictions for call forwarding, perform the following steps.

---

Note When defining call forwarding to nonlocal numbers, it is important to note that pattern digit matching is performed before translation-rule operations. Therefore, you should specify in this command the digits actually entered by phone users before they are translated. For more information, see the "Voice Translation Rules and Profiles" section in "Configuring Dialing Plans" on page 287.

---

SUMMARY STEPS

1. enable

2. configure terminal

3. telephony-service

4. call-forward pattern pattern

5. exit

6. ephone-dn dn-tag [dual-line]

7. number number [secondary number] [no-reg [both | primary]]

8. call-forward all target-number

9. call-forward busy target-number [primary | secondary] [dialplan-pattern]

10. call-forward noan target-number timeout seconds [primary | secondary] [dialplan-pattern]

11. call-forward night-service target-number

12. call-forward max-length length

13. no forward local-calls

14. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	telephony-service Example: Router(config)#	Enters telephony-service configuration mode.
Step 4	call-forward pattern pattern Example: Router(config-telephony)# call-forward pattern .T	Specifies the H.450.3 standard for call forwarding. Calling-party numbers that do not match the patterns defined with this command are forwarded using Cisco-proprietary call forwarding for backward compatibility. •pattern—Digits to match for call forwarding using the H.450.3 standard. If an incoming calling-party number matches the pattern, it is forwarded using the H.450.3 standard. A pattern of .T forwards all calling parties using the H.450.3 standard.
Step 5	exit Example: Router(config-telephony)# exit	Exits telephony-service configuration mode.
Step 6	ephone-dn dn-tag [dual-line] Example: Router(config)# ephone-dn 20	Enters ephone-dn configuration mode, creates an ephone-dn, and optionally assigns it dual-line status. •dual-line—(Optional) Enables an ephone-dn with one voice port and two voice channels, which supports features such as call waiting, call transfer, and conferencing with a single ephone-dn.
Step 7	number number [secondary number] [no-reg [both | primary]] Example: Router(config-ephone-dn)# number 2777 secondary 2778	Configures a valid extension number for this ephone-dn instance.
Step 8	call-forward all target-number Example: Router(config-ephone-dn)# call-forward all 2411	Forwards all calls for this extension to the specified number. •target-number—Phone number to which calls are forwarded. Note After you use this command to specify a target number, the phone user can activate and cancel the call-forward-all state from the phone using the CFwdAll soft key or a feature access code (FAC).
Step 9	call-forward busy target-number [primary | secondary] [dialplan-pattern] Example: Router(config-ephone-dn)# call-forward busy 2513	Forwards calls for a busy extension to the specified number.
Step 10	call-forward noan target-number timeout seconds [primary | secondary] [dialplan-pattern] Example: Router(config-ephone-dn)# call-forward noan 2513 timeout 45	Forwards calls for an extension that does not answer.
Step 11	call-forward night-service target-number Example: Router(config-ephone-dn)# call-forward night-service 2879	Automatically forwards incoming calls to the specified number when night service is active. •target-number—Phone number to which calls are forwarded. Note Night service must also be configured. See "Configuring Call-Coverage Features" on page 581.
Step 12	call-forward max-length length Example: Router(config-ephone-dn)# call-forward max-length 5	(Optional) Limits the number of digits that can be entered for a target number when using the CfwdAll soft key on an IP phone. •length—Number of digits that can be entered using the CfwdAll soft key on an IP phone.
Step 13	no forward local-calls Example: Router(config-ephone-dn)# no forward local-calls	(Optional) Specifies that local calls (calls from ephone-dns on the same Cisco Unified CME system) will not be forwarded from this extension. •If this extension is busy, an internal caller hears a busy signal. •If this extension does not answer, the internal caller hears ringback.
Step 14	end Example: Router(config-ephone-dn)# end	Returns to privileged EXEC mode.

SCCP: Enabling Call Transfer for a Directory Number

To enable call transfer for a specific directory number, perform the following steps. This procedure overrides the global setting for blind or consultative transfer for individual directory numbers.

Prerequisites

Call transfer must be enabled globally. See the "Enabling Call Transfer and Forwarding at System-Level" section.

SUMMARY STEPS

1. enable

2. configure terminal

3. ephone-dn dn-tag [dual-line]

4. transfer-mode {blind | consult}

5. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	ephone-dn dn-tag [dual-line] Example: Router(config)# ephone-dn 20	Enters ephone-dn configuration mode, creates an ephone-dn, and optionally assigns it dual-line status. •dual-line—(Optional) Enables an ephone-dn with one voice port and two voice channels, which supports features such as call waiting, call transfer, and conferencing with a single ephone-dn.
Step 4	transfer-mode {blind | consult} Example: Router(config-ephone-dn)# transfer-mode blind	Specifies the type of call transfer for an individual directory number using the H.450.2 standard, allowing you to override the global setting. •Default: system-level value set with the transfer-system command.
Step 5	end Example: Router(config-ephone)# end	Returns to privileged EXEC mode.

SCCP: Configuring Call Transfer Options for Phones

To specify a maximum number of digits for transfer destinations or block transfers to external destinations by individual phones, perform the following steps.

Restrictions

•Transfers made to speed-dial numbers are not blocked when the transfer-pattern blocked command is used.

•Transfers made using speed-dial are not blocked by the after-hours block pattern command.

SUMMARY STEPS

1. enable

2. configure terminal

3. ephone-template template-tag

4. transfer-pattern blocked

5. transfer max-length digit-length

6. exit

7. ephone phone-tag

8. ephone-template template-tag

9. restart

10. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	ephone-template template-tag Example: Router(config)# ephone-template 1	Enters ephone-template configuration mode. •template-tag—Unique sequence number that identifies this template during configuration tasks. Range is 1 to 20.
Step 4	transfer-pattern blocked Example: Router(config-ephone-template)# transfer-pattern blocked	(Optional) Prevents directory numbers on the phone to which this template is applied from transferring calls to patterns specified in the transfer-pattern (telephony-service) command. Note This command is also available in ephone configuration mode to block external transfers from individual phones without using a template.
Step 5	transfer max-length digit-length Example: Router(config-ephone-template)# transfer max-length 8	(Optional) Specifies the maximum number of digits the user can dial when transferring a call. •digit-length—Number of digits allowed in a number to which a call is being transferred. Range: 3 to 16. Default: 16.
Step 6	exit Example: Router(config-ephone-template)# exit	Exits ephone-template configuration mode.
Step 7	ephone phone-tag Example: Router(config)# ephone 25	Enters ephone configuration mode.
Step 8	ephone-template template-tag Example: Router(config-ephone)# ephone-template 1	Applies a template to a phone. •template-tag—Template number that you want to apply to this phone.
Step 9	restart Example: Router(config-ephone)# restart	Performs a fast reboot of this phone without contacting the DHCP server for updated information. •Repeat Step 6 to Step 9 for each phone on which you want to limit transfer capabilities.
Step 10	end Example: Router(config-ephone)# end	Returns to privileged EXEC mode.

SCCP: Verifying Call Transfer

---

Step 1 Use the show running-config command to verify your configuration. Transfer method and patterns are listed in the telephony-service portion of the output. You can also use the show telephony-service command to display this information.

Router# show running-config

!

telephony-service

fxo hook-flash

load 7910 P00403020214

load 7960-7940 P00305000600

load 7914 S00103020002

load 7905 CP7905040000SCCP040701A

max-ephones 100

max-dn 500

ip source-address 10.115.33.177 port 2000

max-redirect 20

no service directed-pickup

timeouts ringing 10

 voicemail 7189

max-conferences 8 gain -6

moh music-on-hold.au

web admin system name cisco password cisco

dn-webedit

time-webedit

transfer-system full-consult

transfer-pattern 92......

transfer-pattern 91..........

transfer-pattern 93......

transfer-pattern 94......

transfer-pattern 95......

transfer-pattern 96......

transfer-pattern 97......

transfer-pattern 98......

transfer-pattern 99......

transfer-pattern .T

secondary-dialtone 9

!

create cnf-files version-stamp 7960 Jul 13 2004 03:39:28




Step 2 If you have used the transfer-mode command to override the global transfer mode for an individual ephone-dn, use the show running-config or show telephony-service ephone-dn command to verify that setting.

Router# show running-config

!

ephone-dn 40 dual-line

number 451

description Main Number

 huntstop channel

no huntstop

transfer-mode blind




Step 3 Use the show telephony-service ephone-template command to view ephone-template configurations.

---

Enabling H.450.12 Capabilities

To enable H.450.12 capabilities globally or by individual dial peer when not all gateway endpoints in your network support H.450.2 and H.450.3 standards, perform the following steps. H.450.12 capabilities are disabled by default to minimize the risk of compatibility issues with other types of H.323 systems. Settings for individual dial peers override the global setting.

Restrictions

Cisco CME 3.0 and earlier versions do not support H.450.12.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice service voip

4. supplementary-service h450.12 [advertise-only]

5. exit

6. dial-peer voice tag voip

7. supplementary-service h450.12

8. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	voice service voip Example: Router(config)# voice service voip	(Optional) Enters voice service configuration mode to establish global call transfer and forwarding parameters.
Step 4	supplementary-service h450.12 [advertise-only] Example: Router(conf-voi-serv)# supplementary-service h450.12	(Optional) Enables H.450.12 supplementary services capabilities globally for VoIP endpoints. •This command enables call-by-call detection of H.450 capabilities when some endpoints in your mixed network are H.450-capable and other endpoints are not. This command is disabled by default. •advertise-only—(Optional) Advertises H.450 capabilities to the remote end but does not require H.450.12 responses. Use this keyword on Cisco CME 3.1 or later systems if you have a mixed network containing Cisco CME 3.0 systems. This command is also used in dial-peer configuration mode to affect an individual dial peer.
Step 5	exit Example: Router(conf-voi-serv)# exit	(Optional) Exits voice-service configuration mode.
Step 6	dial-peer voice tag voip Example: Router(config)# dial-peer voice 1 voip	(Optional) Enters dial-peer configuration mode.
Step 7	supplementary-service h450.12 Example: Router(config-dial-peer)# supplementary-service h450.12	(Optional) Enables H.450.12 supplementary services capabilities for an individual dial peer. This command is disabled by default. This command is also used in voice-service configuration mode to enable H.450.12 services globally. •If this command is enabled globally and enabled on a dial peer, the functionality is enabled for the dial peer. •If this command is enabled globally and disabled on a dial peer, the functionality is enabled for the dial peer. •If this command is disabled globally and enabled on a dial peer, the functionality is enabled for the dial peer. •If this command is disabled globally and disabled on a dial peer, the functionality is disabled for the dial peer. This is the default.
Step 8	end Example: Router(config-dial-peer)# end	Returns to privileged EXEC mode.

Enabling H.323-to-H.323 Connection Capabilities

VoIP-to-VoIP connections permit the termination and reorigination of transferred and forwarded calls over the VoIP network. VoIP-to-VoIP connections are used for hairpin call routing and for H.450 tandem gateways. The only type of VoIP-to-VoIP connection that is supported by Cisco CME 3.1 or a later version is H.323-to-H.323 connection.

VoIP-to-VoIP connections are disabled on the router by default, and they must be explicitly enabled to make use of hairpin call routing or an H.450 tandem gateway. In addition, you must configure a mechanism to direct transferred or forwarded calls to the hairpin or the H.450 tandem gateway, using one of the following methods:

•Enable H.450.12 capabilities globally or on the routes that your transfers and forwards take. See the "Enabling H.450.12 Capabilities" section.

•Explicitly disable H.450.2 and H.450.3 capabilities globally or on the routes that your transfers and forwards take. See the "Enabling Call Transfer and Forwarding at System-Level" section.

Restrictions

•Codecs on all the VoIP dial peers of the H.450 tandem gateway must be the same.

•Only one codec type is supported in the VoIP network at a time, and there are only two codec choices: G.711 (A-law or mu-law) or G.729.

•Transcoding is not supported.

•Codec renegotiation is not supported. For example, if an H.323 call that uses a G.729 codec is received by a Cisco Unified CME system and is forwarded to a voice-mail system that requires a G.711 codec, the codec cannot be renegotiated from G.729 to G.711.

•H.323-to-SIP hairpin call routing is supported only with Cisco Unity Express. For more information, see Integrating Cisco CallManager Express and Cisco Unity Express.

•Cisco Unified Communications Manager must use a media termination point (MTP), intercluster trunk (ICT) mode, and slow start.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice service voip

4. allow-connections h323 to h323

5. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	voice service voip Example: Router(config)# voice service voip	Enters voice service configuration mode to establish global call transfer and forwarding parameters.
Step 4	allow-connections h323 to h323 Example: Router(conf-voi-serv)# allow-connections h323 to h323	Enables VoIP-to-VoIP call connections. Use the no form of the command to disable VoIP-to-VoIP connections; this is the default.
Step 5	end Example: Router(config-voi-serv)# end	Returns to privileged EXEC mode.

Forwarding Calls Using Local Hairpin Routing

When Cisco Unified CME is used to forward calls that originate on phones that do not support the H.450.3 standard such as Cisco Unified Communications Manager phones, local hairpin routing must be used to forward the calls. For calling parties whose numbers match the pattern specified, the system automatically detects whether H.450.3 is supported and uses the appropriate method to forward calls.

To enable hairpin routing, you must denote the originating and terminating legs of the hairpin. To forward calls to Cisco Unity Express, connections must be allowed to a SIP trunk.

Optionally, you can disable the use of H.450.3 but this is not required because the system automatically detects calls on which H.450.3 is not supported and local hairpin routing is required when the calling-party numbers match the pattern specified.

SUMMARY STEPS

1. enable

2. configure terminal

3. telephony-service

4. call-forward pattern pattern

5. calling-number local

6. exit

7. voice service voip

8. allow connections from-type to to-type

9. supplementary-service h450.3

10. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	telephony-service Example: Router(config)# telephony-service	Enters telephony-service configuration mode.
Step 4	call-forward pattern pattern Example: Router(config-telephony)# call-forward pattern 6000	Specifies the calling-party numbers for which to allow call forwarding with automatic detection of whether H.450.3 is supported. If H.450.3 is supported, H.450.3 is used for the forward and, if not, local hairpin is used. •pattern—Digits to match for call forwarding. A pattern of .T forwards all calling parties.
Step 5	calling-number local Example: Router(config-telephony)# calling-number local	(Optional) Replaces a calling-party number and name with the forwarding-party (local) number and name for hairpin-forwarded calls only. •Before Cisco CME 3.3, this command must be used with Tool Command Language (Tcl) script app-h450-transfer.2.0.0.7 or a later version. The local-hairpin attribute-value (AV) pair must be set to 1.
Step 6	exit Example: Router(config-telephony)# exit	Exits telephony-service configuration mode.
Step 7	voice service voip Example: Router(config)# voice service voip	Enters voice-service configuration mode.
Step 8	allow connections from-type to to-type Example: Router(conf-voi-serv)# allow connections h323 to sip	Allows connections between specific types of endpoints in a network. •from-type—Originating endpoint type. Valid choices are h323 and sip. •to-type—Terminating endpoint type. Valid choices are h323 and sip.
Step 9	supplementary-service h450.3 Example: Router(conf-voi-serv)# no supplementary-service h450.3	(Optional) Enables H.450.3 supplementary services capabilities exchange globally. This is the default. Use the no form of this command to disable H.450.3 capabilities globally. This command can also be used in dial-peer configuration mode to disable H.450.3 functionality for a single dial peer. Note If this command is disabled globally and either enabled or disabled on a dial peer, the functionality is disabled for the dial peer.
Step 10	end Example: Router(config-voi-serv)# end	Returns to privileged EXEC mode.

Enabling H.450.7 and QSIG Supplementary Services at a System-Level

To enable H.4350.7 capabilities and QSIG supplementary services on all dial peers, perform the following steps.

Prerequisites

Cisco Unified CME 4.0 or a later version.

Restrictions

•QSIG integration supports SCCP phones only.

•QSIG integration is exclusive; once QSIG integration is configured, QSIG transit node capability is disabled. There is no dial-peer control to enable either transit or originate/terminate capability on a call by call basis.

•If you enable QSIG supplementary services at a system-level, you cannot disable the capability on individual dial peers.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice service voip

4. supplementary-service h450.7

5. qsig decode

6. exit

7. voice service pots

8. supplementary-service qsig call-forward

9. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	voice service voip Example: Router(config)# voice service voip	Enters VoIP voice-service configuration mode to define global call transfer and forwarding parameters.
Step 4	supplementary-service h450.7 Example: Router(config-voi-serv)# supplementary-service h450.7	Enables H.450.7 supplementary services capabilities exchange at a system-level.
Step 5	qsig decode Example: Router(config-voi-serv)# qsig decode	Enables decoding for QSIG supplementary services.
Step 6	exit Example: Router(config-voi-serv)# exit	Exits VoIP voice-service configuration mode.
Step 7	voice service pots Example: Router(config)# voice service pots	Enters POTS voice-service configuration mode to define global call transfer and forwarding parameters.
Step 8	supplementary-service qsig call-forward Example: Router(config-voi-serv)# supplementary-service qsig call-forward	Enables QSIG call-forwarding supplementary services (ISO 13873) to forward calls to another number.
Step 9	end Example: Router(config-voi-serv)# end	Returns to privileged EXEC mode.

Enabling H.450.7 and QSIG Supplementary Services on a Dial Peer

To enable H.4350.7 capabilities and QSIG supplementary services on an individual dial peer, perform the following steps.

Prerequisites

Cisco Unified CME 4.0 or a later version.

Restrictions

•QSIG integration supports SCCP phones only.

•QSIG integration is exclusive; once QSIG integration is configured, QSIG transit node capability is disabled. There is no dial-peer control to enable either transit or originate/terminate capability on a call by call basis.

•If you enable QSIG supplementary services at a system-level, you cannot enable or disable the capability on individual dial peers.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice service voip

4. qsig decode

5. exit

6. dial-peer voice tag voip

7. supplementary-service h450.7

8. exit

9. dial-peer voice tag pots

10. supplementary-service qsig call-forward

11. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	voice service voip Example: Router(config)# voice service voip	Enters VoIP voice-service configuration mode to define global call transfer and forwarding parameters.
Step 4	qsig decode Example: Router(config-voi-serv)# qsig decode	Enables decoding for QSIG supplementary services.
Step 5	exit Example: Router(config-voi-serv)# exit	Exits VoIP voice-service configuration mode.
Step 6	dial-peer voice tag voip Example: Router(config)# dial-peer voice 1 voip	Enters dial-peer configuration mode to define parameters for an individual dial peer.
Step 7	supplementary-service h450.7 Example: Router(config-dial-peer)# supplementary-service h450.7	Enables H.450.7 supplementary services capabilities exchange on a single dial peer.
Step 8	exit Example: Router(config-dial-peer)# exit	Exits dial-peer configuration mode.
Step 9	dial-peer voice tag pots Example: Router(config)# dial-peer voice 2 pots	Enters dial-peer configuration mode to define parameters for an individual dial peer.
Step 10	supplementary-service qsig call-forward Router(config-dial-peer)# supplementary-service qsig call-forward	Enables QSIG call-forwarding supplementary services (ISO 13873) to forward calls to another number.
Step 11	end Example: Router(config-dial-peer)# end	Returns to privileged EXEC mode.

Disabling SIP Supplementary Services for Call Forward and Call Transfer

To disable REFER messages for call transfers or redirect responses for call forwarding from being sent to the destination by Cisco Unified CME, perform the following steps. You can disable these supplementary features if the destination gateway does not support them.

Prerequisites

Cisco Unified CME 4.1 or a later version.

Restrictions

Disabling supplementary services is supported only when all endpoints are SCCP or all endpoints are SIP. It does not support a mix of SCCP and SIP endpoints.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice service voip
or
dial-peer voice tag voip

4. no supplementary-service sip {moved-temporarily | refer}

5. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	voice service voip or dial-peer voice tag voip Example: Router(config)# voice service voip or Router(config)# dial-peer voice 99 voip	Enters voice-service configuration mode to set global parameters for VoIP features. or Enters dial peer configuration mode to set parameters for a specific dial peer.
Step 4	no supplementary-service sip {moved-temporarily | refer} Example: Router(conf-voi-serv)# no supplementary-service sip refer or Router(config-dial-peer)# no supplementary-service sip refer	Disables SIP call forwarding or call transfer supplementary services globally or for a dial peer. •moved-temporarily—SIP redirect response for call forwarding. •refer—SIP REFER message for call transfers. •Sending REFER and redirect messages to the destination is the default behavior. Note This command is supported for calls between SIP phones and calls between SCCP phones. It is not supported for a mixture of SCCP and SIP endpoints.
Step 5	end Example: Router(config-voi-serv)# end or Router(config-dial-peer)# end	Exits to privileged EXEC mode.

Enabling Interworking with Cisco Unified Communications Manager

If Cisco CME 3.1 or later and Cisco Unified Communications Manager are used in the same network, some additional configuration is necessary, as described in the following sections:

• Configuring Cisco CME 3.1 or Later to Interwork with Cisco Unified Communications Manager

• Enabling Cisco Unified Communications Manager to Interwork with Cisco Unified CME

• Troubleshooting Transfer and Forwarding Configuration

Figure 33 shows a network containing Cisco Unified CME and Cisco Unified Communications Manager systems.

Figure 33 Network with Cisco Unified CME and Cisco Unified Communications Manager

Prerequisites

•Cisco Unified CME must be configured to forward calls using local hairpin routing. For configuration information, see the "Forwarding Calls Using Local Hairpin Routing" section.

Configuring Cisco CME 3.1 or Later to Interwork with Cisco Unified Communications Manager

All of the Cisco IOS commands in this section are optional because they are set by default to work with Cisco Unified Communications Manager. They are included here only to explain how to implement optional capabilities or return nondefault settings to their defaults.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice service voip

4. h323

5. telephony-service ccm-compatible

6. h225 h245-address on-connect

7. exit

8. supplementary-service h225-notify cid-update

9. exit

10. voice class h323 tag

11. telephony-service ccm-compatible

12. h225 h245-address on-connect

13. exit

14. dial-peer voice tag voip

15. supplementary-service h225-notify cid-update

16. voice-class h323 tag

17. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	voice service voip Example: Router(config)# voice service voip	Enters voice-service configuration mode to establish global parameters.
Step 4	h323 Example: Router(conf-voi-serv)# h323	Enters H.323 voice-service configuration mode.
Step 5	telephony-service ccm-compatible Example: Router(conf-serv-h323)# telephony-service ccm-compatible	(Optional) Globally enables a Cisco CME 3.1 or later system to detect a Cisco Unified Communications Manager and exchange calls with it. This is the default. •Use the no form of this command to disable Cisco Unified Communications Manager detection and exchange. We do not recommend using the no form of the command. •Using this command in an H.323 voice class definition allows you to specify this behavior for an individual dial peer.
Step 6	h225 h245-address on-connect Example: Router(conf-serv-h323)# h225 h245-address on-connect	(Optional) Globally enables a delay for the H.225 message exchange of an H.245 transport address until a call is connected. The delay allows the Cisco Unified Communications Manager to generate local ringback for calls to Cisco Unified CME phones. This is the default. •The no form of this command disables the delay. We do not recommend using the no form of the command. •Using this command in an H.323 voice class definition allows you to specify this behavior for an individual dial peer.
Step 7	exit Example: Router(conf-serv-h323)# exit	Exits H.323 voice-service configuration mode.
Step 8	supplementary-service h225-notify cid-update Example: Router(conf-voi-serv)# supplementary-service h225-notify cid-update	(Optional) Globally enables H.225 messages with caller-ID updates to be sent to Cisco Unified Communications Manager. This is the default. •The no form of the command disables caller-ID update. We do not recommend using the no form of the command. This command is also used in dial-peer configuration mode to affect a single dial peer. •If this command is enabled globally and enabled on a dial peer, the functionality is enabled for that dial peer. This is the default. •If this command is enabled globally and disabled on a dial peer, the functionality is disabled for that dial peer. •If this command is disabled globally and either enabled or disabled on a dial peer, the functionality is disabled for that dial peer.
Step 9	exit Example: Router(config-voice-service)# exit	Exits voice-service configuration mode.
Step 10	voice class h323 tag Example: Router(config)# voice class h323 48	(Optional) Creates a voice class that contains commands to be applied to one or more dial peers.
Step 11	telephony-service ccm-compatible Example: Router(config-voice-class)# telephony-service ccm-compatible	(Optional) Enables the dial peer to exchange calls with a Cisco Unified Communications Manager system when this voice class is applied to a dial peer. This is the default. •The no form of the command disables call exchange with Cisco Unified Communications Manager. We do not recommend using the no form of the command.
Step 12	h225 h245-address on-connect Example: Router(config-voice-class)# h225 h245-address on-connect	(Optional) Enables the calls that use this dial peer to delay the exchange of H.225 messages that contain the H.245 transport address until calls are connected, when this voice class is applied to a dial peer. The delay allows the playing of local ringback for calls from Cisco Unified Communications Manager. This is the default. •The no form of this command disables the delay. We do not recommend using the no form of the command.
Step 13	exit Example: Router(config-voice-class)# exit	Exits voice-class configuration mode.
Step 14	dial-peer voice tag voip Example: Router(config)# dial-peer voice 28 voip	(Optional) Enters dial-peer configuration mode to set parameters for an individual dial peer.
Step 15	supplementary-service h225-notify cid-update Example: Router(config-dial-peer)# no supplementary-service h225-notify cid-update	(Optional) Enables H.225 messages with caller-ID updates to Cisco Unified Communications Manager for a specific dial peer. This is the default. •The no form of the command disables caller-ID updates. We do not recommend using the no form of the command.
Step 16	voice-class h323 tag Example: Router(config-dial-peer)# voice-class h323 48	(Optional) Applies the previously defined voice class with the specified tag number to this dial peer.
Step 17	end Example: Router(config-dial-peer)# end	Returns to privileged EXEC mode.

What to Do Next

Set up Cisco Unified Communications Manager using the configuration procedure in the "Enabling Cisco Unified Communications Manager to Interwork with Cisco Unified CME" section.

Enabling Cisco Unified Communications Manager to Interwork with Cisco Unified CME

To enable Cisco Unified Communications Manager to interwork with a Cisco CME 3.1 or later system, perform the following steps in addition to the normal Cisco Unified Communications Manager configuration.

SUMMARY STEPS

1. Set Cisco Unified Communications Manager service parameters.

2. Configure the Cisco CME 3.1 or later system as an ICT in the Cisco Unified Communications Manager network.

3. Ensure that the Cisco Unified Communications Manager network uses an MTP.

4. Set up dial peers to establish routing.

DETAILED STEPS

---

Step 1 Set Cisco Unified Communications Manager service parameters. From Cisco Unified Communications Manager Administration, choose Service Parameters. Choose the Cisco Unified Communications Manager service, and make the following settings:

•Set the H323 FastStart Inbound service parameter to False.

•Set the Send H225 User Info Message service parameter to H225 Info for Ring Back.

Step 2 Configure the Cisco CME 3.1 or later system as an ICT in the Cisco Unified Communications Manager network. For information about different intercluster trunk types and configuration instructions, see the Cisco  Unified Communications Manager documentation.

Step 3 Ensure that the Cisco Unified Communications Manager network uses an MTP. The MTP is required to provide DSP resources for transcoding and for sending and receiving G.729 calls to the Cisco CME 3.1 or later system. All media streams between Cisco Unified Communications Manager and Cisco CME 3.1 or later must pass through the MTP because Cisco CM  3.1 does not support transcoding. For more information, see the Cisco Unified Communications Manager documentation.

Step 4 Set up dial peers to establish routing using the instructions in the Dial Peer Configuration on Voice Gateway Routers guide.

---

Troubleshooting Transfer and Forwarding Configuration

---

Step 1 If you encounter lack of ringback on direct calls from a Cisco Unified Communications Manager phone to an IP phone on a Cisco Unified CME system, check the show running-config command output to ensure that the following two commands do not appear: no h225 h245-address on-connect and no telephony-service ccm-compatible. These commands should be enabled, which is their default state.

Step 2 Use the debug h225 asn1 command to display the H.323 messages that are sent from the Cisco Unified CME system to the Cisco Unified Communications Manager system to see if the H.245 address is being sent too early.

Step 3 For calls that are routed using VoIP-to-VoIP connections, use the show voip rtp connections detail command to display the call identification number, IP addresses, and port numbers involved for all VoIP call legs. This command includes VoIP-to-POTS and VoIP-to-VoIP call legs. The following is sample output for this command:

Router# show voip rtp connections detail




VoIP RTP active connections :

No. CallId  dstCallId         LocalRTP     RmtRTP       LocalIP RemoteIP

1 7 8 16586 22346 172.27.82.2 172.29.82.2

2 8 7 17010 16590 172.27.82.2 209.165.202.129

Found 2 active RTP connections




Step 4 Use the show call prompt-mem-usage detail command to see information on ringback tone generation that uses the interactive voice response (IVR) prompt playback mechanism. This ringback is needed for hairpin transfers that are committed during the alerting-of-the-transfer-destination phase of the call and for calls to destinations that do not provide in-band ringback tone, such as IP phones (FXS analog ports do provide in-band ringback tone). Ringback tone is played to the transferred party by the Cisco Unified CME system that performs the transfer (the system attached to the transferring party). The system automatically generates tone prompts as needed based on the network-locale setting for the Cisco Unified CME system.

If you are not getting ringback tone when you should, use the show call prompt-mem-usage command to ensure that the correct prompt is loaded and playing. The following sample output indicates that a prompt is playing ("Number of prompts playing") and indicates the country code used for the prompt (GB for Great Britain) and the codec.

Router# show call prompt-mem-usage detail




Prompt memory usage:

config'd wait active free mc total ms total

file(s) 0200 0001 -001 00200 00001 00002

memory 02097152 00003000 00000000 02094152 00003000

Prompt load counts: (counters reset 0)

success 0(1st try) 0(2nd try), failure 0

Other mem block usage:

mcDynamic mcReader

gauge 00001 00001

Number of prompts playing: 1

Number of start delays : 0

MCs in the ivr MC sharing table

===============================

Media Content: NoPrompt (0x83C64554)

URL:

cid=0, status=MC_READY size=24184 coding=g711ulaw refCount=0

Media Content: tone://GB_g729_tone_ringback (0x83266EC8)

URL: tone://GB_g729_tone_ringback

---

SIP: Configuring SIP-to-SIP Phone Call Forwarding

To configure SIP-to-SIP call forwarding using a back-to-back user agent (B2BUA) which allows call forwarding on any dial peer, perform the following steps.

Prerequisites

•Connections between specific types of endpoints in a Cisco IP-to-IP gateway must be configured by using the allow-connections command. For configuration information, see the "Enabling Calls in Your VoIP Network" on page 110.

•Cisco CME 3.4 or a later version.

Restrictions

•SIP-to-SIP call forwarding is invoked only if that phone is dialed directly. Call forwarding is not invoked when the phone number is called through a sequential, longest-idle, or peer hunt group.

•If call forwarding is configured for a hunt group member, call forward is ignored by the hunt group.

•In Cisco Unified CME 4.1 and later versions, Call Forward All requires SIP phones to be configured with a directory number (using dn keyword in number command); direct line numbers are not supported.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice register dn dn-tag

4. call-forward b2bua all directory-number

5. call-forward b2bua busy directory-number

6. call-forward b2bua mailbox directory-number

7. call-forward b2bua noan directory-number timeout seconds

8. call-forward b2bua unreachable directory-number

9. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	voice register dn dn-tag Example: Router(config)# voice register dn 1	Enters voice register dn mode to define a directory number for a SIP phone, intercom line, voice port, or an MWI.
Step 4	call-forward b2bua all directory- number Example: Router(config-register-dn)# call-forward b2bua all 5005	Enables call forwarding for a SIP back-to-back user agent so that all incoming calls will be forwarded to the designated directory-number. •In Cisco CME 3.4 and Cisco Unified CME 4.0, this command is also available in voice register pool configuration mode. The configuration under voice register dn takes precedence over the configuration under voice register pool. •If the call-forward b2bua all command is configured in voice register pool configuration mode, it applies to all directory numbers on the phone.
Step 5	call-forward b2bua busy directory- number Example: Router(config-register-dn)# call-forward b2bua busy 5006	Enables call forwarding for a SIP back-to-back user agent so that incoming calls to an extension that is busy will be forwarded to the designated directory number. •In Cisco CME 3.4 and Cisco Unified CME 4.0, this command is also available in voice register pool configuration mode. The configuration under voice register dn takes precedence over the configuration under voice register pool.
Step 6	call-forward b2bua mailbox directory- number Example: Router(config-register-dn)# call-forward b2bua mailbox 5007	Enables call forwarding for a SIP back-to-back user agent so that incoming calls that have been forwarded to a busy or no-answer extension will be forwarded to the recipient's voice mail. •In Cisco CME 3.4 and Cisco Unified CME 4.0, this command is also available in voice register pool configuration mode. The configuration under voice register dn takes precedence over the configuration under voice register pool.
Step 7	call-forward b2bua noan directory- number timeout seconds Example: Router(config-register-dn)# call-forward b2bua noan 5010 timeout 10 or Router(config-register-pool)# call-forward b2bua noan 5010 timeout 10	Enables call forwarding for a SIP back-to-back user agent so that incoming calls to an extension that does not answer will be forwarded to the designated directory number. •In Cisco CME 3.4 and Cisco Unified CME 4.0, this command is also available in voice register pool configuration mode. The configuration under voice register dn takes precedence over the configuration under voice register pool. •timeout seconds—Duration that a call can ring before it is forwarded to the destination directory number. Range: 3 to 60000. Default: 20.
Step 8	call-forward b2bua unreachable directory- number Example: Router(config-register-dn)# call-forward b2bua unreachable 5009 or Router(config-register-pool)# call-forward b2bua unreachable 5009	(Optional) Enables call forwarding for a SIP back-to-back user agent so that calls can be forwarded to a phone that has not registered in Cisco Unified CME. •Target directory-number must be configured in Cisco Unified CME. •In Cisco CME 3.4 and Cisco Unified CME 4.0, this command is also available in voice register pool configuration mode. The configuration under voice register dn takes precedence over the configuration under voice register pool. •This command was removed in Cisco Unified CME 4.1.
Step 9	end Example: Router(config-register-dn)# end	Exits configuration mode and enters privileged EXEC mode.

SIP: Configuring Call-Forwarding-All Soft Key URI

To specify the uniform resource identifier (URI) for the call forward all (CfwdAll) soft key on supported SIP phones, perform the following steps. This URI and the call forward number is sent to Cisco Unified CME when a user enables Call Forward All on a SIP phone.

Prerequisites

•Cisco Unified CME 4.1 or a later version.

•The mode cme command must be enabled in Cisco Unified CME.

•Call Forward All must be enabled on the directory number. For information, see "SIP: Configuring SIP-to-SIP Phone Call Forwarding".

Restrictions

•This feature is supported only on Cisco Unified IP Phone 7911G, 7941G, 7941GE, 7961G, 7961GE, 7970G, and 7971GE.

•If a user enables Call Forward All using the CfwdAll soft key, it is enabled on the primary line.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice register global

4. call-feature-uri cfwdall service-uri

5. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	voice register global Example: Router(config)# voice register global	Enters voice register global configuration mode to set global parameters for all supported SIP phones in a Cisco Unified CME environment.
Step 4	call-feature-uri cfwdall service-uri Example: Router(config-register-global)# call-feature-uri cfwdall http://1.4.212.11/cfwdall	Specifies the URI for soft keys on SIP phones connected to a Cisco Unified CME router.
Step 5	end Example: Router(config-register-global)# end	Exits to privileged EXEC mode.

SIP: Specifying Number of 3XX Responses To be Handled

To specify how many subsequent 3XX responses an originating SIP phone can handle for a single call when the terminating side is a forwarding party which does not use B2BUA, perform the following steps.

Prerequisites

•Cisco CME 3.4 or a later version.

•The mode cme command must be enabled

SUMMARY STEPS

1. enable

2. configure terminal

3. voice register global

4. phone-redirect-limit number

5. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	voice register global Example: Router(config)# voice register global	Enters voice register global configuration mode to set parameters for all supported SIP phones in Cisco Unified CME.
Step 4	phone-redirect-limit number Example: Router(config-register-global)# phone-redirect-limit 8	Changes the default number of 3XX responses a SIP phone that originates a call can handle for a single call. •Default: 5.
Step 5	end Example: Router(config-register-global)# end	Exits configuration mode and enters privileged EXEC mode.

SIP: Configuring Call Transfer

To create and apply a template to enable call transfer softkeys on an individual SIP phone in Cisco Unified CME, perform the following steps.

Prerequisites

Cisco CME 3.4 or a later version.

Restrictions

•Blind transfer is not supported on certain phones such as Cisco Unified IP Phone 7911G, 7941G, 7941GE, 7961G, 7961GE, 7970G, or 7971GE.

•In Cisco Unified CME 4.1, the soft key display can be customized only for certain IP phones, such as Cisco Unified IP Phone 7911G, 7941G, 7941GE, 7961G, 7961GE, 7970G, and 7971GE. For configuration information, see "SCCP: Modifying Soft-Key Display" on page 878.

SUMMARY STEPS

1. enable

2. configure terminal

3. voice register template template-tag

4. transfer-attended

5. transfer-blind

6. voice register template template-tag

7. exit

8. voice register pool pool-tag

9. template template-tag

10. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	voice register template template-tag Example: Router(config)# voice register template 1	Enters voice register template configuration mode to define a template of common parameters for SIP phones in Cisco Unified CME. •Range is 1 to 5.
Step 4	transfer-attended Example: Router(config-register-template)# transfer-attended	Enable a soft key for attended transfer on any supported SIP phone that uses a template in which this command is configure.
Step 5	transfer-blind Example: Router(config-register-template)# transfer-blind	Enable a soft key for blind transfer on any supported SIP phone that uses a template in which this command is configure.
Step 6	exit Example: Router(config-register-template)# exit	Exits configuration mode to the next highest mode in the configuration mode hierarchy.
Step 7	voice register pool pool-tag Example: Router(config)# voice register pool 3	Enters voice register pool configuration mode to set phone-specific parameters for SIP phones.
Step 8	template template-tag Example: Router(config-register-pool)# voice register pool 1	Applies a template created with the voice register template command. •template-tag—Range: 1 to 5.
Step 9	end Example: Router(config-register-pool)# end	Exits configuration mode and enters privileged EXEC mode.

Configuration Examples for Call Transfer and Forwarding

The following configuration examples are included in this section:

• H.450.2 and H.450.3: Example

• Basic Call Forwarding: Example

• Call Forwarding Blocked for Local Calls: Example

• Selective Call Forwarding: Example

• Call Transfer: Example

• H.450.12: Example

• H.450.7 and QSIG Supplementary Services: Example

• Cisco Unified CME and Cisco Unified Communications Manager in Same Network: Example

• H.450 Tandem Gateway Working with Cisco Unified CME and Cisco Unified Communications Manager: Example

• Forwarding Calls to Cisco Unity Express: Example

H.450.2 and H.450.3: Example

The following example sets all transfers and forwards that are initiated by a Cisco CME 3.0 or later system to use the H.450 standards, globally enables H.450.2 and H.450.3 capabilities, and disables those capabilities for dial peer 37. The supplementary-service commands under voice-service configuration mode are not necessary because these values are the default, but they are shown here for illustration.

telephony-service

 transfer-system full-consult

 transfer-pattern .T

 call-forward pattern .T

!

voice service voip

 supplementary-service h450.2

 supplementary-service h450.3

!

dial-peer voice 37 voip

 destination-pattern 555....

 session target ipv4:10.5.6.7

 no supplementary-service h450.2

 no supplementary-service h450.3

Basic Call Forwarding: Example

The following example sets up forwarding for extension 2777 to extension 2513 on all calls, busy, and no answer. During night service hours, calls are forwarded to a different number, extension 2879.

ephone-dn 20

 number 2777

 call-forward all 2513

 call-forward busy 2513

 call-forward noan 2513 timeout 45

 call-forward night-service 2879

Call Forwarding Blocked for Local Calls: Example

In the following example, extension 2555 is configured to not forward local calls that are internal to the Cisco Unified CME system. Extension 2222 dials extension 2555. If 2555 is busy, the caller hears a busy tone. If 2555 does not answer, the caller hears ringback. The internal call is not forwarded.

ephone-dn 25

 number 2555

 no forward local-calls

 call-forward busy 2244

 call-forward noan 2244 timeout 45

Selective Call Forwarding: Example

The following example sets call forwarding on busy and no answer for ephone-dn 38 only for its primary number, 2777. Callers who dial 2778 will hear a busy signal if the ephone-dn is busy or ringback if there is no answer.

ephone-dn 38

 number 2777 secondary 2778

 call-forward busy 3000 primary

 call-forward noan 3000 primary timeout 45

Call Transfer: Example

The following example limits transfers from ephone 6, extension 2977, to numbers containing a maximum of 8 digits.

telephony-service

 load 7910 P00403020214

 load 7960-7940 P00305000600

 load 7914 S00103020002

 load 7905 CP7905040000SCCP040701A

 load 7912 CP7912040000SCCP040701A

 max-ephones 100

 max-dn 500

 ip source-address 10.104.8.205 port 2000

 max-redirect 20

 system message XYZ Inc.

 create cnf-files version-stamp 7960 Jul 13 2004 03:39:28

 voicemail 7189

 max-conferences 8 gain -6

 moh music-on-hold.au

 web admin system name admin1 password admin1

 dn-webedit

 time-webedit

 transfer-system full-consult

 transfer-pattern 91..........

 transfer-pattern 92......

 transfer-pattern 93......

 transfer-pattern 94......

 transfer-pattern 95......

 transfer-pattern 96......

 transfer-pattern 97......

 transfer-pattern 98......

 transfer-pattern 99......

 secondary-dialtone 9

 fac standard




ephone-template 2

 transfer max-length 8




ephone-dn 4

 number 2977




ephone 6

 button 1:4

 ephone-template 2

H.450.12: Example

The following example globally disables H.450.12 capabilities and then enables them only on dial peer 24.

voice service voip

 no supplementary-service h450.12

!

dial-peer voice 24 voip

 destination-pattern 555....

 session target ipv4:10.5.6.7

 supplementary-service h450.12

H.450.7 and QSIG Supplementary Services: Example

The following example implements QSIG supplementary services on extension 74367 and globally enables H.450.7 supplementary services and QSIG call-forwarding supplementary services.

telephony-service

 voicemail 74398

 transfer-system full-consult




ephone-dn 25

 number 74367

 mwi qsig

 call-forward all 74000




voice service voip

 supplementary-service h450.7




voice service pots

 supplementary-service qsig call-forward

Cisco Unified CME and Cisco Unified Communications Manager in Same Network: Example

The following example shows a running configuration for a Cisco CME 3.1 or later router that has a Cisco Unified Communications Manager in its network.

Router# show running-config




version 12.3

service timestamps debug datetime msec

service timestamps log datetime msec

no service password-encryption

!

hostname Router

!

enable password pswd

!

aaa new-model

!

!

aaa session-id common

no ip subnet-zero

!

ip dhcp pool phone1

 host 172.24.82.3 255.255.255.0

 client-identifier 0100.07eb.4629.9e

 default-router 172.24.82.2

 option 150 ip 172.24.82.2

!

ip dhcp pool phone2

 host 172.24.82.4 255.255.255.0

 client-identifier 0100.0b5f.f932.58

 default-router 172.24.82.2

 option 150 ip 172.24.82.2

!

ip cef

no ip domain lookup

no mpls ldp logging neighbor-changes

no ftp-server write-enable

!

voice service voip

 allow-connections h323 to h323

!

voice class codec 1

 codec preference 1 g711ulaw

!

no voice hpi capture buffer

no voice hpi capture destination

!

interface FastEthernet0/0

 ip address 172.24.82.2 255.255.255.0

 duplex auto

 speed auto

 h323-gateway voip interface

 h323-gateway voip bind srcaddr 172.24.82.2

!

ip classless

ip route 0.0.0.0 0.0.0.0 172.24.82.1

ip route 192.168.254.254 255.255.255.255 172.24.82.1

!

ip http server

!

tftp-server flash:P00303020700.bin

!

voice-port 1/0/0

!

voice-port 1/0/1

!

dial-peer cor custom

!

dial-peer voice 1001 voip

 description points-to-CCM

 destination-pattern 1.T

 voice-class codec 1

 session target ipv4:172.26.82.10

!

dial-peer voice 1002 voip

 description points to router

 destination-pattern 4...

 voice-class codec 1

 session target ipv4:172.25.82.2

!

dial-peer voice 1 pots

 destination-pattern 3000

 port 1/0/0

!

dial-peer voice 1003 voip

 destination-pattern 26..

 session target ipv4:10.22.22.38

!

!

telephony-service

 load 7960-7940 P00303020700

 max-ephones 48

 max-dn 15

 ip source-address 172.24.82.2 port 2000

 create cnf-files version-stamp Jan 01 2002 00:00:00

 keepalive 10

 max-conferences 4

 moh minuet.au

 transfer-system full-consult

 transfer-pattern ....

!

ephone-dn 1

 number 3001

 name abcde-1

 call-forward busy 4001

!

ephone-dn 2

 number 3002

 name abcde-2

!

ephone-dn 3

 number 3003

 name abcde-3

!

ephone-dn 4

 number 3004

 name abcde-4

!

ephone 1

 mac-address 0003.EB27.289E

 button 1:1 2:2

!

ephone 2

 mac-address 000D.39F9.3A58

 button 1:3 2:4

!

line con 0

 exec-timeout 0 0

 logging synchronous

line aux 0

line vty 0 4

 password pswd

!

end

H.450 Tandem Gateway Working with Cisco Unified CME and Cisco Unified Communications Manager: Example

The following example shows a sample configuration for a Cisco CME 3.1 or later system that is linked to an H.450 tandem gateway that serves as a proxy for Cisco Unified Communications Manager.

Router# show running-config




Building configuration...




Current configuration : 1938 bytes

!

version 12.3

service timestamps debug datetime msec

service timestamps log datetime msec

no service password-encryption

!

hostname Router

!

boot-start-marker

boot-end-marker

!

enable password pswd

!

aaa new-model

!

aaa session-id common

no ip subnet-zero

!

ip cef

no ip domain lookup

no ftp-server write-enable

no scripting tcl init

no scripting tcl encdir

!

voice call send-alert

!

voice service voip

 allow-connections h323 to h323

 supplementary-service h450.12

 h323

!

voice class codec 1

 codec preference 1 g711ulaw

 codec preference 2 g729r8

 codec preference 3 g729br8

!

interface FastEthernet0/0

 ip address 172.27.82.2 255.255.255.0

 duplex auto

 speed auto

 h323-gateway voip interface

 h323-gateway voip h323-id host24

!

ip classless

ip route 0.0.0.0 0.0.0.0 172.26.82.1

ip route 0.0.0.0 0.0.0.0 172.27.82.1

ip http server

!

dial-peer cor custom

!

dial-peer voice 1001 voip

 description points-to-CCM

 destination-pattern 4...

 session target ipv4:172.24.89.150

!

dial-peer voice 1002 voip

 description points to CCME1

 destination-pattern 28..

 session target ipv4:172.24.22.38

!

dial-peer voice 1003 voip

 description points to CCME3

 destination-pattern 9...

 session target ipv4:192.168.1.29

!

dial-peer voice 1004 voip

 description points to CCME2

 destination-pattern 29..

 session target ipv4:172.24.22.42

!

line con 0

 exec-timeout 0 0

 logging synchronous

line aux 0

line vty 0 4

 password pswd

!

end

Forwarding Calls to Cisco Unity Express: Example

The following example enables the ability to forward calls that originate from Cisco Unified Communications Manager phones and are routed through a Cisco Unified CME system to a Cisco Unity Express extension. Call forwarding is enabled for all calling parties, H.450.3 is disabled, and connections are allowed to SIP endpoints.

telephony-service

 call-forward pattern .T




voice service voip

 no supplementary-service h450.3

 allow connections from h323 to sip

Where to Go Next

If you are finished modifying the configuration, generate a new configuration file and restart the phones. See "Generating Configuration Files for Phones" on page 265.

Soft Keys

To block the function of the call-forward-all or transfer soft key without removing the key display or to remove the soft key from one or more phones, see the "How to Customize Soft Keys" section on page 878.

Feature Access Codes (FACs)

Phone users can activate and deactivate a phone's call-forward-all setting by using a feature access code (FAC) instead of a soft key on the phone if standard or custom FACs have been enabled for your system. The following are the standard FACs for call forward all:

•callfwd all—Call forward all calls. Standard FAC is **1 plus an optional target extension.

•callfwd cancel—Cancel call forward all calls. Standard FAC is **2.

For more information about FACs, see "Configuring Feature Access Codes" on page 775.

Night Service

Calls can be automatically forwarded during night service hours, but you must define the night-service periods, which are the dates or days and hours during which night service will be active. For instance, you may want to designate night service periods that include every weeknight between 5 p.m. and 8 a.m. and all day every Saturday and Sunday. For more information, see "Configuring Call-Coverage Features" on page 581.

Additional References

The following sections provide references related to Cisco Unified CME features.

Related Documents

Related Topic	Document Title
Cisco Unified CME configuration	• Cisco Unified CME Command Reference • Cisco Unified CME Documentation Roadmap
Cisco IOS commands	• Cisco IOS Voice Command Reference • Cisco IOS Software Releases 12.4T Command References
Cisco IOS configuration	• Cisco IOS Voice Configuration Library • Cisco IOS Software Releases 12.4T Configuration Guides
Phone documentation for Cisco Unified CME	• Quick Reference Cards • User Guides

Technical Assistance

Description	Link
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register on Cisco.com.	http://www.cisco.com/techsupport

Feature Information for Call Transfer and Forwarding

Table 30 lists the features in this module and enhancements to the features by version.

To determine the correct Cisco IOS release to support a specific Cisco Unified CME version, see the Cisco Unified CME and Cisco IOS Software Version Compatibility Matrix at http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_documentation_roadmap09186a0080189132.html.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

---

Note Table 30 lists the Cisco Unified CME version that introduced support for a given feature. Unless noted otherwise, subsequent versions of Cisco Unified CME software also support that feature.

---

Table 30 Feature Information for Call Transfer and Forwarding

Feature Name	Cisco Unified CME Version	Feature Information
Call Forwarding	4.1	•Call Forward All synchronization between Cisco Unified CME and SIP phones was added. •Disabling SIP supplementary services for call forward and call transfer was added.
	4.0	•Automatic call forwarding during night service was introduced. •Selective call forwarding was introduced. •Forwarding of local (internal) calls can be blocked. •H.450.7 standards support and QSIG supplementary services capability was introduced.
	3.4	Calls into a SIP device can be forwarded to other SIP or SCCP devices including Cisco Unity, third- party voice mail systems, or an auto-attendant (AA) or other interactive voice response (IVR) devices. SCCP devices may also be forwarded to SIP devices.
	3.1	•Number of digits that can be entered using the CfwdALL (call-forward all) soft key can be limited. •H.450.12 standards support, which provide dynamic detection of H.450.2 and H.450.3 capabilities on a call-by-call basis, was introduced.
	3.0	•CFwdALL soft key was introduced. •Local hairpin call routing was supported as an option for networks that cannot support H.450 call transfer and forwarding. This feature requires installation of the Tcl script app_h450_transfer.2.0.0.8.tcl or a later version.
	2.1	Call forwarding using the H.450.3 standard was introduced.
Call Forwarding	1.0	Call forwarding for all calls, busy conditions, and no-answer conditions was introduced, using a Cisco-proprietary method.
Call Transfer	4.1	•Disabling SIP supplementary services for call transfer and call forward was added.
	4.0	•Default for the transfer-system command was changed from the blind keyword to the full-consult keyword. •Transfers to phones outside the Cisco Unified CME system can be blocked for individual ephones. •Number of digits in transfer destination numbers can be limited.
	3.4	Support for attended and blind transfer s using SIP IP phone directly connected to Cisco CME.
	3.2	•Consultative transfer to monitored lines using direct station select was introduced. •Transcoding between G.711 and G.729 is supported when one leg of a Voice over IP (VoIP)-to-VoIP hairpin call uses G.711 and the other leg uses G.729.
	3.1	Support was introduced for the following: •Enhancements for VoIP networks which contain a mix of platforms that support H.450.2 and H.450.3 standards, such as Cisco CME 3.1, Cisco CME 3.0, Cisco ITS V2.1, and platforms that do not support H.450.2 and H.450.3 standards, such as Cisco Unified Communications Manager, Cisco BTS Softswitch (BTS), and Cisco PSTN Gateway (PGW). •H.450.12 standards, which provide dynamic detection of H.450.2 and H.450.3 capabilities on a call-by-call basis. •Automatic detection of Cisco Unified Communications Manager endpoints. •Hairpin VoIP-to-VoIP call routing and routing to an H.450 tandem gateway. •Hairpin call routing does not require a Tcl script.
	3.0	Local hairpin call routing was supported as an option for networks that cannot support H.450 call transfer and forwarding. This feature requires installation of the Tcl script app_h450_transfer.2.0.0.8.tcl or a later version.
	2.1	Consultative transfer using the ITU-T H.450.2 standard was introduced.
	1.0	Call transfer was introduced, using a Cisco proprietary method.

Posted: Thu Sep 13 15:36:07 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.