Shulou(Shulou.com)06/02 Report--

Introduction

The following documents are used to build the test environment:

Link:

Configure Teams: https://thamaraw.com/2018/07/04/direct-routing-configuration-with-microsoft-teams-and-audiocodes-virtual-sbc-part-1/

Regular expressions: https://blog.51cto.com/ucworld/441917

Documentation:

Audiocodes SBC with MS teams Direct Routing Enterprise Model Configuration Note*

1 Architectural Topology

This test environment consists of the following components:

Microsoft Office 365International E5 (including Teams/Phone system license) Orco VE SBC VMWare V7.20A.156.028 (including SW/Teams and SBC test license) Avaya CM 7.0 (including SIP Trunk license) VMWare 5.5 virtualization platform virtual machine one public network certificate (including one SBC FQDN) 2 intranet IP / 1 public network IP

2 basic environment

2.1 Domain name information

AD Domain:domain.com.cn

SIP Domain:domain.com.cn

Office 365 Domain:domain.com.cn

2.2 IP address Information

RoleIPMaskGatewayCommentsSBC Intranet 10.21.196.1602410.21.196.252 Public Network IP:220.248.21.142SBC Public Network 10.21.198.1102410.21.198.252-Avaya10.21.198.222410.21.198.252TCP 5060TeamsTeams.localMurray-Public Network DNS parsing

2.3 username password

Gateway default username password: Admin

3 deploy VE SBC

Before deploying SBC, please download the corresponding version of soft SBC software through the link below.

Virtual Edition (VE):

VMware: https://audiocodes.sharefile.com/d-s6c29b271d1f4e0c8

KVM: https://audiocodes.sharefile.com/d-sa7e6187a2ef4e5ea

Hyper-V: https://audiocodes.sharefile.com/d-s7f347ccab9d4b149

Server Edition (SE):

ISO: https://audiocodes.sharefile.com/d-s75b567dfd274f3a8

3.1Import SBC

Import the downloaded soft SBC software through the VM management client, and complete the configuration of multiple network cards before import. After the import is completed, complete the basic network configuration through the console of VM Clinet through the following command

Command:

User Name:Admin

Password:admin

Enable

Password:Admin

# configure network

(config-network) # interface network-if 0

(network-if-0) #

(network-if-0) # ip-address 10.4.212.155 (please use real IP)

(network-if-0) # prefix-length 16 (please use real mask length)

(network-if-0) # gateway 10.4.0.1 (please use real gateway address)

(network-if-0) # activate

(network-if-0) # exit

Once the configuration is completed, you can enter the management through the WEB management end.

3.2 configure the network

Enter the default user name and password Admin/Admin to log in to the Web management console. Since we need to configure a dual network card in this test environment, we configure the second network card through the Web side. First check the Physical Ports (setup-IP network-Core Entities-Physical Ports) and confirm that there are two physical network cards and the status is Active.

Then check the Ethernet Groups (setup-IP network-Core Entities-Ethernet Groups) to make sure that each Group contains the corresponding physical network card

Enter Ethernet Devices (setup-IP network-Core Entities-Ethernet Devices), click the New button, and press the figure to add the second network card (the network card here is the SBC internal network card, corresponding to the physical network card, group).

Finally, configure IP Interfaces (setup-IP network-Core Entities-IP Interfaces) and click New

The window that appears again is configured as shown in the figure. Note that a SBC can only have one OAM address (the error is caused by the default OAMP address is not deleted, or you can directly modify the default IP Interfaces configuration)

The final effect is as follows: two IP Interfaces will be used to correspond to the internal network and the public network respectively.

Import SBC licen

Soft SBC comes with 3-way SBC concurrent test license by default, but because you need to enable SILK NB/WB and OPUS protocol coding to support Teams, you need additional Teams support license (SW/Teams) to export INI File and send it to Orco to apply for a test license.

Copy after receiving the serial number

Then click actions in the upper right corner, find License Key, click Load String below, paste the copied Key into the pop-up box, and click Apply

3.4 configure encryption

Interfacing with Microsoft Teams must be encrypted, so you need to configure the encryption certificate, setup-ip network-security-TlS Contexts, and click add.

Click apply on the open page and click the configuration as shown in the figure.

When you are finished, select the TLS Contexts you just created, pull it to the bottom, and click change certificate

If you need to change the key size, drag it below to modify it, and then click generate private key

Then go back to the top, complete the relevant information, click create CSR, copy the generated CSR to the TXT file, and send the TXT to the certificate provider

After receiving the certificate issued by the certificate provider, the load certificate

Prompt load success at the top

Go back to the previous page and click certification info to see the certificate information. If the certificate provider provides an intermediate certificate, you can click trusted Root cerificates and configure it on the open page.

Click Import directly, select a file on the page and click OK (in this test environment, the intermediate certificate is not provided by the certificate provider, so the certificate is not configured)

3.5 create Media Realms

Media Realms is the channel of the media, which is used to define information such as the port used by the media. Together with SIP interface, it will be bound to the corresponding IP Group later. To create a Media Realms, you need to use setup-signaling&media-core entities-media realms, and then click New.

Configure the media port as shown below. This test environment will be configured with two Media Realms, corresponding to the internal network and the external network.

The following figure shows the parameters to be configured. Fill in the specific parameter values according to the actual situation.

After-effect drawing

3.6 create Signaling Interface

SIP interface is the channel of signaling, which is used to define the port and other information used by signaling. Later, it will be bound to the corresponding IP Group. To create a Sip Interface, you need to go through setup-signaling&media-core entities-Sip interface, and then click New.

As configured as shown in the figure, this test environment needs to create two SIP Interface, partial for external Teams and internal Avaya.

The following figure shows the parameters that need to be configured. The specific parameter values are subject to the actual situation.

After-effect drawing

3.7Configuring Proxy sets

Proxy Sets is a set of IP addresses with the same attribute, such as multiple SFB front-end servers or multiple SIP servers of the same type. These servers with the same type and function need to write all the IP addresses into a Proxy sets list. To configure Proxy sets, click setup-sinagling&media-core entities-Proxy sets, click new.

On the page that opens, configure according to the following two figures. This test environment will create two proxy sets, with the branch representing teams and Avaya.

The following figure shows the parameters that need to be configured, and the parameters are filled in according to the actual situation.

After the creation is completed, go back to the previous page, select the created proxy sets, pull it to the bottom, and click Proxy address items.

In the pop-up page, fill in the relevant IP address. Teams is special. You need to write FQDN (fixed). Later, you will resolve the IP address through DNS parsing.

3.8Create internal SRV record

Since Teams is filled in with FQDN, you need to create this configuration so that SBC can parse the FQDN. On the Internal SRV page, click New directly.

Fill in the pop-up window according to the following picture (fixed)

3.9 configure code group

Microsoft Teams supports SILK communication protocol. In order to cooperate with the use of Teams, you need to configure the following Code. On the code groups page, configure it as shown in the figure (SILK NB/WB OPUS needs to be activated through SW/Teams license)

3.10 configure IP Profile

IP Profile is a parameter customized by a group of users for signaling media, which will be bound to IP Group later. To create an IP Profile, use setup-signaling&media-coders&profiles-Ip profile, and then click New to configure as shown in the figure.

Effect after completion

3.11 create IP Group

IP Group is a set of servers of the same type, such as multiple SFB frontend. IP Group is just a container. The specific configuration needs to be associated through configurations such as IP Profile,Media Realms. Please browse to setup-signaling&media-core entities

-Ip group, and then click New. Please follow the figure below to configure (Proxy keep-alive using ip group settings is not configured) (the configuration for internal Avaya may be different)

Effect after completion

3.12 configure SRTP

Microsoft Teams must use SRTP, so you need to enable SRTP in media, which is not enabled by default.

3.13 create message condition rules

3.14 create Classsification Rule

3.15 create IP2IP rout

Please configure the routing of IP2IP according to the actual situation

Teams to avaya

Avaya to teams

3.16 configure call line ID

3.17 configure NAT

Since SBC needs to be released before it can be connected by Teams, you need to NAT. To configure NAT, you need to go to Setup-IP Network-Core Entities-NAT Translation, click New, and publish NAT according to the previously planned port.

After configuring NAT, you need to enable NAT. If you want to enable it, you need to use Setup-Signaling&media-Media-Media settings to change the Nat Traversal parameter value to Nat by signaling in the right window.

3.18 check configuration

When you are finished, you can check the connectivity between SBC and Teams and Avaya. You can use Monitor-VOIP Status-Proxy sets status to ensure that all states are Online. If Offline is found, it needs to be checked. The test environment found that the docking with teams is offline.

Check the warning and find that there is an error in proxy set proxy lost. Try to change the Keep A-live Option parameter to disable to solve the problem. Teams may not be able to send Option messages.

The state is normal after modification.

4 configure Office 365

4.1 add Domain

Log in to the Office 365Admin console and click add Domain in install-Domain

Enter the domain you own and click next

Then by selecting a certain method for verification, the test environment uses TXT records to verify.

Add the following record to the public network DNS, and then click verify

Select a method, and then click next

Select SFB and click next.

The recommended DNS record appears, and the FQDN of SBC is added to the public network DNS together.

Click finish to complete the domain addition

If you see it! Number, which means that DNS has not been added properly.

4.2 install management tools and connect to Teams

If you need to configure Teams, you need to manage it through a remote Powershell command. The following modules need to be installed to ensure that the Teams can be connected.

Install sfb online powershell and powershell 3.0

Https://docs.microsoft.com/en-us/SkypeForBusiness/set-up-your-computer-for-windows-powershell/set-up-your-computer-for-windows-powershell

Https://www.microsoft.com/zh-CN/download/details.aspx?id=41950

Install the msonline module first, and all the following usernames use the user name of the domain.com.cn suffix. First of all, you need to have an administrator with the domain.com.cn suffix, otherwise there will be an error in the later management that the domain has not been added.

Then use the following command to connect to Teams, and you will be prompted for the username and password. Please enter the username and password of the administrator (the username needs to be suffixed with domain.com.cn).

Import-Module MSOnline

Connect-MsolService-Credential $credential

Import-Module LyncOnlineConnector

$lyncSession = New-CsOnlineSession-Credential $cred

Import-PSSession $lyncSession-allowClobber

4.3 create a paired SBC

Use the GCM command to check whether you have successfully connected to the Teams. If the following figure appears, the connection is normal.

Then create the SBC through New-CsOnlinePSTNGateway-Fqdn-SipSignallingPort-MaxConcurrentSessions-Enabled $true

You can view the created SBC configuration through the get command

4.4 create Dial Plan

Create a Dial Plan with the following command, and the rules need to be written through regular expressions: (command parameter values are based on the actual situation)

$rule1 = New-CsVoiceNormalizationRule-Parent Global-Name AU-Mobile-Description "Australia Mobile Numbers"-Pattern'^ 0 ([45]\ d {8}) $'- Translation'+ 61 $1'-InMemory

$rule2 = New-CsVoiceNormalizationRule-Parent Global-Name AU-Local-Description "Perth Local Numbers"-Pattern'^ ([2-9]\ d {7}) $'- Translation'+ 618 $1'-InMemory

Set-CsTenantDialPlan-Identity Global-NormalizationRules @ {add=$rule1,$rule2}

4.5 create pstnusage

Set-CsOnlinePstnUsage-Identity Global-Usage @ {Add= "AU-Mobile"}

4.6 create routing

New-CsOnlineVoiceRoute-Identity "AU-Mobile"-NumberPattern "^ + 61 (45 (\ d {7})) $"-OnlinePstnGatewayList sbc.uctechie.com-Priority 2-OnlinePstnUsages "AU-Mobile"

4.7 create a voice policy

New-CsOnlineVoiceRoutingPolicy "AU-AllCalls"-OnlinePstnUsages "AU-Mobile"

Assign voice policy (sometimes fail, try more)

4.8 configure user

Set-CsUser-Identity thamaraw@uctechie.com-EnterpriseVoiceEnabled $true-HostedVoiceMail $true-OnPremLineURI tel:+61893423245

The following two commands are used to configure the client's preferred Teams, otherwise SFB will be preferred as the user's voice client in an environment where SFB and Teams are used at the same time

Grant-CsTeamsInteropPolicy-PolicyName DisallowOverrideCallingTeamsChatTeams-Identity thamaraw@uctechie.com

Grant-CsTeamsCallingPolicy-PolicyName Tag:AllowCalling-Identity thamaraw@uctechie.com

! []

Log in to Teams and test * *

Since this route translation rule is only configured with mobile phones, we can only call external mobile phones.

Further technical support or cooperation intention can be obtained through our Wechat official account: Audiocodes. Contact us.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.