Acme Packet (MOSC)

MOSC Banner

SBC and communication to Microsoft Azure shared platform

in Acme Packet (MOSC) 2 commentsAnswered

We have recently managed to setup one SIP trunk against MS Azure. Problems seem to occure when we need to add muliple sip trunks communicating to MS Azure. Multiple sip trunk setup is needed because the SBC is used as a shared platform.

OPTIONS related problem:

As we have session agents (sip.pstnhub.microsoft.com, sip2.pstnhub.microsoft.com, sip3.pstnhub.microsoft.com) we can only tie these to one specific sip trunk realm and the OPTIONS monitoring is therefore working only with this specific realm & sip interface because MS has build their system in a way that it requires the SBC device to send the customer fqdn name (configured in the realm with the teams fqdn parameter) in the contact header. Otherwise the MS platform wont allow the connection. The ideal situation would be that we could monitor all the MS Azure hostnames from different realms (with their own sip interfaces) at the

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