Hi all,
We have the following setup with a customer:
18 Snom M70 handsets - 6 Snom M900 antennas.
The antennas are configured in one Multicell chain.
3CX pbx is hosted off site, V20.0.7.1080. Connection to the pbx is via IPSEC.
At installation a few weeks ago, all handsets were registered through the different antennas in the pbx.
Then, at random, handsets lost registration ("no sip reg" on the handsets screen, "sip error" for the extension in the antenna).
We moved the antennas to fixed free IP's out of DHCP scope, all handsets were registered again.
Yesterday, the customer stated there were again handsets with "no sip reg".
In the evening (when the company was closed), I checked the antennas.
All handsets were linked to one antenna, IP ending on .21, being the one closest to the charging stations location, all handsets showed a sip reg error.
I updated M900 antenna firmware to 740 B103, M70 handsets tot 760 B400.
After update, all handsets were registered through the same .21 antenna.
This morning, the customer informed us all handsets were again showing "no sip reg", in the antenna I saw sip reg error for each extension.
I rebooted the antenna, I factory resetted the antenna, this did not work.
I asked the network partner to shut the .21 antenna down so the handsets would link on other antennas.
The handsets linked to the other antennas.
The handsets that linked to the .20 antenna also showed sip reg error. Handsets that linked to one of the other 4 antennas did register in the pbx, which leads me to believe there is no network issue.
I changed the fixed IP of the .20 antenna to .26, then all handsets that are linked to this antenna did register in the pbx.
I changed the IP of .26 back to .20, all handsets remained registered.
This leaves me at a loss: I don't think there is a network issue as registration does work, I also don't think it's an issue with the IP address since when the antenna is put back on it's original IP the handsets remain registered.
The issue is for now resolved, but I fear that it will return.
Anyone has a suggestion as to what could be going on?
We have the following setup with a customer:
18 Snom M70 handsets - 6 Snom M900 antennas.
The antennas are configured in one Multicell chain.
3CX pbx is hosted off site, V20.0.7.1080. Connection to the pbx is via IPSEC.
At installation a few weeks ago, all handsets were registered through the different antennas in the pbx.
Then, at random, handsets lost registration ("no sip reg" on the handsets screen, "sip error" for the extension in the antenna).
We moved the antennas to fixed free IP's out of DHCP scope, all handsets were registered again.
Yesterday, the customer stated there were again handsets with "no sip reg".
In the evening (when the company was closed), I checked the antennas.
All handsets were linked to one antenna, IP ending on .21, being the one closest to the charging stations location, all handsets showed a sip reg error.
I updated M900 antenna firmware to 740 B103, M70 handsets tot 760 B400.
After update, all handsets were registered through the same .21 antenna.
This morning, the customer informed us all handsets were again showing "no sip reg", in the antenna I saw sip reg error for each extension.
I rebooted the antenna, I factory resetted the antenna, this did not work.
I asked the network partner to shut the .21 antenna down so the handsets would link on other antennas.
The handsets linked to the other antennas.
The handsets that linked to the .20 antenna also showed sip reg error. Handsets that linked to one of the other 4 antennas did register in the pbx, which leads me to believe there is no network issue.
I changed the fixed IP of the .20 antenna to .26, then all handsets that are linked to this antenna did register in the pbx.
I changed the IP of .26 back to .20, all handsets remained registered.
This leaves me at a loss: I don't think there is a network issue as registration does work, I also don't think it's an issue with the IP address since when the antenna is put back on it's original IP the handsets remain registered.
The issue is for now resolved, but I fear that it will return.
Anyone has a suggestion as to what could be going on?
