Convert BYOC Premises to hybrid media

Genesys Cloud Hybrid Media Beta

Prerequisites

  • Telephony > Plugin > All permission
  • Minimum Edge software version: 1.0.0.10590 

If you are using BYOC Premises as your telephony connection option and would like to be able take advantage of the cloud-only features available in BYOC Cloud or Genesys Cloud Voice, you can do so with our new hybrid telephony connection option. With this new option, you can create a hybrid media organization where part of your organization is in the cloud using a BYOC Cloud telephony connection and the other part remains on premises, using a BYOC Premises telephony connection. Or, you can use the hybrid telephony connection option to move your entire BYOC Premises organization to BYOC Cloud.

Apply for the beta program

If you are not currently in the Hybrid Media Orgs beta program and would like to be considered for participation, click here to learn more

Overview

Converting a BYOC Premises organization to a hybrid media organization is made possible by two key features and is a three phase operation. The two key features are Hybrid Media Groups and Site Links. The three phases consist of: 1) Enabling the hybrid telephony connection. 2) Moving your Edges into a new Edge Group called the Hybrid Media Group. 3) Enabling and configuring Site Links.

Hybrid telephony connection

The first phase during the beta program is performed by us and that is to enable the hybrid telephony connection for your organization. Once we do that, several new components, including the key features, are added to your organization. These new components will not come into play until you perform the steps in the second and third phases. Until you do so, your organization will continue to function as a standard BYOC Premises organization.

Hybrid Media Group

The second phase involves the Hybrid Media Group feature and you moving your premises Edges into the new Hybrid Media Group. Moving your premises Edges into the Hybrid Media Group allows your premises Edges to function along side of your new cloud media instances. (Cloud media instances perform the same function that your premises Edges perform, but in the cloud via a set of AWS-powered microservices.)

Site Links

In the third phase, you will enable and configure Site Links. Enabling Site Links establishes a connection between your premises core site and the cloud core site. Once you enable Site Links, your premises core site will have access to all the resources in the cloud core site. Likewise, the cloud core site will have access to all the resources in the premises core site.

We’ll describe in more detail how the Hybrid Media Group and Site Links features work and show you how to configure them in later sections of this article.

Warning: All of your premises Edge devices must be running Edge software version 1.0.0.10590 or higher. If any one of your premises Edges is running on a software version prior to 1.0.0.10590, the entire operation will fail. For more information, see Determine an Edge’s current software version and Manually update the Edge software.

Telephony changes

To help you to acclimate, let’s take a look at some the changes that you’ll notice in your organization after we enable the hybrid telephony connection, but before you begin converting your organization. You’ll find changes in the following sections of the Telephony interface.

  • Edge Groups
  • Edges
  • Trunks
  • Sites
  • Location

Click each tab to learn more.

Edge Groups

After we enable the hybrid telephony connection, you’ll discover a new item in Edge Groups called Genesys Cloud Hybrid Media Group.

Under BYOC Premises, you could have multiple Edge Groups; however, under the new hybrid telephony connection, you only need one and we have created and configured it for you. This new Genesys Cloud Hybrid Media Group is where your new cloud media instances now exist. (Cloud media instances perform the same function that your premises Edges perform, but in the cloud via a set of AWS-powered microservices.)

Edges

After we enable the hybrid telephony connection, you’ll discover a new item in Edges. This new item is a cloud media instance and it basically performs the same function that your premises Edges perform. You’ll also notice that the cloud media instance is associated with the Genesys Cloud Hybrid Media Group.

Your premises Edges still appear and are still  associated with your original Edge Groups. As you work through the conversion process, you will move your premises Edges into the Genesys Cloud Hybrid Media Group.

Trunks

After we enable the hybrid telephony connection option, you’ll discover that you now have the option to create BYOC Cloud external trunk types. You’ll also discover that you have two new phone trunks: Genesys Cloud – CDM SIP Phone Trunk and Genesys Cloud – CDM WebRTC Phone Trunk.

Phone compatibility

When making to move to a hybrid telephony connection option, you need to be aware that AudioCodes phones, Genesys branded phones, and the PureCloud softphone are not compatible with BYOC Cloud and so can’t be used on the cloud side of a hybrid organization. However, if you have AudioCodes phones, Genesys branded phones, or the PureCloud softphone on the premises side, they will continue to function normally.

