[asterisk-bugs] [Asterisk 0014041]: [patch] IAXy runs ok for a while, then goes bonkers

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Jan 20 11:25:23 CST 2009


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14041 
====================================================================== 
Reported By:                jcovert
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   14041
Category:                   Channels/chan_iax2
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.21.2 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-12-09 09:18 CST
Last Modified:              2009-01-20 11:25 CST
====================================================================== 
Summary:                    [patch] IAXy runs ok for a while, then goes bonkers
Description: 
After up to a month, or as little as a day or two, both the IAXy I
originally purchased, and a replacement given to me by Stephen Burcham in
October (to try to eliminate a specific piece of hardware) become
unreliable.  In some cases it just stops processing calls, in the more
likely case, documented in the attached log, it goes into a
reachable/unreachable loop like this:

[Dec  9 10:01:45] NOTICE[26712]: chan_iax2.c:8832 __iax2_poke_noanswer:
Peer 'x29' is now UNREACHABLE! Time: 5
[Dec  9 10:01:45] NOTICE[26712]: chan_iax2.c:7912 socket_process: Peer
'x29' is now REACHABLE! Time: 10
[Dec  9 10:02:29] NOTICE[26712]: chan_iax2.c:8832 __iax2_poke_noanswer:
Peer 'x29' is now UNREACHABLE! Time: 10
[Dec  9 10:02:29] NOTICE[26712]: chan_iax2.c:7912 socket_process: Peer
'x29' is now REACHABLE! Time: 13

Since it provides service to the phone next to the main place at which
"she who expects phones to work" generally sits, this causes me a major
headache.
====================================================================== 

---------------------------------------------------------------------- 
 (0098204) jcovert (reporter) - 2009-01-20 11:25
 http://bugs.digium.com/view.php?id=14041#c98204 
---------------------------------------------------------------------- 
Eventually we're lucky, and the last PROVISN coming out of Asterisk is the
one for version "3538259848", and after that all is quite until the next
reload of Asterisk, when this whole thing starts over again.

Rx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass:
REGREQ 
   Timestamp: 00002ms  SCall: 12963  DCall: 00000 [192.168.0.17:4569]
   USERNAME        : x29
   REFRESH         : 60
   DEVICE TYPE     : iaxy2
   SERVICE IDENT   : 000000000cc8
   PROVISIONG VER  : 3538259848

Tx-Frame Retry[000] -- OSeqno: 000 ISeqno: 001 Type: IAX     Subclass:
REGACK 
   Timestamp: 00019ms  SCall: 14937  DCall: 12963 [192.168.0.17:4569]
   USERNAME        : x29
   DATE TIME       : 2009-01-20  11:38:16
   REFRESH         : 60
   APPARENT ADDRES : IPV4 192.168.0.17:4569
   CALLING NUMBER  : 29
   CALLING NAME    : John Covert IAXy

Rx-Frame Retry[ No] -- OSeqno: 001 ISeqno: 001 Type: IAX     Subclass: ACK
   
   Timestamp: 00019ms  SCall: 12963  DCall: 14937 [192.168.0.17:4569] 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-20 11:25 jcovert        Note Added: 0098204                          
======================================================================




More information about the asterisk-bugs mailing list