| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
After some digging around, according to rfc3264, it looks like the Session ID in the “o=” line must be representable by a 64-bit signed integer. I believe anything longer than 20 digits would not qualify, and this is the source of the error. If someone could confirm that would be great. Thanks, Mike From: Mike Hubbard [mailto:mike.hubbard@xxxxxxx] Hello, I have an application that is returning an error in ParseBuffer.cxx. This is the output from the exception (with the IP address obfuscated): Parse failed Overflow detected. in context: Contents v=0 o=Rms-11-301-1647-18-1641486 113011816474279238672 855679187 IN IP4 x.y.z.w[CRLF] ^[CRLF] s=- c=IN IP4 x.y.z.w t=0 0 a=sendrecv m=audio 34806 RTP/AVP 18 0 8 101 a=rtpmap:18 G729/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=maxptime:40 Would anyone possibly be able to shed some light on what is going with the “[CRLF]” and “^[CRLF]” after the “o=” line? When I look at the raw SIP message in Wireshark, I can’t see any strange characters after the “o=” line. Thanks for any insight on this. Regards, Mike |