Acme Packet (MOSC)

MOSC Banner

recurrent SNMP .1.3.6.1.4.1.9148.3.2.6.0.15 traps

edited May 21, 2014 4:30AM in Acme Packet (MOSC) 1 commentAnswered

 Hi!,

 

I'd like to know if any of you guys have experienced this situation before, We're recieving large ammounts of the following trap:

 

 

apSysMgmtSAStatusChangeTrap:
1.3.6.1.4.1.9148.3.2.6.0.15

 

Looking at the MIB guide we found out that:


Generated when a session agent is declared unreachable or unresponsive for the
following reasons:
•signaling timeout (H.323 and SIP)
•session agent does not respond to SIP pings (SIP only)
When session agents are declared unreachable or unresponsive, they are placed out-of-service for a configurable period of time.

 

So this means possibly that connectivity is failing?, I'm not sure if this would be the only cause since we have not been reported calls failing or something in that fashion ofr this session agent.

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