Re: [AVT] SSRC change in a single RTP session
Colin Perkins <csp@csperkins.org> Wed, 20 October 2010 09:42 UTC
Return-Path: <csp@csperkins.org>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 29E923A6874 for <avt@core3.amsl.com>; Wed, 20 Oct 2010 02:42:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.467
X-Spam-Level:
X-Spam-Status: No, score=-103.467 tagged_above=-999 required=5 tests=[AWL=0.131, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sWQRZ-2VIYOd for <avt@core3.amsl.com>; Wed, 20 Oct 2010 02:42:23 -0700 (PDT)
Received: from lon1-msapost-3.mail.demon.net (lon1-msapost-3.mail.demon.net [195.173.77.182]) by core3.amsl.com (Postfix) with ESMTP id 282763A693B for <avt@ietf.org>; Wed, 20 Oct 2010 02:39:11 -0700 (PDT)
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]) by lon1-post-3.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1P8V8D-00016r-eQ; Wed, 20 Oct 2010 09:39:23 +0000
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/alternative; boundary="Apple-Mail-250-22682735"
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <AANLkTi=6jXtBpGcattXEzoCO-shLMUnZ-qRxd6Ux9Q3v@mail.gmail.com>
Date: Wed, 20 Oct 2010 10:38:47 +0100
Message-Id: <FD1338C2-1520-4AE1-8FE3-7252A13AA3FD@csperkins.org>
References: <AANLkTikQ5ShYa-CR7-28Wvj8PxH+Gb6dM9rVUWP6ugLW@mail.gmail.com> <2F4E0AC9-6542-4153-A652-9FEF6CB870B0@csperkins.org> <AANLkTi=6jXtBpGcattXEzoCO-shLMUnZ-qRxd6Ux9Q3v@mail.gmail.com>
To: paromita chowdhury <paromitaz@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: avt@ietf.org
Subject: Re: [AVT] SSRC change in a single RTP session
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 09:42:25 -0000
An SSRC collision can happen at any time, and will force a change of SSRC. A new participant can join at any time, causing new SSRCs to appear. An existing participant may decide to send an additional media stream into a session, causing a new SSRC to appear. An application may restart, causing an SSRC change. A source may change its transport address requiring an SSRC change, but do so behind a NAT such that you don't see the change of transport address. An implementation may be broken, and change its SSRC for no reason. Don't assume the SSRC is constant. Nothing in RFC 3550 requires it to be, and there are many things that may cause it to change. Colin On 20 Oct 2010, at 10:10, paromita chowdhury wrote: > I noticed in a audio(VoIP) call with no change in the source or destination IP addresses, the ssrc value of side of the communication changed while the call was still going. > > I find in the RFC 3550 that ssrc may change when one of the endpoint changes but it mentions nothing about the scenario when endpoints do not change. Can you please point/direct me to the section of the RFC stating it? > > Thanks > > On 20 October 2010 01:54, Colin Perkins <csp@csperkins.org> wrote: > On 20 Oct 2010, at 09:25, paromita chowdhury wrote: >> I have read the RTP rfc 3550 a couple of times, still have a doubt on the following issue: >> >> - If a RTP unicast session with no change in the source and destination address, changes its SSRC during the call session is it permissible? In other words, between the same pair of source and destination addresses, can a change in the SSRC value acceptable at the destination? > > > Yes, the SSRC can change. In addition, you might see multiple SSRCs on the session (a unicast session is not restricted to one single SSRC from each participant, or even only two participants, since one may be an RTP translator or mixer). > > -- > Colin Perkins > http://csperkins.org/
- [AVT] SSRC change in a single RTP session paromita chowdhury
- Re: [AVT] SSRC change in a single RTP session Colin Perkins
- Re: [AVT] SSRC change in a single RTP session paromita chowdhury
- Re: [AVT] SSRC change in a single RTP session Colin Perkins
- Re: [AVT] SSRC change in a single RTP session paromita chowdhury