Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- Technology and Support
- DevNet
- DevNet Collaboration
- Collaboration Knowledge Base
- Nuance ASR not working with CVP
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2889
Views
1
Helpful
0
Comments
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-24-2014 06:06 PM
This document was generated from CDN thread
Created by: Manoj Varghese on 10-01-2014 11:20:43 AM
I am trying to make CVP 9 works with Nuance for ASR/TTS. TTS is working fine. But when I tried to use ASR using inline or external grammar, ASR doesn't recognise the voice/dtmf input. I have attached the vxml gateway logs for call with application is using inline grammar for ASR and no voice input is detected by the application. Is there anywhere on Nuance server I can lookout to see why its not working?
Subject: RE: Nuance ASR not working with CVP
Replied by: Janine Graves on 10-01-2014 07:57:10 PM
The default is that the gateway will collect the DTMF tones. To use speech reco, you have to configure it in the Studio app under Project/Properties/CallStudio/General
Subject: RE: Nuance ASR not working with CVP
Replied by: Janine Graves on 12-01-2014 09:25:41 AM
David,
That behavior seems bizarre.
1.What do you have set for the NoInput timeout in the Settings tab of
the Form element? Perhaps you have something like '5' (which would mean 5
milliseconds) instead of '5s' (to indicate seconds).
Post a picture of the Settings tab.
2. Try using a Digits element (which uses a 'builtin' grammar) to
collect some digits using speech reco - do you get the same behavior
where Nuance only hears speech during the prompt, but not after the
prompt?
3. Maybe the grammar is funky. Can you post your grammar?
4. Do DTMF tones work during AND after the prompt?
5. Did you take a look at the Nuance log.txt file or nss.log to look for any errors?
6. Perhaps there's a Nuance configuration setting that's amiss (post the nss.cfg (?) file)
7. Perhaps the gateway isn't configured properly (post the vxml gateway config, omit IP addresses)
8. You could try turning on MRCP logging on the gateway - perhaps you'll see something.
Subject: RE: Nuance ASR not working with CVP
Replied by: David Macias on 11-01-2014 07:37:33 PM
Janine,
Something we've discovered is that the ASR seems to be
working as long as you speak while the TTS is playing, if you wait for
the audio to finish you will not get any recognition. I've attached a
picture of the studio app as well as the project properties.
Thank you.
Subject: RE: Nuance ASR not working with CVP
Replied by: David Macias on 12-01-2014 03:55:14 PM
1.What do you have set for the NoInput timeout in the Settings tab of
the Form element? Perhaps you have something like '5' (which would mean 5
milliseconds) instead of '5s' (to indicate seconds).
Attached, it's set to 5s.
2. Try using a Digits element (which uses a 'builtin' grammar) to
collect some digits using speech reco - do you get the same behavior
where Nuance only hears speech during the prompt, but not after the
prompt?
Same result attached a picture of the new app.
3. Maybe the grammar is funky. Can you post your grammar?
We're trying to use an inline grammar, so no grammar file.
4. Do DTMF tones work during AND after the prompt?
Exact same bahavior while TTS is playing we can press DTMF, but not once TTS is playing.
5. Did you take a look at the Nuance log.txt file or nss.log to look for any errors?
log.txt nothing strange, but nss.log:
20140110093909500| 2624| 0| FCMNHAKKAAAADNAJAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in SWIgrAPI.c:1585
20140110093909500| 2624| 0| FCMNHAKKAAAADNAJAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in SWIgrAPI.c:1190
20140110094900765| 3108| 0| FCNABABPAAABKLDPAAAAAAAB| MyApp| ** WARNING **| 7464| UNKERR| unknown error| swi:SBinet |
20140110094922843| 248| 0| FCNABEBBAAAALHBLAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110094922843| 248| 0| FCNABEBBAAAALHBLAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110094922843| 248| 0| FCNABEBBAAAALHBLAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110094922843| 248| 0| FCNABEBBAAAALHBLAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110095119875| 1536| 0| FCNABGOAAAALDEKHAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110095119875| 1536| 0| FCNABGOAAAALDEKHAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110095119875| 1536| 0| FCNABGOAAAALDEKHAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110095119875| 1536| 0| FCNABGOAAAALDEKHAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110100615468| 1536| 0| FCNABGOAAAALDEKHAAAAAAAB| MyApp| ** WARNING **| 7464| UNKERR| unknown error| swi:SBinet |
20140110100637515| 3108| 0| FCNABABPAAABKLDPAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110100637515| 3108| 0| FCNABABPAAABKLDPAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110100637515| 3108| 0| FCNABABPAAABKLDPAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110100637515| 3108| 0| FCNABABPAAABKLDPAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
6. Perhaps there's a Nuance configuration setting that's amiss (post the nss.cfg (?) file)
Attached.
7. Perhaps the gateway isn't configured properly (post the vxml gateway config, omit IP addresses)
Attached.
8. You could try turning on MRCP logging on the gateway - perhaps you'll see something.
Without knowing more, this stuff looks correct:
*Jan 13 00:28:57.919: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B4DDE4, Count=1968, Event=0x490C78FC
*Jan 13 00:28:57.931: //1421//MRCP:/mrcp_process_events:
event: RECOGNIZER_STOP RECOGNIZER
*Jan 13 00:28:57.931: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1968, Event=0x490C78FC
*Jan 13 00:28:57.935: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B4CD4C, Count=1969, Event=0x490C7884
*Jan 13 00:28:57.935: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B4CD4C, Count=1970, Event=0x490C77BC
*Jan 13 00:28:57.939: //1421//MRCP:/mrcp_process_events:
event: SYNTH_LIB_DESTROY SYNTHESIZER
*Jan 13 00:28:57.939: //1421//MRCP:/mrcp_free_fsm:
*Jan 13 00:28:57.939: //1421//MRCP:/mrcp_disconnect_connect_fsm:
(0x4DB3BE88)
*Jan 13 00:28:57.939: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B5457C, Count=1971, Event=0x490C76CC
*Jan 13 00:28:57.939: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1969, Event=0x490C7884
*Jan 13 00:28:57.939: //1421//MRCP:/mrcp_process_events:
event: RECOG_LIB_DESTROY RECOGNIZER
*Jan 13 00:28:57.939: //1421//MRCP:/mrcp_free_fsm:
*Jan 13 00:28:57.939: //1421//MRCP:/mrcp_disconnect_connect_fsm:
(0x4DB007FC)
*Jan 13 00:28:57.939: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B5457C, Count=1972, Event=0x490C79EC
*Jan 13 00:28:57.939: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1970, Event=0x490C77BC
*Jan 13 00:28:57.939: //1421//MRCP:/mrcp_process_events:
event: LIB_DISCONNECT RESOURCE_NONE
*Jan 13 00:28:57.939: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1971, Event=0x490C76CC
*Jan 13 00:28:57.939: //1421//MRCP:/mrcp_process_events:
event: LIB_DISCONNECT RESOURCE_NONE
*Jan 13 00:28:57.939: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1972, Event=0x490C79EC
*Jan 13 00:28:58.043: //-1//MRCP:/mrcp_response_handler:
status=RTSPLIB_STATUS_CLEANUP
*Jan 13 00:28:58.043: //1421//MRCP:/mrcp_cleanup_connect_fsm:
connect_fsm(0x4DB3BE88)
*Jan 13 00:28:58.071: //-1//MRCP:/mrcp_response_handler:
status=RTSPLIB_STATUS_CLEANUP
*Jan 13 00:28:58.071: //1421//MRCP:/mrcp_cleanup_connect_fsm:
connect_fsm(0x4DB007FC)
*Jan 13 00:28:58.071: //1421//MRCP:/mrcp_free_scb:
scb=0x4D6A4918
*Jan 13 00:28:58.071: //1421//MRCP:/mrcp_create_session_history:
scb=0x4D6A4918 stream=0x490C62C4
*Jan 13 00:28:58.071: //1421//MRCP:/mrcp_insert_session_history_record:
current=0x49724ABC, count = 1
*Jan 13 00:28:58.071: //1421//MRCP:/mrcp_insert_session_history_record:
starting history record deletion_timer of 10 minutes
*Jan 13 00:29:02.843: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B4CD4C, Count=1973, Event=0x490C7B54
*Jan 13 00:29:02.843: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B4CD4C, Count=1974, Event=0x490C7BA4
*Jan 13 00:29:02.843: //1419//MRCP:/mrcp_process_events:
event: SYNTH_LIB_DESTROY SYNTHESIZER
*Jan 13 00:29:02.843: //1419//MRCP:/mrcp_free_fsm:
*Jan 13 00:29:02.843: //1419//MRCP:/mrcp_disconnect_connect_fsm:
(0x495132C0)
*Jan 13 00:29:02.843: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B5457C, Count=1975, Event=0x490C76A4
*Jan 13 00:29:02.843: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1973, Event=0x490C7B54
*Jan 13 00:29:02.843: //1419//MRCP:/mrcp_process_events:
event: RECOG_LIB_DESTROY RECOGNIZER
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_free_fsm:
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_disconnect_connect_fsm:
(0x494BAC68)
*Jan 13 00:29:02.847: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B5457C, Count=1976, Event=0x490C7924
*Jan 13 00:29:02.847: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1974, Event=0x490C7BA4
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_process_events:
event: LIB_DISCONNECT RESOURCE_NONE
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_cleanup_connect_fsm:
connect_fsm(0x495132C0)
*Jan 13 00:29:02.847: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1975, Event=0x490C76A4
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_process_events:
event: LIB_DISCONNECT RESOURCE_NONE
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_cleanup_connect_fsm:
connect_fsm(0x494BAC68)
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_free_scb:
scb=0x494B4B68
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_create_session_history:
scb=0x494B4B68 stream=0x0
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_create_session_history:
No streams in session control block
*Jan 13 00:29:02.847: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1976, Event=0x490C7924
Subject: RE: Nuance ASR not working with CVP
Replied by: Manoj Varghese on 14-01-2014 10:41:59 AM
Subject: RE: Nuance ASR not working with CVP
Replied by: Janine Graves on 16-01-2014 09:44:49 AM
Hi David,
Go to this link and it'll explain how to turn on vxml gateway logging. It'll show you what to look for. The question is whether the vxml gateway is detecting the voice/dtmf energy on the line; and/or is it passing it to nuance. I'm hoping this document will help you figure that out. You might need to put a sniffer on the line to detect what's going between the gateway and nuance. The document works for mrcp v2 (even though it's labeled mrcp v1).
http://www.cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example09186a008087d2ac.shtml
Subject: RE: Nuance ASR not working with CVP
Replied by: Manoj Varghese on 17-01-2014 04:40:35 PM
It looks like Nuance recognizer is taking almost 13 seconds to responds to any speech input. So I increased the digit element Noinput timeout to 15 seconds and after that ASR is giving right response to all the calls. Is there any setting to improve nuance response time?
Subject: RE: Nuance ASR not working with CVP
Replied by: Janine Graves on 17-01-2014 06:37:57 PM
You can try setting the VoiceXML property name: incompletetimeout value: 1s
at the bottom of the settings tab of the Digits element.
Created by: Manoj Varghese on 10-01-2014 11:20:43 AM
I am trying to make CVP 9 works with Nuance for ASR/TTS. TTS is working fine. But when I tried to use ASR using inline or external grammar, ASR doesn't recognise the voice/dtmf input. I have attached the vxml gateway logs for call with application is using inline grammar for ASR and no voice input is detected by the application. Is there anywhere on Nuance server I can lookout to see why its not working?
Subject: RE: Nuance ASR not working with CVP
Replied by: Janine Graves on 10-01-2014 07:57:10 PM
In the Studio app, did you specify under Project/Properties/CallStudio/General that it should use the Gateway CVP with Nuance?Manoj Varghese:I am trying to make CVP 9 works with Nuance for ASR/TTS. TTS is working fine. But when I tried to use ASR using inline or external grammar, ASR doesn't recognise the voice/dtmf input. I have attached the vxml gateway logs for call with application is using inline grammar for ASR and no voice input is detected by the application. Is there anywhere on Nuance server I can lookout to see why its not working?
The default is that the gateway will collect the DTMF tones. To use speech reco, you have to configure it in the Studio app under Project/Properties/CallStudio/General
Subject: RE: Nuance ASR not working with CVP
Replied by: Janine Graves on 12-01-2014 09:25:41 AM
**********************************************************************************************David Macias:Janine,
Something we've discovered is that the ASR seems to be
working as long as you speak while the TTS is playing, if you wait for
the audio to finish you will not get any recognition. I've attached a
picture of the studio app as well as the project properties.
Thank you.
David,
That behavior seems bizarre.
1.What do you have set for the NoInput timeout in the Settings tab of
the Form element? Perhaps you have something like '5' (which would mean 5
milliseconds) instead of '5s' (to indicate seconds).
Post a picture of the Settings tab.
2. Try using a Digits element (which uses a 'builtin' grammar) to
collect some digits using speech reco - do you get the same behavior
where Nuance only hears speech during the prompt, but not after the
prompt?
3. Maybe the grammar is funky. Can you post your grammar?
4. Do DTMF tones work during AND after the prompt?
5. Did you take a look at the Nuance log.txt file or nss.log to look for any errors?
6. Perhaps there's a Nuance configuration setting that's amiss (post the nss.cfg (?) file)
7. Perhaps the gateway isn't configured properly (post the vxml gateway config, omit IP addresses)
8. You could try turning on MRCP logging on the gateway - perhaps you'll see something.
Subject: RE: Nuance ASR not working with CVP
Replied by: David Macias on 11-01-2014 07:37:33 PM
Janine,
Something we've discovered is that the ASR seems to be
working as long as you speak while the TTS is playing, if you wait for
the audio to finish you will not get any recognition. I've attached a
picture of the studio app as well as the project properties.
Thank you.
Subject: RE: Nuance ASR not working with CVP
Replied by: David Macias on 12-01-2014 03:55:14 PM
1.What do you have set for the NoInput timeout in the Settings tab of
the Form element? Perhaps you have something like '5' (which would mean 5
milliseconds) instead of '5s' (to indicate seconds).
Attached, it's set to 5s.
2. Try using a Digits element (which uses a 'builtin' grammar) to
collect some digits using speech reco - do you get the same behavior
where Nuance only hears speech during the prompt, but not after the
prompt?
Same result attached a picture of the new app.
3. Maybe the grammar is funky. Can you post your grammar?
We're trying to use an inline grammar, so no grammar file.
4. Do DTMF tones work during AND after the prompt?
Exact same bahavior while TTS is playing we can press DTMF, but not once TTS is playing.
5. Did you take a look at the Nuance log.txt file or nss.log to look for any errors?
log.txt nothing strange, but nss.log:
20140110093909500| 2624| 0| FCMNHAKKAAAADNAJAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in SWIgrAPI.c:1585
20140110093909500| 2624| 0| FCMNHAKKAAAADNAJAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in SWIgrAPI.c:1190
20140110094900765| 3108| 0| FCNABABPAAABKLDPAAAAAAAB| MyApp| ** WARNING **| 7464| UNKERR| unknown error| swi:SBinet |
20140110094922843| 248| 0| FCNABEBBAAAALHBLAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110094922843| 248| 0| FCNABEBBAAAALHBLAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110094922843| 248| 0| FCNABEBBAAAALHBLAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110094922843| 248| 0| FCNABEBBAAAALHBLAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110095119875| 1536| 0| FCNABGOAAAALDEKHAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110095119875| 1536| 0| FCNABGOAAAALDEKHAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110095119875| 1536| 0| FCNABGOAAAALDEKHAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110095119875| 1536| 0| FCNABGOAAAALDEKHAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110100615468| 1536| 0| FCNABGOAAAALDEKHAAAAAAAB| MyApp| ** WARNING **| 7464| UNKERR| unknown error| swi:SBinet |
20140110100637515| 3108| 0| FCNABABPAAABKLDPAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110100637515| 3108| 0| FCNABABPAAABKLDPAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110100637515| 3108| 0| FCNABABPAAABKLDPAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
20140110100637515| 3108| 0| FCNABABPAAABKLDPAAAAAAAB| MyApp| RecognizerErrorUnwind|| SWI error URI_NOT_FOUND(17) detected in cache\cache.c:968
6. Perhaps there's a Nuance configuration setting that's amiss (post the nss.cfg (?) file)
Attached.
7. Perhaps the gateway isn't configured properly (post the vxml gateway config, omit IP addresses)
Attached.
8. You could try turning on MRCP logging on the gateway - perhaps you'll see something.
Without knowing more, this stuff looks correct:
*Jan 13 00:28:57.919: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B4DDE4, Count=1968, Event=0x490C78FC
*Jan 13 00:28:57.931: //1421//MRCP:/mrcp_process_events:
event: RECOGNIZER_STOP RECOGNIZER
*Jan 13 00:28:57.931: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1968, Event=0x490C78FC
*Jan 13 00:28:57.935: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B4CD4C, Count=1969, Event=0x490C7884
*Jan 13 00:28:57.935: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B4CD4C, Count=1970, Event=0x490C77BC
*Jan 13 00:28:57.939: //1421//MRCP:/mrcp_process_events:
event: SYNTH_LIB_DESTROY SYNTHESIZER
*Jan 13 00:28:57.939: //1421//MRCP:/mrcp_free_fsm:
*Jan 13 00:28:57.939: //1421//MRCP:/mrcp_disconnect_connect_fsm:
(0x4DB3BE88)
*Jan 13 00:28:57.939: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B5457C, Count=1971, Event=0x490C76CC
*Jan 13 00:28:57.939: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1969, Event=0x490C7884
*Jan 13 00:28:57.939: //1421//MRCP:/mrcp_process_events:
event: RECOG_LIB_DESTROY RECOGNIZER
*Jan 13 00:28:57.939: //1421//MRCP:/mrcp_free_fsm:
*Jan 13 00:28:57.939: //1421//MRCP:/mrcp_disconnect_connect_fsm:
(0x4DB007FC)
*Jan 13 00:28:57.939: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B5457C, Count=1972, Event=0x490C79EC
*Jan 13 00:28:57.939: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1970, Event=0x490C77BC
*Jan 13 00:28:57.939: //1421//MRCP:/mrcp_process_events:
event: LIB_DISCONNECT RESOURCE_NONE
*Jan 13 00:28:57.939: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1971, Event=0x490C76CC
*Jan 13 00:28:57.939: //1421//MRCP:/mrcp_process_events:
event: LIB_DISCONNECT RESOURCE_NONE
*Jan 13 00:28:57.939: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1972, Event=0x490C79EC
*Jan 13 00:28:58.043: //-1//MRCP:/mrcp_response_handler:
status=RTSPLIB_STATUS_CLEANUP
*Jan 13 00:28:58.043: //1421//MRCP:/mrcp_cleanup_connect_fsm:
connect_fsm(0x4DB3BE88)
*Jan 13 00:28:58.071: //-1//MRCP:/mrcp_response_handler:
status=RTSPLIB_STATUS_CLEANUP
*Jan 13 00:28:58.071: //1421//MRCP:/mrcp_cleanup_connect_fsm:
connect_fsm(0x4DB007FC)
*Jan 13 00:28:58.071: //1421//MRCP:/mrcp_free_scb:
scb=0x4D6A4918
*Jan 13 00:28:58.071: //1421//MRCP:/mrcp_create_session_history:
scb=0x4D6A4918 stream=0x490C62C4
*Jan 13 00:28:58.071: //1421//MRCP:/mrcp_insert_session_history_record:
current=0x49724ABC, count = 1
*Jan 13 00:28:58.071: //1421//MRCP:/mrcp_insert_session_history_record:
starting history record deletion_timer of 10 minutes
*Jan 13 00:29:02.843: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B4CD4C, Count=1973, Event=0x490C7B54
*Jan 13 00:29:02.843: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B4CD4C, Count=1974, Event=0x490C7BA4
*Jan 13 00:29:02.843: //1419//MRCP:/mrcp_process_events:
event: SYNTH_LIB_DESTROY SYNTHESIZER
*Jan 13 00:29:02.843: //1419//MRCP:/mrcp_free_fsm:
*Jan 13 00:29:02.843: //1419//MRCP:/mrcp_disconnect_connect_fsm:
(0x495132C0)
*Jan 13 00:29:02.843: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B5457C, Count=1975, Event=0x490C76A4
*Jan 13 00:29:02.843: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1973, Event=0x490C7B54
*Jan 13 00:29:02.843: //1419//MRCP:/mrcp_process_events:
event: RECOG_LIB_DESTROY RECOGNIZER
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_free_fsm:
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_disconnect_connect_fsm:
(0x494BAC68)
*Jan 13 00:29:02.847: //-1//MRCP:/mrcp_get_ev:
****>Caller PC=0x43B5457C, Count=1976, Event=0x490C7924
*Jan 13 00:29:02.847: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1974, Event=0x490C7BA4
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_process_events:
event: LIB_DISCONNECT RESOURCE_NONE
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_cleanup_connect_fsm:
connect_fsm(0x495132C0)
*Jan 13 00:29:02.847: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1975, Event=0x490C76A4
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_process_events:
event: LIB_DISCONNECT RESOURCE_NONE
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_cleanup_connect_fsm:
connect_fsm(0x494BAC68)
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_free_scb:
scb=0x494B4B68
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_create_session_history:
scb=0x494B4B68 stream=0x0
*Jan 13 00:29:02.847: //1419//MRCP:/mrcp_create_session_history:
No streams in session control block
*Jan 13 00:29:02.847: //-1//MRCP:/mrcp_free_ev:
---------------->Caller PC=0x43B4FB28, Count=1976, Event=0x490C7924
Subject: RE: Nuance ASR not working with CVP
Replied by: Manoj Varghese on 14-01-2014 10:41:59 AM
We just noticed that if an audio element with barge In is there before the form/digit element then asr works only if we speak at the begining of the audio element. Otherwise giving a cvp error message?:
Subject: RE: Nuance ASR not working with CVP
Replied by: Janine Graves on 16-01-2014 09:44:49 AM
Hi David,
Go to this link and it'll explain how to turn on vxml gateway logging. It'll show you what to look for. The question is whether the vxml gateway is detecting the voice/dtmf energy on the line; and/or is it passing it to nuance. I'm hoping this document will help you figure that out. You might need to put a sniffer on the line to detect what's going between the gateway and nuance. The document works for mrcp v2 (even though it's labeled mrcp v1).
http://www.cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example09186a008087d2ac.shtml
Subject: RE: Nuance ASR not working with CVP
Replied by: Manoj Varghese on 17-01-2014 04:40:35 PM
It looks like Nuance recognizer is taking almost 13 seconds to responds to any speech input. So I increased the digit element Noinput timeout to 15 seconds and after that ASR is giving right response to all the calls. Is there any setting to improve nuance response time?
Subject: RE: Nuance ASR not working with CVP
Replied by: Janine Graves on 17-01-2014 06:37:57 PM
You can try setting the VoiceXML property name: incompletetimeout value: 1s
at the bottom of the settings tab of the Digits element.
Labels:
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
Customers Also Viewed These Support Documents