Dialogic Ports Don't Initialize

[timc]

Hi,

We have had voiceguide running sucessfully in testing for a few weeks now, but had to reinstall Dialogic drivers in order to diagnose a problem which was related to the phone system. However after installing SR6.0 Dialogic drivers it seems that either Dialogic or VoiceGuide is not initializing the Dialogic ports on startup.

 

Dialogic D120JCT

Here's an account of how things are working currently;

 

1. System boots up

2. Dialogic Drivers are set to run at startup

3. Dialogic card initializes sucessfully

4. VoiceGuide is run at startup and starts sucessfully

5. A call is made to the first port on the Dialogic Card

6. The call is not answered until after 4-7 rings.

7. The is the same for all ports on the card.

8. I have plugged an analog phone into each of the lines and when a call is made the phone rings immediately.

 

Now here is the crazy part...

If I close VoiceGuide and run one of the Dialogic demo programs; eg ANSRMT

Setting it to answer on the first 4 ports, the call is answered immediately.

If I close the Dialogic demo program and restart VoiceGuide, the first 4 ports answer immediately and the others do not.

If I repeat the process for each of the 3 sets of 4 ports on the card the calls are answered immediately.

 

Its almost as if the Dialogic card need to initialize each of the ports before Voiceguide can recieve information from it.

 

Anyway I'm going live on Monday so any urgent help would be much appreciated. If Adam can contact me on the contact number he has that would also help greatly.

 

Thanks,

 

Tim Chapman

[SupportTeam]

Could you please post a copy of VoiceGuide's Trace Logs which captures the problem, this will allow us to see what happened.

 

Enable logging by setting the log levels to 10 in VG.INI as per below:

[Log]

ktTel=10

Then restart VoiceGuide and make a test call which demonstrates the problem.

 

Trace files will be created in VG's \log\ subdirectory.

 

Please post the traces.

 

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

[timc]

I have done some additional testing as follows;

 

1. As per the original problem, when the ports have been initialised by using the Dialogic demo program, stopping and restarting the Dialogic service does NOT recreate the issue, the ports appear to stay initialised until a complete server restart.

 

2. If the Dialogic service is set to start manually and is started manually once the server has restarted, followed by starting Voiceguide the problem does not happen.

 

3. However when the Dialogic service is set to start automatically along with VG on startup the problem occurs. Restarting VG and the Dialogic service does not fix this, only running a Dialogic sample program.

 

4. After a sample program is run "some" of the other ports on the card other than those initialised appear to be working.

 

When a call is made to a port that isnt working no VG logs appear, so it looks like VG is not being presented with the call.

 

I have attached logs that were created after the first 4 ports were initialised using the Dialogic demo program.

 

My thoughts are that possibly the Dialogic service is starting before a necessary service on startup therefore not completing whatever its initialisation routine is. Hence the reason it works when started manually.

 

Can you suggest a script to run at startup that might be a workaround for this.

 

Thanks!

tracelogs.zip

[SupportTeam]

Dialogic service is set to start automatically along with VG on startup the problem occurs.

Is VoiceGuide started as a service as well?

 

2. If the Dialogic service is set to start manually and is started manually once the server has restarted, followed by starting Voiceguide the problem does not happen.

What happens if the Dialogic service is set to start Automatically and after ensuring that it has started (use the Dialogic configuration Manger) then start VoiceGuide?

 

Can you suggest a script to run at startup that might be a workaround for this.

Just use a batch file that waits for a while before starting VoiceGuide.

 

Check out these links:

http://voiceguide.com/forums/index.php?showtopic=4067

http://voiceguide.com/forums/index.php?showtopic=3639

[timc]

To close off this thread, delaying the start of VoiceGuide for three minutes using one of the methods described by the support team appears to have resolved the issue. It looks like the Dialogic drivers / card are not in the correct state when Voiceguide starts up.

[SupportTeam]

Yes. The Dialoigc service does take a fair bit of time to start up. The more ports on system the longer the startup time.