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
B must send RFC2833 using payload 96
and A must send RFC2833 using payload 101
regards
Attila
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of
varun
Sent: 29 November 2010 10:31
To:
Hi,
Asymmetric payload is allowed in sip.
As SDP is receive capability hence:
A- B (RFC2833 Payload :101)
B- A (RFC2833 Payload :96)
Also based on what is negotiated the streaming will be using that
payload.
Regards
Sunil Verma
-Original Message-
From:
Answers inline:
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of
Tarun2 Gupta
Sent: Thursday, November 25, 2010 4:45 PM
To: sip-implementors@lists.cs.columbia.edu
Subject: [Sip-implementors] Query
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?
Regards,
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
You have it backwards. SDP describes what a User Agent is prepared to received.
Therefore, when A offers 96 for DTMF, B must send DTMF using payload 96. When B
answers with 101 for DTMF, A must send DTMF using payload 101.
-Original Message-
From:
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. SDP
Hello
Let's assume user agent A is in conversation with user agent B with audio media
in both way.
If a user agent A sends a new sdp offer with a=inactive for the audio media,
should A user agent stop sending/receiving media RTP right after having sent
the REINVITE, or should it wait for 200
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 responsible for these RFCs:
this is a FAQ since years and
Hi all;
I am investigating about how Centrex work with SIP. If an enterprise
customer has a 2 different locations, how they call each other with short
numbers(4 digit) ? Which SIP headers are used for it? Is there a
standartization ? Does any one have a solution documentation? How the big
On 11/29/2010 10:44 AM, Ali Kemal MAYUK wrote:
I am investigating about how Centrex work with SIP. If an enterprise
customer has a 2 different locations, how they call each other with short
numbers(4 digit) ? Which SIP headers are used for it? Is there a
standartization ? Does any one have a
2010/11/29 Schwarz, Albrecht (Albrecht) albrecht.schw...@alcatel-lucent.com:
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
2010/11/29 Saúl Ibarra Corretgé sag...@gmail.com:
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
2010/11/24 ENTRESSANGLE, ERIC (ERIC) eric.entressan...@alcatel-lucent.com:
If a user agent A sends a new sdp offer with a=inactive for the audio media,
should A user agent stop sending/receiving media RTP right after having sent
the REINVITE, or should it wait for 200 OK response with audio
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 possibility
Yes, it is.
Cheers,
Charles
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-
boun...@lists.cs.columbia.edu] On Behalf Of Saúl Ibarra Corretgé
Sent: Monday, November 29, 2010 8:32 AM
To: Iñaki Baz Castillo
Cc:
Hello,
RTP Dynamic Payload and Static Payload
Static payload is payload which is defined in the IANA rtp parameter document
An example of a static payload type is a-law PCM coded single channel audio
sampled at 8KHz. This is completely defined in the RTP Audio/Video profile as
payload type
2010/11/29 Pavesi, Valdemar (NSN - US/Irving) valdemar.pav...@nsn.com:
Hello,
RTP Dynamic Payload and Static Payload
Excellent information. Thanks.
--
Iñaki Baz Castillo
i...@aliax.net
___
Sip-implementors mailing list
Every INVITE/re-INVITE recieved has to be acknoledged
with a final response to satisfy the transaction and other layers (Offer
answer too in this case).
Once the re-INVITE with a=inactive is recieved UAS can stop sending the RTP
rite away as it is clear that
UAC is no more intrested in
On 11/29/2010 11:06 AM, Alex Balashov wrote:
On 11/29/2010 10:44 AM, Ali Kemal MAYUK wrote:
I am investigating about how Centrex work with SIP. If an enterprise
customer has a 2 different locations, how they call each other with short
numbers(4 digit) ? Which SIP headers are used for it? Is
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:
22 matches
Mail list logo