[asterisk-bugs] [JIRA] (ASTERISK-19254) When working in real time with ARA and MySQL the backslashes not works properly

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-19254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201512#comment-201512 ] 

Matt Jordan commented on ASTERISK-19254:
----------------------------------------

Please note that {{pbx_realtime}} is an extended support module and development effort for it comes from the open source community. Response times may reflect that.

(Patches are always appreciated for all issues, but especially those in extended support!)

                
> When working in real time with ARA and MySQL the backslashes not works properly
> -------------------------------------------------------------------------------
>
>                 Key: ASTERISK-19254
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19254
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Addons/app_mysql
>    Affects Versions: 1.8.8.2
>         Environment: Debian GNU/Linux 6.0.3
>            Reporter: Janu
>
> Hello.
> I found a problem with MySQL Realtime in the dialplan.
> I'm trying to set different ring tones in a Snom 3xx, like this:
> http://asterisk.snom.com/index.php/Asterisk_1.6/Ringtone_Configuration
> As you can see we have to add this application:
> SIPAddHeader("Alert-Info:<http://nohost>\;info=alert-internal\;x-line-id=0")
> This example works properly in typical static configurations, like this:
> exten => _XXX,1,SIPAddHeader("Alert-Info:<http://nohost>\;info=alert-internal\;x-line-id=0")
> exten => _XXX,n,Dial(SIP/${EXTEN})
> exten => _XXX,n,Hangup
> This is the simple programming dialplan in MySQL database:
> mysql> SELECT * FROM dialplan WHERE exten='_XXX' ORDER BY priority;
> +-----+---------+-------+----------+--------------+------------------------------------------------
> + id  | context | exten | priority | app          | appdata                                                      
> +-----+---------+-------+----------+--------------+------------------------------------------------
> + 597 | intern  | _XXX  |        1 | SIPAddHeader | Alert-Info:<http://nohost>\;info=alert-internal\;x-line-id=0
> + 551 | intern  | _XXX  |        2 | Dial         | SIP/${EXTEN},15,Tt                                          
> + 552 | intern  | _XXX  |        3 | Hangup       |                                                             
> +-----+---------+-------+----------+--------------+------------------------------------------------
> 3 rows in set (0.00 sec)
> The result of the execution in the CLI is:
>   == Using SIP RTP CoS mark 5
>     -- Executing [202 at intern:1] SIPAddHeader("SIP/201-00000000", "x-line-id=0")
>     -- Executing [202 at intern:2] Dial("SIP/201-00000000", "SIP/202,15,Tt")
> Note that only displays the text after the last backslash.
> I found in the archive from the list of digium a user already reported the error in the past:
> http://lists.digium.com/pipermail/asterisk-users/2007-September/196183.html
> Thanks for your time.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira