SBC restarting

[Michael Wllie]

I have several vps hosted v16 sp6 pi based sbc's . seeing a bunch the sbc's re-register indiscriminately, some as much as every 30 minutes.
I am wondering if anyone else is seeing this.
I have received a few complaints of dropped calls.
But of course, when I am doing captures no calls drop.
1st time posting.
Thanks
Mike

 

[cobaltit]

So is the SBC restarting, or is it re-registering? The uptime is listed on the trunk page. What version of the SBC software? And are you saying that it's happening as often as every 30 minutes but you haven't been able to get a capture of it?

 

[Michael Wllie]

re-register in the sip trunk tab, shows the last failed register and register ok.
Have delved into pi logs for os and sbc, did not see anything.
Worked on one sbc intently, added (sudo apt-get install mtr) for trouble shooting and this sbc has been up for 2 days 17 hrs.
Whilst most of all the other sbc's have, at best, an 3 hour register.
Side not, one of these installs just had the sip trunk uncheck its option for allow inbound and outbound uncheck its self. Another hot text. This install also has a re-registering sbc.
I am unclear on what causes the sbc to re-register. I am also assuming that this re-register will cause a call to drop.
Have done pcaps, but of course it did not reset during the 4 plus hour test call.

 

[SteveITS]

I've found the SBC "up" notification is sent on every "up" while the "down" notification email is only sent after some time period, like a few minutes. So an "up" by itself generally means there was a short connection drop.

 

[JohnS_3CX]

Hi Michael,

It would be good to also mention the SBC version (as it appears in your trunks section).

If all of them are coming/going often then it may be a good idea to add the PBX machine in the list of suspects (or it's connection)

 

[SteveITS]

In situations like this with suspect connections we often just run "ping -n 10000 servername" to ping it for a few hours and see how much packet loss there is. Tip: CTRL+Break will give you a summary but keep pinging.

 

[Michael Wllie]

The sbc's are running 16.1.152 and 16.3.390
The one sbc 16.1.152 has been running the mtr constantly and has not restarted. I think, that means that the constant connection to the phone server has seemed to keep it from restarting.
Is there a keep alive that can be run to keep the others from restarting?

 

[Michael Wllie]

There has been no packet loss on the sbc running the mtr for 3 days 17hrs.

 

[SteveITS]

You keep saying "restarting"...running "top" on the SBC shows a short uptime?

 

[Michael Wllie]

So the following is from 2 different sbc's statistics tab .

Uptime

8h 34 m

Uptime

3 Days 17 h

When looking at the sbc under sip trunks double clicking on sbc.

 

[SteveITS]

I think you're looking at the connection uptime (since last registration/connection) and not the time-since-boot of the SBC. On the one in our office the two pages both show "3 days 7 hours" but the SBC hasn't restarted for several hundred days.

16.1.152 is the latest public beta version...

 

[Michael Wllie]

Correct, the raspberry PI is not rebooting. The software SBC stays running. The registration time of the sbc to the 3cx server is re-starting.