Description: MGCP: This trap indicates NCS Media Gateway endpoint has 
reported an ErrorCode or a Reason Code:

error
code      commentary
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
400       The transaction could not be executed, due to 
          a transient error
502       The transaction could not be executed because the 
          endpoint does not have sufficient resources
504       Unknown or unsupported command (this code is in 
          RFC3435, but not in PacketCable NCS I07)
507       Unsupported functionality (this code is in RFC3435,
          but not in PacketCable NCS I07)
508       Unknown or unsupported quarantine handling
510       The transaction could not be executed because a 
          protocol error was detected
516       The transaction refers to an unknown call-id
518       Unsupported or unkown package
520       The transaction could not be executed because 
          the endpoint is restarting
526       Insufficient bandwidth
528       Incompatible protocol version
529       Internal hardware failure
534       Codec negotiation failure^M
            
reason
code      commentary 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
900       Endpoint malfunctioning
901       Endpoint taken out of service
902       Loss of lower layer connectivity (e.g., downstream 
          sync)
903       QoS resource reservation was lost

An example of rtpEvtShortText will be as follows:

errorCode or reasonCode Commentary TransactionID 
EndPointID@Hostname Protocol

where:

error code or reason code           as in the above 
                       
Commentary                          as in the above

TransactionID                       0..999,999,999
        
EndPointID(Id for the Line or DS0)  aaln/1, aaln/2, aaln/3, aaln/4 
                 
Hostname                            fully qualified domain name

Protocol                            MGCP 1.0 NCS 1.0
 
An example of rtpEvtShortText will be as follows:

520 Endpoint malfunctioning 18 aaln/1@motomta101.ipfonix.com  MGCP 1.                              0 NCS 1.0

This trap is informational. There is no corresponding trap for its 
                      its abatement(clear).
 To avoid flooding the element manager system, this trap will be 
suppressed if the same msgType is received from the same hostname  
twice in a pre-determined suppresion interval of 15 seconds.