Following table shows Communication Gateway port mapping
|
|
Hosted Port |
Location |
Mapping |
Description |
|---|---|---|---|---|
|
1 |
443 |
/chat/ |
https://<hc-core>:8444 |
|
|
2 |
|
/ socket.io/ |
https://<hc-core>:8444 |
|
|
3 |
|
/ |
/agent-gadget/ |
|
|
4 |
|
/mre/ |
https://<hc-core>:8095 |
|
|
5 |
|
/mre-microservice/ |
https://<hc-core>:8447 |
|
|
6 |
|
/mre-frontend/ |
https://<hc-core>:8443/mre-frontend |
|
|
7 |
|
/eabc/ |
https://<hc-core>:8443/eabc |
|
|
8 |
|
/ecm-frontend/ |
https://<hc-core>:8443/ecm-frontend |
|
|
9 |
|
/file-engine/ |
https://<hc-core>:8495 |
|
|
10 |
|
/customer-gadget/ |
https://<communication-gateway>:8443/customer-gadget |
|
|
11 |
|
/database-connector/ |
https://<hc-core>:8450 |
|
|
12 |
|
/umm/ |
https://<hc-core>:8443/umm |
|
|
13 |
|
/agent-gadget/ |
https://<hc-core>:8443/agent-gadget |
|
Following table states ports used by Windows Deployment of Hybrid Chat
|
|
Source Host |
Destination Host |
Source Component |
Destination Component |
Source Port |
Destination Port |
Direction |
Communication Protocol |
Scope |
Description |
|---|---|---|---|---|---|---|---|---|---|---|
|
1 |
Agent Machine Browser |
Communication Gateway |
Agent Gadget |
Communication Gateway |
any |
443 (Communication Gateway → 8095, 8495, 8450) |
Unidirectional |
HTTPS |
private |
Agent Gadget connects to Mre, File Engine and Database Connector. These ports are accessible via 443 (Communication Gateway) |
|
2 |
Agent Machine Browser |
Communication Gateway |
Agent Gadget |
Communication Gateway |
any |
443 (Communication Gateway → 8444) |
Bidirectional |
HTTPS |
private |
Agent Gadget connects to Chat Server REST APIs and Socket Server. These ports are accessible via 443 (Communication Gateway) |
|
3 |
Customer Machine Browser |
Communication Gateway |
Customer Gadget |
Communication Gateway |
any |
443 (Communication Gateway → 8495, 8443) |
Unidirectional |
HTTPS |
public |
Customer Gadget connects to Mre, File Engine and Database Connector. These ports are accessible via 443 (Communication Gateway) |
|
4 |
Customer Machine Browser |
Communication Gateway |
Customer Gadget |
Communication Gateway |
any |
443 (Communication Gateway → 8444) |
Bidirectional |
HTTPS |
public |
Customer Gadget connects to Chat Server REST APIs and Socket Server. These ports are accessible via 443 (Communication Gateway) |
|
5 |
Hybrid Chat Core |
Hybrid Chat Core |
Mre |
ActiveMQ |
any |
61617 |
Bidirectional (Publisher & Subscriber) |
TCP over TLS |
private |
Mre connects to other components via OpenWire using ActiveMQ broker. This communication is private within Hybrid Chat Core machine and isn't accessible from Communication Gateway. |
|
6 |
Hybrid Chat Core |
Hybrid Chat Core |
Mre Microservice |
ActiveMQ |
any |
61615 |
Bidirectional (Publisher & Subscriber) |
TCP over TLS |
private |
Mre Microservice connects to other components via OpenWire using ActiveMQ broker. This communication is private within Hybrid Chat Core machine and isn't accessible from Communication Gateway. |
|
7 |
Hybrid Chat Core |
Hybrid Chat Core |
Communication Server |
ActiveMQ |
any |
61617 |
Bidirectional (Publisher & Subscriber) |
TCP over TLS |
private |
Communication Server connects to other components via OpenWire using ActiveMQ broker. This communication is private within Hybrid Chat Core machine and isn't accessible from Communication Gateway. |
|
8 |
Hybrid Chat Core |
Hybrid Chat Core |
Chat Server |
ActiveMQ |
any |
61615 |
Bidirectional (Publisher & Subscriber) |
TCP over TLS |
private |
Chat Server connects to other components via OpenWire using ActiveMQ broker. This communication is private within Hybrid Chat Core machine and isn't accessible from Communication Gateway. |
|
9 |
Hybrid Chat Core |
Hybrid Chat Core |
Database Connector |
ActiveMQ |
any |
61615 |
Unidirectional (Subscriber Only) |
TCP over TLS |
private |
Database Connector connects to other components via OpenWire using ActiveMQ broker. This communication is private within Hybrid Chat Core machine and isn't accessible from Communication Gateway. |
|
10 |
Communication Gateway Machine |
Communication Gateway Machine / Customer Gadget Deployment Machine |
Communication Gateway |
Customer Gadget |
any |
8443 |
Unidirectional |
HTTPS |
public |
Communication Gateway fetches Customer Gadget over 8443 which is accessible to users via 443 port. |
|
11 |
Communication Gateway Machine |
Hybrid Chat Core / Agent Gadget Deployment Machine |
Communication Gateway |
Agent Gadget |
any |
8443 |
Unidirectional |
HTTPS |
public |
Communication Gateway fetches Agent Gadget over 8443 which is accessible to users via 443 port. |
|
12 |
Communication Gateway Machine |
Hybrid Chat Core |
Communication Gateway |
Chat Server REST Client |
any |
8444 |
Unidirectional |
HTTPS |
public |
Chat Server REST Client is accessible on 8444 port from Communication Gateway. User can access it via 443 port of Communication Gateway. |
|
13 |
Communication Gateway Machine |
Hybrid Chat Core |
Communication Gateway |
Socket Server |
any |
8444 |
Bidirectional |
HTTPS |
public |
Socket Server is accessible on 8444 port from Communication Gateway. Agent Gadget and Customer Gadget access it via 443 port of Communication Gateway. |
|
14 |
Communication Gateway Machine |
Hybrid Chat Core |
Communication Gateway |
UMM |
any |
8443 |
Unidirectional |
HTTPS |
public |
UMM is accessible on 8443 port from Communication Gateway. User can access it via 443 port of Communication Gateway. |
|
15 |
Communication Gateway Machine |
Hybrid Chat Core |
Communication Gateway |
Ecm Frontend |
any |
8443 |
Unidirectional |
HTTPS |
public |
Ecm Frontend is accessible on 8443 port from Communication Gateway. User can access it via 443 port of Communication Gateway. |
|
16 |
Communication Gateway Machine |
Hybrid Chat Core |
Communication Gateway |
EABC |
any |
8443 |
Unidirectional |
HTTPS |
public |
EABC is accessible on 8443 port from Communication Gateway. User can access it via 443 port of Communication Gateway. |
|
17 |
Communication Gateway Machine |
Hybrid Chat Core |
Communication Gateway |
Mre Frontend |
any |
8443 |
Unidirectional |
HTTPS |
public |
Mre Frontend is accessible on 8443 port from Communication Gateway. User can access it via 443 port of Communication Gateway. |
|
18 |
Communication Gateway Machine |
Hybrid Chat Core |
Communication Gateway |
Mre Microservice |
any |
8447 |
Unidirectional |
HTTPS |
public |
Mre Microservice is accessible on 8443 port from Communication Gateway. User can access it via 443 port of Communication Gateway. |
|
19 |
Communication Gateway Machine |
Hybrid Chat Core |
Communication Gateway |
File Engine |
any |
8495 |
Unidirectional |
HTTPS |
public |
File Engine is accessible on 8495 port from Communication Gateway. User can access it via 443 port of Communication Gateway. |
|
20 |
Communication Gateway Machine |
Hybrid Chat Core |
Communication Gateway |
Mre |
any |
8095 |
Unidirectional |
HTTPS |
public |
Mre is accessible on 8095 port from Communication Gateway. User can access it via 443 port of Communication Gateway. |