Drilldown: GEcTelCon

Carrier Service (1)

MPLS (1)

BYOC (1)

0. NA (1)

1. Standard (1)

None · Azure: via Microsoft Teams Direct Routing between Genesys and MS. Remote agent call forwarding only...no presence or desktop integration. · On AWS, via data over MPLS. Check individual application support in AWS. · No transport resale of any kind in Azure. · No physical circuit handoff to Genesys in Azure. Microsoft ExpressRoute may be used as virtual connection (for voice). · GEC on AWS/MPLS supports specific vendors/models. In Azure, hardphone behind customer PBX and SIP trunk...not direct registered. · ExpressRoute (BYOC) w/Azure Private Peering enables voice connectivity for unencrypted voice streams · Chrome, Firefox, or Chromium Edge · Check individual application support in AWS (e.g. IVR PaaS requires MPLS for AWS deployments). · Azure: using Private IP service. AWS: using MPLS. · "Private IP" is a direct BYOC ExpressRoute (Azure Private peering) to Genesys, but leverages non-RFC-1918 IP space. MPLS in AWS. · Azure: Use browser-based webRTC (favorable product roadmap) · Azure: requires customer SBC for TLS/SRTP encryption to Genesys SBC. Unencrypted between customer SBC and SIP softphone. · Azure: All public IP (encrypted). AWS: MPLS. · AWS only: availability varies by country, DID or Toll-free, etc... Refer to pricing guide on Genie · Available, for some capabilities refer to Capabilities tab · Any public IP transport or BYOC ExpressRoute (Microsoft peering) in Azure. No SIP trunking over public IP in AWS. · Agent is reached as PSTN endpoint. · PSTN: Bring Your Own Carrier. Consumer leg, ingress and egress. · Other