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.

Move your Edges into the Genesys Cloud Hybrid Media Group

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. 

    1. Take an Edge out of service.
    2. Select the Hybrid Edge Group.
    3. Put the Edge back in service.
    4. Select the Site Interconnects.

To learn more click each tab.

Take an Edge out of service

The first thing that you must do is take your premises Edge out of service.

  1. Click Admin.
  2. Under Telephony, click Edges.
  3. Select the Edge Name check box next to the Edge you want to take out of service.
  4. Click Take Out-of-Service on the toolbar.
  5. When the Take Out-of-Service dialog appears, determine how you want to handle call draining.
    • By default, the Wait for the Edge to drain calls first check box is selected.
    • If you clear the Wait for the Edge to drain calls first check box, you will see a warning that informs you that all calls will be dropped immediately.
  6. Click Yes.

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.

Select the Hybrid Edge Group

After your premises Edge is out of service, you can move it into the Genesys Cloud Hybrid Media Group.

  1. From the Edge Name column, click the name of your premises Edge to open the Edit Edge page.
  2. From the Edge Group list, select Genesys Cloud Hybrid Media Group to assign it to the Edge.
  3. Click Save Edge.

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.

  1. From the Edge Name column, click the name of your premises Edge to open the Edit Edge page.
  2. In the Edge information panel that appears on the right side of the General tab, locate the Edge State.
  3. Click Put In-Service.
  4. When the Put In-Service dialog appears, Click Yes.

The Edge state changes to In-Service.

Select the Site interconnects

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.

Note: Direct interface is the default connection for BYOC Premises.

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.
  1. Click the Network tab.
  2. Under the Site Interconnects heading, take note of the port selected in the Direct Interface list. 
  3. Select that same port from the Indirect interface  list and the Cloud Proxy interface list.
  4. Click Save Interfaces.

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. 

  1. Enable Site links.
  2. Create a Location.
  3. Create a branch site.

To learn more, click each tab.

  1. Click Admin.
  2. Under Telephony, click Sites.
  3. From the Site Name column, click your premises core site to open the Edit Site page.
  4. Click the Site Links 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.

  1. Enable the Link Site toggle.
  2. Click Save Site Links.

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.

Note: The PureCloud Voice – AWS cloud site is a managed site, so you cannot view or modify it.

Create a Location

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.

  1. Click Admin.
  2. Under Directory, click Locations.
  3. Click Add Location. The Add Locations window appears.
  4. In the Name box, type the location name that you want to appear in the system.
  5. In the Address box, type the location’s street address.
  6. Continue specifying the location address by filling in the City, State/Province/Region, and Zip/Postal Code boxes.
  7. In the Country list, select your country.
  8. In the Notes box, type any additional information about this location.
  9. Click Save. The Location Details tab appears.
  10. Select Make this location available for use on sites.
  11. In the Emergency Number box, type the appropriate phone number.
  12. Select one of the following:
    • Use as the ANI only if the phone or user doesn’t have a phone number — Only use this number if no other identifying information is available.
    • Always use as the ANI — Always use this number, even if other information is available. When you select this option, any call from a phone associated with the location’s site sends this ANI to emergency services.

There are several other boxes on this page that you can fill in later.

  1. Click Save.

Create a branch site

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.

  1. Click Admin.
  2. Under Telephony, click Sites.
  3. Click Create New.
  4. Type a name in the Site Name box.
  5. From the Location list, select the location you just created.
  6. From the Time Zone list, select your time zone.
  7. Under Media Model, select Cloud.
  8. Click Create Site. The Edit Site page appears.

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.

  1. Enter a Description for your site.
  2. If you are using WebRTC, you need to select a set of media regions and specify a Relay/TURN Behavior. For more information, see Configure your site for Global Media Fabric.
  3. Click Save Site.

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.

Note: The default site is the site that handles inbound calls. The default site also handles IVR initiated transfers in which it is unclear which site to use.

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.

Configure the hybrid telephony connection

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. 

  1. Create a BYOC Cloud trunk.
  2. Add the new phone trunks.
  3. Create an Outbound Route.
  4. Add a Number Plan.
  5. Create/move phones.

