Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Acme Packet (MOSC)

Routing: Policy-atrribute VS session-agent-group

Mar 27, 2013 12:25PM edited Mar 27, 2013 4:53PM in Acme Packet (MOSC) 3 commentsAnswered ✓

Hi community!

I have some questions about local-policy-attributtes and routing, we are using Net-Net 6.3.x and 6.4.x.

To do a single HUNT strategy we have two different options (of course depending of the licenses on use):

Create a SAG with the two SA and use Hunt strategy.
Create two different policy-attributes with the same cost.

Both options allow you recurssion (test on one SA and if it did not work use the next SA).

The questions are several:

What are the differences between the two methods? Wich one would give a better performance?
A SA is always attached or linked to a unique realm, what is the idea of the field "realm" on the policy-attributes? is this field deprecated? (still active on NetNet 6.4.0)

Tagged:

SIP - Signalling, Trunking and Interconnect

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month