[asterisk-bugs] [Asterisk 0014754]: [patch] Realtime bad Reconstruct of field 'fullcontact' after restart

Asterisk Bug Tracker noreply at bugs.digium.com
Thu May 7 11:45:24 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14754 
====================================================================== 
Reported By:                Alexei Gradinari
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   14754
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Target Version:             1.6.0.10
Asterisk Version:           1.6.0.6 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-03-25 15:14 CDT
Last Modified:              2009-05-07 11:45 CDT
====================================================================== 
Summary:                    [patch] Realtime bad Reconstruct of field
'fullcontact' after restart
Description: 
If both sippeers & sipregs set in the extconfig.conf to the same table
after restart asterisk there is a bad field 'fullcontact'.
This filed contains duplicate value delimited with ';'

For example
; extconfig.conf
; Realtime configuration engine
;
sipusers => odbc,asterisk,sipbuddies
sippeers => odbc,asterisk,sipbuddies
sipregs => odbc,asterisk,sipbuddies

The field 'fullcontact' in the database contains 
sip:TEST707 at 192.168.0.43

after restart asterisk and before this peer registers again
if load peer from database
  asterisk -r -x 'sip show peer TEST707 load'
result is
  Reg. Contact : sip:TEST707 at 192.168.0.43;sip:TEST707 at 192.168.0.43

If disable sipregs the result is correct
  Reg. Contact : sip:TEST707 at 192.168.0.43

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

---------------------------------------------------------------------- 
 (0104366) svnbot (reporter) - 2009-05-07 11:45
 http://bugs.digium.com/view.php?id=14754#c104366 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 192934

_U  branches/1.6.0/
U   branches/1.6.0/channels/chan_sip.c

------------------------------------------------------------------------
r192934 | tilghman | 2009-05-07 11:45:23 -0500 (Thu, 07 May 2009) | 24
lines

Merged revisions 192933 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/trunk

................
  r192933 | tilghman | 2009-05-07 11:43:56 -0500 (Thu, 07 May 2009) | 17
lines
  
  Merged revisions 192932 via svnmerge from 
  https://origsvn.digium.com/svn/asterisk/branches/1.4
  
  ........
    r192932 | tilghman | 2009-05-07 11:29:08 -0500 (Thu, 07 May 2009) | 10
lines
    
    Eliminate repetition of fullcontact during reconstruction.
    If the fullcontact field appears in both the sippeers and the
    sipregs table, then during reconstruction of the field, it will
    otherwise be doubled.
    (closes issue http://bugs.digium.com/view.php?id=14754)
     Reported by: Alexei Gradinari
     Patches: 
           20090506__bug14754.diff.txt uploaded by tilghman (license 14)
     Tested by: lmadsen
  ........
................

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

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

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-07 11:45 svnbot         Checkin                                      
2009-05-07 11:45 svnbot         Note Added: 0104366                          
======================================================================




More information about the asterisk-bugs mailing list