Skip to content

Preparing the network

This section provides information on the network considerations needed to install Kubernetes.

Network considerations

Sametime Meetings uses UDP on port 30000 by default for media streams. Ensure that the clients to service have UDP inbound access to this port and that outbound UDP traffic from the deployment is unrestricted.

The Sametime server must be able to connect to MongoDB with a user account which has the authority to create databases. The database is created during the installation.

STUN Service

Sametime Meetings use internet accessible STUN servers to help clients and the server negotiate media paths for the exchange of audio/video/appshare data. Public Google STUN servers are configured by default.

These addresses must be reachable by the container. If they are not, there may be issues joining meetings.

stun.l.google.com:19302
stun1.l.google.com:19302
stun2.l.google.com:19302

To change the defult STUN server, see Configuring alternate STUN servers. For further information on STUN, see the topic Session Traversal Utilities for NAT (STUN).

Ingress Controller

Kubernetes uses internal private network addresses for deployed services. Sametime uses an Ingress for incoming web traffic and either a LoadBalancer, NodePort, hostNetwork binding for media traffic. An ingress controller is required for the incoming web traffic and either the LoadBalancer or the IP address of the video node must be accessible for the media traffic.

DNS Considerations

Your Kubernetes cluster must be able to resolve the supporting servers: MongoDB, Sametime Proxy, and STUN. If DNS is unreliable or not able to resolve these hostnames to their IP addresses, complete the topic Configuring Host Aliases for Kubernetes deployments."

See Loading the Sametime images to a Docker repository.

Parent Topic: Installing Sametime in a Kubernetes environment