Installing Intel Dialogic E/4PCI card
cody
III 1.o Ghz , Win2000 Sp1. I downloaded from site
http://www.mawnet.com/boards.html the instruction for installing
Dialogic D/4PCI under Windows 2000. I also went to
http://resource.intel.com/telecom/support/releases/winnt/index.html
and downloaded System release 5.1.1 for windows (service pack for
5.1.1 as well. The installation for 5.1.1 and the service pack 5.1.1
went well. Step 17 in the instructions is where I have a problem. I
run the Phone and Modem Options from Control panel to configure
"Dialogic Genereration 2 Service Provider for NT" Channel information,
but no channels appear. I click on detect boards and a message states
"No Started Boards are found". I run Intel Dialogic Configuration
Manager to check to make sure the service status is "running" and it
is. In the Dialogic Configuration manager window is the following:
- Configured Devices on_EX138233
- D/x1D-PCI
(a green led) ???? #0 in slot 2/11
- TDM Bus
Bus-0
with system Service Status: Running.
I check the event Viewer for any errors;
CTBBAPI.exe 01.50 bld 3 (release).
0x20000003 : CTBB_ERROR_NO_CLIENT: Client was not registered.
Exit value : 0x3.
CTBBAPI.exe -Lctbbapi.log -apiCTBB_AddToTDMBus -clientDLGCSRAM
returned fatal error.
Dialogic System Service started
I am not sure what that is telling me.
What am I missing?? I am tying to use this D/4PCI card in my project
to dial a response center and when the technician answers the phone, a
wave file is played telling the technician there is a problem the
system. Any help would be appreciated...
Cody
Dan Scavezze
I had a very similar problem. There's a thread in this newsgroup titled
"answering the phone reliably" that tells about it. The good news is
that I got it solved. The bad news is that to get a good solution, I had
to buy a new PC. That wasn't too bad for me, because I was planning to
buy a new machine to act as a dedicated server anyway. When I did, I
found that the problems that my HP Pavilion were gone.
The thread tells most of the detail about the workaround I used. The
only thing that I never updated is that I did find a way to start up my
Dialogic board on boot. I used WinSpy to see what message I could send
to Dialogic's DCM program to get the board going. I was lucky that
Dialogic happened to have an accelerator key for the "start services"
command.
Here's a snippet of the thread (below). Hope this helps.
Dan
____________
Well, I've got the Dialogic board running and all it took was a magic
incantation -- actually running some commands from the command line.
When we left our story, the Dialogic DCM would not detect my board, and
it was logging the message CTBB_ERROR_NO_CLIENT. After researching the
Dialogic website
(http://www.intel.com/network/csp/programs/support.htm), I found an
entry titled "Starting Dialogic Boards from Command Line under NT"
(http://resource.intel.com/telecom/support/tnotes/tnbyos/winnt/tn243.htm).
I invoked their suggested commands as shown below. At the end of the
sequence, when "regvox - c" did not give me an error message, I thought
perhaps I registered the elusive client that the CT Bus Broker was
looking for. When I tried the genload command again, this time genload
said…
"1 Dialogic Board [was] Successfully Installed"
…and my God, it was. I still had to go back into DCM to start the board,
but finally I could use the board with my TAPI app and it works! It
works very well, in fact. It has never failed to answer a call! I'm in
heaven, almost.
I can't seem to get this configuration to be persistent. Every time I
boot the computer I have to issue the magic incantation (I have it in a
batch file now), and then run the GUI-based DCM to start the board. I'm
hoping to eventually get unattended 24x7 operation of the server, so it
seems like there may be a few more obstacles to overcome in order to do
an automatic reboot. On the other hand, since the board is so reliable,
if I can make my application bullet proof, re-boot may never be required.
I'm thinking that perhaps I should repost this in a separate thread for
those that might also be having trouble setting up the Dialogic software
with WindowsXP and the D/4PCI. The thread name could be named "Dialogic
magic." I suppose I should tell Dialogic about this too, except that
they wanted $250 the last time I tried to talk to them.
____________
cody
But unfortunately, the genload failed with this error
WSB0324: ???? (PCI IC 0) download failed-Genboot did not start
No dialogic boards successfully Installed..
Why did you have to get a new PC...
Ray Cassick (home)
Even if you DO get it working, if it stops working latter do not expect help
to get it running again.
Windows XP support is not available until SR 5.1.1 FP1 (Feature Pack 1) and
unless you have a support contract you will need to pay for it.
There should not be any reason why you have to jump through the hoops that
you just to start the service. Set the service for autostart and you should
be all set. The only reason that you need to use DCM is when you first
install the board to get it detected.
If you have problems getting a PCI Dialogic card detected under Windows 2000
(I will not say XP because it is not supported anyway) try turning off
Plug-and-Play in the system BIOS. I have seen this work on several HP
systems (mostly Vectras) before. You might also have to tie an IRQ to a
specific slot to get it to work as well.
"Dan Scavezze" <d...@scavezze.com> wrote in message
news:3E54EE3C...@scavezze.com...
Dan Scavezze
When you ask "Why did you have to get a new PC..." to get my Dialogic
board working, I guess the answer is "I still don't know." Without any
help from Dialogic, I can only tell you what worked and speculate about
what didn't.
I originally speculated that it was due to some problem with the order
of loading all the services (roughly 90 or so) that are running on my
old machine. Perhaps some service wasn't loaded before a Dialogic
service needed to use it or perhaps some service conflicted with the
Dialogic service(s). But the new machine has a lot of services too and
it doesn't seem to matter.
My other theory was that the PCI bus handling was not adequate on my old
machine. The new machine (Intel motherboard) has PCI options in its BIOS
that were not even available on my old machine (the HP Pavilion). Things
like Ray mentions in his message "tie an IRQ to a specific slot" were
not available in my old machine. I've been told that HP sometimes
disables BIOS options. The new machine _would_ let me do things like
that, but it wasn't necessary. The board came up fine. Both machines are
running XP.
I can tell you that I had exactly the same error you just mentioned
"WSB0324: ???? (PCI IC 0) download failed-Genboot did not start." You'll
see in the window capture below that I invoked genload, got that error,
then invoke the "magic" commands...
regvox
startdrv
regvox -c
...and then the next time I invoke genload I got "1 Dialogic Board
Successfully Installed"
Dan
<start of command window capture>
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Program Files\Dialogic\BIN>net start dlgcsram
The Dialogic SRAM Protocol Driver service was started successfully.
C:\Program Files\Dialogic\BIN>genload
Dialogic Generic Downloader Version 5.11 (Build 30)
Copyright (c) 1992-2000 by Dialogic Corp.
No Springware boards were found in the Dialogic database.
C:\Program Files\Dialogic\BIN>genload
Dialogic Generic Downloader Version 5.11 (Build 30)
Copyright (c) 1992-2000 by Dialogic Corp.
System Download ...
GENBOOT not responding on board 0.
WSB0324: ???? (PCI ID 0) download failed - GENBOOT did not start
No Dialogic Boards Successfully Installed
C:\Program Files\Dialogic\BIN>regvox
There are 0 interrupt vectors being used
C:\Program Files\Dialogic\BIN>startdrv
Starting driver \\.\Dialogic SRAM PD failed with error e0000012
C:\Program Files\Dialogic\BIN>regvox -c
C:\Program Files\Dialogic\BIN>genload
Dialogic Generic Downloader Version 5.11 (Build 30)
Copyright (c) 1992-2000 by Dialogic Corp.
System Download ...................................
D/4PCI (PCI ID 0) Download .. BCV Firmware Version 6.53
1 Dialogic Board Successfully Installed
C:\Program Files\Dialogic\BIN>
<end of command window capture>
-------------------------------
cody
and Play in the bios and it works just fine....