# Teams ↔ OpenSIPS SBC (Enterprise Communications Integration)

> **Summary**: A custom session border controller connecting Microsoft Teams Direct Routing with existing SIP infrastructure, providing controlled signaling, media routing, and interoperability.
> **Role**: Solution architect & implementation engineer (Enterprise deployment)
> **Tech Stack**: Microsoft Teams, OpenSIPS, SIP, RTPProxy, Linux, Direct Routing

---

- **Canonical Web Page**: https://shadikur.com/work/teams-opensips-sbc
- **Source Repository**: https://github.com/shadikur/opensips
- **Live / Demo URL**: https://github.com/shadikur/opensips

---


## The Problem
The organization needed Microsoft Teams calling to interoperate reliably with its existing SIP trunks and telephony environment without replacing established carrier and PBX infrastructure.

## What Was Built & Technical Solution
I designed and deployed an OpenSIPS-based SBC for SIP signaling and used RTPProxy for media handling. I implemented routing and interoperability logic, connected Teams Direct Routing to the on-premises voice environment, and applied operational controls for maintainability and troubleshooting.

## Results & Impact
The integration enabled Teams users to use the existing telephony infrastructure through a purpose-built, supportable bridge. It showcases practical expertise across Microsoft cloud telephony, SIP routing, Linux networking, media paths, production diagnostics, and enterprise system integration.

---

## Author & Context
- **Creator**: Mohammad Shadikur Rahman (Senior Infrastructure Architect & Full Stack Engineer)
- **All Projects**: https://shadikur.com/work.txt
- **LLM Index**: https://shadikur.com/llms.txt