[asterisk-bugs] [Asterisk 0019223]: [patch] realtime peer update fails, because "" is not a valide int value for lastms

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19223 
====================================================================== 
Reported By:                marcelloceschia
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19223
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
JIRA:                       SWP-3421 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.8 
SVN Revision (number only!): 316037 
Request Review:              
====================================================================== 
Date Submitted:             2011-05-04 02:56 CDT
Last Modified:              2011-05-05 20:39 CDT
====================================================================== 
Summary:                    [patch] realtime peer update fails, because "" is
not a valide int value for lastms
Description: 
The issue also present on asterisk 1.6.x
====================================================================== 

---------------------------------------------------------------------- 
 (0134567) tilghman (manager) - 2011-05-05 20:39
 https://issues.asterisk.org/view.php?id=19223#c134567 
---------------------------------------------------------------------- 
It can be NULL, and making the field NULLable has nothing to do with
whether the field is required or not.

The database must take on the attributes that we find useful in Asterisk;
Asterisk is not modeled on top of the database.  Asterisk specifically
expects NULL for those values which are not specified.  Alternatively, you
can create the field as a char type. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-05-05 20:39 tilghman       Note Added: 0134567                          
======================================================================