<div dir="ltr">This might sound like a lazy answer, but will help in the long term.. <div><br></div><div>I'd suggest learning about SIP as a protocol before you do anything else. </div><div><br></div><div>You'll find learning the protocol itself inherently dictates how to scales across multiple servers. For example, in defining what the role of a Registrar is, SIP explains that a single 'server/process' can handle that job independently of any other SIP related activity. It likewise discusses that what a SBC is, and thereby helps understand that you can seperate the handling of SIP and RTP to a proxy and media server.</div><div><br></div><div>Once you understand SIP properly, it's easy to come in and say "Well I need a registrar.. that's OpenSIPS or Kamailio.. Now I need a server to handle Media.. well FreeSWITCH does that.. I need a server to handle presence.. well presence can utilise dialog info to produce this I might as well use OpenSIPS or Kamailio". </div><div><div><br></div><div>If you do implement it using Kazoo, using a guide, or whatever, you'll find yourself learning about SIP anyway. Why don't you just attack it head on, and you'll understand it all a bit better?</div><div><br></div><div>The latest OpenSIPS book has a good chapter on SIP I think is worth the read.</div></div><div><br></div><div>I think this is why a lot of people are responding with 'it depends'. What they really mean is, "SIP is a flexible protocol, and it's really your choice in how you want to implement its various components".</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 18, 2016 at 2:04 PM, Sergey Safarov <span dir="ltr"><<a href="mailto:s.safarov@gmail.com" target="_blank">s.safarov@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 dir="ltr">Luis with all due respect to you and your work still...<div><br></div><div><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>as i said it depends on how you use it. it doesn't make sense to call the api to fetch a list of 200.000 devices or callflows. use v2 for paging and/or use the search api.</div></div></blockquote><div><br></div></span><div>If you look at <a href="https://2600hz.atlassian.net/browse/KAZOO-4326" target="_blank">KAZOO-4326</a> one more time, you can see that I stores one callflow via kazoo API. For database containing about 20 000 callflows 30 sec to save one callflow is much. Think saving 200 000 callflows via kazoo API took about 1-2 months.</div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div></div><div>also, the question was about same realm not same account. you can have a common realm for many accounts.</div></div></blockquote><div><br></div></span><div>I has tried assign same realm to two accounds but get error.</div><span class=""><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>finally, as with any other software, kazoo does is not "completed" and there are optimizations tat can be done.</div></div></blockquote><div><br></div></span><div>I completely agree with you. Moreover, I believe that what I have described would not require major change in the kazoo. And soon kazoo can be successfully used for the described case.<br></div><div><br></div></div></div></div>
<br>_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" rel="noreferrer" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" rel="noreferrer" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://confluence.freeswitch.org" rel="noreferrer" target="_blank">http://confluence.freeswitch.org</a><br>
<a href="http://www.cluecon.com" rel="noreferrer" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" rel="noreferrer" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" rel="noreferrer" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" rel="noreferrer" target="_blank">http://www.freeswitch.org</a><br></blockquote></div><br></div>