Sites

After we enable the hybrid telephony connection option, you’ll discover that you now have new cloud-based core site called PureCloud Voice – AWS. This cloud-based core site will allow access to the resources provided by the cloud media services. PureCloud Voice – AWS is a managed site, which means that you will not be able to view or modify it.

This PureCloud Voice – AWS site will not be functional until you begin the conversion process. However, your existing premises sites are still fully functional. 

When you access any one of your existing sites, you’ll discover a new tab titled Site Links. Until you perform the first step in the conversion, where you move your premises Edges into the Genesys Cloud Hybrid Media Group, the Site Links tab will show an error message that indicates that the site is not assigned to an Edge Group that supports the site links feature.

The Site Links feature will allow you to connect your existing premises Sites with new cloud Sites, thus forming a hybrid organization.

Note: Adjacent to each site name you’ll see an icon that indicates the media model: The icon indicates a cloud site (cloud media) and the icon indicates a premises site (premises media).

Location

After we enable the hybrid telephony connection option, you’ll discover a new item in Locations called Default PCV Location. This is essentially a dummy location created in concert with the PureCloud Voice – AWS site. While the Default PCV Location is required, its only function is to serve as a placeholder and it should not be edited or deleted. 

You’ll need to create a new location for the cloud and then connect it to a new branch site.

Beta notes:

As a Hybrid Media Orgs beta program participant, there are a few things that you need to know before you begin. Things will look and work a bit differently than what you are currently accustomed to in BYOC Premises. Furthermore, there are some things that will only be a part of the beta that will not be a part of the General Availability (GA) release. Some of these things will require a manual procedure during the beta, but will be automated in the General Availability release. Other things will appear in your organization during the beta, but will be hidden or otherwise unavailable in the General Availability release.

Items that fall in this beta category will be marked with a beta symbol (β).

Knowing ahead of time that these things exist in the beta will allow you to stay focused on the pertinent details and not get distracted or otherwise derailed as you experiment with and learn about the features that our new hybrid telephony connection option is going to bring to the table.

Experimentation

After we enable the hybrid telephony connection option, your organization will continue to function exactly as it did before using the BYOC Premises telephony connection. The new hybrid telephony connection is available but remains totally separate until you begin the actual move as described in the the next section. 

This means that if you would like to experiment with some of the new cloud-based features before you begin converting your organization to a hybrid telephony connection, you can do so.

Click each tab to learn more.

Create a Location

As we described in the overview, after we enable the hybrid telephony connection option, 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, the first thing that you will need to do to begin experimenting with the new cloud-based features is to create 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. Click Save.

Create a branch site

After you create a new location, you need to create a cloud branch site and connect it to your new location.

  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.
  9. Enter a Description for your site.
  10. Click Save Site.

Move a couple of 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.

Make some calls

You can then have the users who are assigned to the phones you moved to the new cloud branch site call each other to verify the new cloud configuration is working.

Note: The users that you put into the cloud site are isolated from the premises site at this point. This means that the users in the cloud site cannot call users on the premises site. Likewise, users in the premises site cannot call users on the cloud site.

Use the Genesys Community to share your beta experiences

If you encounter something that does not work as you expect, please take a moment to report your findings in the Genesys Cloud Hybrid Media Orgs BETA community forum in the Genesys Community. By sharing your findings in this forum you may connect with others who have had or are encountering the same issue. You may also connect with others who have the solution you are looking for. Regardless of whether you find an immediate solution, by reporting the issue in the community, our experts will be able to compare the issue with others, find commonalities, and move quickly to develop a solution for all.

Move your premises Edges into the Genesys Cloud Hybrid Media Group

When you are ready to convert your organization, you move all of your premise Edges from your existing Edge Group(s) into the Genesys Cloud Hybrid Media Group. If you have multiple premise 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 need to 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 cloud proxy interface.

Click each tab to learn more.

Take an Edge out of service

The first thing that you need to 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.

You’ll then return to the Edges page.

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.

You’ll then see that the Edge state changes to In-Service.

β – Select the cloud proxy interface

After you put a premises Edge in service, you need to make sure that the cloud proxy interface is configured.

  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 Cloud Proxy interface list.
  4. Click Save Interfaces.

β This step only applies during the beta. For the GA, this step will be automated.

