Thanks for your post. I think there may be an easier way to handle this scenario if someone runs into it again.
What’s happening here is the switch page has some logic in it that checks for the TAPI driver loaded. The switches and integrations offered on this page depend on which driver is loaded (i.e. Cisco vs. Dialogic analog, vs proprietary digital integration for some or our partners etc…). If it makes a check and discovers either no TAPI driver loaded or no ports offered by the TAPI driver, it will display no switches as available. Same deal for the switch edit utility.
From your description it sounds like the TAPI driver was probably reporting no ports to us. It installs after the Dialogic drivers are installed and if that failed for whatever reason (bogus IRQ, wrong base address, a conflict in the system, whatever) the TAPI driver will install and load but set itself for no ports available since it didn’t detect any.
The easiest way to handle this is to fix the Dialogic problem using DCM as you did. Instead of uninstalling and reinstalling, however, reinitialize the TAPI driver configuration. To do this, first go to the Control Panel and open the “Telephony” application. On the “Telephony Drivers” tab, choose the ‘Dialogic Generation 2 Service Provider’ and hit the “Configure” button. On the configuration dialog, hit the “Detect Boards” button. If the Driver is now loaded and running properly the TAPI driver should now pick them up.
At this point if you restart the system, Unity should pick up the TAPI ports and allow you to select a switch configuration.
Jeff Lindborg
Unity Product Architect
Active Voice
jlindborg@activevoice.com
http://members.home.net/jlindborg
