<div dir="ltr"><div>Hello Bogdan,<br><br>Thanks for your reply! We are using opensips 1.8.0-notls (x86_64/linux).<br><br></div>We do not think this issue is load related but perhaps older registrations have not yet expired. We will try setting the min_expires parameter to a low number to test this hypothesis; any other approaches we could try? <br>
<br>Thanks once again!<br><br>James<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 16, 2013 at 1:53 AM, Bogdan-Andrei Iancu <span dir="ltr"><<a 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"><u></u>
<div text="#000000" bgcolor="#ffffff">
<tt>Hello James,<br>
<br>
No, there is no such known bug or issue. What I suspect is that
there are short intervals (milisecs) where an AOR is not
registered - this may happen because :<br>
- the test tool is not performing properly under high load and
fails to do re-register before old registration expires.<br>
- OpenSIPS is overloaded (too few processes ?) and it is not
able to process traffic in realtime (check the LOAD related
statistics).<br>
<br>
What OpenSIPs versions are you using ?<br>
<br>
Regards,<br>
</tt>
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre><div><div class="h5">
<br>
On 05/15/2013 01:56 AM, James Tranovich wrote:
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">
<div>
<div>
<div>Hello all --<br>
<br>
</div>
First, we love opensips :)<br>
<br>
Lately, we have been running into a strange issue which
seems to be related to handling a ton of REGISTER messages.
Basically, we have a test script that tries to simulate
about 50 to 100 simultaneous calls; they all register en
masse and then randomly start placing calls to another test
number (after a random time interval). Every once in a
while, though, an INVITE won't go through because opensips
apparently can't find that phone number. Oddly enough, if we
do an "opensipsctl online" immediately before/after, that
command shows that, in fact, the recipient's number is
present and presumably already registered. SIP logs/ngrep
tracing confirm this.<br>
<br>
</div>
I was wondering if this is a known bug. This behavior only
happens when registering a certain number of calls at once; if
we test with a low number of calls (10, say), this behavior
does not happen. It may be that we are spamming opensips with
too many REGISTER messages (authentication is required, so two
REGISTER messages are sent, the first w/o auth, the second
with auth). But I don't see why opensips should have problems
with this.<br>
<br>
</div>
Any thoughts on this? Is this a known issue already? (Searching
for this issue didn't yield much). Thanks!<br>
<div><br>
James<br>
</div>
</div>
</div></div><pre><fieldset></fieldset>
_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
</div>
</blockquote></div><br></div>