- Joined
- Aug 10, 2018
- Messages
- 28
- Reaction score
- 6
Client has many small remote deployments with just a Raspberry Pi SBC and a snom M300 with 2 handsets. Each pair of handsets is registered to an extension unique to the location. Randomly one of these extensions will not be reachable.
Today we finally caught it, i was able to log into the gui for the snom and it said the status was "In Use" even though no call was live in the PBX. I tried turning on "accept multiple calls" for the relevant extension, but that I was still not able to ring this location.
After a forced reboot of the snom everything worked again. I am trying to figure out if there is a way to increase reliability at these locations. It happens very infrequently, but we have enough of these deployments that it is a noticeable issue.
Since i wasn't at the site, i didn't get a look at the handset, so i dont know if it looks like it it in a call or if just the base antenna is confused. I was wondering if anyone else has had any similar issues, as I have seen a drop in internet at a remote site cause a call in the PBX to get stuck, but never in the end sip device.
Today we finally caught it, i was able to log into the gui for the snom and it said the status was "In Use" even though no call was live in the PBX. I tried turning on "accept multiple calls" for the relevant extension, but that I was still not able to ring this location.
After a forced reboot of the snom everything worked again. I am trying to figure out if there is a way to increase reliability at these locations. It happens very infrequently, but we have enough of these deployments that it is a noticeable issue.
Since i wasn't at the site, i didn't get a look at the handset, so i dont know if it looks like it it in a call or if just the base antenna is confused. I was wondering if anyone else has had any similar issues, as I have seen a drop in internet at a remote site cause a call in the PBX to get stuck, but never in the end sip device.