Outbound Call Hangup

[sddev]

Occasionally, I am seeing a hangup on outbound calls which appears due to a timeout. These events are reflected in OutDial_Dialed.txt but are not being saved in any of the Results Files.

 

I have installed Dailogic D/4PCIUF card.

 

Following log excerpt shows hangup after waiting approximately 8 seconds.

 

170945.73 1 dial [217,9,5037447,0,0,2359,MoTuWeThFrSaSu,[,,],2,NONE,c:\develop\vg\arms\ext.vgp,c:\develop\vg\arms\ext.vgp,[LOG_ID]{91}[uSER_PIN]{210}[TTS_PATH]{C:\Control Center\20610_2_tts.txt}[DIAL_EXT]{307},30,0,0,,none] (search started at 170945.73)

170945.73 1 dial DialOnLine start tel[9,5037447] ann[NONE] vgs[c:\develop\vg\arms\ext.vgp] am[c:\develop\vg\arms\ext.vgp] rv[[LOG_ID]{91}[uSER_PIN]{210}[TTS_PATH]{C:\Control Center\20610_2_tts.txt}[DIAL_EXT]{307}]

170945.75 0 dial callque update id=217: NextCallTime=0508261711, RetriesLeft=-1

170945.75 0 dial callque DB update returned (MSAccess)

170945.75 1 rv clear all

170945.77 1 rv add [LOG_ID]{91}

170945.77 1 rv add [uSER_PIN]{210}

170945.77 1 rv add [TTS_PATH]{C:\Control Center\20610_2_tts.txt}

170945.78 1 rv add [DIAL_EXT]{307}

170945.78 1 rv add [OutDial_RetriesLeft]{0}

170945.78 1 dial making call tel[9,5037447] ann[NONE] vgs[c:\develop\vg\arms\ext.vgp] am[c:\develop\vg\arms\ext.vgp] OnHangup[] rv[[LOG_ID]{91}[uSER_PIN]{210}[TTS_PATH]{C:\Control Center\20610_2_tts.txt}[DIAL_EXT]{307}[OutDial_RetriesLeft]{0}]

170945.80 1 script interpretor: VgMulti v6.0.2092

170945.80 1 state Dialing 9,5037447

170945.81 1 timer set 30 EV_TIMEOUT_MAKECALL_NORESPONSE

170946.34 1 tw DialogicEvent 135,TDX_SETHOOK,0,0,0,DX_OFFHOOK,CALL_OUTBOUND,

170946.36 1 event TDX_SETHOOK, code=135, state=5200

170946.36 1 LsWaitAfterDialingOut : 135,TDX_SETHOOK,0,0,0,DX_OFFHOOK,CALL_OUTBOUND,

170946.36 1 tw DialogicEvent 134,TDX_CST,240,0,0,DE_LCON,,

170946.38 1 event TDX_CST, code=134, state=5200

170946.38 1 LsWaitAfterDialingOut : 134,TDX_CST,240,0,0,DE_LCON,,

170954.39 0 btn Hangup on line 1

170954.39 1 event EV_TIMEOUT_HANGUP, code=9001, state=5200

 

Currently I am logging successful calls from a *.vgp script and parsing the results files to log failed calls. All information is saved to a MySQL database.

The rv{LOG_ID] is key information.

 

Accurate logging is important to permit proper followup by a separate monitoring application.

 

I prefer not to utilize the sOnNotConnected vbScript because it would expose the database connection information.

 

I do capture this situation in my own timeout routine but wonder if there is anything I can do to glean the information more quickly from vg.

Or, better yet, is there a way to prevent it.

 

Thanks for your help.

[SupportTeam]

Trace shows that outgoing call was abandoned as the "Hangup" button was pressed:

 

170954.39 0 btn Hangup on line 1

[sddev]

Hung up again without indication of btn hangup.

 

Obviously I see [OutDial_Result]{Uncontactable_NoAnswer}.

However, given the time lapse (.02 seconds ?) that is not an accurate result.

 

So what happened here.

How can I avoid this failure.

 

fyi 307 is a valid internal extension which is usually successfully dialed and answered.

 

100026.61 1 dial making call tel[307] ann[NONE] vgs[c:\develop\vg\arms\arms_evt_notify.vgp] am[c:\develop\vg\arms\arms_evt_notify.vgp] OnHangup[] rv[[LOG_ID]{129}[uSER_PIN]{210}[TTS_PATH]{}[OutDial_RetriesLeft]{0}]

100026.61 1 script interpretor: VgMulti v6.0.2092

100026.63 1 state Dialing 307

100026.63 0 dial callque delete id=227 (MSAccess)

100026.63 1 rvns add [OutDial_Result]{Uncontactable_NoAnswer}

100026.63 1 timer clear

100026.63 1 dial no escalation info

100026.63 1 rv add [Hangup Time]{8/30/2005 10:00:26 AM}

100026.63 1 state Hanging up call...

100026.63 1 HangupCall_Common hCall=0

100026.63 1 rec RecSoundStop ok

100026.63 1 play PlaySoundStop ok

100026.63 1 timer set 2 EV_TIMEOUT_WAITFORIDLEAFTERLINEDROP

100026.63 1 HangupCall : lCallHandle& = 0 - lets close and open line

100026.63 1 state Waiting for a call...

100026.63 1 fnHangupCall end

100026.64 1 event callstate IDLE 1 0 0

100026.64 1 WorkingMode@Idle=

100026.64 1 timer clear

100026.64 1 LineState(iLineId).iVgsIdx = 0

100026.64 1 timer set 1 EV_TIMEOUT_TIMETOREINITLINE

