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)

cam error

Sep 26, 2014 4:12AM edited Sep 29, 2014 3:29PM in Acme Packet (MOSC) 1 commentAnswered

adding 61st access-control

1: src XXX.21.0.0/17; 0.0.0.0; access; SIP; ALL
2: src XXX.236.40.0/21; 0.0.0.0; access; SIP; ALL
3: src XXX.90.240.0/20; 0.0.0.0; access; SIP; ALL
4: src XXX.78.192.0/18; 0.0.0.0; access; SIP; ALL

61: src XXX.156.64.0/18; 0.0.0.0; access; SIP; ALL

acmelog
brokerd@Acme: MAJOR ALARM[00010014] Task[0f944480] error adding nat information in cam table
brokerd@Acme: CRITICAL ALARM[00010014] Task[0f944480] error adding nat information in cam table

Acme#display-alarms
65556 408949712
Count Description error adding nat information in cam table
131101 423931280
Count Description health score is under threshold 25%

Acme# sh health

Media Synchronized true
SIP Synchronized true
MGCP Synchronized true
H248 Synchronized disabled
Config Synchronized true
Collect Synchronized disabled
Radius CDR Synchronized disabled
Rotated CDRs Synchronized disabled

Tagged:

SEC- Security and Compliance

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