Other Stuff?

  1.  Do this…
  2. Then do this…

Enable and configure Site Links

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.

Click each tab to learn more.

Enable Site Links

  1. From the Telephony menu on the left, click Sites to open the Sites page.
  2. From the Site Name column, click your premises core site to open the Edit Site page.
  3. 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 as well as 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 will have access to all the resources in the core cloud site. Likewise, the core cloud site will have 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

As we described in the overview, after we enable the hybrid telephony connection option, the process creates a placeholder location called Default PCV Location. This placeholder locations is tied to the PureCloud Voice – AWS cloud site, which is a managed site that you cannot view or modify. As such, you will need to create 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 need to create a cloud branch site and connect it to your new location.

  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’ll 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’ll continue the initial site configuration on the General tab.

  1. Enter a Description for your site.
  2. If you are using WebRTC, you may want to enable the Geo-Lookup TURN feature. The Geo-Lookup TURN feature optimizes the network path for WebRTC calls routed through cloud TURN services. For more information, see Use the Geo-Lookup TURN feature.
  3. Click Save Site.

In the Site information panel, you’ll see the Make this Site my default Site prompt. Since you probably already have a default site, do not select Make this Site my default Site. You’ll also see that the Site Type is identified as a Branch Site and that the Media Model is Cloud. 

Site Links

If you click the Site Links tab, you’ll see a message 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’ll 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, under the External Trunk Configuration heading, contains other settings that you can use to refine your external trunk configuration. The page categorizes these other settings under expandable sections.

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 in the External Trunk Configuration section to refine your external trunk configuration.

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 / Termination you 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 should be populated with a regionally unique identifier. This identifier will be used to direct 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 should be populated with a regionally unique identifier. This identifier will be used to direct 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: This configuration is optional. These fields 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.

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

For more information, see the Inbound section of the Configure SIP routing for a BYOC Cloud trunk article.

  1. Under Outbound, enter identifiers in the appropriate Outbound SIP boxes to configure your outbound request URI.

For more information, see the Outbound section of the Configure SIP routing for a BYOC Cloud trunk article.

  1. Specify the SIP Servers or Proxies by entering a hostname or IP address and a port number and clicking 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 Address and Name, and the appropriate override methods for each.
  1. Under SIP Access Control, build a list of IP or CIDR addresses to which you want to permit SIP access by entering an address and clicking Plus .
  2. If you are configuring BYOC PBX trunk, you'll see the PBX Passthrough setting.
    • Enable PBX Passthrough 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.

  • 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.

  1. Click Save External Trunk.

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 the appropriate 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 need to 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 the vast majority of 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.

Other telephony changes

After you convert to a hybrid media organization, you’ll find changes in the following sections of the Telephony interface.

Edges > Network tab

After you move your premises Edges into the Genesys Cloud Hybrid Media Group, the items on the Network tab change. Instead of Edge Communication, the first item on the Network tab is Site Interconnects. The settings under Site Interconnects control which network interface is used to connect the Edge to other premises Edges or to Cloud Media services within other Sites. There are three type of Site Interconnects. The types that show a value will differ depending on what type of site link is being used by the Edge and whether these links are to other Edges or to Cloud Media services.

Direct interface
Site interconnects using the direct method will communicate using the selected interface’s assigned IP address. Use this option when there is a direct route from the interface’s private IP address and the remote end.

Indirect interface
Site interconnects using the indirect method will communicate using the public P address specified on the interface. Use this option when a NAT enabled firewall is between the Edge and the remote end.

Cloud proxy interface
Site interconnects using the cloud proxy method will broker the connection between them with a cloud proxy, This method is required for connections between one or more sites using cloud media, but can optionally be used between two premises sites if either Direct or Indirect are not an option.

Edge Groups

After you move your premises Edges into the Hybrid Media group, you will have one or more legacy Edge Groups remaining in the Edge Groups list. Since a hybrid media organization requires all premises Edges be in the Hybrid Media group, you can delete your legacy Edge Groups

  1. Click Admin.
  2. Under Telephony, click Edge Groups.
  3. Select the Edge Group Name check box next to each legacy Edge Group you want delete.
  4. Click Delete on the toolbar.

Note: After you move your premises Edges into the Hybrid Media group, you cannot create new Edge Groups.