- Joined
- Jan 18, 2011
- Messages
- 160
- Reaction score
- 45
Hi all, I wonder if anyone has comments/thoughts on this. I've got a 3cx instance (hosted on a VM on OVH public cloud) - is current release 3cx - 18.0 (Build 314)
I've got inbound calls coming in
- first to a top level IVR menu of "STANDARD" type. Where callers can
press 1 for reception
press 2 for sales
press 3 for support
press 4 to dial by lastname/company directory
if callers press 1,2,3,4 this works fine.
Then if callers go into (4 - dial by lastname) - I have another IVR setup, "TYPE" is designated as "DTMF INPUT". Then I've got a variety of 4-digit things listed that callers may dial to spell first 4 letters of names of people at company.
what appears to happen currently, is that most of the time, 3cx just says sometihng like "Invalid response, try again"
as if the DTMF codes are not coming through clean
but it is just weird because my top-level "standard" menu is working perfectly
I've used this kind of dial-by-name setup with "DTMF" IVR on other small 3cx instances I've setup last year, and none of them have this problem
I'm curious if anyone has ideas about some 'poison pill' that causes the DTMF recognition to just totally crap out.
many thanks,
Tim
I've got inbound calls coming in
- first to a top level IVR menu of "STANDARD" type. Where callers can
press 1 for reception
press 2 for sales
press 3 for support
press 4 to dial by lastname/company directory
if callers press 1,2,3,4 this works fine.
Then if callers go into (4 - dial by lastname) - I have another IVR setup, "TYPE" is designated as "DTMF INPUT". Then I've got a variety of 4-digit things listed that callers may dial to spell first 4 letters of names of people at company.
what appears to happen currently, is that most of the time, 3cx just says sometihng like "Invalid response, try again"
as if the DTMF codes are not coming through clean
but it is just weird because my top-level "standard" menu is working perfectly
I've used this kind of dial-by-name setup with "DTMF" IVR on other small 3cx instances I've setup last year, and none of them have this problem
I'm curious if anyone has ideas about some 'poison pill' that causes the DTMF recognition to just totally crap out.
many thanks,
Tim