Loading...
Loading...
Loading...
When you are ready to completely convert your BYOC Premises organization into a hybrid media organization, you will move your existing Edges into the Genesys Cloud Hybrid Media Group and enable the Site Links.
You need to move all of your Edges from your existing Edge Groups into the Genesys Cloud Hybrid Media Group. However, if you have multiple Edges, you need to understand that you can only move one premises Edge at a time.
Note: Before you decide to begin moving your Edges into the Hybrid Media Group, you must be sure that you are able to complete the entire operation from start to finish. Furthermore, if you have multiple sites, each containing Edges, you will need to move all of the Edges in one site before you begin moving the Edges in your other sites.
The reason is twofold. First, if you have multiple premises Edges, the operation may take a while to complete. Second, once you begin the move, your organization will be segmented, which essentially means that the part that you move to the hybrid media group will not be able to communicate with the part that remains in your existing Edge group. Therefore, it will be to your benefit to begin the move during off hours to ensure that you can perform the operation from start to finish without disrupting business operations.
The basic steps for this part of the operation are as follows.
To learn more click each tab.
The first thing that you must do is take your premises Edge out of service.
If you enabled the call draining feature, you’ll see the Edge state change to Draining calls along with the number of calls remaining. After the calls are drained or the timeout period elapses, you’ll see the Edge state change to Out-of-Service.
If you disabled the call draining feature, you’ll immediately see the Edge state change to Out-of-Service.
After your premises Edge is out of service, you can move it into the Genesys Cloud Hybrid Media Group.
Put the Edge back in service
After you move a premises Edge into the Genesys Cloud Hybrid Media Group, you can put it back into service.
The Edge state changes to In-Service.
After you put a premises Edge in service, you must make sure that the Site interconnects are configured. Under hybrid media, site interconnects allow Edges in various sites to communicate with each other. For each type of Site Interconnect that you want to enable, you select the interface that you want to use. There are three types of Site Interconnects as described in the table.
| Site Interconnects | Description |
|---|---|
| Direct interface | This is a connection where each Edge has a private IP address that they use to communicate with each other. The Direct interface allows Edges on the same LAN to communicate with each other. |
| Indirect interface | This is a connection between Edges that uses NAT traversal via a 1:1, public to private IP address mapping on the Edge interface. The Indirect interface allows an Edge to communicate with other Edges outside the NAT, |
| Cloud Proxy interface | This is a connection that uses WebRTC technology in the cloud to broker connectivity between Edge devices and the cloud. The main use case for Edge devices to communicate with the cloud media services. Essentially they reach out from the Edge through the firewall, just like a WebRTC client does and media is negotiated just like a WebRTC client. This makes this connection incredibly resilient. If there is no direct or indirect path between Edges, you can use the Cloud-Proxy interface. |
After you move your premises Edges into the Genesys Cloud Hybrid Media Group, you can create a connection between your premises site and the new cloud site by enabling the Site Links feature. You’ll then create a new location and a cloud branch site.
The basic steps for this part of the operation are as follows.
To learn more, click each tab.
When you select the Site Links tab, you’ll see a list of the sites in your organization. This list includes the new PureCloud Voice – AWS cloud core site and any branch sites that you have in your premises organization. You’ll also see an error message that indicates the connections between your default premises site and the PureCloud Voice – AWS site are disabled.
When you enable the Link site, you’ll now have a connection between your core premises site and the core cloud site (PureCloud Voice – AWS). Once the link is enabled, your core premises site has access to all the resources in the core cloud site. Likewise, the core cloud site has access to all the resources in the core premises site.
After you enable hybrid media, the process creates a placeholder location called Default PCV Location. This placeholder location is tied to the PureCloud Voice – AWS cloud site, which is a managed site that you cannot view or modify. As such, you need to create a new Location.
There are several other boxes on this page that you can fill in later.
After you create a new location, you must create a cloud branch site and connect it to your new location. You then select your new cloud branch site as the default site.
You’ll see that the Edit Edge page contains five tabs titled General, Number Plans, Outbound Routes, Site Links, and Simulate Call. You continue the branch site configuration on the General and Site Links tabs. You’ll configure the settings on the Number Plans and Outbound Routes tabs later.
General
You continue the initial site configuration on the General tab.
In the Site information panel, you’ll see that the Site Type is identified as a Branch Site and that the Media Model is Cloud. Next to the Default Site, click Make this Site my default Site.
For more information, see Sites overview.
Site Links
If you click the Site Links tab, a message appears that indicates that Site links can only be configured between core sites.
If you return to the General tab and click the Show Topology in the Site information panel, you see a graphical representation of the links between your core site and branch site.
After you enable Site links, create a new location, and create a branch site, you can configure the rest of your hybrid telephony connection.
The basic steps for this part of the operation are as follows.
The Create External Trunks page has two sections. The upper section contains the base settings needed for an External Trunk. The lower section, which consists of a series of collapsible sections, contains other settings that you can use to refine your external trunk configuration.
Genesys Cloud recommends that you rely on the base BYOC Cloud trunk settings described in this article. However, if your carrier has other requirements, you can use the additional settings to refine your external trunk configuration. For more information, see Configure advanced external trunk settings.
There are two types of BYOC Cloud trunks (BYOC Carrier or BYOC PBX) that you can select depending on how your telephony system is set up. Each trunk type also has a subtype that is designed to narrow down the settings that are required for that type of trunk. For the BYOC PBX trunk type, there is only one subtype. For the BYOC Carrier trunk type, there are three subtypes: One is a generic subtype that you can use for most carrier configurations. The second is a Verizon-specific subtype that you use if Verizon is your carrier. The third is a WhatsApp-specific subtype that you choose if you are using WhatsApp Business Calling.
If you need more information about any of the settings on the External trunk page, see External trunk settings.
For more information about the Inbound settings, see Configure SIP routing for a BYOC Cloud trunk.
For more information about the Outbound settings, see Configure SIP routing for a BYOC Cloud trunk.
For more information, see Use the Prioritized caller ID locations feature to configure caller ID information.
For more information, see Configure PBX passthrough for a BYOC trunk.
For more information, see Configure Custom SIP headers.
For more information about any of the settings on the Create/Edit External Trunk page, see External trunk settings.
After you create your BYOC Cloud trunk, you can add the two new phone trunks (Genesys Cloud – CDM SIP Phone Trunk and Genesys Cloud – CDM WebRTC Phone Trunk) to the Genesys Cloud Hybrid Media Group.
After you create a BYOC Cloud trunk and add the new phone trunks to the Genesys Cloud Hybrid Media Group, you can add an outbound route to your new cloud branch site.
For example, you might enter +13177151000 in the first box and +13177152000 in the second box.
Select one of the options:
You can create new phones and add them to the cloud branch site or you can move existing phones from the premises site to the cloud branch site. Either way, you must keep phone compatibility in mind. AudioCodes phones, Genesys branded phones, and the PureCloud Softphone are not compatible with BYOC Cloud.
This means that if you are creating new phones for your cloud branch site, you can only create Polycom or WebRTC phones. If you are moving phones from the premises site to the cloud branch site, you can only move Polycom or WebRTC phones.
To create a new Polycom phone, see:
To create a new WebRTC phone, see:
To move existing phones:
Get user feedback about articles.