<div dir="ltr"><div>Addendum: we have a detailed log here:<br><br><a href="https://gist.github.com/captdeaf/5580914">https://gist.github.com/captdeaf/5580914</a><br><br></div>Thanks!<br><br>James<br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, May 14, 2013 at 3:56 PM, James Tranovich <span dir="ltr"><<a href="mailto:james@openhorizonlabs.com" target="_blank">james@openhorizonlabs.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<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!<span class="HOEnZb"><font color="#888888"><br><div><br>James<br></div></font></span></div>
</blockquote></div><br></div>