<div dir="ltr"><div><div><div><div><div><div><div>Hi Jason,<br><br></div><div>Please ignore the last mail.<br></div><div><br></div>Thanks for
your reply, we are facing an issue in following usecase where UE will
use a different contact as shown below in INVITE.<br><br></div>UE ---------------------------------------REGISTER----------------------------------------->PCSCF<br></div>[src ip:<a href="http://127.0.0.1:8008" target="_blank">127.0.0.1:8008</a>]<br></div><a href="http://Contact:sip:user@127.0.0.1:8008" target="_blank">Contact:sip:userA@127.0.0.1:8008</a><br><br><br><br>UE ---------------------------------------INVITE----------------------------------------->PCSCF<br>[src ip:<a href="http://127.0.0.1:8008" target="_blank">127.0.0.1:8008</a>]<br><a href="http://Contact:sip:user@127.0.0.1:8008" target="_blank">Contact:sip:userB@127.0.0.1:9000</a><br><br><br></div>In
the above scenario kamailio PCSCF is treating the UE as registered,even
though the contact is different in INVITE and call will be successful.<br><br>why are we not validating the contact URI in the INVITE?is it not a mandatory to validate?if yes,any spec references?<br><br></div>Regards,<br></div>Prashant</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 25, 2015 at 3:26 PM, Prashant Desai <span dir="ltr"><<a href="mailto:pdesai05@gmail.com" target="_blank">pdesai05@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hi Jason,<br><br></div>Thanks for your reply, we are facing an issue in following usecase.<br><br></div>UE -------------------------------------------------------------------------------->PCSCF<br></div><div>REGISTER<br></div>[src ip:<a href="http://127.0.0.1:8008" target="_blank">127.0.0.1:8008</a>]<br></div><a href="http://Contact:sip:user@127.0.0.1:8008" target="_blank">Contact:sip:user@127.0.0.1:8008</a><br><div><div><div><br></div></div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 24, 2015 at 5:41 PM, Jason Penton <span dir="ltr"><<a href="mailto:jason.penton@smilecoms.com" target="_blank">jason.penton@smilecoms.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Hi Prashant,<br><br></div>Often the P-CSCF has to know about the contact (for example for Rx QoS, security (asserting identity, etc). It is also possible that a contact header is not provided by the UE so you have no alternative but to search src info, via info, etc. So that is the main reason.<br><br></div><div>So let me understand your problem a little more. You are saying the contact with the wrong state is being 'found'? If this is the case, there is a reslution we have in our code base that will get into master later this week? If not, please can you explain the problem you are having in more detail.<br><br></div><div>Cheers<br></div><div>Jason<br></div></div><div class="gmail_extra"><div><div><br><div class="gmail_quote">On Tue, Nov 24, 2015 at 1:22 PM, Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
updated the subject of the email to reflect it refers to IMS
extensions, which are different than the standard IETF registrars.<br>
<br>
That makes it easier to be spotted by the people using IMS and the
dev guys can shed some light on why the implemented that way.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div>On 24/11/15 11:59, Prashant Desai
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_quote">
<div link="blue" vlink="purple" lang="EN-US">
<div>Hi,
<p class="MsoNormal"> </p>
<p class="MsoNormal"> We observe that the following
kamailio API is trying to find out user registration by
comparing source IP and port with stored contact, if it
fails, then it compares based on incoming SIP msg
contact uri.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">is_registered(struct sip_msg* _m,
udomain_t* _d){</p>
<p class="MsoNormal"> getContactP(_m,_d);</p>
<p class="MsoNormal">}</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">pcontact_t * getContactP(struct
sip_msg* _m, udomain_t* _d) {);</p>
<p class="MsoNormal">
//Getting pcontact from source IP and port</p>
<p class="MsoNormal">
if (ul.get_pcontact_by_src(_d, &received_host,
_m->rcv.src_port, _m->rcv.proto, &c) == 1) {</p>
<p class="MsoNormal">
LM_DBG("No entry in usrloc for %.*s:%i (Proto %i)
found!\n", received_host.len, received_host.s,
_m->rcv.src_port, _m->rcv.proto);</p>
<p class="MsoNormal">
} </p>
<p class="MsoNormal"> if (c
== NULL) {</p>
<p class="MsoNormal">
//Getting pcontact from contact uri.</p>
<p class="MsoNormal" style="margin-left:1.0in;text-indent:.5in">if
(ul.get_pcontact(_d, &ct->uri, &c) == 0) {</p>
<p class="MsoNormal">
</p>
<p class="MsoNormal">
}</p>
<p class="MsoNormal"> }</p>
<p class="MsoNormal">We have use case where INVITE message
is from same source IP and port but having unregistered
contact.With this scenario,is_registered() will return
success.
</p>
<p class="MsoNormal">We would like to know reason behind
comparing the source IP and port to fetch the pcontact?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Regards,</p>
<p class="MsoNormal">Prashant</p>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><span><font color="#888888">
</font></span></pre><span><font color="#888888">
</font></span></blockquote><span><font color="#888888">
<br>
<pre cols="72">--
Daniel-Constantin Mierla
<a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a>
Book: SIP Routing With Kamailio - <a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a>
Kamailio Advanced Training, Nov 30-Dec 2, Berlin - <a href="http://asipto.com/kat" target="_blank">http://asipto.com/kat</a></pre>
</font></span></div>
<br>_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br></div></div><div><div dir="ltr"><div><table style="width:450pt" width="600" border="0" cellpadding="0" cellspacing="0"><tbody><tr><td style="padding:0cm" valign="top"><p></p></td></tr></tbody></table><table style="font-family:monospace" width="320px" border="0" cellpadding="0" cellspacing="0"><tbody><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><strong>Jason Penton</strong></td></tr><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><strong>Senior Manager: Applications and Services</strong></td></tr><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:15px;padding-top:10px"><strong>Smile Communications Pty (Ltd)</strong></td></tr><tr><td><table width="100%" cellpadding="0" cellspacing="0"><tbody><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:15px;padding-top:10px" width="27%"><strong>Mobile:</strong></td><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:10px;padding-top:10px" width="73%">+27 (0) 83 283 7000</td></tr><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:15px;padding-top:10px"><strong>Skype:</strong></td><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:10px;padding-top:10px">jason.barry.penton</td></tr></tbody></table></td></tr><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><a href="mailto:name.surname@smilecoms.com" style="font-family:Arial;color:rgb(117,179,67);text-decoration:none" target="_blank">jason.penton@smilecoms.com</a></td></tr><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><a href="http://www.smilecoms.com/" style="font-family:Arial;color:rgb(117,179,67)" target="_blank">www.smilecoms.com</a><br><img src="http://196.33.227.129/~smlcoms/sigs/pty/images/smile_signature_07_09.jpg" height="144" width="420"><br></td></tr></tbody></table></div><br></div></div>
</div>
<br>
<span><font color="#888888"><pre>This email is subject to the disclaimer of Smile Communications at <a href="http://www.smilecoms.com/home/email-disclaimer/" target="_blank">http://www.smilecoms.com/home/email-disclaimer/</a><a href="http://www.smilecoms.com/disclaimer" target="_blank"></a></pre></font></span><br>_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>