<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hello,</p>
<p>using kamailio as a front end proxy in front of a freeswitch farm
is a common scenario. Look at dispatcher module if you want to
implement a load balancer.</p>
<p>Using a redis server can be an option as well, ndb_redis module
in kamailio can be used for that.</p>
<p>Cheers,<br>
Daniel<br>
</p>
<br>
<div class="moz-cite-prefix">On 08/06/16 20:26, Colin Morelli wrote:<br>
</div>
<blockquote
cite="mid:CAPtU-Uqp24YTpo__4j7q=HFZgFLXjrgS=fqo3cwhiLqZFyATbA@mail.gmail.com"
type="cite">
<div dir="ltr">Hello,
<div><br>
</div>
<div>I currently have Freeswitch acting as a B2BUA, handling
registrations, routing, etc for a prototype voice application
I have built.</div>
<div><br>
</div>
<div>Now I'm at the point where it's time to actually scale it
out, and I'm looking at a few different options for the SIP
proxy + registration later. Essentially, what I would like to
have (I think), is:</div>
<div><br>
</div>
<div>1) Stateless SIP proxy with consistent hashing to route to:</div>
<div>2) Transaction-stateful SIP proxy handling registrations
and initial routing</div>
<div><br>
</div>
<div>Ideally, the only thing that's stored across the cluster
(if possible) would be registrations, in something like
memcache/redis. Then, of course, each node might have its own
internal state of transactions that it's tracking. I'd prefer
the only thing to care about dialog state to be Freeswitch.</div>
<div><br>
</div>
<div>Finally, the decisions about which FS instance to route to
would be made by my application as well, based on runtime
rules.</div>
<div><br>
</div>
<div>Is this something people here have done before? Are there
other suggestions on how to scale out kamailio to multiple
instances.</div>
<div><br>
</div>
<div>Thanks in advance,</div>
<div>Colin</div>
</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://www.asipto.com">http://www.asipto.com</a> - <a class="moz-txt-link-freetext" href="http://www.kamailio.org">http://www.kamailio.org</a>
<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></pre>
</body>
</html>