Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Yealink BLF and Blind transfer

Discussion in '3CX Phone System - General' started by mirjam.nz, Aug 5, 2011.

Thread Status:
Not open for further replies.
  1. mirjam.nz

    Joined:
    Dec 6, 2010
    Messages:
    28
    Likes Received:
    0
    Hi,

    Blind transfers with Yealink T26p phones is only possible if one enteres the extension manually.
    If a blind transfer is made via a BLF key, the original call disconnects instead of being transferred through to its destination.

    The same Blind transfer works just fine with Cisco or Snom phones.

    Does anybody have a resolution for this Blind Transfer Problem with Yealink BLF?

    FYI, an announced transfer works just phone using the BLF keys.

    Firmware on Yealink T26p: 6.60.0.120
    3CX version: V10 SP2

    Cheers
    Mirjam
     
  2. willow

    willow Member

    Joined:
    Mar 1, 2011
    Messages:
    471
    Likes Received:
    0
    Re: Yealink T26p and BLF Blind transfer

    have you tried it with the 60.110 firmware. the .120 is a little buggy.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. mirjam.nz

    Joined:
    Dec 6, 2010
    Messages:
    28
    Likes Received:
    0
    Re: Yealink T26p and BLF Blind transfer

    Hi Jeremy

    Yes, we did, the same behavior. I can reproduce this fault on different 3CX servers.

    I really hope there is a solution for this.

    Can you perform a Blind Transfer with the BLF button ?

    Cheers
    Mirjam
     
  4. mirjam.nz

    Joined:
    Dec 6, 2010
    Messages:
    28
    Likes Received:
    0
    Hi,

    Found a solution to our problem, change the setting on the Yealink phone to:

    Disable the option Semi-Attend Transfer in the menu Phone/Features/Enable Semi-Attend Transfer

    Cheers
    Mirjam
     
Thread Status:
Not open for further replies.