Microsoft Teams (Direct Routing)
Integration key: teams-direct-routing
For tenants running Microsoft Teams Phone with Direct Routing through a Session Border Controller (AudioCodes, Ribbon, AnyNode, Oracle, others). CallingEdge appears as the carrier behind your SBC.
What you get
Section titled “What you get”- Outbound calls from CallingEdge to Teams users via your SBC
- Inbound calls from Teams Phone answered by CallingEdge
- Blind transfer via SIP REFER
- Real-time webhook stream
- Recording
- Optional enrichment from Microsoft Graph call records (if you grant us read access)
What we need from you
Section titled “What we need from you”| Item | What it is |
|---|---|
| SBC FQDN | Your SBC reachable from the public internet via SIP TLS |
| Trust the carrier | Add us as a trusted PSTN gateway in your Teams voice routing policy |
| Voice route | Routing rule that sends matching numbers through us |
| Optional: Microsoft Graph app registration | Read scope CallRecords.Read.All for call-record enrichment |
| Webhook URL | Where you want us to POST normalized events |
Setup at a glance
Section titled “Setup at a glance”- Confirm Direct Routing licensing on your tenant.
- Configure your SBC for SIP TLS to our termination URI (mutual TLS supported).
- Add the voice route + voice routing policy targeting the right user set.
- Send us the SBC FQDN through the secure intake; we allowlist + verify.
- Place a test call.
Limitations
Section titled “Limitations”- Graph enrichment is optional and only adds richer call records on
get_call_status; without it you still get the full normalized event stream. - No wrap-up code surface on this path.
- Teams meetings / Calls Platform are out of scope; this is PSTN-side only.