Hang Up Detection Strange One

[Carphone]

Hi all,

 

at present we have a single pc running a d4pciu and latest version of VG, this is working fine. we recently purchased another d4pciu and installed this into a new (seperate) pc to run alongside our exisiting one. this new pc will not detect when the caller has hung up (everything else is fine). the settings are no different to our original pc.

 

In our original setup we did not have to change any settings, hang up detectiuon was perfect - i assume from choosing UK as country settings.

 

We have used the same software drivers to install the dialogic card.

 

 

having read this article:

http://www.voiceguide.com/vghelp/html/Disc...ctionDetect.htm

 

and variuos threads, it seems i may have to record the hang up sound. but will this really help me at all as i have the default uk settings that work in the other computer.

 

any ideas because after many hours im stuck.

 

thanks

 

Dan

[SupportTeam]

Please post the screenshots of the Dialogic TSP config screens from both systems.

[Carphone]

All the settings are identical for both computers, i have been through them very carefully.

 

I have attached a recording of our disconnect tone. could you please take a look at this and recommend settings for us.

 

i will also post some screen shots from pbxepert shortly.

 

thanks

 

Dan

disconnect.zip

[SupportTeam]

please post screenshots from the Dialogic TSP - like the screenshots here: http://www.voiceguide.com/vghelp/html/Disc...ctionDetect.htm

[Carphone]

hi please find screen shots from both computers within the attached zip file.

 

I look forward to your further assistance.

 

thanks

 

Dan

screenshots.zip

[SupportTeam]

The screenshot of the 'working TSP' does not show the page where the disconnection tone is set - please post the screenshot of the 'Disconnect Tone' tab from that machine.

[Carphone]

please find a screen shot from the working computer. from what i can see they are the same.

 

Can you compare the default settings we are using with your analysis of the disconnection tone sound file attached in the above post.

 

I look forward to your help, this has causing us problems for several days now.

 

Thanks

[SupportTeam]

The recording of the disconnect tone (attached a few posts back) shows that the disconnect tone has a frequency of 425Hz and is on for 375ms followed by silence of 375ms.

 

I'd recommend the settings to be:

 

Freq 1 : 425

Freq 1 deviation : 50

Freq 2 : 0

Freq 2 deviation : 0

On time : 37

On time deviation : 5

Off time : 37

Off time deviation : 5

Repetition : 2

 

 

You can use the CoolEdit software to do frequency analysis on recorded sound files to determine the frequencies of the busy/disconnect tones.

 

CoolEdit has now been purchased by Adobe and is known as "Audition", but the original free software can still be downloaded from a number of places, eg:

 

http://www.xtec.es/recursos/clic/bin/c96setup.exe

 

Another tool you can use is Audacity ( http://audacity.sourceforge.net/ ) it has a View->Plot Spectrum menu which will also show you the frequencies in a sound file.

 

This post was corrected as the original frequencies reported were wrong. Changes are in bold.

Edited 08/30/2004 01:09 AM by SupportTeam

[Carphone]

Appologies i attached an incorrect disconnection tone file earlier (because i was looking at other examples from past threads and attached the wrong file in error). please find attached the correct disconnection file.

 

I have attempted to analyse this file but am not really sure in what i am doing. Can you please analyse this file and give results as you did above.

 

thanks for your continued patience.

hangup.zip

[SupportTeam]

The new tone is just a continuous tone of 400Hz.

 

I'd recommend the settings to be:

 

Freq1 : 400

Freq1 deviation : 50

Freq2 : 0

Freq1 deviation : 0

On time : 200

On time deviation : 20

Off time : 0

Off time deviation : 0

Repetition count : 1

 

or try:

 

Freq1 : 400

Freq1 deviation : 50

Freq2 : 0

Freq1 deviation : 0

On time : 200

On time deviation : 20

Off time : -200

Off time deviation : 20

Repetition count : 1

 

Please let us know which one (or both) works for you and which model card you are using.

[Carphone]

Hi thanks for your help. We have spent some time experimenting with your settings.

 

firstly we are using a dialogic d4pciu, it is not possible to put your 2nd settings in as the minus charachter is not accepted.

 

The first settings detected hangup but also caused unexpected hangups as well. After tweaking them slightly we have now have a setup which seems to work reliably. (very good news :-)) We still need to do further testing but looks good so far. Please see the screen shot attached for details on the settings we are using.

