Not all extensions in Ring Group ring!

[leading1]

Hi
Basic issue - SOME extensions in SOME Ring groups do not ring.
Setup -
3XC Pro V16.0.676 Linux 16 license on an internal physical device with 5 branches connected - 1 head office and branches via VPN so all extensions are treated as "local".
ALL Ring Groups have the strategy "All Ring"
ALL Extensions are set to "Accept multiple calls", "Accept calls from Ring Groups" and "Accept Push Notifications"

Local Extensions are either Grandstream GXP2140, GXP2130 or Yealink W60B DECT base with SIP-W56H DECT handsets

GXP2140/2130 Firmware V1.0.9.135
DECT Base W60B Firmware V77.83.0.20
DECT Handsets W56H for V61.83.0.10

Example of the operational problem -
Branch 1 (Site where 3CX resides) - 1 x W60B base, 3 x W56H handsets, 10 x GXP2140, 1 x GXP2130
Ring Group "A" has ALL local extensions and when the RG is called from another extension outside of the group they all ring


No issues there

Branch 2 (Via VPN) - 1 x W60B base, 5 x W56H handsets, 4 x GXP2130
Ring Group "B" has ALL local extensions and when the RG is called from another extension outside of the group only 8 ring

Tests
Extensions 640 through 648 are in order in the Ring Group, although being "Ring All" it shouldn't matter

Extension 645 (DECT) fails to ring
Move 645 up one in the Ring Group order now 644 (DECT) fails to ring whilst 645 now works.

Move 640 (GXP2130) from top to bottom and leave rest in extension order and 645 again fails to ring.

Created a new Ring Group and try same setups - same issue

T:RingAll:830@[Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5483;rinstance=1909209066ef46b9,Dev:sip:[email protected]:5060]


Branch 3 (Via VPN) - 1 x W60B base, 8 x W56H handsets, 7 x GXP2130
Extensions 660 through 674

Tests
Extensions 660 through 674 are in order in the Ring Group, although being "Ring All" it shouldn't matter

3 extensions do not ring - similar issues to Branch 2


HOWEVER
Branches 4 & 5 & 6 (Each Via VPN) -
1 x W60B base, 3 x W56H handsets, 3 x GXP2130
&
1 x W60B base, 2 x W56H handsets, 5 x GXP2130
&
3 x GXP2130

ALL work as expected!


So what are we missing? (apart from a bit of sanity!)

 

[leejor]

And in the Activity Log, are all of the extensions being rung, shown, and are the IP's and ports correct?

 

[StefanW]

1 x W60B base, 8 x W56H handsets

in case you use G722 as codec, then only 4 handsets will ring as it 1/2 the amount of sip calls a base can do...

 

[leading1]

Ahhhhhh this makes sense as it relates to the quantities mentioned - ie: only 4 ring at each branch that has greater than 4 handsets! Will add an additional base and retest and report! Thank you for the heads-up Stefan ;-)

 

[StefanW]

welcome

 

[leading1]

Stefan you were SO RIGHT! Thank you, Added an extra base station to each site and moved handsets so that there’s only 4 on each and ALL NOW RING in the ring group! Another life’s lesson

 

[AWS2P]

Perhaps just more often the need to read products features in details to be sure they are really able to do what we expect

 

[leading1]

Agreed except that that specific part wasn’t obvious at the time. It indicated 8 simultaneous calls. Didn’t expect a 4 ring group limit! But thanks for your input anyway