Hi,<br><br>According to rfc 3261:<br><pre><span class="h4"><h4><a name="section-19.1.3">19.1.3</a> Example SIP and SIPS U<span style="font-family: monospace;">RI</span></h4></span> sip:alice;day=<a href="mailto:tuesday@atlanta.com">
tuesday@atlanta.com</a><br><br> The last sample URI above has a user field value of<br> "alice;day=tuesday". The escaping rules defined above allow a<br> semicolon to appear unescaped in this field. For the purposes of
<br> this protocol, the field is opaque. The structure of that value is<br> only useful to the SIP element responsible for the resource.<span class="h4"><br></span></pre><br>in such case shouldn't the lookup_user($tu.uid, @ruri) method analyze only the username part before semicolon
<br>for the lookup??<br><br>Waiting for Your Feedback<br>Bests<br>Tomasz<br>