<div dir="ltr"><div>Hi Daniel,</div><div><br></div><div>Thanks for the response. </div><div><br></div><div>We are not using the pike module. </div><div><br></div><div>The requests to a port are not dismissed; rather, in most cases, there is a delay in response from kamailio. Also, the delay is not restricted to any particular message request. it happens for any type of request. (register; subscribe; etc...).</div><div><br></div><div>But those same requests, if pointed to different port, have no issues.</div><div><br></div><div>Also, to note, I am not restarting kamailio when the issue occurs on a particular port. kamailio is kept running and pointing traffic to a non-problematic port seems fine.</div><div><br></div><div>Karthik</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 11, 2015 at 12:41 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 text="#000000" bgcolor="#FFFFFF">
Hello,<br>
<br>
do you have pike module loaded and enabled?<br>
<br>
Are all requests to a port dismissed or just some of them?<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div>On 11/05/15 19:20, Karthik Srinivasan
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi,</div>
<div><br>
</div>
<div>I have encountered an issue with kamailio and am hoping
someone on this email distro can help:</div>
<div><br>
</div>
<div>Here's my setup and description of the issue:</div>
<div><br>
</div>
<div>I am running kamailio version 3.1.4. </div>
<div><br>
</div>
<div>I have the kamailio process bound to ports 5060, 5070, and
5090. all UDP.</div>
<div><br>
</div>
<div>I have several client devices registering to the kamailio
registrar.</div>
<div><br>
</div>
<div>The issue I have encountered is this:</div>
<div><br>
</div>
<div>SIP registrations to port 5070 are fine for a period of
time; by fine I mean clients send SIP registration requests
to kamailio; and kamailio responds promptly to the request.
by period of time I mean (this could be somewhat random)
that for10 hours; 12 hours; 1 hour; that kamailo has no
issue processing requests. after this random time period
has elapsed, kamailo isn't able to respond to sip
registrations and other messages in timely manner; to the
point where the clients timeout and have to resend their
registration requests. at times, kamailio does respond to the
requests (with a significant delay) and at other times no
response is received by the client. the user experience is
intermittent registration delays/failures.</div>
<div><br>
</div>
<div>The same behavior is seen on port 5090.</div>
<div><br>
</div>
<div>I have not encountered the issue yet on port 5060.</div>
<div><br>
</div>
<div>During times when kamailio isn't able to respond timely to
requests on a particular port, requests to other ports are
responded to timely.</div>
<div><br>
</div>
<div>for ex: if port 5070 encounters the issue; port 5060 and
5090 seem fine. meaning, I can point my client devices to
5060 or 5090 and kamailio processes the requests timely.</div>
<div><br>
</div>
<div>I have studied a tcp dump on the server end (kamailio side)
and noticed that the network layer shows the messages from the
client to be received timely while kamailio is encountering
this issue. which indicates to me that it probably isn't a
network lag related issue. </div>
<div><br>
</div>
<div>Something at the application layer is probably causing
kamailio to not respond timely.</div>
<div><br>
</div>
<div>Furthermore the issue resolves itself after a period of
time; that is, kamailio begins to respond to messages timely
on the problematic port.</div>
<div>I haven't had a chance yet to determine exactly how long it
takes to recover. it certainly takes some time though. at
least 30 minutes; maybe more. </div>
<div><br>
</div>
<div>I can also state that the load on the kamailio system is
minimal. far below than what the performance metrics state it
can handle.</div>
<div><br>
</div>
<div>Has anyone encountered this issue where kamalio isn't
responding to registration and other requests timely on a
particular port but does so fine for other ports?</div>
<div><br>
</div>
<div>Any help on this would be appreciated.</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Karthik</div>
<div><br>
</div>
<div><br>
</div>
<div> </div>
<div><br>
</div>
<div><br>
</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 class="HOEnZb"><font color="#888888">
</font></span></pre><span class="HOEnZb"><font color="#888888">
</font></span></blockquote><span class="HOEnZb"><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>
Kamailio World Conference, May 27-29, 2015
Berlin, Germany - <a href="http://www.kamailioworld.com" target="_blank">http://www.kamailioworld.com</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">sr-users@lists.sip-router.org</a><br>
<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><br>
<br></blockquote></div><br></div>