Yealink added recording BLF, lost others

[Mike Hammett]

I have a deployment of Yealink T41 handsets. IIRC, we set up the BLFs to be one-button call forwarding. Last week I set their first button to be a record button by copying the Yealink T4x template and changing "linekey.1.type = 0" to be "linekey.1.type = 25".

The recording works great, but they've lost their ability to transfer.

I have verified the extensions still have their BLFs set in the 3CX management console.

Before I go on-site to see what they're talking about, what should I be looking for? Obviously, I'll roll one of the extensions back to the stock template to verify functionality.

 

[Mike Hammett]

I went looking into this again and came back across my own, unanswered thread. sigh

 

[JohnS_3CX]

Hi Mike,

Sorry you faced issues with this, we usually recommend that you keep the default 3CX templates as these have been tested by us to support the phone features in conjunction with the PBX functionality.

Generally speaking, many models may rely on the first and second line keys in order to function properly and if you modify them you may get unexpected results (especially as new firmware and templates get released and things may change in the implementation). That being said, the manufacturer's forum/resources may be able to give you more information as to how the templates work but you will have to do your own proof-testing to ensure things still work. We would recommend to keep using the 3CX template for maximum compatibility.

 

[Mike Hammett]

That would be easier if the default template included the desired functionality. ;-)

 

[Mike Hammett]

The user didn't accurately explain the problem. Transfers were working, just some of them blindly instead of attended.

sigh

 

[JohnS_3CX]

No worries

That happens more often than you think, the users usually don't see or interpret things the way a system admin does