Setting Tapi Control In The Vg.ini

[ktruk]

Hi there.

 

I wish to set "TAPI" function calls in the VG.INI so that TAPI functions are used to request line transfers to a TAPI compatible driver.

 

I have set the Vg.INI params:

 

;"TAPI"    : TAPI functions calls are made to driver to action transfers and conferences.

;"Generate" : exlilicit tones and signals are generated using TAPI calls

;"AT"      : modem AT commands are used

TransferControl_Modem=TAPI

TransferControl_TelBoards=TAPI

 

...but the transfer fails and the VG debug log still shows the transfer method as "Generate" and a couple of errors.

 

133812.25  10 timer clear

133812.26  10 timer set 0.4  EV_TIMEOUT_READYTOBEGINTRANSFER

133812.58  10 timer fired EV_TIMEOUT_READYTOBEGINTRANSFER

133812.58  10 ScriptEventCode 9012 iLineState=1900

133812.58  10 LsXferStart EV_TIMEOUT_READYTOBEGINTRANSFER

133812.58  10 timer set 5  EV_TIMEOUT_ANNOUNCED_TRANSFER_ATTEMPT_TOOK_TOO_LONG

133812.58  10 [TransferCall] Blind Transfer to 30 (Generate)

133812.59  10 tapic lineGenerateDigits(66235 [!] 100) => -2147483576:LINEERR_OPERATIONFAILED [80000048]

133812.59  10 rv    lg add [Hangup Time]{29/11/2005 13:38:12}

133812.59  10 Hanging up call... [lineGenerateDigits ret=-2147483576]

133812.59  10 RecSoundStop ok

133812.59  10 PlaySoundStop err=0

133812.60  10 timer set 2  EV_TIMEOUT_WAITFORIDLEAFTERLINEDROP

133812.61  10 fnHangupCall end

133812.97  10 tapi  Reply (LineEvReply) ok 66184 0

133812.97  10 callstate IDLE 66235 0 0

133812.98  10 WorkingMode@Idle=

133812.99  10 timer clear

133813.00  10 timer set 1  EV_TIMEOUT_TIMETOREINITLINE

133813.00  10 linedevstate 2048 0 0

133813.01  10 linedevstate 1 0 0

133813.91  10 timer fired EV_TIMEOUT_TIMETOREINITLINE

133813.91  10 ScriptEventCode 9008 iLineState=900

133813.92  10 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE

133813.92  10      ReinitTelephony due to IDLE

133813.93  10 tapic lineDeallocateCall(MainCall:66235) 0

133813.95  10 lineOpen(10)=>

133813.95  10 Waiting for a call...

133813.96  10 LineHandle=66167

133813.97  10 amchk set AMdet=False in Reinit@idle

133813.98  10 timer set 3  EV_TIMEOUT_ATERIDLE_ALLOWOUT

133814.95  0 dial  start any summary:|10:rdy=0|11:idx=0|

133816.98  10 timer fired EV_TIMEOUT_ATERIDLE_ALLOWOUT

133816.98  10 ScriptEventCode 9013 iLineState=900

133818.33  0 dial  start any summary:|10:idx=0|11:idx=0|

 

I have tried restarting the machine and VG and such-like, but the transfer method indicated in the debug log still shows "Generate".

 

I am using v5.2.5003.

 

Can you please help.

 

Thanks.

 

PS: Any news on this thread? http://voiceguide.com/forums/index.php?showtopic=3409

[ktruk]

Is the abve information enough to see whats going on here or do you need anything else?

 

If I can force VoiceGuide to use TAPI for call transfers then I am sure that my problems will be solved!

 

Thank you.

[SupportTeam]

Looks like the TAPI driver for the device which you are using returned an error when the TAPI function was called to generate a hookflash.

 

As to why it gave an error you can only really ask that question from the TAPI driver provider...

[ktruk]

