asterisk users - Aug 2010 - AEL - what is error: ael.flex:647 ael_yylex: Unhandled char(s):

Hi List,

When doing 'ael reload' on two servers, which are setup with asterisk
1.4.22
and 1.4.35 respectively, I am getting multiple lines of this strange error:

ERROR[15483]: ael.flex:647 ael_yylex: Unhandled char(s):

On three other servers with same versions of asterisk, i.e. 1.4.22, I don't
see this error.

Number of lines of the error are the same as the number of lines of the
code. But the AEL code works fine otherwise.

Any idea what is the reason of this error? I couldn't find any useful info
on google regarding this error.

-- 
Zeeshan A Zakaria
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20100825/8212a68d/attachment.htm

>From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Zeeshan
Zakaria
>Sent: Wednesday, August 25, 2010 10:24 AM
>To: Asterisk Users Mailing List - Non-Commercial Discussion
>Subject: [asterisk-users] AEL - what is error: ael.flex:647
ael_yylex:Unhandled char(s):

 
>Hi List,
 
>When doing 'ael reload' on two servers, which are setup with
asterisk
1.4.22 and 1.4.35 respectively, I am getting multiple lines of this strange
error:

 
>ERROR[15483]: ael.flex:647 ael_yylex: Unhandled char(s):
 
>On three other servers with same versions of asterisk, i.e. 1.4.22, I
don't
see this error.

 
>Number of lines of the error are the same as the number of lines of the
code. But the AEL code works fine otherwise.

 
>Any idea what is the reason of this error? I couldn't find any useful
info
on google regarding this error.
>Zeeshan A Zakaria
 

According to this

https://issues.asterisk.org/view.php?id=14022

 

1.4.X doesn't have all of the 8-bit handling it should have (something in
your ael script is freaking out UTF-8)

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20100825/22720a96/attachment.htm

That's what I understood too from this one and probably only related google
search result, but even if I have just 3-4 lines of code, the error is still
there. It is all English characters, so UTF-8 compatibility issue should not
be there. I am sure there is some small little config change is required
somewhere related to AEL, but where, I don't know.

Zeeshan A Zakaria

--
www.ilovetovoip.com

On 2010-08-25 11:37 AM, "Danny Nicholas" <danny at debsinc.com>
wrote:

  *>From:* asterisk-users-bounces at lists.digium.com [mailto:
asterisk-users-bounces at lists.digium.com] *On Behalf Of *Zeeshan
Zakaria
>*Sent:* Wednesday, August 25, 2010 10:24 AM
>*To:* Asterisk Users Mailing List - Non-Commercial Discussion
>*Subject:* [asterisk-users] AEL - what is error: ael.flex:647
ael_yylex:Unhandled char(s):




>Hi List,

>When doing 'ael reload' on two servers, which are setup with
asterisk
1.4.22 and...


>Any idea what is the reason of this error? I couldn't find any useful
info
on google regarding th...

According to this

https://issues.asterisk.org/view.php?id=14022



1.4.X doesn?t have all of the 8-bit handling it should have (something in
your ael script is freaking out UTF-8)

--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
              http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20100825/eb1762ec/attachment.htm

Actually I have found the problem, and leanred some new stuff along with it.

Apparently all Linux files have a mime type information stored in them,
which can be checked using command:

file -i <filename>

For my extensions.ael, which I copied from a different server, the mime type
is 'text/x-c' whereas all the other files have mime type
'text/plain'. Now
if I create a new file extemsions.maelstrom on this machine which is by
default 'text/plain', there are no errors on doing 'ael reload',
however
using extensions.maelstrom with mime type 'text/x-c' gives errors,
though
the code works fine.

How it got mime type 'text/x-c' on the other machine, Vim which I use
there
assigned it this mime type. I'll have to fix it there.

Now I am trying to figure out how to convert between mime types. A simpler
solution is to just copy text to a new file, but would be nice to do a
proper conversion.

Zeeshan A Zakaria

--
www.ilovetovoip.com

On 2010-08-25 12:01 PM, "Watkins, Bradley" <Bradley.Watkins at
compuware.com>
wrote:



 ------------------------------


From: asterisk-users-bounces at lists.digium.com [mailto:
asterisk-users-bounces at lists.digium.com] On B...
*Sent:* Wednesday, August 25, 2010 11:43 AM


To: Asterisk Users Mailing List - Non-Commercial Discussion
*Subject:* Re: [asterisk-users] AEL - what is error: ael.flex:647
ael_yylex:Unhandled char(s):

That's what I understood too from this one and probably only related google
search result, but even ...

Is there any chance that these files were edited on a Windows machine and
then copied back to the Asterisk boxes?  That is, are there some nefarious
^m characters hiding in there?



Regards,

- Brad


--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
              http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20100825/9dee1eb9/attachment.htm

