Call Pilot IP ports to open?
Call Pilot IP ports to open?
(OP)
Hello, I have several sites running Call Pilot with users running the Desktop Messaging client on their PC's.
My problem is we have webmail enabled via our Exchange server from a public IP address which gets resolved through a DNS server and then passes through our firewall. Some of my users have configured their Outlook clients to use the webmail IP address for the times they are travelling and using a regular Internet connection. However, the Desktop Messaging module just hangs forever trying to get to the Call Pilot system before finally giving up. My users are frustrated over this. I need to create a DNS entry from the outside world for our Call Pilot server but only want to open up the ports that are really needed. Does anyone know what ports that would be?
My problem is we have webmail enabled via our Exchange server from a public IP address which gets resolved through a DNS server and then passes through our firewall. Some of my users have configured their Outlook clients to use the webmail IP address for the times they are travelling and using a regular Internet connection. However, the Desktop Messaging module just hangs forever trying to get to the Call Pilot system before finally giving up. My users are frustrated over this. I need to create a DNS entry from the outside world for our Call Pilot server but only want to open up the ports that are really needed. Does anyone know what ports that would be?
Talk To Other Members
RE: Call Pilot IP ports to open?
Here is the infromation from the NTP.
Desktop Client to CallPilot Server
IMAP = 143, SSL = 993
SMTP = 25, SSL = 465
LDAP = 389, SSL = 636
Others
My CallPilot Web Client to CallPilot Server: HTTP, FTP and IMAP Ports
My CallPilot Web Client to Stand-Alone web server: HTTP, FTP, and IMAP Ports
CallPilot Manager to CallPilot server: LDAP, FTP and RPC Ports
CallPilot Manager to stand-alone web server: HTTP Port
Reporter to stand-alone web server: HTTP Port
CallPilot to Groupware server (for Email by Phone or Desktop): IMAP Port
AppBuilder client to CallPilot server: LDAP, FTP, RPC Ports and AOS
HTTP: Unencrypted = 80, SSL = 443
IMAP: Unencrypted = 143, SSL = 993
SMTP: Unencrypted = 25, SSL = 465
LDAP: Unencrypted = 389, SSL = 636
FTP: 20, 21
RPC: 135
SNMP: 60, 61
AOS DCOM uses port 135, but may dynamically used any port between 1024 and 65535
Firewall information:
If the Firewall is between My CallPilot and the user’s browser, the following ports must be open: HTTP, FTP, IMAP (for audio player telset)
If the Firewall is between the CallPilot Server and the My CallPilot server, then the following ports must be open: FTP, IMAP, SMTP and LDAP.
CallPilot Reporter Requirements:
If a firewall is implemented, you must ensure that all required services are up and operational on both CallPilot and Reporter server and the ports are “open” in the firewall for two-way communications between servers. Ports include the following:
HTTP: Unencrypted = 80, SSL = 443
LDAP: Unencrypted = 389, SSL = 636
FTP: 20, 21
RPC: 135
ODBC: 1499
Good Luck
Jeff
RE: Call Pilot IP ports to open?
You rock!
God Bless You!