[asterisk-bugs] [JIRA] (ASTERISK-26780) res_pjsip: PJSIP Registration Fails when transport=transport-udp6

[Joshua Colp (JIRA)]

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

Joshua Colp updated ASTERISK-26780:
-----------------------------------

    Summary: res_pjsip: PJSIP Registration Fails when transport=transport-udp6  (was: PJSIP Registration Fails when transport=transport-udp6)

> res_pjsip: PJSIP Registration Fails when transport=transport-udp6
> -----------------------------------------------------------------
>
>                 Key: ASTERISK-26780
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26780
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 14.2.1
>            Reporter: Peter Sokolov
>            Severity: Trivial
>         Attachments: Debug-Log.txt, pjsip.conf, sip.log
>
>
> Probably related to ASTERISK-26309.
> When a section "type=registration" in pjsip.conf contains the line
> transport=transport-udp6
> registration fails even though the registrar hostname resolves to both, IPv4 and IPv6 address.
> With "transport=transport-udp" registration is successfull to the IPv4 address of the registrar and without the "transport=" line, registration is successfull to the IPv6 address of the registrar.
> Debug messages show that with "transport=transport-udp6", Asterisk will only lookup DNS names of type 1 (A), 33 (SRV) and 35 (NAPTR), but not type 28 (AAAA), while in other two cases (transport-udp and without transport=) it will lookup DNS types 1, 33, 28 and 35.
> As can be seen in the sip.log it somehow tries to send out a REGISTER request directed to IPv4 address of the registrar, otherwise filled with IPv6 addresses. It looks like this packet does not get sent out however:
> Failed to send Request msg REGISTER/cseq=37962 (tdta0x7fb4500607b0)! err=120101 (Network is unreachable)
> I have not checked whether the behavior is similar when transport= is used on type=endpoint.



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