I’ve got a device that seems to become unreachable for about 2 minutes, every hour. From what I can tell, it isn’t due to network or server issues. Any ideas?
I would guess conflicting IP addresses. It comes back up at regular intervals, detects the conflict, and shuts down..
I gave up on a couple devices here in my home network (an old SPA2000 and a cheap DP715 grandstream) and plugged their IP addreses into Asterisk and turned off registration. No more annoying messages.
Friday, June 17, 2016, 11:56:34 PM, Mike wrote:
The default registration time in spa112 is 1 hour. If registering is slow in your infrastructure, this can be the reason.
It sounds like a keep alive issue
I would try the following:
* If you can login through HTTP, check the uptime of the Cisco device. Make sure the device is not rebooting.
* If you can, make a ‘ping’ from the PBX to the device and annotate milli-seconds of response. Then compare then to the default ‘qualify’ sip setting for the Cisco peer (width sip show peer _SPA112_PEER_NAME_). Maybe you can set ‘qualify=X’ where ‘X’ is the measured round-trip time to a peer.
* If the Cisco is behind a NAT device/router, maybe the default 60 seconds for the ‘qualifyfreq`’ sip setting is not enough to keep active the session. Try changing this value to something lower like 15 or 30 seconds.