Can you see any potential problems with these settings?

 

Also whilst experimenting with on time it seems this has little or no affect. Even if we increase the on time to 1000, we get an instant hangup detection. From what i understand with the current settings we are using, a 2 sec freq of 400hz should be detected before the hangup is confirmed. But it is an instant detection.

any idea why the hangup is detected so quickly. (this is good for us but still would like to know why)

 

I am still puzzled why our first computer does not require these settings at all. I assume that our first computer is detecting hangup using loop current drop. If this is the case I suspect that our new dialogic card may be faulty as it can not detectect the loop current drop.

do you think this is likely?

Is there a way to confirm that our first computer is using loop current drop to detect hangup?

 

 

Once again thanks for you patience and ongoing support!

[SupportTeam]

Can you see any potential problems with these settings?

"Freq1 deviation" isprobably set too low - I'd set it to at least 10 or 20

any idea why the hangup is detected so quickly. (this is good for us but still would like to know why)

Looking at the debug trace should tell us what's happening. 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.

Is there a way to confirm that our first computer is using loop current drop to detect hangup?

We can tell by looking at the MMDDtw.log trace - see in VG's \log\ subdirectory.

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. Select 'save to file' - the log file will then be created for subsequent calls.

[Carphone]

please find a trace from our computer which is using the custom settings above:

 

 

174122.92  8 ScriptEventCode 9002 iLineState=1101
174122.92  8 LsPlayMsgFinished EV_TIMEOUT_GOTOMODULE
174122.92  8 TimeoutClear
174122.94  8 [Enter Network play] Playing
174122.94  8 [Enter Network play] Playing (sounds for voice\IRISHenternetwork.wav)
174122.94  8 PlaySoundStart ok [C:\sounds for voice\IRISHenternetwork.wav]
174122.95  8 TimeoutClear
174122.95  8 RunModule PLAY end
174122.95  8 wa(13125,81848400)
174122.95  8 callinfo MONITORMODES
174132.03  8 callstate DISCONNECTED 65996,0,0
174132.03  8 ScriptEventCode 9250 iLineState=1100
174132.05  8 LsPlayMsg EV_REMOTEPARTY_DISCONNECT
174132.05  8 rv    add [Hangup Time]{31/08/2004 17:41:32}
174132.05  8 Hanging up call...
174132.05  8 RecSoundStop ok
174132.11  8 PlaySoundStop err=0
174132.11  8 TimeoutSet 2 EV_TIMEOUT_WAITFORIDLEAFTERLINEDROP
174132.13  8 fnHangupCall end
174132.17  8 linedevstate 2048 0 0
174132.17  8 callstate IDLE 65996 0 0
174132.17  8 WorkingMode@Idle=
174132.19  8 TimeoutClear
174132.19  8 TimeoutSet 1 EV_TIMEOUT_TIMETOREINITLINE
174132.19  8 tapi  Reply (LineEvReply) ok 65962 0
174133.23  8 Timer fired EV_TIMEOUT_TIMETOREINITLINE
174133.23  8 ScriptEventCode 9008 iLineState=900
174133.23  8 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE
174133.23  8 ReinitTelephony due to IDLE
174133.23  8 tapic lineDeallocateCall(MainCall:65996) 0
174133.30  8 lineOpen(8)=>
174133.30  8 Waiting for a call...
174133.30  8 LineHandle=65945
174133.30  8 TimeoutSet 3 EV_TIMEOUT_ATERIDLE_ALLOWOUT
174136.91  8 Timer fired EV_TIMEOUT_ATERIDLE_ALLOWOUT
174136.91  8 ScriptEventCode 9013 iLineState=900

 

can you use this to see why our hangup detection is so quick, as mentioned earlier with the settings we are using i would expect it to be 2 seconds.

 

also we have had to reduce the deviation to zero now any higher and we still get unexpected hangup problems.

 

thanks

[SupportTeam]

we need to see the MMDDtw.txt trace - not the MMDDvgm.txt trace.