Subject: RE: [speechsc] Clarification on speechsynth and speechrecog part of samesession

From: "Shanmugham, Saravanan" <[email-masked]>
Date: Wed, 10 May 2006 11:28:11 -0700

This is a hangover from the MRCPv1 days. 
You proposed changes look fine to me.
 
Sarvi

________________________________

	From: Dave Burke [mailto:[email-masked]] 
	Sent: Monday, May 08, 2006 4:02 AM
	To: [email-masked]
	Subject: [speechsc] Clarification on speechsynth and speechrecog
part of samesession

	In 8.4.2 it says:
	 
	   If the recognizer or signal detector resource is on the same
server
	   as the synthesizer, the server SHOULD recognize their
interactions by
	   their common MRCPv2 channel identifier (ignoring the portion
after
	   "@" which is the resource type) and work with both to provide
kill-
	   on-barge-in support.
	 
	My understanding was that the server can determine a speechrecog
and speechsynth should work in concert simply by virtue of the fact that
they were set up in the same SIP dialog and hence part of the same
session. The paragraph in 8.4.2 anyways moot because the server assigns
the channel identifiers. Suggest something like:
	 
	   If the recognizer or signal detector resource is on the same
server
	   as the synthesizer and are part of the same session, the
server
	   SHOULD work with both to provide kill-on-barge-in support.
	 
	Dave

_______________________________________________
Speechsc mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/speechsc