Create a BYOC Cloud trunk

The 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 trunks 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. In the case of the BYOC PBX trunk type, there is only one subtype. In the case of the BYOC Carrier trunk type, there are two subtypes: One is a generic subtype that you can use for most carrier configurations. The other is a Verizon-specific subtype that you use if Verizon is your carrier.

If you need more information about any of the settings on the External trunk page, see External trunk settings.

Configure an external trunk

  1. Click Admin.
  2. Under Telephony, click Trunks.
  3. Click the External Trunks tab.
  4. Click Create New.
  5. In External Trunk Name, enter a trunk name.
  6. From the Type lists, select the type and subtype for the BYOC Cloud trunk you want to create.
  • Under Type:
    • Select BYOC Carrier from the first list.
    • Select either Generic BYOC Carrier or Verizon BYOC Carrier from the second list.
  • Under Type:
    • Select BYOC PBX from the first list.
    • Select Generic BYOC PBX from the second list
  1. Set Trunk State to In-Service.
  2. Select the appropriate trunk transport protocol from the Protocol list.

For more information, see Choose a trunk transport protocol.

  1. Under Inbound select your Number Plan Site. This setting allows you to identify the site with the number plan that you want to use. For more information, see Improve inbound call handling with the Number Plan Site feature.
  2. Configure the appropriate settings for your trunk subtype:
  • Enter an identifier in the Inbound SIP Termination Identifier box.
    • The Inbound SIP Termination Identifier is a static configuration that populates with a regionally unique identifier. This identifier directs traffic from third-party PBXs to the organization.
  • Enter a header in the Inbound SIP Termination Header box.
    • The Inbound SIP Termination Header is a custom field that contains the Termination Identifier value for inbound calls to Genesys Cloud.

  • Enter an identifier in the Inbound SIP Termination Identifier box.
    • The Inbound SIP Termination Identifier is a static configuration that populates with a regionally unique identifier. This identifier directs traffic from external Carriers to the organization.
  • Enter a header in the Inbound SIP Termination Header box.
    • The Inbound SIP Termination Header is a custom field that contains the Termination Identifier value for inbound calls to Genesys Cloud.

Note: The Inbound SIP Termination Header field is optional. This field should only be used when the standard identification methods like FQDN, TRGP and SIP DNIS are unavailable.

  • Enter an identifier in the Inbound SIP Termination Identifier box.
    • The Inbound SIP Termination Identifier is a static configuration that should be populated with a regionally unique identifier. This identifier will be used to direct traffic from Verizon to the organization.
  • The Inbound SIP Termination Header box is preconfigured with a Verizon-specific header.

  1. If you cannot use either the FQDN or the TGRP format for the inbound SIP termination identifier, enable DNIS Replacement Routing.

For more information on the Inbound settings, see Configure SIP routing for a BYOC Cloud trunk.

  1. Under Outbound, enter the appropriate identifiers in the Outbound SIP Termination FQDN, Outbound SIP TGRP Attribute, and Outbound SIP DNIS boxes to configure your outbound request URI.

For more information on the Outbound settings, see Configure SIP routing for a BYOC Cloud trunk.

  1. To specify any SIP Servers or Proxies enter a value in the Hostname or IP Address box, a port number in the Port box, and click Plus . 
  2. Choose the appropriate Digest Authentication setting.
    • If you enable Digest Authentication, you need to specify the associated Realm, and the User Name, and Password to use as the authentication credentials.
  3. Under Calling, specify the Caller Address and Caller Name for the trunk and then use the Prioritized Caller Selection to specify the location from which and order in which you want to display caller ID information to the call recipient.
  1. Under SIP Access Control, you can build a list of IP or CIDR addresses to which you want to permit SIP access. To do so,  enter an address and click Plus .
  2. If you are configuring a BYOC PBX trunk, you'll see the PBX Passthrough setting.
    • Enable this setting if you want to allow your PBX to pass calls intended for the PSTN directly through Genesys Cloud.

