The following table lists the required network ports for a CoIP Platform deployment.
Component | Direction | Port | To/From | Purpose |
zCenter | Inbound | 443/tcp | 0/0 (must be accessible from all CoIP components) | Admin portal CoIP Launcher portal API gateway Control channel connection from zLink, Gateway Proxy and MSG |
Inbound | 22/tcp | Admin devices | ssh access for management (supports source IP lock) | |
Outbound | 4433/tcp | ZNS nodes | zCenter to ZNS control pathway | |
ZNS | Inbound | 443/tcp | 0/0 (must be accessible from all CoIP components) | Data plane connections from CoIP components |
Inbound | 4443/tcp | zCenter (including HA/DR) | Data plane connections from CoIP components | |
Inbound | 22/tcp | Admin devices | ssh access for management (supports source IP lock) | |
zLink | Outbound | 443/tcp | zCenter and ZNS nodes | Control channel to zCenter, and data path to ZNS nodes |
Inbound | 9797/tcp | Other zLink devices | Optional CoIP LAN transport | |
CoIP Launcher | Outbound | 443/tcp | zCenter and ZNS nodes | Control channel to zCenter, and data path to ZNS nodes |
Gateway Proxy | Outbound | 443/tcp | zCenter and ZNS nodes | Control channel to zCenter, and data path to ZNS nodes |
Outbound | all | Local network | Egress for proxied traffic onto the local network | |
Inbound | 22/tcp | Admin devices | ssh access for management (supports source IP lock) | |
MSG | Outbound | 443/tcp | zCenter and ZNS nodes | Control channel to zCenter, and data path to ZNS nodes |
Inbound | 22/tcp | Admin devices | ssh access for management (supports source IP lock) |
Comments
0 comments
Please sign in to leave a comment.