3 - Way Conference

[Guest R Venkatesh]

Hi,

We are evaluating voiceguide for our business. We want to implement the following scenario. Can you tell us if this is possible with voiceguide

 

1. A caller calls

 

2 voice guide accepts a number N

 

3. transfer the call to N. If the number is busy or there is no response then dial an alternate number. If there is a response then conference the two.

 

We do not want blind 3-way conference because we want to handle the case when the second number is busy.

 

Is it possible to make something similar to announced conference but without requiring the second person to explicitly accept the call. As soon as the second person answers the conference should be set up and in case the second person does not answer then an alternate path needs to be taken.

 

The problem with the telestra example provided is that it does not work well when the second number is busy.

 

Thanks in advance for your help.

 

Venky

[SupportTeam]

Is it possible to make something similar to announced conference but without requiring the second person to explicitly accept the call.

Not with the TAPI version of VoiceGuide. It is not possible to detect the human voice answering the call on conference calls in this version. You should be using 'Announced Transfer' with this version.

 

This is possible on the version of VoiceGuide written to work specifically with Dialogic cards. Currently this is only available for ISDN installations, but will soon be also available for analog systems (which I assume you are using).

 

The problem with the telestra example provided is that it does not work well when the second number is busy.

That sample script shows the approach that should be used to implement your own 'announced transfer' - looking at that demo script now I can see that it is not designed to handle the case where you'd want to drop attempted conference if the conference is not accepted by recipient - but this can be quite easily added and you will then be able to control all aspects of announced conferences from within your own script.

[Guest Guest]

Thank you for the prompt response.

 

That sample script shows the approach that should be used to implement your own 'announced transfer' - looking at that demo script now I can see that it is not designed to handle the case where you'd want to drop attempted conference if the conference is not accepted by recipient - but this can be quite easily added and you will then be able to control all aspects of announced conferences from within your own script.

 

How can we handle the case when the recipients line is busy? In this case we want to take a different path.

 

In the telestra example in the "dial 3rd number" module how do i choose different paths based on whether the call has been answered or not.

 

We understand how to handle the case when the recipient does not accept the call.

 

Appreciate any help. Thanks.

 

Venky

[SupportTeam]

How can we handle the case when the recipients line is busy? In this case we want to take a different path.

You can use a timeout path in the module that asks for call acceptance. If call has not been accepted within that time then the timeout path will be taken and you can point the timeout path to a module which issues the required hookflashes/dtmfs to 'take back' the call and then continue as desired.

 

You cannot detect 'busy' on announced call conferences under the TAPI system - the only mechanism is to timeout awaiting for acceptance or have the call expressly refused be recipient.

 

The version of VoiceGuide written for Dialogic directly can detect busy/disconnect etc and can act when these situations are detected.

[Guest Cleo]

Did I understand correctly? Can VG not diffrentiate between human voice and answer machine on a basic outgoing conferenced call?

[SupportTeam]

Not on 2nd leg of a 3-way conference call - that is why recipient of call has to 'press 1 to accept call'.