Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
Community Member

Problems with call transfer using CME


We are using the CME 4.1 version in one site. When someone calls a cellular nummber a voip dial peer sends this call to a CME 3.2 in another site which has some connections with the cellular network.

The problem is that when the caller (in the CME 4.1) tries to transfer the call to another extension in the same CME 4.1 the call drops.

What causes this problem? How can we solve it? Would this problem be solved using H.450.2 between the two CMEs to handle the call transfer?

Thanks in advance for your help.

Hall of Fame Super Gold

Re: Problems with call transfer using CME


are you using SIP or H.323 between the two CME's ?

Community Member

Re: Problems with call transfer using CME


Sorry. The only think that we have configured in the CME4.0 is the following dial peer. We haven't set any special communication between the two CMEs.

Dial-peer voice 103 voip

Destination-pattern 06........

Session target ipv4:2ndCME32_IPaddress

voice-class codec 20

Community Member

Re: Problems with call transfer using CME

Call Transfer Methods for VoIP

This section describes several methods for implementing call transfer across VoIP networks:

? H.450 and SIP

? Hairpin Routing

? H.450.12

? Empty Capabilities Set

H.450 and SIP

The ITU-T standards-based H.450.2 transfer method and the Cisco method operate in a similar way. In both cases, when a call transfer occurs, a control message is sent back to the transferee party to request that the transferee initiates a follow-on call from the transferee to the final transfer-to destination. In the H.450.2 case, the follow-on call originated by the transferee can act to replace the transfer consultation call that is in progress between the transferor and the transfer-to destination party. The consultation call between transferor and transfer-to and the original transferee-transferor call are not torn down until the "replaces" operation is completed successfully. The term replaces is used here in the context of "Call 2 replaces call 1." If for any reason the replacement operation fails, it is usually possible for the transferor to reconnect the call to the transferee. The H.450.2 mechanism works in a manner similar to the REFER method used for SIP VoIP calls. The Cisco transfer mechanism does not support the call replacement mechanism and, therefore, allows you to perform only blind call transfers. This proprietary method is similar to the older BYE/ALSO method that was used to perform blind transfers for SIP VoIP calls. The BYE/ALSO method has been mostly superseded by the SIP REFER method.

Both of these H.323 call transfer methods result in an optimal direct call path between the transferee and the transfer-to party after the call transfer is committed.

Hairpin Routing

The third alternative is to hairpin route the VoIP call transfer. In this case, the original transferee-to-transferor VoIP call leg is kept, and a second transferor to transfer-to VoIP call leg is created for the consultation call phase of the transfer. When the transfer is committed, the original and consultation call legs are simply bridged together at the Cisco Unified CME router. This method has the advantage that it has no end-to-end dependency on the capabilities of the transferee or transfer-to VoIP endpoint.

To enable hairpin routing of VoIP calls that cannot be transferred (or forwarded) using H.450, use the allow-connections command. The following example shows a call transfer configuration using this command.

voice service voip

supplementary-service h450.12

allow-connections h323 to h323


transfer-system full-consult

transfer-pattern .T

The configuration shown in the preceding example turns on the H.450.2 (transfer-system full-consult) and H.450.12 services, allows VoIP-to-VoIP hairpin call routing (allow-connections) for calls that don't support H.450, and permits transfers to all possible destinations (transfer-pattern). The transfer permission is set to .T to provide full wildcard matching for any number of digits. (The T stands for terminating the transfer destination digit entry with a timeout.)

The following example shows a configuration for more restrictive transfer permissions.


transfer-system full-consult

transfer-pattern 1...

transfer-pattern 2... blind

CreatePlease to create content