We rarely revise RFCs solely to clarify the wording. Sometimes we issue
clarifying RFCs instead. Or the clarification is simply captured as an
errata and then it will be incorporated if/when the RFC is revised.
Thanks,
Paul
On 11/29/2010 11:20 AM, Iñaki Baz Castillo wrote:
> 201
2010/11/29 Pavesi, Valdemar (NSN - US/Irving) :
> Hello,
>
> RTP Dynamic Payload and Static Payload
Excellent information. Thanks.
--
Iñaki Baz Castillo
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbi
@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] dynamic payload negotiation
>> Can you provide a reference to this? Is it really allowed?
>
> Yes it is. Each direction of the stream can epecify its own payload
> types even for same codec. Also note that a stream could use codec A
> in
: sip-implementors@lists.cs.columbia.edu
> Subject: Re: [Sip-implementors] dynamic payload negotiation
>
> >> Can you provide a reference to this? Is it really allowed?
> >
> > Yes it is. Each direction of the stream can epecify its own payload
> > types even for sa
>> Can you provide a reference to this? Is it really allowed?
>
> Yes it is. Each direction of the stream can epecify its own payload
> types even for same codec. Also note that a stream could use codec A
> in left direction and codec B in right direction.
>
My question was not regarding the possi
2010/11/29 Saúl Ibarra Corretgé :
>> So lets say party A sends G711 a-law with payload type 0 but party B sends
>> G711 a-law with dynamic payload 100 so what should happen in this case.
>>
>
> Can you provide a reference to this? Is it really allowed?
Yes it is. Each direction of the stream can
2010/11/29 Schwarz, Albrecht (Albrecht) :
> Asymmetric media configurations are in general possible.
> See SDP Offer/Answer, RFC 3264.
> Both directions are independent.
> Thus, different media configurations may be negotiated for the two
> Offerer-to-Answerer directions.
> To the folks respons
ent: Montag, 29. November 2010 14:13
> To: varun
> Cc: sip-implementors@lists.cs.columbia.edu
> Subject: Re: [Sip-implementors] dynamic payload negotiation
>
> > Also I believe that even static paylaod types can be used
> as dynamic ones.
> > So lets say party A sends G71
That's right.
-Original Message-
From: Bob Penfield [mailto:bpenfi...@acmepacket.com]
Sent: Monday, November 29, 2010 10:24 AM
To: Uttam Sarkar (usarkar); varun;
sip-implementors@lists.cs.columbia.edu
Subject: RE: [Sip-implementors] dynamic payload negotiation
You have it backwards
...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Uttam
Sarkar (usarkar)
Sent: Monday, November 29, 2010 9:57 AM
To: varun; sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] dynamic payload negotiation
Correction..
-Original Message-
From
Subject: [Sip-implementors] dynamic payload negotiation
Hi,
I have a question about dynamic payload type negotiation.
Lets say A is the offerer:
m=audio 5006 RTP/AVP 8 96
a=rtpmap:8 PCMA/8000
a=rtpmap:96 telephone-event/8000
Lets say B is the amswerer
m=audio 1046 RTP/AVP 8 101
a=rtpmap:8 PCMA
Please see inline.
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of
varun
Sent: Monday, November 29, 2010 5:31 AM
To: sip-implementors@lists.cs.columbia.edu
Subject: [Sip-implementors] dynamic
> Also I believe that even static paylaod types can be used as dynamic ones.
> So lets say party A sends G711 a-law with payload type 0 but party B sends
> G711 a-law with dynamic payload 100 so what should happen in this case.
>
Can you provide a reference to this? Is it really allowed?
Regard
s-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of
varun
Sent: Monday, November 29, 2010 4:01 PM
To: sip-implementors@lists.cs.columbia.edu
Subject: [Sip-implementors] dynamic payload negotiation
Hi,
I have a question about dynamic payload type negotiation.
-implementors@lists.cs.columbia.edu
Subject: [Sip-implementors] dynamic payload negotiation
Hi,
I have a question about dynamic payload type negotiation.
Lets say A is the offerer:
m=audio 5006 RTP/AVP 8 96
a=rtpmap:8 PCMA/8000
a=rtpmap:96 telephone-event/8000
Lets say B is the amswerer
m=audio 1046
Hi,
I have a question about dynamic payload type negotiation.
Lets say A is the offerer:
m=audio 5006 RTP/AVP 8 96
a=rtpmap:8 PCMA/8000
a=rtpmap:96 telephone-event/8000
Lets say B is the amswerer
m=audio 1046 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
What RTP payload
16 matches
Mail list logo
