Drilldown: GEcTelCon

Jump to: navigation, search
GEcTelCon

Use the filters below to narrow your results.

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

Showing below up to 1 result in range #1 to #1.

View (previous 250 | next 250) (20 | 50 | 100 | 250 | 500)


View (previous 250 | next 250) (20 | 50 | 100 | 250 | 500)

Retrieved from "https://all.docs.genesys.com/Special:Drilldown/GEcTelCon (2022-07-06 19:23:33)"