Acme Packet (MOSC)

MOSC Banner

Access Control mystery

in Acme Packet (MOSC) 14 commentsAnswered ✓

Hello,

I run vSBC 9.2.0p6. The customer has reported a problem related to the ACLs and I tried to reproduce it in a lab. I run the simplest configuration I could have - 2 realms and almost all items in defaults.

The inbound realm (called parent, but there's no child/parent configuration) does not use access-control (initial-trust-level is none), and there is a static access-control:

access-control
realm-id parent
description
source-address 10.4.14.130 //call.gen. IP
destination-address 10.4.11.78 //parent sip-int IP
application-protocol SIP
transport-protocol UDP
access permit
average-rate-limit 0
trust-level low
minimum-reserved-bandwidth 0
invalid-signal-threshold 0
maximum-signal-threshold 620
untrusted-signal-threshold 430
deny-period 30
nat-trust-threshold 0
max-endpoints-per-nat 0
nat-invalid-message-threshold 0
cac-failure-threshold 0
untrust-cac-failure-threshold 0

After reboot I see this:

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center