From speechsc-bounces@ietf.org Fri Feb 02 00:55:49 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCrOG-0005E5-Pg; Fri, 02 Feb 2007 00:55:16 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCrOF-0005Dz-Sh for speechsc@ietf.org; Fri, 02 Feb 2007 00:55:15 -0500 Received: from szxga01-in.huawei.com ([61.144.161.53]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCrOA-00052n-DZ for speechsc@ietf.org; Fri, 02 Feb 2007 00:55:15 -0500 Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JCT00KT2MX1C8@szxga01-in.huawei.com> for speechsc@ietf.org; Fri, 02 Feb 2007 13:51:01 +0800 (CST) Received: from huawei.com ([172.24.1.18]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JCT0042LMX09Y@szxga01-in.huawei.com> for speechsc@ietf.org; Fri, 02 Feb 2007 13:51:01 +0800 (CST) Received: from hemanth ([10.18.4.189]) by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JCT00LMPMWW3O@szxml03-in.huawei.com> for speechsc@ietf.org; Fri, 02 Feb 2007 13:51:00 +0800 (CST) Date: Fri, 02 Feb 2007 11:20:55 +0530 From: Hemanthkumar To: speechsc@ietf.org Message-id: <003501c7468e$1bbeadd0$bd04120a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Mailer: Microsoft Office Outlook 11 Thread-index: AcdGi0oG5yycWDhDR1CElgat/32chwAAspFQ X-Spam-Score: 0.0 (/) X-Scan-Signature: 6379955759c38e2371a49573a0932fc7 Subject: [Speechsc] About QUERY-VOICEPRINT X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hemanthkc@huawei.com List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2125320516==" Errors-To: speechsc-bounces@ietf.org This is a multi-part message in MIME format. --===============2125320516== Content-type: multipart/related; boundary="Boundary_(ID_jqruwuf/sUGVC6TxjD7sQA)" This is a multi-part message in MIME format. --Boundary_(ID_jqruwuf/sUGVC6TxjD7sQA) Content-type: multipart/alternative; boundary="Boundary_(ID_x54q9EstTQPcJ/mLBARcyQ)" --Boundary_(ID_x54q9EstTQPcJ/mLBARcyQ) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Hi, Whether Voiceprint-Exists header is mandatory for the 2XX Response for QUERY-VOICEPRINT Method. Regards, Hemanth ============================================================================ ============================================================================ === This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! ============================================================================ ============================================================================ === --Boundary_(ID_x54q9EstTQPcJ/mLBARcyQ) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT

Hi,

         Whether Voiceprint-Exists header is mandatory for the 2XX Response for QUERY-VOICEPRINT Method…

 

Regards,

Hemanth

 

===========================================================================================================================================================

This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

===========================================================================================================================================================

 

--Boundary_(ID_x54q9EstTQPcJ/mLBARcyQ)-- --Boundary_(ID_jqruwuf/sUGVC6TxjD7sQA) Content-id: Content-type: image/jpeg; name=image002.jpg Content-transfer-encoding: base64 Content-disposition: attachment; filename=image002.jpg /9j/4AAQSkZJRgABAgEASABIAAD/7QSyUGhvdG9zaG9wIDMuMAA4QklNA+kAAAAAAHgAAwAAAEgA SAAAAAADBgJS//f/9wMPAlsDRwUoA/wAAgAAAEgASAAAAAAC2AIoAAEAAABkAAAAAQADAwMAAAAB Jw8AAQABAAAAAAAAAAAAAAAAYAgAGQGQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA4 QklNA+0AAAAAABAASAAAAAEAAQBIAAAAAQABOEJJTQPzAAAAAAAIAAAAAAAAAAA4QklNBAoAAAAA AAEAADhCSU0nEAAAAAAACgABAAAAAAAAAAI4QklNA/UAAAAAAEgAL2ZmAAEAbGZmAAYAAAAAAAEA L2ZmAAEAoZmaAAYAAAAAAAEAMgAAAAEAWgAAAAYAAAAAAAEANQAAAAEALQAAAAYAAAAAAAE4QklN A/gAAAAAAHAAAP////////////////////////////8D6AAAAAD///////////////////////// ////A+gAAAAA/////////////////////////////wPoAAAAAP////////////////////////// //8D6AAAOEJJTQQAAAAAAAACAAA4QklNBAIAAAAAAAIAADhCSU0ECAAAAAAAEAAAAAEAAAJAAAAC QAAAAAA4QklNBAkAAAAAAqIAAAABAAAAgAAAAAIAAAGAAAADAAAAAoYAGAAB/9j/4AAQSkZJRgAB AgEASABIAAD//gAnRmlsZSB3cml0dGVuIGJ5IEFkb2JlIFBob3Rvc2hvcKggNC4wAP/uAA5BZG9i ZQBkgAAAAAH/2wCEAAwICAgJCAwJCQwRCwoLERUPDAwPFRgTExUTExgRDAwMDAwMEQwMDAwMDAwM DAwMDAwMDAwMDAwMDAwMDAwMDAwBDQsLDQ4NEA4OEBQODg4UFA4ODg4UEQwMDAwMEREMDAwMDAwR DAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDP/AABEIAAIAgAMBIgACEQEDEQH/3QAEAAj/xAE/ AAABBQEBAQEBAQAAAAAAAAADAAECBAUGBwgJCgsBAAEFAQEBAQEBAAAAAAAAAAEAAgMEBQYHCAkK CxAAAQQBAwIEAgUHBggFAwwzAQACEQMEIRIxBUFRYRMicYEyBhSRobFCIyQVUsFiMzRygtFDByWS U/Dh8WNzNRaisoMmRJNUZEXCo3Q2F9JV4mXys4TD03Xj80YnlKSFtJXE1OT0pbXF1eX1VmZ2hpam tsbW5vY3R1dnd4eXp7fH1+f3EQACAgECBAQDBAUGBwcGBTUBAAIRAyExEgRBUWFxIhMFMoGRFKGx QiPBUtHwMyRi4XKCkkNTFWNzNPElBhaisoMHJjXC0kSTVKMXZEVVNnRl4vKzhMPTdePzRpSkhbSV xNTk9KW1xdXl9VZmdoaWprbG1ub2JzdHV2d3h5ent8f/2gAMAwEAAhEDEQA/APROif0Kv6X81T9L j+ar/m/5K0F8rJJIfqlJfKySKn6pSXyskkp+qUl8rJJKfqlJfKySSn6pSXyskkp+qUl8rJJKfqlJ fKySSn//2ThCSU0EBgAAAAAABwABAAAAAQEA//4AJ0ZpbGUgd3JpdHRlbiBieSBBZG9iZSBQaG90 b3Nob3CoIDQuMAD/7gAOQWRvYmUAZIAAAAAB/9sAhAAMCAgNCQ0VDAwVGhQQFBogGxoaGyAiFxcX FxciEQwMDAwMDBEMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMAQ0NDREOERsRERsUDg4OFBQO Dg4OFBEMDAwMDBERDAwMDAwMEQwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAz/wAARCAAYBaAD ASIAAhEBAxEB/90ABABa/8QBPwAAAQUBAQEBAQEAAAAAAAAAAwABAgQFBgcICQoLAQABBQEBAQEB AQAAAAAAAAABAAIDBAUGBwgJCgsQAAEEAQMCBAIFBwYIBQMMMwEAAhEDBCESMQVBUWETInGBMgYU kaGxQiMkFVLBYjM0coLRQwclklPw4fFjczUWorKDJkSTVGRFwqN0NhfSVeJl8rOEw9N14/NGJ5Sk hbSVxNTk9KW1xdXl9VZmdoaWprbG1ub2N0dXZ3eHl6e3x9fn9xEAAgIBAgQEAwQFBgcHBgU1AQAC EQMhMRIEQVFhcSITBTKBkRShsUIjwVLR8DMkYuFygpJDUxVjczTxJQYWorKDByY1wtJEk1SjF2RF VTZ0ZeLys4TD03Xj80aUpIW0lcTU5PSltcXV5fVWZnaGlqa2xtbm9ic3R1dnd4eXp7fH/9oADAMB AAIRAxEAPwCv0T+n4/8AxrP+qavW15J0U/r+P/xrP+qavWg8eKElsWSHZfXWYe4A+ZUMjIFTJBE/ Fc1kXbg63mJP+amk0uesGqdc19Sup2ZrLmWGQxwLR4B35v8A0V0qKlJJJIqUkkkkpSSSSSlJJJJK UkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSS SSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJ KUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpS SSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJ JKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkp SSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJ JJKUkkkkpSSSSSn/0J9G6oKn04zKKXOdYA6x7d1kOP8Ag/3Hs/MXY/sOl/0hYfCT/wCQavnZJArQ /S1HTXVN21+weYa7/vqzcroeQ+Q3XcYOn/mbF89pIaJfpboXRK+k1uDQPUsILyONPotZ/JatRfKq SSX6qSXyqkip+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJ KfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp +qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6 qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqp JfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl 8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXy qkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKq SSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJ KfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp +qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6 qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn/2Q== --Boundary_(ID_jqruwuf/sUGVC6TxjD7sQA)-- --===============2125320516== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc --===============2125320516==-- From speechsc-bounces@ietf.org Thu Feb 08 11:33:47 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HFCCw-0006Ge-Lk; Thu, 08 Feb 2007 11:33:14 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HF3X3-0005N2-QZ for speechsc@ietf.org; Thu, 08 Feb 2007 02:17:26 -0500 Received: from bay0-omc2-s16.bay0.hotmail.com ([65.54.246.152]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HF3LC-0005we-4q for speechsc@ietf.org; Thu, 08 Feb 2007 02:05:11 -0500 Received: from hotmail.com ([65.55.135.94]) by bay0-omc2-s16.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Wed, 7 Feb 2007 23:05:09 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 7 Feb 2007 23:05:09 -0800 Message-ID: Received: from 65.55.135.123 by by130fd.bay130.hotmail.msn.com with HTTP; Thu, 08 Feb 2007 07:05:05 GMT X-Originating-IP: [221.122.54.66] X-Originating-Email: [sorrylala@hotmail.com] X-Sender: sorrylala@hotmail.com From: "lala lala" To: speechsc@ietf.org Bcc: Date: Thu, 08 Feb 2007 07:05:05 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed X-OriginalArrivalTime: 08 Feb 2007 07:05:09.0493 (UTC) FILETIME=[783A3A50:01C74B4F] X-Spam-Score: 0.0 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b X-Mailman-Approved-At: Thu, 08 Feb 2007 11:33:13 -0500 Subject: [Speechsc] a problem with mrcpv2:how can I establish a media control channel X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: speechsc-bounces@ietf.org hi. I wanna make a mrcpv2 server myself,But I have a problem with the sip.First I have got a client for mrcpv2 form the web.Then I use this client to send SIP message to my server with TCP.like this: INVITE sip:mresources@localhost:4900 SIP/2.0 Via: SIP/2.0/TCP;branch=z9hG4bK09a7a775a4f24e1b Max-Forwards: 6 To: MediaServer From: clien_user ;tag=a0ac26c8 Contact: Call-Id: 1cb629ac592a712c Cseq: 665931353 INVITE Content-Type: application/sdp Content-Length: 317 v=0 o=client_user 2890844526 2890842808 IN IP4 zhujin.sinovoice.com s=SomeSIPsession m=application 9 TCP/MRCPv2 c=IN IP4 10.0.0.79 a=setup:active a=connection:new a=resource:speechsynth a=cmid:1 m=audio 37774 RTP/AVP 0 96 c=IN IP4 10.0.0.79 a=rtpmap:0 pcmu/8000 a=rtpmap:96 l16/8000 a=recvonly a=mid:1 Then I pharse the message and send the SIP 200 Ok ,and I give the client a listen port:6000,at this time my server listen this port for mrcp connection.like this: SIP/2.0 200 OK Via: SIP/2.0/TCP;branch=z9hG4bK09a7a775a4f24e1b;received=10.0.0.79 To: MediaServer From: clien_user ;tag=a0ac26c8 Contact: Call-Id: 1cb629ac592a712c Cseq: 665931353 INVITE Content-Type: application/sdp Content-Length: 310 v=0 o=client_user 2890844526 2890842808 IN IP4 10.0.0.79 s=SomeSIPsession m=application 6000 TCP/MRCPv2 c=IN IP4 10.0.0.79 a=setup:passive a=connection:new a=channel:1@speechsynth a=cmid:1 m=audio 7774 RTP/AVP 0 96 c=IN IP4 10.0.0.79 a=rtpmap:0 pcmu/8000 a=rtpmap:96 l16/8000 a=sendonly a=mid:1 Then the client send me the ACK,like this: ACK sip:mresources@10.0.0.79:4900 SIP/2.0 Via: SIP/2.0/TCP;branch=z9hG4bKfbb398e28bc5ca41 Max-Forwards: 60 To: MediaServer ;tag= From: clien_user ;tag=a0ac26c8 Contact: Call-ID: 1cb629ac592a712c CSeq: 665931353 ACK Content-Length: 0 But then I can not get the mrcp message from the port 6000.I don't know if I haven't understand the mrcpv2 protocal yet.I see the client log,It has make the mrcp message just like "MRCP/2.0 486 SPEAK",but it said that "The connection is not exists for Channel-Id\=1@speechsynth".So it can not send the message to my server,I wonder if this time the client should send the mrcp message to my 6000 port.My server should do what after I send the SIP/2.0 200 OK.How can I establish the media control channel by the SIP.Thanks very much! _________________________________________________________________ 享用世界上最大的电子邮件系统— MSN Hotmail。 http://www.hotmail.com _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From speechsc-bounces@ietf.org Thu Feb 08 20:49:12 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HFKsy-0005Ng-51; Thu, 08 Feb 2007 20:49:12 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HFKsx-0005Nb-09 for speechsc@ietf.org; Thu, 08 Feb 2007 20:49:11 -0500 Received: from usaga01-in.huawei.com ([206.16.17.211]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HFKsp-0005xK-Rb for speechsc@ietf.org; Thu, 08 Feb 2007 20:49:10 -0500 Received: from huawei.com (usaga04-in [172.18.9.16]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JD600KN9ADRHP@usaga04-in.huawei.com> for speechsc@ietf.org; Thu, 08 Feb 2007 19:49:03 -0600 (CST) Received: from huawei.com ([172.17.1.36]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JD600F6MADO45@usaga04-in.huawei.com> for speechsc@ietf.org; Thu, 08 Feb 2007 19:49:03 -0600 (CST) Received: from [172.24.1.18] (Forwarded-For: [10.70.145.164]) by szxmc04-in.huawei.com (mshttpd); Fri, 09 Feb 2007 09:49:00 +0800 Date: Fri, 09 Feb 2007 09:49:00 +0800 From: prasanna 70008 Subject: Re: [Speechsc] a problem with mrcpv2:how can I establish a media control channel To: lala lala Message-id: <1bd65381bda2f2.1bda2f21bd6538@huawei.com> MIME-version: 1.0 X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.25 (built Mar 3 2004) Content-type: text/plain; charset=us-ascii Content-language: en Content-transfer-encoding: 7BIT Content-disposition: inline X-Accept-Language: en Priority: normal X-Spam-Score: 0.0 (/) X-Scan-Signature: 2086112c730e13d5955355df27e3074b Cc: speechsc@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: speechsc-bounces@ietf.org Hi, Did you check if the client opened a TCP connection with the server @ 6000 port? Cheers, Prasanna ****************************************************************************************** This email and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! ***************************************************************************************** ----- Original Message ----- From: lala lala Date: Thursday, February 8, 2007 3:05 pm Subject: [Speechsc] a problem with mrcpv2:how can I establish a media control channel > List-Unsubscribe: , > > List-Help: > List-Id: Speech Services Control Working Group > X-OriginalArrivalTime: 08 Feb 2007 07:05:09.0493 (UTC) > FILETIME=[783A3A50:01C74B4F] > > hi. > I wanna make a mrcpv2 server myself,But I have a problem with > the > sip.First I have got a client for mrcpv2 form the web.Then I use > this > client to send SIP message to my server with TCP.like this: > > INVITE sip:mresources@localhost:4900 SIP/2.0 > Via: SIP/2.0/TCP;branch=z9hG4bK09a7a775a4f24e1b > Max-Forwards: 6 > To: MediaServer > From: clien_user > ;tag=a0ac26c8Contact: > Call-Id: 1cb629ac592a712c > Cseq: 665931353 INVITE > Content-Type: application/sdp > Content-Length: 317 > > v=0 > o=client_user 2890844526 2890842808 IN IP4 zhujin.sinovoice.com > s=SomeSIPsession > m=application 9 TCP/MRCPv2 > c=IN IP4 10.0.0.79 > a=setup:active > a=connection:new > a=resource:speechsynth > a=cmid:1 > m=audio 37774 RTP/AVP 0 96 > c=IN IP4 10.0.0.79 > a=rtpmap:0 pcmu/8000 > a=rtpmap:96 l16/8000 > a=recvonly > a=mid:1 > > Then I pharse the message and send the SIP 200 Ok ,and I give > the > client a listen port:6000,at this time my server listen this port > for mrcp > connection.like this: > > SIP/2.0 200 OK > Via: SIP/2.0/TCP;branch=z9hG4bK09a7a775a4f24e1b;received=10.0.0.79 > To: MediaServer > From: clien_user > ;tag=a0ac26c8Contact: > Call-Id: 1cb629ac592a712c > Cseq: 665931353 INVITE > Content-Type: application/sdp > Content-Length: 310 > > v=0 > o=client_user 2890844526 2890842808 IN IP4 10.0.0.79 > s=SomeSIPsession > m=application 6000 TCP/MRCPv2 > c=IN IP4 10.0.0.79 > a=setup:passive > a=connection:new > a=channel:1@speechsynth > a=cmid:1 > m=audio 7774 RTP/AVP 0 96 > c=IN IP4 10.0.0.79 > a=rtpmap:0 pcmu/8000 > a=rtpmap:96 l16/8000 > a=sendonly > a=mid:1 > > Then the client send me the ACK,like this: > > ACK sip:mresources@10.0.0.79:4900 SIP/2.0 > Via: SIP/2.0/TCP;branch=z9hG4bKfbb398e28bc5ca41 > Max-Forwards: 60 > To: MediaServer ;tag= > From: clien_user > ;tag=a0ac26c8Contact: > Call-ID: 1cb629ac592a712c > CSeq: 665931353 ACK > Content-Length: 0 > > But then I can not get the mrcp message from the port 6000.I > don't know > if I haven't understand the mrcpv2 protocal yet.I see the client > log,It has > make the mrcp message just like "MRCP/2.0 486 SPEAK",but it said > that "The > connection is not exists for Channel-Id\=1@speechsynth".So it can > not send > the message to my server,I wonder if this time the client should > send the > mrcp message to my 6000 port.My server should do what after I send > the > SIP/2.0 200 OK.How can I establish the media control channel by > the > SIP.Thanks very much! > > _________________________________________________________________ > ??????????????? MSN Hotmail? http://www.hotmail.com > > > _______________________________________________ > Speechsc mailing list > Speechsc@ietf.org > https://www1.ietf.org/mailman/listinfo/speechsc > _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From speechsc-bounces@ietf.org Sun Feb 11 11:49:26 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HGHsi-0005YH-S9; Sun, 11 Feb 2007 11:48:52 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HFEuy-00058N-Rn for speechsc@ietf.org; Thu, 08 Feb 2007 14:26:52 -0500 Received: from out002.iad.hostedmail.net ([209.225.56.24]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HFEuw-000688-3X for speechsc@ietf.org; Thu, 08 Feb 2007 14:26:52 -0500 Received: from ATL1VEXC020.usdom003.tco.tc ([10.158.7.32]) by out002.iad.hostedmail.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 8 Feb 2007 14:26:53 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 8 Feb 2007 14:28:56 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: m=application line grammar in the MRCPv2 context Thread-Index: AcdLt1+/sZsswiLFTu6Po3fPhvI40A== From: "Vadim.Ivlev" To: X-OriginalArrivalTime: 08 Feb 2007 19:26:53.0620 (UTC) FILETIME=[16C11740:01C74BB7] X-Spam-Score: 0.5 (/) X-Scan-Signature: 162d87dc0b780d17da9b1934777fd451 X-Mailman-Approved-At: Sun, 11 Feb 2007 11:48:50 -0500 Subject: [Speechsc] m=application line grammar in the MRCPv2 context X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2141446914==" Errors-To: speechsc-bounces@ietf.org This is a multi-part message in MIME format. --===============2141446914== Content-class: urn:content-classes:message Content-Type: multipart/related; type="multipart/alternative"; boundary="----_=_NextPart_001_01C74BB7.12F9260F" This is a multi-part message in MIME format. ------_=_NextPart_001_01C74BB7.12F9260F Content-Type: multipart/alternative; boundary="----_=_NextPart_002_01C74BB7.12F9260F" ------_=_NextPart_002_01C74BB7.12F9260F Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable To Whom It May Concern: =20 Grammar for m=3Dapplication line seems to contradict the SDP RFC4566, which requires at least one format: =20 media-field =3D %x6d "=3D" media SP port ["/" integer] SP proto 1*(SP fmt) CRLF =20 whereas=20 m=3Dapplication 9 TCP/MRCPv2 has no fmt field. =20 Should this m-line look like: m=3Dapplication 9 TCP MRCPv2 or m=3Dapplication 9 TCP/TLS MRCPv2 this problem would be eliminated. =20 Sincerely, =20 Vadim Ivlev Senior Software Engineer 220 Perry Parkway Gaithersburg, MD 20877 Tel.: (240) 364-5205 Fax: (301) 977-8846 E-mail: vadim@broadsoft.com =20 =20 ------_=_NextPart_002_01C74BB7.12F9260F Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
To = Whom It May=20 Concern:
 
Grammar for m=3Dapplication line seems to contradict the SDP = RFC4566, which requires at least one=20 format:
 
   media-field=20 =3D         %x6d "=3D" media SP = port ["/"=20 integer]
          &= nbsp;           &n= bsp; =20 SP proto 1*(SP fmt) CRLF
 
whereas
    m=3Dapplication 9 = TCP/MRCPv2
has no fmt field.
 
Should this = m-line look=20 like:
   =20 m=3Dapplication 9 TCP MRCPv2
or
    m=3Dapplication 9 TCP/TLS=20 MRCPv2
this problem would be = eliminated.
 
Sincerely,
 

Vadim Ivlev

Senior = Software=20 Engineer

220 Perry=20 Parkway

Gaithersburg, MD 20877

Tel.: (240)=20 364-5205

Fax: (301)=20 977-8846

E-mail:=20 vadim@broadsoft.com

 

 
------_=_NextPart_002_01C74BB7.12F9260F-- ------_=_NextPart_001_01C74BB7.12F9260F Content-Type: image/jpeg; name="image002.jpg" Content-Transfer-Encoding: base64 Content-ID: <195462219@08022007-3223> Content-Description: image002.jpg Content-Location: image002.jpg /9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7 Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAYAIYDASIA AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3 ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3 uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwC14Wbx J4nhupT4wnsvIkCbXwd2Rn2pf7c8RaH4ju9Hk1xtVQ2kjeaMZjPllgw9CCKwvC8HhCeK6PiW8kgk Eg8kI7DK456D1qe1msLPxLfweGJJLjTprCVZWlGSF8sljkjIAOOaAOg8Laf4q8TaKuor4wurcF2T YV3dO+adofivWdI13U9J1W/XUIbRTi4YAFWGMc+/oemKqeCPA9h4i8MLfTX19BK0roPIlwgx04xW TY6dLa6vq3huONJZoizfaAP3jBcfpyDQB2ttqV/rVnLqFowkhT+InAXB+bOR2HPHWrHhvxlb3t79 iabfltoLDBz9K46xu9c0y3jsGkuJIpdwumDnIBG1Qn93b97jqaztmoaXb3Oo6ncszBTHE7N8zt6g 9fera0OeEm5bmpr3jHX5tdv9T0m6mGl6dPHGyKfkbnHP+8Qf0rq/HWvzp4Eg1fSbuSAzyRMskZwd pBJFcxofhjxg/hV7S0i09bHUV8x1n/1jAgYJPboMViyaq7fD298P3TbbiwvUKIx52kkEfg2fzqDo Ozi8OeM5tJjv7XxhPJLJCJVhdMA5Gduf/rViz/EjWZPBxUMI9RS58mS4VBnZtJzjoG4I/CultfiN 4a0/w/bp9v8AOuIbZV8lEbJYKBjpjrXNeD7TSYfDOp6l4pRY9Pv7lUj3qeWG45XHPUnB9qANm10T xBdWsU4+IePMUNhdpAyOnWn+Ita1jwV4btrL+0jqWp3szBLqRfuJx0HfqAPrWDe2nwuWzma3vp/O 2HywjOTuxxwRisNbLV7nwbaasUlmt9PvGCZydqEKSR/s7hj2zQB3U/hvxta6W1+PFkz3ccfmNbbB sOBkqD/9as6b4k6lceDbeS3EUeqTXP2Z5McLwDvAPAJyPpzW9d/E3w22hSXEV5uuXiIW22nfuI6H t1715pLpM9r4d0qa8RoxqF+SisMEphRn8cmgDv4/Dnid41abx8UkIyyoAQD+dZ3iix8U+GtE/tT/ AITC5ul8xUCKoXOe+ea3v+FU+F/+ed3/AOBBqr8SrODTfh3HZQZEMEsUabjk4Gcc0ANsfDHiy9sL e7HjW5QTxLJt8vOMjOOvvRXYaF/yL+nf9esX/oIooAb/AMI9on/QIsv+/C/4VNBpWnW0ckcFhbRJ Iu1wkSgMPQ8ciiigCW1tLayh8m1t44Iwc7I1CjP0FMGm2K3bXi2kK3LdZhGA5/HrRRQBFJo9jK25 oRmlk0bTZ41jnsYJlU5USoGwfxoooAuKqooVQFUDAAHAFUZdC0iaV5ZdLtHkc5ZmhUlj6k4oooAa vh/RVORpNkCP+ndf8Kk1S0im0qaP7HDcmOMtFDJGGUsAdvFFFAnsc1HEQilvBNtu4yREoyOc8bev HA960YNY1MQ+WnhqVIwzIqBgoAAz0x+HHGaKKvTsYLm7/kZiiZpxdjwbbqAN3EA3sfm9RwOAfWtS KebVpohqPhseXGheNpQGKuADwCOM9u9FFDt2CPNdakcuua3KipBos0TvGrbyC205GRgj0yP/AK1Q T6jqD6eV1bQPtcKLvkMqgKCBnoRjqOvvRRT07Ety3ubGgamuqaXFMtqbdQuFUA7MAkDacDI4oooq JKzNqbcoJs//2Q== ------_=_NextPart_001_01C74BB7.12F9260F-- --===============2141446914== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc --===============2141446914==-- From speechsc-bounces@ietf.org Sun Feb 11 21:09:31 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HGQdF-0006kA-PN; Sun, 11 Feb 2007 21:09:29 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HGQdE-0006k3-8G for speechsc@ietf.org; Sun, 11 Feb 2007 21:09:28 -0500 Received: from usaga01-in.huawei.com ([206.16.17.211]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGQdC-000310-Pm for speechsc@ietf.org; Sun, 11 Feb 2007 21:09:28 -0500 Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JDB00LVFVBPJ6@usaga01-in.huawei.com> for speechsc@ietf.org; Sun, 11 Feb 2007 18:09:25 -0800 (PST) Received: from huawei.com ([172.17.1.36]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JDB00DMJVBNSK@usaga01-in.huawei.com> for speechsc@ietf.org; Sun, 11 Feb 2007 18:09:25 -0800 (PST) Received: from [172.24.1.18] (Forwarded-For: [10.70.145.164]) by szxmc04-in.huawei.com (mshttpd); Mon, 12 Feb 2007 10:09:25 +0800 Date: Mon, 12 Feb 2007 10:09:25 +0800 From: prasanna 70008 Subject: Re: [Speechsc] a problem with mrcpv2:how can I establish a media control channel To: lala lala Message-id: <1d1760b1d18750.1d187501d1760b@huawei.com> MIME-version: 1.0 X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.25 (built Mar 3 2004) Content-type: text/plain; charset=us-ascii Content-language: en Content-transfer-encoding: 7BIT Content-disposition: inline X-Accept-Language: en Priority: normal X-Spam-Score: 0.0 (/) X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e Cc: speechsc@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: speechsc-bounces@ietf.org Hi, A silly query... did you check if your server has bound to 6000 port and listening on it? Cheers, Prasanna ****************************************************************************************** This email and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! ***************************************************************************************** ----- Original Message ----- From: lala lala Date: Friday, February 9, 2007 10:01 am Subject: Re: [Speechsc] a problem with mrcpv2:how can I establish a media control channel > I use the software"Active Ports" and find the client dose not > create a > connection with the 6000 port but also gives me a ACK?If a ACK be > gived to > me means that the connection has been established. > > And who can give me another client for mrcpv2 and the client > source > code.Thanks very much! > > > >From: prasanna 70008 > >To: lala lala > >CC: speechsc@ietf.org > >Subject: Re: [Speechsc] a problem with mrcpv2:how can I establish > a media > control channel > >Date: Fri, 09 Feb 2007 09:49:00 +0800 > > > >Hi, > >Did you check if the client opened a TCP connection with the > server @ 6000 > port? > >Cheers, > >Prasanna > >****************************************************************************************** > > > This email and its attachments contain confidential information > from > HUAWEI, which is intended only for the person or entity whose > address is > listed above. Any use of the information contained herein in any > way > (including, but not limited to, total or partial disclosure, > reproduction, > or dissemination) by persons other than the intended recipient(s) > is > prohibited. If you receive this e-mail in error, please notify the > sender > by phone or email immediately and delete it! > > > ***************************************************************************************** > > > > >----- Original Message ----- > >From: lala lala > >Date: Thursday, February 8, 2007 3:05 pm > >Subject: [Speechsc] a problem with mrcpv2:how can I establish a > media control channel > > > > > List-Unsubscribe: > ,> > request@ietf.org?subject=unsubscribe>> > List-Help: request@ietf.org?subject=help>> > List-Id: Speech Services Control > Working Group > > > X-OriginalArrivalTime: 08 Feb 2007 07:05:09.0493 (UTC) > > > FILETIME=[783A3A50:01C74B4F] > > > > > > hi. > > > I wanna make a mrcpv2 server myself,But I have a problem with > > > the > > > sip.First I have got a client for mrcpv2 form the web.Then I use > > > this > > > client to send SIP message to my server with TCP.like this: > > > > > > INVITE sip:mresources@localhost:4900 SIP/2.0 > > > Via: SIP/2.0/TCP;branch=z9hG4bK09a7a775a4f24e1b > > > Max-Forwards: 6 > > > To: MediaServer > > > From: clien_user > > > ;tag=a0ac26c8Contact: > > > Call-Id: 1cb629ac592a712c > > > Cseq: 665931353 INVITE > > > Content-Type: application/sdp > > > Content-Length: 317 > > > > > > v=0 > > > o=client_user 2890844526 2890842808 IN IP4 zhujin.sinovoice.com > > > s=SomeSIPsession > > > m=application 9 TCP/MRCPv2 > > > c=IN IP4 10.0.0.79 > > > a=setup:active > > > a=connection:new > > > a=resource:speechsynth > > > a=cmid:1 > > > m=audio 37774 RTP/AVP 0 96 > > > c=IN IP4 10.0.0.79 > > > a=rtpmap:0 pcmu/8000 > > > a=rtpmap:96 l16/8000 > > > a=recvonly > > > a=mid:1 > > > > > > Then I pharse the message and send the SIP 200 Ok ,and I give > > > the > > > client a listen port:6000,at this time my server listen this port > > > for mrcp > > > connection.like this: > > > > > > SIP/2.0 200 OK > > > Via: SIP/2.0/TCP;branch=z9hG4bK09a7a775a4f24e1b;received=10.0.0.79 > > > To: MediaServer > > > From: clien_user > > > > ;tag=a0ac26c8Contact: > > > > Call-Id: 1cb629ac592a712c > > > Cseq: 665931353 INVITE > > > Content-Type: application/sdp > > > Content-Length: 310 > > > > > > v=0 > > > o=client_user 2890844526 2890842808 IN IP4 10.0.0.79 > > > s=SomeSIPsession > > > m=application 6000 TCP/MRCPv2 > > > c=IN IP4 10.0.0.79 > > > a=setup:passive > > > a=connection:new > > > a=channel:1@speechsynth > > > a=cmid:1 > > > m=audio 7774 RTP/AVP 0 96 > > > c=IN IP4 10.0.0.79 > > > a=rtpmap:0 pcmu/8000 > > > a=rtpmap:96 l16/8000 > > > a=sendonly > > > a=mid:1 > > > > > > Then the client send me the ACK,like this: > > > > > > ACK sip:mresources@10.0.0.79:4900 SIP/2.0 > > > Via: SIP/2.0/TCP;branch=z9hG4bKfbb398e28bc5ca41 > > > Max-Forwards: 60 > > > To: MediaServer ;tag= > > > From: clien_user > > > ;tag=a0ac26c8Contact: > > > Call-ID: 1cb629ac592a712c > > > CSeq: 665931353 ACK > > > Content-Length: 0 > > > > > > But then I can not get the mrcp message from the port 6000.I > > > don't know > > > if I haven't understand the mrcpv2 protocal yet.I see the client > > > log,It has > > > make the mrcp message just like "MRCP/2.0 486 SPEAK",but it said > > > that "The > > > connection is not exists for Channel-Id\=1@speechsynth".So it can > > > not send > > > the message to my server,I wonder if this time the client should > > > send the > > > mrcp message to my 6000 port.My server should do what after I send > > > the > > > SIP/2.0 200 OK.How can I establish the media control channel by > > > the > > > SIP.Thanks very much! > > > > > > _________________________________________________________________ > > > ??????????????? MSN Hotmail? http://www.hotmail.com > > > > > > > > > _______________________________________________ > > > Speechsc mailing list > > > Speechsc@ietf.org > > > https://www1.ietf.org/mailman/listinfo/speechsc > > > > > > > _________________________________________________________________ > ?????????????? MSN Messenger: http://messenger.msn.com/cn > > _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From speechsc-bounces@ietf.org Thu Feb 15 09:30:22 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HHhcV-0006PA-8s; Thu, 15 Feb 2007 09:29:59 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HHhcT-0006Oe-Un for speechsc@ietf.org; Thu, 15 Feb 2007 09:29:57 -0500 Received: from szxga01-in.huawei.com ([61.144.161.53]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHhcR-0006WF-9i for speechsc@ietf.org; Thu, 15 Feb 2007 09:29:57 -0500 Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JDI00KK3DKJVC@szxga01-in.huawei.com> for speechsc@ietf.org; Thu, 15 Feb 2007 22:29:07 +0800 (CST) Received: from huawei.com ([172.24.1.18]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JDI00KO4DKJGJ@szxga01-in.huawei.com> for speechsc@ietf.org; Thu, 15 Feb 2007 22:29:07 +0800 (CST) Received: from vADIRAJ ([10.18.4.23]) by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JDI00AF4DKHON@szxml03-in.huawei.com> for speechsc@ietf.org; Thu, 15 Feb 2007 22:29:07 +0800 (CST) Date: Thu, 15 Feb 2007 19:59:05 +0530 From: Vadiraj To: speechsc@ietf.org Message-id: <007801c7510d$a5e1eca0$1704120a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-Priority: 3 X-MSMail-priority: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Subject: [Speechsc] content-length header in GET-PARAMS method X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1223881124==" Errors-To: speechsc-bounces@ietf.org This is a multi-part message in MIME format. --===============1223881124== Content-type: multipart/alternative; boundary="Boundary_(ID_N6E0WzbW3F+JPUA4/cPjOg)" This is a multi-part message in MIME format. --Boundary_(ID_N6E0WzbW3F+JPUA4/cPjOg) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Hi, I have a query on handling of content-length header in GET-PARAMS method. MRCP draft-11 is not clear on the handling of content-length header in GET-PARAMS method. Although there is no use case where we can send any content in GET-PARAMS, still some generic implementation can send Content-Length=0 in GET-PARAMS method. As there is no supportive text in the draft to prohibit this, it is possible to have Content-Length=0 in GET-PARAMS. Should the server respond with 403 "Un Suppoted Header" for such a Request? If so can we make it clear in the draft ? Thanks in Advance, -Vadiraj --Boundary_(ID_N6E0WzbW3F+JPUA4/cPjOg) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: 7BIT
Hi,
 
  I have a query on handling of content-length header in GET-PARAMS method.
  
  MRCP draft-11 is not clear on the handling of content-length header in GET-PARAMS method.
 
   Although there is no use case where we can send any content in GET-PARAMS, still some generic implementation can send Content-Length=0 in GET-PARAMS method.
As there is no supportive text in the draft to prohibit this, it is possible to have Content-Length=0 in GET-PARAMS.
 
Should the server respond with 403 "Un Suppoted Header" for such a Request? If so can we make it clear in the draft ?
 
Thanks in Advance,
-Vadiraj
--Boundary_(ID_N6E0WzbW3F+JPUA4/cPjOg)-- --===============1223881124== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc --===============1223881124==-- From speechsc-bounces@ietf.org Mon Feb 26 08:56:38 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HLgL6-0004uU-B9; Mon, 26 Feb 2007 08:56:28 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HLgL5-0004uL-Ml for speechsc@ietf.org; Mon, 26 Feb 2007 08:56:27 -0500 Received: from web52704.mail.yahoo.com ([206.190.48.227]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HLgKu-0004X7-J3 for speechsc@ietf.org; Mon, 26 Feb 2007 08:56:27 -0500 Received: (qmail 53798 invoked by uid 60001); 26 Feb 2007 13:56:15 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=u2dk1mQu8hDA9CHWw35O9ofoYII+6/FH3fwuWQII3ptX47M3Pgdg4fISoZsKNkpYv+ZRkw+LdHWG8ukk/4Q//sfdWSu668U1iCY8Vxv+rQokD5tBKLEG9UcrOgBGWT7r75WH8CSL/al1igp4ZOjcBW9jcE2JmRb/wGFX0kOun8E=; X-YMail-OSG: pcBoP_sVM1n6dHOldiq4TGZORHniDpSsqtZxDvEX8odMZ0PUzbAFdDkB4k37Rhp9e5oP80V4bkb6UnGQVn.IRtxlO8IqcyNoCcxDCiPs6tAAqa24BskPGXvtS_tfGQmL.1TryfDxSLVfLg-- Received: from [195.69.162.137] by web52704.mail.yahoo.com via HTTP; Mon, 26 Feb 2007 05:56:15 PST X-Mailer: YahooMailRC/368.8 YahooMailWebService/0.6.132.8 Date: Mon, 26 Feb 2007 05:56:15 -0800 (PST) From: Arsen Chaloyan To: speechsc@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <821140.49484.qm@web52704.mail.yahoo.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Subject: [Speechsc] Query regarding status-code in request-line X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: speechsc-bounces@ietf.org Some of the requests contain status-code in start-line (STOP, BARGE-IN-OCCU= RRED,...), while the others are not (SPEAK, CONTROL,...)=0A=0AAccording to = MRCP v2 specification the request line is=0Arequest-line =3D mrcp-version S= P message-length SP method-name SP request-id CRLF=0A=0AI guess, it should= be=0Arequest-line =3D mrcp-version SP message-length SP method-name SP r= equest-id [SP status-code] CRLF=0A=0Awith optional status-code at the end o= f the start-line.=0A=0APlease, share your consideration.=0AThanks,=0AArsen.= =0A=0A=0A=0A=0A =0A________________________________________________________= ____________________________=0AFood fight? Enjoy some healthy debate =0Ain = the Yahoo! Answers Food & Drink Q&A.=0Ahttp://answers.yahoo.com/dir/?link= =3Dlist&sid=3D396545367 _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From speechsc-bounces@ietf.org Tue Feb 27 13:53:20 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HM7Rj-0008Lr-9T; Tue, 27 Feb 2007 13:53:07 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HM7Rh-0008Lh-HC for speechsc@ietf.org; Tue, 27 Feb 2007 13:53:05 -0500 Received: from usremg02.bea.com ([66.248.192.22]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HM7Rg-0004Fr-4g for speechsc@ietf.org; Tue, 27 Feb 2007 13:53:05 -0500 Received: from usremr02.bea.com (mailrelay.bea.com [10.160.29.92]) by usremg02.bea.com (Switch-3.2.2/Switch-3.2.2) with ESMTP id l1RIr20h021423 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 27 Feb 2007 10:53:02 -0800 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by usremr02.bea.com (Switch-3.2.2/Switch-3.2.2) with ESMTP id l1RIqv7X001216 for ; Tue, 27 Feb 2007 10:53:01 -0800 Received: from 172.24.29.89 ([172.24.29.89]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Tue, 27 Feb 2007 18:52:59 +0000 User-Agent: Microsoft-Entourage/11.3.3.061214 Date: Sun, 25 Feb 2007 19:45:24 -0800 From: Eric Burger To: Message-ID: Thread-Topic: MRCPv2 Status Thread-Index: AcdZP2ZzpQ9opMUyEdukwwAWy4mm/w== Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.5.0.283055, Antispam-Data: 2007.2.21.151434 X-Spam-Score: 0.3 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Subject: [Speechsc] MRCPv2 Status X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: speechsc-bounces@ietf.org You may be wondering why we've gone silent for a few months. In preparation of the IESG Shepherding write-up, quite a few typographical errors, many of which had protocol implications, were found. There were enough to the point where it was clear that the document would never pass IESG muster. In addition, many, many, many protocol elements were listed as SHOULD's. Upon close examination, many are really MUST's, and a bunch are MAY's. This is a very important distinction in that interoperability of protocols tend to be directly proportional to the ratio of MUST:SHOULD. That is, the fewer SHOULDs, the more interoperable the protocol is. The litmus test is that every SHOULD clause has to have an UNLESS clause that explains why the clause is a SHOUD and not a MUST (or MAY). A construction that ends up "A MRCPv2 server SHOULD do foo unless it does not fell like it" really means that foo is a MAY. Likewise, "A MRCPv2 client SHOULD do bar," where there is no clear reason bar should ever not be done, really means that bar is a MUST. The editors are going through a final scrubbing of the document and will be producing a new draft before the Prague draft deadline. We will do another Work Group Last Call (WGLC) on that document before redoing the IESG Shepherd document and passing it to the IESG. As before, we will NOT entertain WGLC comments that will extend the protocol. We will save that for work group re-chartering, if that is what the IESG and work group wishes to do at that time. _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From speechsc-bounces@ietf.org Tue Feb 27 13:53:25 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HM7Rx-000065-Kc; Tue, 27 Feb 2007 13:53:21 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HM7Rw-00005U-0r for speechsc@ietf.org; Tue, 27 Feb 2007 13:53:20 -0500 Received: from usremg01.bea.com ([66.248.192.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HM7Ru-0004Jg-JW for speechsc@ietf.org; Tue, 27 Feb 2007 13:53:20 -0500 Received: from usremr02.bea.com (usremr02.bea.com [10.160.29.92]) by usremg01.bea.com (Switch-3.2.2/Switch-3.2.2) with ESMTP id l1RIr1bq005770 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 27 Feb 2007 10:53:15 -0800 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by usremr02.bea.com (Switch-3.2.2/Switch-3.2.2) with ESMTP id l1RIqv7V001216; Tue, 27 Feb 2007 10:52:59 -0800 Received: from 172.24.29.89 ([172.24.29.89]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Tue, 27 Feb 2007 18:52:59 +0000 User-Agent: Microsoft-Entourage/11.3.3.061214 Date: Sun, 25 Feb 2007 19:37:52 -0800 Subject: Re: [Speechsc] m=application line grammar in the MRCPv2 context From: Eric Burger To: "Vadim.Ivlev" Message-ID: Thread-Topic: [Speechsc] m=application line grammar in the MRCPv2 context Thread-Index: AcdLt1+/sZsswiLFTu6Po3fPhvI40ANhvlL3 In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.5.0.283055, Antispam-Data: 2007.2.21.151434 X-Spam-Score: 0.3 (/) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 Cc: speechsc@ietf.org X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: speechsc-bounces@ietf.org This is a situation where I cannot believe anyone, including MYSELF, missed this one. Vadim - you get the prize for finding a show-stopper bug BEFORE the IESG finds it and halts publication. Of all the comments and discussion in the past six months, this one will require a fix to the specification. We have directed the editors to correct the text. I am sorry in that on the one hand, this may break existing MRCPv2 implementations. HOWEVER, not fixing this means a standard SDP parser will not properly parse MRCPv2 SDP, which is not acceptable. On 2/8/07 2:28 PM, "Vadim.Ivlev" wrote: > To Whom It May Concern: > > Grammar for m=application line seems to contradict the SDP RFC4566, which > requires at least one format: > > media-field = %x6d "=" media SP port ["/" integer] > SP proto 1*(SP fmt) CRLF > > whereas > m=application 9 TCP/MRCPv2 > has no fmt field. > > Should this m-line look like: > m=application 9 TCP MRCPv2 > or > m=application 9 TCP/TLS MRCPv2 > this problem would be eliminated. > > Sincerely, > > Vadim Ivlev > Senior Software Engineer > 220 Perry Parkway > Gaithersburg, MD 20877 > Tel.: (240) 364-5205 > Fax: (301) 977-8846 > E-mail: vadim@broadsoft.com > > > > > _______________________________________________ > Speechsc mailing list > Speechsc@ietf.org > https://www1.ietf.org/mailman/listinfo/speechsc _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc From speechsc-bounces@ietf.org Tue Feb 27 17:22:32 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMAiG-0006D9-8p; Tue, 27 Feb 2007 17:22:24 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HM9SD-0000dJ-EU for speechsc@ietf.org; Tue, 27 Feb 2007 16:01:47 -0500 Received: from smtp2.wanadoo.co.uk ([193.252.22.157] helo=smtp2.freeserve.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HM9RO-0001LA-FJ for speechsc@ietf.org; Tue, 27 Feb 2007 16:01:41 -0500 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3113.me.freeserve.com (SMTP Server) with ESMTP id 0B8435C00085 for ; Tue, 27 Feb 2007 22:00:50 +0100 (CET) Received: from Codalogic (user-54433ea2.lns5-c7.dsl.pol.co.uk [84.67.62.162]) by mwinf3113.me.freeserve.com (SMTP Server) with SMTP id B9A125C00082 for ; Tue, 27 Feb 2007 22:00:49 +0100 (CET) X-ME-UUID: 20070227210049760.B9A125C00082@mwinf3113.me.freeserve.com Message-ID: <003601c75ab2$5a570780$1300a8c0@Codalogic> From: "Pete Cordell" To: References: Date: Tue, 27 Feb 2007 21:00:40 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Spam-Score: 0.1 (/) X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027 Subject: [Speechsc] Whitespace in ABNF X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: speechsc-bounces@ietf.org I must admit I've only scanned SPEECHSC, but one thing I noticed with the ABNF is that some times the white space seems implicit, and some times it seems explicit. For example: portlist = portnum *("," *LWS portnum) seems explicit about mentioning where whitespace is allowed, whereas: cookie2 = attribute "=" value *(";" cookie-av2) (in the same section) presumably allows implied whitespace. Also, content-encoding = "Content-Encoding" ":" *WSP content-coding *(*WSP "," *WSP content-coding *WSP ) CRLF and: cache-control = "Cache-Control" ":" [*WSP cache-directive *( *WSP "," *WSP cache-directive *WSP )] CRLF seem quite explicit about whitespace (btw - should the WSPs be LWSs?), but: active-request-id-list = "Active-Request-Id-List" ":" request-id *("," request-id) CRLF seems implicit. If you're polishing up the text, would it be worth doing the same to the ABNF? Also, while I found text that said leading and trailing whitespace in field content could be removed, and intervening whitespace collapsed, I didn't find anything that said LWS can go between any token (although I might have missed it). Regards, Pete. -- ============================================= Pete Cordell Tech-Know-Ware Ltd for XML to C++ data binding visit http://www.tech-know-ware.com/lmx (or http://www.xml2cpp.com) ============================================= ----- Original Message ----- From: "Eric Burger" To: Sent: Monday, February 26, 2007 3:45 AM Subject: [Speechsc] MRCPv2 Status > You may be wondering why we've gone silent for a few months. In > preparation > of the IESG Shepherding write-up, quite a few typographical errors, many > of > which had protocol implications, were found. There were enough to the > point > where it was clear that the document would never pass IESG muster. > > In addition, many, many, many protocol elements were listed as SHOULD's. > Upon close examination, many are really MUST's, and a bunch are MAY's. > This > is a very important distinction in that interoperability of protocols tend > to be directly proportional to the ratio of MUST:SHOULD. That is, the > fewer > SHOULDs, the more interoperable the protocol is. > > The litmus test is that every SHOULD clause has to have an UNLESS clause > that explains why the clause is a SHOUD and not a MUST (or MAY). A > construction that ends up "A MRCPv2 server SHOULD do foo unless it does > not > fell like it" really means that foo is a MAY. Likewise, "A MRCPv2 client > SHOULD do bar," where there is no clear reason bar should ever not be > done, > really means that bar is a MUST. > > The editors are going through a final scrubbing of the document and will > be > producing a new draft before the Prague draft deadline. We will do > another > Work Group Last Call (WGLC) on that document before redoing the IESG > Shepherd document and passing it to the IESG. > > As before, we will NOT entertain WGLC comments that will extend the > protocol. We will save that for work group re-chartering, if that is what > the IESG and work group wishes to do at that time. > > _______________________________________________________________________ > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the individual > or entity named in this message. If you are not the intended recipient, > and have received this message in error, please immediately return this > by email and then delete it. > > _______________________________________________ > Speechsc mailing list > Speechsc@ietf.org > https://www1.ietf.org/mailman/listinfo/speechsc > _______________________________________________ Speechsc mailing list Speechsc@ietf.org https://www1.ietf.org/mailman/listinfo/speechsc