Line 2 Always Initialising

[Guest Guest_hdouglas]

I have just upgraded to vg5.1 and at the same time taken the opportunity to perform a clean install of Operating system (w2k SP4) and dialogic card (D/4PCI with 5.1.1 software)

 

All tests seem to work fine and the scripts I am using also work, but only on line 1. Line 2 gives "Initialising..." in the state column and never moves on to "Waiting for a call..."

 

Line 1 and Line 2 both work with the Dialogic TAPI test program. Any ideas?

[SupportTeam]

Strange... can you try re-running the VoiceGuide Configuration Wizard?

 

in VG.INI please change LogToFile entry in [TraceLog] section to be:

 

[TraceLog]

LogToFile=1

 

 

the start VG again and post the trace created in VoiceGuide's \log\ subdirectory.

[eZigma]

Hi,

 

I am seeing the same problem....

 

We had the 5.0 working on our test server, and noticed that 5.1 had been released.

 

So figured rather that upgrade do a clean install of 5.1

 

Scenario:

 

Intel810e Motherboard, PIII500 with 512MB ram and 20GB drive

Clean Install of Win2k, Sp4, + All patches to date... 11-1-2003

Norton Antivirus Corp

Clean install of Dialogic Software release 5.1.1 + Sp1

4 Ports in use.

 

Proceeded to download and install VG5.1

 

Installed without any issues

 

Upon running the config wizard and launching VG, noticed that Port1 indicated that it was waiting for a call, but ports 2 to 4 were shown as initialising.

 

Clicked on ports 2 through 4 and clicked the hangup button and then the status changed to hanging up and then immediateley changed to waiting for a call..

 

Also tried to change the pickup after "x" rings from default of 2 to 1 and it changed Ok on port 1, but ports 2 through 4 did not...

 

Tried to change pick after "x" ring to 1ring on ports 2 through 4 a few times (3 times to be exact) before the changes took place.

 

Any ideas...

 

Did not even try to run a script... as there is no point if i have to manually initialise, then hang up before line is ready.

 

At this time i have resorted back to version 5.0

 

Please advise, i woul drather start with the latest it if will behave.

[SupportTeam]

Upon running the config wizard and launching VG, noticed that Port1 indicated that it was waiting for a call, but ports 2 to 4 were shown as initialising.

Did you try placing calls on those lines, to see if maybe it was just a display of line state problem and the lines were in fact answering calls OK?

Also tried to change the pickup after "x" rings from default of 2 to 1 and it changed Ok on port 1, but ports 2 through 4 did not...

So after you typed in "1" in the pickup after "x" rings box and then after changing focus to another line and returning back to the same line you saw a "2" there instead of "1" ? or did the "2" reappear there after restarting VG?

 

Which Dialogic card are you using?

 

Please place attached file in "C:\" and then run VG again and post the created file "c:\TapiWrapLogMMDD.txt" - we can then see better what is going on...

TapiWrapLogSelect.txt

[Guest Guest]

Using Dialogic 4PCI card...

 

"x" ring issue was both when making the changes and goign back to that port and also happens when making the changes and restarting VG...

 

In the end i did it via vg.ini file manually...

 

Also i have noticed that when there is an incoming call 2 ports answer eve though there is only on incoming call...

[SupportTeam]

"x" ring issue was both when making the changes and goign back to that port and also happens when making the changes and restarting VG...

In the end i did it via vg.ini file manually...

Sounds like the VG.INI file on your system cannot be edited - was it open for editing at the same time in other editor? Perhaps it's properties were changed to "Read-Only" ?

Not too sure how this could have occurred, can you try uninstalling VG and installing it a differently named directory?

Also i have noticed that when there is an incoming call 2 ports answer eve though there is only on incoming call...

I take it that there are two different lines plugged into those ports? - ie: it's not the same line just split apart into two cables?

 

Could you please send us a copy of VoiceGuide's Debug Printout which captures the problem, this will allow us to see what is going wrong.

 

