[Speechsc] MRCPv2 Protocol Basics - Questions
Slawomir Testowy <slawomir.testowy@gmail.com> Fri, 08 May 2009 11:21 UTC
Return-Path: <slawomir.testowy@gmail.com>
X-Original-To: speechsc@core3.amsl.com
Delivered-To: speechsc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FFCD3A70F9 for <speechsc@core3.amsl.com>; Fri, 8 May 2009 04:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level:
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599]
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 Xx6h+y-XppF6 for <speechsc@core3.amsl.com>; Fri, 8 May 2009 04:21:35 -0700 (PDT)
Received: from mail-bw0-f174.google.com (mail-bw0-f174.google.com [209.85.218.174]) by core3.amsl.com (Postfix) with ESMTP id 86E403A6C47 for <speechsc@ietf.org>; Fri, 8 May 2009 04:21:31 -0700 (PDT)
Received: by bwz22 with SMTP id 22so1311118bwz.37 for <speechsc@ietf.org>; Fri, 08 May 2009 04:22:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=Gxh8nPbCSBmNzTC3pJTBjnYQjRqa45FzKRbgTWFzXSs=; b=OfXhT5LbuqXpsLZkMoMj6s+PHJH+wwBHYYEhHv5KlSRMVzHU9NUufgO8HSvUsmI1sm S8uYTeCDEKAt9le6G/y3GsOt6d0RihymwgzLu+OEwQFIxzYK9kuZLC7aZrLxp9dI9Hm9 aa7zaDrimeI8axoeRp8y+x39TVfz9lQUHpteo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=BUiTRnOBXjDRtrZycxsHnFzpy8Z01bd99e3eTDiztsaV20+rUnnFN24O/VkF9PczSb IrZz7DdzBihNuTVQsTQQlYEugBTPaITIFe1FcZkJo5qEuifvUmxkDeJUxSu4GPgZM7IY cqW45arFJmEbdU0ZavWEyHUVCss3AfuU3P6Co=
MIME-Version: 1.0
Received: by 10.204.65.78 with SMTP id h14mr3537422bki.35.1241781776251; Fri, 08 May 2009 04:22:56 -0700 (PDT)
Date: Fri, 08 May 2009 13:22:56 +0200
Message-ID: <8681d1580905080422i446b0aachc7f27746ad464430@mail.gmail.com>
From: Slawomir Testowy <slawomir.testowy@gmail.com>
To: speechsc@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Speechsc] MRCPv2 Protocol Basics - Questions
X-BeenThere: speechsc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Speech Services Control Working Group <speechsc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/speechsc>, <mailto:speechsc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/speechsc>
List-Post: <mailto:speechsc@ietf.org>
List-Help: <mailto:speechsc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/speechsc>, <mailto:speechsc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 May 2009 11:21:36 -0000
Hi, I have few more questions regarding MRCPv2. > 4.2. Managing Resource Control Channels > When the client wants to add a media processing resource to the > session, it issues a SIP re-INVITE transaction. Is it possible to allocate more than one resource of the same type during one SIP dialog? Example in 4.2 shows how to allocate synthesizer and recognizer, but does not specify if there may be e.g. more than one synthesizer. > When the client wants to de-allocate the resource from this session, > it issues a SIP re-INVITE transaction with the server. The SDP MUST > offer the control m-line with port 0. The server MUST then answer > the control m-line with a response of port 0. This de-allocates the > associated MRCPv2 identifier and resource. The server MUST NOT close > the TCP, SCTP or TLS connection if it is currently being shared among > multiple MRCP channels. When all MRCP channels that may be sharing > the connection are released and/or the associated SIP dialog is > terminated, the client or server terminates the connection. Can client open connection with the server, send SET-PARAMS request and close connection? Then open second connection, send SPEAK request and close connection without waiting for any events? > 4.4. MRCPv2 Message Transport > Multiple resource control channels between a client and > a server that belong to different SIP dialogs can share one or more > TLS, TCP or SCTP connections between them; the server and client MUST > support this mode of operation. The individual MRCPv2 messages carry > the MRCPv2 channel identifier in their Channel-Identifier header, > which MUST be used to differentiate MRCPv2 messages from different > resource channels (see Section 6.2.1 for details). Is it possible to use more than one TCP (or TLS or SCTP) connection for one control channel? Can client send messages with the same channel identifier using many connections? -- Slawomir Testowy
- [Speechsc] MRCPv2 Protocol Basics - Questions Slawomir Testowy