${CMGR} exported variable have an '\n', and confuse AGI scrips

bg111 / asterisk-chan-dongle

Automatically exported from code.google.com/p/asterisk-chan-dongle

Other

346 stars 308 forks source link

${CMGR} exported variable have an '\n', and confuse AGI scrips #185

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago


chan_dongle when an SMS arrive export also the ${CMGR} variable, with the RAW 
PDU of the message.

But the variable content have an '\n' inside, that confuse AGI scripts, that 
expect reply in one row only.

I've solved adding in dialplan:

 exten => sms,n,Set(CMGR_BASE64=${BASE64_ENCODE(${CMGR})})
 exten => sms,n,AGI(my_script)

but i hope will be fixed also. Thanks.

Original issue reported on code.google.com by macog...@gmail.com on 20 Sep 2014 at 9:25

GoogleCodeExporter commented 9 years ago

its referred to asterisk dialplan escapes and AGI interface.
in any case nothing forbid send something to AGI encoded

Original comment by bg_...@mail.ru on 14 Oct 2014 at 10:30

Changed state: Invalid

GoogleCodeExporter commented 9 years ago

Ok, but:

a) i think that stuff is worth a note in docs

b) as exist ${SMS} and ${SMS_BASE64}, probably it is better to add directly 
${CMGR_BASE&$} in chan_dongle, instead of using a dialplan hack...

Thanks.

Original comment by macog...@gmail.com on 15 Oct 2014 at 12:51