CEL For Attented Transfer

Home » Asterisk Users » CEL For Attented Transfer
Asterisk Users 7 Comments

Hi list,

I’m trying to use CEL to display channel information in real time. It works fine for simple calls, blind transfers, or SIP attended transfers
(initiated from the SIP phone). My problem is for Asterisk attended transfers (atxfer as configured in features.conf).

The scenario is:
. phone 107 calls phone 100,
. 100 dials the atxfer code,
. 107 is on hold, and 100 hears the transfer message,
. 100 dials phone 103,
. 103 answers,
. 100 hangups,
. 107 and 103 are connected,
. 107 hangups.

CEL is configured with apps=all and events=ALL, and events are stored in a database via cel_pgsql.

This is the list of events in the database for this call:

eventtype | channame | peer

—————–+——————————–+——————————-
CHAN_START | SIP/107-0274 |
CHAN_START | SIP/100-0275 |
ANSWER | SIP/100-0275 |
ANSWER | SIP/107-0274 |
BRIDGE_START | SIP/107-0274 | SIP/100-0275
CHAN_START | Local/103@100-0042;1 |
CHAN_START | Local/103@100-0042;2 |
CHAN_START | SIP/103-0276 |
ANSWER | SIP/103-0276 |
ANSWER | Local/103@100-0042;2 |
BRIDGE_START | Local/103@100-0042;2 | SIP/103-0276
ANSWER | Local/103@100-0042;1 |
BRIDGE_START | SIP/100-0275 | Local/103@100-0042;1
BRIDGE_END | SIP/100-0275 | Local/103@100-0042;1
ATTENDEDTRANSFER | SIP/107-0274 | Local/103@100-0042;1
CHAN_START | Transfered/SIP/107-0274 |
BRIDGE_END | Transfered/SIP/107-0274| SIP/100-0275
BRIDGE_START | SIP/107-0274 | Local/103@100-0042;1
HANGUP | SIP/100-0275 |
CHAN_END | SIP/100-0275 |
HANGUP | Transfered/SIP/107-0274|
CHAN_END | Transfered/SIP/107-0274|
BRIDGE_END | SIP/107-0274 | Local/103@100-0042;1
HANGUP | Local/103@100-0042;1 |
CHAN_END | Local/103@100-0042;1 |
HANGUP | SIP/107-0274 |
CHAN_END | SIP/107-0274 |
BRIDGE_END | Local/103@100-0042;2 | SIP/103-0276
HANGUP | SIP/103-0276 |
CHAN_END | SIP/103-0276 |
HANGUP | Local/103@100-0042;2 |
CHAN_END | Local/103@100-0042;2 |
LINKEDID_END | Local/103@100-0042;2 |
(33 lignes)

How should these events be interpreted?

Asterisk version is 11.6.0.

Thanks,
– —
Jean-Denis Girard

SysNux Systèmes Linux en Polynésie française http://www.sysnux.pf/ Tél: +689 50 10 40 / GSM: +689 79 75 27
—–BEGIN PGP SIGNATURE—–

iEYEARECAAYFAlKJn7EACgkQuu7Rv+oOo/gM+wCeMuUit/qQDBH3ymnxkngZAPUs FKUAn3wYVXKqtyd/xEZQM5u4tVqAwyZ9
=6SQH
—–END PGP SIGNATURE—–

7 thoughts on - CEL For Attented Transfer

  • Nobody, really?

    Thanks,
    – —
    Jean-Denis Girard

    SysNux Systèmes Linux en Polynésie française http://www.sysnux.pf/ Tél: +689 50 10 40 / GSM: +689 79 75 27

    Le 17/11/2013 19:03, Jean-Denis Girard a écrit :
    —–BEGIN PGP SIGNATURE—–

    iEYEARECAAYFAlKK6p0ACgkQuu7Rv+oOo/heAACeN0eMR1qwRLcdV+Tsgn9fA+6c RKcAn246hmNUU2dxivPFEziueHYRTWcS
    =q196
    —–END PGP SIGNATURE—–

  • Hi Jean.

    I am not sure but believe the sequence of CEL events should be considered for a more detailed understanding of a call.

    Replicating the case you described I got this CEL event and fields:

    *************************** 17. row ***************************
    id: 27984
    eventtype: ATTENDEDTRANSFER
    eventtime: 2013-11-20 15:05:33
    userdeftype:
    cid_name: Jairo desktop
    cid_num: 311
    cid_ani: 311
    cid_rdnis:
    cid_dnid: 310
    exten: 310
    context: entrada-canal
    channame: SIP/311-351096-0000048d
    appname: Dial
    appdata: SIP/310-777940,40,kKtT
    amaflags: 3
    accountcode:
    peeraccount:
    uniqueid: 1384967109.1184
    linkedid: 1384967109.1184
    userfield:
    peer: Local/321@entrada-canal-00000001;1

    The 3 extensions can be found in the event. Does it help?

    2013/11/19 Jean-Denis Girard

  • Well, it is a way lot harder to figure out because you used features.conf. Because of this, local channels are involved.

    Specifically, you are going to have to track the channel IDs and look at the sequence of events. Then make an educated guess about what is happening.