<div>
Thanks so much for the feedback guys,
</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>I was under the impression that kamailio didn't record any dialog accounting into the database unless you turn the flag on and take a rather large performance hit on the proxy side. Since I only want to check if a user is on the line in rare circumstances, I opted to use the in memory rpc call.</div><div><br></div><div>Awesome to hear about the XMLDispatcher routing, that's great that it will work out of the box in the PRO solution :) </div><div><div>-- </div><div>Matt Van Veenendaal</div><div><br></div></div>
<p style="color: #A0A0A8;">On Thursday, October 11, 2012 at 3:00 AM, Klaus Peter v. Friedeburg wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>Hi Andreas,</div><div><br></div><div>ok I think we have different approaches to the database. My solution is to build up a MySQL Cluster ore using tungsten-replicator for Multi-Master Replication for all proxy-nodes so that all nodes of the ng Cluster works with the same database tables. We have do this so that we can update a proxy-node ore restart the kamailio-service without any outage.</div><div>We use an other usrloc module which support the use of the same table in all of the proxy-nodes without any datacollision. </div><div>The advantage of using a database-query is, that you see "broken" calls where the second acc-record (stop) is missing. In some circumstances we see that some Bye-Messages are not probably handled so that "broken" accounting entrys exist.</div><div><br></div><div>But I will take a look in the XMLDispatcher Doku so my solution need some optimization :-)</div><div><br></div><div>Klaus Peter</div><div><br></div><blockquote type="cite"><div><div>-----Ursprüngliche Nachricht-----</div><div>Von: spce-user-bounces@lists.sipwise.com [<a href="mailto:spce-user-bounces@lists.sipwise.com">mailto:spce-user-bounces@lists.sipwise.com</a>] Im Auftrag von</div><div>Andreas Granig</div><div>Gesendet: Donnerstag, 11. Oktober 2012 11:35</div><div>An: <a href="mailto:spce-user@lists.sipwise.com">spce-user@lists.sipwise.com</a></div><div>Betreff: Re: [Spce-user] API for getting current calls status?</div><div><br></div><div>Hi,</div><div><br></div><div>On 10/11/2012 11:09 AM, Klaus Peter v. Friedeburg wrote:</div><blockquote type="cite"><div><div>when I see it right you get the data form kamailio FIFO via kamctrl. But</div><div>what happens when using more than one proxy for load balancing and</div><div>rendundancing?</div></div></blockquote><div><br></div><div>This is not exactly a valid point for a stock CE, but see my comments below:</div><div><br></div><blockquote type="cite"><div><div>I think the only right way is to get the information from the database</div><div>where active calls are logged (kamailio.acc).</div><div><br></div><div>My solution is to take a look on kamailio.acc for active calls.</div></div></blockquote><div><br></div><div>You'd still need to query all your kamailio.acc tables, like you'd need</div><div>to do with XMLDispatcher, however XMLDispatcher - beside other things</div><div>like sync/async requests - already supports querying more than one proxy</div><div>(the "dispatch" function in XMLDispatcher.pm has a detailed</div><div>documentation on that).</div><div><br></div><div>So Matt's approach is the more elegant one from my point of view,</div><div>because it allows easy expansion to query more than one proxy.</div><div><br></div><div>For our up-scaled carrier solutions, which transparently supports</div><div>multiple pairs of PROs, we've a dedicated provisioning middleware which</div><div>routes API calls to the pair which serves the user, so in this case</div><div>Matt's approach would work out of the box as well, because in this case</div><div>the serving node has only one proxy running (like a CE in active/standby</div><div>mode).</div><div><br></div><div>The good thing about open source though is that everyone can do it the</div><div>way it suits him best :)</div><div><br></div><div>Andreas</div></div></blockquote><div><br></div><div><br></div><div>_______________________________________________</div><div>Spce-user mailing list</div><div><a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a></div><div><a href="http://lists.sipwise.com/listinfo/spce-user">http://lists.sipwise.com/listinfo/spce-user</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>