| Summary: | ASTERISK-28345: IMS TEL URI incoming INVITE RFC 3966 not recognized | ||||||
| Reporter: | newborn (newborn838) | Labels: | |||||
| Date Opened: | 2019-03-22 06:37:48 | Date Closed: | 2019-03-28 08:17:42 | ||||
| Priority: | Trivial | Regression? | |||||
| Status: | Closed/Complete | Components: | Channels/chan_sip/General | ||||
| Versions: | 13.25.0 | Frequency of Occurrence | Constant | ||||
| Related Issues: |
| ||||||
| Environment: | Attachments: | ||||||
| Description: | Issue still not resolved.
Getting this upon an incoming call: [Mar 22 14:32:54] WARNING[22921][C-00000093]: chan_sip.c:18256 get_rdnis: Huh? Not an RDNIS SIP header (tel:7x)? [Mar 22 14:32:54] -- Executing [7xxxxxxxx@incoming-from-mangotelecom:1] [Mar 22 14:34:08] INVITE sip:7xxxxxxxx@7x:5060 SIP/2.0 [Mar 22 14:34:08] Via: SIP/2.0/UDP 81.x:5060;branch=z9hG4bKb6a9.4a5bcd83.0 [Mar 22 14:34:08] Max-Forwards: 68 [Mar 22 14:34:08] Contact: <sip:7x@8x;did=43a.e6b18777> [Mar 22 14:34:08] To: <sip:asterisk@xxx> [Mar 22 14:34:08] From: "7x"<sip:7x@x>;tag=3457da2c [Mar 22 14:34:08] Call-ID: Jn4dEWWGNJywY0P9VQWN1A.. [Mar 22 14:34:08] CSeq: 1 INVITE [Mar 22 14:34:08] Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, UPDATE, UPDATE, INFO, REFER, MESSAGE [Mar 22 14:34:08] Content-Type: application/sdp [Mar 22 14:34:08] Supported: replaces [Mar 22 14:34:08] User-Agent: Softswitch3 [Mar 22 14:34:08] x-comm-id: 201:300885250 [Mar 22 14:34:08] x-comm-context: 6048132520 [Mar 22 14:34:08] x-intf-context_group_id: 6048132508 [Mar 22 14:34:08] Diversion: <tel:7x>;counter=1;reason=unconditional [Mar 22 14:34:08] Content-Length: 316 | ||||||
| Comments: | By: Asterisk Team (asteriskteam) 2019-03-22 06:37:49.197-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]. 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. By: Sean Bright (seanbright) 2019-03-22 09:15:17.434-0500 bq. Issue still not resolved. Was there some indication that this was resolved? Is there another open issue you are referring to? Edit - I assume this is referencing ASTERISK-17179 By: newborn (newborn838) 2019-03-26 03:43:35.411-0500 Yes, it was resolved in 11. In Asterisk 13 it is appeared again. By: Joshua C. Colp (jcolp) 2019-03-26 04:35:29.768-0500 What exactly happens besides the WARNING message? I also checked the code itself, and the code (including the WARNING message) is the same in 1.8. By: newborn (newborn838) 2019-03-26 04:41:17.135-0500 Nothing, just warnings. It is annoying and it's flooding the message log. | ||||||