No subject


Wed Jan 27 21:05:54 CET 2016


Unplug Internet connection from registered endpoint.

Opensips send sipping. Received "Destination unreachable (Port
unreachable)".

Record in location table is not deleted.

Where is problem?

Regards,
Dragomir


2015-10-01 11:33 GMT+03:00 Ionut Ionita <ionutionita at opensips.org>:

> *Hello all,
>
>     I=E2=80=99m glad to announce a new feature that allows OpenSIPS to mo=
nitor
> (via SIP OPTIONS probing) and disable/delete in realtime the registration=
s
> which are not responding.
>     The previous approach had two issues when came to so called =E2=80=9C=
zombie=E2=80=9D
> registrations (registrations which are not valid anymore):
>     * resources - such zombie registrations may waste resources in your
> OpenSIPS server (memory,  processing time, DB space, useless NAT pinging,
> TCP connect attempts);
>     * user experience - using the zombie registration to reach un-existin=
g
> users translates into useless calls (calls that will simply timeout),
> giving delays in the call setup (instead of going straight to VM, you may
> burn 5-10 seconds in trying to reach the user);
>     The main idea  behind these features is to delete contacts that do no=
t
> respond to a certain number of SIP pings. The SIP pinging is provided by
> the
> nathelper module which was enhanced to keep the state of each pinging
> requests
> (basically, the module is waiting and checking the reply of each SIP
> request
> sent to the registered users). For registrations detected as =E2=80=9Cdea=
d=E2=80=9D (not
> responding),
> the nathelper module interacts directly with the usrloc module in order t=
o
> remove the zombie contact.
>     For usage perspective, the nathelper module now has two new parameter=
s:
>     * ping_threshold - timeout to consider a ping as unanswered;
>     * max_pings_lost - the number of unresponded pings after which the
> contact is
> removed from usrloc;
>     In order to activate this feature, every contact must have the
> sipping_bflag
> (to be pinged) and remove_on_timeout_bflag (to be deleted on no-answer)
> activated.
> This means these flags must also be configured in the nathelper module. [=
0]
>     For full documentation of the nathelper module including the newly
> added
> feature see [1]. Any feedback is highly appreciated.
>
> Regards,
> Ionut Ionita
>
> [0]http://www.opensips.org/html/docs/modules/2.2.x/nathelper.html#id24801=
1
> [1]http://www.opensips.org/html/docs/modules/2.2.x/nathelper.html
> *
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

--001a11c3c7c80576b4052bf6c64d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div><br><div>I try to setup realtime monitoring.=C2=
=A0</div><div>Here is part of my script:<br><br><div>loadmodule &quot;nathe=
lper.so&quot;</div><div>modparam(&quot;nathelper&quot;, &quot;remove_on_tim=
eout_bflag&quot;, &quot;RM_ONTO_FLAG&quot;)=C2=A0</div><div>modparam(&quot;=
nathelper&quot;, &quot;ping_threshold&quot;, 5)=C2=A0</div></div><div>.....=
..</div><div><br></div><div>route {</div><div>.........</div><div>setbflag(=
RM_ONTO_FLAG);<br></div><div>.........</div><div>}</div><div><br></div><div=
>From location tableI (cflags) I see =C2=A0&quot;RM_ONTO_FLAG&quot;</div><d=
iv>Unplug Internet connection from registered endpoint.<br><br>Opensips sen=
d sipping. Received &quot;Destination unreachable (Port unreachable)&quot;.=
<br><br>Record in location table is not deleted.<br><br>Where is problem?</=
div><div><br></div><div>Regards,</div><div>Dragomir<br><br></div></div></di=
v><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">2015-10-01 11:3=
3 GMT+03:00 Ionut Ionita <span dir=3D"ltr">&lt;<a href=3D"mailto:ionutionit=
a at opensips.org" target=3D"_blank">ionutionita at opensips.org</a>&gt;</span>:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">*Hello all,<br>
<br>
=C2=A0 =C2=A0 I=E2=80=99m glad to announce a new feature that allows OpenSI=
PS to monitor<br>
(via SIP OPTIONS probing) and disable/delete in realtime the registrations<=
br>
which are not responding.<br>
=C2=A0 =C2=A0 The previous approach had two issues when came to so called =
=E2=80=9Czombie=E2=80=9D<br>
registrations (registrations which are not valid anymore):<br>
=C2=A0 =C2=A0 * resources - such zombie registrations may waste resources i=
n your<br>
OpenSIPS server (memory,=C2=A0 processing time, DB space, useless NAT pingi=
ng,<br>
TCP connect attempts);<br>
=C2=A0 =C2=A0 * user experience - using the zombie registration to reach un=
-existing<br>
users translates into useless calls (calls that will simply timeout),<br>
giving delays in the call setup (instead of going straight to VM, you may<b=
r>
burn 5-10 seconds in trying to reach the user);<br>
=C2=A0 =C2=A0 The main idea=C2=A0 behind these features is to delete contac=
ts that do not<br>
respond to a certain number of SIP pings. The SIP pinging is provided by th=
e<br>
nathelper module which was enhanced to keep the state of each pinging reque=
sts<br>
(basically, the module is waiting and checking the reply of each SIP reques=
t<br>
sent to the registered users). For registrations detected as =E2=80=9Cdead=
=E2=80=9D (not responding),<br>
the nathelper module interacts directly with the usrloc module in order to<=
br>
remove the zombie contact.<br>
=C2=A0 =C2=A0 For usage perspective, the nathelper module now has two new p=
arameters:<br>
=C2=A0 =C2=A0 * ping_threshold - timeout to consider a ping as unanswered;<=
br>
=C2=A0 =C2=A0 * max_pings_lost - the number of unresponded pings after whic=
h the contact is<br>
removed from usrloc;<br>
=C2=A0 =C2=A0 In order to activate this feature, every contact must have th=
e sipping_bflag<br>
(to be pinged) and remove_on_timeout_bflag (to be deleted on no-answer) act=
ivated.<br>
This means these flags must also be configured in the nathelper module. [0]=
<br>
=C2=A0 =C2=A0 For full documentation of the nathelper module including the =
newly added<br>
feature see [1]. Any feedback is highly appreciated.<br>
<br>
Regards,<br>
Ionut Ionita<br>
<br>
[0]<a href=3D"http://www.opensips.org/html/docs/modules/2.2.x/nathelper.htm=
l#id248011" rel=3D"noreferrer" target=3D"_blank">http://www.opensips.org/ht=
ml/docs/modules/2.2.x/nathelper.html#id248011</a><br>
[1]<a href=3D"http://www.opensips.org/html/docs/modules/2.2.x/nathelper.htm=
l" rel=3D"noreferrer" target=3D"_blank">http://www.opensips.org/html/docs/m=
odules/2.2.x/nathelper.html</a><br>
*<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href=3D"mailto:Users at lists.opensips.org" target=3D"_blank">Users at lists.o=
pensips.org</a><br>
<a href=3D"http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel=3D=
"noreferrer" target=3D"_blank">http://lists.opensips.org/cgi-bin/mailman/li=
stinfo/users</a><br>
</blockquote></div><br></div>

--001a11c3c7c80576b4052bf6c64d--



More information about the Users mailing list