For more information, see Configure PBX passthrough for a BYOC trunk.

  1. If you are configuring a Verizon BYOC Carrier trunk subtype, you need to configure a few Verizon-specific settings in the Custom SIP headers section.

  • Under External Trunk Configuration, expand the Protocol section.
  • Under Outbound, in the Custom SIP headers section, you'll find three Verizon-specific Headers:
    • X-VZ-CSP-Domain
    • X-VZ-CSP-Customer-Identifier
    • X-VZ-CSP-Leg-Type
  • You need to work with your Verizon representative to find the correct values to enter into the Value boxes for X-VZ-CSP-Domain and X-VZ-CSP-Customer-Identifier headers.
  • The Value box for the X-VZ-CSP-Leg-Type header is automatically filled in with the value of "agent" and you should leave this box as is.

For more information, see Configure Custom SIP headers.

  1. Click Save External Trunk.

For more information about any of the settings on the Create/Edit External Trunk page, see External trunk settings. 

Add the new phone trunks

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.

  1. Click Admin.
  2. Under Telephony, click Edge Groups.
  3. Select the Genesys Cloud Hybrid Media Group.
  4. Under Phone Trunks, click Select Phone Trunk and select the Genesys Cloud – CDM SIP Phone Trunk.
  5. Repeat step 4 and select the Genesys Cloud – CDM WebRTC Phone Trunk.
  6. Click Save Edge Group.

Create an Outbound Route

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.

  1. Click Admin.
  2. Under Telephony, click Sites.
  3. Locate and click your site on the Site Name list.
  4. Click the Outbound Routes tab.
  5. Click New Outbound Route.
  6. Enter an outbound route Name and a Description.
  7. From the Classifications list, select a classification.
  8. From the Select an External Trunk list, select the appropriate trunks.
  9. If you select more than one external trunk, you can specify a Distribution Pattern to define how outgoing calls are routed to available trunks.
    • Select Sequential to route outgoing calls to each trunk in succession beginning with the first trunk.

(If the first trunk has reached its capacity or the call is rejected, then outgoing calls are routed to the second trunk and so on.)

    • Select Random to route outgoing calls to a randomly selected trunk.

(You can use this option to essentially load balance outgoing calls across all available trunks.)

  1. To enable the outbound route, enable the State setting.
  2. Click Save Outbound Routes.OutboundRouteV2

Add a Number Plan

  1. Click Admin.
  2. Under Telephony, click Sites.
  3. Select your site from the Site Name list.
  4. Click the Number Plans tab.
  5. Click New Number Plan.
  6. Enter a name in the Number Plan Name box.
  7. Select one of the available match types from the Match Type list.
  8. Depending on what match type you select, enter the required information.

  • Enter a number or a range of numbers in Number of Digits.

  • Enter a range of numbers in E.164 format in the boxes.
  • Click + to add the range to the Numbers box.

For example, you might enter +13177151000 in the first box and +13177152000 in the second box.

Select one of the options:

  • Match any country code except the current Site's country code
  • Match only the country codes specified below
    • Enter the appropriate digits in the Match Country Codes box.

  • There is nothing to configure when you select the Intra-Country match type.

  • Enter comma delimited numbers or a range of numbers in the Numbers box.

  • Enter a regular expression in the Match Expression box.
  • Enter a normalized number expression in the Normalized Number Expression box.

  1. Select the correct classification or enter a new classification in the Classification list.
  2. Click Save Number Plans.

Note: Drag and drop the number plans to change the order of the list. Genesys Cloud processes number plans from top to bottom.

Create new/move existing phones

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.

Note: While most Polycom phones that Genesys Cloud supports are compatible with BYOC Cloud, there are few that are not. For more information, see Managed phones: models and features matrix.

Create phones

To create a new Polycom phone, see:

To create a new WebRTC phone, see:

Move phones

To move existing phones:

  1. Click Admin.
  2. Under Telephony, click Phone Management.
  3. Click the Phones tab.
  4. Select the phone you want to move.
  5. From the Site list, select your cloud branch site.
  6. Click Save Phone.