Weird ringing/not ringing issue with ring group

Status
Not open for further replies.

ElementalWindX

Bronze Partner
Advanced Certified
Joined
Oct 24, 2018
Messages
367
Reaction score
40
Has anyone seen the problem where a ring all ring group doesn't ring all the phones assigned to it? I've got a client that was on one of the beta v18 (until today) who said once or twice a day when a caller called in, they would see only one phone ring. There is no DID going directly to a phone. The call path sends initial callers to a ring group that rings all the phones.

So not sure how to explain why a caller would be experiencing that?

Currently they're on newest RC v18. Cloud hosted debian in a data center. As mentioned before up until today they were on v18 betas.

Fanvil x6u phones.
STUN
SIPTrunk provider
Firewall checker passed
No custom templates.
 
Last edited:
Are all affected IP Phones on the same remote site? If yes, can you confirm if the necessary configuration for deploying IP Phones via STUN has been implemented?

If you have more than one IP Phone on a remote site and it is on those sites that you are facing the issue, I would highly recommend installing a 3CX SBC on those sites instead. This will get rid of any firewall configuration requirements, make provisioning a breeze by enabling the use of PnP, and also provide an extra layer of security due to the use of the 3CX Tunnel service. The only drawback is that you have to use a dedicated device, but a small number of IP Phones should be just fine with just a Raspberry Pi hosting the 3CX SBC.
 
Last edited by a moderator:
As above installed an SBC server, and this will make your life so much easier.
 
  • Like
Reactions: ChrisC_3CX
Is the lone extension that gets polled when the others have not been the operator extension?
 
Operator extension isn't attached to any physical phones. They are all on different ports of all types. All on the same physical location. No SBC installed on any site we manage for any client we have. We haven't seen the value/reason to use a SBC yet. We stay away from them due to the reliability/single point of failure.
 
To check whether this issue is related to IP Phone configuration, you could maybe temporarily have users all launch the 3CX Webclient and login to their extension. If the issue persists with the 3CX Webclient as well, it may mean that something else is happening that is most probably related to 3CX's configuration instead.

If all works fine, it may be worth considering the 3CX SBC for this site, or at least give it a shot to see if it does resolve the problem.

Note: Do bear in mind that you will need to factory reset the devices and reprovision if you do decide to switch to the 3CX SBC. As mentioned above though, due to PnP provisioning, this should a fairly easy and swift process.
 
On an incoming call, that fails, have you checked the 3CX Activity Log, to see if an attempt was made to send an INVITE to all phones in the ring group?
 
On an incoming call, that fails, have you checked the 3CX Activity Log, to see if an attempt was made to send an INVITE to all phones in the ring group?
I'm seeing this in the activity quite a lot

08/05/2021 11:49:35 AM - [CM503003]: Call(C:22): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from x.x.x.x:5069
 
@ElementalWindX

Have you happened to give the 3CX Webclients a test too?
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,982
Messages
590,116
Members
164,908
Latest member
FarizQasimov