Skip to main content

Press Releases


01 Mar 2024

DINSTAR SBC for Microsoft Teams Direct Routing

Dinstar Stand: C30

Deploy DINSTAR SBC locally at the branch, connect to the local operator's IMS via SBC, and simultaneously integrate with the Microsoft Teams through SBC.

What is Microsoft Teams Direct Routing?

Microsoft Teams Direct Routing enables customers to connect local voice trunks directly to the Microsoft Office 365 system, facilitating the implementation of local lines. This allows customers with Microsoft Teams users to continue using their existing voice switching systems, such as PBX, IPPBX, and analog telephone adapter (ATA) , protecting their investments.

When the Microsoft Office 365 system is linked to the user's local voice trunk, it offers flexible dialing rules to enhance the calling experience for Microsoft Teams users, ensuring a seamless integration of communication systems.

Scenario 1: Teams+ Local Voice Trunks

Many multinational companies opt for Microsoft Office 365 as their primary tool for internal communication and collaboration. The group requires Teams to connect to local telecom operators' voice trunk lines, enabling cross-border voice communications. This facilitates communication with branches and customers across different countries, enhances efficiency, and reduces international call costs.


Deploy DINSTAR SBC locally at the branch, connect to the local operator's IMS via SBC, and simultaneously integrate with the Microsoft Teams through SBC.

(1) The branch utilizes the local telecom operator's SIP trunk (IMS).

(2) DINSTAR SBC is deployed in the branch to access the operator's SIP trunk. Simultaneously, it connects to Microsoft Teams through the Internet.

(3) Dialing rules are configured on the Microsoft Teams platform to enable cross-border lines through Direct Routing. Teams’ users can directly dial the mobile phone numbers of domestic users, avoiding high international call charges.

Scenario 2: Teams+ Local IP PBX

Enterprises seek to establish interconnectivity between the existing IP PBX communication system and Microsoft Teams, to build an enterprise voice communication system, enabling unified communications while protecting their initial investments on IP PBX system.


To achieve this, DINSTAR SBC is deployed within the enterprise. The SBC establishes connections to the local operator's IMS line and bridges Microsoft Teams with the original IP PBX system.

(1) The enterprise's original SIP trunk line connects to DINSTAR SBC for voice implementation.

(2) SBC establishes connections to Microsoft Teams via the Internet and the enterprise's local IP PBX system through the intranet.

(3) Dialing rules are configured on the Teams platform, allowing users to make direct domestic calls to colleagues or customers, optimizing call costs.

(4) Extension users from the enterprise's original IP PBX can initiate outbound calls through SBC.

(5) Teams’ users are seamlessly interconnected with the local IP PBX system. Incoming customer calls first enter the local communication system, then reach the employees' Teams accounts. This integration enables employees to answer customer calls through Teams, fostering free calls between IP PBX and Teams users.

Scenario 3: Teams+ Local PBX

The enterprise currently operates a traditional PBX phone system, facilitating outbound calls through E1 trunk lines. In pursuit of a voice system transformation and a phased migration to Teams, the goal is to preserve the existing PBX and operator lines. The objective is to achieve seamless telephone interoperability between Teams users and the enterprise's existing PBX, leveraging the exsiting line resources of the enterprise.


(1) Use the trunk/media gateway to connect both the local PBX and the operator's E1 trunk line, preserving existing operator lines and analog users.

(2) The trunk/media gateway connects to DINSTAR SBC, and then SBC connects to Microsoft Teams, facilitating the interconnection between Teams and the enterprise’s local traditional PBX.

(3) Teams Outbound Calls: Calls initiated on Teams are routed through DINSTAR SBC and then transferred to the local E1 line for outgoing calls.

(4) Calls Between PBX Extensions and Teams Users: PBX transfers the call to the trunk/media gateway via the E1 line. The trunk/media gateway then forwards the call to SBC, and SBC routes it to Teams, enabling seamless communication between analog extensions and Teams users.

(5) The incoming and outgoing calling methods of the PBX system remain unchanged, the dialing habits of existing PBX users in the enterprise will not be altered.

Scenario 4: SBC High Reliability Deployment Solution

(1) DINSTAR SBC supports 1+1 redundancy, seamlessly and automatically switch to the backup device when the main SBC is faulty. This automatic switch ensures uninterrupted service during the transition between active and standby, maintaining business continuity.

(2) SBC offers multiple network port access, enabling simultaneous connection to SIP trunks from different operators for line redundancy.

(3) It provides a range of flexible routing strategies to achieve redundancy in call services.

(4) The Device managemeng system NMS platform centralizes the management and maintenance of SBCs, offering real-time monitoring of equipment operating status.

What role does DINSTAR SBC play in Direct Routing?

Compatibility and Interoperability: Different SIP Servers and SIP trunks may exhibit compatibility variations. DINSTAR SBC facilitates the interconnection and interoperability of diverse platforms, ensuring seamless communication.

Security: SBC enhances security by providing voice firewalls and encrypting signaling and media. This safeguards voice communications, protecting against potential Internet-based malicious attacks.

Smooth Migration: Enterprises often opt for gradual migration to Teams while still utilizing traditional PBX and IP PBX systems during the transition. DINSTAR SBC enables a seamless connection between Teams users and the old PBX during this transitional period.

Flexibility and Fault Tolerance: DINSTAR SBC offers a range of redundancy. This ensures that your system can maintain normal connections even in the event of unforeseen incidents, providing flexibility, failover and fault tolerance.


Extensive Interoperability: Compatible with different vendor platform.

High Reliability: Up to 99.999% reliability , DINSTAR SBC offers various disaster recovery solutions.

High Security: Supports encryption for signaling and media streams, transcoding authorization, and robust voice firewall functions, significantly enhancing the security of enterprise voice communications.

Unified Communications: Enables the integration of original PBX/IPPBX and Teams, creating a unified communications platform. This fosters employee mobility, improves work efficiency, and simplifies voice communication.

Flexible Deployment: Providing both hardware and software SBC options, supporting on-premise/virtual machine/cloud deployment to cater to diverse deployment needs.

Professional Technical Support: Offering comprehensive services, including solution planning, testing, implementation, training, troubleshooting, and software/hardware upgrades, and fast responds.

Tips for Connecting SBC to Teams:

Office 365 E5, or E3/E1 + Phone system

A manageable domain name

A CA encryption certificate (annually)

SBC with a public IP address

* “Teams” and its logo, are trademarks or registered trademarks of Microsoft and its affiliates. DINSTAR SBCs are field-proven interoperable with Teams Platform. DINSTAR products are not affiliated with or endorsed by Microsoft.

View all Press Releases