Versions Compared

Old Version 5

changes.mady.by.user jtel Support

Saved on

compared with

New Version Current

changes.mady.by.user jtel Support

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

ComponentsHostname (Alias)
Name
Function
TELEPHONY
Telephony ServersACD-TELThe telephony servers of the system
DATABASES
DatabaseACD-DBM + ACD-DBS + ACD-DBRThe database masters and slaves
DATABASE MASTERS
+ reporting slaves

Database

UDP Listener

ACD-DBMThe database masters 
LOAD BALANCER

Load Balancers

pcs cluster

ACD-LBThe load balancers containing the haproxy
Webservers
WEBSERVER
ACD-JBThe webservers
STORAGE

Samba Fileshare

pcs cluster

ACD-STOREThe storage servers containing the samba fileshare
CHATSERVER
Chat ServersACD-CHATServers which the Chat services are running on
RESTSERVER
REST ServersACD-RESTServers 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)
ProtocolSourcePort(s)DestinationPort(s)
Internal CommunicationExternal CommunicationDescriptionACD.UDP.Daemon.AddressACD.UDP.Daemon.PortUDP

WEBSERVER

AnyTELEPHONY (DAEMON)20645YesNo

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 LISTENER20644No

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)ACD.UDP.Webserver.SenderPortUDPWEBSERVERAny

 TELEPHONY
(DAEMON)

20700Communication between web server and 8-Server for control of calls. Messages are directed to ACD.Daemon.UDP.r5.(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.

ConfServer.WebServer.UDP.Address

(Configure all, seperate with colon and no spaces)

ConfServer.WebServer.UDP.PortUDP

TELEPHONY

WEBSERVER

AnyWEBSERVER20640

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

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

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.

All ports

Description
Remote AccessTCP

jtel Support

AnyAll Linux22

SSH Remote Access to Linux Systems.

All Windows

DescriptionProtocolSourcePort(s)DestinationPort(s)Description
Remote AccessTCP + UDP

jtel Support

AnyAll Windows3389

RDP remote Access to Windows Systems.

Specific Systems

DescriptionProtocolSourcePortDestinationPorts / PortrangeDescription
http AccessTCPAny (jtel Support)AnyACD-LB80http Access to Webservers and SOAP / REST APIs via Load-Balancer. Will redirect to 443 (https) automatically if https with a certificate are configured.
https AccessTCPAny (jtel Support)AnyACD-LB443https Access to Webservers and SOAP / REST APIs via Load-Balancer.
Samba FileshareTCPAny Reporting API usersAnyACD-STORE445Access to the Samba Fileshare of the system required by Reporting API users if own reports are to be created.
Websocket ChatTCPAnyAnyACD-LB3000The chat-server port if http is being used to access the chat server from external.
Websocket ChatTCPAnyAnyACD-LB3003The chat-server port if https is being used to access the chat server from external.
Reporting APITCPAny Reporting API usersAny

ACD-LB

3306-3308

Used to provide reporting API access to the database for BI applications.

SIPTCP / UDPPBX / SBC / SIP TrunkAnyACD-TEL5060SIP communication port for telephony signalling.
SIPSTCP PBX / SBC / SIP TrunkAnyACD-TEL5061SIPS communication port for telephony signalling.
haproxy WebTCPAny (jtel Support)AnyACD-LB7777Port used for HTTP access to the HaProxy admin GUI.
RTPUDPPBX / SBC / SIP TrunkAnyACD-TEL30000-34999RTP 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.


DescriptionProtocolSourcePortDestinationPort(s)
ComponentHostProtocolSourcePortDestinationPorts / Portrange
Required for Non-Redundant SystemsRequired for Redundant SystemsDescription
pcs
cluster
ClusterTCP

ACD-LB

/STORETCP


ACD-STORE

LOAD BALANCER 

STORAGESTORAGE

Any

LOAD BALANCER

ACD-LB
ACD-STORE

2224NoYes

Ports used for communication between the pcs

clusters

cluster members.

NOT needed when no redundancy is installed.

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 ServerTCPACD-LBAnyACD-CHAT3000YesYesWebsocket for chat server
Database AccessTCPAnyAnyACD-LB3306NoYesRedirect port to master database
Database AccessTCPAnyAnyACD-LB3307NoYesRedirect port to slave database used for real-time reporting
Database AccessTCPAnyAnyACD-LB3308NoYesRedirect port to slave database used for historical reporting
pcs ClusterTCP

ACD-LB
ACD-STORE

Any

ACD-LB
ACD-STORE

pcs clusterACD-LB/STORETCP

LOAD BALANCER

STORAGE

Any

LOAD BALANCER

STORAGE

3121NoYes

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 ServersUDPPBX / SBC / SIP TrunkAnyACD-TEL5060YesYesPort used for SIP 
pcs ClusterTCP

ACD-LB
ACD-STORE

Any

ACD-LB
ACD-STORE

pcs clusterACD-LB/STORETCP

LOAD BALANCER

STORAGE

Any

LOAD BALANCER

STORAGE

5403NoYes

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 ClusterUDP
pcs cluster

ACD-LB

/STOREUDP

LOAD BALANCER

STORAGE

Any


ACD-STORE

Any

ACD-LB
ACD-STORE

LOAD BALANCER

STORAGE

5404NoYes

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 ClusterUDP
pcs cluster

ACD-LB

/STOREUDP


ACD-STORE

LOAD BALANCER

STORAGE

Any

LOAD BALANCER

STORAGE

ACD-LB
ACD-STORE

5405NoYes

Ports used for communication between the pcs clusters members.

NOT needed when no redundancy is installed.

Samba Fileshare

Required on all corosync nodes (needed by corosync)

Hazelcast ClusterTCP

ACD-DBM
ACD-

STORE

TEL

TCPSTORAGE

ACD-JB
ACD-CHAT

Any
ALL

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

5701 - 5801
445
YesYes

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.

Hazelcast cluster ports. 
Web Server AccessTCPAnyAnyACD-JB8080
DatabaseACD-DBM/DBS/DBRTCPDATABASESAny

ALL

3306
YesYes
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.UDP ListenerACD-DBMTCPDATABASE MASTERSAny

TELEPHONY
CHATSERVERS
DATABASE MASTERS
WEBSERVERS

5701 - 5801YesYesPorts used by the UDP Listener to send and receive UDP commands from the other hazelcast cluster members.WebserversACD-JBTCPWEBSERVERAny

TELEPHONY
CHATSERVERS
DATABASE MASTERS
WEBSERVERS

5701 - 5801YesYesPorts used by the UDP Listener to send and receive UDP commands from the other hazelcast cluster members.WebserversACD-JBTCPLOAD BALANCERAnyWEBSERVER8080YesYes?WebserversACD-JBWEBSERVERAny22YesYesSSH PortWebserversACD-JBUDPWEBSERVERAny
http server port for accessing the webserver.
REST Service AccessTCPACD-LBAnyACD-REST8091YesYesRest interface
pcs clusterTCP, UDP

ACD-LB
ACD-STORE

Any

ACD-LB
ACD-STORE

9929NoYesRequired 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 ServersUDPACD-TELAnyACD-TEL20202NoYesIf building a cluster with more than one telephony server, this is the broadcast port used for interchassis communication and discovery.
Web Server CommunicationUDPACD-JBAnyACD-JB
WEBSERVER
20640YesYes

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.

WebserversACD-JBUDPWEBSERVERAny?20642YesYes?WebserversACD-JBUDPWEBSERVERAnyPLATFORM UDP LISTENER

This setting can be found in the parameters:

ConfServer.WebServer.UDP.Port

Webserver conference control of telephony

UDPACD-JBAnyACD-TEL20641
20644
YesYes

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).

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 generationUDPAnyAny

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 APIsUDP

