Hi Forum<br><br>We have sold a CallManger inst. (Ver 3.1.2c) with Unity voice mail (3.0.2). This is installed in an environment where the customer already is running MS-Exchange.<br><br>Existing Exchange server is running NT 4.0 and Exhange 5.5 Servicepack 4. We have installed the Unity server with Windows 2K and MS-Exchange 5.5. Installation went well, we used the existing service account to install the new MS-Exchange server. But we see a strange problem here.<br><br>Outside users who leaves a message to a Unity subscriber, will fail. The message is correctly taken and registered via the phone, but it is not transferred to the users inbox on the exixsting MS-Exchange server.<br><br>I have to mention that all Unity subscribers have there voice mailbox (Inbox) on the existing Exchange server.<br>Sometimes this mail is delayed for a whole day, sometimes it is never delevered.<br><br>The two servers is complaining about RPC problems which can be seen in the application log:<br><br>An RPC communications error occurred. Unable to bind over RPC. <br>Locality Table (LTAB) index: 52, NT/MTA error code: 1722.<br> Comms error 1722, Bind error 1722, <br>Remote Server Name EXSERV [MAIN BASE 1 500 ] (14) <br><br>When two Unity subscribers call each other - it works as supposed. Only external, (Read non subscribers) can not leave a message. It seems like an Exchange problem - but what the h... is going on.<br><br>We have in this installation integrated the new Unity server in the existing MS-Exchange location - would it have been more vise to make a new location and use site connectors? Is the problem that the existing server is running NT and the Unity server is running 2K?<br><br>Regards<br><br>Peter L<br><br><br><br>
Yeah, this is very likely a DNS issue or something along those lines. Often RPC or bind-back errors are related to the fact that RPC does everything by maching name (not IP) and if there's issues connecting or reconnecting it often lies here.
This is working for subscriber to subscriber messages since Unity originates the sending message in the home store of the sender in that scenario. In the case of unidentified callers the messages are left from the the Unity Messaging System account which is homed on the Exchange server on the local Unity server. It is then up to the Exchange MTA (which relies on RPC) to get the messages to the appropriate home store... this is where the RPC breakdown is biting you.
Here's a good MSDN article that is a jumping off point for diagnosing RPC related issues with Exchange 5.5. I've had good luck with people working through this article to clear these problems:
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.