<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Jorge,<br>
<br>
If these keep-alives are SIP requests, you need to answer, otherwise
the sender will do retransmission :)<br>
<br>
So, in the beginning of the script, you can do:<br>
if (is_method("OPTIONS") && uri==myself &&
$rU==NULL) { send_reply("200","ok");exit;}<br>
<br>
That means -> if you get an OPTIONS with the IP of your server in
RURI and without username part -> it is a ping<br>
<br>
<br>
Regards,<br>
Bogdan<br>
<br>
On 03/01/2012 01:56 PM, Jorge Ortea wrote:
<blockquote cite="mid:DUB111-W88D7081E08099F8CA0E776DC6C0@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
<div dir="ltr">
Hi,<br>
<br>
my question is how manage the keep-alives messages ??<br>
<br>
I understand that the keep-alives only serve to keep open NAT. <br>
<br>
Now, to avoid manage this messages in my routing logic, i am
discarding this messages, is this correct? or i should respond.<br>
<br>
I too have detected that when my cisco telephones don't receive
response they keep sending keep-alives.<br>
<br>
Thanks.<br>
Regards.<br>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
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>
<br>
<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>
</body>
</html>