The qualify is on for the peer. It is failing to reply to the requested
SIP status. Maybe it is on wifi, screen goes off, wifi follows, zoiper
iax stack doesn't re-reg with the asterisk.
[Oct 8 18:14:14] NOTICE[510]: chan_iax2.c:11071 socket_process_helper:
Peer 'n4' is now REACHABLE! Time: 441
[Oct 8 18:15:58] NOTICE[519]: chan_iax2.c:8153 register_verify: Host
<n4ipaddr> failed MD5 authentication for 'n4'
(c374d0a70c72e6e9bd359aa6a0f1a6c2 != 2c76c104bbfc3d54f566490f40cd12bd)
[Oct 8 18:19:17] NOTICE[517]: chan_iax2.c:11077 socket_process_helper:
Peer 'n4' is now TOO LAGGED (1002 ms)!
[Oct 8 18:19:29] NOTICE[512]: chan_iax2.c:11071 socket_process_helper:
Peer 'n4' is now REACHABLE! Time: 300
[Oct 8 18:26:02] NOTICE[519]: chan_iax2.c:11077 socket_process_helper:
Peer 'n4' is now TOO LAGGED (1017 ms)!
ip-172-31-29-115*CLI> iax2 show peers
Name/Username Host Mask Port Status Description
n4 <n4ipaddr> (D) 255.255.255.255 4569 LAGGED (1017 ms)
is it still registered, or do we really have an authentication problem?
sean
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
