View source for WebRTC/Current/WebRTCPEGuide/Architecture

{{ArticlePEServiceArchitecture
|ServiceId=12d65e68-20aa-4cf7-848f-cc4358c67b25
|IntroductionText=For more information about the overall architecture of Genesys Private Edition Cloud, see: {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=Architecture|display text=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.
|Image=Pe_webrtc_architecture.png
|PEConnections={{PEConnections
|Connection=1
|SourceType=Other
|SourceOther=Agents
|DestinationType=Third Party
|DestinationThirdParty=f1d380bf-42b1-4b67-9d27-d574bad90c86
|Protocol=04ed835e-0e34-4114-b757-855af1b3bef3
|Port=443
|Purpose=RTP connection from WebRTC agents to load balancer.
|Classification=b2dff270-19d6-4258-a380-da06305a143c
}}{{PEConnections
|Connection=2
|SourceType=Other
|SourceOther=Agents
|DestinationType=Third Party
|DestinationThirdParty=f1d380bf-42b1-4b67-9d27-d574bad90c86
|Protocol=7b607959-2359-49a7-aedd-81bf9140357f
|Port=443
|Purpose=STUN\TURN connection from WebRTC agents to load balancer.
|Classification=b2dff270-19d6-4258-a380-da06305a143c
}}{{PEConnections
|Connection=3
|SourceType=Other
|SourceOther=Agents
|DestinationType=Other
|DestinationOther=AGIC
|Protocol=53fca8fe-9174-417f-bff9-416ea8119f9e
|Port=443
|Purpose=Used for WebRTC signaling.
|Classification=b2dff270-19d6-4258-a380-da06305a143c
}}{{PEConnections
|Connection=4
|SourceType=Other
|SourceOther=Load balancer
|DestinationType=Included Service
|DestinationIncludedService=e21de850-166d-4046-9755-357ff3d4fa05
|Protocol=04ed835e-0e34-4114-b757-855af1b3bef3
|Port=3478
|Purpose=RTP connection from Load Balancer to the Coturn Server.
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
}}{{PEConnections
|Connection=5
|SourceType=Other
|SourceOther=Load Balancer
|DestinationType=Included Service
|DestinationIncludedService=e21de850-166d-4046-9755-357ff3d4fa05
|Protocol=7b607959-2359-49a7-aedd-81bf9140357f
|Port=3478
|Purpose=STUN\TURN connection for SRTP data transmission.
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
}}{{PEConnections
|Connection=6
|SourceType=Other
|SourceOther=AGIC
|DestinationType=Included Service
|DestinationIncludedService=d703e174-b039-43c9-8859-e25b3a7feb22
|Protocol=53fca8fe-9174-417f-bff9-416ea8119f9e
|Port=8086
|Purpose=Used for WebRTC signaling.
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
}}{{PEConnections
|Connection=7
|SourceType=Included Service
|SourceIncluded=d703e174-b039-43c9-8859-e25b3a7feb22
|DestinationType=Included Service
|DestinationIncludedService=2993dc16-58d0-4984-a3ca-0fcf959a79a4
|Protocol=53fca8fe-9174-417f-bff9-416ea8119f9e
|Port=80
|Purpose=Enables authentication of GWS client with WebRTC agents.
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
}}{{PEConnections
|Connection=8
|SourceType=Included Service
|SourceIncluded=e21de850-166d-4046-9755-357ff3d4fa05
|DestinationType=Included Service
|DestinationIncludedService=d703e174-b039-43c9-8859-e25b3a7feb22
|Protocol=04ed835e-0e34-4114-b757-855af1b3bef3
|Port=40000-43000
|Purpose=RTP connection from the Coturn Server to the WebRTC Gateway.
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
}}{{PEConnections
|Connection=9
|SourceType=Included Service
|SourceIncluded=d703e174-b039-43c9-8859-e25b3a7feb22
|DestinationType=Included Service
|DestinationIncludedService=e21de850-166d-4046-9755-357ff3d4fa05
|Protocol=04ed835e-0e34-4114-b757-855af1b3bef3
|Port=40000-64000
|Purpose=RTP connection from the WebRTC Gateway to the Coturn Server.
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
}}{{PEConnections
|Connection=10
|SourceType=Included Service
|SourceIncluded=d703e174-b039-43c9-8859-e25b3a7feb22
|DestinationType=Other
|DestinationOther=SBC
|Protocol=04ed835e-0e34-4114-b757-855af1b3bef3
|Port=10000-65535
|Purpose=RTP connection from the WebRTC Gateway to SBC.
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
}}{{PEConnections
|Connection=11
|SourceType=Included Service
|SourceIncluded=d703e174-b039-43c9-8859-e25b3a7feb22
|DestinationType=Other
|DestinationOther=Shared MCP
|Protocol=04ed835e-0e34-4114-b757-855af1b3bef3
|Port=20000-45000
|Purpose=RTP connection from the WebRTC Gateway to MCP.
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
}}{{PEConnections
|Connection=12
|SourceType=Other
|SourceOther=MCP
|DestinationType=Included Service
|DestinationIncludedService=d703e174-b039-43c9-8859-e25b3a7feb22
|Protocol=04ed835e-0e34-4114-b757-855af1b3bef3
|Port=44000-47000
|Purpose=RTP connection from MCP to the WebRTC Gateway.
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
}}{{PEConnections
|Connection=13
|SourceType=Other
|SourceOther=MCP
|DestinationType=Other
|DestinationOther=SBC
|Protocol=04ed835e-0e34-4114-b757-855af1b3bef3
|Port=10000-65535
|Purpose=RTP connection from MCP to SBC.
|Classification=f12b7433-c91c-4da4-bd6e-445684e38560
}}{{PEConnections
|Connection=14
|SourceType=Other
|SourceOther=SBC
|DestinationType=Other
|DestinationOther=MCP
|Protocol=04ed835e-0e34-4114-b757-855af1b3bef3
|Port=20000-45000
|Purpose=RTP connection from SBC to MCP.
|Classification=b2dff270-19d6-4258-a380-da06305a143c
}}{{PEConnections
|Connection=15
|SourceType=Other
|SourceOther=SBC
|DestinationType=Included Service
|DestinationIncludedService=d703e174-b039-43c9-8859-e25b3a7feb22
|Protocol=04ed835e-0e34-4114-b757-855af1b3bef3
|Port=44000-47000
|Purpose=RTP connection from SBC to the WebRTC Gateway.
|Classification=b2dff270-19d6-4258-a380-da06305a143c
}}{{PEConnections
|Connection=16
|SourceType=Service
|SourceService=4d384b74-f61d-48f7-bace-30048213bf99
|DestinationType=Included Service
|DestinationIncludedService=d703e174-b039-43c9-8859-e25b3a7feb22
|Protocol=84e296bd-6b37-48c4-af34-3a3c84089000
|Port=5070
|Purpose=Used for SIP signaling.
|Classification=b2dff270-19d6-4258-a380-da06305a143c
}}{{PEConnections
|Connection=17
|SourceType=Included Service
|SourceIncluded=d703e174-b039-43c9-8859-e25b3a7feb22
|DestinationType=Service
|DestinationService=4d384b74-f61d-48f7-bace-30048213bf99
|Protocol=84e296bd-6b37-48c4-af34-3a3c84089000
|Port=5060
|Purpose=Allows SIP signaling from the WebRTC Gateway to the tenants.
|Classification=2fb71bb4-3a8f-43ce-9b16-9045d3af916f
}}
}}