No, I think you have missed the point: I don't want to "generate" a hook-flash, as I am trying to make a TAPI request to transfer a call (I'm using a BRI ISDN board). To do this, I want to set VG to work in TAPI mode, by making the setting quoted above for VG to use TAPI. Since the log shows a "generate" call being made it appears that VG (thats your product) is not making the call in TAPI mode.

 

I know its being ignored - because if I install ComISDN, then VG appears to switch to a TAPI mode AND CALL TRANSFERS WORK, but when trying to make a call transfer without ComISDN to a TAPI driver, the call transfer fails as listed above.

 

I know the TAPI driver works because I have tried it with other TAPI compatible systems which do a call transfer. Therefore, VG is not working in TAPI mode and not doing the call transfer using TAPI mode!

 

Attached is a zip file containing 2 sets of debug logging files. The one set marked as "VG-Gen1" show the call transfer failing as per my original post. The second set marked "Vg-Tap1" shows VG operating in TAPI mode and successfully making the call transfer. The logs were generated by starting VG, making one call, attempting a call-transfer, and hanging up, then stopping VG. The script is also included.

 

Highlighted below is the section showing a VG working in TAPI mode:

112519.71  8 timer clear

112519.71  8 timer set 0.4  EV_TIMEOUT_READYTOBEGINTRANSFER

112520.04  8 timer fired EV_TIMEOUT_READYTOBEGINTRANSFER

112520.04  8 ScriptEventCode 9012 iLineState=1900

112520.04  8 LsXferStart EV_TIMEOUT_READYTOBEGINTRANSFER

112520.04  8 timer set 5  EV_TIMEOUT_ANNOUNCED_TRANSFER_ATTEMPT_TOOK_TOO_LONG

112520.04  8 [TransferCall] Blind Transfer to 30 (TAPI)

112520.04  8 lineBlindTransfer(66406,30,0) in LsXferStart => 66372

112520.21  8 callstate ONHOLD 66406 0 0

112520.53  8 callinfo DEVSPECIFIC

112520.54  8 callstate DISCONNECTED 66406 1 0

112520.54  8 ScriptEventCode 9250 iLineState=1900

112520.54  8 LsXferStart EV_REMOTEPARTY_DISCONNECT

112520.54  8 rv    lg add [Hangup Time]{30/11/2005 11:25:20}

112520.54  8 Hanging up call...

112520.54  8 RecSoundStop ok

112520.54  8 PlaySoundStop err=0

112520.54  8 timer set 2  EV_TIMEOUT_WAITFORIDLEAFTERLINEDROP

112520.55  8 fnHangupCall end

112520.56  8 tapi  Reply (LineEvReply) ok 66355 0

112520.65  8 callstate IDLE 66406 0 0

112520.65  8 WorkingMode@Idle=

112520.66  8 timer clear

112520.68  8 timer set 1  EV_TIMEOUT_TIMETOREINITLINE

112521.65  8 timer fired EV_TIMEOUT_TIMETOREINITLINE

112521.65  8 ScriptEventCode 9008 iLineState=900

112521.65  8 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE

112521.65  8      ReinitTelephony due to IDLE

112521.65  8 tapic lineDeallocateCall(MainCall:66406) 0

112521.67  8 lineOpen(8)=>

112521.67  8 Waiting for a call...

112521.67  8 LineHandle=66338

112521.67  8 amchk set AMdet=False in Reinit@idle

112521.67  8 timer set 3  EV_TIMEOUT_ATERIDLE_ALLOWOUT

112522.17  0 dial  start any summary:|8:rdy=0|9:idx=0|

112524.67  8 timer fired EV_TIMEOUT_ATERIDLE_ALLOWOUT

112524.67  8 ScriptEventCode 9013 iLineState=900

112525.19  0 dial  start any summary:|8:idx=0|9:idx=0|

 

Also noted in the startup process:

112354.12  0      ------------------------------------------------------------------------------

