How To Use The Ctitapi_pbxdevice In Vg.ini

[ktruk]

Hi, I have a CTI enabled PABX (German - Elmeg ICT880, see www.elmeg.com) with its CTI driver installed on its connected PC, giving a number of TAPI devices (visible in the VG config program as TAPI devices).

 

The only mention of this functionality is an answer given to someone using a Panasonic PABX exchange, see: http://voiceguide.com/forums/index.php?showtopic=3332

 

Can you please explain how this CTI interface can be used, from the post above, it appears that DNIS can be obtained for an IVR extention, without the extention supporting DNIS, is this correct?

 

So, for example, does this mean that an analog extention can be connected, say at ext 101, but the CLIP/DNIS obtained via the PABX idependently?

 

I guess that no wav playback/record is available (since no wave driver is installed for the PABX device) but what about other functions, perhaps call transfer, are these available?

 

Any clues to the above appreciated - thanks.

[SupportTeam]

So, for example, does this mean that an analog extention can be connected, say at ext 101, but the CLIP/DNIS obtained via the PABX idependently?

Yes, if the PBX supports this.

Try it, and see it if will work with your PBX.

 

The PBXs TAPI device line name just needs to be specified in the VG.INI file, using the ctiTapi_PbxDeviceName field in order for VoiceGuide to retrieve CallerID and DNIS information from it, and make that information accessible within the script.

 

Here is an example:

 

[TapiDevice1]

Id=10

Name=Analog Line 1(dxxxB1C1)

Script=C:\VgScripts\Internet Portal\Internet Portal.vgs

RingsBeforeAnswer=0

PopupCallerId=0

DialoutOK=1

ctiTapi_PbxDeviceName=EXT2001

 

Where EXT2001 is the PBX's name for the line plugged into the corresponding port on the telephony card.

 

Only receiving of call-related information is supported. You would not be able to do call transfers using that PBX TAPI device.

If the PBX supports call transfers through it's TAPI devices then it would be possible to write an extension to VG to let VG call the transfer functions through the PBX directly, but this would be a chargeable extension - contact sales@voiceguide.com to get a quote on getting such work done.

[ktruk]

Okay, I have checked out the CTI interface but didn't get the CLIP/DNIS info. This is what I found out:

 

After installing the PABX CTI driver/TSP, I get a number of additional TAPI devices.

 

 

If I run the VG line config program, I get the new devices listed in the tapi device pick-list.

 

If I run the dialogic Talker32 tapi program, I can see the devices, I can place a call from one extention to another (ie: the tapi call transfer or possibly the confereance method works). If I use the program to check out the device capabilities I get:

 

GETDEVCAPS

dwPermanentLineID = 655366,

dwAddressModes = 1,

dwGenerateToneModes = 0

dwMonitorDigitModes = 0,

dwMediaModes = 4,

dwMaxRate = 0

Line name = PABX Ext. 40

Provider info =

Wave/In ID = 65535, Wave/Out ID = 65535

GETDEVSTATUS

Total calls = 0,

dwNumOpens = 1,

dwOpenMediaModes = 4,

dwNumActiveCalls = 0

dwNumOnHoldCalls = 0,

dwNumOnHoldPendCalls = 0,

dwLineFeatures = 204

, dwDevStatusFlags = INSERVICE

I added the device names to the VG.INI like this:

[TapiDevice1]

Id=7

Name=Analog Line 1(dxxxB1C1)

Script=C:\VgScripts\Internet Portal\Internet Portal.vgs

RingsBeforeAnswer=0

PopupCallerId=0

DialoutOK=1

ctiTapi_PbxDeviceName=PABX Ext. 40

 

The device numbers are listed by VG when the program starts in the LOG files as it counts thru the devices from the last down to the first and sets up the lines:

231713.983 tapic lineNegotiateAPIVersion(0x800003ff, 12, 0x10003, 0x20001, 0x3727670, 0x12c6b4)

231713.983      dwTapiVersionToUse=0x10004, eidExtID=0x0

231713.983 tapic lineGetDevCaps(0x800003ff, 12, 0x10004, 0, 0x3734868) call

231713.983 tapic lineGetDevCaps(0x800003ff, 12, 0x10004, 0, 0x3734868) => NO_ERROR (0)

231713.983 tapic lineGetIcon(12, 0, 0x3727678)

231713.983 tapic lineNegotiateAPIVersion(0x800003ff, 13, 0x10003, 0x20001, 0x3734878, 0x12c6b4)

231713.983      dwTapiVersionToUse=0x10004, eidExtID=0x0

231713.983 tapic lineGetDevCaps(0x800003ff, 13, 0x10004, 0, 0x3741a70) call