100026.64 1 tw DialogicEvent 135,TDX_SETHOOK,0,0,0,DX_ONHOOK,,

100026.64 1 event TDX_SETHOOK, code=135, state=900

100026.64 1 LsAwaitingCalls EV_UNKNOWN_135

100027.66 1 timer fired EV_TIMEOUT_TIMETOREINITLINE

100027.66 1 event EV_TIMEOUT_TIMETOREINITLINE, code=9008, state=900

100027.66 1 init atidle reinit : start

100027.67 1 init atidle reinit iConferenceOtherLegLid=-1

100027.67 1 init atidle reinit : reset all LineState variables

100027.67 1 timer set 0.3 EV_TIMEOUT_ATERIDLE_ALLOWOUT

100027.69 1 state Waiting for a call...

100028.02 1 timer fired EV_TIMEOUT_ATERIDLE_ALLOWOUT

100028.02 1 event EV_TIMEOUT_ATERIDLE_ALLOWOUT, code=9013, state=900

[SupportTeam]

Can you please post a few seconds (at least) worth of trace beforehand as well.

[sddev]

Here are log entries preceding what I previously sent,

 

093514.09 1 state Waiting for a call...

093514.42 1 timer fired EV_TIMEOUT_ATERIDLE_ALLOWOUT

093514.42 1 event EV_TIMEOUT_ATERIDLE_ALLOWOUT, code=9013, state=0

093603.27 0 sys cleanup Start

093603.27 0 sys cleanup End

100026.09 0 cl Dialer_OutDialQueAdd 307, 0, 0, 0, , , 2, , c:\develop\vg\arms\arms_evt_notify.vgp, c:\develop\vg\arms\arms_evt_notify.vgp, [LOG_ID]{129}[uSER_PIN]{210}[TTS_PATH]{}, 30, 0, 0, ,

100026.09 0 dial DialListDB_AddCall '307', 0, 0, 0, MoTuWeThFrSaSu, , 2, , c:\develop\vg\arms\arms_evt_notify.vgp, c:\develop\vg\arms\arms_evt_notify.vgp, [LOG_ID]{129}[uSER_PIN]{210}[TTS_PATH]{}, 30, 0, 0, ESCALATION:

100026.61 1 dial [227,307,0,0,2359,MoTuWeThFrSaSu,[,,],2,NONE,c:\develop\vg\arms\arms_evt_notify.vgp,c:\develop\vg\arms\arms_evt_notify.vgp,[LOG_ID]{129}[uSER_PIN]{210}[TTS_PATH]{},30,0,0,,none] (search started at 100026.61)

100026.61 1 dial DialOnLine start tel[307] ann[NONE] vgs[c:\develop\vg\arms\arms_evt_notify.vgp] am[c:\develop\vg\arms\arms_evt_notify.vgp] rv[[LOG_ID]{129}[uSER_PIN]{210}[TTS_PATH]{}]

100026.61 0 dial callque update id=227: NextCallTime=0508301002, RetriesLeft=-1

100026.61 0 dial callque DB update returned (MSAccess)

100026.61 1 rv clear all

100026.61 1 rv add [LOG_ID]{129}

100026.61 1 rv add [uSER_PIN]{210}

100026.61 1 rv add [TTS_PATH]{}

100026.61 1 rv add [OutDial_RetriesLeft]{0}

100026.61 1 dial making call tel[307] ann[NONE] vgs[c:\develop\vg\arms\arms_evt_notify.vgp] am[c:\develop\vg\arms\arms_evt_notify.vgp] OnHangup[] rv[[LOG_ID]{129}[uSER_PIN]{210}[TTS_PATH]{}[OutDial_RetriesLeft]{0}]

100026.61 1 script interpretor: VgMulti v6.0.2092

 

Thanks again for your assistance.

[SupportTeam]

Do you have the MMDDtw.txt log file capturing the unsuccessful outgoing call? The cause of why this call failed will be in the 'tw' log file.

 

You can enable the automatic saving of the logs to files in \log\ directory. The MMDDtw.txt log file will be created there when that option is enabled.

[sddev]

Attached find excerpt from tw log file for time frame surrounding unexplained hangup

 

093514.094 ocxfn RingsBeforeAnswer(lLineId=1, lRings=0, lParam1=0, strParam2=)

100026.625 001 ocxfn LineMakeCall(1, 0, 307, DX_PAMDOPTEN, 30, 0, 0, , )

100026.625 001 ocxfn RecStop(hLine=1, lRecId=0, lParam1=0, lParam2=0, strParam1=, strParam2=)

100026.625 001 ocxfn PlayStop(hLine=1, lPlayId=0(0x0), lParam1=0, lParam2=0, strParam1=, strParam2=)

100026.625 001 ocxfn LineDrop(sLineId=1, sOpt=0)

100026.641 001 ev TDX_SETHOOK (SetHook Completed)

100026.641 001 te LINE_CALLSTATE(1, 0x1, 0x1, 0x0, 0x0) LINE_CALLSTATE-LINECALLSTATE_IDLE

100026.641 ocxev DoFireDialogic(dwIdx=10, 1, 135, [TDX_SETHOOK], 0, 0, 0, [DX_ONHOOK], [], [])

100027.672 ocxfn RingsBeforeAnswer(lLineId=1, lRings=0, lParam1=0, strParam2=)

100951.906 001 ocxfn LineMakeCall(1, 0, 307, DX_PAMDOPTEN, 30, 0, 0, , )

 

Can you determine problem from this?

 

Thanks

[SupportTeam]

Please update to attached .EXE and capture the unsuccessful outgoing call again, then post both the vgm and tw traces here please.

VgMulti_6.0.2116.zip