Re: [asterisk-users] AEL Variable Warning Messages
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
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
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
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
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
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
[asterisk-users] AEL Variable Warning Messages
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?
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
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
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
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
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
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
Tzafrir Cohen wrote: 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. I don't remember the actual error name, but it showed up when I did dahdi_cfg -vv. It was something like DAHDI_ATTACH_ECHO_CANCELLER Failed for Channel 1. Unsupported command (22). I was trying to see if maybe it was logged to my syslog but this is all I find in my /var/log/messages: Dec 22 17:01:43 localhost modprobe: FATAL: Error inserting dahdi_echocan_oslec (/lib/modules/2.6.23.8x86_64/dahdi/dahdi_echocan_osle c.ko): Unknown symbol in module, or unknown parameter (see dmesg) Dec 22 17:01:43 localhost kernel: rcbfx 1: Spotted a Rhino: Rhino RCB4FXO (4 channels) Dec 22 17:01:43 localhost kernel: dahdi_echocan_oslec: Unknown symbol oslec_create Dec 22 17:01:43 localhost kernel: dahdi_echocan_oslec: Unknown symbol oslec_update Dec 22 17:01:43 localhost kernel: dahdi_echocan_oslec: Unknown symbol oslec_free Also, when using the Dahdi/Oslec/RCBFX combination I was getting tons of blocks like this in my syslog: Dec 22 16:54:58 localhost kernel: 80c = 2c7e5000 Dec 22 16:54:58 localhost kernel: 810 = 240 Dec 22 16:54:59 localhost kernel: 814 = 0 Dec 22 16:55:00 localhost kernel: 818 = 0 Dec 22 16:55:00 localhost kernel: 81c = 0 Dec 22 16:55:00 localhost kernel: 820 = Dec 22 16:55:01 localhost kernel: 824 = Dec 22 16:55:01 localhost kernel: 828 = Dec 22 16:55:02 localhost kernel: 82c = 0 Dec 22 16:55:02 localhost kernel: 830 = Dec 22 16:55:02 localhost kernel: 834 = Dec 22 16:55:02 localhost kernel: 838 = Dec 22 16:55:03 localhost kernel: 83c = 0 Dec 22 16:55:03 localhost kernel: 840 = 3 Dec 22 16:55:04 localhost kernel: 844 = f Dec 22 16:55:04 localhost kernel: 848 = Dec 22 16:55:04 localhost kernel: 84c = 0 Dec 22 16:55:04 localhost kernel: 850 = 0 Dec 22 16:55:05 localhost kernel: 854 = 10f Dec 22 16:55:05 localhost kernel: 858 = 14e00ff Dec 22 16:55:12 localhost kernel: 85c = 3d434310 Dec 22 16:55:13 localhost kernel: 860 = 0 Dec 22 16:55:13 localhost kernel: 864 = 0 Dec 22 16:55:18 localhost kernel: 868 = 229e229e Dec 22 16:55:18 localhost kernel: 86c = 0 Dec 22 16:55:19 localhost kernel: 870 = 5 Dec 22 16:55:19 localhost kernel: 874 = 5 Dec 22 16:55:20 localhost kernel: 878 = Dec 22 16:55:20 localhost kernel: 87c = 0 Dec 22 16:55:21 localhost kernel: 880 = 0 Dec 22 16:55:21 localhost kernel: 884 = 0 Dec 22 16:55:21 localhost kernel: 888 = 0 Dec 22 16:55:22 localhost kernel: 88c = 0 Dec 22 16:55:22 localhost kernel: 890 = 0 Dec 22 16:55:22 localhost kernel: 894 = 0 Dec 22 16:55:24 localhost kernel: 898 = 0 Dec 22 16:55:26 localhost kernel: 89c = 0 Dec 22 16:55:28 localhost kernel: 8a0 = 0 Dec 22 16:55:28 localhost kernel: 8a4 = 0 Dec 22 16:55:28 localhost kernel: 8a8 = 0 Dec 22 16:55:28 localhost kernel: 8ac = 0 Dec 22 16:55:28 localhost kernel: 8b0 = 0 Dec 22 16:55:28 localhost kernel: 8b4 = 0 Dec 22 16:55:28 localhost kernel: 8b8 = 0 Dec 22 16:55:28 localhost kernel: 8bc = 0 Dec 22 16:55:28 localhost kernel: 8c0 = 0 Dec 22 16:55:28 localhost kernel: 8c4 = 0 Dec 22 16:55:28 localhost kernel: 8c8 = 0 Dec 22 16:55:28 localhost kernel: 8cc = 0 Dec 22 16:55:28 localhost kernel: 8d0 = 0 Dec 22 16:55:28 localhost kernel: 8d4 = 0 Dec 22 16:55:28 localhost kernel: 8d8 = 0 Dec 22 16:55:28 localhost kernel: 8dc = 0 Dec 22 16:55:28 localhost kernel: 8e0 = 0 Dec 22 16:55:28 localhost kernel: 8e4 = 0 Dec 22 16:55:28 localhost kernel: 8e8 = 0 Dec 22 16:55:28 localhost kernel: 8ec = 0 Dec 22 16:55:29 localhost kernel: 8f0 = 0 Dec 22 16:55:29 localhost kernel: 8f4 = 0 Dec 22 16:55:29 localhost kernel: 8f8 = 0 Dec 22 16:55:29 localhost kernel: 8fc = 0 Dec 22 16:55:29 localhost kernel: 900 = 0 Dec 22 16:55:29 localhost kernel: 904 = 0 Dec 22 16:55:29 localhost kernel: 908 = 0 Dec 22 16:55:29 localhost kernel: 90c = f0f0f0f Dec 22 16:55:29 localhost kernel: 910 = f0f0f0f Switching back to Zaptel solved all of the problems. ___ -- 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
