Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N
Dima_V wrote:Hello.
We have Vicidial VERSION: 2.14-695a BUILD: 181116-1133 in our infrastructure.
Our manager is complaining about strange behavior in autodial voice messaging.
They say that, for example, if a voice message is interrupted in the middle, the next call continues playing the message from the point where it was interrupted.
Is this possible or not?
carpenox wrote:you are using software from 2018 that probably has bugs, try upgrading to latest svn
williamconley wrote:Dima_V wrote:Hello.
We have Vicidial VERSION: 2.14-695a BUILD: 181116-1133 in our infrastructure.
Our manager is complaining about strange behavior in autodial voice messaging.
They say that, for example, if a voice message is interrupted in the middle, the next call continues playing the message from the point where it was interrupted.
Is this possible or not?
Anything is possible, of course (linux accomplishes multiple impossible bugs daily, often leading to developers to believe they are going insane, and many of us are correct).
That being said: I'm skeptical of this description for multiple reasons.
1) You asked if it's possible, not just for the cause of something you had personally observed.
2) You didn't mention how "the boss" had observed this phenomenon or how often it had been observed. Making it possible (IMHO) that this was a conclusion drawn from inadequate information rather than an actual observation.
For clarity: It's very common for the system to be configured to Leave VM without being configured to Wait For Silence before leaving the VM. This can often cause the VM system to begin recording after the message has been playing for anywhere from a few seconds to a couple minutes, depending on the length of the pre-recording message. Thus if The Boss was told by multiple clients/leads/prospects that the message in question had started from some random point in the recording, he may have simply jumped to the conclusion here rather than jumping to a completely different conclusion that would also explain the situation (ie: Wait for Silence not configured!)
Users browsing this forum: Google [Bot] and 68 guests