Summary: | ASTERISK-25756: INVITEs are sent to old peer ip address if usereqphone is set true | ||
Reporter: | Daniel Heckl (DanielYK) | Labels: | |
Date Opened: | 2016-02-08 13:26:17.000-0600 | Date Closed: | |
Priority: | Major | Regression? | |
Status: | Open/New | Components: | |
Versions: | 13.7.1 13.7.2 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | Attachments: | ( 0) asterisk-debug.log ( 1) sip-debug.txt | |
Description: | Sometimes our provider sent us to another SIP server (because my ip address has changed). So asterisk re-register (all 480 sec) successfully to the new one and updated the peer ip address (dnsmgr ist turned on).
However: OPTIONS and INVITEs are sent to the old ip address. So our provider replies to INVITEs with Forbidden. Only after an "core reload" everything works again. I think the bug is since 13.7.2/13.7.1. Usually the update of the provider ip address works without problems. These trunks uses chan_sip. sip show peers (excerpt) 0987654321/123456789 217.0.20.232 No No A 5060 OK (12 ms) | ||
Comments: | By: Asterisk Team (asteriskteam) 2016-02-08 13:26:18.698-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: Joshua C. Colp (jcolp) 2016-02-08 16:29:59.088-0600 Do you know of a version where this was seemingly working? chan_sip hasn't really been touched that much if at all. By: Daniel Heckl (DanielYK) 2016-02-09 00:54:12.998-0600 I must confess, I can not say exactly. We used asterisk 13 not so long. Before we were at asterisk 11.19.0. At that time there were no problems. By: Daniel Heckl (DanielYK) 2016-02-09 08:47:52.278-0600 We had set "usereqphone = yes". Now I have removed it and couldn't reproduce the error any more. By: Joshua C. Colp (jcolp) 2016-02-09 09:59:41.573-0600 Per reporter, was a configuration issue. By: Daniel Heckl (DanielYK) 2016-02-09 10:04:18.243-0600 I don't think it is a configuration issue, why does this problem appear with "usereqphone = yes". Asterisk should in this situation also contact the provider with the actual peer ip address. RFC 3261 describes following "If the user string contains a telephone number formatted as a telephone-subscriber, the user parameter value "phone" SHOULD be present.". That has nothing to do with the problem. I think it is a bug! By: Asterisk Team (asteriskteam) 2016-02-09 10:04:18.661-0600 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. |