Teams Node Configuration

In the next section of this chapter, we will provide a step-by-step walkthrough on setting up a Teams Node within anynode. We will start with the initial setup process that involves the anynode Scenario Wizard with its Guided Setup that includes:

 

  • Node Type,
  • Network Controller,
  • Ports
  • Certificate & Private Key,
  • Certificate Chain,
  • SBC FQDN,
  • and Node Name.

Guided Setup

To begin the guided setup, the Wizard will lead you through the process. In this example, we will be using the Microsoft Teams Direct Routing and Voice over IP Provider scenario. Once you’ve selected the scenario, click Start and let the Node Interconnection Assistant guide you through the setup tasks.

  • Choose Microsoft Teams Direct Routing and a VoIP Provider
  • Click Start

First Start

When you start anynode for the first time after installation, you must set up an initial password for the default administrator account.

The default username for the Administrator is always “anadmin“.

The initial password must contain a minimum of 9 characters and should not include number sequences like 1234 for security reasons.

The wizard will inform you during input whether the password is valid.

  • Enter password and retype password
  • Click Set Password
  • Click Next

By agreeing to participate in our user experience improvement program, you can help us improve our product or service! Your feedback will enable us to enhance the overall usability and functionality, making it easier and more enjoyable.

  • Choose Help improve anynode
  • Click Continue

anynode Wizard

Let’s proceed with the anynode wizard: When you launch anynode’s frontend for the first time after installation, you’ll automatically be greeted by the anynode Wizard. The anynode Wizard provides a user-friendly interface that leads users through various configuration scenarios step-by-step.

For our example, we will establish a connection between Microsoft Teams Direct Routing and a VoIP provider, including complete routing.

The anynode Wizard simplifies the configuration process by providing multiple pre-defined system profiles for VoIP providers, PBXs, and other Voice over IP systems. It handles the bulk of the configuration work in just a few minutes.

Teams Node Configuration

Once you start the assistant, it will guide you through setting up the selected scenario’s Node configuration.

To configure the node settings, simply choose Configure.

Teams Node: Type

There are several options available to specify the type of Teams node. The most common and straightforward method is Teams Direct Routing.

The carrier trunk option is recommended for providers of multi-tenant hosting systems. Local Media Optimization enables the optimal RTP media flow for in-house hosted SBCs with local connections to providers or PBXs around the world.
Choose the Microsoft Teams Direct Routing environment and hit Next to move forward.

  • Choose Microsoft Teams Direct Routing
  • Click Next

Network Controller

The next step is to configure the network settings for the node.

Since no initial settings or node relationships have been established, you will need to create a new network controller object and configure the appropriate network interface.

For this example, we will use the Use an interface’s address option with IP Version 4. This will allow anynode to use the IP address assigned to the network adapter, and changes to the designated address will be tracked and updated accordingly.

Please note that Microsoft currently only supports IP version 4 for Direct Routing.

Microsoft currently only supports IP version 4 for Direct Routing.

The assistant will automatically enable reverse DNS lookup, as it is required for TLS and Direct Routing connectivity between Microsoft Teams and anynode.

  • Choose an Interface’s Address Option with IP Version 4
  • Click Next

Ports

In this dialog, you need to assign local port values for UDP, TCP, and TLS.

It is important to ensure that these values align with your network and remote configurations.

To avoid port collisions, it is crucial to use unique port ranges if multiple nodes and network controllers in anynode share the same local Ethernet interface and IP address in the operating system.

Keep in mind that the Dynamic UDP/TCP ports must have restricted ranges that are at least three times higher than the maximum number of concurrent sessions.

The node interconnection assistant has auto-populated the ports. Microsoft Teams is configured to use TLS, and the default port suggested by the Teams node is “5067”.

anynode expects incoming TLS connections on this port, so it should be configured on the PSTN Online Gateway on the Teams side.

  • Accept the default value for TLS port
  • Check UDP and TCP port ranges
  • Click Next

Certificate & Private Key

In this setup step, you must configure the private key and public certificate, which is mandatory for a TLS connection.

For our example, we will be using an existing certificate file from a Certification Authority. It is important to note that the certificate must include the valid SBC FQDN.

It is worth noting that anynode accepts any certificate format and will convert it internally into the correct one.
anynode accepts any certificate format.

Simply click “Configure” to start a sub-assistant that will guide you through the certificate and private key setup.

  • Click Configure

To simplify the configuration process, anynode supports importing various file formats for private keys and certificates.

To import the necessary files, simply browse to their location and select them. If the private key and certificate are in separate files, add both files in the same way. Once anynode has successfully imported all required files, you will see a green “completed” message.

After verifying the validity of the imported files, select “Finish” to complete the process.

  • Click Choose File
  • Select Files from your computer
  • Click Finish

Certificate Chain

anynode is pre-loaded with default validation certificates, so the chain is already set up correctly.

If you need to import any additional certificates, simply click “Add”.

For now, just proceed by clicking “Next”.

  • Click Next

SBC FQDN

You will need to enter anynode’s SBC FQDN for the Microsoft Teams Direct Routing tenant.

If you have already imported the necessary certificates, this FQDN should be automatically determined. If multiple FQDNs exist in the certificate, you must select the designated one for this configuration.

Keep in mind that this FQDN is mapped to the corresponding SIP and is used for SIP options sent by anynode.

  • Accept or enter FQDN
  • Click Next

Name

You can easily change the default Node name to your preference in the assistant.

The name of the node serves as a unique identifier for later references, such as in the dashboard or call history. It can be freely chosen, but in most cases, it is sufficient to simply accept the name suggested by the assistant.

Once you have done so, simply click “Finish”.

  • Accept or enter Node Name
  • Click Finish

Check

After completing the configuration, the Node Interconnection Assistant will display an overview of your settings.

If everything is correct, select Next to proceed with the configuration of the second node for this scenario.

  • Click Next
SCROLL UP