Acme Packet (MOSC)

MOSC Banner

Unable to determine why End-Point keeps going into "deny-list" while on call

edited Jan 8, 2013 10:24AM in Acme Packet (MOSC) 5 commentsAnswered

Hi

 

We have a realm configured with a "low" trust level, when making a call from one of the Registered End-Points, while on call the end-point keeps going into the "deny-list" but I'm unable to determine why and what invalid-siganling is causing this?

 

Here is the demote event I keep seeing in the "acmelog"

 

Dec 19 14:04:18.371 sipd@NODE1: MINOR SigAddr[jhb-access:196.2.19.52:62376=low:NONE] ttl=332 exceeded error threshold of 1
Dec 19 14:04:18.371 sipd@NODE1: MINOR recent(32): msgs=0 errs=2 adm fail=0
Dec 19 14:04:18.371 sipd@NODE1: MINOR lifetime: msgs=70 errs=140 adm fail=0

 

The following configuration has been applied to the realm:

 

average-rate-limit 0
access-control-trust-level low
invalid-signal-threshold 1
maximum-signal-threshold 4000
untrusted-signal-threshold 0

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