Summary:ASTERISK-06990: Userevent command and AEL, wrong parsing ?
Reporter:Alessio Focardi (alessiof)Labels:
Date Opened:2006-05-17 13:06:13Date Closed:2011-06-07 14:07:22
Versions:Frequency of

while revriting my dialplan in AEL I noticed that this instruction

userevent(TAPI|DATA: ${DATASTRING});

result in this

 [userevent(TAPI|DATA] 67. ${DATASTRING})()                          [pbx_ael]

in the dialplan.

Syntax of userevent command seems right to me

Send an arbitrary event to the manager interface

 UserEvent(eventname[|body]): Sends an arbitrary event to the

Am I getting it wrong or is this a parse bug ?

Tnx for the support!
Comments:By: Serge Vecher (serge-v) 2006-05-17 13:18:59

alessiof: could you please try the latest trunk version to see if this is a problem there as well? AEL has gone major changes in trunk ...


By: Alessio Focardi (alessiof) 2006-05-17 13:22:11

I have to add that I solved the issue using

userevent(TAPI|DATA\:\ ${DATASTRING});

instead of

userevent(TAPI|DATA: ${DATASTRING});

Should I test it also against trunk ?

By: Serge Vecher (serge-v) 2006-05-17 13:26:40

if possible; your testing will increase your karma :)

By: Alessio Focardi (alessiof) 2006-05-17 13:35:32

tested with Asterisk SVN-trunk-r26758

_.=>  UserEvent(TAPI|DATA: ${DATASTRING});

[ Context 'none' created by 'pbx_ael' ]
 '_.' =>           1. UserEvent(TAPI|DATA: ${DATASTRING})        [pbx_ael]

It seems to be working ok in trunk ...

By: Serge Vecher (serge-v) 2006-05-17 13:44:49

thanks, allesiof. Kudos to murf and rizzo :)

By: Serge Vecher (serge-v) 2006-05-17 14:04:23

closing this bug, since we have a workaround and problem doesn't exist in trunk.