| Summary: | ASTERISK-13073: Pong response not properly terminated. | ||
| Reporter: | Matt King, M.A. Oxon. (kebl0155) | Labels: | |
| Date Opened: | 2008-11-14 10:37:33.000-0600 | Date Closed: | 2008-11-14 11:02:08.000-0600 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/ManagerInterface |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | In 1.6 the pong response has been changed to: Response: Success Ping: Pong However, the response ends with a single carriage return, so the next event comes as merged with the response, like this: Response: Success Ping: Pong Event: Newchannel Privilege: call,all Channel: SIP/12344-0823b700 ChannelState: 0 ChannelStateDesc: Down CallerIDNum: 12344 CallerIDName: 12344 AccountCode: Uniqueid: 1226680481.26 There should be a blank line between the Response and the Event. ****** ADDITIONAL INFORMATION ****** We need another \n at the end of the Pong response to conform to the standard. | ||
| Comments: | By: Digium Subversion (svnbot) 2008-11-14 11:02:07.000-0600 Repository: asterisk Revision: 156911 U trunk/main/manager.c ------------------------------------------------------------------------ r156911 | tilghman | 2008-11-14 11:02:07 -0600 (Fri, 14 Nov 2008) | 4 lines Ping is missing the standard double-newline after the event. (closes issue ASTERISK-13073) Reported by: kebl0155 ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=156911 | ||