This section outlines environmental requirements which are applicable to all aspects of the RealConnect Service, regardless of which Microsoft unified communications services are to be used. Additional requirements specific only to either Microsoft Teams or Skype for Business will be covered later in the applicable sections.
Microsoft Office 365
In order to utilize the Poly RealConnect Service a valid Microsoft Office 365 tenant is required and a user with the Global administrator role assigned. All topologies of Microsoft Exchange and Skype for Business are currently supported, as is Microsoft Teams.
The RealConnect Service is currently available globally to Microsoft Office 365 tenants homed in any country, with the following exceptions. Note this requirement only applies to the region that the tenant is homed in, not the user specifically. So, a tenant homed in North America can still utilize the service with users located in any region.
|RealConnect for |
|"cn", "China", "ru", "Russian Federation"|
|RealConnect for |
(Skype for Business)
|"cn", "China", "ru", "Russian Federation", "kp", "North Korea", "ao", "Angola", "bw", "Botswana", "cm", "Cameroon", "cp", "Cape Verde", "ci", "Côte d'Ivoire", "et", "Ethiopia", "gh", "Ghana", "ke", "Kenya", "mu", "Mauritius", "na", "Namibia", "ng", "Nigeria", "rw", "Rwanda", "sn", "Senegal", "tz", "Tanzania", "ug", "Uganda","zm", "Zambia"|
This section outlines IP communication requirements for standard network firewalls or existing standards-based video conferencing traversal solutions to successfully allow outbound calls from video endpoints to reach the various Microsoft Azure datacenter locations where the Poly RealConnect Service resides.
Note that it may not be required to manually configure anything if the network where the endpoints reside already allows outbound traffic to any host on the Internet. If that may be the case then skip ahead to the Test Calls section, but if the call fails then return here to validate the proper network communications are allowed.
Configure any outbound firewall rules to match the settings listed below for the desired protocol(s).
- For example, if only SIP calls are to be allowed then only the top ports in the table are needed (5060-5061, 15001-16000 TCP & 20002-30001 UDP)
- Alternatively, if only H.323 calls are to be allowed then the bottom half of the table is applicable (1719, 20002-30001 UDP & 1720, 10001-13000 TCP)
The destination network(s) for traffic in the table shown above could be in one of several Microsoft Azure datacenters globally, primarily depending on the location of the calling endpoint or its registrar (if applicable). It is recommended to allow outbound traffic to all IP addresses utilized by the service for the inherent geographical redundant load balancing to function correctly. In the event of a single datacenter issue inbound calls can automatically be routed to a remote datacenter, but if those destination IP addresses are not also allowed by firewalls then the redirected call would fail.
To identify the current list of all IP addresses in use by the RealConnect Service Poly maintains three up-to-date DNS records which can be queried using a simple nslookup command.
- edge-global.plcm.vc – This DNS record returns all IP addresses used by the Poly RealConnect Service for supporting both Microsoft Teams and Skype for Business meetings.
- edge-sfb.plcm.vc – This DNS record returns only the subset of IP addresses used by the Poly RealConnect Service for supporting Microsoft Skype for Business meetings.
- edge-teams.plcm.vc – This DNS record returns only the subset of IP addresses used by the Poly RealConnect Service for supporting Microsoft Teams meetings.
If the environment contains any video conferencing infrastructure components like Polycom DMA and RPAD then further configuration may be required to correctly route calls to the RealConnect Service. For detailed information about how to use the RealPresence DMA system, see the Poly RealPresence DMA System Operations Guide.
If the environment contains either Cisco endpoints and/or Cisco infrastructure components, then further configuration may be required to correctly route calls to the RealConnect Service.
Additionally, a Poly Cloud Relay virtual server will need to be deployed on-premises in order to support the Poly One Touch Dial (OTD) capability which is compatible with several Cisco’s native One Button to Push (OBTP) feature. It is recommended to perform the Cloud Relay deployment and configuration prior to advancing any further with the RealConnect Service configuration and license activation steps.
Verify the configuration settings on your Cisco TelePresence Video Communication Server (VCS). For detailed information about configuring the Cisco TelePresence Video Communications Server, see the Cisco support site.
Verify Zone Configuration
Within Cisco VCS verify the DNS and Traversal zones are Active and that either one or both SIP and H.323 are enabled (On).
Navigate to Configuration > Zones > Zones.
Verify the Status for both H.323 and SIP are On.
- Select DNS Zone and verify the State is Active.
- Select Traversal Zone and verify the State is Active.
Verify DNS Configuration
Verify that VCS can correctly resolve the
plcm.vc domain in order to route calls to the RealConnect service from registered endpoints.
Navigate to System > DNS.
Verify that at least one DNS server has been provided which can resolve the public
Once the environment configuration is validated then place a test call from one or more video endpoints using either SIP or H.323 with the following dial string:
For example, if using a Poly Group Series endpoint connect to the device’s IP address using a web browser and then select the Place a Call menu. Expand Manual Dial, select the desired options, enter the test dial string, and then click Call.
If the call is successful, the following inbound video image should appear on the system’s monitor.
Also, select the Call Statistics button at the top of the page to confirm that both audio and video communications are each reporting successful transmit (TX) and receive (RX) channels.