Required Port Configuration

Database

UDP Listener

Load Balancers

pcs cluster

Samba Fileshare

pcs cluster

jtel Support

Remote Access to Linux Systems.

jtel Support

Remote Access to Windows Systems.

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.

LOAD BALANCER 

STORAGE

LOAD BALANCER

STORAGE

Ports used for communication between the pcs clusters 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.

LOAD BALANCER

STORAGE

LOAD BALANCER

STORAGE

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.

LOAD BALANCER

STORAGE

LOAD BALANCER

STORAGE

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.

LOAD BALANCER

STORAGE

LOAD BALANCER

STORAGE

Ports used for communication between the pcs clusters members.

Required on corosync nodes if corosync is configured for multicast UDP

LOAD BALANCER

STORAGE

LOAD BALANCER

STORAGE

Ports used for communication between the pcs clusters members.

Required on all corosync nodes (needed by corosync)

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

DATABASE MASTERS
TELEPHONY
WEBSERVERS
CHATSERVERS

DATABASE MASTERS
TELEPHONY
WEBSERVERS
CHATSERVERS

LOAD BALANCER

STORAGE

LOAD BALANCER

STORAGE

A setting can be found in the parameters:

ConfServer.WebServer.UDP.Port

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.

Webservers

(connection is initiated by web application in each case)

A setting can be found in the parameters:

ConfServer.Daemon.UDP.Port

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

TELEPHONY (DAEMON)

Yes

A setting can be found in the parameters:

Portal.Daemon.TTS.UDP.Address

Portal.Daemon.TTS.UDP.Port

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

ACD-DBM

ACD-JB

WEBSERVER

DATABASE MASTERS

A setting can be found in the parameters:

ACD.UDP.MediaEventsListener.Address

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

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

WEBSERVER

Yes

A setting can be found in the parameters:

ACD.UDP.Daemon.Address

ACD.UDP.Daemon.Port

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.

Yes

A setting can be found in the parameters:

dialler.8Servers.IPs

dialler.ClickToCall.UDP.8ServerCommand.Port

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.

Yes

A setting can be found in the parameters:

dialler.ClickToCall.UDP.Connector.Host

dialler.ClickToCall.UDP.Connector.Port

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.

A setting can be found in the parameters:

Portal.AgentCallControl.UDP.Address

Portal.AgentCallControl.UDP.Port

IP address and port of the PBX-Connector, if commands such as "Answer" are supported via the PBX-Connector.

A setting can be found in the parameters:

Portal.JTELTAPIServer.UDP.Address

Portal.JTELTAPIServer.UDP.Port

IP address and port of the JTELTAPI forwarding service, when using the connector with TAPI / ECSTA.(