[asterisk-bugs] [JIRA] (ASTERISK-21011) Asterisk to Asterisk IAX2 trunk registration does not register

[Jonathan Rose (JIRA)]

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

Jonathan Rose commented on ASTERISK-21011:
------------------------------------------

I have a couple things to request from you as well.

1. Complete iax.conf including general sections, register lines, etc for both machines. Just the peer definitions won't cut it unfortunately. I assumed that you included a line like:
register => iax2testprotocol:scrubbed at 192.168.192.1

in 192.168.192.74's config since the peer definition for 192.168.192.74 on the other machine was dynamic, but so far I still haven't been able to reproduce the bug using these configurations.


2. Output of the following command on each machine:
module show like res_timing

-- there were only two changes that really touched chan_iax2 over the revisions between the one that the bug is reported as present in and the one that it isn't. One of them seemed really innocuous and self-contained. The other was timing related, so aligning which timing modules we are both using might to isolate it.
                
> Asterisk to Asterisk IAX2 trunk registration does not register
> --------------------------------------------------------------
>
>                 Key: ASTERISK-21011
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21011
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: 11.2.1
>            Reporter: David Brillert
>            Assignee: David Brillert
>         Attachments: iax2 asterisk to asterisk failure.txt, iax2 configurations.txt, iax2 debug 11.0.1.txt
>
>
> Asterisk dynamic server does not update iax2 show peers or register remote/static Asterisk server.
> iax2 set debug on trace uploaded from both servers.

--
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