<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
first, not related to the topic you reported, I would recommend at
least upgrading to latest 4.0.x, there were many fixes from v4.0.0
and there are no changes to be done to config or database -- simply
deploy latest 4.0.x and restart.<br>
<br>
Back to this topic. Is all the other traffic handled apart of big
OPTIONS?<br>
<br>
Do you have pike module enabled? If yes, can you double check and be
sure that the SBC is not blacklisted (traffic from it should not be
handled via pike_check_req()).<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 01/04/15 15:42, Yufei Tao wrote:<br>
</div>
<blockquote
cite="mid:CAJwP0iR0M-o=boErEbxXCnGJu9P8_XNC5S8CqUe7CO4QdNWs1A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>Hi<br>
<br>
</div>
We've got Kamailio (v4.0.0) connected to some SBC, which
sends SIP traffic and periodic OPTIONS pings to
Kamailio's VIP. Kamailio responds to the OPTIONS pings
with OK, i.e. in the main route block:<br>
if (is_method("OPTIONS")) <br>
{<br>
sl_send_reply("200","OK");<br>
exit;<br>
}<br>
<br>
</div>
All works fine for a week or so, then Kamailio stopped
responding to the OPTIONS pings on the VIP it listens to.
But it still respond to OPTIONS pings that are sent to its
real IP. The real IP is not used for receiving/sending any
traffic while only the VIP is. So it seems that Kamailio
is still working, but maybe having problems with the
receiving buffer for the VIP?<br>
<br>
</div>
We do see that some SIP messages sent to Kamailio's VIP are
too big (sometimes over 1500 bytes). My question is, in this
case, what would be expected to happen? Is it possible
somehow the receiving buffer for the VIP got messed up by
the big UDP messages? Any one seen similar problems? What is
the suggested solution?<br>
<br>
</div>
<div>We're considering moving to TCP. But since this is
production environment, I want to get some confidence that
the problem we saw was likely to have been caused by the UDP
message being too large.<br>
</div>
<div><br>
</div>
Cheers,<br>
</div>
Yufei<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a>
Kamailio World Conference, May 27-29, 2015
Berlin, Germany - <a class="moz-txt-link-freetext" href="http://www.kamailioworld.com">http://www.kamailioworld.com</a></pre>
</body>
</html>