[asterisk-bugs] [JIRA] (ASTERISK-25286) After a period of time chan_iax2 stops accepting packets

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-25286:
-----------------------------------------

In regards to my comment above.

Please provide:

 * Debug log excerpt covering a time period starting before the issue occurs and ending after the issue has occurred. 
 * Debug log captured after you have unloaded and loaded the module to demonstrate normal function.

Make sure the debug logs include verbose, debug and the output of "iax2 set debug on". verbose and debug should both be turned up to 5 and please verify they are present in the log before attaching it to the issue.

Can you test with the latest Git branch of 11 to see if the issue still occurs? 

> After a period of time chan_iax2 stops accepting packets
> --------------------------------------------------------
>
>                 Key: ASTERISK-25286
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25286
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: 11.6.0
>         Environment: CentOS 5.11 2.6.18-400.1.1.el5 i686
>            Reporter: rsw686
>
> This issue is occurring on two servers running CentOS 5.11 i686 after upgrading from 1.8.15-cert5 to 11.6-cert11. After a day or two chan_iax2 will stop accepting packets. Turning on iax2 debug you will see the outgoing packets, but no inbound packets.
> If I issue "module unload chan_iax2.so" and "module load chan_iax2.so" everything starts working again. This looks to be identical to ASTERISK-21996, but I was told to open a new issue.
> Interestingly I have a CentOS 5.11 x86_64 server that was also upgraded from 1.8.15-cert5 to 11.6-cert11 that doesn't experience this issue. I also have a Red Hat 6.5 x86_64 server running 11.6-cert4 that doesn't experience this issue.



--
This message was sent by Atlassian JIRA
(v6.2#6252)