Selecting Line Devices For D/41jct

[Guest doug]

I installed SR5.1.1 and also its SP on Windows XP. I have D/41JCT that passed all UDD test. I downloaded latest voiceguide demo software today. On the Intel Dialogic configurationThe Configuration Wizard, Service is started and set to automatic. In the voiceguide configuration wizard, there is a list of TAPI devices to select and I'm not sure which to select, and I selected all of them:

 

RAS PPPoE Line0000

RAS VPN Line 0

WAN Miniport(L2PT)

LPT1T

IPCONF LINE

H232 Line

 

1. Can you pls advise which is the right selection for D/41JCT-LS ?

 

2. Why is there an error: I started the Dialogic Talker32 "TAPI" program, and it immediately shows a message "Failed to open line 4, Reason=LINEERR_OPERATIONUNAVAIL. It shows 5 lines (D/41JCT only has 4), and shows Line 4 circle as black. When clicking on the Info button for each line:

 

Line 0: General (Line type:unknown), Status unavailable (lineGetDevStatus failed)

Line 1: Same as Line 0

Line 2: General (Line type:unknown),

Total calls = 0,

dwNumOpens = 1

dwOpenMediaModes = 258

dNumActiveCalls = 0

dwNumOnHoldCalls = 0,

dwNumOnHoldPendCalls = 0,

dwLineFeatures = 0

,dwDevStatusFlags = INSERVICE

Line 3: same as Line 2

Line 4: General (Line type:unknown), Status unavailable:last open failed, rc=80000

Line 5: General (Line type:unknown)

Total calls = 0,

dwNumOpens = 1

dwOpenMediaModes = 14

dNumActiveCalls = 0

dwNumOnHoldCalls = 0,

dwNumOnHoldPendCalls = 0,

dwLineFeatures = 140

,dwDevStatusFlags = INSERVICE

 

None of the above shows "Line Type: Dialogic Gen 2". What is the fix?

[SupportTeam]

You have two options:

 

Option 1:

Use v5.2 of VoiceGuide, for which you will need to install Dialogic's TAPI and Wave drivers - instructions here: http://www.voiceguide.com/vghelp/html/Inst...allDialogic.htm

 

Option 2:

Download and install the "VoiceGuide for Dialogic" patch. Follow instructions in the downloaded archive's readme.txt file. You do not need to install TAPI/Wave drivers if using VG for Dialogic.

 

We'd recommend you go with Option 2. If you use a Dialogic card you might as well use VG for Dialogic.

[Guest doug]

I installed the patch, and followed the readme.txt instructions. I did not modify any xml file since I am using 4 port D/41jct card. I then installed Dialogic Global Call 4.2.

 

I can make a call to test the credit card payment without any problem. The voiceguide devices displayed are:

[1] dxxxB1C1 dxxxB1C1 Waiting for a call...

[2] dxxxB1C2 dxxxB1C2 Waiting for a call...

[3] dxxxB1C3 dxxxB1C3 Waiting for a call...

[4] dxxxB1C4 dxxxB1C4 Waiting for a call...

 

1. But running the Configuration Wizard would show a message "Edit the LinesConfig.xml file in \data\subdirectory." What do I need to edit?

 

2. The Dialogic talker32 TAPI program still doesnt work, showing same errors.

[SupportTeam]

LinesConfig.xml file in \data\subdirectory allows you to set what are the Busy/Disconnect/etc tones which the system should be detecting.

 

2. The Dialogic talker32 TAPI program still doesnt work, showing same errors.

Don't need to test with Talker32 if you are using VG for Dialogic. Also, you say that "I can make a call to test the credit card payment without any problem", so it looks like everything is working fine.

[Guest doug]

The file in the data directory is called "ConfigLine.xml" (from the patch), instead of "LinesConfig.xml". I am new to voiceguide and do not have any manual on the D/41jct used card. Do you have step by step instructions on what to modify in order for the configuration wizard to work?

[SupportTeam]

Configuration Wizard is not used in VG for Dialogic.

 

Configuration Wizard (when used with v5.2 of VG) just selects the lines for system to use and what script are to be used on those lines. Both of those items are specified in Config.xml when running VG for Dialogic.

 

From your previous posts it looks like VG is starting fine and it is answering incoming calls OK.

Configuring busy/disconnect tones is not essential to get the system to function - but it's better to set those right if you would like the system to hangup immediately when caller hangs up and to correctly detect what is happening on the line during call transfers.