Disconnect Detection Instead Of Busy

[pedgarhi]

Hello. I'm working with VG for Dialogic.

 

My problem is that the disconnect and busy tones of my PBX have the same frequency and ON/OFF periods. The only difference is that in the disconnect tone there is a silence after 3 ON/OFF periods while in the busy tone the ON/OFF periods are continuous.

 

I have tryed to configure this tones in the configLine.xml file, but VoiceGuide is detecting the disconnect tone instead of the busy tone.

 

My configuration is:

 

BUSY TONE:

 

Freq1: 433 Hz

Freq1Dev: 100 Hz

Freq2: 0

Freq2Dev: 0

On: 220 ms

OnDev: 30 ms

OffDev: 220 ms

OffDev: 30 ms

Count: 5

 

DISCONNECT TONE:

 

Freq1: 433 Hz

Freq1Dev: 100 Hz

Freq2: 0

Freq2Dev: 0

On: 220 ms

OnDev: 30 ms

OffDev: 220 ms

OffDev: 30 ms

Count: 2

 

How can I configure this tones in the configLine.xml?

[SupportTeam]

Looks like it will not be possible to distinguish between the two tones on your system...

 

Are you trying to do monitored or announced hookflash transfers?

 

Could you please post a copy of VoiceGuide's Debug Printout which captures the problem, 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.

[pedgarhi]

I'm trying to make announced hookflash transfers.

 

You can see 3 transfer attempts in the attached file. First at 123610,42, second at 123642,34 and third at 123714,14.

 

The first and second attempts are finished with NORINGBACK detection. Could you explain me the meaning of this?

 

And the third attempt is finished with a DISCONNECT tone detection instead of a BUSY detection (the destination number was busy).

 

Any idea?

0624vgm__disconnect_.txt

[SupportTeam]

Try setting the BUSY tone's repetition counter to a value lower then the Disconnect tone's.

 

eg: make BUSY tone's repetition counter 2 and DISCONNECT tone's repetition counter 4.

 

We are looking into the NORINGBACK results.

[pedgarhi]

Now VoiceGuide is detecting the BUSY tone, but it is hanging up the call. I have defined a BUSY path in the transfer module but it hangs up anyway.

 

I attach the log file.

0627vgm__busy_tone_hangs_up_.txt

[SupportTeam]

You are using an old version VG for Dialogic (v6.0.1055).

That version had the bug which you describe.

 

Please download the current release of VG for Dialogic (v6.0.2028 now) and update your system with the .EXEs and .OCXs from that version and try again.

[pedgarhi]

I have updated to VG for Dialogic 6.0.2028, but I continue having problems with tones detection.

 

Now I have set BUSY tone's repetition counter to 2 and DISCONNECT tone's repetition counter to 2 as well. I can't set the DISCONNECT tone's repetition count to a higher value because in this case the tone is not detected. VoiceGuide is detecting false BUSY and DISCONNECT tones in different modules of my script that are hanging up the call. Not in the Transfer Call module, but in Play or Say Numbers modules.

 

Besides, I have seen that the program sometimes executes the script from the beginning after hanging up a previous call. It seems that VoiceGuide is detecting the DISCONNECT tone as if it was the RING tone and it starts a new call.

Can I configure anywhere a delay time between calls?

 

What can I do? Please, help.

[SupportTeam]

What is the actual problem when you set the BUSY tone's repetition counter to 2 and DISCONNECT tone's repetition counter to 4 ?

 

Please provide a trace capturing it.

 

It seems that VoiceGuide is detecting the DISCONNECT tone as if it was the RING tone and it starts a new call.

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

[pedgarhi]

The problem of setting DISCONNECT tone's repetition counter to 4 is that VoiceGuide is unable to detect it because it follows this pattern:

 

ON: 200 ms OFF: 200 ms

ON: 200 ms OFF: 200 ms

ON: 200 ms OFF: 600 ms

ON: 200 ms OFF: 200 ms

ON: 200 ms OFF: 200 ms

ON: 200 ms OFF: 600 ms

...

 

The attached file captures the described problem about the hangup and restart of the call.

 

This line appears in the log file before the current call has been finished:

 

075134,59 1 event callstate OFFERING 1 0 0

 

so, a new call is started just after hanging up the previous one.

0630vgm__restart_call_.txt