subject:"Re\: \[asterisk\-users\] AEL and \};"

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 da...@debsinc.com wrote:

  *From:* asterisk-users-boun...@lists.digium.com [mailto:
asterisk-users-boun...@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
-- 
_
-- 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

Re: [asterisk-users] AEL - what is error: ael.flex:647 ael_yylex:Unhandled char(s):

2010-08-25 Thread Watkins, Bradley

From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Zeeshan
Zakaria
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 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

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

Re: [asterisk-users] AEL - what is error: ael.flex:647 ael_yylex:Unhandled char(s):

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.watk...@compuware.com
wrote:



 --


From: asterisk-users-boun...@lists.digium.com [mailto:
asterisk-users-boun...@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
-- 
_
-- 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

Re: [asterisk-users] AEL - what is error: ael.flex:647 ael_yylex:Unhandled char(s):

2010-08-25 Thread Rodrigo Lang

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 zisha...@gmail.com

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.watk...@compuware.com
wrote:

From: asterisk-users-boun...@lists.digium.com [mailto:
asterisk-users-boun...@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

--
_
-- 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

--
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

Re: [asterisk-users] AEL - what is error: ael.flex:647 ael_yylex:Unhandled char(s):

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 rodrigoferreiral...@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 zisha...@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
-- 
_
-- 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

Re: [asterisk-users] AEL - what is error: ael.flex:647 ael_yylex:Unhandled char(s):

2010-08-25 Thread Steve Edwards

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
  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
  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   sedwa...@sedwards.com  Voice: +1-760-468-3867 PST
Newline  Fax: +1-760-731-3000

-- 
_
-- 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

Re: [asterisk-users] AEL - what is error: ael.flex:647 ael_yylex:Unhandled char(s):

Thanks Steve for clearing this confusion.

Zeeshan A Zakaria

--
www.ilovetovoip.com

On 2010-08-25 3:16 PM, Steve Edwards asterisk@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
  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
  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   sedwa...@sedwards.com  Voice: +1-760-468-3867 PST
Newline  Fax: +1-760-731-3000

--

_
-- Bandwidth and Colocation Pr...
-- 
_
-- 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

Re: [asterisk-users] AEL in 1.6 and Gosub

2010-03-17 Thread Klaus Darilion



Am 17.03.2010 00:40, schrieb Steve Murphy:



 How about:


 blacklist(${exten});


 macro blacklist(the_exten)
 {
  switch(the_exten)
  {
  pattern +4390[01]: Hangup();
  default: return;
  }
 }

Yes, that would work. I didn't knew the pattern statement.

 Basically, you are using the pattern matching capability to
 end the call for certain extensions... so the above should
 come close. If you really, really want to keep your gosub call,
 then you can, you'll just have to ignore the warnings, iirc.

I think I will just ignore it :-)

thanks
klaus


-- 
_
-- 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

Re: [asterisk-users] AEL in 1.6 and Gosub

2010-03-17 Thread Elliot Murdock

Hello Klaus,

Just for your quick reference, here are some other changes in the AEL
from versions 1.4 to 1.6 (source:
http://asteriskuptospeed.linuxinnovations.com/core1.4-1.6.2.html and
CHANGES file) :

Macros are now implemented underneath with the Gosub() application.
Heaven Help You if you wrote code depending on any aspect of this!
Previous to 1.6, macros were implemented with the Macro() app, which
provided a nice feature of auto-returning. The compiler will do its
best to insert a Return() app call at the end of your macro if you did
not include it, but really, you should make sure that all execution
paths within your macros end in return;.

The conf2ael program is 'introduced' in this release; it is in a
rather crude state, but deemed useful for making a first pass at
converting extensions.conf code into AEL. More intelligence will come
with time.

AEL upgraded to use the Gosub with Arguments instead of Macro
application, to hopefully reduce the problems seen with the
artificially low stack ceiling that Macro bumps into. Macros can only
call other Macros to a depth of 7. Tests run using gosub, show depths
limited only by virtual memory. A small test demonstrated recursive
call depths of 100,000 without problems. -- in addition to this, all
apps that allowed a macro to be called, as in Dial, queues, etc, are
now allowing a gosub call in similar fashion.

AEL now generates LOCAL(argname) declarations when it Set()'s the each
arg name to the value of ${ARG1}, ${ARG2), etc. That makes the
arguments local in scope. The user can define their own local
variables in macros, now, by saying local myvar=someval; or using
Set() in this fashion: Set(LOCAL(myvar)=someval); (local is now an
AEL keyword).
utils/conf2ael introduced. Will convert an extensions.conf file into
extensions.ael. Very crude and unfinished, but will be improved as
time goes by. Should be useful for a first pass at conversion.

aelparse will now read extensions.conf to see if a referenced macro or
context is there before issueing a warning.

AEL parser sets a local channel variable ~~EXTEN~~, to preserve the
value of ${EXTEN} thru switch statements.

New operator in $[...] expressions: the ~~ operator serves as a
concatenation operator. AT THE MOMENT, it is really only necessary and
useful in AEL, especially in if() expressions. Operation: ${a} ~~ ${b|
with force both a and b to strings, strip any enclosing double-quotes,
and evaluate to the value of a concatenated with the value of b. For
example if a is set to xyz and b has the value abc, then ${a} ~~
${b| would evaluate to xyzabc

Good luck with your upgrade!
Elliot

On Wed, Mar 17, 2010 at 12:48 PM, Klaus Darilion
klaus.mailingli...@pernau.at wrote:


 Am 17.03.2010 00:40, schrieb Steve Murphy:
 
 

  How about:
 
         
  blacklist(${exten});
         
 
  macro blacklist(the_exten)
  {
       switch(the_exten)
       {
       pattern +4390[01]: Hangup();
       default: return;
       }
  }

 Yes, that would work. I didn't knew the pattern statement.

  Basically, you are using the pattern matching capability to
  end the call for certain extensions... so the above should
  come close. If you really, really want to keep your gosub call,
  then you can, you'll just have to ignore the warnings, iirc.

 I think I will just ignore it :-)

 thanks
 klaus


 --
 _
 -- 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

-- 
_
-- 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

Re: [asterisk-users] AEL in 1.6 and Gosub

2010-03-16 Thread Steve Murphy

On Mon, Mar 15, 2010 at 12:47 PM, Klaus Darilion 
klaus.mailingli...@pernau.at wrote:



 Am 15.03.2010 13:48, schrieb Kevin P. Fleming:
  Klaus Darilion wrote:
  Hi!
 
  I just updated from 1.4 to 1.6.2.6 and Asterisk complains about my AEL
  dialplan:
 
  application call to Gosub affects flow of control, and needs to
  be re-written using AEL if, while, goto, etc. keywords instead
 
  What is the suggested replacement for an explicit Gosub() call? I use it
  like this:
 
  ...
  Gosub(blacklist,${exten},1);
  ...
 
  context blacklist {
  _+43900! =  Hangup();
  _+43910! =  Hangup();
  _+X. =  return;
 
  }


How about:

  
  blacklist(${exten});
  

macro blacklist(the_exten)
{
switch(the_exten)
{
pattern +4390[01]: Hangup();
default: return;
}
}

You could use something like the above.

Basically, you are using the pattern matching capability to
end the call for certain extensions... so the above should
come close. If you really, really want to keep your gosub call,
then you can, you'll just have to ignore the warnings, iirc.

murf


  In 1.6, AEL macro() is implemented using Gosub(), so you can use it as a
  direct replacement. This is listed in the CHANGES file.

 Hi Kevin!

 I know that AEL macro does not use Macro() anymore, but Gosub(). But
 does that imply the other way round too?

 Using an AEL macro (which is implemented as Gosub) instead of a Gosub
 does not work as the target is a context, not a macro which is
 implemented as pseudo context with an 's' extension.

 I do not see a way to implement the above dialplan using an AEL macro.
 Do I miss something?

 regards
 Klaus

 --
 _
 -- 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




-- 
Steve Murphy
ParseTree Corp
-- 
_
-- 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

Re: [asterisk-users] AEL in 1.6 and Gosub

2010-03-15 Thread Kevin P. Fleming

Klaus Darilion wrote:
 Hi!
 
 I just updated from 1.4 to 1.6.2.6 and Asterisk complains about my AEL 
 dialplan:
 
application call to Gosub affects flow of control, and needs to
be re-written using AEL if, while, goto, etc. keywords instead
 
 What is the suggested replacement for an explicit Gosub() call? I use it 
 like this:
 
...
Gosub(blacklist,${exten},1);
...
 
 context blacklist {
_+43900! = Hangup();
_+43910! = Hangup();
_+X. = return;
 
 }

In 1.6, AEL macro() is implemented using Gosub(), so you can use it as a
direct replacement. This is listed in the CHANGES file.

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
skype: kpfleming | jabber: kflem...@digium.com
Check us out at www.digium.com  www.asterisk.org

-- 
_
-- 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

Re: [asterisk-users] AEL in 1.6 and Gosub

2010-03-15 Thread Klaus Darilion



Am 15.03.2010 13:48, schrieb Kevin P. Fleming:
 Klaus Darilion wrote:
 Hi!

 I just updated from 1.4 to 1.6.2.6 and Asterisk complains about my AEL
 dialplan:

 application call to Gosub affects flow of control, and needs to
 be re-written using AEL if, while, goto, etc. keywords instead

 What is the suggested replacement for an explicit Gosub() call? I use it
 like this:

 ...
 Gosub(blacklist,${exten},1);
 ...

 context blacklist {
 _+43900! =  Hangup();
 _+43910! =  Hangup();
 _+X. =  return;

 }

 In 1.6, AEL macro() is implemented using Gosub(), so you can use it as a
 direct replacement. This is listed in the CHANGES file.

Hi Kevin!

I know that AEL macro does not use Macro() anymore, but Gosub(). But 
does that imply the other way round too?

Using an AEL macro (which is implemented as Gosub) instead of a Gosub 
does not work as the target is a context, not a macro which is 
implemented as pseudo context with an 's' extension.

I do not see a way to implement the above dialplan using an AEL macro. 
Do I miss something?

regards
Klaus

-- 
_
-- 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

Re: [asterisk-users] AEL, 1.6, CUT and commas [SOLVED]

2009-12-03 Thread Olivier

2009/12/3 Olivier oza-4...@myamail.com

 Hello,

 How can you parse a comma separated list using function CUT and AEL ?

 I've tried but it displays error message (though is seems to find the
 correct value) :

 STRING=101,102
 VAL=${CUT(STRING,\,,1)};
 NoOp(VAL is ${VAL});

 Cheers


Sorry for the noise but I mixed up with another mistake elsewhere in my
code.
The above example works !
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL problem: bug or feature?

2009-10-05 Thread Klaus Darilion

forgot to mention this happens on Asterisk 1.4.26.1

Klaus Darilion schrieb:
 Hi! I have a problem with jump in AEL:
 
  _+43123456789!  =  jump +22;
  +22 = { NoOp(); }
 
 - OK
 
  _+43123456789!  =  jump 22;
  22 = { NoOp(); }
 
 - OK
 
  _+43123456789!  =  jump 22;
  _22 = { NoOp(); }
 
 - OK
 
  _+43123456789!  =  jump +22;
  _+22 = { NoOp(); }
 
 -- AEL compile error:
 LOG: lev:4 file:pbx_ael.c  line:1234 func: check_goto  Error: file 
 ./ofis/extensions.ael_trunking, line 525-525: goto:  no label +22|1 
 exists in the current context, or any of its inclusions!
 
 Is this is some special feature/limitation or just a bug?
 
 thanks
 Klaus
 
 ___
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --
 
 AstriCon 2009 - October 13 - 15 Phoenix, Arizona
 Register Now: http://www.astricon.net
 
 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

AstriCon 2009 - October 13 - 15 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL problem: bug or feature?

2009-10-05 Thread Steve Edwards

On Mon, 5 Oct 2009, Klaus Darilion wrote:

 forgot to mention this happens on Asterisk 1.4.26.1

 Klaus Darilion schrieb:
 Hi! I have a problem with jump in AEL:

  _+43123456789!  =  jump +22;
  +22 = { NoOp(); }

Don't you need another semi-colon after the closing brace?

Since AEL compiles to dialplan, what does the resulting dialplan look 
like?

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

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

AstriCon 2009 - October 13 - 15 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL problem: bug or feature?

2009-10-05 Thread Philipp Kempgen

Klaus Darilion schrieb:
 forgot to mention this happens on Asterisk 1.4.26.1
 
 Klaus Darilion schrieb:
 Hi! I have a problem with jump in AEL:
 
  _+43123456789!  =  jump +22;
  +22 = { NoOp(); }
 
 - OK
 
  _+43123456789!  =  jump 22;
  22 = { NoOp(); }
 
 - OK
 
  _+43123456789!  =  jump 22;
  _22 = { NoOp(); }
 
 - OK
 
  _+43123456789!  =  jump +22;
  _+22 = { NoOp(); }
 
 -- AEL compile error:
 LOG: lev:4 file:pbx_ael.c  line:1234 func: check_goto  Error: file 
 ./ofis/extensions.ael_trunking, line 525-525: goto:  no label +22|1 
 exists in the current context, or any of its inclusions!

Not that it should make a difference (as + is not a special
character in Asterisk's patterns) but did you try
 _+43123456789!  =  jump +22;
 _[+]22 = { NoOp(); }
just in case?

 Is this is some special feature/limitation or just a bug?

Looks like a bug to me.


Philipp Kempgen
-- 
AMOOMA GmbH - Bachstr. 126 - 56566 Neuwied  -  http://www.amooma.de
Geschäftsführer: Stefan Wintermeyer, Handelsregister: Neuwied B14998
Asterisk: http://the-asterisk-book.com - http://das-asterisk-buch.de
Videos of the AMOOCON VoIP conference 2009 -  http://www.amoocon.de
-- 

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

AstriCon 2009 - October 13 - 15 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL problem: bug or feature?

2009-10-05 Thread Klaus Darilion



Steve Edwards schrieb:
 On Mon, 5 Oct 2009, Klaus Darilion wrote:
 
 forgot to mention this happens on Asterisk 1.4.26.1

 Klaus Darilion schrieb:
 Hi! I have a problem with jump in AEL:

  _+43123456789!  =  jump +22;
  +22 = { NoOp(); }
 
 Don't you need another semi-colon after the closing brace?

No. IIRC this was changed from AEL to AEL2.

 Since AEL compiles to dialplan, what does the resulting dialplan look 
 like?

it failes during compilation, thus there is no dialplan generated.

regards
klaus

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

AstriCon 2009 - October 13 - 15 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL problem: bug or feature?

2009-10-05 Thread Klaus Darilion



Philipp Kempgen schrieb:
 Klaus Darilion schrieb:
 forgot to mention this happens on Asterisk 1.4.26.1

 Klaus Darilion schrieb:
 Hi! I have a problem with jump in AEL:

  _+43123456789!  =  jump +22;
  +22 = { NoOp(); }

 - OK

  _+43123456789!  =  jump 22;
  22 = { NoOp(); }

 - OK

  _+43123456789!  =  jump 22;
  _22 = { NoOp(); }

 - OK

  _+43123456789!  =  jump +22;
  _+22 = { NoOp(); }

 -- AEL compile error:
 LOG: lev:4 file:pbx_ael.c  line:1234 func: check_goto  Error: file 
 ./ofis/extensions.ael_trunking, line 525-525: goto:  no label +22|1 
 exists in the current context, or any of its inclusions!
 
 Not that it should make a difference (as + is not a special
 character in Asterisk's patterns) but did you try
  _+43123456789!  =  jump +22;
  _[+]22 = { NoOp(); }
 just in case?

Indeed, that works. Also jump +22${FOO}; works

 
 Is this is some special feature/limitation or just a bug?
 
 Looks like a bug to me.

Me too :-)
https://issues.asterisk.org/view.php?id=16019

regards
klaus

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

AstriCon 2009 - October 13 - 15 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL question: testing channel variables

2009-01-11 Thread Allann Jones

http://www.voip-info.org/wiki-Asterisk+variables
http://www.voip-info.org/wiki-Asterisk+Dialplan+Globals

Beware with the variable scope, if its scope is local the values can
be lost, so declare the variable as global when its value must persist
between calls.

[globals]

   FOOBAR = NO

[some_context]

if (${FOOBAR}=YES) {
   ...
}


On Sat, Jan 10, 2009 at 2:53 PM, Philipp Kempgen
philipp.kemp...@amooma.de wrote:
 Klaus Darilion schrieb:
 I use the following condition:

 if (${FOOBAR}=YES) {
...
 }

 The problem is, that if FOOBAR is not defined at all Asterisk generates
 a warning:

 WARNING[11982]: ast_expr2.fl:407 ast_yyerror: ast_yyerror():  syntax
 error: syntax error, unexpected '=', expecting $end; Input:
 =YES


 Of course I could use the following code, but this bloats up the code:


 if (${EXISTS(${FOOBAR})}) {
if (${FOOBAR}=YES) {
  ...
}
 }


 Is there another syntax to have nice looking code but avoid the warning?

 if (${FOOBAR}=YES) {
   ...
 }

 or

 if (x${FOOBAR}=xYES) {
   ...
 }


   Philipp Kempgen

 --
 AMOOCON 2009, May 4-5, Rostock / Germany   -  http://www.amoocon.de
 Asterisk: http://the-asterisk-book.com - http://das-asterisk-buch.de
 AMOOMA GmbH - Bachstr. 126 - 56566 Neuwied  -  http://www.amooma.de
 Geschäftsführer: Stefan Wintermeyer, Handelsregister: Neuwied B14998
 --

 ___
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users




-- 
___
Allann J. O. Silva

I received the fundamentals of my education in school, but that was
not enough. My real education, the superstructure, the details, the
true architecture, I got out of the public library. For an
impoverished child whose family could not afford to buy books, the
library was the open door to wonder and achievement, and I can never
be sufficiently grateful that I had the wit to charge through that
door and make the most of it. (from I. Asimov, 1994)

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL question: testing channel variables

2009-01-10 Thread Philipp Kempgen

Klaus Darilion schrieb:
 I use the following condition:
 
 if (${FOOBAR}=YES) {
...
 }
 
 The problem is, that if FOOBAR is not defined at all Asterisk generates 
 a warning:
 
 WARNING[11982]: ast_expr2.fl:407 ast_yyerror: ast_yyerror():  syntax 
 error: syntax error, unexpected '=', expecting $end; Input:
 =YES
 
 
 Of course I could use the following code, but this bloats up the code:
 
 
 if (${EXISTS(${FOOBAR})}) {
if (${FOOBAR}=YES) {
  ...
}
 }
 
 
 Is there another syntax to have nice looking code but avoid the warning?

if (${FOOBAR}=YES) {
   ...
}

or

if (x${FOOBAR}=xYES) {
   ...
}


   Philipp Kempgen

-- 
AMOOCON 2009, May 4-5, Rostock / Germany   -  http://www.amoocon.de
Asterisk: http://the-asterisk-book.com - http://das-asterisk-buch.de
AMOOMA GmbH - Bachstr. 126 - 56566 Neuwied  -  http://www.amooma.de
Geschäftsführer: Stefan Wintermeyer, Handelsregister: Neuwied B14998
-- 

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL and };

2009-01-08 Thread Olivier

2009/1/8 Klaus Darilion klaus.mailingli...@pernau.at

 Hi!

 All the AEL examples have a semicolon after the closing curly bracket, e.g:

 context test {
   1 = Hangup();
 };

 but without ; it works fine too, e.g:


 context test {
   1 = Hangup();
 }


 So - what is the reason for the ; after the closing curly bracket?


for syntax edition (ie ael.vim 0.2), this question seems to matter.





 thanks
 klaus

 ___
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL and };

2009-01-08 Thread Watkins, Bradley

 -Original Message-
 From: asterisk-users-boun...@lists.digium.com 
 [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of 
 Klaus Darilion
 Sent: Thursday, January 08, 2009 8:28 AM
 To: Asterisk Users Mailing List - Non-Commercial Discussion
 Subject: [asterisk-users] AEL and };

 Hi!

 All the AEL examples have a semicolon after the closing curly 
 bracket, e.g:

 context test {
1 = Hangup();
 };

 but without ; it works fine too, e.g:

 context test {
1 = Hangup();
 }

 So - what is the reason for the ; after the closing curly bracket?

In the original implementation of AEL, it was required to have the
semicolon after closing a block.  In the new implementation (AEL2), it
is not required but is allowed for backward compatibility with dialplans
written for the earlier parser.

- Brad

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL and };

