[asterisk-bugs] [JIRA] (ASTERISK-26934) RTP instance does not use same IP as explicit transport (unspecified transport)

Bernhard Schmidt (JIRA) noreply at issues.asterisk.org
Mon Apr 10 08:50:59 CDT 2017


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

Bernhard Schmidt updated ASTERISK-26934:
----------------------------------------

    Summary: RTP instance does not use same IP as explicit transport (unspecified transport)  (was: CLONE - RTP instance does not use same IP as explicit transport (unspecified transport))

> RTP instance does not use same IP as explicit transport (unspecified transport)
> -------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26934
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26934
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Resources/res_pjsip_sdp_rtp
>    Affects Versions: 13.15.0
>         Environment: Debian
>            Reporter: Bernhard Schmidt
>
> ASTERISK-26851 fixed an issue where you explicitly needed to set media_address on multihomed systems. Unfortunately, this code only works when transport is explicitly set on the endpoint and the transport is explicitly set to a specific IP.
> This makes it impossible to configure an endpoint (customer) that can dynamically use UDP/TLS or IPv4/IPv6.
> If transport is not set RTP should bind to the IP address used in the transport the endpoint is registered on



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



More information about the asterisk-bugs mailing list