Acme Packet (MOSC)

MOSC Banner

Acme Packet v9.1- Teams Refer routing - Derive static Diversion headers from Refer

in Acme Packet (MOSC) 1 commentAnswered

Our setup is an acme pair in a DMZ connected to Teams over a Direct routing trunk. For PSTN calling, the DMZ acme's route to a separate acme pair which is connected to the carrier's SIP trunk. The carrier requires a valid DID in the From, PAID, or Diversion header to authenticate the call.

From Teams, I've configured a Call Queue with DN=Japan DID which is call forwarded to my mobile phone. If I dial the Call Queue from my Teams client, I see a single invite with the Referred-by header including the the Japan DID. If I dial the Call Queue from my mobile phone, I see the inbound call to Teams and then a Refer message with the orig call dialog tags. I do not see the original dialed number from teams, only the calling and forward destination in the Refer message.

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