|
From: | Karol Rosłaniec |
Subject: | [osip-dev] Sip uri parsing |
Date: | Mon, 23 Oct 2017 01:58:13 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 |
Hi, When analyzing IMS implementation, I've found out that osip
library is (probably) incorrectly parsing sip uri. Let's consider the field "From" like below (this is a real-world
example): From: <sip:0123456789;address@hidden;user=phone>;tag=0e20s135-DD-1008-OAC-24 is parsed by osip2 library (git master) to osip_uri_t: scheme=sip username=0123456789;phone-context=ims.mnc001.mcc123.3gppnetwork.org passowrd= host=ims.mnc001.mcc123.3gppnetwork.org port= string= url_params=1 url_headers=
Obviously I would expect rather "string=0123456789" And additionally two params: "phone-context" and "user". I'm not sure what are the parsing rules according to RFC and
if "@" sign is allowed inside phone-context. But even if it is not, the example above is from real IMS implementation and somehow I have to handle it even if it's not standard compliant. Do you have any plans to fix or improve osip2 uri parsing methods? Best Regards, Karol Roslaniec |
[Prev in Thread] | Current Thread | [Next in Thread] |