Hangup On Silence Detect Truncating Message

[fedup]

Currently, because the line is so poor quality, silence detection appears to be the only reliable method of detecting hangup. However, regardless of what length of detection I set, voiceguide is truncating too much of the message. Setting detect to as little as 10 (one second) will truncate over two seconds of the wave file (this btw, necessitates almost constant noise to keep connected). At a guess, the wave file is being recorded at a lower bitrate than the silence detection algorithm expects and subsequently the wave file is truncated excessively. I don't want the file truncated at all, I just want 5 seconds of silence detect from TAPI to pass through before hangup. I don't care if every message contains additional silence at the end. Is this possible to configure?

[SupportTeam]

Which version of Voiceguide are you using?

 

Could you please post a copy of VoiceGuide's Trace Logs which captures the call, this will allow us to see what happened.

[ktruk]

fedup: 1. There are a couple of parameters in the VG.INI file (maybe just for the tapi version?) that allow you to tweak the silence detection process for all recordings (ie: system wide) and also you can set 2 RV parameters prior to any 1 recording to control silence detection. I have tried both of these and can confirm that they work well to adjust the performance. See recording section in the help file.

 

2. ISDN lines don't suffer hangup detection problems. You can use multi-channel Dialogic (expensive) cards (or twin-channel (cheap) ISDN BRI cards)