It did the trick. Thanks a lot for solving this annoying problem. Yes, it
was invisible ^M characters, which I could see in Vim, but not in vi. Now
'ael reload' ouput is how it should be.

Zeeshan A Zakaria

--
www.ilovetovoip.com

On 2010-08-25 1:29 PM, "Rodrigo Lang" <rodrigoferreiralang at
gmail.com> wrote:

Use the command "aptitude install tofrodos" to install dos2unix. This
command get the file and clear the "^M".


Regards,
Rodrigo Lang.

2010/8/25 Zeeshan Zakaria <zishanov at gmail.com>

>
> Actually I have found the problem, and leanred some new stuff along with
it.
>
> Apparently all...


-- 
Rodrigo Lang
http://rodrigorecipes.blogspot.com/<http://rodrigorecipes.blogspot.com/2010/08/ssh-rapido-e-pratico.html>


--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
              http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20100825/ab401cf3/attachment.htm

On Wed, 25 Aug 2010, Zeeshan Zakaria wrote:
> Apparently all Linux files have a mime type information stored in them, 
> which can be checked using command:
> 
> file -i <filename>
Linux files are just a byte stream. They do not have "mime type 
information stored in them."

"file" works by examining the first x bytes of the file and comparing
this
to a "magic" file of "rules" to guess file types.

For instance, a JPEG file starts with "0xff 0xd8 0xff 0xe1."

The "-i" or "--mime" command line option causes file to
display a "mime
type" instead of a "more traditional human readable" one.

The "hexdump" command will show you the "binary" contents of
a file in a
variety for formats:

# Create a file with 2 lines
$ printf "line 1\nline 2\n" >foo

# Dump the file. Note that "0a" (newline, aka line-feed) is the line 
# ending character.
$ hexdump -C foo
00000000  6c 69 6e 65 20 31 0a 6c  69 6e 65 20 32 0a        |line 1.line 2.|

# file says it is just ASCII text, like all text files on Unix should be.
$ file foo
foo: ASCII text

# Convert the file to DOS line endings
$ unix2dos foo
unix2dos: converting file foo to DOS format ...

# Dump the file. Note that the line ending characters are now "0d" 
# (carriage return) and "0a" (newline).
$ hexdump -C foo
00000000  6c 69 6e 65 20 31 0d 0a  6c 69 6e 65 20 32 0d 0a  |line 1..line 2..|

# file says it has "funky" line endings.
$ file foo
foo: ASCII text, with CRLF line terminators

CRLF = Carriage Return, Line Feed -- think of a typewriter. Watch the 
History Channel for more info.

-- 
Thanks in advance,
-------------------------------------------------------------------------
Steve Edwards       sedwards at sedwards.com      Voice: +1-760-468-3867 PST
Newline                                              Fax: +1-760-731-3000

Thanks Steve for clearing this confusion.

Zeeshan A Zakaria

--
www.ilovetovoip.com

On 2010-08-25 3:16 PM, "Steve Edwards" <asterisk.org at
sedwards.com> wrote:

On Wed, 25 Aug 2010, Zeeshan Zakaria wrote:
> Apparently all Linux files have a mime type informati...
Linux files are just a byte stream. They do not have "mime type
information stored in them."

"file" works by examining the first x bytes of the file and comparing
this
to a "magic" file of "rules" to guess file types.

For instance, a JPEG file starts with "0xff 0xd8 0xff 0xe1."

The "-i" or "--mime" command line option causes file to
display a "mime
type" instead of a "more traditional human readable" one.

The "hexdump" command will show you the "binary" contents of
a file in a
variety for formats:

# Create a file with 2 lines
$ printf "line 1\nline 2\n" >foo

# Dump the file. Note that "0a" (newline, aka line-feed) is the line
# ending character.
$ hexdump -C foo
00000000  6c 69 6e 65 20 31 0a 6c  69 6e 65 20 32 0a        |line 1.line 2.|

# file says it is just ASCII text, like all text files on Unix should be.
$ file foo
foo: ASCII text

# Convert the file to DOS line endings
$ unix2dos foo
unix2dos: converting file foo to DOS format ...

# Dump the file. Note that the line ending characters are now "0d"
# (carriage return) and "0a" (newline).
$ hexdump -C foo
00000000  6c 69 6e 65 20 31 0d 0a  6c 69 6e 65 20 32 0d 0a  |line 1..line
2..|

# file says it has "funky" line endings.
$ file foo
foo: ASCII text, with CRLF line terminators

CRLF = Carriage Return, Line Feed -- think of a typewriter. Watch the
History Channel for more info.

--
Thanks in advance,
-------------------------------------------------------------------------
Steve Edwards       sedwards at sedwards.com      Voice: +1-760-468-3867 PST
Newline                                              Fax: +1-760-731-3000

--

_____________________________________________________________________
-- Bandwidth and Colocation Pr...
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20100825/aca016bf/attachment.htm