hi there<br><br>we have a client running Unity 2,3,4,,147. The PABX is a Fujitsu Essence. the site has one exchange server and unity is installed on the same Server. in 6 months they have had a problem twice where when any pc tries to play a voice message in outlook they get the error" unknown problems are preventing the completion of this call". stopping and starting unity does not solve the problem. but if the server is rebooted the problem goes away. <br>any ideas on this? <br><br>
this is probably a situation where one of the ports we are trying to dial out on for the TRAP connection is "burned" at the Dialogic TAPI level. We've gotten most of these fixed with Dialogic but there's still the occasional scenario that cause them to get hosed up.
If we go to try and do a dialout and the port isn't doing what we expect, you'll get that "unknown error" thing. You'd also get that if we couldn't contact the Unity server from the client but that doesn't sound like the case you're talking about here.
that would also explain why restarting Unity doesn't fix it... you have to reset the server to get the Dialogic drivers to reinit.
If you get into this state again, try calling the ports setup for TRAP dials directly one at a time and see if any or all of them are responsive.
well wat i would like to know is do we have to reboot the server everytime this happens to fix it? also if so would an upgrade to a later version of unity eg. 2,4,5 solve this since they are a unity 2,3?
the problem described in my earlier posts happened on my computer at work.Mine was the only pc at my company that was affected. i rang all unity's ports individually and they all answered perfectly. i could play messages thro soundcard but not over the fone. rebooting my pc fixed the problem
That sounds like it might have been a known problem with the TRAP connector on your local box.
We leave the TRAP connector active for a while after you've finished/closed the recording session so you don't have to dial your station again when you want to record another greeting (or listen to another message via VMO). There were some issues where this guy was never dropping out of memory and new connection attempts would fail without ever trying to connect to the Unity server.
These, along with a few other TRAP connection problems mentioned in other posts out here, were largely cleaned up in 2.4.6 102. Folks have had much better luck with consistent TRAP functionality in 2.4.6 land...
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.