Summary:ASTERISK-18171: Ajax Bug Asterisk 1.8 Manager using mxml
Reporter:Justin Barrett (jbarrett)Labels:
Date Opened:2011-07-25 14:04:56Date Closed:2011-09-26 14:38:17
Versions:1.8.4 Frequency of
Environment:PBX in a Flash build on the Centos 5.6 OS and running FreePBX 2.9Attachments:
Description:Ajax Bug Asterisk 1.8 Manager using mxml
I just upgraded my voip server. My old voip server was running Asterisk 1.4 and the new server was built using PBX in a Flash with Asterisk 1.8. When using the Asterisk Manager on the old voip server, I was able to figure out that the url for an http connection was slightly different:
old server = http://IPaddress:PORT/asterisk/mxml?...ecret=PASSWORD
new server = http://IPaddress:PORT/mxml?action=lo...ecret=PASSWORD

The problem is, on the new voip server running Asterisk 1.8, the mxml doesn't work. It looks like it's missing the final ">". for example, here are the two responses for the old version versus the new:

old server:
<response type='object' id='unknown'><generic response='Success' message='Authentication accepted' /></response>

new server:
<response type='object' id='unknown'><generic response='Success' message='Authentication accepted' /></response>

Notice the missing ">" at the end. This is causing my software to fail with a error saying "The following elements are not closed: ajax-response"

Can anyone help me with this? I assume this is a bug in the newer version of Asterisk?
Comments:By: Leif Madsen (lmadsen) 2011-09-08 12:02:06.698-0500

Well looking at the code that response is there correctly. There is nothing missing in terms of text or whatnot. Not sure if there is a specific window size or something like that which could be stripping the response?

By: Leif Madsen (lmadsen) 2011-09-12 13:10:13.103-0500

Requesting feedback from the reporter.

By: Leif Madsen (lmadsen) 2011-09-26 14:38:10.955-0500

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.  Further information can be found at http://www.asterisk.org/developers/bug-guidelines