[Serusers] ser 2_0_0 lookup_user($tu.uid, @ruri) and handling of user names with unescaped semicolon.
Jiri Kuthan
jiri at iptel.org
Thu Oct 18 11:57:47 CEST 2007
no, it is saying that "sip:alice;day=<mailto:tuesday at atlanta.com>tuesday at atlanta.com" is the username
(consistiing of semicolon, equal sign, etc.) A strange but a valid one.
The only deficit to my knowledge is not expanding % escapes. (perhaps you want
to report it in JIRA?)
-jiri
p.s. some of the questions you had asked previously are addressed in the new oob.cfg
-- feel free to check it out and give feeback.
At 11:36 18/10/2007, Tomasz Zieleniewski wrote:
>Hi,
>
>According to rfc 3261:
>
>
>
>19.1.3 Example SIP and SIPS URI
>
>
>
> sip:alice;day=<mailto:tuesday at atlanta.com>
>tuesday at atlanta.com
>
> The last sample URI above has a user field value of
> "alice;day=tuesday". The escaping rules defined above allow a
> semicolon to appear unescaped in this field. For the purposes of
>
> this protocol, the field is opaque. The structure of that value is
> only useful to the SIP element responsible for the resource.
>
>
>in such case shouldn't the lookup_user($tu.uid, @ruri) method analyze only the username part before semicolon
>for the lookup??
>
>Waiting for Your Feedback
>Bests
>Tomasz
>_______________________________________________
>Serusers mailing list
>Serusers at lists.iptel.orghttp://lists.iptel.org/mailman/listinfo/serusers
--
Jiri Kuthan http://iptel.org/~jiri/
More information about the sr-users
mailing list