While CDRs and the Manager are basically both event tracking mechanisms, CEL tries to track only those events that might pertain to billing issues.

Table of CEL Events

Event

Description

CHAN_START

The time a channel was created

CHAN_END

The time a channel was terminated

ANSWER

The time a channel was answered (ie, phone taken off-hook)

HANGUP

The time at which a hangup occurred

CONF_ENTER

The time a channel was connected into a conference room

CONF_EXIT

The time a channel was removed from a conference room

CONF_START

The time the first person enters a conference room

CONF_END

The time the last person left a conference room (and turned out the lights?)

APP_START

The time a tracked application was started

APP_END

the time a tracked application ended

PARK_START

The time a call was parked

PARK_END

Unpark event

BRIDGE_START

The time a bridge is started

BRIDGE_END

The time a bridge is ended

BRIDGE_UPDATE

This is a replacement channel (Masquerade)

3WAY_START

When a 3-way conference starts (usually via attended transfer)

3WAY_END

When one or all exit a 3-way conference

BLINDTRANSFER

When a blind transfer is initiated

ATTENDEDTRANSFER

When an attended transfer is initiated

TRANSFER

Generic transfer initiated; not used yet...?

PICKUP

This channel picked up the peer channel

FORWARD

This channel is being forwarded somewhere else

HOOKFLASH

So far, when a hookflash event occurs on a DAHDI interface

LINKEDID_END

The last channel with the given linkedid is retired

USER_DEFINED

Triggered from the dialplan, and has a name given by the user

Table of CEL Event Fields

Table 11.2: List of CEL Event Fields

Field

Description

eventtype

The name of the event; see the above list.

eventtime

The time the event happened

cid_name

CID name field

cid_num

CID number field

cid_ani

CID ANI field

cid_rdnis

CID RDNIS field

cid_dnid

CID DNID field

exten

The extension in the dialplan

context

The context in the dialplan

channame

The name assigned to the channel in which the event took place

appname

The name of the current application

appdata

The arguments that will be handed to that application

amaflags

The AMA flags associated with the event; user assignable.

accountcode

A user assigned datum (string)

peeraccount

A user assigned datum (string) on the peer.

uniqueid

Each Channel instance gets a unique ID associated with it.

linkedid

the per-call id, spans several events, possibly.

userfield

A user assigned datum (string)

peer

For bridge or other 2-channel events, this would be the other channel name

userdeftype

User defined event name

extra

Extra information associated with the event.