Not all extensions ring in ring all group

[jofer]

Hi
I have a 3cx host on Debian, all the newest updates.
I have 1 yealink T42G, 1 yealink T23G and 1 yealink dect W52P, all provisioned and firmware up to date.
They are all in a ring group (Ring ALL)
my SIP trunk inbound is pointed to the ring group.
First incoming call rings all of them.
If the call answered on the t42g then the next calls coming in will only ring at that t42g, the other 2 phones will not ring.
only when i use the t23g again for outbound call or i look at the call log on the phone, the next call will be presented to the phone again, and strange enough the next call will also ring at the w52p
This does not happen to the t42g at all, if i do not answer a call on the t42g it does not make a difference. that phone always just keep ringing on every call

Any ideas will be appreciated.

 

[JohnS_3CX]

Hi Johan,

you did not mention the important parts, like how are the phones provisioned. Are these local to the PBX, STUN, SBC, VPN?

 

[Rich.Hopkins]

What is your ring group strategy set to?

 

[jofer]

The 3cx is hosted in the cloud in a data centre. The extensions all in the same location, provisioned Direct SIP (STUN-Remote)
Ring strategy (Ring ALL)

 

[JohnS_3CX]

Ok I had a feeling this was a STUN installation from the description that the phone started receiving calls again after IT FIRST made an outgoing call.

Suggestions:

Check all 3 extensions, under provisioning of their phones.
- Ensure they each have a unique SIP port
- Ensure that they each have a unique range of RTP ports, with no overlap with other extensions
- Ensure you allow at least as many RTP ports needed per model (20 ports should be ok)
- Reprovision the phones so they can receive their new ports. You should see them registering on their specific port from the logs
- At the phones site, open those ports to each device on the router/firewall/modem they use

It is very important those ports are forwarded correctly for each and every device unuquely otherwise you will continue to face those issues.

Alternative suggestion:
- If all the phones are at the same site, then ignore all the above I said, and install an SBC. This means no ports to worry about, no provisioning issues, and best of all you get full encryption and any calls between those extensions stay as local traffic.

 

[Saqqara]

As the phones are configured by stun, have you configured them the 3CX supported way.

Each phone needs a fixed IP address (can be done via dhcp)

Each phone, different SIP / RTP ports (rtp ports - normally block of 12).

For example - phone 1 - sip 5065 rtp 14000 to 14012
phone 2 - sip 5065 , rtp ports 14013 to 14025

Firewall protecting the phone, setup portforwarding to the phone IP address with the correct sip and rtp ports.

 

[jofer]

Thanks for the detailed answers, i will look at all of this. I have not set it like this.