[asterisk-users] FUNC_ODBC expr must be non-null

2012-05-01 Thread Doug Lytle
I'm slowly, but surely converting a 1.4.x dial-plan to an Asterisk 10.3.1 dial-plan, while also converting from mysql to func_odbc. The part of my dial plan that handles the blacklisting of phone numbers reads as: [tele_query] exten = s,1,Set(torture.calls=0) exten =

Re: [asterisk-users] FUNC_ODBC expr must be non-null

2012-05-01 Thread Eric Wieling
Sent: Tuesday, May 01, 2012 1:56 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: [asterisk-users] FUNC_ODBC expr must be non-null I'm slowly, but surely converting a 1.4.x dial-plan to an Asterisk 10.3.1 dial-plan, while also converting from mysql to func_odbc. The part

Re: [asterisk-users] FUNC_ODBC expr must be non-null

2012-05-01 Thread Doug Lytle
If a value can EVER be empty, then you want to use quotes in your expressions. Thanks Eric! It's working great now, I've learned something today. Doug -- Ben Franklin quote: Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor

Re: [asterisk-users] FUNC_ODBC expr must be non-null

2012-05-01 Thread Eric Wieling
...@lists.digium.com] On Behalf Of Doug Lytle Sent: Tuesday, May 01, 2012 2:08 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] FUNC_ODBC expr must be non-null If a value can EVER be empty, then you want to use quotes in your expressions. Thanks Eric! It's