[asterisk-bugs] [JIRA] (ASTERISK-29957) Transport autoselection is broken on FreeBSD

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-29957:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> Transport autoselection is broken on FreeBSD
> --------------------------------------------
>
>                 Key: ASTERISK-29957
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29957
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 16.24.1, 18.10.1
>         Environment: OS: FreeBSD 13.0-RELEASE
> Architecture: amd64
> Environment: jail(8)
>            Reporter: 04dco
>
> PJSIP transport autoselection fails and the last defined transport in pjsip.conf is used if not explicitly specified on endpoint, as a result no audio gets through. For example if the last transport in pjsip.conf is over IPv6, calls over IPv4 have no audio. RTP Packet Debugging says packets of -13 bytes are send to the endpoint but none are received back. When the endpoint tries to send RTP packets to Asterisk, they bounce with ICMP port-unreachable.
> Issue is as described in this older forum post:
> https://community.asterisk.org/t/13-14-0-pjsip-rtp-problem-no-audio/70244
> RTP Packet Debugging output excerpt:
> [Mar  6 23:17:40] Sent RTP packet to      10.0.1.5:33024 (type 09, seq 020789, ts 000160, len -000013)
> [Mar  6 23:17:40] Sent RTP packet to      10.0.1.5:33024 (type 09, seq 020790, ts 000320, len -000013)
> [Mar  6 23:17:40] Sent RTP packet to      10.0.1.5:33024 (type 09, seq 020791, ts 000480, len -000013)
> Forcing transport fixes it but for one address family only. If I force an IPv4 UDP transport then RTP over IPv6 breaks with the usual -13 byte packets and vice-versa. If I force an IPv4 UDP transport, TLS over IPv4 works normally.
> Steps to reproduce: specify two UDP transports in pjsip.conf, one over IPv4 then one over IPv6 (in that order). Make a call over IPv4 and fail to get audio.
> Workarounds: explicitly specify transport for endpoints



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