In our voice messages, we use the following line to make sure that, when a answering machine or voice mail answers the call, the system waits until after the beep until the message is read:
<record cond="calleeType=='answeringmachine'" finalsilence="4000ms"><noinput></noinput></record> (see post http://support.plumgroup.com/viewtopic.php?t=865)
Sometimes the call is by mistake identified as an answering machine call when a human answers the call.
In the past, this caused the system to wait longer, but the message still started to be pronounced after some time. But now, the system keeps on waiting infinitely, so there's no message but only silence.
Has something been changed in the plumvoice service that causes this?
We've Moved! Please visit our new and improved forum over at our new portal: https://portal.plumvoice.com/hc/en-us/community/topics
Infinite wait for answering machine beep
Adjust IVR code by changing values within <record> tag
Hi,
Nothing has been changed with callee type detection in our IVR system. Please keep in mind that callee type detection is not 100% perfect. There's still a slight chance that callee type detection might mistake a human for an answering machine. You may have to adjust some values within your IVR tag, record, or adjust the value of your timeout to make sure that the message is played at the right time.
Regards,
Plum Support
Nothing has been changed with callee type detection in our IVR system. Please keep in mind that callee type detection is not 100% perfect. There's still a slight chance that callee type detection might mistake a human for an answering machine. You may have to adjust some values within your IVR tag, record, or adjust the value of your timeout to make sure that the message is played at the right time.
Regards,
Plum Support
Plum Support
http://www.plumvoice.com
http://www.plumvoice.com