Unusually High Number If "disconnected"

[jewillis]

I am running VG on two separate systems and experience a very large number of "DISCONNECTED" status for many calls (see attached). The numbers are goos and if I restart VG and reload the calls, the calls will go through. I am having to restart VG every day to avoid this. I experience this on two separate sytems in two separate data centers

 

I am running:

vgEngine version : 7.1.3559.20538 (RELEASE Build)

Dialogic D/480-JCT-2T1

Drivers : SR60SU184_for_VoiceGuide_red

 

Jeff

logs.zip

CallReport.zip

[SupportTeam]

A number of calls in the trace were disconnected as the Dialogic card reported hearing the DISCONNECT_USER_1 tone on the line.

 

As you are using an ISDN system then you do not need to use tone detection to determine end of call.

 

Would recommend you remove the extra DISCONNECT tone definitions from your ConfigLine.xml file, and set the main DISCONNECT tone definition to a tone combination that is unlikely to be detected (narrow frequency bank with lots of cadence repetitions).If you would like you can post your ConfigLine.xml file here and we will modify it accordingly.

[jewillis]

Attached

 

Thanks

config.zip

[jewillis]

One more file

ConfigLine.zip

[SupportTeam]

Please see attached ConfigLine.xml and try using this file on your system. Please post traces as before if you still encounter problems.

ConfigLine.zip

[jewillis]

Still an issue and I have discovered another issue

 

 

Invalid Disconnect (numbers verified to be good)

12164757801

15418474844

15418475844

12167314723

12165314709

12164757801

12164690696

 

Disconnected calls with Answer Time (numbers are verified to be good)

13234281849

15415142423

15414243047

 

 

The VG Disconnect.XLS is an export of the SQL database of calls that have invalid disconnects. Currently there are two issues.

 

Issue#1 – The numbers listed below as Invalid Disconnect are valid numbers that we receive a disposition of Disconnect.

 

Issue#2 – Disconnected calls with Answer Time, these numbers receive a disposition of disconnect, and an Answer time is recorded. These numbers are verified as good.

 

The zip file contains the system logs, all of these numbers are verified to exist in the logs.

 

 

An additionall issue that i had reported some tome ago, but is still happening. After a call is completed, the OUT flag is still active, thus preventing the line fron being used again until U restart VG.

 

All logs attached

 

 

Jeff

logs.zip

[SupportTeam]

The ISDN message 'Disconnect' means that the call is to be ended. It does not mean that the 'Number is Disconnected'. Every call completes with a Disconnected message.

 

eg: The second number on list 15418474844 had successful calls to it made 3 times, and once the Telco sent Disconnected - but we can see that the Disconnected was sent at time when this number was dialed at same time on another line (look at the timestamps of calls below).

 

Most likely the other calls on the list were ended by Telco as the dialed number was busy.

 

163644.186 3768 7 gc_MakeCall [15418474844] call (SR60)

163644.186 3768 7 gc_MakeCall ok. crn=28000f9

163644.202 1304 7 ev GCEV_DIALING crn=28000f9 crn_lastMakeCall=28000f9

163644.311 1304 7 ev GCEV_PROCEEDING crn=28000f9 lastMakeCall=28000f9, hli->crn=28000f9

163644.311 1304 7 ev GCEV_PROGRESSING crn=28000f9

163651.186 1304 7 ev GCEV_ALERTING crn=28000f9 (ktTel_SR60 v7.1.0, Sep 29 2009 14:21:35)

163718.827 1304 7 ev GCEV_CONNECTED (ktTel_SR60 v7.1.0, Sep 29 2009 14:21:35)

163722.436 1304 7 TDX_CALLP CR_CNCT CON_PVD (connection due to Positive Voice Detection)

 

 

220712.472 3768 7 gc_MakeCall [15418474844] call (SR60)

220712.472 3768 7 gc_MakeCall ok. crn=2800111

220712.487 1304 7 ev GCEV_DIALING crn=2800111 crn_lastMakeCall=2800111

