We're using Record element to collect some prompts from customers in CVP 8.5 and encountered a problem with the max record time parameter. We set it to 7s (seven seconds) and most of the time, the recording stops at seven secs. Only for about 40 cases out of 10000, the recording didn't stop at 7s and IVR kept recording the prompt until the max record time parameter of the voice gateway was reached. When we look at the problematic cases, they have nothing in common. They don't come from the same voice gateway, and they have no other common properties.
Has anyone ever encountered a similar problem? Could it be a bug or is there another cause?
Here are the settings of the record element. Note that VAD is OFF, so we don't use no input timeout and final silence parameters.
I think for your record element you need to enable VAD in gateway dial-peers. Below is url and screenshot for your reference.
Please go though with the above link to validate your setting and enable VAD on GW.
Hope it helps.
Enabling VAD is not required for this.
VAD allows the record element to end after a period of silence and not a period of time (i.e. 7 second timer).
In this scenario, the terminal should occur after 7 seconds and so enabling or disabling VAD will make no difference.
the issue here would appear to be a bug likely in IOS.
Also enablign VAD for CVP Compreshensive woudl enable it for all calls (CVP standalone - you can do just for your app)
I would raise a TAC case to find out route cause or try enabling Syslog and debug and reviewing if you can spot a difference between a good / typical call and what happens when the timer does and does NOT kick in.
Best option might be to review the IOS version and see if you can upgrade to a supported later version.
Check CVP BOM for supported IOS versions for the CVP you are using.
Yes, I agree that this could be some issue with IOS or it's compatibility.