Vg Won't Detect Hangup After Update

[Guest docfate]

Hello,

 

I went ahead and upgraded my VoiceGuide recently to version. 6.0.2322

 

However after the upgrade, VoiceGuide no longer detects hangup calls, and it stays on indefinately. Here is the Trace Log.

 

Any help would be appreciated.. I have a Dialogic Card.

 

 

203947.34 1 event callstate OFFERING 1 2,0,0

203947.34 1 script interpretor: VgMulti v6.0.2322

203947.34 1 fired OFFERING event to listeners

203947.36 1 set LineState().hCall = 1 in LINECALLSTATE_OFFERING

203947.36 1 cid CallerID vars set (in 'offering' event) [,,]

203947.36 1 call AnswerTheCallIfAllowed from LINECALLSTATE_OFFERING

203947.36 1 rings=0, min rings before answer=0 (iCallerIdHasArrived=0)

203947.38 1 tw ring 1

203947.38 1 ring time since last ring event (sec): 0.00

203947.38 1 rings=1, min rings before answer=0 (iCallerIdHasArrived=0)

203947.38 1 answer as number of rings reached

203947.39 1 rv clear all

203947.39 1 init LineState ResetAtStartOfNewCall.

203947.41 1 answer the call

203947.41 1 timer clear

203947.44 1 tw DialogicEvent 134,TDX_CST,0,0,0,DE_RINGS,ET_RON,

203947.44 1 event ScriptEventCode TDX_CST, code=134, state=6001

203948.28 1 tw DialogicEvent 135,TDX_SETHOOK,0,0,0,DX_OFFHOOK,CALL_INBOUND,

203948.28 1 event ScriptEventCode TDX_SETHOOK, code=135, state=6001

203948.30 1 event callstate CONNECTED 1 256,0,0

203948.31 1 LineEvCallState_Connected hDevice=1 params=256,0,0

203948.31 1 WorkingModes tapi= script= LineState().iState=6001

203948.34 1 Inband detection not enabled

203948.36 1 StartLoadedVgs at 12/30/2005 8:39:48 PM [VgMulti v6.0.2322]

203948.38 1 set LineState().iVgsIdx=1

203948.38 1 set sScriptToRunOnHangup=[] in StartLoadedVgs

203948.39 1 init StartLoadedVgs_InitLineState start

203948.41 1 rv add [$RV_STARTTIME]{12/30/2005 8:39:48 PM}

203948.41 1 rv add [$RV_DEVICEID]{1}

203948.42 1 rv add [$RV_CIDNAME]{}

203948.44 1 rvns add [PathApp]{C:\Program Files\VoiceGuide\}

203948.45 1 rvns add [scriptsPath]{c:\pbds-phone\}

203948.45 1 rv add [$RV_CIDNUMBER]{}

203948.47 1 fn RunModule start

203948.48 1 tw DialogicEvent 134,TDX_CST,7357,0,0,DE_LCON,,

203948.50 1 event ScriptEventCode TDX_CST, code=134, state=6001

203948.52 1 timer clear

203948.53 1 state [Welcome Message] Number Input

203948.53 1 state [Welcome Message] Playing (WELCOME_MESSAGE.wav)

203948.55 1 tw ConvertWav2Vox c:\pbds-phone\WELCOME_MESSAGE.wav

203948.56 1 timer clear

203948.61 1 tw wav->vox convert end 467593,c:\pbds-phone\WELCOME_MESSAGE.vox,1,0,,

203948.66 1 play start ok, lPlayId=467671

203953.47 1 tw DialogicEvent 134,TDX_CST,545,0,0,DE_LCOF,,

203953.48 1 event ScriptEventCode DE_LCOF, code=134, state=1300

203953.50 1 LsGetNbrsPlayWelcMsg EV_UNKNOWN_134,DE_LCOF

203953.50 1 path {DE_LCOF} not found

203953.78 1 tw DialogicEvent 134,TDX_CST,31,0,0,DE_LCON,,

203953.80 1 event ScriptEventCode TDX_CST, code=134, state=1300

203953.81 1 LsGetNbrsPlayWelcMsg EV_UNKNOWN_134,TDX_CST

203953.81 1 path {TDX_CST} not found

204004.55 1 tw DialogicEvent 134,TDX_CST,1076,0,0,DE_LCOF,,

