[YMCS/YDMP Free Trial Program]Yealink would like to offer Free Trial Program of Yealink device management service for our current eligible customers. You can see the details below.
https://www.yealink.com/ydmp-freetrial-2020


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Blind transfer unsuccessful - W52P and Cisco Call Manager 9.1.2
Author Message
fidotas Offline
Junior Member
**

Posts: 2
Joined: Jan 2016
Reputation: 0
Post: #1
Blind transfer unsuccessful - W52P and Cisco Call Manager 9.1.2
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.


Attached File(s)
.zip  Yealink.zip (Size: 675.56 KB / Downloads: 10)
01-08-2016 12:26 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Post Reply 


Messages In This Thread
Blind transfer unsuccessful - W52P and Cisco Call Manager 9.1.2 - fidotas - 01-08-2016 12:26 PM

Possibly Related Threads...
Thread: Author Replies: Views: Last Post
Sad W52P not picking up IP Burkni 3 355 11-11-2022 06:01 PM
Last Post: complex1
  W56H with W52P Base dmvcomms 5 902 10-26-2022 03:04 PM
Last Post: poznaniak
  W52P Repeater RT10/rt20/RT30 schnell-yealink 3 5,322 04-20-2022 10:17 PM
Last Post: complex1
  W52P Firmware upgrade aunijaffer@gmail.com 5 7,565 09-07-2021 11:42 PM
Last Post: complex1
  W52P 2 handsets DAZZLING 1 4,620 06-01-2021 09:55 PM
Last Post: complex1
  W52P Openvpn with mikrotik info@quantiss.com 4 14,096 04-11-2021 06:25 AM
Last Post: Harms_Kubiak
  Slow to ring on incoming call rodcrux 1 5,249 01-25-2021 07:10 PM
Last Post: complex1
  internal call between two base stations fails janus 1 5,494 01-07-2021 07:20 PM
Last Post: complex1
  Is there no call history in web management panel in W52P? poznaniak 1 6,124 08-10-2020 12:49 PM
Last Post: complex1
  W52P factory reset without password ralph 1 7,476 04-02-2020 03:05 AM
Last Post: Yisroel_MongoTEL

Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us   Yealink   Return to Top   Return to Content   Lite (Archive) Mode   RSS Syndication