14 Mar
2011
14 Mar
'11
3:38 p.m.
On 3/14/11 12:33 PM, Daniel-Constantin Mierla wrote:
Hello Stefan,
On 3/14/11 11:03 AM, Stefan Tiedje wrote:
... ^^^ ... obviously this was incomplete phrase, it meant to be:
"I
used Kamailio 3.1.2 and recommend using it since it has the latest
commits for stability".
I can add also that I got more familiar in configuring it with snmpstats
on debian/ubuntu, so it would be easier for me to give hints as well as
add new features since it is the same as devel version.
Cheers,
Daniel
Thanks for the answer.
Maybe I have some older versions of the OPENSER-MIB and the other
related MIB's since I could not find the counter you pointed at. I'm
using a MIB browser for reading the MIB's.
Is the suggested counter "expired dialogs" added in a specific
release of Kamailio? Which? We use Kamailio 3.0.2.
I used Kamailio and recommend
using it sine it has the latest commits
for stability.
However, what I wrote before is pretty much not related to the
version. There is a counter that tracks the processed dialogs, but
seems it is not exported by default through snmpstats module. The
statistics counter is named "processed_dialogs", implemented by dialog
module.
You can dump all internal statistics through kamctl or via xmlrpc
command, but probably to export it through snmpstats you may need to
extend the mibs and the code of the module.
I just grepped the sources of snmpstats module to see what dialog
statistics it is exporting:
$ grep -n _dialogs modules_k/snmpstats/* | grep get_statistic
modules_k/snmpstats/alarm_checks.c:83: num_dialogs =
get_statistic("active_dialogs");
modules_k/snmpstats/snmpObjects.c:404: int result =
get_statistic("active_dialogs");
modules_k/snmpstats/snmpObjects.c:424:
get_statistic("active_dialogs") -
modules_k/snmpstats/snmpObjects.c:425:
get_statistic("early_dialogs");
modules_k/snmpstats/snmpObjects.c:443: int result =
get_statistic("early_dialogs");
modules_k/snmpstats/snmpObjects.c:459: int result =
get_statistic("failed_dialogs");
modules_k/snmpstats/snmpObjects.c:508: int num_dialogs =
get_statistic("active_dialogs");
Perhaps when the snmpstats was developed the dialog module didn't
export the statistics counter of "processed_dialogs" and then it was
not updated.
Now, what I tried to say is that if the "processed_dialogs" counter is
not available through snmpstats (and it is not now after grepping the
sources) you can get its value from another application through
"kamctl get_statistics all" or XMLRPC command for all of the existing
kamailio releases. Upcoming one we will look to implement the export
through snmpstats as well. If you have time to do it and send us a
patch, we will gladly commit it to source tree in our GIT repository.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com
Do you have the MIB name for the "expired
dialogs" counter. I will
look for that in my version of OPENSER MIBS.
Important, do you have a link to where MIB files can be downloaded
for Kamailio 3.0.2?
Below follows an excerp from one of the MIB's. Is it old, I don't know?
--
***********************************************************************
-- OPENSER-MIB: OPENSER MIB
--
-- Date of Creation: Januay 2006
--
-- This MIB provides information related to the OpenSER SIP Router.
--
-- Copyright (c) The Internet Society (2006)
-- Ammendments (c) Soma Networks, Inc. (2006)
--
-- All rights reserved.
-- *****************************************************************
/Stefan
------------------------------------------------------------------------
*From:* Daniel-Constantin Mierla [mailto:miconda@gmail.com]
*Sent:* den 14 mars 2011 10:16
*To:* Stefan Tiedje
*Cc:* sr-users(a)lists.sip-router.org
*Subject:* Re: [SR-Users] OPENSER MIB
Hello,
On 3/14/11 9:42 AM, Stefan Tiedje wrote:
--
Daniel-Constantin Mierla
http://www.asipto.com
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users Hi,
In the Kamailio OPENSER-MIB there is the counter
"openserTotalNumFailedDialogSetups". This is a Counter32.
The description is:
"The total number of calls that failed with an error. The
following codes define a failed call:"
*Question:*
* I'm looking for the corresponding counter to
"openserTotalNumFailedDialogSetups" who counts successful
Dialog setups of Counter32 type. Does it exist?
* If not, does it exist a work around?
* Where in the code can the new suggested counter be added?
* Something else????
the dialog module counts the number of processed dialogs, see:
http://kamailio.org/docs/modules/stable/modules_k/dialog.html#id2966360
There is no counter currently inside dialog module exporting exactly
the number of successfully setup dialogs, it should not be hard to do
it, though. Using the above and the number of failed and expired
dialogs, you can actually get the number of successful dialogs.
Dialog module being the one that tracks SIP dialogs, therefore being
able to count them, now I don't know if snmpstats module exports all
the counters from dialog module. I setup snmpstats just few weeks ago
and works perfect on Ubuntu/Debian servers, but I had no need to
check dialog module counters.
Note that you can get the list of all internal statistics via kamctl:
- kamctl fifo get_statistics all
Or via XMLRPC if you need them remotely in another application.
Another option is to define your statistics with statistics module.
Knowing that in SIP a successful call dialog means 200ok reply to an
INVITE transaction, you can count it in the onreply_route[abc] that
you arm for relayed transactions with t_on_reply("abc").
Hope these help you,
Daniel
Suggestion for the new counter is a name like:
"openserTotalNumSucceededDialogSetups". It has a counter32.
Description: "The total number of calls that succeeded"
I know that there are the counters openserCurNumDialogs,
openserCurNumDialogsInProgress and openserCurNumDialogsInSetup but
these are of Gauge type who only reflects the current situation.
These Gauge counters can't be used together with a Counter32
counter. That don't mix. The calculation done for the counter
"openserCurNumDialogsInProgress" should be used where every new
dialog setup is added to the new suggested counter. A counter of 32
should cover a great deal of connections. These counters are usually
read, if used, every 15 minutes or 1 hour.
*Rationale:*
The reason for the new counter is that a calculation between
succeeded and failed dialog setups can be done and be used for SLA
agreements. Without this, its hard to make any customer versus
provider agreements.
/Stefan
PS. Ask if anything is unclear and I need an answer rapidly.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://www.asipto.com