- Joined
- Jul 26, 2022
- Messages
- 23
- Reaction score
- 7
Hi Guys,
This might be an obvious one but I needed to clarify whats going on and if its 100% the Pi at fault here.
We have an Azure hosted PBX for a customer who's using V18 of 3CX, we recently moved their office to a new location and after setting up the equipment the existing SBC re-registered to the PBX and phones worked as expected. about a day later we had complaints that the desk phones were no longer working and could not make calls, checking the PBX its showing the SBC as being offline. softphones are working as you'd expect, the only issue is with getting the SBC to register.
There's no firewall rules getting involved here or anything that would stop the Pi from being able to connect to the PBX from within the office, we've simply done a basic lift and shift to a new site with a new internet connection we've kept their exiting infrastructure , firewall, switches etc
We've got the SBC on our testing bench at a different site using a different ISP it boots up as expected, however I'm a little green with Linux so getting to a login prompt maybe a far stretch away from fully working and I appreciate this, so I've got a couple questions I was hoping you could help me with.
This might be an obvious one but I needed to clarify whats going on and if its 100% the Pi at fault here.
We have an Azure hosted PBX for a customer who's using V18 of 3CX, we recently moved their office to a new location and after setting up the equipment the existing SBC re-registered to the PBX and phones worked as expected. about a day later we had complaints that the desk phones were no longer working and could not make calls, checking the PBX its showing the SBC as being offline. softphones are working as you'd expect, the only issue is with getting the SBC to register.
There's no firewall rules getting involved here or anything that would stop the Pi from being able to connect to the PBX from within the office, we've simply done a basic lift and shift to a new site with a new internet connection we've kept their exiting infrastructure , firewall, switches etc
We've got the SBC on our testing bench at a different site using a different ISP it boots up as expected, however I'm a little green with Linux so getting to a login prompt maybe a far stretch away from fully working and I appreciate this, so I've got a couple questions I was hoping you could help me with.
- Are there any log files on the SBC I can look at that might give me an idea to what is going on and why it won't register ?
- Is there a command i can run or file i can check to see the version of the SBC software to gauge if its so far out of date it won't work with the version 18 PBX anymore ?
- Any other ideas on why it won't connect would be appreciated.
I'm hoping this issue is limited to this SBC and not a compatibility issue from a recent update, since we have another 4 Pi 3B+'s at other remote offices for this customer that all appear to be working fine with no connectivity issues so far
.