Guest dc103fm Report post Posted 04/16/2003 10:45 AM The following problems occur with Voiceguide and the Dialogic D4/PCI voiceboard I have a series of wavefiles playing as one wavefile passed from module to module by a timeout=0 command. when however someone hangs up the phone during a module, Voiceguide does not disconnect and keeps playing the waves until the end. Share this post Link to post
SupportTeam Report post Posted 04/17/2003 01:58 AM VoiceGuide will disconnect a call when the Dialogic card informs it that it can hear a busy tone on the line. Does your telephone system play a busy tone to VoiceGuide when the caller hangs up? You may need to configure your card to correctly detect the busy tones. Please read the release notes which came with our card - they will inform you which parameter file you should be using for your country (you specify the parameter file in the Dialogic Configuration Manager). You can also train your card to detect the busy tones correctly - see the Dialogic PBXpert application. Share this post Link to post
Guest dc103fm Report post Posted 04/23/2003 05:07 PM I have configured the card (I am in the Netherlands) and trained with the PBXpert that came with the card, however voice still refuses to disconnect the call while the user has already hung up, resulting in an endless loop. Anyone any sugestions or otherways to free the line when the user hangs up in the middle of a seties of wavefiles played my continuing playmodules? Share this post Link to post
SupportTeam Report post Posted 04/23/2003 11:06 PM You should speak with the local Dialogic dealer to ask them how to configure your card to correctly detect busy tones in your area. Does your phone company play a busy tone when caller hangs up? Related posts: http://katalinatech.com/forums/index.php?a...act=ST&f=2&t=76 http://katalinatech.com/forums/index.php?a...ct=ST&f=2&t=139 http://katalinatech.com/forums/index.php?a...ct=ST&f=2&t=181 I would also look at structuring the script in such a way that is does not have any endless loops in it. Share this post Link to post