Acme Packet (MOSC)

MOSC Banner

Egress Realm Precedence for SIP OPTIONS and Normal Requests

edited Apr 24, 2013 9:58AM in Acme Packet (MOSC) 2 commentsAnswered

Hi,

I'm posting this info here as I've seen this question several times from different customers before.

When we have one Session-Agent that belongs to multiple realms, i.e. is a Global Session-Agent that can be reached via multiple realms, the realm-id of this SA definition is '*'.

Customers report that once the realm-id is changed to * the SIP OPTIONS requests stopped being sent out towards the SA.

When your Session-Agent is global, the parameter egress-realm-id should be configured indicating to the SD what's the realm that should be used to send out the SIP OPTIONS requests used to monitor the availability of the Session-Agent.

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