Hi,

According to rfc 3261:
19.1.3 Example SIP and SIPS URI
   sip:alice;day=
tuesday@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