[asterisk-bugs] [Asterisk 0016533]: Realtime is broken, blank strings aren't valid any more

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16533 
====================================================================== 
Reported By:                sergee
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16533
Category:                   Addons/res_config_mysql
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
JIRA:                        
Regression:                 Yes 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.0 
SVN Revision (number only!): 237134 
Request Review:              
====================================================================== 
Date Submitted:             2010-01-02 16:03 CST
Last Modified:              2010-01-04 09:58 CST
====================================================================== 
Summary:                    Realtime is broken, blank strings aren't valid any
more
Description: 
For a few years i've used a blank strings for values that i didn't wish to
specify. Recent commit into asterisk-addons 1.6.0 (revision 1070) broke
everything. A lot of problems arise, since my blank values aren't blank
anymore. For example, former blank fields 'fromuser' and 'fromdomain'
become not blank with this patch, and i get an error: SIP/2.0 400 Bad
Request – ‘Malformed/Missing FROM: field’.
Because my From header looks like this: From: "1000" <sip: @
>tag=as3e28b5d2

This problem doesn't have a simple solution, if you wish to support two
different blank values (empty strings and NULL) you should implement that
in the asterisk first. Replacing either value with non-empty strings is a
very bad idea, because there will be a lot of problems in both cases.

For now i wish that change would be reverted. Thank you in advance!
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-04 09:58 lmadsen        Regression               No => Yes           
2010-01-04 09:58 lmadsen        Description Updated                          
======================================================================