204004.59 1 event ScriptEventCode DE_LCOF, code=134, state=1300

204004.63 1 LsGetNbrsPlayWelcMsg EV_UNKNOWN_134,DE_LCOF

204004.67 1 path {DE_LCOF} not found

204004.89 1 tw DialogicEvent 134,TDX_CST,35,0,0,DE_LCON,,

204004.91 1 event ScriptEventCode TDX_CST, code=134, state=1300

204004.98 1 LsGetNbrsPlayWelcMsg EV_UNKNOWN_134,TDX_CST

204005.00 1 path {TDX_CST} not found

[SupportTeam]

Can you please post the MMDDtw.txt log (in VG's \data\ subdirectory).

 

Did you set the disconnect tones in ConfigLine.xml file?

[Guest Guest]

I noticed that you told other people to record the disconnect tone, and to post it up here as a zip file, and you would analyze and tell us what to put in the settings.

 

So, here is my file.

 

Thanks

Docfate

disconnect_tone.zip

[SupportTeam]

Can you please post the MMDDtw.txt log (in VG's \data\ subdirectory).

 

What frequencies/cadences did you set for the disconnect tones in ConfigLine.xml file?

[Guest Guest]

There's no such file in the data subdirectory.

 

about the cadences.. unsure where you find that, all I did was keep everything as default, and it was working fine before the update.

 

Docfate

[SupportTeam]

There's no such file in the data subdirectory.

Please see in \log\ subdirectory then. MMDD stand for Month and Day.

 

For information on how to find out and set the disconnect tones frequencies/cadences please read: http://www.voiceguide.com/vghelp/html/Disc...ctionDetect.htm

[Guest Guest]

Here is the file that you wanted.

 

Docfate

0102tw.zip

[Guest Guest]

Here is the cadences that I tried. taken directly from that file you posted.

 

<Tone Name="Call Progress Tone TID_DISCONNECT">

<Notes>Our Disconnect Tone</Notes>

<ID>TID_DISCONNECT</ID>

<Freq1>428</Freq1>

<Freq1Dev>50</Freq1Dev>

<Freq2>0</Freq2>

<Freq2Dev>0</Freq2Dev>

<On>25</On>

<OnDev>5</OnDev>

<Off>75</Off>

<OffDev>5</OffDev>

<Count>3</Count>

</Tone>

 

 

 

 

Docfate

[SupportTeam]

The MMDDtw.txt trace shows:

210149.515 001 ev    DE_LCOF does not cause DISCONNECTED event as Rule: SendDisconnectOnLoopCurrentDrop=0

in ConfigLine.xml file in the 'Rules' section find entry for SendDisconnectOnLoopCurrentDrop and set it's value to 1. This way the disconnect will occur when loop current drop is detected.

 

Did you analyze the recorded disconnect tone? What frequency/cadence values did you obtain after analyzing the disconnect tone?

[Guest Guest]

alright, this seems to have fixed the problem. My system is now hanging up the call as soon as the phone is hungup.

 

I think you guys should really make this the default , because I know that most people will want to have their calls hungup after someone disconnects.

 

Just my 02 cents.

 

Docfate

[SupportTeam]

On some phone systems the Loop Current get dropped during call transfers, and sometimes even partway through the call - that's why by default VG does not end the call when it detects Loop Current drop.

 

And on analog lines you can also detect end of call by listening for the disconnect tone as well (which you did not configure by the looks of it...)

[Guest Guest]

You are right, I did not configure this part of it. I was trying to, but so far haven't had problems with the way we did it.

 

However, on the system that I had, before the upgrade, everything worked well without havng to worry about the disconnect tone, etc.

 

So, maybe it's whe you have a PBX that things get screwy.

 

 

Anyway, I have another question, does your system able to have a on HOLD MUSIC function. Meaning, when I place a call on HOLD, it starts playing nice music so that people don't get bored and hang up he phone? This would be cool for my business, withou having to integrate another piece of hardware or software.

 

Thanks

Docfate

[SupportTeam]

It's not VoiceGuide that would play the 'on-hold' music - it's the equipment which recognised the hookflash signal and placed the call on hold (so that VG can now do whatever else it needs to do) that is able to play any hold music.

 

When call is placed 'on-hold' the voice path between VG and caller is broken, so original caller does not hear what VG is doing (dialing digits, playing etc).