Re: [Sip] Multiple SDP descriptions for conferencing

Alan Johnston <alan.johnston@wcom.com> Thu, 23 January 2003 22:05 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21587 for <sip-archive@odin.ietf.org>; Thu, 23 Jan 2003 17:05:57 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0NMOdX29868 for sip-archive@odin.ietf.org; Thu, 23 Jan 2003 17:24:39 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0NMNrJ29835; Thu, 23 Jan 2003 17:23:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0NMJhJ29662 for <sip@optimus.ietf.org>; Thu, 23 Jan 2003 17:19:43 -0500
Received: from pmesmtp01.wcom.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21459 for <sip@ietf.org>; Thu, 23 Jan 2003 17:00:30 -0500 (EST)
Received: from pmismtp01.wcomnet.com ([166.38.62.36]) by firewall.wcom.com (Iplanet MTA 5.2) with ESMTP id <0H9600G32T5WDX@firewall.wcom.com> for sip@ietf.org; Thu, 23 Jan 2003 22:01:08 +0000 (GMT)
Received: from pmismtp01.wcomnet.com by pmismtp01.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7 2002)) with SMTP id <0H9600701SZYTV@pmismtp01.wcomnet.com>; Thu, 23 Jan 2003 22:01:08 +0000 (GMT)
Received: from ajohnston.wcom.com ([166.42.33.61]) by pmismtp01.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7 2002)) with ESMTP id <0H96007GTT3VIL@pmismtp01.wcomnet.com>; Thu, 23 Jan 2003 21:59:57 +0000 (GMT)
Date: Thu, 23 Jan 2003 15:59:52 -0600
From: Alan Johnston <alan.johnston@wcom.com>
Subject: Re: [Sip] Multiple SDP descriptions for conferencing
In-reply-to: <01b201c2c25f$473f5610$400015ac@skim>
X-Sender: Alan.Johnston@pop.mcit.com
To: Seonman Kim <seonman@funtv.com>, sip@ietf.org
Message-id: <5.1.1.6.0.20030123154639.03e95c68@pop.mcit.com>
MIME-version: 1.0
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Content-type: text/plain; charset="us-ascii"; format="flowed"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>

Hi Seonman,

You will find more updated work on SIP conferencing with the SIPPING 
Conferencing Design Team:

      http://www.softarmor.com/sipping/teams/conf/

The framework document includes a discussion of the this model:

      http://www.ietf.org/internet-drafts/draft-rosenberg-sipping-conferencing-framework-00.txt

Instead of multiple SDP message bodies, the re-INVITE would add an extra 
media line for each participant that enters the conference.  See below for 
an example.

For other valid offer/answer examples of SDP, see:

      http://www.ietf.org/internet-drafts/draft-johnston-mmusic-offer-answer-examples-00.txt

Thanks,
Alan Johnston
WorldCom
sip:alan@digitalari.com


At 01:43 PM 1/22/2003 -0800, Seonman Kim wrote:
>Hi,
>
>I am trying to implement a SIP-based multi-point conferencing based on
>"Centralized Signaling, Distributed Media" model
>(draft-ietf-sipping-conferencing-models-01.txt). In this model, each
>participant  UA gets updated SDP descriptions using "re-INVITE" whenever a
>user enters to (or exits from) the conference. If the number of participants
>becomes more than two,
>then the re-INVITE message should contain two or more SDP descriptions.
>For example, if user A, B and C are in the conference, then a re-INVITE to
>user A should contain two SDP description, one for user B and the other for
>user C.
>
>My question here is: how to describe multiple SDP descriptions in the
>content body
>of INVITE (or 200 OK) message? Do we just concatenate them?
>For example, if the conference server sends re-INVITE to user A with SDPs of
>user B and C, the content body will look like this:
>
>v=0
>o=user-b 0 0 IN IP4 192.168.1.100
>s=session
>c=IN IP4 192.168.1.100
>b=CT:1000
>t=0 0
>m=audio 30001 RTP/AVP 0
>a=rtpmap:0 PCMU/8000
>v=0
>o=user-c 0 0 IN IP4 192.168.1.101
>s=session
>c=IN IP4 192.168.1.101
>b=CT:1000
>t=0 0
>m=audio 30002 RTP/AVP 0
>a=rtpmap:0 PCMU/8000
>
>Is this correct implementation for multiple SDP sessions?

No, I think it would look like this:

v=0
o=user-b 0 0 IN IP4 192.168.1.100
s=session
b=CT:1000
t=0 0
m=audio 30001 RTP/AVP 0
c=IN IP4 192.168.1.100
a=rtpmap:0 PCMU/8000
m=audio 30002 RTP/AVP 0
c=IN IP4 192.168.1.101
a=rtpmap:0 PCMU/8000

>I could not find any descriptions in RTF 3261 that say UA should handle
>multiple SDP sessions.
>
>Thanks,
>Seonman
>
>_______________________________________________
>Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>This list is for NEW development of the core SIP Protocol
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sipping@ietf.org for new developments on the application of sip

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip