Module Cel Error With Bridge Events

Home » Asterisk Users » Module Cel Error With Bridge Events
Asterisk Users 3 Comments

Hi,

On Asterisk 16.11.1 when enabling cel I get error with BRIDGE_START and BRIDGE_END events

zone-s*CLI> module reload cel The module ‘cel’ reported a reload failure
    — Reloading module ‘cel’ (CEL Engine)
[2020-07-10 17:57:01] ERROR[16163]: cel.c:428 ast_cel_str_to_event_type:
Unknown event name ‘BRIDGE_START’
[2020-07-10 17:57:01] ERROR[16163]: config_options.c:798
aco_process_var: Error parsing events=APP_START,CHAN_START,CHAN_END,BRIDGE_START,BRIDGE_END,ANSWER,HANGUP
at line 72 of
[2020-07-10 17:57:01] ERROR[16163]: config_options.c:544
process_category: In cel.conf: Processing options for general failed zone-s*CLI> module reload cel The module ‘cel’ reported a reload failure
    — Reloading module ‘cel’ (CEL Engine)
[2020-07-10 17:57:31] ERROR[16163]: cel.c:428 ast_cel_str_to_event_type:
Unknown event name ‘BRIDGE_END’
[2020-07-10 17:57:31] ERROR[16163]: config_options.c:798
aco_process_var: Error parsing events=APP_START,CHAN_START,CHAN_END,BRIDGE_END,ANSWER,HANGUP at line
72 of
[2020-07-10 17:57:31] ERROR[16163]: config_options.c:544
process_category: In cel.conf: Processing options for general failed

If I remove BRIDGE_START and BRIDGE_END error disappears.

zone-s*CLI> module reload cel Module ‘cel’ reloaded successfully.
    — Reloading module ‘cel’ (CEL Engine)
    — CEL logging enabled. zone-s*CLI>

Are those 2 events removed from cel ?


Daniel

3 thoughts on - Module Cel Error With Bridge Events

  • BRIDGE_END does not exist in current code. All the removed events were noted in the UPGRADE.txt document:

    – CEL has undergone significant rework in Asterisk 12, and is now built on the
    Stasis message bus. Please see the specification for CEL on the Asterisk
    wiki at https://wiki.asterisk.org/wiki/x/4ICLAQ for more detailed
    information. A summary of the affected events is below:
    – BRIDGE_START, BRIDGE_END, BRIDGE_UPDATE, 3WAY_START, 3WAY_END, CONF_ENTER,
    CONF_EXIT, CONF_START, and CONF_END events have all been removed. These
    events have been replaced by BRIDGE_ENTER/BRIDGE_EXIT.
    – BLINDTRANSFER/ATTENDEDTRANSFER events now report the peer as NULL and
    additional information in the extra string field.

    This occurred as of Asterisk 12.

  • Le 22/07/2020 à 17:47, Joshua C. Colp a écrit :

    My doc bases is still voip-info.org (aside of the wiki) which seems outdated. Sorry, for the noise, thanks for having pointed that point

    Regards