Call Forwarding does not work for Provisioned Fanvil phones

Status
Not open for further replies.

Kwang Mien

Silver Partner
Advanced Certified
Joined
May 14, 2020
Messages
255
Reaction score
17
Hi,

My Fanvil X3 phones is provisioned to our 3CX V16 server.

I configured Call Forwarding on the phone to forward calls when no answer.
However, when there is an incoming call to the phone, the call is not forwarded.

Before provisioning the phone, the call can be forwarded.

Can anyone advise how to resolve this issue ?

Thanks.

Regards,
Kwang Mien
 
Just so that we better understand the situation, are you referring to configuring call forwarding on the device itself or have you configured call forwarding from within the Management Console for that Extension?

If you are talking about configuring this on the device itself, do note that manually configuring the device is not supported and all configuration must be done via 3CX. If this is in fact what you are doing, it would also explain the fact that it stops working after provisioning, as it is very likely that the configuration gets overwritten when the device gets re-provisioned.

If however you are configuring the call forwarding via the Management Console, then it should work. If this is the case, please provide the info mentioned here: https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/
 
i was referring to configuring call forwarding on the phone. Anyway to enable configuring call fwd on the phone ?
 
I'm afraid not, or at least not while keeping a 3CX Supported configuration. But why not use forwarding rules on the extension/PBX level?
 
The “fix” is in a 3 year old post , I remember due to writing it originally and having the same issue, trying to forward calls from the phone only using it’s built in forward option. It was for yealink but I’m almost positive it applies to Fanvil and other vendors phones. It’s disable feature sync. This can/probably does impact some other features so likely only want to do on a per phone basis.


There can sometimes be a situation its not ideal to use the 3cx application to have the pbx forward, instead this allows the phone alone to do it.

See this thread for full discussion.

Original post:
dan_tx said:
Did a wireshark on the 3cx server and testing this. The Yealink phone does not appear to be sending the 302 Moved Temporarily command back to the 3cx server. I don't know why. If I do a manual forward on an incoming call, it shows up in the wireshark and the forward works.

**Found Fix**

So did some googleing and found a yealink change log that mentioned not sending the 302 move when feature_key_sync was enabled. THey said the fix was to either disable that or add UseLocalFwd =1 to the config. Well adding to the config didnt work , probably because it is for a different model phone. However disable feature_key_sync fixed it, now the phone forwards as it should.

This was on a yealink t42g.

https://www.3cx.com/community/threads/dial-code-to-set-custom-forwarding-rule.47134/
 
i was referring to configuring call forwarding on the phone. Anyway to enable configuring call fwd on the phone ?
The supported way would be to use the forwarding rules and provision a status button on the phone. This works fine if the forward destination is always the same.
 
  • Like
Reactions: ChrisC_3CX
Status
Not open for further replies.

Members Online Now

Forum statistics

Threads
111,834
Messages
589,287
Members
164,663
Latest member
svdDGS