2009-01-08 Thread Klaus Darilion



Watkins, Bradley schrieb:
  
 
 -Original Message-
 From: asterisk-users-boun...@lists.digium.com 
 [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of 
 Klaus Darilion
 Sent: Thursday, January 08, 2009 8:28 AM
 To: Asterisk Users Mailing List - Non-Commercial Discussion
 Subject: [asterisk-users] AEL and };

 Hi!

 All the AEL examples have a semicolon after the closing curly 
 bracket, e.g:

 context test {
1 = Hangup();
 };

 but without ; it works fine too, e.g:


 context test {
1 = Hangup();
 }


 So - what is the reason for the ; after the closing curly bracket?

 
 In the original implementation of AEL, it was required to have the
 semicolon after closing a block.  In the new implementation (AEL2), it
 is not required but is allowed for backward compatibility with dialplans
 written for the earlier parser.

sounds logical

thanks
klaus

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL question: testing channel variables

2009-01-08 Thread Julian Lyndon-Smith

Klaus Darilion wrote:
 Hi!

 I use the following condition:

 if (${FOOBAR}=YES) {
...
 }

 The problem is, that if FOOBAR is not defined at all Asterisk generates 
 a warning:

 WARNING[11982]: ast_expr2.fl:407 ast_yyerror: ast_yyerror():  syntax 
 error: syntax error, unexpected '=', expecting $end; Input:
 =YES


 Of course I could use the following code, but this bloats up the code:


 if (${EXISTS(${FOOBAR})}) {
if (${FOOBAR}=YES) {
  ...
}
 }


 Is there another syntax to have nice looking code but avoid the warning?
   

