|
The UPLINX Remote Phone Control Tool utilizes the following protocols and ports on the servers. If there are intermediate filters or firewalls, the protocol and ports must be opened towards the servers. The ports cannot be changed on the servers or the UPLINX Remote Phone Control Tool.
The connectivity to all the resources below can be verified by Testing the Configuration .
Outgoing Connections - from Phone Control Tool to CUCM and Phones
|
Outgoing Connection
|
Ports Used
|
URL Used
|
|
CUCM AXL Connection
|
HTTPS: TCP 443
|
https://<serverIP>:443/axl
|
|
CUCM JTAPI Connection
|
Secured: TCP 2749
Non-Secured: TCP 2748
|
N/A
|
|
Direct Web Access to Phones
|
HTTP: TCP 80
HTTPS: TCP 443
|
https://<phoneIP>/CGI/Screenshot
https://<phoneIP>/CGI/Execute
|
|
Ping to CUCMs and phones
|
|
All CUCM member servers should be pingable by IP and also by name (full and hostname only). Please see also DNS entries
|
The direct Web Access to phones is required to display the remote phone's screen as well as deploy Bulk Background Images. More information: Phone Authentication Issues and Phone Screen Display Issues.
Incoming Connections - from Phones to Phone Control Tool
The Remote Phone Control Tool also runs a built-in Web Server to be accessed from the phones to download images or text messages. The built-in Web Server will use the TCP port configured on the Server tab in the section Web Server. The incoming connection to the port needs to be allowed to pass through any firewall to allow the tool to function properly.
More information: Configure Built-in Web Server
|
