kenmirrors/asterisk
1
0
Fork 0
mirror of https://github.com/asterisk/asterisk.git synced 2025-10-03 03:02:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

res_pjsip: Add ignore_uri_user_options option.

Browse Source 
This implements the chan_sip legacy_useroption_parsing option but with a
better name.

* Made the caller-id number and redirecting number strings obtained from
incoming SIP URI user fields always truncated at the first semicolon.
People don't care about anything after the semicolon showing up on their
displays even though the RFC allows the semicolon.

ASTERISK-26316 #close
Reported by: Kevin Harwell

Change-Id: Ib42b0e940dd34d84c7b14bc2e90d1ba392624f62
This commit is contained in:
Richard Mudgett
2016-08-29 18:08:22 -05:00
parent 7580a736bb
commit 30af92e78d
16 changed files with 276 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
res/res_pjsip.c
View File

@@ -1544,6 +1544,30 @@
</para>
</description>
</configOption>
<configOption name="ignore_uri_user_options">
<synopsis>Enable/Disable ignoring SIP URI user field options.</synopsis>
<description>
<para>If you have this option enabled and there are semicolons
in the user field of a SIP URI then the field is truncated
at the first semicolon. This effectively makes the semicolon
a non-usable character for PJSIP endpoint names, extensions,
and AORs. This can be useful for improving compatability with
an ITSP that likes to use user options for whatever reason.
</para>
<example title="Sample SIP URI">
sip:1235557890;phone-context=national@x.x.x.x;user=phone
</example>
<example title="Sample SIP URI user field">
1235557890;phone-context=national
</example>
<example title="Sample SIP URI user field truncated">
1235557890
</example>
<note><para>The caller-id and redirecting number strings
obtained from incoming SIP URI user fields are always truncated
at the first semicolon.</para></note>
</description>
</configOption>
</configObject>
</configFile>
</configInfo>