[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:29:10 CDT 2009
The following issue has been RESOLVED.
======================================================================
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: resolved
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:29 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
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2009-05-07 11:29 svnbot Status ready for review =>
assigned
2009-05-07 11:29 svnbot Status assigned => resolved
2009-05-07 11:29 svnbot Resolution open => fixed
======================================================================
More information about the asterisk-bugs
mailing list