MS Teams ® Session Border Controller

MS Teams ® SBC is an OpenSIPS based Session Border Controller especially designed to allow an easy and fast integration of MS Teams ® trunks (Direct Routing) with existing SIP infrastructures, like SIP PBXes, SIP Carriers or SIP Service Providers.

The MS Teams ® SBC is a multi-tenant bridge between the customer's side (left side) and the provider's side (right side). On his side, the customer may bring multiple MS Teams ® tenants and also multiple SIP PBX trunks. On the provider's side the SBC may uplink the customer's traffic to various PSTN carriers or to SIP Service Provider.

Supported scenarios

Depending on the bridging logic, the MS Teams ® SBC may address several MS Teams ® integration needs.

Traffic pass through

For the existing SIP Service Providers looking to accept MS Teams ® trunks into their platform, the MS Teams ® SBC is the fastest and non-disruptive way to do it.

Acting as a front SBC, the MS Teams ® SBC coverts the MS Teams ® trunks (Direct Routing) into either SIP registering users, either IP authenticated trunks into the platform, for traffic termination or origination. The SBC will take care of all SIP transport conversion (TLS to UDP) and RTP to SRTP bridging.

Traffic termination

If looking to create and provide new service, the MS Teams ® SBC is the ideal tool to start a PSTN termination and origination service for the MS Teams ® users. Any number of MS Teams ® tenants may uplink to the SBC in order to provide PSTN interconnection with variable set of carriers. The SBC handles the termination side, with prefix routing, LCR, CLI management and failover over the carriers. On the inbound side, the SBC overs DID mapping over the MS Teams ® tenants.

Traffic aggregation

For creating and providing a new type of service, the MS Teams ® SBC is able to do more than simple traffic termination. The SBC, in a multi-tenant manner, is able to aggregate traffic from multiple source, on the customer side. Traffic from MS Teams ® and from tradditional SIP PBXes may be aggregated and internally routed, per customer bases. Any external traffic (dialplan detected), like PSTN related traffic, may be pushed via the inter-connected carriers.

This is a new standalone type of service that does not require any pre-existing service on the provider side. The traffic aggregation between PSTN and multiple customer sources is a valuable capability, considering the varity of customer side SIP based solutions

Contact us and get more details on the MS Teams ® OpenSIPS SBC product.

SIPGene - designed to build your SIP network.

Need more info?

  • 2+3=