Voip Testing Issues

[Guest Guest_Jack]

I'm testing a Voip application with VoiceGuide and Dialogic D/4PCI. The system is calling out on a Voip line (SIP) to my analog line. The analog line does not connect to the dialogic card. Everything works fine, except that every so often, usually occuring in clusters, the dialer dials, then responds with Uncontactable_NoAnswer or Uncontactable_Busy, even though the target analog line doesn't ring, nor is it busy. As part of the normal function of the Voip line, when it is off hook the dial tone is preceeded by a series of pulse tones that sound like a re-order tone. I wonder if this might have something to do with it? The Voip line otherwise has an excellent quality, capturing DTMF tones with 100% reliability. Broadband cable internet connection, via cheap router.

 

What up?

Jack

[SupportTeam]

Could you please post a copy of VoiceGuide's Debug Printout which captures the call, this will allow us to see what happened.

 

When running the script click on VoiceGuide's View menu and select 'Event Trace Log' option - any log information will then appear in this window. You must open the trace window before making the call. You can enable the automatic saving of the logs to files in \log\ directory as well.

 

Pleae supply both the MMDDvgm.txt and MMDDtw.txt traces.

[Guest Guest_Jack]

This is an example of a call interpreted as 'Uncontactable_NoAnswer, where the telephone did not ring.

 

Thank you in advance,

Jack

VGM___TW_Logs.txt

[SupportTeam]

Trace shows that VoiceGuide made the call :

 

131244.55 6 Dialing: **********

 

Then after about 20 seconds the Dialogic card reported that it heard the answering machine on the line

 

131308.04 6 callstate DISCONNECTED 66078 16 0

 

The actions set for answering machine was "Retry" - but as the number of retries was exhausted (it was set to 0) then the call was classified as "Uncontactable_NoAnswer".

 

It's probably best to set the answering machine action/script to "Ignore".

 

When making calls over most IP lines whish are usually poor quality there is a higher chance of real human answers being mistaken for answering machines by the Dialogic card.

[Guest Guest_Jack]

Thank you,

 

How is it that during the 20 seconds that you speak of prior to the erroneous detection of an answering machine, the target telephone was not ringing?

 

Regards,

Jack

[SupportTeam]

Looks like most likely what happened then is that the phone company or VoIP carrier could not connect the call and after about 20 seconds an automated message was played and that's what the Dialogic card detected.

 

When an answering machine / automated message is detected then VoiceGuide will start recording what it hears on the line is there is a script or sound files specified to run/play for that situation. You may want to run a few tests like that to see what the Dialogic card is hearing on the line at that time. Recordings are saved in Vg's \data\ subdirectory and are named RecAm_X.wav