Ongoing calls would be monitored at the proxy OR the gateway. The gateway might be more problematic, because that means the SNMP strings for the gateway have to support active calls. At the same time, it's not a bad idea to put an SNMP monitor on the gateway though.
The proxy initiates the call and then "takes itself out of the lopp" on the call until it see they bye, at which point it cuts the CDR record to historic. I don't think anyone has written an easy was for something to see the active calls at the proxy level (yet). That, along with a way to "kill" specific calls at the proxy is something that should be a good improvement to raise and see how feasible it is to write that into the system. FWIW - I use Groundwork open source (nagios inside a useable interface). The latest release (this week): http://www.groundworkopensource.com/products/whats-new-6.2.html <http://www.groundworkopensource.com/products/whats-new-6.2.html>A new Java monitoring agent provides deep insight into Java application servers and containers. The new agent provides performance monitoring for any MBean exposed by Java applications including JDBC performance, cache hit-rates and transaction rates. Release 6.2 includes pre-built profiles for JBoss, Tomcat and IBM Websphere. My question is, is there any interest in monitoring JAVA on sipxecs? I seem to think it's a good idea, but would like input. On Thu, Jul 15, 2010 at 8:33 AM, <[email protected]> wrote: > Hello everybody, > > my Name is Steven. I'm from germany and I am working on seminar paper about > Nagios-plugin for sipX. > Nagios is an OpenSource monitoring software. http://www.nagios.org/ > Nagios is used with plugins, that monitor particular propertys of a System. > It also can create automated warnings (per SMS, mail, pager, ...) or trigger > scripts. And a lots more. > > I have to write some Plugins that monitor: > - registered useres > - ongoing calls and where they go to (trunk1, trunk2, internal, ...) > - traffic used by all the calls together > > I have already spend quite a lot of time to analyse sipx. In the meantime I > got a realy nice way to monitor the registered users. There is a file called > "registration.xml" in /var/sipxdata/sipdb/ It provides all the information I > needed to write the plugin. :-) > > But now I want to write the pluins to monitor ongoing calls and where they > go to. I couln't find any "information interface" to get this information > from. > I know that this information has to be somewhere, because I can see it in > the adminportal in "Diagnostics -> Call Detail Records -> Active". I know > that there is a PostgreSQL-database that contains some information about the > cdr. But I don't think that's the nice way to gather that information. > > Any ideas how to find out about: > - ongoing calls and where they go to (trunk1, trunk2, internal, ...) > - traffic used by all the calls together > > > Thank you and greetings from germany, > Steven > > > > > > ********************************* > Sprit/21 AG > Steven Bühner > Systemberater > > > SPIRIT/21 AG > > Sitz der Gesellschaft: Böblingen > Vorstand: Dietmar Wendt (Vorsitzender), Philipp Steffen, Joachim Gutheil > Vorsitzender des Aufsichtsrates: Siegfried J. Althaus > Registergericht: Amtsgericht Stuttgart, Registernummer: HRB 244681 > Umsatzsteuer-Identifikationsnummer: DE 198412560 > > _______________________________________________ > sipx-dev mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
