Acme Packet (MOSC)

MOSC Banner

Impacts on existing MS Teams configuration when MS deprecate the "sip-all.pstnhub.microsoft.com"

in Acme Packet (MOSC) 7 commentsAnswered

After reading "Oracle SBC with Microsoft Teams Direct Routing Technical Application Note" and "Configuring the Oracle SBC to Microsoft Teams Direct Routing-Carrier Model Technical Application Note" I still can't get my head around how this is supposed to work. Maybe someone here already adjusted their MS-Teams related configuration and can bring some light on this.

From my understanding, we've previously been recommended using Session-Agent with "sip-all.pstnhub.microsoft.com" as FQDN in order to allow traffic originating from MS Teams. The DNS resolving of this FQDN will give us all possible IP's for the MS equipment. The ingresses traffic on the Teams facing realms will thereby be allowed sine we have configured the sip-port in the teams facing sip-interface with "allow anonymous = agents only". We also have "access-control" configuration allowing traffic from 52.112.0.0/14 + 52.114.0.0/16 + 52.120.0.0/14 in order to allow traffic on L3-level.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center