This section details all SBC Edge Portfolio alarms and events. The SBC Edge Portfolio displays these alarms in the Viewing Alarms and Events and are configured in the Configuring Alarms and Events page.
Hardware-related Alarms and Events are not applicable for SBC SWe Edge.
The following list provides the alarms and events defined in various SBC Edge Portfolio subsystems.
Decode Key Table
The following table defines the decode key types used throughout the system Alarms and Events in the SBC 1000/2000.
Decode Key | Description |
|---|---|
System | By default it will be the SBC 1000/2000 system |
Service | Service in which this alarm/event belongs to, for ex. ISDN, SIP etc.. |
Username | Username responsible for the generation of the alarm/event, mostly related to the User Authentication Service |
IP address | IP address of the system responsible for generation of this alarm/even. |
Frame | Frame responsible, at which the data transmission has failed/generated an error |
Card/Slot | Card /Slot involved in generating the alarm For ex. TI DSP etc.. |
ActSetTble | Action set table number responsible for the alarm/event |
NormTble | Normalization table number responsible for this alarm |
RtTble | Route table number responsible for this alarm/event |
| TLSProfile | TLS Profile (ID of the TLS Profile) |
TransTble | Translation table number responsible for this alarm/event |
Call Dest | Call destination (address) responsible for this alarm/event |
Conference ID | Conference ID involved in the alarm generation. It will be an integer starting from 1 to FFFFFFFF |
Codec | Media codec like G711, used when this alarm is generated |
SG/Signaling Group | Signaling Group on which this alarm occurred |
Channel | Channel number that involved in generating this alarm |
CallID | Call ID of the call failed/is responsible for generating this alarm |
Port | Port number on which this alarm is generated |
Interface | Name/Number of the interface involved in generating this alarm. For ex. ETH1, T1 etc.. |
Server | Server responsible for this alarm. for Ex. SIP server which is not responding |
CertificateCommonName | Server certificate common name for ex:"VeriSign Trial Secure Server CA - G2 " |
SBAInstance | Its the SBA monitor involved in generating the alarm |
Interface | By default it will be the Ethernet interface card |
SIPCluster | Name of the SIP cluster associated with a set of SIP servers |
ServID | ID of the SIP server |
Protocol | Protocol involved in generating this alarm/event |
Fan_No | Fan number |
Overview
Content Tools