[reSIProcate] resiprocate and my illegal SDP
Shaun Dawson
scdawson at gmail.com
Mon Dec 11 10:53:25 CST 2006
I recently sent a message about this SDP:
v=0
o=PVG 0 0 IN IP4 189.173.77.70
s=-
c=IN IP4 189.173.77.70
a=sqn: 0
a=cdsc: 1 audio RTP/AVP 8 0 116 18 13 101
a=cpar: a=rtpmap:116 AAL2-G726-32/8000
a=cpar: a=rtpmap:101 telephone-event/8000
a=cpar: a=fmtp:101 0-15
a=cpar: a=ptime:10
a=cpar: a=ptime:20
a=cpar: a=fmtp:18 annexb=yes
t=0 0
m=audio 54098 RTP/AVP 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
It was pointed out to me (thanks, Scott) that this SDP is illegal
because there are session level attribute lines before the 't=' line.
In my application, however, I need to support this SDP, in spite of
the fact that it is not RFC compliant.
I'm happy to parse the SDP myself, but I can't get access to the raw
data (I see that it's stored as a HeaderFieldValue in the mContentsHfv
member of the SipMessage class, though.) Is there any supported way
of accessing this data in its raw, unprocessed form?
thanks,
Shaun
More information about the resiprocate-devel
mailing list