Acme Packet (MOSC)

MOSC Banner

Teams refer problems starting in the last week.

in Acme Packet (MOSC) 11 commentsAnswered ✓

I just started having problems with call transfers to external numbers from auto attendants in Teams so I wonder if anyone is seeing anything similar.

What I see is when a Refer comes back from Teams the host URI in the Refer-To header is specified as sip.pstnhub.microsoft.com and the SBC sends a 202 accepted back to Teams then followed by an Invite going back to Teams that Teams than rejects with SIP/2.0 403 Forbidden with an error of "Get Outbound routing - No viable path" contained in the details.

This is all in an environment where call forwarding to external numbers from auto attendants has been working for years and the SBC configuration has not changed in over a year. Teams configuration within my control has also not changed. It feels like something has changed on the Microsoft side but unfortunately I don't have a call trace from when this was working to be able to compare to what I am seeing now.

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