[asterisk-bugs] [Asterisk 0018251]: [patch] Realtime field 'fullcontact' populated with invalid data

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Dec 16 09:04:40 UTC 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18251 
====================================================================== 
Reported By:                bcnit
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   18251
Category:                   Channels/chan_sip/DatabaseSupport
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.2.13 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-11-04 09:55 CDT
Last Modified:              2010-12-16 03:04 CST
====================================================================== 
Summary:                    [patch] Realtime field 'fullcontact' populated with
invalid data
Description: 

Using Asterisk realtime, the field 'fullcontact' is populated with invalid
data. The result is that warnings occur when a handset re-registers after
Asterisk has been restarted.

In my case, after a handset registers, the field contains something like:

'spts211..52:04ln=2lbnso30731'

The warnings are:

[Nov  4 14:50:29] WARNING[5157]: chan_sip.c:12302
__set_address_from_contact: Invalid contact uri
spts211..52:04ln=2lbnso30731 (missing sip: or sips:), attempting to use
anyway
[Nov  4 14:50:29] WARNING[5157]: chan_sip.c:12321
__set_address_from_contact: Invalid host name in Contact: (can't resolve in
DNS) : 'spts211..52'

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0018279 [patch] res_odbc using ^ separator in M...
====================================================================== 

---------------------------------------------------------------------- 
 (0129651) svnbot (reporter) - 2010-12-16 03:04
 https://issues.asterisk.org/view.php?id=18251#c129651 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 298481

_U  branches/1.6.2/
U   branches/1.6.2/res/res_config_odbc.c

------------------------------------------------------------------------
r298481 | tilghman | 2010-12-16 03:04:39 -0600 (Thu, 16 Dec 2010) | 21
lines

Merged revisions 298480 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/branches/1.4

........
  r298480 | tilghman | 2010-12-16 03:03:40 -0600 (Thu, 16 Dec 2010) | 14
lines
  
  Only increment the pointer once per loop, otherwise we corrupt the
value.
  
  (closes issue https://issues.asterisk.org/view.php?id=18251)
   Reported by: bcnit
   Patches: 
         20101110__issue18251.diff.txt uploaded by tilghman (license 14)
   Tested by: trev, jthurman, elguero
  
  (closes issue https://issues.asterisk.org/view.php?id=18279)
   Reported by: zerohalo
   Patches: 
         20101109__issue18279.diff.txt uploaded by tilghman (license 14)
   Tested by: zerohalo
........

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=298481 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-12-16 03:04 svnbot         Checkin                                      
2010-12-16 03:04 svnbot         Note Added: 0129651                          
======================================================================




More information about the asterisk-bugs mailing list