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
