On Tue, Mar 8, 2011 at 12:12 AM, Mircea Carasel <[email protected]> wrote:
> Hi, > > I am thinking to find a way to get all ongoing calls (CDRs in progress) > creating a REST service > > Given my research on CDRs and call events I found that there are two > processes involved in this: > > 1. sipXproxy - that is responsible with getting call events and saves then > in call_state_events table > 2. sipXcallresolver that agregates all records from all call_state_events > table from all hosts where sipXproxy is running > SipXcallresolver (the CDR service) runs only on primary, being part of the > management role and resolves all call_state_events into CDRs and saves them > into SIPXCDR database on master, in cdrs table > > Looking into master's cdrs table I find only ended calls... In order to get > the ongoing calls (CDRs that are in progress) there is a SOAP service that > sipXconfig calls and it is > situated in sipXcallresolver written in Ruby on Rails > > My question is if all call events from all proxy hosts are by any chance > agregated/saved in a call_state_events table situated on master. > This scenario applies in a HA environment, where proxy may run only on secondary. I cannot create HA here and therefore cannot figure this out > If the answer is yes, it would be simple for my to create a REST service > that simply reads from this table > If the answer is no, I would need to create a Ruby Rest service in > sipxcallresolver next to the soap service. The bad news is I didn't find > concludent information on > how to build such service in Ruby > > Any feedback is really appreciated > > Thanks, > Mircea > > >
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
