Re: [splices] Using Two Separate Devices to Start a Conversation proposal

Paul Kyzivat <pkyzivat@cisco.com> Mon, 06 June 2011 22:09 UTC

Return-Path: <pkyzivat@cisco.com>
X-Original-To: splices@ietfa.amsl.com
Delivered-To: splices@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31DB811E81CE for <splices@ietfa.amsl.com>; Mon, 6 Jun 2011 15:09:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.256
X-Spam-Level:
X-Spam-Status: No, score=-110.256 tagged_above=-999 required=5 tests=[AWL=0.343, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Za6-8WcG3zQA for <splices@ietfa.amsl.com>; Mon, 6 Jun 2011 15:09:14 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id BC74D11E8073 for <splices@ietf.org>; Mon, 6 Jun 2011 15:09:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=673; q=dns/txt; s=iport; t=1307398154; x=1308607754; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=ecas9JY4hnHDaezxVEk+TyfbeiX5bRLyNFrdzW2ZOXM=; b=Y9z4wgEvsaM0vDCVqfjnuwRz9tlFRtyiHnDBFyjO/FPvRxWE/No+99zL RyS/u+Iz0Npxswfbkbi3XRt9n3lpgkCfN+I/ZB6uA9M7MmA7/phrfWHFj 0AIAMw/2aUErB2uxL0nWSTGtOXyHyXDaqI0j52xdD/XNnGi4ARR3hV0cH M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EACNP7U2tJXG+/2dsb2JhbABTphF3rHaeEYYhBJB5hEiLDg
X-IronPort-AV: E=Sophos;i="4.65,328,1304294400"; d="scan'208";a="331359022"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by sj-iport-3.cisco.com with ESMTP; 06 Jun 2011 22:09:14 +0000
Received: from [161.44.174.125] (dhcp-161-44-174-125.cisco.com [161.44.174.125]) by rcdn-core2-3.cisco.com (8.14.3/8.14.3) with ESMTP id p56M9Dof023409; Mon, 6 Jun 2011 22:09:13 GMT
Message-ID: <4DED5009.4020700@cisco.com>
Date: Mon, 06 Jun 2011 18:09:13 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
References: <6369CB70BFD88942B9705AC1E639A33822CCE270F5@DC-US1MBEX4.global.avaya.com> <BANLkTin+7fnDjmsfZVWKsmt631B7toRYVw@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222907E9A1@DC-US1MBEX4.global.avaya.com> <1C6C5AB3-6085-4CCA-9F1D-8BA5D98ED651@gmail.com> <4DED2EFA.20004@cisco.com>, <BANLkTimfP2EaJZtPcjOp6s4v+Gk87vetGw@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222907E9AB@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222907E9AB@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "splices@ietf.org" <splices@ietf.org>
Subject: Re: [splices] Using Two Separate Devices to Start a Conversation proposal
X-BeenThere: splices@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Loosely-coupled SIP Devices \(splices\) working group discussion list" <splices.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/splices>, <mailto:splices-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/splices>
List-Post: <mailto:splices@ietf.org>
List-Help: <mailto:splices-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/splices>, <mailto:splices-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jun 2011 22:09:15 -0000

OK, forget what I said about this. I didn't read the details and made a 
bad assumption about them.

	Sorry,
	Paul

On 6/6/2011 5:15 PM, Worley, Dale R (Dale) wrote:
> No, surely it is an ordinary join.  At the far UA, there are two incoming dialogs, each with one audio m= line.  The only oddity is that one dialog is recvonly (at the far UA), and so is never sent media.  The other dialog is sendonly (at the far UA) and so never provides audio to the mixing, but is only sent the result of the mixing.  The effect is that the far UA's input audio is sent only to the second dialog, and the far UA's output audio is driven only by the first dialog.
>
> Dale
>