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

Info

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)

Name

	Function

TELEPHONY


Telephony Servers	ACD-TEL	The telephony servers of the system

DATABASES

Database

ACD-DBM + ACD-DBS + ACD-DBR

The database masters and slaves + reporting slaves

DATABASE MASTERS

Database

UDP Listener

ACD-DBM

The database masters

LOAD BALANCER

Load Balancers

pcs cluster

ACD-LB

The load balancers containing the haproxy

WEBSERVER

Webservers

ACD-JB

The webservers

STORAGE

Samba Fileshare

pcs cluster

ACD-STORE

The storage servers containing the samba fileshare

CHATSERVER

Chat Servers

ACD-CHAT

Servers which the Chat services are running on

RESTSERVER

REST Servers

ACD-REST

Servers which the REST API services are running on

Table (System Parameters)

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

Host (System Parameter jtel ACD)Port Setting (System Parameter jtel ACD)

	Protocol	Source	Port(s)	Destination	Port(s)	Description

ACD.UDP.Daemon.AddressACD.UDP.Daemon.PortUDP

WEBSERVER

AnyTELEPHONY (DAEMON)20645

Communication from the web server to the daemon process for ACD control.

Note: The daemon ACD.Daemon.UDP.r5 must run on the corresponding TELEPHONY server.

ACD.UDP.MediaEventsListener.Address(Static Setting)UDPDATABASESAnyPLATFORM UDP LISTENER20644

Communication from database server to hazelcast (web server) on change of agent status for signaling events via SOAP.

The platformUDPListener must run on the corresponding target computers. (Preferably on localhost - only on the DB masters, not slaves).

ACD.UDP.Webserver.AddressACD.UDP.Webserver.PortUDPTELEPHONYAnyPLATFORM UDP LISTENER20644

Communication of 8-Server TELEPHONY processes to Hazelcast (web server) on change of call status for signaling of events to SOAP and Agent-Home.

The platformUDPListener must run on the corresponding target computer. (Preferably on localhost).

(connection is initiated by web application in each case)ConfServer.Daemon.UDP.PortUDPWEBSERVERAny TELEPHONY (DAEMON)20641Controlling the telephone conference from the web application. ConfServer.Daemon.UDP.r5 must be running on the target computer ( 8-Server). The actual destination for the message is determined dynamically by the web application.dialler.8Servers.IPsdialler.ClickToCall.UDP.8ServerCommand.PortUDPWEBSERVERAny TELEPHONY (DAEMON)20645

Port on the 8-Server to which the commands are sent via UDP for the Dialler.

Must be set the same as ACD.UDP.Daemon.Port, because the commands are directed to ACD.Daemon.UDP.r5.

dialler.ClickToCall.UDP.Connector.Hostdialler.ClickToCall.UDP.Connector.PortUDPWEBSERVERAnyPBX CONNECTOR40406

From the web server, the IP address of the PBX-Connector, if outdials are to be initiated via the connector (and not via the 8-Server).

Recommendation: set dialler.ClickToCall.UDP.Connector.Host EMPTY if 8-Server is to be used for Outdial.

Otherwise set (only with Innovaphone), then ALL Click-To-Dial commands run directly out via the Innovaphone.

Portal.AgentCallControl.UDP.AddressPortal.AgentCallControl.UDP.PortUDPAnyPBX CONNECTOR40406IP address and port of the PBX-Connector, if commands such as "Answer" are supported via the PBX-Connector.Portal.Daemon.TTS.UDP.AddressPortal.Daemon.TTS.UDP.PortUDPTELEPHONYAny

TELEPHONY (DAEMON)

20643

IP address and port of the 8-Server on which the TTS daemon is running (only for installations with TTS installed).

