Delay In The Starting Of Voiceguide

[pedgarhi]

Hello,

 

I have just upgraded my system to VoiceGuide for Dialogic 6.0.2384 and I have noticed that it spends much more time in the starting than the previous version.

 

In the trace shown below, there is a gap of 32 seconds after "Inband Signaling Config file not specified". Why? Is there any way to reduce this time?

 

160608,00 0 ---------------------------------------------------

160608,00 0 VoiceGuide for Dialogic

160609,02 0 v6.0.2384

160609,02 0 ---------------------------------------------------

160609,02 0 rv global loaded >>><<<

160609,02 0 cti Inband Signaling Config file not specified

160641,33 0 init ApiMode=[DialogicGC]

160641,56 0 vm loading VMB data begin

160641,56 0 vm loading VMB data - about to delete old entries

160641,58 0 vm loading VMB data - sorting/ordering

160641,58 0 vm loading VMB data end

 

Thanks.

[Guest RobG]

I too am using V6.0.2384. Here is a snip from this morning's time:

 

094107.64 0 VoiceGuide for Dialogic

094107.66 0 v6.0.2384

094107.66 0 ---------------------------------------------------

094107.67 0 rv global loaded >>><<<

094107.69 0 cti Inband Signaling Config file not specified

094108.80 0 init ApiMode=[DialogicGC]

094109.05 0 vm loading VMB data begin

094109.06 0 vm loading VMB data - about to delete old entries

094109.19 0 vm loading VMB data - sorting/ordering

094109.19 0 vm loading VMB data end

 

 

Sorry I can't help you with your situation, but maybe the additional data of seeing v6.0.2384 on my system is useful to you. I suppose you have already thought about how consistent the delay is for you and what affect other system activities might be having on your time. My system gets slowed by heavy disk activity at times.

[Harry L. Roberts]

Were you upgrading from version 5 to Dialogic or just upgrading your Dialogic version to a more recent Dialogic Version?

 

I noticed a huge difference in load time between version 5 and the dialogic version.

 

The version 5 would load almost immediately but the Dialogic version takes much longer. Guessing I would say at least 30 seconds maybe much longer.

 

I just stopped and restarted my VG Dialogic version and it took roughly 40 seconds for it to get ready to answer a call.

 

Here is a partial log file from the restart. The log file I used was 0131tw.txt

 

130101.531 ocxfn LogLevels 5,C:\Program Files\VoiceGuide\log\,tw.txt,0,

130101.609 ocxfn LogLevels 5,C:\Program Files\VoiceGuide\log\,tw.txt,0,

 

<<<<<<<<<<<<<SNIP>>>>>>>>>>>>>

<<<<<<<<<<<<<SNIP>>>>>>>>>>>>>

 

130101.937 dlgc dx_setparm(1, DXBD_FLASHTM, &[10]) => 0, err=0, No error

130109.937 dlgc dx_setparm(1, DXBD_MFDELAY, &[6]) => -1, err=3, I/O function timeout

130117.937 dlgc dx_setparm(1, DXBD_MFLKPTONE, &[10]) => -1, err=3, I/O function timeout

130125.937 dlgc dx_setparm(1, DXBD_MFMINON, &[0]) => -1, err=3, I/O function timeout

130133.937 dlgc dx_setparm(1, DXBD_MFTONE, &[6]) => -1, err=3, I/O function timeout

130133.937 dlgc dx_setparm(1, DXBD_MINLCOFF, &[50]) => 0, err=3, I/O function timeout

 

<<<<<<<<<<<<<<SNIP>>>>>>>>>>>>

<<<<<<<<<<<<<<SNIP>>>>>>>>>>>>

 

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

130137.734 ocxfn RingsBeforeAnswer(lLineId=2, lRings=0, lParam1=0, strParam2=)

130137.953 ocxfn RingsBeforeAnswer(lLineId=3, lRings=0, lParam1=0, strParam2=)

130138.187 ocxfn RingsBeforeAnswer(lLineId=4, lRings=0, lParam1=0, strParam2=)

 

 

As you can see it started at 130101.531 and finished at 130138.187. If I did the math correctly that is 36.656 seconds.

 

I've attached the complete start log to this message.

0131tw_Log_File_Partial.zip

[Guest RobG]

I think I may be doomed for longer loads too. Maybe mine loads so fast right now because some of the Dialer functionality is missing!

 

Anyway, I checked today's time-to-get-ready... 4.38 seconds. And picked another random date, 1/24/06, that showed a startup time of 2.39 seconds.

 

The log I posted earlier today (Dialer Not Dialing Yet.) shows typical log entries. Mine just does not show all the activity that yours does, Harry. Beats me why. My gray matter is elsewhere.

[SupportTeam]

VG for Dialogic does an exhaustive check of Dialogic cards & their channels when it starts up. If you're using a T1 or E1 line then this will take some time.

 

In the next release this check will only be made if log level is set to 10 - so setting log level to 9 should result in quick start-ups.

[Guest RobG]

I remember sensing those snide thoughts when I claimed that setting Logging at level 10 actually caused VG to do more

 

It must have been my future sense working overtime!

[pedgarhi]

I was upgrading from a previous version of VG for Dialogic to a more recent one. With the previous version, the time to get ready was a few seconds but with the new version it is always more than 30 seconds.

 

I'm working with analog lines, not T1 or E1, and in both cases the disk usage is the same.

[SupportTeam]

Could you please post a copy of VoiceGuide's Debug Printout which captures the startup phase, this will allow us to see what is happening.

 

When running the script click on VoiceGuide's View menu and select 'Event Trace Log' option - then set logging level to 9 (or 10).

 

When posting traces/scripts please .ZIP them up and post them as attachements.

[pedgarhi]

Here you are.

 

I think the delay is caused by the initialisation of the ktTelControl.ocx when reading from Config.xml (see tw log file).

startup.zip

[SupportTeam]

Which Dialogic card are you using?

 

Which System Release drivers are you using?

 

Trace shows that a lot of time is spent waiting for the card to set some parameters (you can see "I/O function timeout" in the MMDDtw.txt trace) We've seen this reported before on some other systems. The delays are resolved by removing the parameters with which the Dialogic card is having problems from the config.xml file.

 

Edit your config.xml file and remove the <SetParam> sections for these settings:

 

DXBD_MFDELAY

DXBD_MFLKPTONE

DXBD_MFMINON

DXBD_MFTONE

 

The future releases of VG for Dialogic will have these settings commented out in Config.xml

[pedgarhi]

I'm using a D/4PCIU card with System Release 5.1.1 SP1 and a Point Release for D/4PCIU.

 

I removed from Config.xml the settings you indicated and now it starts much faster. Thanks for your help.