[asterisk-bugs] [Asterisk 0018251]: Realtime field 'fullcontact' populated with invalid data
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Nov 10 11:43:47 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18251
======================================================================
Reported By: bcnit
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18251
Category: Channels/chan_sip/DatabaseSupport
Reproducibility: always
Severity: major
Priority: normal
Status: new
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:
======================================================================
Date Submitted: 2010-11-04 09:55 CDT
Last Modified: 2010-11-10 11:43 CST
======================================================================
Summary: 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'
======================================================================
----------------------------------------------------------------------
(0128748) tilghman (administrator) - 2010-11-10 11:43
https://issues.asterisk.org/view.php?id=18251#c128748
----------------------------------------------------------------------
The code to replace the semicolon is intentional, to prevent the Contact
field from being split into two values when it is read back out of the
database. Removing it will guarantee that the Contact field will be
invalid.
Issue History
Date Modified Username Field Change
======================================================================
2010-11-10 11:43 tilghman Note Added: 0128748
======================================================================
More information about the asterisk-bugs
mailing list