[asterisk-users] Problem with CEL logging and channel bridging

Fabio Moretti fmoretti at tecytal.com
Thu Jun 13 09:31:36 CDT 2013


Hi, I've already post this to the forum three days ago, sorry if it's
sounds like a crosspost, but I've got no replies, so I'm trying other
channels :)

This is the link to the forum post if someone prefer to reply here:
http://forums.asterisk.org/viewtopic.php?f=1&t=86985

I'm using Asterisk 1.8.20.0 (the freepbx build) with CEL logging
activated. I'm using CEL because in our pbx we have different queues and
trunks serving different customers (we are an inbound call center) and
we need to detect when and how we have to bill our customers.
I'm facing an issue with the call transfer, for example I have:
- call entering a queue
- operator answer the call
- operator make an outgoing call to reach the customer
- operator put in communication the ingoing call with the outgoing
this result in various channel to be created/destroyed, and I'm using
bridge events to detect what is going on with the call. In this case I
have (I've hidden CHAN_START,ANSWER and HANGUP events because they have
no useful information in this case):

+--------+---------------+---------------------+-------+---------------------+----------------------------------+---------+-----------------------------+----------------------------------+

| id     | eventtype     | eventtime           | exten | context             | channame                         | appname | appdata                     | peer                             |

+--------+---------------+---------------------+-------+---------------------+----------------------------------+---------+-----------------------------+----------------------------------+

| 965224 | BRIDGE_START  | 2013-06-10 10:15:18 | 20    | ext-queues          | DAHDI/i1/96034296-30a3           | Queue   | 20,t,,                      | Local/1004 at from-queue-00019c34;1 |

| 965226 | BRIDGE_START  | 2013-06-10 10:15:18 | s     | macro-dial-one      | Local/1004 at from-queue-00019c34;2 | Dial    | SIP/1004,"",trM(auto-blkvm) | SIP/1004-000040ce                |

| 965340 | BRIDGE_UPDATE | 2013-06-10 10:16:08 | s     | macro-dialout-trunk | Local/1004 at from-queue-00019c34;2 | Dial    | IAX2/issuegroup/110,300,    | IAX2/issuegroup-17175            |

| 965513 | BRIDGE_END    | 2013-06-10 10:18:15 | 20    | ext-queues          | DAHDI/i1/96034296-30a3           | Queue   | 20,t,,                      | Local/1004 at from-queue-00019c34;1 |

| 965515 | BRIDGE_END    | 2013-06-10 10:18:15 | s     | macro-dialout-trunk | Local/1004 at from-queue-00019c34;2 | Dial    | IAX2/issuegroup/110,300,    | IAX2/issuegroup-17175            |

+--------+---------------+---------------------+-------+---------------------+----------------------------------+---------+-----------------------------+----------------------------------+


The first BRIDGE_START is the connection between the inbound call
(DAHDI/i1/96034296-30a3) and the local phone
(Local/1004 at from-queue-00019c34;1), the second BRIDGE_START is the
connection between the local phone (Local/1004 at from-queue-00019c34;2)
and the outgoing call (SIP/1004-000040ce) that is going out by a IAX trunk.
After that I have a BRIGDE_UPDATE event where no field make me know
which channel is being updated, I only have the channame
(Local/1004 at from-queue-00019c34;2) that is the channel being bridged out
and the outgoing channel (IAX2/issuegroup-17175), but I have no
information that in fact the ingoing call (DAHDI/i1/96034296-30a3) is
being bridged to the outgoing channel.
I have no other event (TRANSFER or something like that) to know what is
going on.

In my cel.conf I have:

apps=queue
events=CHAN_START,CHAN_END, APP_START,APP_END, ANSWER,HANGUP,
BRIDGE_START,BRIDGE_END,BRIDGE_UPDATE,
BLINDTRANSFER,ATTENDEDTRANSFER,TRANSFER, PICKUP, FORWARD,
PARK_START,PARK_END, LINKEDID_END

Should I change something in my configuration or it's wrong to rely on
bridges to follow a call? What kind of event should I follow to be sure
to catch where the call is going?

Thank you for any suggestion!




More information about the asterisk-users mailing list