When using a separate Unity and Exchange server, what TCP ports are used between the two servers? My customer wants the servers on separate subnets and wants to put access lists up for security.<br><br>
Unity is connecting to the remote Exchange sites through LDAP. So they need to figure out the LDAP ports on their exchange servers. Also Unity hosts the SA and AA web pages. The incoming requests for that need to be enabled. Be cautious of moving the Unity out of the subnet for Exchange. Some folks have had lots of performance issues related to the latency in the subnets. Unity can seem to work slower, especially while forwarding and deleting messages.
Exchange 5.5 will need to change it's configuration from 389... you can't have AD and Ex55 fighting over the same port. If you leave Exchange at 389 we wont see it there when you point us at the Exchange server and part 2 setup will fail. You need to change it to something like 1024 or whatever paints your wagon.
The scenario we're looking at is new Unity 3.1 installation along with new Windows 2000/Active Directory/Exchange 2000. They have an existing Lotus Domino server but we will not be integrating with that. They are migrating their users over to the new Active Directory installation. Do we still have to change the LDAP port if there is no Exchange 5.5?
There is no LDAP port to change for Ex2K so if you're hooking up to Ex2K there's nothing you need to do along these lines. I thought since you were talking about changing the LDAP port you were talking 55...
As a follow up, here's a couple of interesting responses from some folks up here as to which ports get used (a comprehensive list is next to impossible since many are dynamic):
================= Note that each side of the connection has it's own port. Like when you surf the web, you connect to the "well known" port 80 on the http server, but your browser binds to a local port which is likely to be above 1024 (it is assigned by the OS, since it doesn't need to be a "well known" port on the client.)
The Skinny messages by default get sent to TCP port 2000 on the *Call Manager*. On the Unity, the socket binds to a local TCP port assigned by the OS, guaranteed to be between 1024 and 5000. On my system, they start at 3000 and work up, one for each Unity "port".
Type `netstat` at a command prompt on the Unity box during active use and see what it lists for you...
========================== Other possible ports:
TCP 2000 for skinny messages unity<->CM
UDP 16384-32767 for RTP streams unity<->voice terminating device (phone/gateway)
TCP 143 for communication from unity<->exchange IMAP
TCP 389 for communication from unity<->exchange LDAP directory
TCP 137-139 for any SMB communication from unity<->exchange server (copy files to/from remote share \\server\share )
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...