(When running the script click on VoiceGuide's View menu and select 'Event Trace Log' option - any log information will then appear in this window. You must open the trace window before making the call.)

 

Also could you post the "C:\TapiWrapLogMMDD.txt" log file as mentioned in the previous post.

[hdouglas]

Following my original post I am still having the "Initialising..." problem on line 2 (only 2 lines in use on Dialogic D/4PCI card

 

Here is the contents of the VG Logfile (1103vgm)

The first line receives calls as normal, the second line will not answer when a call comes in.

 

104153.28 0 Tapi device 8 is: Analog Line 4(dxxxB1C4)

104153.28 0 Tapi device 7 is: Analog Line 3(dxxxB1C3)

104153.30 0 Tapi device 6 is: Analog Line 2(dxxxB1C2)

104153.30 0 Tapi device 5 is: Analog Line 1(dxxxB1C1)

104153.31 0 Tapi device 4 is: H323 Line

104153.31 0 Tapi device 3 is: IPCONF LINE

104153.33 0 Tapi device 2 is: LPT1T

104153.34 0 Tapi device 1 is: WAN Miniport (L2TP)

104153.34 0 Tapi device 0 is: RAS VPN Line 0

104153.39 0 Inband Signaling Config file not specified

104153.39 0 Loading VMB data begin

104153.39 0 Loading VMB data - about to delete old entries

104153.41 0 Loading VMB data - sorting/ordering

104153.41 0 Loading VMB data end

104153.45 5 Initialising...

104153.45 6 Initialising...

104153.47 0 Script Load C:\Hotline Scripts\amber_019.vgs

104153.50 0 Calling .lineOpen on device 1

104153.70 0 Calling .GetLineHandle on LineId 5

104153.70 5 hLine=65655

104153.70 0 Calling .GetProviderInfo on LineId 5

104153.75 5 Line 5 Provider: D41MT.TSP: Dialogic D41 Service Provider

104153.75 0 Calling lineSetNumRings on lLineHandle 65655

104153.77 5 Waiting for a call...

104236.52 5 linedevstate 2048 0 0

104236.55 5 callstate OFFERING 65604 0 4

104236.56 5 Answer the call at 03/11/2003 10:42:36

104236.56 5 lineAnswer(65604) => 65587

104236.56 5 callinfo CALLEDID

104236.58 5 callinfo ORIGIN

104236.58 5 ring 0

104237.14 5 callstate CONNECTED 65604,1,0

104237.14 5 WorkingModeTAPI@Connected=

104237.14 5 WorkingModeScript@Connected=

104237.16 5 Inband detection not enabled

104237.17 5 StartLoadedVgs at 03/11/2003 10:42:37

104237.19 5 tapi Reply (LineEvReply) ok 65587 0

104237.19 5 [welcome_message] Playing

104237.19 5 [welcome_message] Playing (C:\11Khz Lois\Welcome_message.wav)

104237.36 5 PlaySoundStart ok [C:\11Khz Lois\Welcome_message.wav]

104237.36 5 RunModule PLAY end

104251.69 0 sys cleanup Start

104251.69 0 sys cleanup End

104347.59 5 wb(22684300)

104348.67 5 Play End line[5] (id=226843)

104348.69 5 LsPlayMsg EV_PLAY_FINISHED

104348.69 5 LsPlayMsgFinished EV_TIMEOUT_GOTOMODULE

104348.69 5 [main_menu] Playing

104348.69 5 [main_menu] Playing (C:\11Khz Lois\Main_menu.wav)

104348.84 5 PlaySoundStart ok [C:\11Khz Lois\Main_menu.wav]

104348.84 5 RunModule PLAY end

104405.78 5 wb(29835900)

104406.86 5 Play End line[5] (id=298359)

104406.88 5 LsPlayMsg EV_PLAY_FINISHED

104410.05 5 LsPlayMsgFinished EV_TIMEOUT_REPLAYMSG

104410.05 5 [main_menu] Playing (C:\11Khz Lois\Main_menu.wav)

104410.14 5 PlaySoundStart ok [C:\11Khz Lois\Main_menu.wav]

104427.06 5 wb(31970300)

104428.14 5 Play End line[5] (id=319703)

104428.14 5 LsPlayMsg EV_PLAY_FINISHED

104431.31 5 LsPlayMsgFinished EV_TIMEOUT_REPLAYMSG

104431.31 5 [main_menu] Playing (C:\11Khz Lois\Main_menu.wav)

104431.42 5 PlaySoundStart ok [C:\11Khz Lois\Main_menu.wav]

104448.27 5 wb(34096800)

104449.36 5 Play End line[5] (id=340968)

104449.36 5 LsPlayMsg EV_PLAY_FINISHED

104452.53 5 LsPlayMsgFinished EV_TIMEOUT_REPLAYMSG

104452.53 5 [main_menu] Playing (C:\11Khz Lois\Main_menu.wav)

104452.64 5 PlaySoundStart ok [C:\11Khz Lois\Main_menu.wav]

104509.53 5 wb(36218700)

104510.61 5 Play End line[5] (id=362187)

104510.61 5 LsPlayMsg EV_PLAY_FINISHED

104521.45 5 LsPlayMsgFinished EV_TIMEOUT_HANGUP

104521.45 5 Hanging up call...

104521.47 5 RecSoundStop ok

104521.47 5 PlaySoundStop ok

104521.48 5 fnHangupCall end

104521.53 5 linedevstate 2048 0 0

104521.55 5 callstate IDLE 65604 0 0

104521.55 5 WorkingMode@Idle=

104521.58 5 tapi Reply (LineEvReply) ok 65570 0

104522.59 5 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE

104522.59 5 ReinitTelephony due to IDLE start

104522.59 5 tapic lineDeallocateCall(MainCall:65604) 0

104522.83 5 lineOpen(5) => 0

104522.83 5 Waiting for a call...

104522.83 5 lineOpen(5)LineHandle=65553

 

Also attached is the TAPI log file

 

This problem is with VG5.1 I too am having issues with not being able to set the number of rings (which I need to be 0) for line 2 (line 1 is OK)

TapiWrapLog.txt

[SupportTeam]

The TapiWrapLog file shows that the old version of TAPIWRAP.OCX in still installed on your system.

 

In trace we can see:

 

TAPIWrap OCX v1.35.0, Jul 31 2003 23:05:39 [ForDialogic]

 

and it should be:

 

TAPIWrap OCX v1.51.0, Oct 31 2003 18:34:43 [For Dialogic Analog]

 

Not too sure why the installation routine did not update that OCX - can you please uninstall VG - delete TAPIWRAP.OCX manually if it is still in Windows's System32 directory, and then run VG Install again (selecting the Dialogic-Analog option during install).

 

Correct OCX is attached below...

TapiWrap.zip

[SupportTeam]

After re-installing v5.1 and checking that the right OCX is installed in Windows' System32 directory please place the attached file in VoiceGuide's directory (replacing the original file).

 

Attached copy of VGMULTI.EXE has extra debugging in the initialization routines which will show more info in the traces.

 

If you are still having problems please post both traces again...

VgMulti.zip

[SupportTeam]

Just found out that v5.1 install is actually first installing an older version of the OCX - then overwriting it with the correct version afterwards (depending on what install type was selected...)

 

It's possible that this overwriting is not working for some reason on some systems and that is why the old version of the OCX winds up in the System32 directory.

 

A new install was created (called v5.1a) which will just install the correct OCX in the first place. It is now available for download from our WWW.

 

Please just uninstall v5.1 and install v5.1a. v5.1a install has the VGMULTI.EXE that has extra debugging in the initialization routines...

 

 

We are still puzzled by the inability to set the "pick after "x" ring" value - we are not able to replicate the problem at all on any of the test systems...

[hdouglas]

Thanks, now sorted. I re-installed v5.1 and this put an older tapiwrap file in system32 (1 Aug 2003 00:05:44) Replacing this manually seems to have resolved the problem.

 

Incidentally, I think I have an answer on the rings before answer not updating. The screen that this is set on does not have any button to confirm changes or write changes, therefore these changes are only written if you tab out of the field. If you are changing more than one line the tendancy is to select line 1, show options, change the ring field and rather than tab out, use the mouse to select next line. This operation will not change the field

 

Hope this helps, Thanks for the quick response.

 

Final observation which would be useful, since there is a significant time difference between you and a number of users, myself included who are UK based, is there a way of showing the current time on this forum? It would help knowing when to expect to look for a response.

[SupportTeam]

If you are changing more than one line the tendancy is to select line 1, show options, change the ring field and rather than tab out, use the mouse to select next line. This operation will not change the field

It should... when a line is selected using the mouse then the description of the Line Device Config frame should change to the name of selected line and the correct settings for that line displayed...

Dees the frame title change for you when you select different lines with a mouse?

 

The new "Rings before answering" setting is set as soon as the text box where you enter the number loses focus... The method that you describe above works on our systems, and we're a bit surprised that it does not work on your system. What version of Windows are you using?

It would help knowing when to expect to look for a response.

You can subscribe to the thread (click on "Track this topic") then emails are sent as soon as an answer is posted...

[hdouglas]

Have tried changing the rings before answer again and it definately does not update unless you exit from the field using tab, changing focus using the mouse does not work if the mouse click is to select a different line (ie in the panel above) if you use the mouse to click/unclick the Allow voiceguide to dialout, it will update.

 

Version of windows is W2000 Professional version 5.0 (build 2195 service pack 4)

 

Let me know if you need further info.