Octel 50 Replacement Voice Board

[gregarican]

Here's my situation. My company's Smooth Operator 4.0 (aka Octel 50) system went down. Fried system board, power supply and one of the two 4-port Rhetorex boards. I relocated the PC components and Sentinel key to another PC. There were no hardware IRQ/Port/Memory Address issues as everything came back up fine.

Where I'm running into problems is adding another Rhetorex board to replace the failed one. The good board that was salvaged was a 4108 model that was set to Port 300. Works fine. But I installed a replacement 432 model to replace the fried one at Port 301 and it won't come up under the Smooth Operator software. It will load up drivers under Rhetorex, however. All 8 ports are seen at the driver level.

Our company has operated with 8 ports for about 5 years now and we have adequate resources for the replacement card. Supposedly the replacement board came from an Octel system so I would think that the Octel bit is enabled on it so that the Sentinel recognizes it okay. But perhaps not.

Does anyone know of typical system behavior when it encounters a non-Octel signed board? Here's excerpts from a few system files:

VIEWSENT.EXE
------------
Serial Number <00000000000000000000>*
Product Code <0>*
Max Ports <32>*
Max Mailboxes <0>*
Revision <0>
Max Languages <0>
Fax Retrieval <Off>
Fax Mail <Off>
SMDI <Off>
AMIS <0>
Intercom Redirect <0>
Octel Board Required <On>

VOICECNF.LOG
------------
Port Channels Status Serial Number
---- -------- ------ -------------
300H 01 02 03 04 Tested OK 91154434
301H 05 06 07 08 Tested OK 01094066

Number Of RDSPs Found : 2
Number Of Voice Channels : 8
Memory Segment : D800
DOS Memory Allocation : 128 Kb
EMS Memory Allocation : 0 Kb
DOS RAMDISK Allocation : 0 Kb
Firmware Level : 440f
Revision : 7.27
Date : 01/24/96

Analog Trunk Line Count : 8
Analog Station Line Count : 0
Analog Driver Installed. Copyright (c) 1994, Rhetorex, Inc.

OPERATOR.LOG
------------
02/06/2004 02:34 AM Date:Aug 27 1997 Time:09:02:15
02/06/2004 02:34 AM DOS Version 6.22 DPMI Version 0.9 CPU 80486
02/06/2004 02:34 AM ERROR 16: Invalid board type: Error 1896 RET
02/06/2004 02:34 AM ERROR 16: Invalid board type: Error 1896 RET
02/06/2004 02:34 AM ERROR 16: Invalid board type: Error 1896 RET
02/06/2004 02:34 AM ERROR 16: Invalid board type: Error 1896 RET
02/06/2004 02:34 AM Initializing Voice Sub-System. Ver 27.07
02/06/2004 02:34 AM ERROR 16: Invalid board type: Error 1896 RET
02/06/2004 02:34 AM ERROR 16: Invalid board type: Error 1896 RET
02/06/2004 02:34 AM System Version 4.0
02/06/2004 02:34 AM ERROR 16: Invalid board type: Error 1896 RET
02/06/2004 02:34 AM ERROR 16: Invalid board type: Error 1896 RET

If I knew for a fact that this beahvior simply means I need a true Octel signed board I would feel more comfortable outlaying the expense. Anyone have suggestions? I see no technical documentation on the error codes returned by the system. And since Avaya no longer supports the Octel 50 system I'm out of luck :-(

 

[gregarican]

Forgot to include the config file that's in place. The only thing I toggled was MODE16, but it didn't affect anything. Here are the specifics:

CONFIG
------
RDSP=300
RDSP=301
HOOK=ON
AGC=ENABLED
MODE16=ENABLED
HANGUP=ENABLED
WHITENOISE=ENABLED
GAIN=0
DUALPORT=d8
ENTRYPOINT=61
REALMEMORY=128
EMSMEMORY=0
RAMDISK=0
OUTDIAL=VOICE
VOXLIMIT=3
SPIKES=6
DROPOUTS=6
ADPCM=0
HOST=0
CHIME1=0
CHIME2=0
FILTERTABLE=COMPASS.TON
TONETABLE=COMPASS.TON

 

[gregarican]

I know that no one replied to my posting, but as an FYI if anyone runs into the situation described above indeed the voice board didn't contain the Octel bit signature. Once I obtained a board that did everything came up fine.