[asterisk-bugs] [JIRA] (ASTERISK-13156) Asterisk logs: Max retries exceeded to host on IAX/peer (type = 6, subclass = 11) but these packages can't be found in a tcpdump

[Bobby Hakimi (JIRA)]

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

Bobby Hakimi commented on ASTERISK-13156:
-----------------------------------------

i have the same issue with asterisk 11.25. anyone got any updates with this ?

> Asterisk logs: Max retries exceeded to host on IAX/peer (type = 6, subclass = 11) but these packages can't be found in a tcpdump
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-13156
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-13156
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Channels/chan_iax2
>            Reporter: Daniel Tryba
>         Attachments: 20081202__bug14008.diff.txt
>
>
> During the last 2 months I had a couple of asterisk "crashes", each time the logs get spammed with lines like:
> [Dec  1 20:18:55] WARNING[1812] chan_iax2.c: Max retries exceeded to host 89.146.34.134 on IAX2/locografix-5656 (type = 6, subclass = 2, ts=4978257, seqno=230)
> During the last I had the opportunity  to make a tcpdump (tshark -w /tmp/foo port 4569), but this tcpdump only contains normal iax2 traffic for this host:
> pokes/pongs/acks and regreqs/regacks/acks
> So the only subclass I have in the cap are 3,4,13,15 and 30.
> During the previous "crash" the problem started with 1 iax peer, but over the course of 30m the max retries log entries started to appear for almost all iax peers (sadly no packetdump from this crash).
> Next time I'll try to remember to dump all interfaces (2 ethernet (1 external, 1 lan) and loopback), maybe somehow asterisk is routing the traffic to the wrong interface. 
> Restarting asterisk fixes all problems.
> This machine is the gateway to the ISDN network, the peers connect thru iax trunks.
> ****** ADDITIONAL INFORMATION ******
> Asterisk version is 1.4.21.2 from Debian/unstable backported to Debian/stable amd64, so there are a couple of nonstandard patches applied, but the only patch that might interfere with iax is the chan-iax2-hangup-cause patch (http://patch-tracking.debian.net/patch/series/view/asterisk/1:1.4.21.2~dfsg-2/bristuff/chan-iax2-hangup-cause)
> The cause of the problem might be in the zaptel driver used on this system. I found this iax problem when I couldn't dial a external number through the ISDN-pri connected to a TE121 with VPMADT032. Due to echo cancelling problems with the hw canceller we are running http://svn.digium.com/svn/zaptel/team/mspiceland/zaptel-1.4-adtapiupdatefor117 (rev 4420). Trying to dial outwards from iax hangs (Dial(Zap/g1/xxx) never returns), incoming calls get routed to the fallback asterisk server by the isdn provider.
> So my dilemma is: should the bug category be iax of zaptel? Since I have no usefull zaptel debug info I decided for iax since the max retries log entries appear not to be correct.
> BTW up until the calls started to get routed to the fallback machine, "pri debug span 1" was producing the normal debug output, suddenly it went completely silent.



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