Solved Phones not ringing simultaneously anymore

[[email protected]]

I host 8 phone systems on AWS. For all my 3CX systems, inbound calls go into call queue using "ring all" strategy and it rings all the phones at the same time. About a month ago, the phones began ringing oddly. The first ring would ring one phone, the second ring would hit a few more phones then by the third or fourth ring, they would all ring. I've noticed it with my system and my customers are not happy with this arrangement. Below are the particulars:

1) Self hosted on AWS using 3CX image - By 3CX | Ver 3CX Phone System 18.0.5.418
2) Carrier is CallCentric and BCM One (formerly nexVortex)
3) Phones are Yealink T46S or U
4) Nothing has changed except the phones don't ring at the same time anymore.
5) Phones set to Direct SIP - (STUN - remote)
6) Carrier SIP trunk use registration: username and password

Thanks for any advice in this very frustrating situation.

 

[ebrowne_sts]

Depending on the number of phones at each location, you may want to use an SBC instead of stun. Also check you firewall and switches. I recently had this issue onsite at one of our locations and it turned out the switch had latency of 150ms pinging internally to the firewall. Ended up rebooting the switch to resolve.

 

[cobaltit]

SBC is definitely recommended. The other thing to check is if they are STUN, are they setup properly? STUN phones should have unique SIP and RTP ports configured and those should be forwarded in the firewall

 

[[email protected]]

Thanks everyone for their timely reply.
1) I implemented the SBC and that fixed the issue at one customer site.
2) I implemented new phone sets and I don't think I did a good job with STUN on separate ports and that possibly is causing the issue as well. I will implement that at another site and see if I get good results on that. I'll reply to let you know how fixing the STUN ports goes. I'm really curious.
3) Stay tuned...

-Ken

 

[JohnS_3CX]

Hi Ken,

Just like your original case where things worked, and then suddenly they didn't, so will your 2nd site sooner or later if you choose to stay on STUN. Your ISP might change something, or the firewall may do something unexpected and you are back in square one.
You will diligently reboot your hardware and check your ports and the issue will give the impression that it went away, only to return at later stage, and usually at the worst possible time.

Install SBC on that site too, it's the most reliable and recommended way of doing it.

 

[[email protected]]

Hi Ken,

Just like your original case where things worked, and then suddenly they didn't, so will your 2nd site sooner or later if you choose to stay on STUN. Your ISP might change something, or the firewall may do something unexpected and you are back in square one.
You will diligently reboot your hardware and check your ports and the issue will give the impression that it went away, only to return at later stage, and usually at the worst possible time.

Install SBC on that site too, it's the most reliable and recommended way of doing it.

I've already changed three sites to SBC. That has definitely fixed my issue! Thank you all!

 

[[email protected]]

I'm going to consider this case closed. How do I do that?

 

[JohnS_3CX]

Thanks Ken, happy to hear all is well now. We can mark it as solved