<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Hotword support</title>
  <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&amp;threadId=5883382" />
  <subtitle>Hotword support</subtitle>
  <id>http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&amp;threadId=5883382</id>
  <updated>2013-05-22T02:28:33Z</updated>
  <dc:date>2013-05-22T02:28:33Z</dc:date>
  <entry>
    <title>RE: Hotword support</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=6228006" />
    <author>
      <name>Anupam Jain</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=6228006</id>
    <updated>2012-08-03T12:24:55Z</updated>
    <published>2012-08-03T12:24:55Z</published>
    <summary type="html">Thanks Raghavendra! This worked great for us.

Also, the doc here(http://www.cisco.com/en/US/docs/routers/access/xml/voice/quick/guide/vxml_qsg.html) does not mention about defining the SIP dial peer for MRCPv2 but your post helped us to add that as well. It may be good to add that to the doc as well. Thanks again!

Regards
Anupam</summary>
    <dc:creator>Anupam Jain</dc:creator>
    <dc:date>2012-08-03T12:24:55Z</dc:date>
  </entry>
  <entry>
    <title>RE: Hotword support</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5883568" />
    <author>
      <name>Raghavendra Gutty Veeranagappa</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5883568</id>
    <updated>2012-06-18T11:13:40Z</updated>
    <published>2012-06-18T11:13:40Z</published>
    <summary type="html">Hi Anupam,

you need to configure mrcp v2 on the gateway.The configurations differ for mrcpv1 and mrcpv2. MRCPv1 uses RTSP protocol whereas MRCPv2 uses SIP protocol.

For MRCPv1:
 
1. ivr asr-server rtsp://ipaddress/recognizer
   ivr tts-server rtsp://ipaddress/synthesizer
 
For MRCPv2:
1. Define voice class uri
    
   voice class uri  nuance sip
    pattern nuance@ipaddress
 
2. ivr asr-server sip:nuance@ipaddress
   ivr tts-server sip:nuance@ipaddress
 
3. Define SIP dial-peer
 
   dial-peer voice 10000 voip
    session protocol sipv2
    destination uri nuance
    dtmf-relay rtp-nte
    codec g711ulaw
    no vad

Thanks,
Raghavendra</summary>
    <dc:creator>Raghavendra Gutty Veeranagappa</dc:creator>
    <dc:date>2012-06-18T11:13:40Z</dc:date>
  </entry>
  <entry>
    <title>RE: Hotword support</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5881765" />
    <author>
      <name>Anupam Jain</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5881765</id>
    <updated>2012-06-18T10:51:16Z</updated>
    <published>2012-06-18T10:51:16Z</published>
    <summary type="html">Raghavendra,

I could not understand your reply.

As you would appreciate, MRCP is a control protocol. So it only passes the parameters to the Recognizer in SET-PARAMS. The protocol version itself may not be deciding whether hotword is supported or not.

The above error comes on the IOS platform only and is not received from Nuance server. So looks like the IOS platform is itself rejecting the hotword property. 

Ideally, MRCPv1 and v2 both support hotword since it is sent in SET-PARAMS to the Recognizer. 

Our question is that when we set the property to hotword, we get the above mentioned error on IOS. So we wanted to know if we need to do any other configuration to enable hotword support on IOS.

Thanks
Anupam</summary>
    <dc:creator>Anupam Jain</dc:creator>
    <dc:date>2012-06-18T10:51:16Z</dc:date>
  </entry>
  <entry>
    <title>RE: Hotword support</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5883462" />
    <author>
      <name>Raghavendra Gutty Veeranagappa</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5883462</id>
    <updated>2012-06-18T10:32:46Z</updated>
    <published>2012-06-18T10:32:46Z</published>
    <summary type="html">Hi Anupam,

yes, IOS supports hotword feature with MRCP V2.

Thanks,
Raghavendra</summary>
    <dc:creator>Raghavendra Gutty Veeranagappa</dc:creator>
    <dc:date>2012-06-18T10:32:46Z</dc:date>
  </entry>
  <entry>
    <title>RE: Hotword support</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5881700" />
    <author>
      <name>Anupam Jain</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5881700</id>
    <updated>2012-06-18T10:24:20Z</updated>
    <published>2012-06-18T10:24:20Z</published>
    <summary type="html">Hi Raghavendra

Thanks for your reply. We are using Nuance Recognizer. 

Actually, MRCPv1 does support hotword as per the MRCP spec. We have been using hotword over MRCPv1 for very long now.

Did you mean to say that hotword is supported only on MRCPv2 on Cisco IOS?

Thanks
Anupam</summary>
    <dc:creator>Anupam Jain</dc:creator>
    <dc:date>2012-06-18T10:24:20Z</dc:date>
  </entry>
  <entry>
    <title>RE: Hotword support</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5883434" />
    <author>
      <name>Raghavendra Gutty Veeranagappa</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5883434</id>
    <updated>2012-06-18T10:18:30Z</updated>
    <published>2012-06-18T10:18:30Z</published>
    <summary type="html">Hi Anupam,

which MRCP server you are using, i think only MRCP v2 supports hotword feature , MRCP v1 ASR server does not support this feature.

Thanks,
Raghavendra</summary>
    <dc:creator>Raghavendra Gutty Veeranagappa</dc:creator>
    <dc:date>2012-06-18T10:18:30Z</dc:date>
  </entry>
  <entry>
    <title>Hotword support</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5883381" />
    <author>
      <name>Anupam Jain</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5883381</id>
    <updated>2012-06-18T09:53:50Z</updated>
    <published>2012-06-18T09:53:50Z</published>
    <summary type="html">We tried to user bargeintype=hotword property (as mentioned in the VXML 2.0 spec) but we
got the following error:
 
1845573: Jun  4 06:18:13.018: //656//AFW_:/vapp_asr:
grammar_id=session:field2503@field.grammar
grammar_id=session:field2504@field.grammar
 
1845574: Jun  4 06:18:13.018: //656//AFW_:/vapp_asr: encoding_name=N/A
1845575: Jun  4 06:18:13.018: //656//AFW_:/vapp_asr:  xml_lang=en-US
[b]1845576: Jun  4 06:18:13.018: //656//AFW_:/vapp_asr: hotword not supported[/b]
1845577: Jun  4 06:18:13.018: //656/E5ED6E5980AB/VXML:/vxml_vapp_asr:  
   CALL_ERROR;
http://192.168.10.60:8080/test-hotword.vxml
   at line 11: fail with vapp error 23
1845578: Jun  4 06:18:13.018: //656/E5ED6E5980AB/VXML:/vxml_formitem_select:  
   loop cnt=0,
1845579: Jun  4 06:18:13.018: //656/E5ED6E5980AB/VXML:/vxml_load_immediate_done:  
   sidp-&gt;status=A
1845580: Jun  4 06:18:13.018: //656/E5ED6E5980AB/VXML:/vxml_throw_error_session_event:  
   async_status=A 
1845581: Jun  4 06:18:13.018: //656/E5ED6E5980AB/VXML:/vxml_event_proc:  
         &lt;event&gt;: event=error.unsupported.property.bargeintype status=0
1845582: Jun  4 06:18:13.018: //656/E5ED6E5980AB/VXML:/vxml_expr_eval:  
   expr=(var _event='error.unsupported.property.bargeintype')
1845583: Jun  4 06:18:13.018: //656/E5ED6E5980AB/VXML:/vxml_expr_eval:  
   expr=(var _message=undefined)
1845584: Jun  4 06:18:13.018: //656/E5ED6E5980AB/VXML:/vxml_default_event_handler:  
   use default event handler
[b]1845585: Jun  4 06:18:13.018: //656//AFW_:/vapp_session_exit_event_name: Exit Event[/b]
[b]error.unsupported.property.bargeintype[/b]

 
 
 
We are using :
Cisco IOS Software, 2800 Software (C2800NM-ADVENTERPRISEK9_IVS-M), Version 15.1(4)M3
 

Cisco 2851 (revision 1.0) with 247808K/14336K bytes of memory.
Processor board ID FHK1325F0RM
2 Gigabit Ethernet interfaces
31 Serial interfaces
1 Channelized E1/PRI port
1 Virtual Private Network (VPN) Module
2 Voice FXS interfaces
DRAM configuration is 64 bits wide with parity enabled.
239K bytes of non-volatile configuration memory.
125440K bytes of ATA CompactFlash (Read/Write)

 
 
I know that hotword property is supported on IOS but not sure if we needs a different version of IOS or a different hardware. Can anyone suggest?
Thanks is advance!
 
Regards
Anupam

&lt;pre style="font-size: 14px; color: #666666; line-height: normal;"&gt;
&lt;/pre&gt;</summary>
    <dc:creator>Anupam Jain</dc:creator>
    <dc:date>2012-06-18T09:53:50Z</dc:date>
  </entry>
</feed>

