Hello,
On 3/14/11 9:42 AM, Stefan Tiedje wrote:
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@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://www.asipto.com
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
