VoiceGuide IVR Software Main Page
Jump to content

Calls With Linecallstate_Didconnected

Recommended Posts

We have a client that experienced large number of calls that were disconnected in the middle of the VoiceGuide script processing. It appears that program detects that line has been disconnected and hang up the call.

 

In VoiceGuide Log Viewer Hangup Source property of the call is listed as LINECALLSTATE_DISCONNECTED

 

VG v7.1.3656.25878; Dialogic D/4PCIUF; OS - Windows XP - Professional

 

I have attached log files and screen shoot of VoiceGuide Log Viewer with two events in question.

 

Please assist to resolve the issue.

 

Thank you

20100829 logs.zip

20100902 logs.zip

LINECALLSTATE_DISCONNECTED Call Viewer example events.zip

Share this post


Link to post

Traces show that calls are disconnected as the Dialogic card reported hearing the DISCONNECT_USER_2 tone.

 

Looks like you should look at the DISCONNECT_USER_2 tone definition in ConfigLine.xml and change its settings so that it is less likely to be falsely detected. This means increasing the cadence count and reducing the allowed deviation ranges. Or you can remove the DISCONNECT_USER_2 tone definition altogether if it does not represent a tone that system should be listening for.

 

Please see: http://www.voiceguide.com/vghelp/source/html/disconnectiondetect.htm

 

 

 

065535.578 19 1 1 ev CallState LINECALLSTATE_DISCONNECTED-DISCONNECT_USER_2, crn=10000068, iEvent=2 ,16384,0,64,,,]. vgEngine v7.1.3656.25878 (2010-01-04 14:22:37.40)

065535.578 19 1 1 qScr add evCallState 2 LINECALLSTATE_DISCONNECTED-DISCONNECT_USER_2

065535.578 6 1 1 qScr run evCallState sCode=[LINECALLSTATE_DISCONNECTED-DISCONNECT_USER_2] iActionID=0, crn=10000068[16384|0|64|0|0][|||||]

065535.578 6 1 1 ls set Disconnected (scriptstate=LS_GETNBRS_RXDIGITS)

065535.578 6 1 1 yLineStateAppPov: Disconnected crn=10000068,ev=2,LINECALLSTATE_DISCONNECTED-DISCONNECT_USER_2,0, sParam1=

065535.578 6 1 1 LineEvCallState LINECALLSTATE_DISCONNECTED begin

Share this post


Link to post

I have removed "the DISCONNECT_USER_2 tone definition", which partially resolved the issue (the number of rejected called reduced by 9 times). We still can see the drop calls in the Log files, however an exact cause was not identified.

 

If any definitive source of the issue will be identified, I will update this post.

 

Thank you

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×