220712.612 1304 7 ev GCEV_PROCEEDING crn=2800111 lastMakeCall=2800111, hli->crn=2800111

220712.612 1304 7 ev GCEV_PROGRESSING crn=2800111

220719.581 1304 7 ev GCEV_ALERTING crn=2800111 (ktTel_SR60 v7.1.0, Sep 29 2009 14:21:35)

220747.472 1304 7 ev GCEV_CONNECTED (ktTel_SR60 v7.1.0, Sep 29 2009 14:21:35)

220751.003 1304 7 TDX_CALLP CR_CNCT CON_PVD (connection due to Positive Voice Detection)

 

 

220744.784 3768 13 gc_MakeCall [15418474844] call (SR60)

220744.800 1304 13 ev GCEV_DIALING crn=2800119 crn_lastMakeCall=2800119

220744.956 1304 13 ev GCEV_PROCEEDING crn=2800119 lastMakeCall=2800119, hli->crn=2800119

220744.956 1304 13 ev GCEV_PROGRESSING crn=2800119

220749.440 1304 13 ev GCEV_DISCONNECTED crn=2800119

 

 

221245.425 3768 10 gc_MakeCall [15418474844] call (SR60)

221245.440 1304 10 ev GCEV_DIALING crn=2800124 crn_lastMakeCall=2800124

221245.550 1304 10 ev GCEV_PROCEEDING crn=2800124 lastMakeCall=2800124, hli->crn=2800124

221245.550 1304 10 ev GCEV_PROGRESSING crn=2800124

221252.987 1304 10 ev GCEV_ALERTING crn=2800124 (ktTel_SR60 v7.1.0, Sep 29 2009 14:21:35)

221319.331 1304 10 ev GCEV_CONNECTED (ktTel_SR60 v7.1.0, Sep 29 2009 14:21:35)

221322.847 1304 10 TDX_CALLP CR_CNCT CON_PVD (connection due to Positive Voice Detection)

 

Looks like in situations where call was not connected due to number being busy the CDR sometimes just saves the last ISDN message (which is 'Disconnected') in the Disposition field. Will look into this to see if this is still the case in current version of VGv7.

 

 

 

In the call to 13234281849 at 19:11 looks like the recipient of call placed the handset back on the phone about 9 seconds after they picked it up. Looks like during that time nothing was spoken (?) as Dialogic did not establish whether call was answered by answering machine or live person, so the script was not started yet at time when call was ended by call recipient.

 

The CDR Duration and BillSeconds fields reflect what happened, but looks like the hangup time was not correcty updated in this situation. Will look into the Hangup time bug to see if it was fixed in the more recent versions of VGv7.

 

 

191120.159 3768 2 gc_MakeCall [13234281849] call (SR60)

191120.159 3768 2 gc_MakeCall ok. crn=280010c

191120.175 1304 2 ev GCEV_DIALING crn=280010c crn_lastMakeCall=280010c

191120.253 1304 2 ev GCEV_PROCEEDING crn=280010c lastMakeCall=280010c, hli->crn=280010c

191120.253 1304 2 ev GCEV_PROGRESSING crn=280010c

191122.909 1304 2 ev GCEV_ALERTING crn=280010c (ktTel_SR60 v7.1.0, Sep 29 2009 14:21:35)

191132.518 1304 2 ev GCEV_CONNECTED (ktTel_SR60 v7.1.0, Sep 29 2009 14:21:35)

191132.518 1304 call progress: started listening on chdev 3

191141.956 1304 2 ev GCEV_DISCONNECTED crn=280010c

[jewillis]

Thanks

 

this worries me "It does not mean that the 'Number is Disconnected'. Every call completes with a Disconnected message."

 

I forward teh disposition to the client and they se all the disconnects and complain that the software is not making clls. How should I label them instead?

 

Jeff

[SupportTeam]

Will check and advise whether the current versions of VoiceGuide v7 set the Disposition field to the Disconnection cause in the cases where the outgoing call is Disconnected due to 'Busy'. That field should be set to Disconnection cause value.