Make plans now to attend XMPP integration with CVP 2012/06/14 @ 10:00 AM at Cisco Live! in San Diego. ...Read More

 



Cisco Developer Network will be presenting a CDN Developer Track at Cisco Live! London the week of January 31, 2011.

We are presenting technical sessions which highlight Application Programming interfaces (APIs) and Software Developer Kits (SDKs) for Cisco technologies such as Unified Communications, IOS, and Access Routing Technologies ¿ including the new Cisco Cius ...Read More

 

Recently noticed that there have been repeated questions from our developer community complaining that they can't seem to get the beep to work with <record>. They have set the beep attribute to "true" alright, and the reference guide even says this is supported but why doesn't it work?
...Read More

 

August 01, 2006
Earlier today, as I was typing a comment in our internal issuing-tracking system, I hit backspace to correct a typo. WHAM! I go back to the previous page, and my long-winded comment is gone. Apparently I somehow left the context of the text area (did I tab, or spuriously click, or??), which causes backspace to act as a hotkey for "Back". The web browser was not very forgiving of my mistake.

Are your IVR applications forgiving? They should be.
...Read More

 

Mark Gibbs over at Network World has put together a spiffy little scoring system for customer service systems (including many criteria for IVR systems). How would callers score your IVR using Mark's guidelines? Place a call and find out, you may be surprised.
...Read More

 

If you're using JNDI to connect to your database through Tomcat, then it's possible you've had to deal with database connection pool leaks. Your code tests fine, it's been reviewed, but in load tests or in production your app is unable to acquire database connections, the pool is empty!

Fear not, there are some handy parameters which can be set in your application's XML configuration file (in tomcat/conf/Catalina/YOUR_IP/YOUR_APP.xml):
...Read More

 

Showing 6 results.
Items per Page 50
of 1

CVP Forum

« Back to CVP - All Versions

CVP Nuance Speech Server Integration

Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Dear All,
 
we have one development to integrate CVP Applicaiton with ASR/TTS Nuance Speech Server.
Nuance Speech Server installed in the separate machine.
today we configured Nuance Speech Server in the Cisco CVP Operaiton Console.
Finally we got un-expected error.


<strong style="mso-bidi-font-weight: normal;">Speech Server device with IP Address:
172.23.25.41 and Hostname: awts-asr-tts operation failed. Device could not be
reached. The device may have multiple NIC cards enabled. To resolve the issue
please keep only one NIC card with required IP address enabled. In addition to
the NIC cards change also restart the Unified CVP Resource Manager service on
the device.

Please advice how to resolve this erro in the Operation Console.

Regards
Juluri.
 

It's right in the CVP Config and Admin Guide. You have to configure your gateway.
ip host asr-en-us 10.10.10.1
ip host tts-en-us 10.10.10.2
Use the following configuration on the gateway if you are using Nuance, Scansoft, or IBMWebSphere ASR/TTS servers:

mrcp client rtpsetup enable
ivr asr-server rtsp://asr-en-us/recognizer
ivr tts-server rtsp://tts-en-us/synthesizer

mrcp client timeout connect 5
mrcp client timeout message 5
rtsp client timeout connect 10
rtsp client timeout message 10

Hello i have a similar issue on a CVP integration with vocalizer
and i have follo GW configuration
ip host tts-es-MX 10.10.49.17
ivr tts-server rtsp://tts-es-mx/synthesizer
rtsp client timeout connect 10
rtsp client timeout message 10
mrcp client timeout connect 5
mrcp client timeout message 5
mrcp client rtpsetup enable



and i getting a time out is no working

send me follow error
 
---------------->Caller PC=0x256736A8, Count=123, Event=0x31726CF0
002858: Jan  2 11:56:26.390 CST: //81438//MRCP:/mrcp_process_events:
   event: SPEAK SYNTHESIZER
002859: Jan  2 11:56:26.390 CST: //81438//MRCP:/mrcp_process_events:
   event: SPEAK defered
002860: Jan  2 11:56:31.390 CST: //-1//MRCP:/mrcp_response_handler:
   status=RTSPLIB_STATUS_MESSAGE_TIMEOUT
002861: Jan  2 11:56:31.390 CST: //81438//MRCP:/mrcp_send_synth_app_response:

002862: Jan  2 11:56:31.390 CST: //81438//MRCP:/mrcp_send_synth_app_response:
   Execute MSW CallBack; active_session_id=7,stream_context=0x2B04D6E0
