[asterisk-bugs] [JIRA] (ASTERISK-20963) iax2 not responding to registration packets

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-20963:
----------------------------------------

A few things:
# There is not enough information on this issue to determine what is actually occurring. Please attach a pcap with the IAX2 traffic.
# From the release summaries, there does not appear to be any changes that were made to {{chan_iax2}} between 1.8.18.0 and 1.8.19.0.
# Asterisk does not silently reject registrations. On top of that, it does not drop or hide packets when the appropriate channel technology debug is enabled. This, combined with the lack of changes in {{chan_iax2}}, makes me suspect that there is a configuration issue here.

Please at least provide a pcap, which should illustrate whether or not there is a network condition affecting the traffic. Please also provide a DEBUG 5 log with 'iax2 set debug on' enabled so that we can verify the lack of packets.
                
> iax2 not responding to registration packets
> -------------------------------------------
>
>                 Key: ASTERISK-20963
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20963
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: 1.8.19.0
>         Environment: centos 5.2
>            Reporter: sdolloff
>            Severity: Critical
>
> using iaxmodem to connect to asterisk peers on localhost. asterisk shows no data from 'iax2 set debug on'.  tcpdump shows no response to registration packets to asterisk.  works in 1.8.18.0 but not 1.8.19.0-rc1 or subsequent versions.  iax.conf entry:  
> {noformat}
> ; fax001
> [fax001]
> callerid=Fax001 <0000000000>
> secret=somesecretword
> context=mycontext
> type=friend
> host=dynamic
> transfer=no
> qualify=no
> requirecalltoken=no
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira