This guide will help you to test out the beroNet Cloud SBC and connect it to your local machine and perform a test call.

Prerequisites

• a beta account for betaCloud.beronet.com

• A Microsoft 365 Tenant or Developer Tenant (Follow step 1 to set one up)

• A way to establish a VPN connection with your

• SIP-Client / SIP-Server to send calls from

Open

1. Create and setup your Microsoft Tenant*

* This step is optional if you already have an Office 365 Tenant with the necessary subscription!

To use Microsoft Teams, you will need to create a Microsoft 365 Account with the necessary subscription level to use Microsoft Teams or a Developer Account.

Buy MS 365 E5 subscription here: Compare Office 365 Enterprise Pricing and Plans | Microsoft 365

Setup MS 365 E5 developer subscription here: Office 365 Developer

• To create a Developer Account, you need to log in with a Microsoft Account and fill in your name

• Choose a company Name

• Create a Sandbox for your Office 365 Environment

  • Create a Admin User and Domain

  • Verify your Phone Number (it cannot be used for another developer account)

More information can be found at Microsofts Documentation:
Set up a Microsoft 365 developer sandbox subscription

2. Create the beroNet Cloud SBC VM

2.1 Set up Cloud SBC

Create a Cloud SBC in beroCloud and make sure you can access the GUI via the provided FQDN

For this, follow this guide to set up your Cloud SBC on betacloud.beronet.com

Via Update-Management, make sure to Update to the latest SBC package and set the Package Type to “Testing”. Press on save and perform an Update. This can take a few minutes.

Open

2.2 (optional) Create your own SSL Certificate for your own domain.

Make sure the domain used for the certificate has an A-Record that points to the public IP-Adress of the Cloud SBC.
Please refer to your DNS Provider. (The public IP can be found under Network Settings and will not change!)

The SSL Certificate must be provided in 3 files in the pem format. Depending on the Certificate Authority, the file may come in a variety of names.

• cafile.pem / chain.pem / ca-bundle.pem
  This is the CA-Bundle or CA-Chain file provided by the CA.

• cert.pem / certificate.pem
  This is the CRT file provided by the CA. This is the domain specific certificate and will be combined with the generated private key

• privkey.pem / key.pem
  This is the generated private-key that is used to generate the certificate

3. Pre-configure the Cloud SBC

3.1 Scenario / What do we want to achieve?

In this example guide we want to connect the Cloud SBC to your local machine via a VPN connection.
With this, we want to simulate a real IP-PBX that is connected to Teams.

You additionally need:

• A way to connect to a VPN network (VPN-Router, openVPN client, etc.)

• A calling party (a softphone, an IP PBX, a SIP-Server like Asterisk)

3.2 Create a VPN and a SIP Connection

Establish the VPN Connection

In the beroNet web-GUI, visit Preferences → VPN and create a VPN.
(Additional Resources can be found here: https://beronet.atlassian.net/wiki/spaces/PUB/pages/3390341121 )

After creation, go to Client Configuration and download the client.conf file and connect your device to the VPN Network. The client.conf file contains all the necessary information and keys to authentificate with the machine.

Create the SIP Connection

In the beroNet web-GUI, visit SIP → SIP and add a new connection.

The connected client via VPN will get IP-Address that is one over the SBCs internal LAN IP-Address.

• Set your SIP Outbound Proxy to your connected clients IP-Address!

• If your SIP Client / Server needs additional Authentification, please set the Username and Secret here!

• If you need to have the beroNet Cloud SBC registered at your SIP Server, set the Register Flag.

  • If not, just set Validate. (This will verify that the client is reachable by the SBC via SIP-Options)

• Choose the SIP Stack, in this case LAN/VPN. If you register via the public IP-Address, it should be WAN

4. Connect to Microsoft Teams

In the beroNet web-GUI, visit SIP → SIP and click the Setup Teams button.

4.1 Certificate and linked SIP Account

Choose your certificate method. beroNet will provide signed certificates for the FQDN under which you are able to reach the web-GUI. Then give your Teams SIP Account a new name and link your created SIP Account that we just created! All necessary configuration will be set automatically.

4.2 Verify Domain at Microsoft Teams

Admin Center → Show All → Settings → Domains or click here or in the wizard: https://docs.microsoft.com/en-us/microsoft-365/admin/setup/add-domain

• Add hostname of SBC as Domain name

• Add TXT Record to domain’s DNS record

The TXT Value that you will get shown, must be entered into the Wizard and we will create the TXT record for you at the end of the Set-Up! When you submit all the information to the wizard, you will be able to finish the verification process in the Microsoft 365 admin center.

4.3 Activate the Domain with activation User

The domain must be activated, in order to use it for Microsoft Teams. For this you need to create an Office 365 User to the Tenant and log in once!

For this section you need to be on the Microsoft 365 Admin Portal

Admin Center → Users → Active Users

• Add a User with the new domain

  • For example Activation; User; Activation User; activationuser@<your-domain>

  • It is important to choose the newly added domain of the SBC here!

• Assign the user the E5 or E5 Developer License!

• Open new private browser window and sign in as the new user at portal.office.com

4.4 Add the SBC to Microsoft Teams

Go to Voice → Direct Routing → SBCs and add a new SBC here: Teams Admin Center: SBCs

Only two things must be changed from the default template.

• SIP Signaling Port: 5061

• Forward PAI header: On (This is important to avoid anonymous calling)

4.5 Add a voice route and PSTN usage record

Now we need to connect the telephone service. For this you go to the second tab in Direct Routing and add a voice route! Teams Admin Center: Voice Routes

It should look like this:

• The Dialed number pattern “\d+” is a catch-all rule. You can change this later.

• Add the SBC to SBCs enrolled

• Add a PSTN usage record. You may have to create a new usage record and then select it here.

After creation, add it to your Voice routing policies under Teams Admin Center: Voice Routing

• You can open your Global Policy and add the PSTN usage record you just created

4.6 Assign a Phone Number to a Teams User to enable the dialpad

Go to Teams Admin Center: Manage Users and select the user of your choice and click on edit.

Then you will want to edit the general information and add Direct Routing and a phone number. This phone number will be used to match rules on the Cloud SBC later. You may want to use the same phone number and extension as your SIP Provider, to avoid changing it within the SBC.

• Phone Number Type: Direct Routing

• Assign Phone Number

If you log in with the User in Teams, you should see a dialpad under Teams Client: Calls. That means everything worked well!

You can now call a number and your Cloud SBC will forward the call to your SIP Client.