Field Notice: FN - 62436 - Cisco Unity Express 2.3.1 Default Transfer Mode Does Not Work With Cisco Unified CallManager Express 3.2 and 3.3

Available Languages

Updated:June 2, 2006
Document ID:FN62436

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.


June 2, 2006

NOTICE:

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.

Products Affected

Products Affected

Comments

Unity Express - 2.3.1

With Cisco Unified CallManager Express 3.2 and 3.3

Problem Description

When semi-attended and attended call transfers are done from Cisco Unity Express 2.3.1 with Cisco Unified CallManager Express 3.2 and 3.3, call transfer fails.

Background

In Cisco Unity Express 2.3.1, the default transfer mode is set to semi-attended transfer. During testing it was found that semi-attended and attended transfers do not work with Cisco Unified CallManager Express 3.2 and 3.3.

Cisco Unified CallManager Express version 3.4 and later versions do not exhibit this problem with Cisco Unity Express 2.3.1.

Cisco Unity Express 2.2 and prior versions only support blind transfer mode. There is no option to select semi-attended or attended transfers in these releases.

Problem Symptoms

Sometimes the call is not transferred to the destination or the transfer is done but the voice path is not through between the transferee and transfer-to party.

Scenario 1:

A makes call to AA.

AA transfers (semi-attended or attended) call to B.

B does not answer.

After no answer the call should go to Voicemail but the call does not get forwarded to Voicemail.

Scenario 2:

A makes call to AA.

AA transfers (semi-attended or attended) call to B.

B answers but there is no voice path between A and B.

Workaround/Solution

If this issue is seen, change the default transfer mode to blind (bye-also) using the following commands:

se-cue> conf t 
se-cue(config)> ccn subsystem sip 
se-cue(config-sip)> transfer-mode blind bye-also 
se-cue(config-sip)> end 
se-cue(config)> end

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

DDTS

Description

CSCse26216 (registered customers only)

When semi-attended and attended xfr are done from CUE, xfr fails in CME

Revision History

Revision

Date

Comment

1.0

02-JUN-2006

Initial Public Release

NetPro Discussion Forums - Featured Conversations

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products