Introduction

The following ports must be configured if the jtel virtual machines are located in different subnets or a firewall is installed between them.

General Information

During the basic installation of a jtel ACD, all firewalls are configured locally. There is generally no requirement to install additional firewalls between the jtel ACD virtual machines.

For further information, please visit the pages describing the basic installation of a jtel system: Debian Linux + Windows Server 2019

Glossary

Components	Hostname (Alias)	Function
Telephony Servers	ACD-TEL	The telephony servers of the system
Database	ACD-DBM + ACD-DBS + ACD-DBR	The database masters and slaves + reporting slaves
Database UDP Listener	ACD-DBM	The database masters
Load Balancers pcs cluster	ACD-LB	The load balancers containing the haproxy
Webservers	ACD-JB	The webservers
Samba Fileshare pcs cluster	ACD-STORE	The storage servers containing the samba fileshare
Chat Servers	ACD-CHAT	Servers which the Chat services are running on
REST Servers	ACD-REST	Servers which the REST API services are running on

Ports required from External Systems

The ports documented here are required to be accessed from external systems, in order that the system may function correctly.

All Linux

Description	Protocol	Source	Port(s)	Destination	Port(s)	Description
Remote Access	TCP	jtel Support	Any	All Linux	22	SSH Remote Access to Linux Systems.

All Windows

Description	Protocol	Source	Port(s)	Destination	Port(s)	Description
Remote Access	TCP + UDP	jtel Support	Any	All Windows	3389	RDP remote Access to Windows Systems.

Specific Systems

Description	Protocol	Source	Port	Destination	Ports / Portrange	Description
http Access	TCP	Any (jtel Support)	Any	ACD-LB	80	http Access to Webservers and SOAP / REST APIs via Load-Balancer. Will redirect to 443 (https) automatically if https with a certificate are configured.
https Access	TCP	Any (jtel Support)	Any	ACD-LB	443	https Access to Webservers and SOAP / REST APIs via Load-Balancer.
Samba Fileshare	TCP	Any Reporting API users	Any	ACD-STORE	445	Access to the Samba Fileshare of the system required by Reporting API users if own reports are to be created.
Websocket Chat	TCP	Any	Any	ACD-LB	3000	The chat-server port if http is being used to access the chat server from external.
Websocket Chat	TCP	Any	Any	ACD-LB	3003	The chat-server port if https is being used to access the chat server from external.
Reporting API	TCP	Any Reporting API users	Any	ACD-LB	3306-3308	Used to provide reporting API access to the database for BI applications.
SIP	TCP / UDP	PBX / SBC / SIP Trunk	Any	ACD-TEL	5060	SIP communication port for telephony signalling.
SIPS	TCP	PBX / SBC / SIP Trunk	Any	ACD-TEL	5061	SIPS communication port for telephony signalling.
haproxy Web	TCP	Any (jtel Support)	Any	ACD-LB	7777	Port used for HTTP access to the HaProxy admin GUI.
RTP	UDP	PBX / SBC / SIP Trunk	Any	ACD-TEL	30000-34999	RTP communication ports for audio / video data.

Ports required Internally

The ports documented here are required to be accessed between the servers in the solution.

Note, that between the servers ALL of the ports documented above are required no matter what APIs or components are being used.

When Any is documented as the source in the table below, any server internal to the solution is meant.

