Detection Of Humans/answering Machine Errors

[Guest Guest_Richard]

Since we have a high incidence of mis-detection for both humans and answer machines, we do not want to use the feature for detecting at all. We are using Voice Guide (5.2.3063 Enterprise version)

 

Misdetection has hurt our campaign in two ways:

 

1. if we call a human - but it's mis-detected as an answer machine - they can not press a prompt. - they can not express their interest in our product.

 

2. if we call an answer machine - but its mis-detected as a human - the call length report appears that a human listened to our entire message - falsely giving the impression that they were interested in our product. of course this is not true as we played our entire message to their machine.

 

How do we change our setting to make calls with no answer machine detection AND with no human detection.

 

In otherwords, we want to dial out allowing prompts to be pressed/responded for all numbers we call AND whenever they hang up, we hang up.

 

We believe the best way to achieve this is to deactivate detection. What do you recommend?

 

Note: We want to continue using the same version because our scripts are not compatible with the new version and have to undergo a lot of changes.

[SupportTeam]

You should use IGNORE or DISABLE keyword in the place where the action to take on Answering Machine answer is specified. But you will need to use "VG for DIalogic"...

 

from http://www.voiceguide.com/vghelp/html/DialListInto.htm :

If IGNORE is specified in this field then VoiceGuide will ignore Dialogic's advice that an answering machine was detected and will just start the script/file specified in the "when a real person answers" text box.

 

If DISABLE is specified in this field then VoiceGuide will disable Dialogic's detection of when the call has been answered

 

because our scripts are not compatible with the new version and have to undergo a lot of changes.

What? There would be no major changes required between v5.2.3063 and current version of "VG for TAPI"... There are even no changes required when you move from using "VG for TAPI" to "VG for Dialogic"...

 

What are the changes that you think you need to make to move from v5.2.306 to the current version?

[Guest sanjayetsi]

One more question again.

 

What is the other doawback if we move from Voice guide version "VG for TAPI" to "VG for Dialogic" ?

[Guest sanjayetsi]

Sorry I mean (DRAWBACK)

 

What are the other (if any) DRAWBACKS if we move from Voice guide version "VG for TAPI" to "VG for Dialogic" ?

[SupportTeam]

There are none.

We strongly recommend all Dialogic card users to use the "VoiceGuide for Dialogic" version of the software.

[Guest sanjayetsi]

Hello,

 

1) I believe We have a disadvantage for using VG 6.0 for Dialogic:

We have to convert our old files to a bit inferior sound quality of PCM 8kHz 8bit Mono!

Right?

If I use the same 11 KHz sound file then it is playing in a very slow motion speed!

 

2) I am still not able to get the Unique ID for the Dialogic card. The card is working fine ( D/4 PCI Analog ) but the Windows device manager shows a question mark for "Other Devices". Is this the reason? What do you think is the problem? I am not able to use the Reg Code in this situation. Can you help?

 

3) Is there any 5.X version for Dialogic where we can use the same sound files?

 

Thanks,

Sanjay

[SupportTeam]

We have to convert our old files to a bit inferior sound quality of PCM 8kHz 8bit Mono!

The 8kHz sound files are more then adequate for telephone lines. Average phone line has a 3.5kHz frequency range.

2) I am still not able to get the Unique ID for the Dialogic card.

Is the Dialogic service started before you start VG?

Windows device manager shows a question mark for "Other Devices".

This can be just ignored. See: http://voiceguide.com/forums/index.php?showtopic=1147

3) Is there any 5.X version for Dialogic where we can use the same sound files?

No.