[asterisk-bugs] [JIRA] (ASTERISK-21996) chan_iax2 fails to process network packets after a while

[Rusty Newton (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208205#comment-208205 ] 

Rusty Newton commented on ASTERISK-21996:
-----------------------------------------

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.  Further information can be found at http://www.asterisk.org/developers/bug-guidelines


                
> chan_iax2 fails to process network packets after a while
> --------------------------------------------------------
>
>                 Key: ASTERISK-21996
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21996
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: 11.2.2, 11.3.0, 11.4.0
>         Environment: Gentoo ebuild Asterisk without additional patches
>            Reporter: Heiko Wundram
>         Attachments: threads-bt.txt
>
>
> After a while, chan_iax2 fails to accept new networking packets. The initial symptom is visible when enabling IAX2-debugging: outgoing packets are shown, but all incoming packets (directed to the correct port) are no longer visible inside Asterisk, even tough they do show up with an appropriate tcpdump on the corresponding network interface they arrive at. All IAX2 peers become unreachable, and IAX2 calls stop working.
> I've core-dumped a running Asterisk executable while it was in this state, and it seems that the IAX2 networking thread (chan_iax2.c:network_thread) isn't running anymore. The issue doesn't seem to affect any other areas of networking/SIP telephony in the Asterisk core, and the IAX2 module seems to be running fine otherwise (i.e., all threads are "idle") even though the networking thread is "gone".
> I've not yet tried additional debugging while Asterisk is running yet.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira