System Not Detecting Caller Hangup

[vatsal]

We are currently testing a script on 4 line Pro version, using D/4PCI.

 

I have been trying to get the script to handle "unexpected" responses

 

I have been having a problem with the system detecting the caller has hung-up. The script carries on running until the it picks up "no responses" later on in the script, then finally it resets.

 

Is there some way of the scripting the detection of the caller hanging up at any point and recording that fact somewhere?

 

Regards

 

Vatsal

[SupportTeam]

The Dialogic card can detect end of call in two different ways:

 

1. Detection of the busy tone being played on the line

 

2. Drop in loop current at end of call / Calling Party Control

 

1. When Dialogic card hears the Busy signal it will indicate to VoiceGuide that the call is now disconnected. To ensure that your D4PCI is properly set up to detect the busy signal standard in your country please read the release notes which have come with your card. They usually indicate which Parameter File you should specify in your Dialogic Configuration Manager, and what other settings you should use.

You can also use Dialogic's PBXpert application to specify what type of tone sequence constitutes a busy signal on your telephone system.

 

 

2. The second approach (Drop in loop current) is a much better approach. But you must set up your PBX or ask your phone company to ensure that this is happening. This method is also called Calling Party Control (CPC).

(Its easy to test if your card detects it - when you unplug the line from the card the card should register a hangup and send a 'disconnected' event to VoiceGuide).

 

 

BTW: a voice modem cannot detect CPC - it has to rely on detecting the busy signal. Some modems are OK at this, and some hardly ever detect the busy signal, especially when a sound file is played. The type of busy signal they are designed to detect is usually not settable by the user.