Hi Colin/Christer,
In case ptime needs to be treated as a media level attribute, I have doubt
in SDP negotiation
of UA which support RFC 2327 and RFC 3264.
When UA receives the message with multiple ptime, please let me know which
ptime needs to
be selected for that media line (First ptime or last ptime in the set of
ptime for that m line) .
I faced this issue in Sipit 15 with one UA as I always select the last
ptime attribute in the m line.
This issue is already discussed in the mailing list but I could not figure
out the final conclusion
in the thread at
http://lists.cs.columbia.edu/pipermail/sip-implementors/2003-March/004747.html
Could you please clarify the expected UAS behavior.
Regards
Partha
------------------------------------------------------------------
R.Parthasarathi
Flextronics Software Systems (FSS)- B'lore- India
Off: +91-80-51069088 Mob: +91-9448383781
------------------------------------------------------------------
Colin Perkins
<[EMAIL PROTECTED]
g> To
Sent by: "Lyons, Terry"
sip-implementors- <[EMAIL PROTECTED]>
[EMAIL PROTECTED] cc
ia.edu [email protected],
[email protected]
Subject
09/12/2005 06:16 Re: [MMUSIC] a=mptime not needed ?
PM FW: [Sip-implementors] Multiple
ptime attributes in the SDP
Terry,
The "a=ptime:" is a media level attribute, which makes it specific to
the "m=" line. It does not work on a per-codec basis, and the
suggestion that "the ptime value corresponds to the previous codec
specified in the attribute list" is incorrect.
Colin
On 9 Sep 2005, at 18:56, Lyons, Terry wrote:
> Is this a valid concept, "codec specific attribute"?
> SDP says ptime "is a media attribute".
>
> - [EMAIL PROTECTED]
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of
> [EMAIL PROTECTED]
> Sent: Wednesday, September 07, 2005 1:33 AM
> To: Kool Guy
> Cc: [EMAIL PROTECTED];
> [email protected]
> Subject: Re: [Sip-implementors] Multiple ptime attributes in the SDP
>
> Hi,
>
> ptime is a codec specific attribute. The ptime value corresponds to
> the
> previous codec specified in the attribute list. The multiple ptime
> attribute can be represented as follows:
>
> m=audio 49230 RTP/AVP 96 97 98
> a=rtpmap:96 L8/8000
> a=ptime:20
> a=rtpmap:97 L16/8000
> a=ptime:25
> a=rtpmap:98 L16/11025/2
>
> In the above, ptime=20 corresponds to L8 codec and ptime=25
> corresponds to
> L16.
>
> Regards
> Partha
>
> ------------------------------------------------------------------
> R.Parthasarathi
> Flextronics Software Systems (FSS)- B'lore- India
> Off: +91-80-51069088 Mob: +91-9448383781
> ------------------------------------------------------------------
>
> _______________________________________________
> mmusic mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/mmusic
>
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
*********************** FSS-Unclassified ***********************
"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended solely for the use of the individual to whom it is
addressed. It may contain privileged or confidential information and
should not be circulated or used for any purpose other than for what it is
intended. If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient, you are
notified that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. HSS accepts no responsibility for
loss or damage arising from the use of the information transmitted by this
email including damage from virus."
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
