Acme Packet (MOSC)

MOSC Banner

Using Session Agents with Multiple Realms

edited Sep 10, 2014 2:39PM in Acme Packet (MOSC) 1 commentAnswered

 

I read the documentation on how to resolve the 409 error when using session agents within multiple realms.  The documentation have you either use an wildcard *, leave blank for the realm id.  The SD will use the local policy for routing. If an SAG is used as an policy attribute then all session agents within the SAG should be unique either with the wildcard *, left blank or consistent name as the realm id.

 

I'm asking for clarification - Does this mean I can create a SAG and add all sessions agents used for inbound and outbound call processing within this SAG group? Can someone confirm this?

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