Acme Packet (MOSC)

MOSC Banner

To-tag updated on private side, why?

edited Jan 11, 2014 3:34PM in Acme Packet (MOSC) 2 commentsAnswered

I have a call going from an application server (private side) to an Acme 4500 (ver. 6.3.7) which sends the call out to one of our providers (public side), the first provider sends an error message so via SAG regression a secondary IP is tried.  I will preface my question with the fact that dialog-transparency is set to disabled and my operation-mode is set to dialog in my sip-config.

 

The question is, with the Acme Packet setup to act like a true B2BUA why when the 183 comes in from the secondary IP would it update the To-tag on the private side when all the retries and errors are being handled on the public side?

Tagged:

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