When using your own SIP Trunk (BYOT) in combination with a VitalPBX to setup Direct Routing to Microsoft Teams you will need to make some firewall rules. You can find the up to date IP addresses in belows chapters.
This will only be for Microsoft 365, Office 365, and Office 365 GCC tenants.
Signaling IPs
When configuring Direct Routing you will need to setup 3 FQDNs for signaling.
The first one will be located by location and performance metrics. If your location is EMEA, you 2nd location will be US and the 3th ASIA.
| Primary DC sip.pstnhub.microsoft.com | EMEA | NOAM | ASIA |
|---|---|---|---|
| Secondary DC sip2.pstnhub.microsoft.com | US | EU | US |
| Tertiary DC sip3.pstnhub.microsoft.com | ASIA | ASIA | EU |
These FQDN’s resolve to the following IP Addresses ranges:
- 52.112.0.0/14
- 52.120.0.0/14
In belows list you will find the extracted IP Address Ranges:
- 52.112.0.0/16
- 52.113.0.0/16
- 52.114.0.0/16
- 52.115.0.0/16
- 52.120.0.0/16
- 52.121.0.0/16
- 52.122.0.0/16
- 52.123.0.0/16
If your firewall supports DNS names you can use the following FQDN, this one resolves all above addresses.
Media IPs
When we talk about media ports (not in media Bypass mode) the following ranges are used. Media is using a serparate service in the Microsoft cloud, these are called Media Processors.
Locations where both SIP proxy and media processor components deployed:
- US (two in US West and US East datacenters)
- Europe (Amsterdam and Dublin datacenters)
- Asia (Singapore and Hong Kong datacenters)
Locations where only media processors are deployed (SIP flows via the closest datacenter listed above):
- Japan (JP East and West datacenters)
- Australia (AU East and Southeast datacenters)
The following ranges are being used:
- 52.112.0.0/14
- 52.122.0.0/15
For more information on how to configure VitalPBX with Microsoft Teams, see the following Blog: