[Home]

Summary:ASTERISK-25414: CLONE - [patch] IMS TEL URI incoming INVITE RFC 3966 not recognized
Reporter:Alexander Gonchiy (alexander.gonchiy)Labels:INVITE PATCH RFC3966 RFC5341 SIP TEL URI
Date Opened:2015-09-22 09:15:28Date Closed:2015-09-22 13:41:05
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/Interoperability
Versions:11.17.1 11.19.0 Frequency of
Occurrence
Related
Issues:
is the original version of this clone:ASTERISK-17179 [patch] IMS TEL URI incoming INVITE RFC 3966 not recognized
Environment:All platformsAttachments:
Description:Asterisk still doesn't recognize tel uri, causing loss of rdnis in incoming calls:

[2015-09-22 15:03:30] WARNING[2194][C-00000f66]: chan_sip.c:17454 get_rdnis: Huh?  Not an RDNIS SIP header (tel:7XXXXXXXXXX)?

Although patched in 11.5.0, this is still an issue in later versions - checked 11.17.1 and 11.19.0.
Comments:By: Asterisk Team (asteriskteam) 2015-09-22 09:15:29.901-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: Richard Mudgett (rmudgett) 2015-09-22 13:41:05.835-0500

This patch was committed to trunk on April 17 2014.  Asterisk v13 has since been branched from trunk so it contains the patch.  The patch will not go into v11 because it is a new feature.