[asterisk-bugs] [Asterisk 0013643]: [patch] VM_CALLERID yields different results if CID is null or empty

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=13643 
====================================================================== 
Reported By:                tomo1657
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   13643
Category:                   Core/PBX
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     resolved
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!): 147263 
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-10-07 15:35 CDT
Last Modified:              2008-10-09 14:28 CDT
====================================================================== 
Summary:                    [patch] VM_CALLERID yields different results if CID
is null or empty
Description: 
Thanks Corydon76 for the patch, but although VM_CIDNAME and VM_CIDNUM have
been dealt with VM_CALLERID still yields different results depending on if
callerid is NULL or empty string.

Perhaps modifying ast_callerid_merge() to treat both NULL and empty string
caller ID the same way is the solution?

I've attached a patch for this where ast_callerid_merge() uses
!ast_strlen_zero() to check for string length for name and num.



====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-09 14:28 svnbot         Status                   assigned => resolved
2008-10-09 14:28 svnbot         Resolution               open => fixed       
======================================================================