Learn about WebRTC Media Service architecture.
For more information about the overall architecture of Genesys Private Edition Cloud, see: Architecture.
Genesys Web Services (GWS) provides Tenant specific information to WebRTC. Workspace Web Edition (WWE) Agent Desktop retrieves all the required information such as tenant ID and WebRTC locations from GWS and sends them to WebRTC.
For information about the overall architecture of Genesys Multicloud CX private edition, see the high-level Architecture page.
See also High availability and disaster recovery for information about high availability/disaster recovery architecture.
Architecture diagram — Connections
The numbers on the connection lines refer to the connection numbers in the table that follows the diagram. The direction of the arrows indicates where the connection is initiated (the source) and where an initiated connection connects to (the destination), from the point of view of WebRTC Media Service as a service in the network.
The connection numbers refer to the numbers on the connection lines in the diagram. The Source, Destination, and Connection Classification columns in the table relate to the direction of the arrows in the Connections diagram above: The source is where the connection is initiated, and the destination is where an initiated connection connects to, from the point of view of WebRTC Media Service as a service in the network. Egress means the WebRTC Media Service service is the source, and Ingress means the WebRTC Media Service service is the destination. Intra-cluster means the connection is between services in the cluster.
|Connection||Source||Destination||Protocol||Port||Connection Classification||Data that travels on this connection|
|1||Agents||Load balancer||RTP/RTCP||443||Ingress||RTP connection from WebRTC agents to load balancer.|
|2||Agents||Load balancer||TURN/STUN||443||Ingress||STUN\TURN connection from WebRTC agents to load balancer.|
|3||Agents||AGIC||HTTP||443||Ingress||Used for WebRTC signaling.|
|4||Load balancer||WebRTC CoTurn Service||RTP/RTCP||3478||Intra-cluster||RTP connection from Load Balancer to the Coturn Server.|
|5||Load Balancer||WebRTC CoTurn Service||TURN/STUN||3478||Intra-cluster||STUN\TURN connection for SRTP data transmission.|
|6||AGIC||WebRTC Gateway Service||HTTP||8086||Intra-cluster||Used for WebRTC signaling.|
|7||WebRTC Gateway Service||GWS Voice Service||HTTP||80||Intra-cluster||Enables authentication of GWS client with WebRTC agents.|
|8||WebRTC CoTurn Service||WebRTC Gateway Service||RTP/RTCP||40000-43000||Intra-cluster||RTP connection from the Coturn Server to the WebRTC Gateway.|
|9||WebRTC Gateway Service||WebRTC CoTurn Service||RTP/RTCP||40000-64000||Intra-cluster||RTP connection from the WebRTC Gateway to the Coturn Server.|
|10||WebRTC Gateway Service||SBC||RTP/RTCP||10000-65535||Intra-cluster||RTP connection from the WebRTC Gateway to SBC.|
|11||WebRTC Gateway Service||Shared MCP||RTP/RTCP||20000-45000||Intra-cluster||RTP connection from the WebRTC Gateway to MCP.|
|12||MCP||WebRTC Gateway Service||RTP/RTCP||44000-47000||Intra-cluster||RTP connection from MCP to the WebRTC Gateway.|
|13||MCP||SBC||RTP/RTCP||10000-65535||Intra-cluster||RTP connection from MCP to SBC.|
|14||SBC||MCP||RTP/RTCP||20000-45000||Ingress||RTP connection from SBC to MCP.|
|15||SBC||WebRTC Gateway Service||RTP/RTCP||44000-47000||Ingress||RTP connection from SBC to the WebRTC Gateway.|
|16||Voice Microservices||WebRTC Gateway Service||SIP/UDP||5070||Ingress||Used for SIP signaling.|
|17||WebRTC Gateway Service||Voice Microservices||SIP/UDP||5060||Egress||Allows SIP signaling from the WebRTC Gateway to the tenants.|