You are here

H323 port 1719 conflict

1 post / 0 new
kbittner
H323 port 1719 conflict

I am attempting to switch from Paradial H323/SIP platform to a Radvision GK and Pathfinder client to run my eSummit MCU (public IP) and H323 client software from behind my firewall.  The Paradial Platform has been killed but I am still getting port 1719 conflict when I attempt to log onto the Radvision Proxy server.

Is it possible that a Paradial client installed on a laptop somewhere is causing this conflict even though the server and process has been killed?

How can I test to see what is listening on port 1719? The eSummit MCU is running on a Linux RedHat 5.0 server.

Edited by: admin on 05/16/2010 - 04:32