Any

Any

ACD-JB
ACD-REST
ACD-TEL

20644YesYes

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 controlUDP

Any

AnyACD-TEL20645

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 controlUDPAnyAnyACD-TEL40404YesYes

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 connectorUDPACD-JBAnyACD-TEL40406

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-TELICMPv4TELEPHONYAnyYesYesTelephony ServersACD-TELTCPTELEPHONYAny

TELEPHONY
CHATSERVERS
DATABASE MASTERS
WEBSERVERS

5701 - 5801YesYesPorts used by the UDP Listener to send and receive UDP commands from the other hazelcast cluster members.Telephony ServersACD-TELUDPTELEPHONYAnyPBX / SBC30000 - 34999YesYesPorts used for RTP  Telephony ServersACD-TELUDPTELEPHONYAnyPBX / SBC5060YesYesPorts used for SIP Telephony ServersACD-TELUDPTELEPHONYAnyNONE1 - 65535YesYesLocal UDP PortsLoad BalancersACD-LBTCPLOAD BALANCERAnyLocal Network ?80YesYesPort used for HTTP accessLoad BalancersACD-LBTCPLOAD BALANCERAnyLocal Network ?443YesYesPort used for HTTPS accessLoad BalancersACD-LBTCPLOAD BALANCERAnyLocal Network ?7777YesYesPort used for HTTP access to the HaProxy admin interfaceLoad BalancersACD-LBTCPLOAD BALANCERAny?3306NoYes?Load BalancersACD-LBTCPLOAD BALANCERAny?3307NoYes?Load BalancersACD-LBTCPLOAD BALANCERAny?3308NoYes?Chat ServersACD-CHATTCPCHATSERVERSAnyTELEPHONY
CHATSERVERS
DATABASE MASTERS
WEBSERVERS5701 - 5801YesYesPorts used by the UDP Listener to send and receive UDP commands from the other hazelcast cluster members.Chat ServersACD-CHATTCPCHATSERVERSAny?3000YesYes?REST ServersACD-RESTTCPRESTSERVERSAnyLocal + Public Network ?8091YesYes?