Description	Protocol	Source	Port	Destination	Port(s)	Required for Non-Redundant Systems	Required for Redundant Systems	Description
pcs Cluster	TCP	ACD-LB ACD-STORE	Any	ACD-LB ACD-STORE	2224	No	Yes	Ports used for communication between the pcs cluster members. Required on all nodes (needed by the `pcsd` Web UI and required for node-to-node communication) It is crucial to open port 2224 in such a way that `pcs` from any node can talk to all nodes in the cluster, including itself. When using the Booth cluster ticket manager or a quorum device you must open port 2224 on all related hosts, such as Booth arbiters or the quorum device host.
Chat Server	TCP	ACD-LB	Any	ACD-CHAT	3000	Yes	Yes	Websocket for chat server
Database Access	TCP	Any	Any	ACD-LB	3306	No	Yes	Redirect port to master database
Database Access	TCP	Any	Any	ACD-LB	3307	No	Yes	Redirect port to slave database used for real-time reporting
Database Access	TCP	Any	Any	ACD-LB	3308	No	Yes	Redirect port to slave database used for historical reporting
pcs Cluster	TCP	ACD-LB ACD-STORE	Any	ACD-LB ACD-STORE	3121	No	Yes	Ports used for communication between the pcs clusters members. Required on all nodes if the cluster has any Pacemaker Remote nodes. Pacemaker's `crmd` daemon on the full cluster nodes will contact the `pacemaker_remoted` daemon on Pacemaker Remote nodes at port 3121. If a separate interface is used for cluster communication, the port only needs to be open on that interface. At a minimum, the port should open on Pacemaker Remote nodes to full cluster nodes. Because users may convert a host between a full node and a remote node, or run a remote node inside a container using the host's network, it can be useful to open the port to all nodes. It is not necessary to open the port to any hosts other than nodes.
Telephony Servers	UDP	PBX / SBC / SIP Trunk	Any	ACD-TEL	5060	Yes	Yes	Port used for SIP
pcs Cluster	TCP	ACD-LB ACD-STORE	Any	ACD-LB ACD-STORE	5403	No	Yes	Ports used for communication between the pcs clusters members. Required on the quorum device host when using a quorum device with `corosync-qnetd`. The default value can be changed with the `-p` option of the `corosync-qnetd` command.
pcs Cluster	UDP	ACD-LB ACD-STORE	Any	ACD-LB ACD-STORE	5404	No	Yes	Ports used for communication between the pcs clusters members. Required on corosync nodes if `corosync` is configured for multicast UDP
pcs Cluster	UDP	ACD-LB ACD-STORE	Any	ACD-LB ACD-STORE	5405	No	Yes	Ports used for communication between the pcs clusters members. Required on all corosync nodes (needed by `corosync`)
Hazelcast Cluster	TCP	ACD-DBM ACD-TEL ACD-JB ACD-CHAT	Any	ACD-DBM ACD-TEL ACD-JB ACD-CHAT	5701 - 5801	Yes	Yes	Hazelcast cluster ports.
Web Server Access	TCP	Any	Any	ACD-JB	8080	Yes	Yes	http server port for accessing the webserver.
REST Service Access	TCP	ACD-LB	Any	ACD-REST	8091	Yes	Yes	Rest interface
pcs cluster	TCP, UDP	ACD-LB ACD-STORE	Any	ACD-LB ACD-STORE	9929	No	Yes	Required to be open on all cluster nodes and booth arbitrator nodes to connections from any of those same nodes when the Booth ticket manager is used to establish a multi-site cluster.
Telephony Servers	UDP	ACD-TEL	Any	ACD-TEL	20202	No	Yes	If building a cluster with more than one telephony server, this is the broadcast port used for interchassis communication and discovery.
Web Server Communication	UDP	ACD-JB	Any	ACD-JB	20640	Yes	Yes	When changing slides in the presentation, this port is used to send the information to the other web servers. The 8-Server sends information to the web servers so that the information of the current conference call is displayed in the browser. This setting can be found in the parameters: ConfServer.WebServer.UDP.Port
Webserver conference control of telephony	UDP	ACD-JB	Any	ACD-TEL	20641	Yes	Yes	Used for controlling telephone conferences from the web application. ConfServer.Daemon.UDP.r5 must be running on the target telephony server. The actual destination for the message is determined dynamically by the web application. This setting can be found in the parameters: ConfServer.Daemon.UDP.Port
Telephony Servers - TTS generation	UDP	Any	Any	ACD-TEL	20643	Yes	Yes	IP address and port of the telephony server on which the TTS daemon is running (only for installations with TTS installed). Used to initiate ad-hoc tts generation. This setting can be found in the parameters: Portal.Daemon.TTS.UDP.Address Portal.Daemon.TTS.UDP.Port
Event generation for APIs	UDP	Any	Any	ACD-JB ACD-REST ACD-TEL	20644	Yes	Yes	Communication from event producers to the hazelcast cluster on change of various status for signaling events via the APIs or internally. The PlatformUDPListener must run on the corresponding target computers. If running on the source itself, no port will need to be opened between the servers. This setting can be found in the parameters: ACD.UDP.MediaEventsListener.Address ACD.UDP.Webserver.Address
Call initiation and call control	UDP	Any	Any	ACD-TEL	20645	Yes	Yes	Communication from servers to the daemon process for ACD and call control. Note: The daemon ACD.Daemon.UDP.r5 must run on the corresponding ACD-TEL server. This setting can be found in the parameters: dialler.8Servers.IPs ACD.UDP.Daemon.Address ACD.UDP.Daemon.Port
TAPI call forwarding and redirection control	UDP	Any	Any	ACD-TEL	40404	Yes	Yes	Used to control the call forwarding settings in the PBX via the PBX connector (usually ECSTA or a multi-line TAPI). This setting can be found in the parameters: Portal.JTELTAPIServer.UDP.Address Portal.JTELTAPIServer.UDP.Port
Call initiation via PBX connector	UDP	ACD-JB	Any	ACD-TEL	40406	Yes	Yes	The IP address of the PBX-Connector, if outdials are to be initiated via the PBX connector and not via the telephony server. This setting can be found in the parameters: dialler.ClickToCall.UDP.Connector.Host dialler.ClickToCall.UDP.Connector.Port Recommendation: set dialler.ClickToCall.UDP.Connector.Host EMPTY if the telephony server is to be used for outdial requests. Otherwise when set then ALL click-to-cial commands will be sent directly to the PBX connector.

Page tree

Required Port Configuration