[asterisk-bugs] [Asterisk 0014498]: String operator ':' error with UTF8 code
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Feb 19 16:44:57 CST 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=14498
======================================================================
Reported By: ibercom
Assigned To: murf
======================================================================
Project: Asterisk
Issue ID: 14498
Category: PBX/General
Reproducibility: always
Severity: major
Priority: normal
Status: closed
Asterisk Version: 1.4.23
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: duplicate
Duplicate: 0
Fixed in Version:
======================================================================
Date Submitted: 2009-02-18 07:43 CST
Last Modified: 2009-02-19 16:44 CST
======================================================================
Summary: String operator ':' error with UTF8 code
Description:
I have a dialplan with:
exten=>_0.,1,GotoIf($["${CALLERID(name)}" : "Fax"]?cat4,${EXTEN},1)
If I use UTF8 code (Spanish in my case) this expression generate a error:
[Feb 18 11:55:23] WARNING[21600] ast_expr2.fl: ast_yyerror(): syntax
error: syntax error, unexpected '<token>', expecting $end; Input:
"Extension Campaña 20000" : "Fax"
^
[Feb 18 11:55:23] WARNING[21600] ast_expr2.fl: If you have questions,
please refer to doc/channelvariables.txt in the asterisk source.
It could be related to http://bugs.digium.com/view.php?id=14022.
======================================================================
----------------------------------------------------------------------
(0100414) murf (administrator) - 2009-02-19 16:44
http://bugs.digium.com/view.php?id=14498#c100414
----------------------------------------------------------------------
I've just attached "14498.patch", which solves the problem. I'm going to
close this bug again, so sure am I that I have *really* found the problem
and fixed it this time (again). Sorry for the hassle. The commit message
will explain all the particulars. If I *still* have not solved your problem
(I tested it here), reopen again, and we'll dig even deeper, but I'm pretty
sure this is it!
Issue History
Date Modified Username Field Change
======================================================================
2009-02-19 16:44 murf Note Added: 0100414
======================================================================
More information about the asterisk-bugs
mailing list