From: "Vick, Steven" <[EMAIL PROTECTED]>
There in lies the problem. The Aspect endpoint is sending two media
streams.
There are two media streams being offered, but the Ptime is only
represented for the first one on the list. This happens regardless of
how many media streams (or whether they're the same codec type) are in
the SDP. This is why I see the ptime in the rfc as needing some
enhancements.
No, it's only offering one media stream, because there is only one "m"
line in the SDP:
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): - 1171987362 1171987362 IN IP4
10.153.96.5
Session Name (s): Aspect Communications SDP Session
Connection Information (c): IN IP4 10.153.96.5
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 10034 RTP/AVP 18 18
101
Media Title (i): telephone-event 8000
Connection Information (c): IN IP4 10.153.96.5
Media Attribute (a): sendrecv
Media Attribute (a): ptime:10
Media Attribute (a): rtpmap:18 G729/8000
Media Attribute (a): fmtp:18 annexb=no
Media Attribute (a): rtpmap:18 G729/8000
Media Attribute (a): fmtp:18 annexb=no
Media Attribute (a): rtpmap:101 telephone-event/8000
All the "a" lines offer altnerative encodings to be used within the
one media stream. As you note, SDP has the limitation that only one
ptime attribute can be given for a single media stream. If you want
to be able to use more than one ptime, you have to offer one media
stream for each ptime.
Dale
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
