SBC reboot issue

[Chris Harrison-Burgess]

Hi all
We have an issue at a new site where the SBC reboots randomly (probably once a week, mainly due to power issues in the area).
After the SBC reboots, all phones have to be factory rest and then reassigned to the correct extension again even though the SBC IP address has not changed.
3CX is on AWS lightsail
SBC is on Windows 10 pro
Phones are Yealink T41s
Everything has the latest updates and firmware.
Is there any way that the phones should come back online as soon as the SBC comes back online, as having to reassign them each time is becoming a pain in the bum!

 

[Alphabetic]

You may want to consider a USB power bank to act as a UPS for your SBC if this is an inevitable issue.

 

[Saqqara]

As above, add a ups to the sbc

What happens, if you just restart the phones.

 

[JohnS_3CX]

Hi Chris,

Two things

1. Next time this happens, check once that the IP has indeed not changed and that no other device has taken it (IP conflict)
2. Check in the management console to ensure the SBC has re-registered, and then reboot all the phones. If they don't come up after a simple reboot you may have to capture some traffic to see what a phone does during that time

Normally a reprovisioning should not be required in the case you described.

 

[Chris Harrison-Burgess]

Hi all
Thanks for the responses.
A UPS would be a good idea and we will be making this recommendation to the customer (Its not just our kit that goes down, its everything)
@JohnS_3CX The IP address of the SBC had been bound by mac address on the DHCP server. We first tried by rebooting the phones after the SBC re-registered but unfortunately this didn't work, hence the factory reset (Our normal process for issues is reprovision, then reboot, then reset)
" Normally a reprovisioning should not be required in the case you described."
This is what i thought but wanted to make sure.
What would i be looking for in the traffic capture? I'm not at all 100% with wireshark captures.

Thanks

 

[cobaltit]

So I didn't see it posted... but what is the SBC version and the Raspbian/Raspberry Pi OS version? This is definitely wonky as I mess with our SBCs all the time here (Pi 4 and Debian VM) and the phones register within a minute of me booting either one of them, or after we do our patch reboots weekly.

 

[Chris Harrison-Burgess]

@cobaltit the SBC is on a Windows 10 pro machine

 

[cobaltit]

Doh... yeah I see you put that in your original post. Don't see the SBC version listed though.

Also is that machine domain joined? Anything else on that machine?

 

[JohnS_3CX]

Please check your SIP trunks section, and tell us the version of your SBC

You can also try to update your SBC to 16.2.24 which is our latest beta and a close release candidate.