Portal.JTELTAPIServer.UDP.AddressPortal.JTELTAPIServer.UDP.PortUDPTELEPHONYAnyPBX CONNECTOR40404IP address and port of the JTELTAPI forwarding service, when using the connector with TAPI / ECSTA.(8Server Intershassis communcationUDPTELEPHONYAny8Server20202If building a cluster with more than one 8-Server, enter the broadcast address for interchassis communication, using port 20202:

All Linux

...

jtel Support

...

Remote Access to Linux Systems.

All Windows

...

jtel Support

...

Remote Access to Windows Systems.

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.

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

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

Description

All ports

ComponentHost

	Protocol	Source	Port	Destination

Ports / Portrange

Port(s)	Required for Non-Redundant Systems	Required for Redundant Systems	Description

Load BalancersACD-LBTCPAnyAnyLOAD BALANCER80YesYesPort used for HTTP accessLoad BalancersACD-LBTCPAnyAnyLOAD BALANCER443YesYesPort used for HTTPS accessSamba FileshareACD-STORETCPSTORAGEAnyALL445YesYes

Ports used by the samba fileshare to provide access for the other jtel vms. All other virtual machines use this port for communication with the fileshare.

This port is required in BOTH redundant and non redundant architecture.

pcs clusterACD-LB/STORETCP

LOAD BALANCER

STORAGE

Any

LOAD BALANCER

STORAGE

pcs Cluster

TCP

ACD-LB
ACD-STORE

Any

ACD-LB
ACD-STORE

2224

No

Yes

Ports used for communication between the pcs

clusters members.NOT needed when no redundancy is installed

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

Servers

Server

TCP

ACD-

CHATTCPLOAD BALANCER

LB

Any

CHATSERVERS

ACD-CHAT	3000	Yes	Yes	Websocket for chat server
Database

ACD-DBM/DBS/DBR

Access

TCP

DATABASES

Any

ALL

ACD-LB

3306

Yes

No

Yes

Ports used by the MySQL to provide access to the other machines, and MySQL Tools like DBForge MySQL used on other machines in the Network.

Redirect port to master database
Database Access	TCP	Any	Any	ACD-LB

Load BalancersACD-LBTCPWEBSERVERSAnyLOAD BALANCER

3307

No

Yes

Redirect port to slave database used for real-time reporting

Load BalancersACD-LB

Database Access

TCP

WEBSERVERS

Any

LOAD BALANCER

ACD-LB	3308	No	Yes	Redirect port to slave database used for historical reporting
pcs

cluster

Cluster

TCP

ACD-LB

/

ACD-STORE

TCP

LOAD BALANCER

STORAGE

Any

LOAD BALANCER

STORAGE

ACD-LB
ACD-STORE

3121

No

Yes

Ports used for communication between the pcs clusters members.

NOT needed when no redundancy is installed.

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

ACD-TEL

UDP

PBX / SBC / SIP Trunk

Any

TELEPHONY

ACD-TEL

5060

Yes

Ports

Port used for SIP

pcs

cluster

Cluster

TCP

ACD-LB

/

ACD-STORE

TCP

LOAD BALANCER

STORAGE

Any

LOAD BALANCER

STORAGE

ACD-LB
ACD-STORE

5403

No

Yes

Ports used for communication between the pcs clusters members.

NOT needed when no redundancy is installed.

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

Cluster

UDP

ACD-LB

/

ACD-STORE

UDP

LOAD BALANCER

STORAGE

Any

LOAD BALANCER

STORAGE

ACD-LB
ACD-STORE

5404

No

Yes

Ports used for communication between the pcs clusters members.

NOT needed when no redundancy is installed.

Required on corosync nodes if corosync is configured for multicast UDP

pcs

cluster

Cluster

UDP

ACD-LB

/

ACD-STORE

UDP

LOAD BALANCER

STORAGE

Any

LOAD BALANCER

STORAGE

ACD-LB
ACD-STORE

5405

No

Yes

Ports used for communication between the pcs clusters members.

NOT needed when no redundancy is installed.

Required on all corosync nodes (needed by corosync)

UDP Listener

Hazelcast Cluster

TCP

ACD-DBM
ACD-TEL
ACD-JB
ACD-CHAT

TCPTELEPHONY
CHATSERVERS
DATABASE MASTERS
WEBSERVERS

Any

TELEPHONY
CHATSERVERS
DATABASE MASTERS
WEBSERVERS

ACD-DBM
ACD-TEL
ACD-JB
ACD-CHAT

5701 - 5801

Yes

Hazelcast cluster ports.

Load BalancersACD-LB

Web Server Access

TCP

Any

LOAD BALANCER7777

YesYesPort used for HTTP access to the HaProxy admin GUIWebservers

ACD-JB

TCPLOAD BALANCERAnyWEBSERVER

8080

Yes

Http

http server port for accessing the webserver.

REST

Servers

Service Access

TCP

ACD-

REST

LB

TCPRESTSERVERS

Any

Local + Public Network ?

ACD-REST	8091	Yes	Yes	Rest interface
pcs cluster

ACD-LB/STORE

TCP, UDP

LOAD BALANCER

STORAGETCP 9929, UDP

ACD-LB
ACD-STORE

Any

LOAD BALANCER

STORAGE

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.

WebserversACD-JBUDPWEBSERVERAny

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

WEBSERVER

20640

Yes

When changing slides in the presentation, this port is used to send the information to the other web

server

servers.

The 8-Server sends information to the web servers so that the information of the current conference call is displayed in the browser.

Webservers

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

Used for controlling telephone conferences from the web application.

ConfServer.Daemon.UDP

WEBSERVER

DATABASE MASTERS

Any

.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

ACD-TEL

20643

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

ACD-JB
ACD-REST
ACD-TEL

PLATFORM UDP LISTENER

20644

Yes

Communication from

database server

event producers to the hazelcast

(web server)

cluster on change of

agent

various status for signaling events via

SOAP

the APIs or internally.

The

platformUDPListener

PlatformUDPListener must run on the corresponding target computers.

(Preferably on localhost - only on the DB masters, not slaves).

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.

Telephony ServersACD-TELUDPPBX / SBCAnyTELEPHONY30000 - 34999YesYesPorts used for RTP

Page tree

Versions Compared

Old Version 11

New Version Current

Key

Introduction

General Information

Glossary

Ports required from External Systems

All Linux

All Linux

All Windows

All Windows

Specific Systems

Ports required Internally

All ports

Page tree

Page History

Versions Compared

Old Version 11

New Version Current

Key

Introduction

General Information

Glossary

Ports required from External Systems

All Linux

All Linux

All Windows

All Windows

Specific Systems

Ports required Internally

All ports