From 30af92e78d36523f8012da5eb9aee16687d8fe61 Mon Sep 17 00:00:00 2001 From: Richard Mudgett Date: Mon, 29 Aug 2016 18:08:22 -0500 Subject: res_pjsip: Add ignore_uri_user_options option. 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 --- configs/samples/pjsip.conf.sample | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'configs') diff --git a/configs/samples/pjsip.conf.sample b/configs/samples/pjsip.conf.sample index 994c8e01c..8d063f4fd 100644 --- a/configs/samples/pjsip.conf.sample +++ b/configs/samples/pjsip.conf.sample @@ -979,6 +979,22 @@ ; If disabled then unsolicited mwi will start processing ; on the endpoint's next contact update. +;ignore_uri_user_options=no ; Enable/Disable ignoring SIP URI user field options. + ; 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. + ; Example: + ; URI: "sip:1235557890;phone-context=national@x.x.x.x;user=phone" + ; The user field is "1235557890;phone-context=national" + ; Which becomes this: "1235557890" + ; + ; Note: The caller-id and redirecting number strings obtained + ; from incoming SIP URI user fields are always truncated at the + ; first semicolon. + ; MODULE PROVIDING BELOW SECTION(S): res_pjsip_acl ;==========================ACL SECTION OPTIONS========================= ;[acl] -- cgit v1.2.3