Re: [Sip-implementors] RTP with wrong payload
Thank you very much Alex, Dale and Paul ! BR/pj -Original Message- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Alex Balashov Sent: den 15 november 2018 07:20 To: sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors] RTP with wrong payload Correct -- if the party receiving the G.722 packets did not advertise support for the G.722 payload type in its SDP stanza, it should just ignore them if they arrive anyway. On Thu, Nov 15, 2018 at 06:21:14AM +, Sundbaum Per-Johan (Telenor Sverige AB) wrote: > I should have given more details, in the example I gave there was actual a > couple of G.722 packets that was marked with payload type G.722 received in a > session where G.711A(PCMA/8000) was established as the agreed codec, the > receiving PBX did not have support for G.722. > As I interpret RFC 3550 the PBX should drop the G.722 packets and let the > session continue, and same applies also in case where G.722 is supported by > PBX, am I wrong ? > BR/pj > > -Original Message- > From: sip-implementors-boun...@lists.cs.columbia.edu > [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of > Dale R. Worley > Sent: den 15 november 2018 05:10 > To: Paul Heitkemper > Cc: sip-implementors@lists.cs.columbia.edu > Subject: Re: [Sip-implementors] RTP with wrong payload > > Paul Heitkemper writes: > > RFC 3550 Section 5.1 > > > > " A receiver MUST ignore packets with payload types that it does not > > understand." > > Though this rule is based on the payload type code, and not the encoding. > The original post says only that the packets contain G.722 data, but if that > data is marked with the payload type code that was negotiated for G.711A, the > recipient will try to decode it as G.711A. > Perhaps the recipient can determine that the data is invalid (as G.711A) and > discard it, but more likely it will decode it into some sort of noise which > it will present to the user. > > Dale > ___ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > ___ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Re: [Sip-implementors] RTP with wrong payload
Correct -- if the party receiving the G.722 packets did not advertise support for the G.722 payload type in its SDP stanza, it should just ignore them if they arrive anyway. On Thu, Nov 15, 2018 at 06:21:14AM +, Sundbaum Per-Johan (Telenor Sverige AB) wrote: > I should have given more details, in the example I gave there was actual a > couple of G.722 packets that was marked with payload type G.722 received in a > session where G.711A(PCMA/8000) was established as the agreed codec, the > receiving PBX did not have support for G.722. > As I interpret RFC 3550 the PBX should drop the G.722 packets and let the > session continue, and same applies also in case where G.722 is supported by > PBX, am I wrong ? > BR/pj > > -Original Message- > From: sip-implementors-boun...@lists.cs.columbia.edu > [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Dale R. > Worley > Sent: den 15 november 2018 05:10 > To: Paul Heitkemper > Cc: sip-implementors@lists.cs.columbia.edu > Subject: Re: [Sip-implementors] RTP with wrong payload > > Paul Heitkemper writes: > > RFC 3550 Section 5.1 > > > > " A receiver MUST ignore packets with payload types that it does not > > understand." > > Though this rule is based on the payload type code, and not the encoding. > The original post says only that the packets contain G.722 data, but if that > data is marked with the payload type code that was negotiated for G.711A, the > recipient will try to decode it as G.711A. > Perhaps the recipient can determine that the data is invalid (as G.711A) and > discard it, but more likely it will decode it into some sort of noise which > it will present to the user. > > Dale > ___ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > ___ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Re: [Sip-implementors] RTP with wrong payload
I should have given more details, in the example I gave there was actual a couple of G.722 packets that was marked with payload type G.722 received in a session where G.711A(PCMA/8000) was established as the agreed codec, the receiving PBX did not have support for G.722. As I interpret RFC 3550 the PBX should drop the G.722 packets and let the session continue, and same applies also in case where G.722 is supported by PBX, am I wrong ? BR/pj -Original Message- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Dale R. Worley Sent: den 15 november 2018 05:10 To: Paul Heitkemper Cc: sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors] RTP with wrong payload Paul Heitkemper writes: > RFC 3550 Section 5.1 > > " A receiver MUST ignore packets with payload types that it does not > understand." Though this rule is based on the payload type code, and not the encoding. The original post says only that the packets contain G.722 data, but if that data is marked with the payload type code that was negotiated for G.711A, the recipient will try to decode it as G.711A. Perhaps the recipient can determine that the data is invalid (as G.711A) and discard it, but more likely it will decode it into some sort of noise which it will present to the user. Dale ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Re: [Sip-implementors] RTP with wrong payload
Paul Heitkemper writes: > RFC 3550 Section 5.1 > > " A receiver MUST ignore packets with payload types that it does not > understand." Though this rule is based on the payload type code, and not the encoding. The original post says only that the packets contain G.722 data, but if that data is marked with the payload type code that was negotiated for G.711A, the recipient will try to decode it as G.711A. Perhaps the recipient can determine that the data is invalid (as G.711A) and discard it, but more likely it will decode it into some sort of noise which it will present to the user. Dale ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Re: [Sip-implementors] RTP with wrong payload
Thank you very much Paul ! BR/pj -Original Message- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Paul Heitkemper Sent: den 14 november 2018 16:35 To: sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors] RTP with wrong payload RFC 3550 Section 5.1 " A receiver MUST ignore packets with payload types that it does not understand." -- Paul On 2018-11-14 01:30, Sundbaum Per-Johan (Telenor Sverige AB) wrote: > Thanks ! > Ok, but to be more specific, are there any general recommendations on > question like: Should the PBX drop the packets with wrong payload and let the > call/session continue or should the PBX also drop the entire call ? > BR/pj > > -Original Message- > From: Dale R. Worley [mailto:wor...@ariadne.com] > Sent: den 14 november 2018 05:25 > To: Sundbaum Per-Johan (Telenor Sverige AB) > Cc: sip-implementors@lists.cs.columbia.edu > Subject: Re: [Sip-implementors] RTP with wrong payload > > "Sundbaum Per-Johan (Telenor Sverige AB)" > writes: > >> Can someone help me getting a link to information regarding how a PBX should >> handle the case when for example the codec G.711A is agreed upon, but >> somehow there are a couple of G.722 packets received that have the same >> ports on UDP level, but clearly belongs to another RTP stream when you look >> at sequence numbers, timestamps and SSRC ? > > There's no real definition of "clearly belongs to". If a packet arrives at a > port, it is processed according to the usage that has been negotiated for > that port. > > Dale > ___ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors [1] Links: -- [1] https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Re: [Sip-implementors] RTP with wrong payload
RFC 3550 Section 5.1 " A receiver MUST ignore packets with payload types that it does not understand." -- Paul On 2018-11-14 01:30, Sundbaum Per-Johan (Telenor Sverige AB) wrote: > Thanks ! > Ok, but to be more specific, are there any general recommendations on > question like: Should the PBX drop the packets with wrong payload and let the > call/session continue or should the PBX also drop the entire call ? > BR/pj > > -Original Message- > From: Dale R. Worley [mailto:wor...@ariadne.com] > Sent: den 14 november 2018 05:25 > To: Sundbaum Per-Johan (Telenor Sverige AB) > Cc: sip-implementors@lists.cs.columbia.edu > Subject: Re: [Sip-implementors] RTP with wrong payload > > "Sundbaum Per-Johan (Telenor Sverige AB)" > writes: > >> Can someone help me getting a link to information regarding how a PBX should >> handle the case when for example the codec G.711A is agreed upon, but >> somehow there are a couple of G.722 packets received that have the same >> ports on UDP level, but clearly belongs to another RTP stream when you look >> at sequence numbers, timestamps and SSRC ? > > There's no real definition of "clearly belongs to". If a packet arrives at a > port, it is processed according to the usage that has been negotiated for > that port. > > Dale > ___ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors [1] Links: -- [1] https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