002863: Jan  2 11:56:31.390 CST: //-1//MRCP:/mrcp_reset_fsm_after_failure:
   type=SYNTHESIZER curr[SYNTH_IDLE] last-method
002864: Jan  2 11:56:31.390 CST: //-1//MRCP:/mrcp_disconnect_connect_fsm:
   (0x3169B5C0)
002865: Jan  2 11:56:31.390 CST: //-1//MRCP:/mrcp_get_ev:
   ****>Caller PC=0x256780FC, Count=125, Event=0x31726D40
002866: Jan  2 11:56:31.390 CST: //-1//MRCP:/mrcp_free_ev:
   ---------------->Caller PC=0x256784DC, Count=124, Even


nad i noticed is still selecting en-us
 
any ideas ?

Jose, In your studio application, use an Application Modifier element and set the Language to 'es-mx' (omit the quotes) This should be sent to the synthesizer configured in the gateway which should have the 'es-mx' language on it. On 1/2/2013 1:20 PM, Cisco Developer Community Forums wrote: Jose jaime Vazquez has created a new message in the forum "CVP - All Versions": -------------------------------------------------------------- Hello i have a similar issue on a CVP integration with vocalizer and i have follo GW configuration ip host tts-es-MX 10.10.49.17 ivr tts-server rtsp://tts-es-mx/synthesizer rtsp client timeout connect 10 rtsp client timeout message 10 mrcp client timeout connect 5 mrcp client timeout message 5 mrcp client rtpsetup enable and i getting a time out is no working send me follow error  ---------------->Caller PC=0x256736A8, Count=123, Event=0x31726CF0 002858: Jan 2 11:56:26.390 CST: //81438//MRCP:/mrcp_process_events:   event: SPEAK SYNTHESIZER 002859: Jan 2 11:56:26.390 CST: //81438//MRCP:/mrcp_process_events:   event: SPEAK defered 002860: Jan 2 11:56:31.390 CST: //-1//MRCP:/mrcp_response_handler:   status=RTSPLIB_STATUS_MESSAGE_TIMEOUT 002861: Jan 2 11:56:31.390 CST: //81438//MRCP:/mrcp_send_synth_app_response: 002862: Jan 2 11:56:31.390 CST: //81438//MRCP:/mrcp_send_synth_app_response:   Execute MSW CallBack; active_session_id=7,stream_context=0x2B04D6E0 002863: Jan 2 11:56:31.390 CST: //-1//MRCP:/mrcp_reset_fsm_after_failure:   type=SYNTHESIZER curr[SYNTH_IDLE] last-method 002864: Jan 2 11:56:31.390 CST: //-1//MRCP:/mrcp_disconnect_connect_fsm:   (0x3169B5C0) 002865: Jan 2 11:56:31.390 CST: //-1//MRCP:/mrcp_get_ev:   ****>Caller PC=0x256780FC, Count=125, Event=0x31726D40 002866: Jan 2 11:56:31.390 CST: //-1//MRCP:/mrcp_free_ev:   ---------------->Caller PC=0x256784DC, Count=124, Even nad i noticed is still selecting en-us  any ideas ? -- To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/9863835 or simply reply to this email. -- Janine Graves

Hello Janine  i noticed i was not able to connect to speech server trough port 5060 for MRCPv2 so  i turn off firewall on Windows box (ASR/TTS) and now i see there is some connection on debug MRCP but i still can get audio from TTS .. can you take a look on debug file ??     thanks   Jaime
Attachments:

here is GW config that i am using 
Attachments:

Here's the NSS 9 docs, I'm sure it has some mrcp v2 info in it.
 

Janine Graves:
Here's the NSS 9 docs, I'm sure it has some mrcp v2 info in it.  
Attachments:

Jose,
Try to get one thing (either TTS or ASR but not both) to work first.
First ensure that you are NOT trying to speak TTS and audio files from within one Studio element. There's a bug in Nuance 9 with this. So, do only TTS or only audio URIs in each element. This is true also for Say it Smarts.
Then ensure that for each TTS prompt, you right-click and select the appropriate tts language.
 

Thanks is working now.. the issue was that port 554 was blocked by the same Windwos box ,, the nuance installation dose not add to exceptions the port
Thanks for everthing was very helpfull
Jaime

Phew, that's a relief! Glad to hear you've gotten it working.