I have successfully configured unity 3.1.4 with 1 dialogic dt/120 ------ID#1 it works great and is detected by unity and everything works fine . I go to install a second dialogic card set its ID # 2 and i get the dialogic service rerminated with service specific error 16383 . I get this with the h.100 bus connected and with out it connected . When i remove 1 of the cards again to only 12 ports everything works fine . HELP Please
No, the 2500 series has had ample testing with voice boards.
Unfortunately, your error is not very specific. It typically shows up with misconfigured or defective hardware. Since the two boards each load fine when place individually in either PCI slot, I don't believe the boards or the server are to blame. The only piece of hardware that I might suspect then is the h.100 cable. Either that or there something in the configuration that we're overlooking. Are there any other errors in the System or Application event logs?
One thing you might try is uninstalling and reinstalling the Dialogic software. Follow the steps here,
I have tried everything even reinstalling the entire box and starting over from scratch even though i knwe it would not fix this issue . I can not even imagine what i can be no w. I opened a case with TAC on friday and still no resolve .
Has anyone ever installed 2 dlaiogic cards with the h.100 connector or am i the only one in the world doing an install like this .
Yes, there has been ample testing with multiple dialogic cards using the h.100 connector. The errors you are seeing typically means that something in the hardware is not installed properly or is defective, in particular, the h.100 cable. If this is the case, TAC is your best bet.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.