Re: [asterisk-users] undocumented change in expression handling in 1.8 beta

2010-07-25 Thread Paul Belanger
On Sun, Jul 25, 2010 at 12:52 AM,  cov...@ccs.covici.com wrote:
 Hi.  I hava a variable and in 1.6 I set the string variable to  and it
 got the null string.  In 1.8, it gets the quotes, I have to set it to
 nothing at all to make it get the null value.

Post an example for working (1.6) and not working (1.8)

-- 
Paul Belanger | dCAP
Polybeacon | Consultant
Jabber: paul.belan...@polybeacon.com | IRC: pabelanger (Freenode)
blog.polybeacon.com

-- 
_
-- 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] undocumented change in expression handling in 1.8 beta

2010-07-25 Thread covici
Paul Belanger paul.belan...@polybeacon.com wrote:

 On Sun, Jul 25, 2010 at 12:52 AM,  cov...@ccs.covici.com wrote:
  Hi.  I hava a variable and in 1.6 I set the string variable to  and it
  got the null string.  In 1.8, it gets the quotes, I have to set it to
  nothing at all to make it get the null value.
 
 Post an example for working (1.6) and not working (1.8)
 

OK, the line actually is:
exten = s,n(auth),Set(password=) which sets to a null value in 1.6.2
but does not in 1.8.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici
 cov...@ccs.covici.com

-- 
_
-- 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] undocumented change in expression handling in 1.8 beta

2010-07-25 Thread Paul Belanger
On Sun, Jul 25, 2010 at 11:39 AM,  cov...@ccs.covici.com wrote:
 OK, the line actually is:
 exten = s,n(auth),Set(password=) which sets to a null value in 1.6.2
 but does not in 1.8.

It's possible something changed, how are you checking if the
${password} is null? Post an example dialplan that works in 1.6.2 and
does not in 1.8.

-- 
Paul Belanger | dCAP
Polybeacon | Consultant
Jabber: paul.belan...@polybeacon.com | IRC: pabelanger (Freenode)
blog.polybeacon.com

-- 
_
-- 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] undocumented change in expression handling in 1.8 beta

2010-07-25 Thread covici
Paul Belanger paul.belan...@polybeacon.com wrote:

 On Sun, Jul 25, 2010 at 11:39 AM,  cov...@ccs.covici.com wrote:
  OK, the line actually is:
  exten = s,n(auth),Set(password=) which sets to a null value in 1.6.2
  but does not in 1.8.
 
 It's possible something changed, how are you checking if the
 ${password} is null? Post an example dialplan that works in 1.6.2 and
 does not in 1.8.
 
Well, when I executed the line 
exten = s,n,SET(password=${password}${digit});add a digit
and when
 I wanted to test the
variable
exten =
s,n(pswd_done),GotoIf($[x${password}=x14036]?custom-conf8200,s,1)
I got the following error in 1.8:
[Jul 25 00:36:14] WARNING[7242] ast_expr2.fl: ast_yyerror():  syntax
error: syntax error, unexpected 'token', expecting $end; Input:
x14036=x14036
 ^

After the  was gone in the set, it works in 1.8, have not tried in
1.6.





--
 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici
 cov...@ccs.covici.com

-- 
_
-- 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] undocumented change in expression handling in 1.8 beta

2010-07-25 Thread Tilghman Lesher
On Saturday 24 July 2010 23:52:39 cov...@ccs.covici.com wrote:
 Hi.  I hava a variable and in 1.6 I set the string variable to  and it
 got the null string.  In 1.8, it gets the quotes, I have to set it to
 nothing at all to make it get the null value.

Please read the 6th item in UPGRADE.txt.

-- 
Tilghman Lesher
Digium, Inc. | Senior Software Developer
twitter: Corydon76 | IRC: Corydon76-dig (Freenode)
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] undocumented change in expression handling in 1.8 beta

2010-07-25 Thread covici
Tilghman Lesher tles...@digium.com wrote:

 On Saturday 24 July 2010 23:52:39 cov...@ccs.covici.com wrote:
  Hi.  I hava a variable and in 1.6 I set the string variable to  and it
  got the null string.  In 1.8, it gets the quotes, I have to set it to
  nothing at all to make it get the null value.
 
 Please read the 6th item in UPGRADE.txt.
The sixth item I have is:
* The default behavior for Set, AGI, and pbx_realtime has been changed
to implement
  1.6 behavior by default, if there is no [compat] section in
  asterisk.conf.  In
  prior versions, the behavior defaulted to 1.4 behavior, to assist in
  upgrades.
  Specifically, that means that pbx_realtime and res_agi expect you to
  use commas
  to separate arguments in applications, and Set only takes a single
  pair of
  a variable name/value.  The old 1.4 behavior may still be obtained by
  setting
  app_set, pbx_realtime, and res_agi each to 1.4 in the [compat] section
  of
  asterisk.conf.
 
I guess that referrs to the following in the 1.6 upgrade file:
  You now only need to quote strings in configuration files if you
  literally
   want quotation marks within a string.

Thanks much for that clarification.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici
 cov...@ccs.covici.com

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