Re: [reSIProcate-users] ParseBuffer.cxx 709, Parse failed expected a digit, got eof in context
Hi Adam, what's revsion of this change ?
Thanks
On Fri, May 22, 2009 at 2:39 AM, Adam Roach
<adam@xxxxxxxxxxx> wrote:
Karlsson:
I've checked in a change so that the SDP parser safely ignores these kinds of malformed "a=fmtp" lines, and added a test case (using the SDP example you sent to the list). Let me know if it fixes the problem for you.
/a
Adam Roach wrote:
Karlsson wrote:
Hi all, when I test my UA with Dialogic video gateway, the parsebuffer failed when it parse the SDP of INVITE.
I have attached the wireshark log file in mail..
I think the error cause the a=fmtp is empty. But with RFC 4566, the section 5.13:
5.13.
Attributes ("a=")
a=<attribute>
a=<attribute>:(value>
Seems the "a" allows two cases ?
In the general case, yes. But "fmtp" means something. Read down further:
a=fmtp:<format> <format specific parameters>
Postel's Maxim does suggest we should accept "a=fmtp" as a no-op, but the Dialogic device is technically generating invalid SDP.
/a