112354.12  0      VoiceGuide TAPI v5.2.5003

112354.12  0      ------------------------------------------------------------------------------

112354.88  0      ApiMode=[TAPI]

 

If I inspect the two log files together, then there are two main differences:

 

1. When ComISDN is used, when VG starts/initialises it sets a "Provider Type" which is set to "PROVTYPE_ComISDN" and the system appears to work in TAPI mode. However when ComISDN is not used, no Provider Type is set.

 

2. When ComISDN is NOT used, some "LineDevState" variables are listed in the debug list.

 

To wrap up: I am getting really frustrated with this and your support is not meeting my needs. I am months behind on my VG project and I am feeling really let down at the moment. Clearly, I have an issue with VG and would like you to deal with these specific points.

ktruk.zip

[SupportTeam]

A note to other readers of this thread:

 

A working soultion was found using an Eicon card with slight modifications to VG.

In recieved email ktruk wrote:

Thank you so much for the VG.EXE update (v5.2.5015) - YES - it works!!

 

I will do more testing during the course of the day. If I find anything

unusual, I will let you know.

 

This fix will enable a range of Eicon ISDN cards (BRI & PRI) to work with

VG without ComISDN.

Although only v2 cards are "officially supported" my testing shows that V1

cards work too, but you have to copy over the v7.x Diva Wave driver to the

v6.x installation.

(copy divawave.drv to windows\system32).

 

The problem with ComISDN (both their dialogic & capi versions) is that

they do not work with Hunt-groups very well. The problem is that if a line

is hunted to, and found busy, but then becomes free before a new line has

answered (ie: during the hunt), the call connects to a free line, but the

DSP/wave driver connects to the previously busy channel and nothing can be

heard on the connected line. The Eicon drivers do not suffer from this,

any free line will answer any call at any time. The comISDN system will

only properley answer in strict channel sequence, which cannot be truly

enforced.

 

Here is the debug trace, in case it is any use to you...

 

111858.86  14 timer clear

111858.87  14 timer set 0.4  EV_TIMEOUT_READYTOBEGINTRANSFER

111859.26  14 timer fired EV_TIMEOUT_READYTOBEGINTRANSFER

111859.26  14 ScriptEventCode 9012 iLineState=1900

111859.27  14 LsXferStart EV_TIMEOUT_READYTOBEGINTRANSFER

111859.28  14 timer set 5

EV_TIMEOUT_ANNOUNCED_TRANSFER_ATTEMPT_TOOK_TOO_LONG

>>111859.29  14 state [TransferCall] Blind Transfer to 30 (TAPI)

>>111859.30  14 lineBlindTransfer(65706,30,0) in LsXferStart => 65672

111859.47  14 devstate NUMCALLS 0 0

111859.48  14 devstate OTHER 0 0

111900.35  14 tapi  callstate start

111900.36  14 tapi  callstate DISCONNECTED 65706 1 0

111900.36  14 ScriptEventCode 9250 iLineState=1900

111900.37  14 LsXferStart EV_REMOTEPARTY_DISCONNECT

111900.38  14 rv    lg add [Hangup Time]{06/12/2005 11:19:00}

111900.39  14 state Hanging up call...

111900.40  14 RecSoundStop ok

111900.41  14 PlaySoundStop err=0

111900.42  14 timer set 2  EV_TIMEOUT_WAITFORIDLEAFTERLINEDROP

111900.43  14 fnHangupCall end

111900.44  14 devstate NUMCALLS 0 0

111900.45  14 devstate OTHER 0 0

111900.46  14 tapi  callstate start

111900.47  14 tapi  callstate IDLE 65706 0 0

111900.48  14 WorkingMode@Idle=

111900.48  14 timer clear

111900.49  14 timer set 1  EV_TIMEOUT_TIMETOREINITLINE

[ktruk]

See this update for issues with v1 and v2 Eicon Diva Server Cards:

 

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