+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: Dect Phone Series (/forumdisplay.php?fid=6)
+--- Forum: W52P (Wireless) (/forumdisplay.php?fid=23)
+--- Thread: Blind transfer unsuccessful - W52P and Cisco Call Manager 9.1.2 (/showthread.php?tid=12003)
Blind transfer unsuccessful - W52P and Cisco Call Manager 9.1.2 - fidotas - 01-08-2016 12:26 PM
I'm attempting to get a Yealink W52P working with Cisco's Call Manager 9.1.2. Everything is working as expected except for call transfers. The scenario is fairly basic:
Phone A calls the Yealink W52P who transfers to the call to Phone B.
I've also confirmed it occurs when the Yealink W52P initiates a call to Phone A and attempts to transfer the call to Phone B.
A call transfer is initiated either as a "blind transfer" where with an active call in progress on the W52P handset we press the Options key then Transfer, enter the destination number (72038) and press the Transfer key again to complete. Or a transfer is initiated as a "consultative transfer" where with an active call in progress on the W52P handset we press the Options key then Transfer, enter the destination number (72038) and press the Green Speaker button to initiate a second call. The second call connects successfully, we speak with the person on Phone B then press the Transfer key on the W52P handset again to complete the transfer.
"Blind transfer"s fail completely. The W52P indicates the transfer is complete with a "Call transferred" message on the display (I can see in SIP traces the correct exchange of REFER, ACK and NOTIFY) however it plays an audible BEEP BEEP BEEP indicating the call has terminated and the call to User A is terminated. User B never receives any incoming call notification.
"Consultative transfer"s work. The two call legs are successfully bridged and User A can speak with User B. However the W52P handset emits an audible BEEP BEEP BEEP indicating the call has terminated despite displaying a successful message.
Are you able to assist with getting blind transfers working? Removing the incorrect audible alert would also be great as it will confuse handset users making them believe the transfer was unsuccessful.
RE: Blind transfer unsuccessful - W52P and Cisco Call Manager 9.1.2 - Yealink_Michael - 01-08-2016 08:06 PM
hi
thanks for your information
1. for this issue , as you mentioned , you are using platform Cisco Call Manager 9.1.2 , but the firmware you are using is 25.73.193.40, this firmware is just for Broadsoft platform !
so please upgrade to the newest commercial firmware and then test again , firmware download link :
http://support.yealink.com/attachmentDownload/download?path=upload%2Fattachment%2F2015-7-4%2F6%2F5cadf3c1-5e00-4c37-9a04-aaa6693b933e%2F25.73.0.40.zip
2. as i can see from the trace file , the called in number is +61487892002 , it is a PSTN number right ? and it call to 72033 then 72033 blind transfer to 72038 , the process seems fine ! so is User B (72038) a yealink phone ? if yes , please provide the trace file of B ,so that we can confirm whether any INVITE is send to it , if no , then is it server side issue !
Note : all yealink phones , please using the commercial firmware but not Broadsofy firmware !
at last , for BEEP issue, did the W52P connect with a Reapter ? if yes , you can follow the guide attached to disable the verification tone !
if any update , please send us an email to support@yealink.com so that you issue will not be missed !
TKS & BR
Michael
RE: Blind transfer unsuccessful - W52P and Cisco Call Manager 9.1.2 - fidotas - 01-12-2016 08:27 AM
(01-08-2016 08:06 PM)Yealink_Michael Wrote: 1. for this issue , as you mentioned , you are using platform Cisco Call Manager 9.1.2 , but the firmware you are using is 25.73.193.40, this firmware is just for Broadsoft platform !
Ah, there's no description on the firmware download page describing what each firmware version is for. I have actually tried 25.73.193.40 and started working my way backwards in version numbers to see if it was just a firmware issue revision.
I'll regenerate the traces using the latest firmware for you.
(01-08-2016 08:06 PM)Yealink_Michael Wrote: 2. as i can see from the trace file , the called in number is +61487892002 , it is a PSTN number right ? and it call to 72033 then 72033 blind transfer to 72038 , the process seems fine ! so is User B (72038) a yealink phone ? if yes , please provide the trace file of B ,so that we can confirm whether any INVITE is send to it , if no , then is it server side issue !
No, the only Yealink handset is 72033. It doesn't matter whether the other parties are Cisco IP phones or PSTN numbers. The behaviour is the same. As mentioned from a SIP trace perspective it all looks fine however the call terminates instead of completing successfully.
RE: Blind transfer unsuccessful - W52P and Cisco Call Manager 9.1.2 - sirius - 01-28-2016 03:37 AM
Hello fidotas,
I was wondering if you ever got the issue with Blind Transfer solved?
I am trying to setup W52P with Cisco Call Manager as well but keep getting 'Register Fail'. Was just wondering if you created an 'How to' or something similar when you set yours up.