<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix"><tt>Hi,<br>
<br>
SIP registration has nothing to do with SIP presence. There are
totally individual mechanisms in SIP.<br>
<br>
In presence, when a device starts publishing for the first time,
it gets an etag (a unique id) that will identify the
device+publisher.<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
On 10.10.2014 04:46, Yuming Zheng wrote:<br>
</div>
<blockquote
cite="mid:CAJ5nD-a4UEp378tB35R-SAahMWc_uxMub58qnLziEgntJTJ3Dg@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div>Yes ,<font face="monospace"><span
style="font-size:11.818181991577148px">GRUU can solve this
situation.</span></font></div>
<div><font face="monospace"><span
style="font-size:11.818181991577148px">So, is there any
similar mechanism with presence info to only keep the
latest presence status of the same register.</span></font></div>
<div><font face="monospace"><span
style="font-size:11.818181991577148px"><br>
</span></font></div>
<div><font face="monospace"><span
style="font-size:11.818181991577148px">BR,</span></font></div>
<div><font face="monospace"><span
style="font-size:11.818181991577148px"><br>
</span></font></div>
<div><font face="monospace"><span
style="font-size:11.818181991577148px">Frank.zheng</span></font></div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2014-10-09 18:32 GMT+08:00
Bogdan-Andrei Iancu <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:bogdan@opensips.org"
target="_blank">bogdan@opensips.org</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div><tt>Hi Jayesh,<br>
<br>
Maybe you should look into GRUU stuff ;).<br>
<br>
On the TCP error - even if you set the TCP persistence
flag, the UAC may close the TCP conn -> you end up
in the same situation. What you can do is to prevent
OpenSIPS to open TCP conns when routing to end-users -
the idea is to have end-users connecting to OpenSIPS
and not the other way around. See
"tcp_no_new_conn_bflag" :<br>
<a moz-do-not-send="true"
href="http://www.opensips.org/Documentation/Script-CoreParameters-1-11#toc96"
target="_blank">http://www.opensips.org/Documentation/Script-CoreParameters-1-11#toc96</a><br>
<br>
Regards,<br>
</tt><span class="">
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
</span>
<div>
<div class="h5"> On 08.10.2014 17:31, Jayesh Nambiar
wrote:<br>
</div>
</div>
</div>
<div>
<div class="h5">
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>Hi Bogdan,<br>
</div>
So I thought of doing this and I have another
problem. Say if a device registered from IP
1.2.3.4, and then moved out to different
network and re-registered from IP 4.3.2.1,
there is a stale registration lying in
opensips for the same device from 1.2.3.4.<br>
</div>
Now when I use TCP as transport, opensips waits
till connect timed out on unreachable IPs before
sending the call to registered contact and the
following messages are logged in syslog:<br>
ERROR:core:tcp_blocking_connect: timeout 10 s
elapsed from 10 s<br>
ERROR:core:tcpconn_connect:
tcp_blocking_connect failed<br>
ERROR:core:tcp_send: connect failed<br>
ERROR:tm:msg_send: tcp_send failed<br>
<br>
</div>
<div>Looks like opensips tries to do a TCP connect
first with all registered contacts before
actually routing the call.<br>
</div>
<div>I do,<br>
modparam("registrar", "tcp_persistent_flag",
"TCP_PERSISTENT")<br>
<br>
if(is_method("REGISTER")) {<br>
setflag(TCP_PERSISTENT);<br>
setbflag(30);<br>
if(!save("location", "fc1")) {<br>
t_reply("500", "Error while
saving AOR");<br>
}<br>
}<br>
<br>
</div>
<div>--- Jayesh<br>
</div>
<div><br>
<br>
<br>
</div>
<div><br>
</div>
<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Oct 8, 2014 at
3:10 PM, Bogdan-Andrei Iancu <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:bogdan@opensips.org"
target="_blank">bogdan@opensips.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div><tt>Hi Jayesh,<br>
<br>
Basically you do not what to have more
registrations from the same IP, right ?<br>
<br>
Exactly the opposit of the
is_other_contact() function :<br>
<a moz-do-not-send="true"
href="http://www.opensips.org/html/docs/modules/1.11.x/registrar.html#id294660"
target="_blank">http://www.opensips.org/html/docs/modules/1.11.x/registrar.html#id294660</a><br>
<br>
Regards,<br>
</tt>
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
<div>
<div> On 01.10.2014 18:15, Jayesh
Nambiar wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>Hi,<br>
</div>
I am trying to solve a
problem of having one
registration per AOR per
device. So user 1234 can
register from device A,
device B and device C. But
the user 1234 should not
have multiple contacts from
device A alone. <br>
</div>
At times when the device loses
network, proxy doesn't receive
de-register and the contact
stays in opensips till its
expiry time. So the same
device is thus capable of
creating multiple contacts. I
could solve this by using
"fc1" flag while doing a
save("location") but I need
multiple registrations to be
allowed from different devices
!!<br>
</div>
So is there a way where while
doing a save("location"), I set
some sort of device id along
with it such that I identify and
overwrite the existing contact
only if the registration comes
from same device-id or else add
it up for parallel forking.<br>
</div>
Do let me know if I make sense
here and there's a solution to
this. Thanks for any suggestions
and directions.<br>
<br>
Thanks,<br>
<br>
</div>
--- Jayesh<br>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<pre>_______________________________________________
Users mailing list
<a moz-do-not-send="true" href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a moz-do-not-send="true" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a moz-do-not-send="true"
href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>