Acme Packet (MOSC)

MOSC Banner

Advice re. access-control entries in an access-SBC envrionment

in Acme Packet (MOSC) 12 commentsAnswered

Hi!

We have an access-SBC environment up and running for MANY years, it is configured with Dynamic HNT etc., and the "access-control-trust-level" for the Internet-facing realm is configured to "low". Registered end-points are promoted to a higher trust level with the built-in functionality in the SBC after successful registration in the registrar. So far so good, the DoS protection kicks in now and then and dynamically blocks IP addresses temporarily etc.

The internet-facing realm has no access-control entries in the configuration (=the trust is inherited from/set in the realm config?). However, now I want to permanently block some spammer's IP that is sending tons of registration attempts with unique src_ip/src_port (untrusted-signal-threshold doesn't catch them correctly) by adding the black-listed IP to an access-control entry specifying this realm, source-address, destination-address, application protocol, and access=deny + trust-level=none.

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