
144 Chapter 2 Fault Management System
P0609330 2.0
Alarm severity: Critical
Trap-type: Error
Logs: None
Comments: Detected possible linked list corruption. Attempts to repair list.
Event ID: 4044 Message: Linked List has unexpected number of entries. %2.
User action: Reboot system.
Alarm severity: Minor
Trap-type: Warning
Logs: None
Comments: Count of entries in linked list is out of sync with the actual number.
Event ID: 4045 Message: %2: H225 setup message exceeds message fragment buffer. %3
User action: Need to reduce the number of codec choices. This will reduce the size
of the setup message.
Alarm severity: Minor
Trap-type: Warning
Logs: None
Comments: H.225 setup message is larger than internal storage buffer. Call may
not go through properly. i.e. one-way speech
Event ID: 4046 Message: %2: Processing more than one fragmented H.225 setup message.
User action: No action required.
Alarm severity: Warning
Trap-type: Informational
Logs: None
Comments: Detects when two setup messages are being processed at the exact
same time.
Event ID: 4047 Message: SIP parser error: %2
User action: Send NT event log and stlog to development / ITAS. Check if there are
any non-SIP packets going through the BCM via the port 5060.
Alarm severity: Critical
Trap-type: Error
Logs: None
Comments: This can happen when there is a SIP parser error or when a non-SIP
packet passes the driver via the default 5060 SIP port.
Event ID: 4048 Message: SIP Init Failure. %2: %3. Please check that mspqos.sys is properly
loaded.
User action: If SIP is to be used as the VOIP protocol, reboot system to make sure
mspqos.sys is loaded properly and that there are no memory
allocation issues.
Alarm severity: Critical
Trap-type: Error
Logs: None
Comments: SIP structures used in driver are not properly initialized.
Event ID: 4049 Message: OSIP Failure. %2: %3.
mspQoSMP Return to table: Component ID (alarm)/eventSource (trap) summary
Comentários a estes Manuais