Forwarding form a desk set drops call on 3CX app

madSeal

Free User
Joined
Aug 22, 2024
Messages
5
Reaction score
1
Note - I am not a 3CX expert by any stretch, but I have been tasked with helping to resolve this issue remotely. I am not on site with the customer, so please let me know what questions to send them if more information is needed.

An employee at an organization I am working with is having trouble receiving forwarded calls from a desk set to the mobile app.

The employee has their own extension, but they are also responsible for answering the organization's main extension when the main line desk set is not staffed. They used to simply activate call forwarding from the desk set (not in 3CX) to their own extension which they would answer on their 3CX mobile app. This worked until the V20 upgrade. Since then, calls to the main line will ring on their mobile app, but will drop immediately on answering. It does work when answering forwarded calls on their own desk set, however.

The temporary solution was to put them in the ring group for the main line. This works, but the problem is that they cannot easily turn off calls from the main line when they don't need to be answering it. They can put themselves on a "do not disturb status," but then they get no calls, which is also not what they want. We could try to use 3CX call forwarding, but that is not what is being asked for (Needs to ring immediately when needed, and they want to be able to quickly turn it on/off without logging in to 3CX)

I haven't confirmed the desk set model number, but I'm pretty sure it's a Snom D785. We were unable to replicate with our own D785s in out office.

Like I said, I'm a 3CX newb. Open to ideas, suggestions, and questions to ask for additional info.
 
Forwarding from deskphones is NOT supported in 3CX. You should use the status forwarding rules. Not sure how it ever worked as it was never supported, like not even in the code.
 
You could define the forwarding to be the extension with the mobile app and just use the DND button on the phone to toggle back and forth.
 
  • Like
Reactions: Evolute IT
You could define the forwarding to be the extension with the mobile app and just use the DND button on the phone to toggle back and forth.
Thanks - I've configured this and asked the customer to test when able. It tested successfully here in our office.
 
  • Like
Reactions: NicholasP_3CX
UPDATE (same issue, some more detail): We are still having trouble with phone forwarding since the v20 upgrade.

Situation and Use Case:
The receptionist front desk for the organization has two seats/phones. Both phones are SnomD785-SIP running firmware version 10.1.175.16 as of this morning. They are both configured to ring on calls from either of two "main" extensions (100, 101). I believe this is done via a ring group containing 100 & 101, but I'm not entirely sure about that. These are the outward facing lines for accepting external calls.
Before the upgrade, the receptionist would simply put the Snom on call forwarding to another extension (113) while away from their desk.

Problems:
-Since the V20 upgrade, when forwarding from the Snom, the calls will forward to 113 but drop immediately when answered.
-A second issue is that the person answering 113 needs to know that the call is coming form the main lines. So the inbound caller id should be 100, 101 instead of the inbound caller's actual number. This apparently was the case before (not sure, I suspect maybe not). At any rate, that's what they want now.

Desired end-state:
-The receptionist should be able to quickly put the main lines (100, 101) into a forwarding mode that will ring to 113.
-This is preferably done by pressing a button on the Snom phone (e.g. Call Forward, or DnD), but the receptionist can also change status of the extensions from their mobile app.
-They should not have to log into the web console (e.g. to change ring group members).
-When a forwarded call rings to 113, it should display the 100/101 as the inbound caller ID (I'll be happy to just get forwarding working for a start).

Solutions attempted:
-We monitor this account remotely. Snom phone forwarding works in our office (same Snom model running v10.1.84.14), but without changing inbound caller ID to the extension being forwarded.
-As suggested above, we have tried several iterations of configurations involving DnD status on the phone and/or in 3CX, and/or ring groups.
-e.g. DnD status set to forward to 113; DnD status set to call a ring group including 113; and several other combinations.
-The closest we got was getting internal calls to forward (without changing caller ID), but inbound external calls still did not forward.
-Upgraded to latest firmware - no change.
-I may start experimenting with call queues next.

We'd prefer to get the old Snom forwarding method to work again, but anything that works is fine as long as it's simple to turn on and off.
 
Is it always 113?

If the receptionist sets up a status that forwards to 113, he/she just needs to change status to forward the call. Sounds like you were experimenting with that.

What if the destination no answer of the ring group is x113? Or even x100 which is set to forward via status.

x113 can sign into and out of a "Main Inbound Calls" queue via BLF...
 

Members Online Now

Forum statistics

Threads
111,832
Messages
589,286
Members
164,662
Latest member
DejanMDS