<div dir="ltr">This makes *a lot* of sense. Thanks!I expected the SIP REGISTER to be terminated at the instance rather than forwarded as I had that user/pw combo in the subscribers table. I assume it doesn't do that by default I have to add a command to the routing logic to do that? Or, architecturally, should I just forward that request anyhow?<div>
<br></div><div>Thanks!</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 15, 2014 at 2:11 AM, Brett Nemeroff <span dir="ltr"><<a href="mailto:brett@nemeroff.com" target="_blank">brett@nemeroff.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">Normally this means that you haven't actually done anything with the call, but you are t_relaying it out.<div>
<br></div><div>In other words, the RURI was destined for your opensips box.. That's how it got there.. it hit opensips, then you sent it back out.. But you never adjusted the RURI to point to the next hop by either changing the request user part or domain part. So it sends it back to itself (loopback) until Max-Forwards expires and returns the 483.</div>
<div><br></div><div>If you remove the 483 check, you get a massive loop on the loopback interface until you start to kill server resources, which gave you the 408.</div><div><br></div><div>Be sure you are actually doing some change to the message before you send it back out. Try to xlog the r-uri before you t_relay() like this:</div>
<div><br></div><div>xlog("L_INFO","Sending call out to $ru");</div><div><br></div><div>If you watch sip traffic on your loopback interface, you'll see what all the madness is about.. I don't really recommend it, since it very quickly will consume your terminal, but you'll at least understand what exactly is happening..</div>
<div><br></div><div>Good luck!</div><div>-Brett</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Wed, May 14, 2014 at 8:36 PM, Kurtis Heimerl <span dir="ltr"><<a href="mailto:kheimerl@endaga.com" target="_blank">kheimerl@endaga.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><span style="font-family:arial,sans-serif;font-size:17px">Hey Users,</span><div style="font-family:arial,sans-serif;font-size:17px">
<br></div><div style="font-family:arial,sans-serif;font-size:17px">I'm a developer with a lot of experience in FreeSWITCH trying out OpenSIPS for a larger, more central piece of infrastructure. I started investigating it a few days ago with the following use case in mind:</div>
<div style="font-family:arial,sans-serif;font-size:17px"><br></div><div style="font-family:arial,sans-serif;font-size:17px">FS instance with users attached.</div><div style="font-family:arial,sans-serif;font-size:17px">OpenSIPS in the cloud routing the FS communications to another cloud provider (e.g., Twilio). </div>
<div style="font-family:arial,sans-serif;font-size:17px"><br></div><div style="font-family:arial,sans-serif;font-size:17px">I've got FS set up with our OpenSIPS box as an external provider and a set username and password. That seems to be working. I set up OpenSIPS from the opensips APT repository (<a href="http://apt.opensips.org/" target="_blank">http://apt.opensips.org/</a>) and version 11.1. It's running, configured with TEXTDB, and I inserted the username and password (after modifying the DB schema to allow null emails, which I guess is an ancient bug... <a href="http://sourceforge.net/p/openser/bugs/593/" target="_blank">http://sourceforge.net/p/openser/bugs/593/</a>). </div>
<div style="font-family:arial,sans-serif;font-size:17px"><br></div><div style="font-family:arial,sans-serif;font-size:17px">The registration from FS is being rejected as a 483 "Too many hops" This is strange. I removed the 483 check in the opensips cfg and now it's a 408 Timeout. OpenSIPS itself it complaining in the following way. The actual log is also available, but too large for the mailing list. </div>
<div style="font-family:arial,sans-serif;font-size:17px"><br></div><div style="font-family:arial,sans-serif;font-size:17px"><div>May 15 01:27:34 [26230] WARNING:core:fm_malloc: Not enough free memory, will atempt defragmentation</div>
<div>May 15 01:27:34 [26230] ERROR:tm:relay_reply: no more share memory</div><div>May 15 01:27:34 [26230] WARNING:core:fm_malloc: Not enough free memory, will atempt defragmentation</div><div>May 15 01:27:34 [26230] ERROR:tm:_reply_light: failed to allocate shmem buffer</div>
</div><div style="font-family:arial,sans-serif;font-size:17px"><br></div><div style="font-family:arial,sans-serif;font-size:17px">Googling this error brings up a few hits on issues with a memory leak, but that can't be the case here as it is just started. </div>
<div style="font-family:arial,sans-serif;font-size:17px"><br></div><div style="font-family:arial,sans-serif;font-size:17px">Ideas? What am I doing wrong? Is this is right use case for OpenSIPS anyhow?</div><div style="font-family:arial,sans-serif;font-size:17px">
<br></div><div style="font-family:arial,sans-serif;font-size:17px">Thanks!</div></div>
<br></div></div>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>