How to configure Cloud Connector Edition with Cloud PBX - Office 365 (Sonus Cloud Link)

-

It is published in Technet:
#The How-To Guide for Cloud PBX in Office 365 Skype for Business Online with Sonus Cloud Link

This how-to guide is written in technical level 200 for Pre-Sales Consultant and the second half reaches leave 400 for Office 365, Sonus Cloud Link CCE Appliance and the Session Boarder Controller.
We start from the Pre-Sales consulting process and the associated arguments. The Pre-Sales and Consultants will learn how the Cloud Connector Edition is working, technical deep drive inside CCE and last but not least the configuration of Office 365 Skype for Business Online and the wizard based CCE installation. Followed by a common scenario with Cloud PBX and multiple sites across different regions.
Second topic is a direct SIP connection to 3rd party on-premises applications (e.g. Contact Center, local PBX or others). Here we focus on the locally hosted Contact Center. 
The question might be asked, “How can we use different CCE sites with different PSTN breakouts assigned?” The answer is, by utilizing a simple two-site deployment that allows replicating the configuration to larger designs with N-Sites.
For the examples that follow, there will be two locations. The first in Munich, Germany, and the other in London, UK. Both sites have their own dedicated PSTN breakout. It will not matter if the connection to the PSTN gateway is via an ISDN/PRI, or an SIP Trunk line. However, there can be a PBX behind the local site gateway.
If Media Bypass is not available, the user can connect to the customer’s LAN, and the connection to the Mediation Server can be direct if firewall rules allow this path. In this scenario, the users connect over the Internet.
PSTN-based calls can generally flow in two directions, from PSTN -> Cloud PBX user, or from the Cloud PBX user -> PSTN. The simplest call flow is the incoming call from PSTN -> Cloud PBX.
Every CCE has a direct connection/path to the Microsoft Office 365 Skype for Business online platform. Therefore, every incoming call will be signalized to the Cloud PBX directly. There are no other logical or technical considerations.


Table of Contents

Introduction to Cloud Connector Edition     5
CCE Planning and Configuration Guide     5
CCE Voice Routing with Multi-site (Generic)    5
CCE Network Switches in Hyper-V      7
Generic Sonus CCE Appliance Setup     8
Advanced Features       9
Network Setup        10
Generating the CSR and Import Certificate    10
Configuring the CCE       11
Infrastructure Definition of Cloud Connector Edition   12
Scenario-based Infrastructure      12
System, MPLS and Connectivity Infrastructure    13
CCE Appliance Infrastructure      15
Logical Infrastructure       17
DNS         17
External Certificates       18
Internal Certificates       19
Firewall Port Configuration      20
Configuration Guide for Users, Dial-Plans, Voice Routes and PSTN Usage 21
Connect to Skype for Business Online     21
Management Guide for Users      22
Reading and Writing User Information and Settings   22
Configuration Guide for Cloud Connector on the Sonus Appliance  23
Cloud Connector Configuration Data Definition    24
Configuration Data Definition APSITE1 (Malaysia)   25
Configuration Data Definition APSITE2 (Germany)    26
Cloud Connector Configuration Files (CloudConnector.ini)  27
Configuring the Sonus Appliance      34
Sonus Appliance Setup – Germany Site     34
Sonus Appliance Setup – Malaysia Site     45
Sonus Session Border Controller Configuration Numbering (Normalization) 56
Normalization – CCE Deployment Overview     56
Normalization – Configuration      57
Normalization – Germany Site (Munich and Toronto)   58
Normalization – Malaysia Site (Kuala Lumpur)    60
Normalization – Incoming from SIP Trunk (Summary)   66
Setting Up the Contact Center Connections    67
Configuring Microsoft Office 365     72
Establishing a Skype for Business Online Session   74
Creating a Hybrid PSTN Site      75
Managing Hybrid PSTN Users      76
Assigning a Hybrid PSTN Site to Users     76
Assigning Voice to Users (Cloud PBX)     76
Assigning On-premises Phone Numbers to Cloud PBX Users   79
Testing All Configurations and Connections..............................82
DialPlans With CCE in Office 365     88
Commandlets for Online Configuration     89
Dial-in Conferencing Commandlets     89
E911 and Location Information Service (LIS) Commandlets   89
Skype Meeting Broadcast Commandlets     89
PSTN Calling Commandlets      89
Hybrid PSTN Site and User Commandlets     90
Internet Protocol Phone Commandlets     90
Reporting Commandlets       90
Online User Commandlets       90
Cloud Connector INI File Parameters     91


Comments

Post a Comment

Popular posts from this blog

How to hide users from GAL if they are AD Connect synchronized

-
Image
How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modif...
Read more

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, uniqu...
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more