[BUG?]Inconsistent "Also ring my mobile" behaviour when logged into queue without internet

[ITSmartwork]

Hi everyone,



I’m experiencing an issue with the "Also ring my mobile" feature in 3CX, and I’m hoping someone can help clarify what might be going wrong.

Here's the situation:

I have the "Also ring my mobile" option enabled in my call forwarding settings.

I’m part of a call queue, and my extension is actively logged into the queue.

When I lose internet connection on my mobile device, I expect that incoming queue calls should automatically forward to my mobile number.

The problem is that this doesn’t always happen consistently. Sometimes the calls are correctly forwarded to my mobile number, but other times they are not — the call simply doesn’t reach me at all.

To clarify:

Push notifications are enabled.

The mobile number is set correctly in international format.

I’ve tested while the 3CX mobile app is fully closed and the device is without internet.

I remain logged into the queue the whole time.

Has anyone else experienced this issue, or is there something specific in the queue or extension configuration that might be causing this inconsistent behaviour?

Any help or suggestions would be greatly appreciated!

Thanks!

 

[JoshWS]

Have you experienced this at all when a call is put through to your specific extension? Not the call queue?

Can you also confirm you have mobile service in the places where this does not reach the device

We have lots of customers who use this feature and have never experienced any issues

 

[ITSmartwork]

When calls are routed directly to my extension (not via the queue), the "Also ring my mobile" feature works instantly and consistently. No delays or missed attempts.

After a lot of testing, the inconsistency only occurs in the call queue. When the queue triggers a call:

• Sometimes: The GSM is runs immediately
• Other times: There’s a 7–8 second delay before the mobile is dialed.

.

 

[NicholasP_3CX]

Check that it is actually the queue that delays the outgoing calls. It might be the provider delays in responding.

Check your logs and a capture to see when you have the INVITE go out from the queue, and when the response comes from the provider.