How about

if (${FOOBAR}=YES) {

Julian
 thanks
 klaus

 ___
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users

   


__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
__

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL question: testing channel variables

2009-01-08 Thread Steve Murphy

On Thu, 2009-01-08 at 19:24 +0100, Klaus Darilion wrote:
 Hi!
 
 I use the following condition:
 
 if (${FOOBAR}=YES) {
...
 }
 
 The problem is, that if FOOBAR is not defined at all Asterisk generates 
 a warning:
 
 WARNING[11982]: ast_expr2.fl:407 ast_yyerror: ast_yyerror():  syntax 
 error: syntax error, unexpected '=', expecting $end; Input:
 =YES
 
 
 Of course I could use the following code, but this bloats up the code:
 
 
 if (${EXISTS(${FOOBAR})}) {
if (${FOOBAR}=YES) {
  ...
}
 }
 
 
 Is there another syntax to have nice looking code but avoid the warning?

Klaus--

The simplest I can think of is:

if (${FOOBAR}=YES) {
   ...
}

adding the quotes just makes it so if ${FOOBAR} evaluates to nothing,
then it will still end being a token, and you avoid the syntax error.

You have to keep in mind that by the time the $[ ... ] exprs are evaluated,
all ${..} constructs have been recursively evaluated away.

the wiki is a good reference for AEL2... 
(http://voip-info.org/wiki/view/Asterisk+AEL2
and there is a page of example snippets.

murf


 
 thanks
 klaus

-- 
Steve Murphy m...@digium.com
Digium


smime.p7s
Description: S/MIME cryptographic signature
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL question: testing channel variables

2009-01-08 Thread Brent Vrieze

Initialize FOOBAR to some know value (ie NO) and change it when you need 
to.  Then it will always be defined.

Klaus Darilion wrote:
 Hi!

 I use the following condition:

 if (${FOOBAR}=YES) {
...
 }

 The problem is, that if FOOBAR is not defined at all Asterisk generates 
 a warning:

 WARNING[11982]: ast_expr2.fl:407 ast_yyerror: ast_yyerror():  syntax 
 error: syntax error, unexpected '=', expecting $end; Input:
 =YES


 Of course I could use the following code, but this bloats up the code:


 if (${EXISTS(${FOOBAR})}) {
if (${FOOBAR}=YES) {
  ...
}
 }


 Is there another syntax to have nice looking code but avoid the warning?

 thanks
 klaus

 ___
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users


   

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL Variable Warning Messages

2009-01-05 Thread Brent Davidson


Watkins, Bradley wrote:



From: asterisk-users-boun...@lists.digium.com


[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Brent
Davidson
  

Sent: Wednesday, December 31, 2008 1:03 PM
To: m...@digium.com; Asterisk Users Mailing List -


Non-Commercial Discussion
  

Subject: Re: [asterisk-users] AEL Variable Warning Messages

Well, before I file a bug I have another question...  In AEL,


what is the correct syntax?  Do all variable references still need to be
wrapped in ${} or not?  If they do, then the documentation on
voip-info.org needs to be changed to reflect that.

Yes, variable references need to be wrapped in ${}.  Where on the wiki
do you see an example that is otherwise?  I just looked at the main
documentation for AEL, and I didn't see any instances of it.  Certainly
they can and should be fixed if they are there.
  


Beyond that, what are the rules for putting the values assigned


to variables in quotes?  In my example above, at one point I had a space
between the = and the Zap/r2 statement with no quotes.  The value
assigned to TRUNK then included a leading space.  I didn't test to see
whether or not putting a space after the variable name adds a space to
the variables name.  I would think that any spaces after an operator
should be ignored unless the come after a single or double quote.

The rules are that there aren't any really.  Neither a single- nor
double-quote have any specific meaning in the sense of signifying a
string.  I'm also curious to know where you saw an example of assignment
that used quotes of any kind, since I can't find that either.

Regards,
- Brad
  
Both the AEL and AEL2 examples include the following examples in the 
Variables section:


---HTML Copied from WIKI page 
http://www.voip-info.org/wiki/view/Asterisk+AEL---



   Variables

Variables in Asterisk do not have a type, so to define a variable, it 
just has to be specified with a value.


Global variables are set in their own block.

globals {
   CONSOLE=Console/dsp;
   TRUNK=Zap/g2;
};

*NOTE:* The opening curly-brace must appear as above. Moving it to the 
following line may have disastrous consequences!


Variables can be set within extensions as well.


context foo {
   555 = {
x=5;
y=blah;
divexample=10/2
NoOp(x is ${x} and y is ${y} !);
   };
};


*NOTE:* Asterisk beta1 parses assignments using a $[] wrapper as opposed 
to the more logical way of doing it like Set and SetVar work. In this 
example, I had ${ARG1} set to SIP/x7065558529 sans-quotes and it 
flunked out.
*NOTE:* Another opinion: The $[ ] allow expressions to be used, and add 
extra power to the language. Read the README.variables about the 
requirements of $ http://www.voip-info.org/wiki/view/Asterisk+AEL 
expressions. In the following example, the SIP/x7065558529
 should not be sans quotes. So, the statement might have been entered:  requesting_channel=${ARG1};( where the 's prevent the evaluation. ) 

*NOTE:* These things are wrapped up in a $[ ] expression: The while() 
test; the if() test; the middle expression in the for( x; y; z) 
statement (the y expression); Assignments --- the right hand side, so a 
= b - Set(a=$[b])


requesting_channel=${ARG1}
ERROR: Oct 10 12:48:59 WARNING[19726]: ast_expr2.y:811 op_div: 
non-numeric argument
  --- Executing Set(SIP/x7065558529-2afd, requesting_channel=0) in new stack 


FROM show dialplan:
's' =1. Set(requesting_channel=$[ ${ARG1} ])   [pbx_ael]

But you can use Set and it works the old way.

Set(requesting_channel=${ARG1})


Writing to a dialplan function is treated the same as writing to a 
variable.



context blah {
   s = {
CALLERID(name)=ChickenMan;
NoOp(My name is ${CALLERID(name)} !);
   };
}; 


---END HTML Copied from WIKI---

I see the line about using the old Set syntax, but the examples and the 
rest of the notes imply that that you could just do x=5; rather than 
${x}=5; and get the same result either way.


Another question along these lines...  If I set a Global called TRUNK 
in the globals section and later assign do a TRUNK=whatever it appears 
that a local variable called TRUNK is created instead of using the 
global.  You must explicitly use the Set(GLOBAL(TRUNK)=whatever) syntax 
to alter the global.


As far as the quotes go, I resorted to using them in an effort to get 
rid of that extra space at the beginning of my value.  I just figured 
that if the examples were wrong on one aspect that maybe they were off 
in other ways as well.


The examples in the Macros and Conditionals sections of AEL shows 
the variables with the curly brace syntax, but the loops section uses 
both syntaxes in it's examples.


I would be happy to help clean up the examples on the wiki as long as 
I'm sure I know what I'm doing.  As for my dialplan, I've reverted to 
using the Set

Re: [asterisk-users] AEL Variable Warning Messages

2009-01-05 Thread Benoit

Brent Davidson a écrit :
 Watkins, Bradley wrote:
 ...
 Well, before I file a bug I have another question...  In AEL,
 
 what is the correct syntax?  Do all variable references still need to be
 wrapped in ${} or not?  If they do, then the documentation on
 voip-info.org needs to be changed to reflect that.

 Yes, variable references need to be wrapped in ${}.  Where on the wiki
 do you see an example that is otherwise?  I just looked at the main
 documentation for AEL, and I didn't see any instances of it.  Certainly
 they can and should be fixed if they are there.
 ..

 I see the line about using the old Set syntax, but the examples and
 the rest of the notes imply that that you could just do x=5; rather
 than ${x}=5; and get the same result either way.
Well, the process of declaring/assigning a value to a variable isn't the
same a refering a variable.
And the wiki example are correct, you can assign a value with x=0;,
but to display this value
(by referring to the variable) you have to do NoOp(${x});.


 Another question along these lines...  If I set a Global called
 TRUNK in the globals section and later assign do a TRUNK=whatever it
 appears that a local variable called TRUNK is created instead of using
 the global.  You must explicitly use the Set(GLOBAL(TRUNK)=whatever)
 syntax to alter the global.
And the question is ?



___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL Variable Warning Messages

2009-01-05 Thread Brent Davidson


Benoit wrote:

Brent Davidson a écrit :
  

Another question along these lines...  If I set a Global called
TRUNK in the globals section and later assign do a TRUNK=whatever it
appears that a local variable called TRUNK is created instead of using
the global.  You must explicitly use the Set(GLOBAL(TRUNK)=whatever)
syntax to alter the global.


And the question is ?
I guess my question was whether or not the above is the intended 
behavior.  It seems to me that if you declare a global, then later use 
the same name it should refer to the global without having to use the 
old syntax.
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL Variable Warning Messages

2008-12-31 Thread Brent Davidson


Steve Murphy wrote:

On Tue, 2008-12-23 at 12:14 -0600, Brent Davidson wrote:
  
I have two offices sharing a phone system.  They also share a common 
internal context because all of the employees of the second office also 
work for the first office.  Each office has 4 outside lines and I have 
defined 2 channel groups in my zapata.conf.  The second office needs all 
of their outgoing calls to go out over their lines so the people they 
call will have the correct callerID.  I created an asterisk database and 
with entries in the database for all extensions in the second office and 
defined the following macro:


globals {
  CONSOLE=Console/dsp;
  TRUNK=Zap/r1;
  TCTC_Operator=15;
  Law_Operator=12;
};

macro outside-dial ( num ) {
  if (${DB_EXISTS(Office/${CALLERID(num)})}) {
TRUNK=Zap/r2;
  } else {
TRUNK=Zap/r1;
  }
  Dial(${TRUNK}/${num},,Ttok);
}

It's working and correctly routing outside calls, but I get the 
following messages when I reload the extensions.ael file:


[Dec 23 12:16:22] WARNING[2994]: pbx_ael.c:2500 check_pval_item: 
Warning: file /etc/asterisk/extensions.ael, line 93-93: expression 
Zap/r2 has operators, but no variables. Interesting...
[Dec 23 12:16:22] WARNING[2994]: pbx_ael.c:2500 check_pval_item: 
Warning: file /etc/asterisk/extensions.ael, line 95-95: expression 
Zap/r1 has operators, but no variables. Interesting...


Any idea what is causing the warnings?



Yes, I do! I was concerned that users were falling into a common
error, where they forget to wrap variable references in $(); so,
if it looks like an expr has arithmetic operators, but no variable
refs, then you get this message.

Yes, I *could* have made it more intelligent. File a bug, and I'll
see if I can do so. At the worst, you can ignore this warning, or
I can simply remove this overly-simple warning.

murf
  
Well, before I file a bug I have another question...  In AEL, what is 
the correct syntax?  Do all variable references still need to be wrapped 
in ${} or not?  If they do, then the documentation on voip-info.org 
needs to be changed to reflect that.


Beyond that, what are the rules for putting the values assigned to 
variables in quotes?  In my example above, at one point I had a space 
between the = and the Zap/r2 statement with no quotes.  The value 
assigned to TRUNK then included a leading space.  I didn't test to see 
whether or not putting a space after the variable name adds a space to 
the variables name.  I would think that any spaces after an operator 
should be ignored unless the come after a single or double quote.


Thanks,
Brent
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL Variable Warning Messages

2008-12-31 Thread Watkins, Bradley

   From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Brent
Davidson
   Sent: Wednesday, December 31, 2008 1:03 PM
   To: m...@digium.com; Asterisk Users Mailing List -
Non-Commercial Discussion
   Subject: Re: [asterisk-users] AEL Variable Warning Messages

   Well, before I file a bug I have another question...  In AEL,
what is the correct syntax?  Do all variable references still need to be
wrapped in ${} or not?  If they do, then the documentation on
voip-info.org needs to be changed to reflect that.

Yes, variable references need to be wrapped in ${}.  Where on the wiki
do you see an example that is otherwise?  I just looked at the main
documentation for AEL, and I didn't see any instances of it.  Certainly
they can and should be fixed if they are there.

   Beyond that, what are the rules for putting the values assigned
to variables in quotes?  In my example above, at one point I had a space
between the = and the Zap/r2 statement with no quotes.  The value
assigned to TRUNK then included a leading space.  I didn't test to see
whether or not putting a space after the variable name adds a space to
the variables name.  I would think that any spaces after an operator
should be ignored unless the come after a single or double quote.

The rules are that there aren't any really.  Neither a single- nor
double-quote have any specific meaning in the sense of signifying a
string.  I'm also curious to know where you saw an example of assignment
that used quotes of any kind, since I can't find that either.

Regards,
- Brad

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL Variable Warning Messages

2008-12-29 Thread Steve Murphy

On Tue, 2008-12-23 at 12:14 -0600, Brent Davidson wrote:
 I have two offices sharing a phone system.  They also share a common 
 internal context because all of the employees of the second office also 
 work for the first office.  Each office has 4 outside lines and I have 
 defined 2 channel groups in my zapata.conf.  The second office needs all 
 of their outgoing calls to go out over their lines so the people they 
 call will have the correct callerID.  I created an asterisk database and 
 with entries in the database for all extensions in the second office and 
 defined the following macro:
 
 globals {
   CONSOLE=Console/dsp;
   TRUNK=Zap/r1;
   TCTC_Operator=15;
   Law_Operator=12;
 };
 
 macro outside-dial ( num ) {
   if (${DB_EXISTS(Office/${CALLERID(num)})}) {
 TRUNK=Zap/r2;
   } else {
 TRUNK=Zap/r1;
   }
   Dial(${TRUNK}/${num},,Ttok);
 }
 
 It's working and correctly routing outside calls, but I get the 
 following messages when I reload the extensions.ael file:
 
 [Dec 23 12:16:22] WARNING[2994]: pbx_ael.c:2500 check_pval_item: 
 Warning: file /etc/asterisk/extensions.ael, line 93-93: expression 
 Zap/r2 has operators, but no variables. Interesting...
 [Dec 23 12:16:22] WARNING[2994]: pbx_ael.c:2500 check_pval_item: 
 Warning: file /etc/asterisk/extensions.ael, line 95-95: expression 
 Zap/r1 has operators, but no variables. Interesting...
 
 Any idea what is causing the warnings?

Yes, I do! I was concerned that users were falling into a common
error, where they forget to wrap variable references in $(); so,
if it looks like an expr has arithmetic operators, but no variable
refs, then you get this message.

Yes, I *could* have made it more intelligent. File a bug, and I'll
see if I can do so. At the worst, you can ignore this warning, or
I can simply remove this overly-simple warning.

murf


 
 Thanks,
 Brent

-- 
 Steve Murphy
Digium, Inc. | Software Developer
57 Lane 17, Cody, WY 82414 USA
direct: +1 256-428-6002
mobile: +1 307-899-5535
fax/home: +1 307-754-5675
irc: codefreeze | jabber: m...@digium.com
Check us out at: www.digium.com  www.asterisk.org



smime.p7s
Description: S/MIME cryptographic signature
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL: how to check if variable is defined

Klaus Darilion schrieb:
 I use an if condition in extensions.ael to check if a channel variable 
 is defined and if defined I add a certain header:
 
 context toNormaleRufe {
_X. = {
 if (${NUMBER}) {
 SIPAddHeader(X-NUMBER: ${NUMBER});
 };
 ...
};
 
 This works fine, except NUMBER starts with the + sign.
 
 I tried using quotes but
 if (${NUMBER})
 evaluates always true.
 
 What is the suggested way to solve this?

if (${NUMBER} != ) {
// ...
}

That doesn't tell you whether the variable is defined but in
most cases (if any) that doesn't matter anyway.

   Philipp Kempgen

-- 
http://www.das-asterisk-buch.de  -  http://www.the-asterisk-book.com
Amooma GmbH - Bachstr. 126 - 56566 Neuwied  -  http://www.amooma.de
Geschäftsführer: Stefan Wintermeyer, Handelsregister: Neuwied B14998
-- 

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL: how to check if variable is defined

Philipp Kempgen schrieb:
 Klaus Darilion schrieb:
 I use an if condition in extensions.ael to check if a channel variable 
 is defined and if defined I add a certain header:
 
 context toNormaleRufe {
_X. = {
 if (${NUMBER}) {
 SIPAddHeader(X-NUMBER: ${NUMBER});
 };
 ...
};
 
 This works fine, except NUMBER starts with the + sign.
 
 I tried using quotes but
 if (${NUMBER})
 evaluates always true.
 
 What is the suggested way to solve this?
 
 if (${NUMBER} != ) {
 // ...
 }
 
 That doesn't tell you whether the variable is defined but in
 most cases (if any) that doesn't matter anyway.

But I guess it wouldn't hurt to add a DEFINED() function to
Asterisk.

if (DEFINED(myvariable)) {
// ...
}


   Philipp Kempgen

-- 
http://www.das-asterisk-buch.de  -  http://www.the-asterisk-book.com
Amooma GmbH - Bachstr. 126 - 56566 Neuwied  -  http://www.amooma.de
Geschäftsführer: Stefan Wintermeyer, Handelsregister: Neuwied B14998
-- 

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL: how to check if variable is defined

2008-12-29 Thread Richard Lyman

Philipp Kempgen wrote:
*snipped
 But I guess it wouldn't hurt to add a DEFINED() function to
 Asterisk.

 if (DEFINED(myvariable)) {
 // ...
 }
   
Isn't that what ISNULL is for?

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL: how to check if variable is defined

2008-12-29 Thread Dave Fullerton

Philipp Kempgen wrote:
 Philipp Kempgen schrieb:
 Klaus Darilion schrieb:
 I use an if condition in extensions.ael to check if a channel variable 
 is defined and if defined I add a certain header:

 context toNormaleRufe {
_X. = {
 if (${NUMBER}) {
 SIPAddHeader(X-NUMBER: ${NUMBER});
 };
 ...
};

 This works fine, except NUMBER starts with the + sign.

 I tried using quotes but
 if (${NUMBER})
 evaluates always true.

 What is the suggested way to solve this?
 if (${NUMBER} != ) {
 // ...
 }

 That doesn't tell you whether the variable is defined but in
 most cases (if any) that doesn't matter anyway.
 
 But I guess it wouldn't hurt to add a DEFINED() function to
 Asterisk.
 
 if (DEFINED(myvariable)) {
 // ...
 }
 

Isn't that what EXISTS() is for?

-Dave

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL: how to check if variable is defined

Dave Fullerton schrieb:
 Philipp Kempgen wrote:

 But I guess it wouldn't hurt to add a DEFINED() function to
 Asterisk.
 
 if (DEFINED(myvariable)) {
 // ...
 }
 
 
 Isn't that what EXISTS() is for?

Well, yes.  :-)
I've never needed it before and it didn't come to my mind.


   Philipp Kempgen

-- 
http://www.das-asterisk-buch.de  -  http://www.the-asterisk-book.com
Amooma GmbH - Bachstr. 126 - 56566 Neuwied  -  http://www.amooma.de
Geschäftsführer: Stefan Wintermeyer, Handelsregister: Neuwied B14998
-- 

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL: how to check if variable is defined

Richard Lyman schrieb:
 Philipp Kempgen wrote:

 But I guess it wouldn't hurt to add a DEFINED() function to
 Asterisk.

 if (DEFINED(myvariable)) {
 // ...
 }
   
 Isn't that what ISNULL is for?

No. ISNULL() works on values not on variables.

But Dave Fullerton found EXISTS():
http://lists.digium.com/pipermail/asterisk-users/2008-December/224059.html


   Philipp Kempgen

-- 
http://www.das-asterisk-buch.de  -  http://www.the-asterisk-book.com
Amooma GmbH - Bachstr. 126 - 56566 Neuwied  -  http://www.amooma.de
Geschäftsführer: Stefan Wintermeyer, Handelsregister: Neuwied B14998
-- 

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL: how to check if variable is defined

2008-12-29 Thread Richard Lyman

Philipp Kempgen wrote:
 Richard Lyman schrieb:
   
 Philipp Kempgen wrote:
 

   
 But I guess it wouldn't hurt to add a DEFINED() function to
 Asterisk.

 if (DEFINED(myvariable)) {
 // ...
 }
   
   
 Isn't that what ISNULL is for?
 

 No. ISNULL() works on values not on variables.

 But Dave Fullerton found EXISTS():
 http://lists.digium.com/pipermail/asterisk-users/2008-December/224059.html


Philipp Kempgen

   
if (${ISNULL(${CAMPAIGN})}) {
Set(CAMPAIGN=INBOUND);
};

This is how i use it.


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL: how to check if variable is defined

2008-12-29 Thread Klaus Darilion

Thanks Dave, Philipp and Richard!

klaus

Richard Lyman wrote:
 Philipp Kempgen wrote:
 Richard Lyman schrieb:
   
 Philipp Kempgen wrote:
 
   
 But I guess it wouldn't hurt to add a DEFINED() function to
 Asterisk.

 if (DEFINED(myvariable)) {
 // ...
 }
   
   
 Isn't that what ISNULL is for?
 
 No. ISNULL() works on values not on variables.

 But Dave Fullerton found EXISTS():
 http://lists.digium.com/pipermail/asterisk-users/2008-December/224059.html


Philipp Kempgen

   
 if (${ISNULL(${CAMPAIGN})}) {
 Set(CAMPAIGN=INBOUND);
 };
 
 This is how i use it.
 
 
 ___
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --
 
 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL Variable Warning Messages

2008-12-23 Thread Philipp Kempgen

Brent Davidson schrieb:

 macro outside-dial ( num ) {
   if (${DB_EXISTS(Office/${CALLERID(num)})}) {
 TRUNK=Zap/r2;
   } else {
 TRUNK=Zap/r1;
   }
   Dial(${TRUNK}/${num},,Ttok);
 }

 [Dec 23 12:16:22] WARNING[2994]: pbx_ael.c:2500 check_pval_item: 
 Warning: file /etc/asterisk/extensions.ael, line 93-93: expression 
 Zap/r2 has operators, but no variables. Interesting...
 [Dec 23 12:16:22] WARNING[2994]: pbx_ael.c:2500 check_pval_item: 
 Warning: file /etc/asterisk/extensions.ael, line 95-95: expression 
 Zap/r1 has operators, but no variables. Interesting...

I'd suggest
Set(TRUNK=Zap/r2);
resp.
Set(TRUNK=Zap/r1);


   Philipp Kempgen

-- 
http://www.das-asterisk-buch.de  -  http://www.the-asterisk-book.com
Amooma GmbH - Bachstr. 126 - 56566 Neuwied  -  http://www.amooma.de
Geschäftsführer: Stefan Wintermeyer, Handelsregister: Neuwied B14998
-- 

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL Variable Warning Messages


Philipp Kempgen wrote:

Brent Davidson schrieb:

  

macro outside-dial ( num ) {
  if (${DB_EXISTS(Office/${CALLERID(num)})}) {
TRUNK=Zap/r2;
  } else {
TRUNK=Zap/r1;
  }
  Dial(${TRUNK}/${num},,Ttok);
}



  
[Dec 23 12:16:22] WARNING[2994]: pbx_ael.c:2500 check_pval_item: 
Warning: file /etc/asterisk/extensions.ael, line 93-93: expression 
Zap/r2 has operators, but no variables. Interesting...
[Dec 23 12:16:22] WARNING[2994]: pbx_ael.c:2500 check_pval_item: 
Warning: file /etc/asterisk/extensions.ael, line 95-95: expression 
Zap/r1 has operators, but no variables. Interesting...



I'd suggest
Set(TRUNK=Zap/r2);
resp.
Set(TRUNK=Zap/r1);


   Philipp Kempgen

  


According to the AEL Documentation I should be able to set variables 
without using the Set command.  They even give the following example:


context foo {
   555 = {
x=5;
y=blah;
divexample=10/2
NoOp(x is ${x} and y is ${y} !);
   };
};

I wonder if maybe AEL is ignoring the double quotes and treating the 
Zap/r2 as if it were division???  Should I file a bug report on this?



___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL Variable Warning Messages

2008-12-23 Thread Dave Fullerton

Brent Davidson wrote:
 Philipp Kempgen wrote:
 Brent Davidson schrieb:

  
 macro outside-dial ( num ) {
   if (${DB_EXISTS(Office/${CALLERID(num)})}) {
 TRUNK=Zap/r2;
   } else {
 TRUNK=Zap/r1;
   }
   Dial(${TRUNK}/${num},,Ttok);
 }
 

  
 [Dec 23 12:16:22] WARNING[2994]: pbx_ael.c:2500 check_pval_item: 
 Warning: file /etc/asterisk/extensions.ael, line 93-93: expression 
 Zap/r2 has operators, but no variables. Interesting...
 [Dec 23 12:16:22] WARNING[2994]: pbx_ael.c:2500 check_pval_item: 
 Warning: file /etc/asterisk/extensions.ael, line 95-95: expression 
 Zap/r1 has operators, but no variables. Interesting...
 

 I'd suggest
 Set(TRUNK=Zap/r2);
 resp.
 Set(TRUNK=Zap/r1);


Philipp Kempgen

   
 
 According to the AEL Documentation I should be able to set variables 
 without using the Set command.  They even give the following example:
 
 context foo {
555 = {
 x=5;
 y=blah;
 divexample=10/2
 NoOp(x is ${x} and y is ${y} !);
};
 };
 
 I wonder if maybe AEL is ignoring the double quotes and treating the 
 Zap/r2 as if it were division???  Should I file a bug report on this?
 

I had gotten similar messages when I forgot to put quotes around 
channels like that (took me forever to realize that one). Since you have 
them I would say this is a bug. What version of asterisk are you running?

-Dave

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL Variable Warning Messages

Dave Fullerton wrote:
 I had gotten similar messages when I forgot to put quotes around 
 channels like that (took me forever to realize that one). Since you have 
 them I would say this is a bug. What version of asterisk are you running?

 -Dave
I'm running 1.4.21.2 and I can't upgrade until Oslec works reliably with 
DAHDI and Rhino RCBFX card.  I tried doing a new install with 1.4.22 
yesterday and couldn't get Oslec to work correctly with the Rhino card 
when running with DAHDI instead of zaptel.  Unfortunately 1.4.22 no 
longer has Zaptel.  :(

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL Variable Warning Messages

2008-12-23 Thread Jeff LaCoursiere



On Tue, 23 Dec 2008, Brent Davidson wrote:

 Dave Fullerton wrote:
 I had gotten similar messages when I forgot to put quotes around
 channels like that (took me forever to realize that one). Since you have
 them I would say this is a bug. What version of asterisk are you running?

 -Dave
 I'm running 1.4.21.2 and I can't upgrade until Oslec works reliably with
 DAHDI and Rhino RCBFX card.  I tried doing a new install with 1.4.22
 yesterday and couldn't get Oslec to work correctly with the Rhino card
 when running with DAHDI instead of zaptel.  Unfortunately 1.4.22 no
 longer has Zaptel.  :(


Why do you need oslec to work with the rhino card - it has hardware echo 
cancellation built in doesn't it?

j

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL Variable Warning Messages

2008-12-23 Thread Tzafrir Cohen

On Tue, Dec 23, 2008 at 03:09:51PM -0600, Brent Davidson wrote:

 Unfortunately 1.4.22 no 
 longer has Zaptel.  :(

Asterisk 1.4.22 builds with both Zaptel and DAHDI.

-- 
   Tzafrir Cohen
icq#16849755  jabber:tzafrir.co...@xorcom.com
+972-50-7952406   mailto:tzafrir.co...@xorcom.com
http://www.xorcom.com  iax:gu...@local.xorcom.com/tzafrir

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL Variable Warning Messages


Tzafrir Cohen wrote:

On Tue, Dec 23, 2008 at 03:09:51PM -0600, Brent Davidson wrote:

  
Unfortunately 1.4.22 no 
longer has Zaptel.  :(



Asterisk 1.4.22 builds with both Zaptel and DAHDI.

  
I spent several hours trying to make it work yesterday and it just 
wouldn't.  I kept getting an error message that it was unable to bind 
the echo canceler to channel 1.  It might have something to do with the 
RCBFX drivers, I'm not sure.  I found your page and followed your 
instructions.  Everything appeared to work until I checked with 
dahdi_cfg -vv.  That's where I got the message.  Don't have my notes 
here so I don't have the actual error message right now.




--
Brent Davidson
I.T. Manager
Texas Country Title Company
112 W 2nd / P.O. Box 663
Cameron, TX 76520
254-605-0140 ex. 21

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL Variable Warning Messages


Jeff LaCoursiere wrote:

On Tue, 23 Dec 2008, Brent Davidson wrote:

  

Dave Fullerton wrote:


I had gotten similar messages when I forgot to put quotes around
channels like that (took me forever to realize that one). Since you have
them I would say this is a bug. What version of asterisk are you running?

-Dave
  

I'm running 1.4.21.2 and I can't upgrade until Oslec works reliably with
DAHDI and Rhino RCBFX card.  I tried doing a new install with 1.4.22
yesterday and couldn't get Oslec to work correctly with the Rhino card
when running with DAHDI instead of zaptel.  Unfortunately 1.4.22 no
longer has Zaptel.  :(




Why do you need oslec to work with the rhino card - it has hardware echo 
cancellation built in doesn't it?


j
  


The Rhino card is supposed to have hardware echo cancellation.  That's 
one of the main reasons I switched to that card from the X-100p's I was 
using.  Unfortunately, either I don't know how to turn on the hardware 
echo cancellation or it just doesn't work.  I have 5  separate location 
where I'm using that card and if I turn off Oslec at any of them the 
echo is so bad that the systems is virtually unusable.  With Oslec 
enabled, however, there is no echo at all.



___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL Variable Warning Messages

2008-12-23 Thread Tzafrir Cohen

On Tue, Dec 23, 2008 at 04:01:24PM -0600, Brent Davidson wrote:
 Tzafrir Cohen wrote:
 On Tue, Dec 23, 2008 at 03:09:51PM -0600, Brent Davidson wrote:
 
   
 Unfortunately 1.4.22 no 
 longer has Zaptel.  :(
 
 
 Asterisk 1.4.22 builds with both Zaptel and DAHDI.
 
   
 I spent several hours trying to make it work yesterday and it just 
 wouldn't.  I kept getting an error message that it was unable to bind 
 the echo canceler to channel 1.  

What error message from where?

With Zaptel the echo canceller settings are global (that is: one
hard-coded echo canceller). With DAHDI there are echo canceller modules
and you can (and actually need to) set them per-channel.

 It might have something to do with the 
 RCBFX drivers, I'm not sure.  I found your page and followed your 
 instructions.  Everything appeared to work until I checked with 
 dahdi_cfg -vv.  That's where I got the message.  Don't have my notes 
 here so I don't have the actual error message right now.
 
 
 
 -- 
 Brent Davidson
 I.T. Manager
 Texas Country Title Company
 112 W 2nd / P.O. Box 663
 Cameron, TX 76520
 254-605-0140 ex. 21
 

 ___
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --
 
 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users

-- 
   Tzafrir Cohen
icq#16849755  jabber:tzafrir.co...@xorcom.com
+972-50-7952406   mailto:tzafrir.co...@xorcom.com
http://www.xorcom.com  iax:gu...@local.xorcom.com/tzafrir

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] AEL Variable Warning Messages