Markolefas, Nikolaos wrote: > The following line is syntactically incorrect. A proper sdp parser > should return an error, and do not accept an SDP offer (or answer) > including "a=rtpmap:18 G729A/8000".
I've been reading the posts earlier this year about the "G729a" not being a valid encoding name as per RFC3551. There appears to be a popular ATA vendor that sends : a=rtpmap:18 G729a/8000 in the SDP for what I can gather is most of their product range. This therefore causes quite a few compatibility problems for VoIP to VoIP calls as many ATAs and softphones are strict do not accept "G729a", only "G729". What is the general consensus for handing this issue? Do you write work arounds into your code to accept it, or do you return an error? Some of the code I have seen, does a comparison byte by byte on "G729" & the encoding name and conveniently never sees the 'a' postfixing the name. I've also been looking at the behavior of some SIP proxies. Some will rewrite the SDP sending a compliant "G729" instead, others appear to just pass it on unaltered. Regards, Craig Peacock _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
