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

sdolloff (JIRA) noreply at issues.asterisk.org
Wed Feb 20 12:26:19 CST 2013


     [ https://issues.asterisk.org/jira/browse/ASTERISK-20963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

sdolloff updated ASTERISK-20963:
--------------------------------

    Status: Waiting for Feedback  (was: Waiting for Feedback)

I checked my menuselect and the only res_timing option currently available to me on these systems is pthread.  Adding load => res_timing_pthread.so in modules.conf and restarting asterisk solved the problem. 

It seems like the iax2 modules should throw an error if it now requires a timing source and one isn't available. I've never loaded one before and this has been working across various versions for years.
                
> 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
>            Assignee: sdolloff
>            Severity: Critical
>         Attachments: consolecapture.txt, iax18.pcap, iax19.pcap, iax20.pcap, iax2 debug 11.0.1.txt, iax.conf-modified, myconfigs.tgz, ttyIAX000-modified.txt
>
>
> 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



More information about the asterisk-bugs mailing list