search for: chan_start

...EL 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 at 100-0...

...eported 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 &...

...39;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' repo...

...    -- 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 &...

Dear friends, Need to know filenames of conference recordings in Asterisk 11. Besides directory scanning the recordings could use CEL: Filter MySQL rows with eventtype equal CHAN_START and channame like ConfBridgeRecorder and then get the eventtime field and convert to timestamp to complete filename(s). Would you suggest any other approaches? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-us...

...r 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 | e...

An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20130630/18883d29/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: 1371568201.486360-80.csv.zip Type: application/zip Size: 1674 bytes Desc: not available URL:

...sz Karolak) * ASTERISK-24443 - CDR fields (dst, dcontext) empty in transfer call started from Macro (Reported by Arveno Santoro) * ASTERISK-25154 - [patch]fromtag may need to be updated after successful call dialog match (Reported by Damian Ivereigh) * ASTERISK-25156 - chan_pjsip???s CHAN_START cel event lacks the correct context and exten (Reported by cloos) * ASTERISK-25157 - bridging: Performing a blonde transfer does not result in connected line updates (Reported by Joshua Colp) * ASTERISK-25087 - Asterisk segfault when using Directory application with alias option...

...sz Karolak) * ASTERISK-24443 - CDR fields (dst, dcontext) empty in transfer call started from Macro (Reported by Arveno Santoro) * ASTERISK-25154 - [patch]fromtag may need to be updated after successful call dialog match (Reported by Damian Ivereigh) * ASTERISK-25156 - chan_pjsip???s CHAN_START cel event lacks the correct context and exten (Reported by cloos) * ASTERISK-25157 - bridging: Performing a blonde transfer does not result in connected line updates (Reported by Joshua Colp) * ASTERISK-25087 - Asterisk segfault when using Directory application with alias option...

...sz Karolak) * ASTERISK-24443 - CDR fields (dst, dcontext) empty in transfer call started from Macro (Reported by Arveno Santoro) * ASTERISK-25154 - [patch]fromtag may need to be updated after successful call dialog match (Reported by Damian Ivereigh) * ASTERISK-25156 - chan_pjsip???s CHAN_START cel event lacks the correct context and exten (Reported by cloos) * ASTERISK-25157 - bridging: Performing a blonde transfer does not result in connected line updates (Reported by Joshua Colp) * ASTERISK-25087 - Asterisk segfault when using Directory application with alias option...

...- [ASTERISK-25154 <https://issues.asterisk.org/jira/browse/ASTERISK-25154>] - [patch]fromtag may need to be updated after successful call dialog match (Reported by Damian Ivereigh) - [ASTERISK-25156 <https://issues.asterisk.org/jira/browse/ASTERISK-25156>] - chan_pjsip’s CHAN_START cel event lacks the correct context and exten (Reported by cloos) - [ASTERISK-25157 <https://issues.asterisk.org/jira/browse/ASTERISK-25157>] - bridging: Performing a blonde transfer does not result in connected line updates (Reported by Joshua C. Colp) - [ASTERISK-25087 <ht...