Author |
Message |
|
|
IngersolPandarinathan
Joined: Nov 4, 2013
Messages: 9
Offline
|
Customer is saying that after upgrading from VP5 to EP7, link item (for DTMF digit) on Prompt & Collect is not working.
Application trace.log is attached.
|
|
|
|
|
WilsonYu
Joined: Nov 6, 2013
Messages: 3950
Offline
|
From the logs, I see that you have 2 links:
6:<link next="transfer?___DDSESSIONID=BA55D7A0B258CD837FF7FD5D06008997%3A%2Ftestdtmf" dtmf="0">
7:</link>
8:<link next="card?___DDSESSIONID=BA55D7A0B258CD837FF7FD5D06008997%3A%2Ftestdtmf" dtmf="2">
9:</link>
Then dtmf 1 seemed to have been entered that ends the session:
08/07/2015 18:42:25:321 INFO - BA55D7A0B258CD837FF7FD5D06008997:/testdtmf : Using SCESession BA55D7A0B258CD837FF7FD5D06008997:/testdtmf servlet : End
08/07/2015 18:42:25:322 INFO - BA55D7A0B258CD837FF7FD5D06008997:/testdtmf : Storing :GreetingGeneralMenu___confidence to complex: GreetingGeneralMenu:confidence as [1]
08/07/2015 18:42:25:322 INFO - BA55D7A0B258CD837FF7FD5D06008997:/testdtmf : Storing :GreetingGeneralMenu___inputmode to complex: GreetingGeneralMenu:inputmode as [dtmf]
Not sure what is not working.
|
|
|
|
|
IngersolPandarinathan
Joined: Nov 4, 2013
Messages: 9
Offline
|
No Wilson, DTMF 0 was entered, please see the complete log below.
08/07/2015 18:42:25:322 INFO - BA55D7A0B258CD837FF7FD5D06008997:/testdtmf : Storing :GreetingGeneralMenu___confidence to complex: GreetingGeneralMenu:confidence as [1]
08/07/2015 18:42:25:322 INFO - BA55D7A0B258CD837FF7FD5D06008997:/testdtmf : Storing :GreetingGeneralMenu___inputmode to complex: GreetingGeneralMenu:inputmode as [dtmf]
08/07/2015 18:42:25:322 INFO - BA55D7A0B258CD837FF7FD5D06008997:/testdtmf : Storing :GreetingGeneralMenu___value to complex: GreetingGeneralMenu:value as [0]
08/07/2015 18:42:25:322 INFO - BA55D7A0B258CD837FF7FD5D06008997:/testdtmf : Storing :GreetingGeneralMenu___interpretation to complex: GreetingGeneralMenu:interpretation as [0]
08/07/2015 18:42:25:322 INFO - BA55D7A0B258CD837FF7FD5D06008997:/testdtmf : Storing :GreetingGeneralMenu___utterance to complex: GreetingGeneralMenu:utterance as [0]
08/07/2015 18:42:25:322 INFO - BA55D7A0B258CD837FF7FD5D06008997:/testdtmf : Storing :GreetingGeneralMenu___noinputcount to complex: GreetingGeneralMenu:noinputcount as [0]
08/07/2015 18:42:25:322 INFO - BA55D7A0B258CD837FF7FD5D06008997:/testdtmf : Storing :GreetingGeneralMenu___nomatchcount to complex: GreetingGeneralMenu:nomatchcount as [0]
There are 2 link items (for 0 and 2) on the Prompt and Collect.
|
|
|
|
|
WilsonYu
Joined: Nov 6, 2013
Messages: 3950
Offline
|
Sorry, mis-read the latter portion of the log. Yes, it seems 0 was entered. The vxml generated looks perfectly fine. That's how is generated all along. I am not sure why it's not work on the platform. Does it work in simulation? One thing I notice is the platform is still set to desktop:
08/07/2015 18:42:18:797 INFO - BA55D7A0B258CD837FF7FD5D06008997:/testdtmf : runtime_platform : Desktop
08/07/2015 18:42:18:797 INFO - 5DCDBA80429C0D819E1A90F3E96CA62D:/testdtmf : runtime_platform : Desktop
08/07/2015 18:42:18:797 INFO - BA55D7A0B258CD837FF7FD5D06008997:/testdtmf : runtime_asr : Desktop Microsoft Speech SAPI
08/07/2015 18:42:18:797 INFO - 5DCDBA80429C0D819E1A90F3E96CA62D:/testdtmf : runtime_asr : Desktop Microsoft Speech SAPI
When exporting for deployment, the platform and asr parameters need to change to match the platform versions.
|
|
|
|
|
IngersolPandarinathan
Joined: Nov 4, 2013
Messages: 9
Offline
|
Customer says that link item is not working on the simulator as well.
Also, he exported the app with correct Platform and ASR settings and observes the same issue on the Platform/App Server as well.
Attaching the trace logs here.
|
|
|
|
|
WilsonYu
Joined: Nov 6, 2013
Messages: 3950
Offline
|
Is it possible that you post the test app that reproduce the problem? Since it happens in simulation, I should be able to reproduce it easily with the exact app you have.
|
|
|
|
|
IngersolPandarinathan
Joined: Nov 4, 2013
Messages: 9
Offline
|
Attached is the test app from customer.
|
|
|
|
|
WilsonYu
Joined: Nov 6, 2013
Messages: 3950
Offline
|
I talked to our EP AVB expert and confirmed that the behavior the customer experienced on VP 5 was actually a defect that later got fixed in EP 6 and above. So the current behavior is the one intended and it jives with the vxml specs ( http://www.w3.org/TR/voicexml20/#dml3.1.4). Basically this section of the specs specifies that the grammar in the input item takes priority over the links in the form. That's why you saw that the build-in digits grammar handles the "0" input before it gets to the link. The old behavior also exists in the simulator that we have to fix.
So what this mean is that the customer has to change the app because of the change on the new platform to make the app work as desired.
|
|
|
|
|
IngersolPandarinathan
Joined: Nov 4, 2013
Messages: 9
Offline
|
Thanks for your time on finding the reason for this behavior.
So, how to handle this issue on the application?
Just avoid link item and evaluate the grammar result as usual and then take a different path for recognized digits.
|
|
|
|
|
WilsonYu
Joined: Nov 6, 2013
Messages: 3950
Offline
|
Yep, if you simply just get rid of the links and examine the result of the grammar in a data node to decide which path to take, that seems to match what you intent to accomplish.
|
|
|
|
|
IngersolPandarinathan
Joined: Nov 4, 2013
Messages: 9
Offline
|
Got it. Thanks again.
|
|
|