Having Problems Sending Messages To Answering Machines

[eweyl]

I have one script for a live person and another one loaded for the answering machine. On some answering machines it thinks it's a live person and starts that script, on other's it won't even leave a message, it will ring 7 times and then hang up, and yet on other answering machines it works fine. Is there something I'm missing, how can I make this more consistent? Thank you.

[SupportTeam]

Answering machine detection is not accurate. It is actually pretty hard for a computer to determine if answered call is a live person or a machine. Dialogic has better success at determining this then any other company. You should on average be seeing 95%+ correct detection. Please read: http://www.voiceguide.com/vghelp/source/ht...tcallanswer.htm

[eweyl]

Is there any difference if the answering machine/voice mail has an automated message or a personal message? This is the only difference I have found so far, I've been testing with 4 different numbers to call and 2 have automated messages and the other 2 have personal messages. A message was left for the two numbers that had a personal message for their voice mail and no message was left for the automated ones.

[SupportTeam]

Is there any difference if the answering machine/voice mail has an automated message or a personal message?

Were the calls to the machines that had their own default message playing categorized as 'live' calls by the Dialogic card? If the message played has been recorded in very high quality then the Dialogic card thinks that a live person has answered the call.

[eweyl]

VG did not recognize the automated messages as a 'live person' (except once) it just hangs up the call instead.

[SupportTeam]

The traces (and the CDR entry) would how what actually happened on the call.

 

If you want to post the traces and indicate which call we should be looking at we can tell you what the traces are showing.

[eweyl]

Here is the VG engine trace and the CDR's.

CDR_and_VG_engine.zip

[SupportTeam]

Attached trace shows that an outgoing call was made and 30 seconds later the call was ended as no answer was detected by the Dialogic card during that time (and answer timeout was set to to 30 seconds).

 

I think the problem here is that you are using a ";" instead of a "," after the leading 9.

 

Does the number dialed actually ring?

 

 

084756.640 6 1 state Dialing 9;12392490216...

084757.187 17 1 ev Dialogic 135,TDX_SETHOOK, crn=2000000d, 0,0,0,DX_OFFHOOK,CALL_OUTBOUND,

084757.187 17 1 qScr add evScriptEvent 135 TDX_SETHOOK

084757.187 6 1 qScr run evScriptEvent TDX_SETHOOK, iActionID=0, crn=2000000d[0|0|0|0|0][DX_OFFHOOK|CALL_OUTBOUND||||]

084757.187 6 1 ScriptEvent TDX_SETHOOK DX_OFFHOOK|CALL_OUTBOUND|

084757.187 6 1 LsWaitAfterDialingOut : 135,2000000d,TDX_SETHOOK,0,0,0,DX_OFFHOOK,CALL_OUTBOUND,

084829.437 20 1 timer fired EV_TIMEOUT_MAKECALL_NORESPONSE

[eweyl]

The numbered dialed does ring. I tried changing the ";" to a "," and that didn't make any difference, it will call to the number but it will not leave a message on the answering machine.

[SupportTeam]

Does the answering machine answer the call within 30 seconds? Looking back to your original post you say that "it will ring 7 times and then hang up", so it sounds like the reason why no message is left is because the answering machine does not even answer the call.

 

If it takes more then 30 seconds for the answering machine to answer the call then you should set the timeout on the outbound calls to be more then 30 seconds.