231713.983 tapic lineGetDevCaps(0x800003ff, 13, 0x10004, 0, 0x3741a70) => NO_ERROR (0)

231713.983 tapic lineGetIcon(13, 0, 0x3734880)

231713.983 tapic lineNegotiateAPIVersion(0x800003ff, 14, 0x10003, 0x20001, 0x3741a80, 0x12c6b4)

231713.983      dwTapiVersionToUse=0x10004, eidExtID=0x0

231713.983 tapic lineGetDevCaps(0x800003ff, 14, 0x10004, 0, 0x374ec78) call

231713.983 tapic lineGetDevCaps(0x800003ff, 14, 0x10004, 0, 0x374ec78) => NO_ERROR (0)

231713.983 tapic lineGetIcon(14, 0, 0x3741a88)

231713.983 tapic lineNegotiateAPIVersion(0x800003ff, 15, 0x10003, 0x20001, 0x374ec88, 0x12c6b4)

231713.983      dwTapiVersionToUse=0x10004, eidExtID=0x0

231713.983 tapic lineGetDevCaps(0x800003ff, 15, 0x10004, 0, 0x375be80) call

231713.983 tapic lineGetDevCaps(0x800003ff, 15, 0x10004, 0, 0x375be80) => NO_ERROR (0)

231713.983 tapic lineGetIcon(15, 0, 0x374ec90)

 

TAPI Device 12,13,14,15 are the PABX devices.

 

also:

 

231713.91  0 init  InitClear start

231713.92  0      -----------------------------------------

231713.92  0      VoiceGuide TAPI v5.2.5015

231713.92  0      -----------------------------------------

231713.98  0      ApiMode=[TAPI]

231713.00  0 tapi  device 15 is: PABX Ext. 20

231713.00  0 tapi  device 14 is: PABX Ext. 10

231713.00  0 tapi  device 13 is: PABX Ext. 41

231713.00  0 tapi  device 12 is: PABX Ext. 40

231713.00  0 tapi  device 11 is: elmeg C3x0

231714.02  0 tapi  device 10 is: Analog Line 4(dxxxB1C4)

231714.03  0 tapi  device 9 is: Analog Line 3(dxxxB1C3)

231714.03  0 tapi  device 8 is: Analog Line 2(dxxxB1C2)

231714.05  0 tapi  device 7 is: Analog Line 1(dxxxB1C1)

231714.05  0 tapi  device 6 is: H323 Line

231714.05  0 tapi  device 5 is: IPCONF LINE

231714.05  0 tapi  device 4 is: LPT1T

231714.05  0 tapi  device 3 is: WAN Miniport (L2TP)

231714.05  0 tapi  device 2 is: RAS VPN Line 0

231714.05  0 tapi  device 1 is: RAS PPPoE Line0000

231714.05  0 tapi  device 0 is: Intel® 536EP Modem

231715.52  0 init  vgmulti ver 5.2.5015

231715.55  0      Inband Signaling Config file not specified

231715.56  0 vm    loading VMB data begin

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

231715.56  0 vm    sort start on 8 entries.

231715.56  0 vm    sort end.

231715.56  0 vm    loading VMB data end

231715.59  0 init  temp dir exists [C:\Program Files\VoiceGuide\temp\]

231715.59  0 init  clear settings on 4 devices.

231715.61  7 state Initializing...

231715.61  8 state Initializing...

231715.61  9 state Initializing...

231715.61  10 state Initializing...

231715.61  0 init  attach vgs on 4 devices.

231715.61  0      script load C:\Program Files\VoiceGuide\Scripts\Internet Portal\Internet Portal.vgs

231715.63  0 init  lineopen on 4 devices.

231715.63  0 init  calling .lineOpen on device 1

231716.27  7      lineOpen(7)=>

231716.27  7      hLine=66033

231716.27  7 tapi  ProviderInfo: D41MT.TSP: Dialogic D41 Service Provider

231716.27  7      set provider type: PROVTYPE_DIALOGIC

231716.27  7 state Waiting for a call...

231716.27  7 ERROR 5.2.5015 DialogicScUnroute => Non-Dialogic version of TapiWrap.ocx

231716.27  0 init  calling .lineOpen on device 2

231716.33  8      lineOpen(8)=>

231716.33  8      hLine=66050

231716.33  8 tapi  ProviderInfo: D41MT.TSP: Dialogic D41 Service Provider

231716.33  8      set provider type: PROVTYPE_DIALOGIC

231716.33  8 state Waiting for a call...

231716.33  8 ERROR 5.2.5015 DialogicScUnroute => Non-Dialogic version of TapiWrap.ocx

