Anecdotal evidence suggests that within our citrix farm, each citrix server may only be handling a single connection of Avaya One-X Communicator 6.0.026. Once Avaya One-X Communicator has registered using UDP port 16384 and assigned a unique TCP port, UDP port 16384 remains active. A second attempt to register Avaya One-X Communicator via UDP port 16384 fails & loops, and does not fail over to another UDP port in the range 16384-17683 to register.
This why when we run a netstat –nao and if we see UDP port 16384 in use on the citrix server, we know that we will always get a failure when attempting to register another session of Avaya One-Communicator.
Any ideas why UDP port 16384 remains open and blocks additional connections or why the UDP port will not simply fail over to the next UDP port in the range 16384-17683
This why when we run a netstat –nao and if we see UDP port 16384 in use on the citrix server, we know that we will always get a failure when attempting to register another session of Avaya One-Communicator.
Any ideas why UDP port 16384 remains open and blocks additional connections or why the UDP port will not simply fail over to the next UDP port in the range 16384-17683
