SBC restarting on inbound calls

[RossPCS]

We have a remote office with 17 phones all Yealink 12 - T27g and 5 - T21P_E2 phones. We started with a raspberry pi 3b+ as the controller and it seemed to work fine during testing. But when we set up the locations rules things have not worked as well. They want all 17 phones to ring when an inbound call comes in. I thought this is easy and added all the phones. Well, when we do this the SBC restarts and the BLFs on the phones start blinking and you can't answer the call. In the SIP Trunks window of the SBC will say Register Sent will be 0 and start again. We lowered the number of extensions in the list down to 6 extensions and that seems to help but still restarts. We also moved the SBC to an i5 windows box to see if that would help and it did not. We left if on the windows box to see if we could possibly troubleshoot it better. We also lowered all the BLFs to less than 10 on each phone included the park lines. Any help would be appreciated.

Netgear Firewall
The location has a Comcast cable modem with 95 Mbits down and 16 up.
Server version Windows 16.0.622

 

[leejor]

So are all 17 phones, in the same ring group? How many BLFs (originally) per set?

I have a feeling that you are asking too much of the SBC, there is obviously a limit of some sort that you are reaching.

 

[CentrexJ]

Are you using the Beta SBC software? if so downgrade to latest release version.

 

[AWS2P]

Hi, could you please answer this to help us knowing some infos about your install
https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[cobaltit]

So I don't think you are overloading the specs on the SBC. Pi 3B+ is good for up to 50 phones @ 10 BLFs each and you seem to be under that limit:

https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/

Even if you did exceed it I wouldn't expect it to crash, but rather just be sluggish.

Please confirm your 3CX version. You said 16.0.622 but there is no 16.0.622. There is a 16.0.5.622 which if that's the version you are on you would want to start by upgrading to 16.0.6.655 (Update 6a). Please also confirm the SBC version you are running

 

[SteveITS]

You said 16.0.622 but there is no 16.0.622. There is a 16.0.5.622

The version number changes format depending on where one looks...on the dashboard the x.x.x.x format is shown but on https://server:5001/#/app/settings/license the y.y.y format is shown, without the third number. Our dashboard shows 16.0.6.655 but click License on the dashboard and that page shows 16.0.655.

The SIP Trunk page Register Sent value I believe is the connection uptime not necessarily the restart of the device...you could ssh in to it (assuming ssh was enabled) and run uptime or top to see the device uptime.

 

[cobaltit]

So it does. I guess I don't click through to see a version that is already listed on the dashboard.

 

[JohnS_3CX]

We have a remote office with 17 phones all Yealink 12 - T27g and 5 - T21P_E2 phones. We started with a raspberry pi 3b+ as the controller and it seemed to work fine during testing. But when we set up the locations rules things have not worked as well. They want all 17 phones to ring when an inbound call comes in. I thought this is easy and added all the phones. Well, when we do this the SBC restarts and the BLFs on the phones start blinking and you can't answer the call. In the SIP Trunks window of the SBC will say Register Sent will be 0 and start again. We lowered the number of extensions in the list down to 6 extensions and that seems to help but still restarts. We also moved the SBC to an i5 windows box to see if that would help and it did not. We left if on the windows box to see if we could possibly troubleshoot it better. We also lowered all the BLFs to less than 10 on each phone included the park lines. Any help would be appreciated.

Netgear Firewall
The location has a Comcast cable modem with 95 Mbits down and 16 up.
Server version Windows 16.0.622

Hi Ross,

Please tell us the total number of BLFs served by that specific Pi SBC. It can handle quite a few, but if you have have any expansion modules, it could be the case that you may be reaching the limits (about 500 BLFs in total maximum allowed)

We would also like to learn the version of your SBC as seen on the SIP Trunks section of your management console.

 

[SteveITS]

I don't click through to see a version that is already listed on the dashboard

I know right? It threw me the first time I tried to check something about a license. Perhaps 3CX hasn't noticed either.

 

[RossPCS]

Some info requested,

• 3CX Version, Enterprise Perpetual 16.0.5.622 on License screen 16.0.622
• Server OS, Windows Server 2016
• Is the 3CX Server Hosted and where? On-Prem
• IP Phone Make/Model/Firmware: Yealink T27G T21P_E2
• Provisioning Method: SBC
• Trunk Provider : Telnyx
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: Yes but will remove it.

They want all 17 phones to ring
We are not running the BETA version of the SBC we were and it did the same thing.
SBC version 16.0.390
We now have less than 10 BLFs including the park lines
The number of BLS in total is less than 96 in total
Neither the Pi nor the Widows box restart but when this happens I get an email that the SBC is registered and the uptime is restarted under the Register Sent column.

I will remove the custom template and see if that does anything. UPDATE: Still reset.

 

[AWS2P]

Try to update PBx to latest 16.0.5.655
SBC is 16.1.152 everywhere on my pbxs without any problems

ISP spec you gave 95DL 16 UL are they on pbx location or where SBC is Used ?

 

[RossPCS]

Try to update PBx to latest 16.0.5.655
SBC is 16.1.152 everywhere on my pbxs without any problems

ISP spec you gave 95DL 16 UL are they on pbx location or where SBC is Used ?

16.1.152 is considered beta. Not sure about your second question. But we are on different ISPs. Main location is on 10Gb fiber and the location with the SBC is on a Comcast connection

 

[AWS2P]

Have that SBC release running everywhere on Pi's or windows PC since several months without a problem

 

[RossPCS]

Have that SBC release running everywhere on Pi's or windows PC since several months without a problem

Ya, I have 2 other locations with that version without this issue. We are wondering if it is a firewall issue at the remote location.

 

[AWS2P]

.655 could be updated on PBX side instead of.622

 

[RossPCS]

.655 could be updated on PBX side instead of.622

Ya we can do that but it will have to be after hours.

 

[JohnS_3CX]

Ok Ross,

Try switching your SBC to TCP mode, and then use the Push Config button.



Let us know if this improves the situation (prevents the issue from happening)

 

[RossPCS]

OK, we upgraded the server to the newest version of the server. We also upgraded all the phone Templates to the most recent version. We also set the SBC to TCP and we have been up for half the day so far so we will see. But I think it is working correctly now.

 

[AWS2P]

Good job , so now finger crossed , you probably got fixed

 

[JohnS_3CX]

Hi Ross,

Let us know how it goes after a day or so of usage