[asterisk-bugs] [Asterisk 0012942]: [patch] Dialog state NOTIFY for hold uses badly formed XML
noreply at bugs.digium.com
noreply at bugs.digium.com
Tue Jul 1 02:42:08 CDT 2008
The following issue has been RESOLVED.
======================================================================
http://bugs.digium.com/view.php?id=12942
======================================================================
Reported By: gowen72
Assigned To: oej
======================================================================
Project: Asterisk
Issue ID: 12942
Category: Channels/chan_sip/Interoperability
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): 1.4
SVN Revision (number only!): 126116
Disclaimer on File?: N/A
Request Review:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 06-27-2008 19:09 CDT
Last Modified: 07-01-2008 02:42 CDT
======================================================================
Summary: [patch] Dialog state NOTIFY for hold uses badly
formed XML
Description:
For DIALOG_INFO_XML subscriptions, asterisk generates malformed XML for the
hold state NOTIFY events.
The problem is that the XML tag added to indicate the hold state (the
sip.rendering attribute) is not being terminated. Since there is no value
for this tag, it should be self-terminated, in the same way you are
supposed to use "<hr/>" for a horizontal ruler in HTML.
Here is what is being sent:
<param pname="+sip.rendering" pvalue="no">
But it shoud be:
<param pname="+sip.rendering" pvalue="no"/>
Note the "/" character prior the closing ">".
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
07-01-08 02:42 svnbot Assigned To => oej
07-01-08 02:42 svnbot Status assigned => resolved
07-01-08 02:42 svnbot Resolution open => fixed
======================================================================
More information about the asterisk-bugs
mailing list