| Summary: | ASTERISK-26934: res_pjsip_sdp_rtp: RTP instance does not use same IP as explicit transport (unspecified transport) | ||||
| Reporter: | Bernhard Schmidt (bschmidt) | Labels: | |||
| Date Opened: | 2017-04-10 08:50:01 | Date Closed: | |||
| Priority: | Major | Regression? | |||
| Status: | Open/New | Components: | Resources/res_pjsip_sdp_rtp | ||
| Versions: | 13.15.0 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | Debian | Attachments: | |||
| Description: | 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 | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2017-04-10 08:50:02.276-0500 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. 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]. By: Joshua C. Colp (jcolp) 2017-04-13 08:58:41.799-0500 If the target of a SIP INVITE is an explicit IP address then we could determine the local IP address that will be used for the traffic and bind to that only. | ||||