WIP 310 and Asterisk Qualify Times

Unanswered Question
Nov 20th, 2009
User Badges:

I've tried both the 5.0.11 and 5.0.12 firmware and I get the same symptoms with both.


The WIP 310 seems to take a long time to respond to the sip qualify message that Asterisk uses to determine whether a peer is reachable or not. I set Asterisk to use a 5 second timeout, and the WIP310 still goes unreachable or lagged frequently:


[2009-11-20 13:04:59] NOTICE[19858] chan_sip.c: Peer '2006' is now UNREACHABLE!  Last qualify: 2021
[2009-11-20 13:05:11] NOTICE[19858] chan_sip.c: Peer '2006' is now Reachable. (2058ms / 5000ms)
[2009-11-20 13:18:38] NOTICE[19858] chan_sip.c: Peer '2006' is now Lagged. (6045ms / 5000ms)
[2009-11-20 13:18:49] NOTICE[19858] chan_sip.c: Peer '2006' is now Reachable. (1569ms / 5000ms)
[2009-11-20 13:19:56] NOTICE[19858] chan_sip.c: Peer '2006' is now Lagged. (7169ms / 5000ms)
[2009-11-20 13:20:08] NOTICE[19858] chan_sip.c: Peer '2006' is now Reachable. (1669ms / 5000ms)
[2009-11-20 13:21:18] NOTICE[19858] chan_sip.c: Peer '2006' is now UNREACHABLE!  Last qualify: 1676
[2009-11-20 13:21:29] NOTICE[19858] chan_sip.c: Peer '2006' is now Reachable. (1094ms / 5000ms)
[2009-11-20 13:22:36] NOTICE[19858] chan_sip.c: Peer '2006' is now Lagged. (7136ms / 5000ms)
[2009-11-20 13:22:47] NOTICE[19858] chan_sip.c: Peer '2006' is now Reachable. (1153ms / 5000ms)
[2009-11-20 13:23:54] NOTICE[19858] chan_sip.c: Peer '2006' is now Lagged. (6101ms / 5000ms)
[2009-11-20 13:24:05] NOTICE[19858] chan_sip.c: Peer '2006' is now Reachable. (1046ms / 5000ms)
[2009-11-20 13:25:15] NOTICE[19858] chan_sip.c: Peer '2006' is now UNREACHABLE!  Last qualify: 1046
[2009-11-20 13:25:26] NOTICE[19858] chan_sip.c: Peer '2006' is now Reachable. (1100ms / 5000ms)
[2009-11-20 13:30:39] NOTICE[19858] chan_sip.c: Peer '2006' is now UNREACHABLE!  Last qualify: 1753
[2009-11-20 13:30:50] NOTICE[19858] chan_sip.c: Peer '2006' is now Reachable. (992ms / 5000ms)
[2009-11-20 13:31:55] NOTICE[19858] chan_sip.c: Peer '2006' is now Lagged. (5436ms / 5000ms)
[2009-11-20 13:32:07] NOTICE[19858] chan_sip.c: Peer '2006' is now Reachable. (1118ms / 5000ms)

Has anyone else observed this?


We are not experiencing the phone unregistering - the registration seems valid throughout.


Mike

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

since my experience with the WIP300 I never dared to touch any of those series again


although cisco documentation tells me the WIP310 has the same 'SIP' stack as the SPA9xx series


is the WIP310 connected via LAN, or is it at another site ?

and can you call normally, or do an echo test ? (normally at *43)

tiagoaviz Tue, 01/19/2010 - 11:27
User Badges:

I see the exact same behavior here. Is your WIP310 usable? I can't put it to production use :(

MIKE JENKINS Wed, 01/20/2010 - 01:05
User Badges:

No. It's no good for production. Just doesn't ring most of the time because it's marked as unreachable by Asterisk.

tiagoaviz Wed, 01/20/2010 - 02:24
User Badges:

Hey Mike,


Thanks for your input. In my case, it consistently gets tagged as lagged but in my case it always rings when called at.


My issue is that is goes "acquiring network" on its screen during a call, causing it to drop.


How are outbound calls on your WIP 310? Do you still have any?


Thanks!

Actions

This Discussion

Related Content