Author Message
DiegoChacón2
Joined: Nov 10, 2016
Messages: 8
Offline
Hi.
In our environment the DTMF tones are being replaced (or encrypted, or encoded) from their original values.

For example, when we select option 1 (DTMF), the browser is detecting "OPT#0xf240f618", and every retry this value changes (OPT#0xf2dd3ba8, OPT#0xf75c5a50, etc.).


Bellow there is a trace from the application, where it was supposed to detect 1:




2021-09-15 14:34:45.564 GMT+0000 INFO - B9F97CF4380E1C0F14CDE6A08E807F0F:/CBASIPCustomer : Using SCESession B9F97CF4380E1C0F14CDE6A08E807F0F:/CBASIPCustomer servlet : representative
2021-09-15 14:34:45.565 GMT+0000 INFO - B9F97CF4380E1C0F14CDE6A08E807F0F:/CBASIPCustomer : Storing :offerCallback___confidence to complex: offerCallback:confidence as [1]
2021-09-15 14:34:45.565 GMT+0000 INFO - B9F97CF4380E1C0F14CDE6A08E807F0F:/CBASIPCustomer : Storing :offerCallback___inputmode to complex: offerCallback:inputmode as [dtmf]
2021-09-15 14:34:45.565 GMT+0000 INFO - B9F97CF4380E1C0F14CDE6A08E807F0F:/CBASIPCustomer : Storing :offerCallback___interpretation to complex: offerCallback:interpretation as ["OPT#0xf240f618"]
2021-09-15 14:34:45.565 GMT+0000 INFO - B9F97CF4380E1C0F14CDE6A08E807F0F:/CBASIPCustomer : Storing :offerCallback___noinputcount to complex: offerCallback:noinputcount as [0]
2021-09-15 14:34:45.565 GMT+0000 INFO - B9F97CF4380E1C0F14CDE6A08E807F0F:/CBASIPCustomer : Storing :offerCallback___nomatchcount to complex: offerCallback:nomatchcount as [0]
2021-09-15 14:34:45.565 GMT+0000 INFO - B9F97CF4380E1C0F14CDE6A08E807F0F:/CBASIPCustomer : Storing :offerCallback___utterance to complex: offerCallback:utterance as [1]
2021-09-15 14:34:45.565 GMT+0000 INFO - B9F97CF4380E1C0F14CDE6A08E807F0F:/CBASIPCustomer : Storing :offerCallback___value to complex: offerCallback:value as ["OPT#0xf240f618"]
2021-09-15 14:34:45.798 GMT+0000 INFO - B9F97CF4380E1C0F14CDE6A08E807F0F:/CBASIPCustomer : Audio url: http://x.x.x.x:8080/CBAPhrases/custom/customer/englishUS/en-us/default/c0022.wav
2021-09-15 14:34:45.798 GMT+0000 DEBUG - B9F97CF4380E1C0F14CDE6A08E807F0F:/CBASIPCustomer : *** Reply for [/CBACustomer/representative] ***
2021-09-15 14:34:45.798 GMT+0000 DEBUG - B9F97CF4380E1C0F14CDE6A08E807F0F:/CBASIPCustomer : 0:<?xml version="1.0" encoding="UTF-8"?>



What do you think could be the problem? Any help would be greatly appreciated.
WilsonYu
Joined: Nov 6, 2013
Messages: 3950
Offline
This looks really odd to me. There is not much you can do on the app side. You would have to get support on the platform side.
raywhite
Joined: Oct 10, 2019
Messages: 13
Offline
Was there any resolution to this- we are experiencing the same issue after and upgrade from AEP 7.1.0 to AEP 7.2.3

Thank you!

Ray
raywhite
Joined: Oct 10, 2019
Messages: 13
Offline
We had our customer open a ticket with Avaya- this was the answer

"you will need to upgrade to a later version of 7.2.3 on the MPP. The patch version 0558 contained a bug that caused the DTMF to show as OPT#0xf132dc40. It is fixed in 7.2.3.0.0562 or later, with 7.2.3.0.0580 being the latest available and what I would recommend you install. "

Go to:   
Mobile view