Fallback to mobile (not app) when handsets not registered

Status
Not open for further replies.

RossAtCC

Bronze Partner
Joined
Dec 28, 2023
Messages
7
Reaction score
0
Hi folks

New partner here, can anyone let me know what the proper way of handling failover to an external number in the event that all handsets on site are not registered?

This is just a single CLI pointed to a group with a bunch of handsets set to ring all. In the event that there is a broadband failure, no handsets will be registered, and we need the system to send calls immediately to a fallback mobile number (not the app).

On our previous platform there was a routing option for when handsets are not registered, if an unregistered handset in a group had a call, the call would immediately go their mobile.

On 3CX there is an option on the user for "Busy or Not Registered", however these are two very different situations. If they are busy, them other handsets in the group should ring, if they are not registered, we need to send to mobile.

There is also an option on the group "Destination if no answer". However customer doesn't want calls landing on him mobile unless the broadband is down, under normal circumstance he just wants the group to ring, so I don't think we can use that option.

What's the proper way to do this? Am I missing something obvious?

Many thanks.
 
In your Ring Group, you can forward the calls via the Destination if no answer to be the mobile phone number you want.

1709206621858.png

The forwarding rules of an extension are ignored when processing calls in a ring group.
 
I see that - but it's not a no answer situation, if you know what I mean.

If we do this, his mobile will ring under "normal" operation when calls are not answered. He doesn't want that, he wants the VOIP handsets to ring indefinitely.

Mobile only to ring if handsets are not registered.

Edge case I know...
 
Just tested this - it' doesn't work though. See configuration below.

Two extensions in the ring group, if I unplug them both, the caller hears ringing for 20 seconds, then it rings the external number.

How do I make it fail over if there's not handsets registered in the group?

1709207400406.png
 

Attachments

  • 1709207368929.png
    1709207368929.png
    37.2 KB · Views: 3
OK - so it looks like it takes about 60 seconds for 3CX to realise the extensions are not registered. Then it does fall back to the external number.

So our fix will be a silly high timeout, and divert to external number.

Thankyou for your help on this Nicholas.
 
The 60 seconds is defined by the devices' REGISTER timeout. When the time comes for the devices to reREGISTER the PBX will not receive a registration from these devices and put them offline.
 
OK that makes sense - thankyou.
 
Status
Not open for further replies.

Forum statistics

Threads
111,973
Messages
590,079
Members
164,899
Latest member
mazet