Home

Resources

Products

Developers

Main • Callcounters

Call counters

This module keeps a count of active calls per user specified context and adds one or all counters to be used in routing decisions. The context parameter must be generated in the call.cdr messages by the cdrbuild module.

Parameters

The following parameters are interpreted in the call.cdr message:

  • chan - the ID of the call leg, always added by cdrbuild
  • direction - direction of the call leg, always added by cdrbuild
  • operation - type of CDR operation, always added by cdrbuild
  • parameter - context parameter as configured

In the call.route message:

  • allcounters - local override of the configured setting to add all counters
  • parameter - context parameter as configured, only if allcounters is not true

If allcounters is false parameter_count will be set to the current counter value. A value of zero is never set as context counters are dynamically created and removed.

If allcounters is true several parameter_count_context parameters will be set, each holding the current count for context.

Example

cdrbuild.conf:
[parameters]
context=false

callcounters.conf:
[general]
parameter=context

If there are 3 incoming calls with context=abc and 2 with context=xyz in a new call.route with context=abc it will set:
context_count=3

If allcounters=true then no matter the context in call.route it will set:
context_count_abc=3
context_count_xyz=2

Configuration file:

 
[general]
; Global settings of the per context call counters

; parameter: string: Name of the call parameter to use for context counting
; This parameter must exist in the call.cdr messages by adding a line
;  like: context=false to the [parameters] section of cdrbuild.conf
;parameter=

; direction: string: Direction of the call legs counted, set empty to count all
;direction=incoming

; allcounters: boolean: Add all counters instead of just the current context
;allcounters=false


[priorities]
; Numerical priorities of installed message handlers

; call.cdr: integer: Priority of CDR message handler used to count calls
;call.cdr=20

; call.route: integer: Priority of handler used to add counters to routing message
;call.route=20

3 May 2010:
Yate 3.0.0 alpha 3 released. Featuring the new Jabber server and wideband audio.
Download NOW

8 March 2010:
Yate 2.2 released. Mostly bug fixes. Dahdi compatible. Latest 2 release before 3.0.

6-7 February 2010:
Yate booth at FOSDEM 2010. Free CD with Freesentral available.

2 Nov 2009:
Yate 2.1 launched. Can replace a Cisco PGW2200 to control a Cisco AS54xx.

6 Aug 2008:
Yate and OpenSIPS (former OpenSER) join to build IP based clusters.

4 Aug 2008:
Yate 2 launched.

10 Jul 2008:
Yate presentation in Germany.

Feb 2008:
Yate 2.0.0 alpha 2 released. New routing module allows sending ENUM routed or forked calls to numbers of registered phones. More...

21 Jan 2008:
Yate 2 alpha released. Major changes, new ISDN, SS7 and MGCP stack. Added analogic and RBS support.

3 September:
Yate 1.3 released. Minor fixes and improvments mainly in client and SIP.

14 August:
Yate based ISDN passive recording system released by Trisys.

16 April:
Yate 1.2 released. Added Jingle and XML support, PBX improved.

25 September:
YateAdmin 1 released.

25 September:
Yate 1.1 released. Fallback routing from a database, fax support in Linux and bug fixes. Changelog and Download availables.

11 July 2006:
O'Reilly published an article about prototyping telephony applications with Yate and Python.

10 July 2006:
Yate 1 released. Includes YIAX, YSIP, YRTP and many new features.

June 1st 2006:
New Yate website launched


EditHistoryBacklinksRecent ChangesSearch