231716.33  0 init  calling .lineOpen on device 3

231716.36  9      lineOpen(9)=>

231716.36  9      hLine=66016

231716.38  9 tapi  ProviderInfo: D41MT.TSP: Dialogic D41 Service Provider

231716.38  9      set provider type: PROVTYPE_DIALOGIC

231716.38  9 state Waiting for a call...

231716.38  9 ERROR 5.2.5015 DialogicScUnroute => Non-Dialogic version of TapiWrap.ocx

231716.38  0 init  calling .lineOpen on device 4

231716.41  10      lineOpen(10)=>

231716.41  10      hLine=65896

231716.42  10 tapi  ProviderInfo: D41MT.TSP: Dialogic D41 Service Provider

231716.42  10      set provider type: PROVTYPE_DIALOGIC

231716.42  10 state Waiting for a call...

231716.42  10 ERROR 5.2.5015 DialogicScUnroute => Non-Dialogic version of TapiWrap.ocx

231716.61  0 dial  start any summary:|7:idx=0|8:idx=0|9:idx=0|10:idx=0|

 

see attached log file for full details...

 

 

ALL THIS - But no CLIP/DNIS is reported on the lines!!!

 

However, when I connect Digital lines to a digital line, my PABX does report CLIP and DNIS, so I am sure that the PABX is obtaining this info, and should be making it available via tapi.

 

So: questions:

Can you tell from the device capabilities if the devices support the required functions?

Can you tell me what this error means?: "ERROR 5.2.5015 DialogicScUnroute => Non-Dialogic version of TapiWrap.ocx" (only just noticed it)

 

I can send you the PABX CTI Log files if these could help provide any futher insight!

logs_0119.zip

[ktruk]

Update to the above: I wondered if the device name "PABX Ext. 40" might be invalid, either because it has spaces in the name or the full-stop/period char?

 

I tried finding a way to rename the devices - without any luck !

 

Also tried quoting the string in the VG.INI ie:

 

[TapiDevice1]

Id=7

Name=Analog Line 1(dxxxB1C1)

Script=C:\VgScripts\Internet Portal\Internet Portal.vgs

RingsBeforeAnswer=0

PopupCallerId=0

DialoutOK=1

ctiTapi_PbxDeviceName="PABX Ext. 40"

 

none of the above made any difference.

[SupportTeam]

After installing the PABX CTI driver/TSP, I get a number of additional TAPI devices.

Good.

However, when I connect Digital lines to a digital line, my PABX does report CLIP and DNIS,

Probalby sent as part of the ISDN's setup message...

so I am sure that the PABX is obtaining this info, and should be making it available via tapi.

It could... as whether it does or not we're about to find out...

Can you tell me what this error means?: "ERROR 5.2.5015 DialogicScUnroute => Non-Dialogic version of TapiWrap.ocx" (only just noticed it)

Not an error - just an informational message.

 

Please place attached .exe in your VG directory - it has some more debugging in the relevant area.

use:

 

ctiTapi_PbxDeviceName=PABX Ext. 40

VgMulti5.2.5027.zip

[ktruk]

It works - After adding this VGMulti.exe and running it, I DO get Caller Number and DNIS figures, when answering calls with my analog Dialogic D4PCI card.

 

If you want logs for the test I ran, I can attach them, but as all is okay, perhaps you don't need them.

 

Is this exe backwards compatible with 5.2.5015 (which includes a TAPI modification I asked for previously) ?

 

Thanks - Tim.

[SupportTeam]

Have you tried doing the call transfers using v5.2.5027?

[ktruk]

Sorry, no, not yet. I didn't realise any changes had been done with respect to call transfers. These tests to get CTI/PABX caller-id and DNIS are using an analog card, so, if need be, I can get DNIS and do dialogic/generate transfers instead. I take it then that there is some new code here to support my earlier request about call transfers? I will do the tests on a digital card (hopefully today) and get back to you.

 

Thanks - Tim.

[ktruk]

Call transfers using version 5.2.5027 are unchanged using the version posted above. I shall post a new thread to cover this.

[ktruk]

Just a quick note for information only about getting PBX callerID information using this Ctiapi_pbxDevice method:

 

It appears that if you get this callerID (CLIP/DNIS) info via the PBX it will be ignored if VG detects CLIP on the connected analog extention. Typically, the CLIP on the connected line overrides the CLIP from the PBX if its available, and the PBX DNIS data is ignored, so you get the fixed DNIS string (typically "0000") as set by the Dialogic TSP driver. So, if you need real DNIS and CLIP, you may need to disable any local CLIP on the connected line first (if you can).

 

As I said, just an FYI, based on recent testing.