Ok,
The issue is that clients are unable to parse the MWI NOTIFY message due to the order of the body. Please see my suggestion on the ticket ASTERISK-26065<https://issues.asterisk.org/jira/browse/ASTERISK-26065> Regards, Ross ________________________________ From: [email protected] <[email protected]> on behalf of Ross Beer <[email protected]> Sent: 26 May 2016 11:02 To: Asterisk Developers Mailing List Subject: [asterisk-dev] Swamped with MWI Notify parse errors Hi All, I'm currently being swamped with MWI Notify parse errors when Asterisk is sending notify messages to phones. The CLI is showing the following: SIP/2.0 400 ../../rutil/ParseBuffer.cxx:669, Parse failed Expected a digit, got: sip:1571@<server ip>:5060 in context: Contents Messages-Waiting: no Voice-Message: 0/0 (0/0) Message-Account: sip:1571@<server ip>:5060[CRLF] ^[CRLF] Via: SIP/2.0/UDP <server ip>:5060;rport=5060;branch=z9hG4bKPjb11bdc9b-030c-453b-8e0d-070a2e01ca6a To: <sip:<account no>@<client ip>;rinstance=784a071431a881b7>;tag=3a20d77e From: <sip:<account no>@<server ip>>;tag=fbdc56c4-d260-43ce-b0ce-9333e1151602 Call-ID: ed88eae3-2daf-4b6e-b5a1-572783bce0b7 CSeq: 8818 NOTIFY Accept-Language: en Content-Length: 0 To me this looks like the transport layer rejecting the message before it's being sent. For some reason the other lines of the message do not show the [CRLF] even though I can see the "\r\n" in the code. Can you please help? I've raised an issue ASTERISK-26065<https://issues.asterisk.org/jira/browse/ASTERISK-26065> Kind regards, Ross
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
