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)

Global Session Agent, multiple SIP Interfaces, source?

Apr 1, 2014 2:56PM edited Apr 4, 2014 7:01PM in Acme Packet (MOSC) 1 commentAnswered

I want to have just one global SA towards my ITSP, but multiple SIP Interfaces. Each customer on a unique SIP Interface on the outside.

When sending traffic from Inside to Outside, using local-policy, how does it know which SIP Interface to source from?

I'm hoping by the local-policy next-hop realm, and thus the SIP-Interface in the realm?

Regards

Roger

Tagged:

SIP - Signalling, Trunking and Interconnect

1

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