Snom 360 looses registration

[ywavel]

There is an issue with one of our Snom 360 phones, among the 320s and 190s we have in the office. This particular 360 looses its' registration once every 2 weeks with the PBXnSIP we have in the same subnet. Curiously, it retains its' registrations with two Asterisk PBX in different locations.

 

When that happens, the Snom's log claims "[2]7/3/2008 08:30:05: Registrar 362@localhost refused with code 500" but after a while it registers since it claims "[2]7/3/2008 10:56:51: Registered at registrar as 362@localhost (Expires: 180 secs)".

 

The particular phone, as well as the other 360 in the office run the following firmware, since running the latest 6.5.17 or 7.1.30 render both phones incapable of connecting with PBXnSIP.

 

Kernel Version: snom360 linux 3.20

Application-Version: snom360-SIP 6.5.15

Rootfs-Version: snom360 ramdisk v3.31

 

Any ideas?

[Vodia PBX]

The particular phone, as well as the other 360 in the office run the following firmware, since running the latest 6.5.17 or 7.1.30 render both phones incapable of connecting with PBXnSIP.

 

Well, at least the 7.1.30 should work find with the PBX.

 

Maybe you should also use the registration tracking emails to see when exactly the phone goes offline.

 

And also keep in mind that sometimes the network also has active components that go offline for some time. We have had switches that needed to be rebootet from time to time. Then if you see that the registration problem occurs on specific parts of the network that might be a useful hint.