Solved Yealink Always Forward occasionally self setting

[3CXNewbie]

Hi there.

In the past year we have had this happen about 4 times.

It appears that a number of phone handsets are self setting the Always Forward code.

You look in 3CX Call Log, you see the dial code from the extension turning the always forward on but the number has not been dialled directly.

Tried to set the forward number to a not allow in 3CX but can't find it.

Anyone else got this issue or is there a way in 3CX to disallow always forward?

Thanks.

 

[Saqqara]

Need more info on your setup

What version of 3CX are you running i.e. 15.5.15502.6

Is the 3CX server local or hosted in the cloud

How are the phones provisioned - local lan, stun or SBC

Are you using 3CX standard templates or custom one.

What phones are you using, have you check they are running the latest firmware

 

[YiannisH_3CX]

Hello @3CXNewbie

That is strange as this function of the phones is not supported by the PBX and is ignored when set. So you are either using a custom template or a very old PBX version.

 

[3CXNewbie]

FOUND IT.

By accident, I pressed the TRAN button on a Yealink T21. Went straight to Forward.

Just need to find in the template the line to disable it..

 

[YiannisH_3CX]

On Yealink phones the Trans button appears only when the phone is on call. You need the button to be able to transfer calls to other extensions so i would not recommend disabling it

 

[3CXNewbie]

Thank you YiannisH_3CX

With the Yealink handsets we are using, we use the Softkey as a transfer button so happy to change the programing of this key.

 

[3CXNewbie]

It appears that with the Yealink (T21 and T23) when not on a call, the button sets always forward.

Have added this to provisioning template:

programablekey.14.type = 47
programablekey.14.line = 1
programablekey.14.value =
programablekey.14.history_type =
programablekey.14.label =
programablekey.14.xml_phonebook =

When you are on a call, the Tran button still works.

I am happy with that resolution.

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread with your solution.