[MMUSIC] Re: mmusic Digest, Vol 22, Issue 3

Teodora Guenkova-Luy <teodora.guenkova-luy@uni-ulm.de> Mon, 06 February 2006 09:45 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F62wI-0001j8-LV; Mon, 06 Feb 2006 04:45:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F62wG-0001gW-IL for mmusic@megatron.ietf.org; Mon, 06 Feb 2006 04:45:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02422 for <mmusic@ietf.org>; Mon, 6 Feb 2006 04:44:00 -0500 (EST)
Received: from mail.uni-ulm.de ([134.60.1.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F638O-0005BH-AK for mmusic@ietf.org; Mon, 06 Feb 2006 04:58:14 -0500
Received: from uni-ulm.de (discovery.informatik.uni-ulm.de [134.60.77.113]) (authenticated bits=0) by mail.uni-ulm.de (8.13.4/8.13.4) with ESMTP id k169jRfJ012697 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 6 Feb 2006 10:45:28 +0100 (MET)
Message-ID: <43E71B89.30205@uni-ulm.de>
Date: Mon, 06 Feb 2006 10:48:57 +0100
From: Teodora Guenkova-Luy <teodora.guenkova-luy@uni-ulm.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mmusic@ietf.org, Osher.Hmelnizky@audiocodes.com
References: <200602051702.k15H2S3i029734@smtp.uni-ulm.de>
In-Reply-To: <200602051702.k15H2S3i029734@smtp.uni-ulm.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: df9edf1223802dd4cf213867a3af6121
Content-Transfer-Encoding: 7bit
Cc:
Subject: [MMUSIC] Re: mmusic Digest, Vol 22, Issue 3
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Hi,
SIP and RTSP are two different sessions. Their frameworks do not exclude 
the scenario that both of them shall be synchronised, however, there is 
no existing solution on such synchronisation. You can synchronize SIP 
and RTSP only at presentation level (i.e. SDP), like done for SIP and 
MRCP, as at session level SIP and RTSP are different instances that are 
not aware of each other. You could "misuse" the SDP SIP/MRCP attribute 
"a=channel:xxx" with your own parameters for RTSP, or use the SDP "i=" 
line also with your own paramentes, or define your own attribute line, 
e.g. "a=stacksynch:whatever". However, all these are non-standard solutions.
KR,
Teodora

mmusic-request@ietf.org wrote:

>
>Message: 1
>Date: Sun, 5 Feb 2006 09:41:06 +0200
>From: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>Subject: RE: [MMUSIC] Using RTSP with SIP
>To: "Burger, Eric" <eburger@brooktrout.com>
>Cc: mmusic@ietf.org
>Message-ID:
>	<79B4F738DDD4EF4F85A4641A0FE5EFD601C89990@aclmsg.corp.audiocodes.com>
>Content-Type: text/plain; charset="us-ascii"
>
>Hi,
>
> 
>
>What I'm trying to say is: why can't I use SIP for the call
>establishment and RTSP for the stream control. How can synchronize two
>protocols on the MRF side? 
>
>On the client side it is no problem, but server side should be aware
>that two sessions are interconnected to the one specific call.
>
>Such synchronization I saw in the SIP/MRCP draft
>(draft-ietf-speechsc-mrcpv2-09).
>
> 
>
>Thanks a lot
>
> 
>
>Osher
>
> 
>
>________________________________
>
>From: Burger, Eric [mailto:eburger@brooktrout.com] 
>Sent: Friday, February 03, 2006 4:34 AM
>To: Osher Hmelnizky
>Subject: RE: [MMUSIC] Using RTSP with SIP
>
> 
>
>What are you trying to accomplish?  Two sessions are two sessions.  It
>is either SIP or RTSP.  MRCP (not an IETF standard) has two, distinct
>sessions.
>
> 
>
>________________________________
>
>From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
>Of Osher Hmelnizky
>Sent: Tuesday, January 10, 2006 7:26 AM
>To: mmusic@ietf.org
>Subject: [MMUSIC] Using RTSP with SIP
>
> 
>
>In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order to
>synchronize the SIP and MRCP Sessios, defined
>
>a=channel:xxx
>
> 
>
>as part of application SDP.
>
> 
>
>I'm trying to find out how I can synchronize SIP and RTSP streams at the
>Media Server layer without any indication.
>
> 
>
>As a=channel defined at the SDP level can I use this parameter to sync
>between SIP and RTSP Streams.
>
> 
>
>Thanks a lot.
>
> 
>
>Osher
>
> 
>
> 
>
> 
>
> 
>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: http://www1.ietf.org/pipermail/mmusic/attachments/20060205/0ce380c0/attachment.htm
>
>------------------------------
>
>Message: 2
>Date: Sun, 5 Feb 2006 08:17:22 -0500
>From: "Burger, Eric" <eburger@brooktrout.com>
>Subject: RE: [MMUSIC] Using RTSP with SIP
>To: "Osher Hmelnizky" <Osher.Hmelnizky@audiocodes.com>
>Cc: mmusic@ietf.org
>Message-ID:
>	<330A23D8336C0346B5C1A5BB196666470228F906@ATLANTIS.Brooktrout.com>
>Content-Type: text/plain;	charset="iso-8859-1"
>
>That is something totally different and explicitly outside the scope of MRCPv2.  What you want is something like the mediactrl work (not chartered).  Search the I-D directory for mediactrl.  To subscribe, send 'subscribe mediactrl' to majordomo@lists.ubiquitysoftware.com
>
>________________________________________
>From: Osher Hmelnizky [mailto:Osher.Hmelnizky@audiocodes.com] 
>Sent: Sunday, February 05, 2006 2:41 AM
>To: Burger, Eric
>Cc: mmusic@ietf.org
>Subject: RE: [MMUSIC] Using RTSP with SIP
>
>Hi,
>
>What I'm trying to say is: why can't I use SIP for the call establishment and RTSP for the stream control. How can synchronize two protocols on the MRF side? 
>On the client side it is no problem, but server side should be aware that two sessions are interconnected to the one specific call.
>Such synchronization I saw in the SIP/MRCP draft (draft-ietf-speechsc-mrcpv2-09).
>
>Thanks a lot
>
>Osher
>
>________________________________________
>From: Burger, Eric [mailto:eburger@brooktrout.com] 
>Sent: Friday, February 03, 2006 4:34 AM
>To: Osher Hmelnizky
>Subject: RE: [MMUSIC] Using RTSP with SIP
>
>What are you trying to accomplish?  Two sessions are two sessions.  It is either SIP or RTSP.  MRCP (not an IETF standard) has two, distinct sessions.
>
>________________________________________
>From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf Of Osher Hmelnizky
>Sent: Tuesday, January 10, 2006 7:26 AM
>To: mmusic@ietf.org
>Subject: [MMUSIC] Using RTSP with SIP
>
>In the last MRCP draft (draft-ietf-speechsc-mrcpv2-09), in order to synchronize the SIP and MRCP Sessios, defined
>       a=channel:xxx
>       
>as part of application SDP.
>
>I'm trying to find out how I can synchronize SIP and RTSP streams at the Media Server layer without any indication.
>
>As a=channel defined at the SDP level can I use this parameter to sync between SIP and RTSP Streams.
>
>Thanks a lot.
>
>Osher
>
>
>
>
>
>
>------------------------------
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www1.ietf.org/mailman/listinfo/mmusic
>
>
>End of mmusic Digest, Vol 22, Issue 3
>*************************************
>  
>

-- 
-----------------------------------------
Teodora Guenkova-Luy

Dept. Distributed Systems, University of Ulm, 
Oberer Eselsberg, 89069 Ulm, Germany

Tel.: +49 (0731) 502-4148 
FAX: +49 (0731) 502-4142

e-Mail: teodora.guenkova-luy@uni-ulm.de

Home Page: http://www-vs.informatik.uni-ulm.de/~Guenkova/ 

-----------------------------------------



_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic