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)

Preventing call loops

Aug 27, 2014 1:21PM edited Aug 29, 2014 2:22PM in Acme Packet (MOSC) 4 commentsAnswered ✓

Hello,

I'm using ENUM based routing between the SIP provider and different IP-PBX in a E-SBC environment. A typical local policy looks like:

from *
to <customer DDI range>

source-realm IP-PBX1

policy-attributes

next-hop enum:enterpriseENUM

realm (empty)

Is there a simple way to prevent call loops, e.g. do not allow calls from a SIP interface to be routed back to the same SIP interface?

Best regards,

Alain

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