| Summary: | ASTERISK-25637: Multi homed server using wrong IP | ||||
| Reporter: | Daniel Journo (journo) | Labels: | |||
| Date Opened: | 2015-12-18 08:31:17.000-0600 | Date Closed: | 2015-12-20 17:07:22.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Channels/chan_pjsip | ||
| Versions: | 13.5.0 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Attachments: | ||||
| Description: | A server with two IPs on one NIC.
IP1: X.X.X.85 (this IP belongs to the server) IP2: X.X.X.87 (this is a virtual IP, managed by pacemaker failover with another server). In the transport I've specified the virtual IP like this:- [transport-public-udp] type = transport external_signaling_address = X.X.X.87 ;I note that this might not be relevant but did this to try to resolve my issue. external_media_address=X.X.X.87 ;I note that this might not be relevant but did this to try to resolve my issue. protocol = udp bind = X.X.X.87 An endpoint is defined like this:- [company_202] type=endpoint context=company_phones disallow=all allow=ulaw direct_media=no moh_suggest=default ;media_use_received_transport=yes accountcode=company force_rport=yes rtp_symmetric=yes rewrite_contact=yes auth=auth_company_202 aors=company_202 [auth_company_202] type=auth auth_type=userpass password=secret username=company_202 [company_202] type=aor max_contacts=1 remove_existing=1 The endpoint registers successfully to the virtual IP and all SIP packets are sent of the virtual IP X.X.X.87. But the RTP UDP data is being sent out of the wrong IP X.X.X.85. It looks like Asterisk is ignoring the Bind address when sending out the audio. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2015-12-18 08:31:18.528-0600 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: Daniel Journo (journo) 2015-12-20 14:56:45.070-0600 Just realised that this has recently been reported here. ASTERISK-25632 I've added more information there. By: Joshua C. Colp (jcolp) 2015-12-20 17:07:22.409-0600 This is being tracked at ASTERISK-25632. | ||||