1-25
Cisco SRST SNMP MIB Release 3.4 Guide
OL-7959-01
Chapter 1 Cisco SRST SNMP MIB Support
Configuration
csrstSipEndpointIpAddrType.2 = ipv4(1)
csrstSipEndpointIpAddrType.3 = ipv4(1)
csrstSipEndpointIpAddress.0 = ipv4:1.4.196.41:26057
csrstSipEndpointIpAddress.1 = ipv4:1.4.196.1:5060
csrstSipEndpointIpAddress.2 = ipv4:1.4.196.41:26057
csrstSipEndpointIpAddress.3 = ipv4:1.4.196.1:5060
csrstSipEndpointDN.0 = 5001
csrstSipEndpointDN.1 = 5001
csrstSipEndpointDN.2 = 5002
csrstSipEndpointDN.3 = 5002
Receiving Notifications/Traps
Notifications and traps are asynchronously generated by SRST to pass information about certain device
status changes.
Table 1-4
lists the SRST notifications/traps and additional information regarding each
notification or trap.
There is no reason string or severity sent with the following traps:
•
csrstSipPhoneUnRegThresholdExceed
•
csrstSipPhoneRegFailed
•
csrstConferenceFailed
The following list contains all the CISCO-SRST-MIB traps.
•
csrstStatusChange - SRST status change trap (Up)
*Mar 7 20:56:23.207: SNMP: V1 Trap, ent ciscoMgmt.441, addr 1.4.196.10, gentrap
Table 1-4
SRST Notifications/Traps
Notification/Trap
Reason
Severity
csrstStateChange
SRST system state change up
Minor
csrstStateChange
SRST system state change down
Minor
csrstStateChange
SIP SRST system state change up
Minor
csrstStateChange
SIP SRST system state change down
Minor
csrstFailNotif
Skinny listening socket setup error
Minor (when system is
running)
csrstFailNotif
Maximum number of allowed sockets has been exceeded
Minor (when system is
running)
csrstFailNotif
Skinny server initialization failed
Sockets initialization failed
Major (at initialization)
csrstFailNotif
Skinny server initialization failed
Not enough memory
Major (at initialization)
csrstFailNotif
Not enough memory to create Registrar Control Block (rcb) for SIP
Voice Register DNS
Minor
csrstFailNotif
Not enough memory to create Call Control Block (ccb) from SIP
registrar outgoing
Minor