You are here: CSP API Reference > 1 EXS & SwitchKit API Messages > Alarm 0x00B9

Alarm 0x00B9

SwitchKit Name

Alarm

Type

EXS API and SwitchKit API message

Description

Alarm 0x00B9

The CSP sends Alarm 0x00B9 message to indicate that an alarm condition has been detected. The following information is reported:

• Severity

• Alarm Type

• Alarm Number

• Alarm Data

Alarm Cleared

In some cases, the CSP sends an Alarm Cleared message after the alarm condition ceases. The alarms that are followed by an Alarm Cleared message are marked with an asterisk (*).

Related Messages

Alarm 0x00B9Alarm Cleared (AlarmCleared) 0x00C1

Sent by

CSP

SwitchKit Code

C Structure

typedef struct {

UBYTE InfoSize;

UBYTE Severity;

UBYTE Entity;

UBYTE AlarmNum;

UBYTE Info[249];

} XL_Alarm;

C++ Class

class XLC_Alarm : public XLC_InboundMessage {

public:

UBYTE getInfoSize() const;

void setInfoSize(UBYTE x);

UBYTE getSeverity() const;

void setSeverity(UBYTE x);

UBYTE getEntity() const;

void setEntity(UBYTE x);

UBYTE getAlarmNum() const;

void setAlarmNum(UBYTE x);

const UBYTE *getInfo() const;

UBYTE *getInfo();

void setInfo(UBYTE *x);

};

Resent in EXS API

This message is resent once after five seconds.

EXS API Hex Format

MESSAGE (White) | RESPONSE (Gray)
Byte | Field Description | Byte | Field Description
0 | Frame (0xFE) | 0 | Frame (0xFE)
1, 2 | Length (0xNNNN) | 1, 2 | Length (0x0005)
3, 4 | Message Type (0x00B9) | 3, 4 | Message Type (0x00B9)
5 | Reserved (0x00) | 5 | Reserved (0x00)
6 | Sequence Number | 6 | Same Sequence Number
7 | Logical Node ID | 7 | Logical Node ID
8 | Checksum
8 | Severity 0x01 Informative 0x02 Minor 0x03 Major
9 | Alarm Type 0x01 General Alarms 0x02 Card Alarms 0x03 Span Alarms 0x04 Channel Alarms 0x05 DSP SIMM Alarms 0x06 DSP Alarms 0x07 Node Alarms 0x08 DS3 Alarms 0x09 VoIP Module Alarms 0x0B SIP Alarm
10 | Alarm Number (see table below)
11 | Data Length (n)
12 | Data[0] (if applicable)
: | Data[n-1]
: | Checksum

Alarm Type

The table below contains a summary of the alarms showing the range of alarm numbers for each type and the length.

Alarm Information

See the table for each alarm type below for the following information:

• Alarm Severity

• Alarm Number/Alarm

• Data Length

• Data

Summary of Alarms

Alarm Type | Alarm Number Value or Range | Data Length
--- | --- | ---
0x01 General | 0x01-0x1F, 0x21-0x22 | Variable
0x02 Card | 0x01-0x1C | Variable
0x03 Span | 0x01-0x05 | 0x06
0x04 Channel | 0x02 | 0x17
0x03 | 0x12
0x05 DSP SIMM | 0x01-0x06 | 0x06
0x06 DSP | 0x01, 0x02 | Variable
0x07 CSP Node | 0x01-0x08, 0x0A-0x15 | 0x06
0x08 DS3 | 0x01 - 0x03 | 0x07
0x09 VoIP Module | 0x00, 0x01, 0x02, 0x03 | 0x07

0x01 General Alarms

Severity | Alarm (Number/Name) | Data Length | Data/Troubleshooting
--- | --- | --- | ---
Major | 0x01* | System busy condition The CSP sends this alarm when the CSP Matrix Series 3 Card is flooded with messages. The CSP will ignore all incoming calls until the alarm is cleared. | 0x00 | The system ignores incoming calls until the alarm is cleared. Ignoring incoming calls decreases the traffic load and eventually the alarm will clear. Ensure that System Busy Warning messages are no longer being seen. Slowly ramp traffic back to normal levels and resume normal operation.
Major: Default Minor: If clock mode was switched to REF1 or REF2. | 0x02 | Clock mode switched | 0x02 | The system automatically switches the clock mode to the next available clock source and reports the following data to the host: Data[0] - Current Synchronization Mode Data[1] - Previous Synchronization Mode Values for Data[0] and Data[1] fields: 0x01 Primary Reference Clock Signal 0x02 Secondary Reference Clock Signal 0x03 Primary Loop Clock Signal 0x04 Secondary Loop Clock Signal 0x05 Free Running Clock Signal _______________________________ This notification occurs when the clock mode was automatically switched or reference clock sources have been lost. The CSP will automatically set the clock mode to the next available clock source. Either a master timing source has been disconnected or gone bad, or a span signal has been lost. Investigate why the signal has been lost and try to restore it if possible. This signal may be controlled by the network in which the Loop timing is dependent.
Inform. | 0x03 | Hardware cannot support DSP function |  | Verify the correct card type.
Major | 0x04* | Reference 1 Clock Source Lost No host intervention is needed. The CSP will automatically switch the clock mode to the next available clock source. | 0x00 | The system automatically switches the clock mode to the next available clock source. The Reference Clock Source has been lost. No host intervention is needed for this occurrence. The CSP will automatically switch the clock mode to the next available clock source. Have Operational Personnel Check to see what happened to the External Timing Source Connected the CSP Matrix I/O.
Major | 0x05* | Reference 2 Clock Source Lost No host intervention is needed. The CSP will automatically switch the clock mode to the next available clock source. | 0x00 | The system automatically switches the clock mode to the next available clock source. The Reference Clock Source has been lost. No host intervention is needed for this occurrence. The CSP will automatically switch the clock mode to the next available clock source. Have Operational Personnel Check to see what happened to the External Timing Source Connected the CSP Matrix I/O.
Major | 0x06 | DSP Resource Blocked | 0x01 | Data[0] DSP Function Type
Major | 0x06 | DSP Resource Blocked | 0x04 | Data[0] Slot where VRA Block occurred Data[1] Chain across SIMMs Data[2-3] RAN ID blocked _______________________________ The CSP will send this alarm when all the resources of the particular resource type are all in use. The request to use a specific resource is placed in a queue until there is a resource of the alarmed type freed. The request is placed in a queue waiting for a resource to free unless a DSP Service Cancel (0x00BE) message is send by the host or the channel that the resource was requested on is release. See the DSP SIMM Configure (0x00C0) message in the API Reference and the CSP Developer’s Guide: Overview for details on DSP function types. Either wait for the resource requested to free up which is the most likely response. Send a DSP Service Cancel (0x00BE) message. Release the channel that the resource was requested on. If you find that the CSP is reporting a large number of these alarm it maybe a good idea to re-evaluate the number of resources per function type you have configure. You may need to increase the number of configured functions type.
Major | 0x07 | DSP Resource Function Type Not Configured | 0x02 | Data[0] Resource Type Data[1] Resource Type 2 (0x00 if no second resource type) _______________________________ The DSP function type requested is not configured and will need to be configure in order to use the resource being requested. Can also indicate a function is configured but the SIMM is out-of-service. See the DSP SIMM Configure (0x00C0) message in the API Reference and the CSP Developer’s Guide: Overview for details on DSP function types. Configure the DSP function type for the resource being requested.
Major | 0x08 | DSP Resource Management Inconsistent. (An internal task has asked to attach the same type of DSP resource to a single timeslot twice. This Alarm is sent when: - A receiver has been requested but a Call Progress or Digit receiver for the same layer is already attached to the timeslot - A transmitter has been requested but a Digit or Recorded Announcement transmitter for the same layer is already attached to the timeslot | 0x09 | Data[0-6] 0x0D Channel AIB (Dialogic use only) Data[7] Process Virtual Identifier (The process that requested the DSP service. For example, Call Control, Layer 4, or E1 PPL) (Dialogic use only) 06 - L4 PPL call processing 11 - Logical ID for all Layer 3's 1A - Layer 3 Plus 24 - SS7 25 - SS7 MTP2 28 - E1 Protocol Layer PPL 29 - T1 Protocol Layer PPL Data[8] Resource Type (The DSP Resource requested. For example, DTMF Digit Transmitter). 00 - Outpulse CP 01 - Outpulse digits 02 - Collect CP 03 - Collect digits 04 - Conference 05 - Outpulse Announcement 06 - Detect energy 07 - Broadcast 08 - Collect FSK 09 - Outpulse FSK 0A - Detect coin 0B - Play file 0C - Record file 0D - Modify play 0E - Fax XMT 0F - Fax RCV 10 - Modify record 11 - Echo cancel XMT 12 - Echo cancel RCV 13 - PVD/AMD RCV _______________________________ An internal task has asked to attach the same type of DSP resource to a single timeslot twice. Free the resource that is attached to the timeslot. Send down a DSP Service Cancel (0x00BE) message to release the channel and start a new call.
Inform. | 0x09 | Download Record Timeout | 0x00 | Restart the download. This alarm only concerns legacy download procedures. The Series 3 Matrix card supports only Full TFTP. The host must follow each download message with another download message or a Download Complete message within five minutes, or the download aborts. For example, when a Download Begin BRecord is sent, a Download BRecord must follow within five minutes. The Download BRecord must be followed by either another Download BRecord or Download Complete within five minutes. Check ethernet connectivity or the application's download module for delays. Restart the download. If problem persists contact Dialogic Technical Support. Please be advised that an Ethernet capture may be requested.
Major | 0x09 | Invalid Associated Channel | 0x03 | Data [0] Logical Span ID MSB Data [1] Logical Span ID LSB Data [2] Channel _______________________________ Verify the configuration and call flow in the socket.log file. If the problem persists, contact Dialogic Technical Support
Inform. | 0x0A | Partial Message Received (for example, incorrect checksum, zero length message, or message did not begin with frame character) | 0x00 | Partial Message Received (for example, incorrect checksum, zero length message, or message did not begin with frame character) Collect the socket.log, alarm.log, maintenance_llc_xxx.log and a list of the applications running on the system and contact Dialogic Technical Support.
| 0x0B | RAN Requested is Unavailable in System |  | Check if this announcement was reached in error. Check in the Vocabulary Index File to see if the file ID is listed there. If it is listed, then report the problem to Dialogic Technical support along with socket.log, alarm.log, and timestamp of when the trap occurred.
Inform. | 0x0C | Unacknowledged Message If you configured the system’s message resend logic to "Resend Once and Generate Alarm," these data fields contain the bytes of the resent message. For more information, refer to the System Configuration message. | Variable | Data[0-N] The bytes of the message _______________________________ Check for other error messages that would indicate a network or system condition leading to this problem.
Major | 0x0D | Recorded Announcement ID Inconsistency | 0x04 | Data[0] Slot Number Data[1] SIMM Number Data[2, 3] RAN ID _______________________________ Sent upon completion of download or on card Insertion. This alarm indicates that an announcement being downloaded has the same ID as an existing announcement, but with different information. When the ID is specified in the Recorded Announcement Connect message, either announcement could be played. Each RAN must have a unique ID. One of the announcements (usually the older one) should be deleted. A Query addressed to one RAN ID returns information for only one of the RANs that share the ID. It is not possible to determine for which RAN the information will be returned. For example, if one file sharing the ID is 20 Kb and one file is 40Kb, only one of the sizes is reported, either 20 Kb or 40 Kb, but not both.
Minor | 0x0E | SS7 Signaling Network Congestion When a route to a destination is congested, MTP sends the MTP_STATUS to ISUP which in turn sends this alarm to the host. | 0x06 | Data[0] SS7 Stack ID Data[1-4] DPC Data[5] Congestion Level _______________________________ Decrease the load or create a new route to the destination. If the system has not decreased the call load and this symptom persists, check the network engineering plan to possibly create a new route to the destination.
Major | 0x0F* | SS7 Remote ISUP Unavailable | 0x05 | Data[0] SS7 Stack ID Data[1-4] DPC _______________________________ SS7 Remote ISDN User Part (ISUP) unavailable. The address information represents the SS7 stack and Destination Point Code (DPC). Check the status of the Links and see if they are in service by sending the SS7 Signalling Link Query (0x0065) message. If they are not in service, attempt to determine why the links are Out Of Service. Make sure that they are marked in service from a host perspective using the Service State Configure (0x000A) message. Also check the status of the SS7 Signalling Routes using SS7 Signalling Route Query (0x0066). If the routes are unavailable, contact your SS7 service provider and ask why they are not in service. Also check the status of layer 1 span using Span Status Query (0x0084) message. This will tell you if the span is in sync, and if not how many slips and errors occurring on the physical span.
Major | 0x10 | Node ID Already Exists | 0x00 | Check configuration and/or installation for correction.
Inform. | 0x11 | Invalid Message Length | 0x00 | The application software sent a message with an invalid length field. Provide the application development team and Dialogic Technical support with the socket.log and the information from the trap.
Major | 0x12 | System Busy Warning | 0x00 | This notification indicates that the traffic volume on the CSP is approaching its capacity. This message is only a warning. It does not mean a System Busy condition will definitely occur. The System Busy Warning does not have a clearing Alarm. It continues to occur every few seconds, until the CPU utilization reduces. The System Busy Warning messages can be between 2 and 20 seconds apart, depending on system load fluctuations. The EXS CSP CPU occupancy has exceeded the "System Busy Warning" threshold. This condition can happen due to traffic congestion or CSP configuration during high traffic or by having Debug printing enabled on a CSP card or cards. When a System Busy Warning is generated, the Host should reduce the number of new calls until the System Busy Warning messages cease. Whenever possible, ramp call rates up slowly and evenly to prevent an initial System Busy. Do not re-configure the CSP and do not enable unnecessary diagnostics. For more information on this alarm, refer to the CSP Developer's Overview Guide, Chapter 4 EXS API Application Development, section System Busy Warning and System Busy Alarm.
Inform. | 0x13 | Resource Utilization Threshold Reached | 0x01 | Data[0] Free Conferencing Timeslots (0x01) _______________________________ This normally occurs during high traffic and high utilization of conference resources. Calculate the number of free timeslots available for EXS Conferencing using the System Resource Usage Query. Determine if free timeslots need to be made available. For complete information see CSP Conferencing Section in the Configuring Multi-Node Systems of the Developer’s Guide: Overview.
| 0x14 | Subrate Resources Unavailable |  | The subrate resource (channels) provided by the SRC card are no longer available as (possibly) the card has been removed. Find out what the Subrate Card Status is and take actions depending on the result. Reset or change the card. If that does not work, contact Dialogic Technical Support.
Major | 0x15 | SS7 Remote TUP Unavailable | 0x05 | Data[0] SS7 Stack ID Data[1-4] DPC _______________________________ Bring remote Telephone User Part in service.
Major | 0x16* | ISDN/SS7 Signaling Stack Congestion | 0x03 | Data[0] Stack ID (SS7), Board Slot Number (ISDN) Data[1] Direction: 0x00 Incoming 0x01 Outgoing Data[2] Status: 0x00 Congestion Cleared (Alarm Cleared) 0x01 Congestion Level 1 0x02 Congestion Level 2 0x03 Congestion Level 3 _______________________________ Decrease the load on the ISDN/SS7 card. Consult Dialogic Technical Support. Calls will resume to normal after the congestion clears. You will receive an alarm cleared message when this occurs.
Inform. | 0x17 | Route Table Updated | 0x01 | Data[0] Table ID (1-10) _______________________________ The active route table has been updated. The address information represents the table ID of the route table. Verify the route table is changed correctly.
Inform. | 0x18 | Resource Group Table Updated | 0x01 | Data[0] Table ID (1-10) _______________________________ The active resource group table has been updated. The address information represents the table ID of the route table. Verify the resource group table is changed correctly.
Inform. | 0x19 | Old Route Table Deleted | 0x01 | Data[0] Table ID (1-10) _______________________________ A previously active routing table has been deleted. The address information represents the table ID. Verify that the table being deleted is no longer needed.
Inform. | 0x1A | Old Resource Group Table Deleted | 0x01 | Data[0] Table ID (1-10) _______________________________ A resource group table has been deleted. Verify the table being deleted is no longer needed.
Inform. | 0x1B | Route Table Forcefully Deleted | 0x01 | Data[0] Table ID (1-10) _______________________________ The active route table was forcefully deleted. The address information represents the table ID. Verify the table being deleted is no longer needed.
Inform. | 0x1C | Resource Group Table Forcefully Deleted | 0x01 | Data[0] Table ID (1-10) _______________________________ The active resource group table has been forcefully deleted. The address information represents the table ID. Verify the table being deleted is no longer needed.
Major or Minor (see Data) | 0x1D | Flash Copy or Load Problem | 0x02 | Data[0] Severity 0x00 Major 0x01 Major 0x02 Major 0x03 Major 0x04 Minor 0x05 Minor 0x06 Major Data(1) Entity Valid entries for this field based on the Entity field value 0x00 are as follows: 0x00 Flash erase failed 0x01 Flash write failed 0x02 RAM load to copy is bad 0x03 Flash load bad after copy from RAM 0x04 RAM and flash have different timestamps 0x05 RAM load bad after a soft reset 0x06 RAM load bad after copy from Flash _______________________________ There is a problem during the flash or RAM loading. Contact Dialogic Technical Support.
Major | 0x1E | TFTP Alarm | Variable | Typically the following events result in this alarm. 1. Filename/path that is returned in BOOTP Response does not match. 2. TFTP Server is not reachable or running. 3. TFTP Configuration File indicates a load that is not resident or incorrectly named on the TFTP Server. 4. The TFTP file has been altered from previous version. There are four things to validate: 1. Verify that TFTP is running on the machine with the software files. 2. Verify that the TFTP Server is a reachable ethernet address from the CSP. 3. Verify that the BOOTP response indicates the correct name and path of the tftp configuration file. 4. Verify that the tftp configuration for the all .bin files specified in the tftp configuration exist on the TFTP server and contain the correct path and filenames of the software .bin files. Assume Dialogic Technical support will require information on BOOTP, TFTP, and Ethernet setups. An ethernet trace may be required. Debug access to the Matrix may also be required. See 0x1E TFTP Alarm after this table.
Major | 0x1F | System Memory Low |  | System memory has dropped below the minimum level of satisfactory performance. When the system is in this condition, it is also in a System Busy condition and the CSP sends a System Busy Alarm (0x01) to the host. Check for other error messages that would indicate a network or system condition leading to this problem. Check Ring Interface hardware and then bring the ring in service.
Major | 0x20 | System Memory Low Cleared |  | Indicates that the system returns to the minimum level of satisfactory performance. The CSP sends a System Memory Satisfactory Alarm (0x20) to the host, along with an Alarm Cleared (0xC1) message. Resume normal operation.
Major | 0x21 | Host Connection Dropped | 0x02 | Data[0] Multi-host port ID 0x3142 - 0x3147
Major | 0x22 | EXNET Ring Down | 0x08 | Data[0-4] Slot AIB Data[5] Logical Ring ID Data[6] Host Service State Data[7] EXNET Ring Error Status _______________________________ This notification is sent when an EXNET® ring goes down. The address information represents the slot of the EXNET-ONE card and logical ring ID of the ring.
Inform. | 0x2F | Log F/Log B Buffer is 75% Full |  |
Inform. | 0x30 | Log T Buffer is 75% Full | 0x01 | Data[0] Slot Number _______________________________ Contact Dialogic Technical Support.
Inform. | 0x31 | Log F/Log B Buffer is Full | 0x01 | Data[0] Slot Number _______________________________ Contact Dialogic Technical Support.
Inform. | 0x32 | Log T Buffer is Full | 0x01 | Data[0] Slot Number _______________________________ Contact Dialogic Technical Support.
| 0x33 | MGC Lost Connection |  |
Inform. | 0x34 | DSP CPA Configuration Conflict | 0x04 | Data[0] Tone Group: 0x00 Data[1] Tone ID: 0x10 Data[2-3]Frequency 0x01-0xA4 _______________________________ Consult the CSP Developers Guide: Overview for details on configuring CPA. Modify the configuration.
Major | 0x35 | ISDN Congestion |  |
| 0x3A | SS7 Signaling Destination Congestion Sent to the host when a particular remote node is congested as indicated by a change in the congestion level. | 0x06 | Data[0] Stack ID Data[1-4] DPC Data[5] ACL Level _______________________________ If the system has not decreased a call to this DPC and this symptom persists, check the network engineering plan to possibly create a new route to the destination.
Major | 0x3B | Signaling Link Congestion When a link is congested, MTP sends MTP Status to ISUP which in turn sends this alarm to the host. | 0x06 | Data[0] Stack ID Data[1-4] DPC Data[5] LINK_CONGESTION_LEVEL _______________________________ If the system has not decreased a call to this DPC and this symptom persists, check the network engineering plan to possibly create another link in the link set.
Inform. | 0x3D | NFS RAM Disk Configuration Failure | 0x03 | Data[0] Slot Data[1,2] Server ID _______________________________ The VIF is missing or wrong. Check NFS settings for the DSP2 Card.
Major | 0x3F | Insufficient Resource Points for DSP Function | 0x01 | Data[0] Function Type _______________________________ The system application has requested more that the allowed resource points configured on the system. Increase the number of resource points in the system with a downloadable license. Contact your sales person to purchase more licenses. You can also contact your sales engineer who can help you design your DSP2 configuration as well as estimate the number of resource points needed.
Inform. | 0x3E | NFS Server Disconnect | 0x02 | Data[0,1] Server ID
Major | 0x40 | DSP Request Queued Due to DSP Series 2 CPU Overload Level 2 | 0x01 | Data[0] DSP Function Type Requested _______________________________ Either reduce recourse requests at the application layer or add more DSP2 cards to the system.
Inform. | 0x41 | Channel has an Echo Canceller resource attached but the requested receiver resource is not available on the same DSP Card. | 0x05 | Data[0] – Slot of DSP Card providing Echo Cancel to channel Data[1] – Function type of requested receiver Data[2, 3] – Span (MSB, LSB) Data[4] - Channel _______________________________ When attaching echo cancellers together with DSP receivers, be sure that the same DSP2 card is being used. The host can force the slot AIB for both message.
Minor | 0x42 | DSP Series 2 FSK General Alarms | 0xnn (Variable) | Data[0] FSK Alarm ID 0x01 FSK Stop ACK Not Rcvd from DSP Chip 0x02 Invalid Resource Type for SMS 0x03 Internal Error Setting PPL Timer Data[1,2] Midplane Time Slot Data[3] DSP Series 2 Slot Data[4,n] Additional Data Specific to FSK Alarm IDs
Major | 0x43 | DSP2 RTP | 0x06 | Data[0] RTP Alarm ID: 0x01 RTP socket open error while Record Data[1] DSP2 slot Data[2-5] File ID
Minor | 0x44 | SCCP/TCAP Capacity Exceeded | 0x04 | Data[0-3] Current "Leaky Bucket" value in TCAP transactions Minor alarm is generated with each one second of licensed bucket capacity exceeded. Major alarm generated once 10 seconds of bucket capacity is exceeded indicating all TCAP transactions are now being rejected. The alarm clears when the bucket capacity returns to a 0.5 second of licensed capacity.

*Followed by an Alarm Cleared message

0x02 Card Alarms

Severity | Alarm (Number/Name) | Data Length | Data/Troubleshooting
| 0x01 | Card Taken Out of Service | Variable | 0x01 Slot AIB _________________________________________ Check with operations personnel to verify card removal. Once card is brought in service, the CSP sends the Alarm Cleared message (0x00C1).
Major | 0x02 | Unable to Allocate Timeslots for this Card | 0x05 | 0x01 Slot AIB _________________________________________ Verify that the CSP contains the required number of available timeslots for this card. If sufficient timeslots are available, contact Dialogic Technical Support.
| 0x03 | Card Download is Corrupt | 0x05 | 0x01 Slot AIB _________________________________________ Reseat the card. Try a different card. Try a different software load. If all above options fail, contact Dialogic Tech Support.
Major | 0x04 | Card Type Not Recognized | 0x05 | 0x01 Slot AIB _________________________________________ Check the TFTP server and the tftp configuration file to make sure the card being used is included. Contact Dialogic Technical Support.
- | 0x05 | Reserved |  |
- | 0x06 | Reserved |  |
Inform. | 0x07 | Card’s Configuration has been Reset to Defaults | 0x05 | 0x01 Slot AIB _________________________________________ One of the following occurred: Card has been reset by the host/switchkit. Card has reset/faulted due to software error. Card has reset due to a hardware problem. If running Switchkit, Switchmgr will take care of reconfiguring the card. If not using Switchkit the host has to reconfigure the card.
- | 0x08 | Reserved |  |
Major | 0x09 | Card Reset | 0x05 | 0x01 Slot AIB _________________________________________ Card has either faulted (software error) or was manually reset (either via software or via push button reset) The card should come back in service by itself.
| 0x0A | Connection Map Failure | 0x05 | 0x01 Slot AIB
Major | 0x0B | Software Does Not Have Download for Card | 0x05 | 0x01 Slot AIB _________________________________________ Software cannot be downloaded to the card. Check the TFTP server and the tftp configuration file to make sure the card being used is included. Contact Dialogic Technical Support.
Major | 0x0C | Card Does Not Support A-Law Encoding Format | 0x05 | 0x01 Slot AIB _________________________________________ Card does not support A-law encoding format. Check the card type and the card configuration.
Major | 0x0D | Card Revision Not Supported by System Software | 0x05 | 0x01 Slot AIB _________________________________________ Card revision not supported by system software revision. Replace the card with a different REV card. The REV can be found on the card itself and is made of a letter and a two digit number (for example, C12). The higher letter/number the newer the REV.
Major | 0x0E | Card Removed | 0x05 | 0x01 Slot AIB _________________________________________ Check with operations personnel to verify card removal.
Major | 0x0F | Hardware Failure Occurred on Slot Specified The CSP also sends a Card Status Report with a description of the failure | 0x05 | 0x01 Slot AIB _________________________________________ A hardware failure has been detected on a card. Reseat the card. If that does not work, replace card.
Minor | 0x10 | Ethernet Host Link Error Detected NOTE: To use the Host Link Failure Detection feature and receive this message, you must have polling enabled. | 0x00 |
Major | 0x11 | Card or Fan Tray Not Installed in Chassis | 0x05 | 0x01 Slot AIB _________________________________________ Check if fan tray and card are installed.
Major | 0x12 | EXNET Port A - Communication Failure | 0x08 | Data[0-4] Slot AIB Data[5] Logical Ring ID Data[6] Host Service State Data[7] EXNET Ring Error Status _________________________________________ Hardware failure on EXNET Port A. The Remote Node terminating to the local EXNET® Port A is not accessible (that is, the problem is not with local node but with the remote node). Verify EXNET Port A's terminating connection (remote node) is accessible. There could be a faulty fiber cabled connected to EXNET Port A. Check fiber connections are snug and connected properly. Bring the ring out of service then back in service. Reset Ring Interface card. If the lights on the Ring Interface card are still not all green, then collect the socket.log,alarm.log, and maintenance_llc_xxx.log and contact Dialogic Technical Support.
Minor | 0x13 | EXNET Port B - Communication Failure | 0x08 | Data[0-4] Slot AIB Data[5] Logical Ring ID Data[6] Host Service State Data[7] EXNET Ring Error Status _________________________________________ Hardware failure on EXNET Port B The Remote Node terminating to the local EXNET® Port B is not accessible (that is, the problem is not with local node but with the remote node). There could be a faulty fiber cabled connected to EXNET® Port B. Check fiber connections are snug and connected properly. Verify EXNET® Port B's terminating connection (remote node) is accessible. Bring the ring out of service then back in service. Reset Ring Interface card.
Minor | 0x14 | EXNET Port A - Fiber Laser Failure | 0x05 | 0x01 Slot AIB _________________________________________ Refer to the Hardware Installation and Maintenance Guide.
Minor | 0x15 | EXNET Port B - Fiber Laser Failure | 0x05 | 0x01 Slot AIB _________________________________________ The fiber driver on the Ring interface card has gone bad. Contact Dialogic Technical Support and replace the Ring Interface Controller card.
| 0x16 | Subrate Card Switchover |  | A switchover has occurred. No action required.
Inform. | 0x17 | Software Error (Please report this error to Dialogic Technical Support) | Variable | 0x01 Slot AIB Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x01) Data[3] Data Length (0x01) Data[4] Slot Number Data[5-44] Filename (in ASCII) Data[45,46] Line Number Data[47-n] Diagnostic Data _________________________________________ A software error occurred on a line card. The address information represents the slot containing the card. Gather information as to what was occurring on the system at the time of the error and report to Dialogic Technical Support.
Major | 0x18 | Remote SS7 card removed | 0x05 | 0x01 Slot AIB (if SS7 card in local node) 0x69 Slot Number (if SS7 card in remote node) _________________________________________ Check with operations personnel to verify card removal. Re-insert the working SS7 card and, Switch Manager will reconfigure this card. SwitchManager will trigger a Card Status Report (0x00A6) message and reconfigure the card per the configuration file that was used to start/configure the system.
Major | 0x19 | Bus Contention with Rear Card | 0x05 | 0x01 Slot AIB _________________________________________ The front card or I/O card are mismatched and incompatible with each other. Verify the I/O and card type and make sure they are supposed to be paired up.
Major | 0x1A | Bus Contention with Front Card | 0x05 | 0x01 Slot AIB _________________________________________ The front card or I/O card are mismatched and incompatible with each other. Verify the I/O and card type and make sure they are supposed to be paired up.
Major | 0x1B | Internal Diagnostic Failure | 0x08 | Data[0-4] Slot AIB Data[5] Logical Ring ID Data[6] Host Service State Data[7] EXNET Ring Error Status _________________________________________ An internal diagnostic error has been detected on an EXNET Ring card. Test the Ring Interface Card in a different slot. If the matrix continues to report this alarm to the host, replace the Ring Interface Card.
Major | 0x1C | EXNET card Looped Out of Ring | 0x08 | Data[0-4] Slot AIB Data[5] Logical Ring ID Data[6] Host Service State Data[7] EXNET Ring Error Status _________________________________________ Test the Ring Interface Card in a different slot. If the matrix continues to report this alarm to the host, replace the Ring Interface Card.
Major | 0x1D | Card Added to Virtual Slot | 0x05 | 0x01 Slot AIB _________________________________________ The host or Switchkit has configured a virtual card. Verify card type and that the card has been placed in the correct slot. If symptoms continue, contact Dialogic Technical Support for configuration guidance.
Major | 0x1E | Line Card Approaching Busy/ Line Card Approaching Busy Clear | Variable | SS7 card Data[0] Slot Number Data[1-n] Reason Codes: 0x00 Low Memory 0x01 Low MCB 0x02 Low Idle CPU Data[n+1] Stack ID 16-Span SLC Data[0] Slot Number Data[1-n] Reason Codes: 0x00 Low Memory 0x01 Low MCB 0x02 Low Idle CPU _________________________________________ Line card busy conditions exceeding the line card "Approaching Busy Threshold". Reduce the line card load by diverting traffic from the overloaded line card. Disable Debug if enabled on the line card.
Major | 0x1F | Line Card Busy Line Card Busy Clear | Variable | SS7 card Data[0] Stack ID Data[1] Slot Number Data[2-n] Reason Codes: 0x00 Low Memory 0x01 Low MCB 0x02 Low Idle CPU 16-Span SLC Data[0] Slot Number Data[1-n] Reason Codes: 0x00 Low Memory 0x01 Low MCB 0x02 Low Idle CPU _________________________________________ Caused by line card overload busy conditions. Reduce line card load by diverting traffic from the overloaded line card. Disable Debug if enabled on the line card.
| 0x20 | DS3 Card Limited Spans for SS7 | 0x05 | 0x01 Slot AIB _________________________________________ Look for other error messages that indicate a network or system condition leading to this problem. If symptoms persist contact Dialogic Technical Support.
| 0x21 | Too many DS3s Configured for Limited Spans | 0x05 | 0x01 Slot AIB _________________________________________ Ensure proper DS3 card DIP Switch positioning. Only one DS3 card can have DIP Switch 4 and 6 set to OFF "limited SS7 CIC traffic". The Standby DS3 card, must always have DIP switch 4 and 6 set to the ON position.
Major | 0x22 | Ethernet Link Failure | 0x06 | Data[0-4] Slot AIB (0x01) Data[5] I/O Card Ethernet Port Number This alarm is sent when an SS7 card loses its connection to a local host. _________________________________________ This alarm is sent if a VDAC-ONE I/O or Multi-Function Media I/O card port that was previously in a steady LINK_UP state loses its connection. The VDAC-ONE slot and failed I/O port (0-2 for the 3 I/O ports on the Multi-Function Media I/O card) is sent in the data portion of the Alarm message. The alarm is cleared when the link returns to a steady Link-Up state. This alarm is sent if any I/O ports lose their network connection, and will be cleared when the connection is re-established. Trace the network cable between the I/O card and the remote Ethernet switch. Replace the Ethernet cable or the connector if necessary.
Inform. | 0x39 | Ethernet Link-Up | 0x06 | Data[0-4] Slot AIB (0x01) Data[5] Ethernet Port Number (0x00-0x02) _________________________________________ This alarm is sent to the host the first time a link-up state is seen on the Multi-Function Media I/O card. Because there are three Ethernet ports on the Multi-Function Media I/O card, the host might see three of these alarms when the card comes into service. No action required.
Inform. | 0x3E | NFS Server Disconnect | 0x07 | Data[0-4] Slot AIB (0x01) Data[5, 6] Server ID ___________________________________________ The connection between the DSP2 card and the NFS server has broken down. Check the Ethernet network and all Ethernet connections. If the alarms persists, update the Generic Card Configuration message in the CSP configuration with a NFS Poll Retries (0x601) TLV. This TLV can change the default number of polls that can be missed before this alarm is sent.
Inform. | 0x40 | NFS Server Mounted Successfully | 0x07 | Data[0-4] Slot AIB (0x01) Data[5, 6] Server ID
Major | 0x41 | NFS Server Mounting Error | 0x09 | Data[0-4] Slot AIB (0x01) Data[5, 6] Server ID Data[7, 8] Error ID _________________________________________ 0x0001 - NFS Polling and Ping Failed 0x0002 - NFS Polling and Mount Failed 0x0003 - NFS Server Unreachable Diagnose the LAN connection between the DSP2 card and the NFS server.
Inform. | 0x42 | DSP Series 2 File Space Low | 0x0C | Data[0-4] Slot AIB (0x01) Data[5, 6] Number of Files Data[7, 8] Number of Free Blocks Data[9] TFTP (future) or NFS 0 TFTP (future) 1 NFS Data[10, 11] Threshold
Major | 0x43 | DSP Series 2 File Space Out of Memory | 0x0C | Data[0-4] Slot AIB (0x01) Data[5, 6] Number of Files in Cache Data[7, 8] Number of Free Blocks Needed Data[9] TFTP (future) or NFS 0 TFTP (future) 1 NFS Data[10, 11] Threshold
Minor | 0x44* | NFS Traffic Minor Threshold Alarm | 0x10 | Data[0-4] Slot AIB (0x01) Data[5] Alarm Type (See list below) 0 (0x00) Number of Reads 1 (0x01) Total Bytes Read 2 (0x02) Average Read Delay 3 (0x03) Maximum Read Delay 4 (0x04) Number of Writes 5 (0x05) Total Bytes Written 6 (0x06) Average Write Delay 7 (0x07) Maximum Write Delay 8 (0x08) Maximum Simultaneous Files Opened 9 (0x09) Average Simultaneous Files Opened 10 (0x0A) CPU Idle Time 11 (0x0B) VRA Process Delay 12 (0x0C) VRA IO Queue Delay Data[6-9] Value of Statistics (Units vary) Data[10] M Value (Hits in window) Data[11] N Value (Samples in window) (N>=M) Data[12-15] Threshold value (if this is a time value, it is in microseconds.) The M-value indicates number of times the threshold is exceeded in the sample window of size N. See the CSP D evelopers G uide Oveview, DSP2 Overload Management for more data.
Major | 0x45* | NFS Traffic Threshold Major Alarm | 0x10 | Data[0-4] Slot AIB (0x01) Data[5] Alarm Type (See list below.) 0 (0x00) Number of Reads 1 (0x01) Total Bytes Read 2 (0x02) Average Read Delay 3 (0x03) Maximum Read Delay 4 (0x04) Number of Writes 5 (0x05) Total Bytes Written 6 (0x06) Average Write Delay 7 (0x07) Maximum Write Delay 8 (0x08) Maximum Simultaneous Files Opened 9 (0x09) Average Simultaneous Files Opened 10 (0x0A) CPU Idle Time 11 (0x0B) VRA Process Delay 12 (0x0C) VRA IO Queue Delay Data[6-9] Value of Statistics (Units vary) Data[10] M Value (Hits in window) Data[11] N Value (Samples in window) (N>=M) Data[12-15] Threshold value (if this is a time value, it is in microseconds.) The M-value indicates number of times the threshold is exceeded in the sample window of size N. See CSP D evelopers G uide Overview, DSP2 Overload L ogic Overload Management for more data.
Major | 0x46 | DSP Series 2 TFTP Communications Error | 0x07 | Data[0-4] Slot AIB (0x01) Data[5, 6] Error ID
Major | 0x47 | NFS Read Error | 0x0F | Data[0-4] Slot AIB (0x01) Data[5, 6] Server ID Data[7-10] File ID Data[11-14] Bytes written to server up to time of failure
Major | 0x48 | NFS Write Error | 0x0F | Data[0-4] Slot AIB (0x01) Data[5, 6] Server ID Data[7-10] File ID Data[11-14] Bytes written to server up to time of failure
Inform. | 0x49 | Vocabulary Index File Read | 0x0F | Data[0-4] Slot AIB (0x01) Data[5, 6] Server ID Data[7-10] Checksum Data[11-14] File ID (Last successfully loaded VIF line)
Inform. | 0x4A | NFS Server Unmounted | 0x07 | Data[0-4] Slot AIB (0x01) Data[5, 6] Server ID
Major | 0x4B | NFS Server Unmount Error | 0x07 | Data[0-4] Slot AIB (0x01) Data[5, 6] Server ID
Major | 0x4C | NFS Open File Error | 0x0B | Data[0-4] Slot AIB (0x01) Data[5] Server ID (MSB) Data[6] Server ID (LSB) Data[7] File ID (MSB) Data[8] File ID . . . Data[9] File ID . . . Data[10] File ID (LSB)
Major | 0x4D | File Queue Failed | 0x0D | Data [0-4] Slot AIB Data[5] Parent Conference ID MSB Data[6] Parent Conference ID LSB Data[7] Child Conference ID MSB Data[8] Child Conference ID LSB Data[9] File ID (MSB) Data[10] File ID … Data[11] File ID … Data[12] File ID (LSB) ________________________________________ In the case of a parent conference, the Child Conference ID bits (Data[7-8]) shall be 0xFFFF.
Inform. | 0x4E | Error reading a .wav file | 0x10 | Data [0-4] Slot AIB Data [5-6] Server ID Data [7-10] File ID Data [11] Alarm Subtype (see below) Data [12-15] Value (Incorrect value found in file, see below) Subtype - Value (0xnnnnnnnn) 0x00 - No RIFF Chunk Found - Name of first chunk 0x01 - RIFF type .wav not found - RIFF type found 0x02 - No Format subchunk found - N/A (0x00000000) 0x03 - Invalid number of channels - Number of channels 0x04 - Invalid number of samples per second - Number of samples per second 0x05 - Invalid number of bits per second - Number of bits per second 0x06 - Unsupported encoding format - Encoding Format 0x07 - Data subchunk not found - N/A (0x00000000)
Major | 0x4F | Ethernet Switchover Occurred |  | Data [0-4] Slot AIB Data [5] Bit mask Bit 0 Interface B link state: 0=Down. 1=Up Bit 1 Interface A link state: 0=Down. 1=Up Bit 2 The active Ethernet Interface: 0=Interface A 1= Interface B ________________________________________ Diagnose the LAN connection between the DSP2 card and the NFS server.
Inform. | 0x4F | Ethernet Switchover Occurred (DSP Series 2 card) | 0x06 | Data [0-4] Slot AIB Data [5] Active Port: 01, 02, or 03 Port Interface 01 NET1 02 NET2 03 NET3
Major | 0x50 | DSP Ethernet Unavailable | 0x09 | Data [0-4] Slot AIB Data [5-8] Ethernet address of the DSP Series 2 Card. If at any point the RCOMM link fails, this alarm is sent to the host.
Major | 0x52 | ISDN Ethernet Unavailable | 0x09 | Data [0-4] Slot AIB Data [5-8] Ethernet address of the ISDN Series 3 Card. If at any point the RCOMM link fails, this alarm is sent to the host.
Inform. | 0x58 | Bad message received from local host | 0x06 | 0x01 Slot AIB Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x01) Data[3] Data Length (0x01) Data[4] Slot Number Data[5] Error Reason 0x00 Unknown cause of error message 0x01 Frame symbol (0xFE) caused error message 0x02 Escape symbol (0xFD) error 0x03 Message has zero length 0x04 Message has bad checksum 0x05 Message has bad length
Minor | 0x59 | Vocabulary Index File Read Incomplete | 0x13 | Data[0-4] Slot AIB (0x01) Data[5, 6] Server ID Data[7-10] Checksum Data[11-14] File ID (Last successfully loaded VIF line) Data[15-18] VIF bytes loaded into memory successfully
Inform. | 0x5A | Vocabulary Index File Potential Delay | 0x0B | Data[0-4] Slot AIB (0x01) Data[5, 6] Server ID
Minor | 0x5B | Fault Log Upload to NFS Succeed | 0x07 | Data[0-4] Slot AIB Data[5, 6] Server ID
Inform | 0x5C | Fault Log Upload to NFS Failed | 0x07 | Data[0-4] Slot AIB (0x01) Data[5, 6] Server ID
Major | 0x5D | HDLC Frame Dropped | 0x06 | Data[0-4] Slot AIB (0x01) Data[5] Sequence Number Mismatch

*Followed by an Alarm Cleared message

0x03 Span Alarms

Severity | Alarm (Number/Name) | Data Length | Data/Troubleshooting
Major | 0x01 | Carrier Group Alarm (CGA) or Span Dead (Please refer to the Span Filter Configure message) | 0x07 | 0x0C Logical Span AIB Span Status (a bit mask that indicates what is being sent and received on the span): Bit 0 0x01 Receiving Red Bit 1 0x02 Receiving Remote Alarm Indication/Yellow Bit 2 0x04 Receiving Loss of Signal Bit 3 0x08 Receiving Out of Frame Bit 4 0x10 Sending Red (AIS) Bit 5 0x20 Sending Remote Alarm Indication/Yellow Bit 6 0x40 Receiving AIS Bit 7 0x80 Receiving constant E-bit with Remote Alarm Indication (valid for E1 with insert CRC and Euro-ISDN) ____________________________________________________ This alarm is generated when the CSP detects a carrier group alarm for more than the configured time period. Either you lost a clock source or someone pulled the patch cord and broke the physical connection to the TDM (Time Division Multiplexed) network. Request operational personnel find out why the physical connection has been compromised between the CSP to the telecom network. Also look at the way the span has been configured - it must be the same on both ends. See the T1 Span Configure, E1 Span Configure or J1 Span Configure messages for different configuration parameters.
| 0x02 | Reserved |  |
Major | 0x03 | Excessive Burst of Slips | 0x08 | 0x0C Logical Span AIB Slot Number Span Offset ____________________________________________________ This notification occurs when the CSP detects an abnormally high number of slips. The address information represents the logical span of the span. There might be noisy T1 signals on the line, a configuration mismatch that is, B8Zs/AMI/SF/ESF etc. for T1, HDB3, CRC-4 etc for E1 spans or a bad timing source for span synchronization. Use the Span Status Query message (0x0084) which will return all Layer 1 parameters. See the API Reference for more details. Also, you can check your timing source. Most of the time the CSP uses a Span from the network to Time the entire CSP chassis. If that source is not good, it may trigger slips and carrier Group Alarms (CGA) on other spans.
Major | 0x04 | J1-Specific Failure | 0x06 | 0x0C Logical Span AIB
Major | 0x05 | Logical Span ID already exists on another node | 0x06 | 0x0C Logical Span AIB ____________________________________________________ An application is trying to configure a Logical Span ID that already exists on another node. There could be a software error in SwitchMgr or an error in the configuration file. Check the configuration. Collect the alarm.log and socket.log and contact Dialogic Technical Support.
Inform. | 0x0F | CGA Filter set to 0xFFFF | 0x06 | 0x0C Logical Span AIB

*Followed by an Alarm Cleared message

0x04 Channel Alarms

Severity | Alarm (Number/Name) | Data Length | Data/Troubleshooting
- | 0x01 | Reserved |  |
Inform. | 0x02 | ISDN D Channel Establishing (the distant end is not communicating on the D Channel) | 0x07 | 0x0D Channel AIB __________________________________ ISDN D channel is trying to get established and the distant end is not communicating on the D channel. Initial configuration or the distant end has stopped communicating on the D channel. Investigate the distant end D channel.
Inform. | 0x03 | PPL Error Data | Variable | Refer to the PPL Error Data at the end of this message for the data format.
| 0x04 | Switchover Initiate |  | Check D Channel Out of Service condition. The Primary D channel has gone from being in-service to out-of-service. The address information represents the slot and channel of the D channel. Look for Card or Span alarms that would also indicate a hardware failure. Reset the D Channel if is does not come back inservice contact remote end network administrator to check remote end status.
| 0x05 | Switchover Success |  | The D channel switchover was successful. The new D channel is now the controller. The address information represents the span and channel of the new D channel. Investigate the cause of the switchover.
| 0x06 | Switchover Failure |  | The controller switchover failed. The existing D channel is still the controlling D channel. The address information represents the span and channel of the new D channel. Investigate cause of switchover and state of the Backup D Channel.
| 0x07 | Backup Diagnostic |  | Information Alarm when the state of the D channel changes. The address information represents the span and channel of the D channel. Investigate the cause of D Channel switchover.
| 0x08 | SS IPDC Error |  | Look for other error messages that would indicate a network or system condition leading to this problem. If symptoms persist, contact Dialogic Technical Support.
Major | 0x09 | Invalid Associated Channel | 0x09 | The Device Server ID and 0x0D Channel AIB.
Major | 0x0A | DSP Resource Wait Timeout | 0x09 | The Device Server ID and 0x0D Channel AIB. __________________________________ A DSP Resource Wait timeout occurs when the CSP gets no response when requesting a physical channel. Could be a hardware failure. If the problem persists, contact Dialogic Technical Support
Major | 0x0E | EXNET Connection Error |  | Contact Dialogic Technical Support.
Inform. | 0x11 | DSP Service Cancel Timeout Severity | 0x09 | Data[0-6] 0x0D Channel [7-8] L4 CH State
Major | 0x12 | No H.245 response has been received for the socket open request | 0x09 | Data[0-1] State Data[2-8] 0x0D Channel

*Followed by an Alarm Cleared message

0x05 DSP SIMM Alarms

Severity | Alarm (Number/Name) | Data Length | Data/Troubleshooting
Inform. | 0x01 | DSP SIMM Taken Out of Service | 0x06 | 0x12 DSP SIMM AIB. _______________________________ Check with operations personnel to verify card removal. Verify the host did not send a Service State Configure (0x000A) message to take the SIMM out of service. Also verify that the DSP card is still installed and powered on.
- | 0x02 | Reserved | 0x00 | No Data
Inform. | 0x03 | Recorded Announcement Erase Complete | 0x00 | No Data Sent upon completion of erasure. When you have erased a VRA SIMM using Recorded Announcement (0x0054), this alarm indicates that the erasure is complete. The host must wait for this alarm before it begins any download.
Major | 0x04 | Recorded Announcement Download Inconsistency | 0x00 | No Data Sent upon completion of download. This alarm indicates an inconsistency between the information in a Recorded Announcement Download 0x0052 message and the actual announcement in the Recorded Announcement Download 0x0053 message. The inconsistency is usually caused by an incorrect checksum or announcement size. The announcement information is stored as it appears in the Recorded Announcement Download 0x0053 message. Play out the announcement to check it. Could be caused by an incorrect checksum or announcement size. Check the announcement and delete one of the announcements.
Major | 0x05 | Recorded Announcement ID Inconsistency (on same card) | 0x00 | No Data Sent when a VRA SIMM is brought in service. This alarm indicates that an announcement uses the same ID as another announcement, with different information, on the DSP card. Both announcements have the same ID, and either announcement might be played when the ID is specified in the Recorded Announcement Connect 0x0055 message. Indicates that the host downloaded an announcement using the same ID as another announcement, with different information on the DSP card. Check the configuration to ensure that you are not using the same ID for different RAN files.
Inform. | 0x06 | Recorded Announcement Download Ready | 0x08 | An AIB indicating the slot number: Data[0] Address Method (0x00) Data[1] No. of Address Elements (0x01) Data[2] Address Type (0x12) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] SIMM Number Data[6, 7] RAN ID _______________________________ Sent upon completion of download. The DSP-ONE card will not accept another Recorded Announcement Download Initiate message until it has sent this alarm.
Inform | 0x07 | Recorded Announcement File System Conversion Success | 0x06 | Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x12) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] SIMM Number _______________________________ Sent after the flash memory file system is converted. Informs the host that the RANs are now stored in the requested file system. This alarm takes three to five minutes to be generated after the host sends the file system conversion request. After this alarm you are able to bring the VRAS simm into service.
Major | 0x08 | Recorded Announcement File System Conversion Failure | 0x07 | Data Length: (0x07) Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x12) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] SIMM Number Data[6]: Failure Code _______________________________ Failure codes: VRA_FAILURE = 0, Amount of Flash Data invalid for New File System. VRA_FLASH_WRITE_FAILURE = 2, Writing to Flash failed. VRA_FLASH_ERASE_FAILURE = 3, Erasing Flash failed. VRA_RAM_WRITE_FAILURE = 4, Writing RAM failed. VRA_DATA_VALIDATION_FAILURE = 5 CRC validation failed. Sent after an unsuccessful attempt to convert the file system. Informs the host that the file system conversion process failed. You should delete the RANs on this VRA SIMM. If the file system convert fails then delete all RANs from this SIMM and try again.
Major | 0x09 | Recorded Announcement File System Timeout | 0x06 | Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x12) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] SIMM Number _______________________________ Sent after an attempt to convert the file system times out, if the attempted deletion of entire flash memory, file system conversion, or defragmentation fails to complete in the time allowed. Try deleting each RAN from the SIMM.
Inform | 0x0B | Recorded Announcement Defragmentation Success | 0x06 | Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x12) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] SIMM Number _______________________________ Sent after defragmentation of the flash memory is complete. Informs the host that the RANs now take up as little flash memory as possible. This alarm takes three to five minutes to be generated after the host sends the file system Defragment request.
Major | 0x0C | Recorded Announcement Defragmentation Failure | 0x07 | Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x12) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] SIMM Number Data[6] Failure Code (see failure codes listed under Alarm File System Conversion Failure 0x08) _______________________________ Sent after an unsuccessful attempt to defragment flash memory. Informs the host that the flash memory defragmentation has failed. The host should delete the flash memory on this VRA SIMM.
Inform | 0x0D | Recorded Announcement Single Deletion Complete | 0x08 | Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x12) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] SIMM Number Data[6] RAN ID (MSB) Data[7] RAN ID (LSB) _______________________________ Sent in response to the message, Recorded Announcement Single Delete. Informs the host that the RAN ID has been marked for deletion and is no longer available for use. This alarm takes zero to 30 seconds to be generated after the host sends the delete request.
Inform | 0x0E | Recorded Announcement Need Defragmentation | 0x07 | Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x12) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] SIMM Number Data[6] Defragmentation Level _______________________________ Sent after a Recorded Announcement Single Delete has been processed and the flash memory where the RANs are stored has reached the highest level of fragmentation. Indicates that enough of the flash memory is occupied by deleted RANs to make it worthwhile to defragment the flash memory.
Major | 0x0F | Recorded Announcement Query Timeout | 0x06 | Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x12) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] SIMM Number _______________________________ Sent if the DSP fails to send the information of all the recorded announcements stored when queried. Occurs when a SIMM/Card is brought In Service. The time taken for this alarm to be generated depends upon the number of recorded announcements stored. For each RAN the timeout is set to 200 msec. Reconfigure the SIMM or reset the card.

*Followed by an Alarm Cleared message

0x06 DSP Alarms

Severity | Alarm (Number/Name) | Data Length | Data/Troubleshooting
Major | 0x01 | DSP Out of Service | 0x03 | Data[0] Slot Number Data[1] Module Number (0-1) Data[2] Chip Number (0-3) _______________________________ Either the user took the DSP chip out of service using a service state configuration message addressing the chip or the DSP mother card took the DSP chip out of service due to lose of polls from the DSP mother card. If SwitchMgr does not bring the DSP chip back into service using the service state configuration message addressing the DSP chip, then collect the alarm.log and socket.log and call Dialogic Technical Support.
Inform. | 0x02* | Resources Exceed Limit | 0x07 | Data[0] Function Type Data[1] Alarm Threshold Data[2] Alarm Cleared Threshold Data[3, 4] Number of Channels Used Data[5, 6] Number of Channels Configured for Function Type
Major | 0x03 | DSP Playback Underrun | 0x08 | Data[0] Slot Number Data[1] Module Number (0-1) Data[2] Chip Number (0-3) Data[3] TFTP (future) or NFS Data[4,5] Total temporary storage Blocks Data[6,7] Number of Blocks in use by DSP
Major | 0x04 | DSP Record Overrun | 0x07 | Data[0] Slot Number Data[1] Module Number (0-1) Data[2] Chip Number (0-3) Data[3-6] File ID
Major | 0x05 | DSP Temporary Storage Minor Alarm | 0x0D | Data[0] Slot Number Data[1] Module Number (0-1) Data[2] Chip Number (0-3) Data[3-6] File ID Data[7,8] Total Number of Blocks Data[9,10] Number of Blocks on DSP Data[11,12] Threshold
Major | 0x06 | DSP Temporary Storage Full | 0x0D | Data[0] Slot Number Data[1] Module Number (0-1) Data[2] Chip Number (0-3) Data[3-6] File ID Data[7,8] Requested Number of Blocks Data[9,10] Number of used Blocks on DSP Data[11,12] Number of free Blocks on DSP
Inform. | 0x07* | DSP Points Exceed Limit | 0x0A | Data[0] Alarm Threshold Data[1] Alarm Clear Threshold Data[2-5] Resource Points in use Data[6-9] Resource Points Configured
Major | 0x08* | DSP Chip Reset | 0x03 | Data[0] Slot Data[1] Module Number Data[2] Chip Number
Major | 0x09 | DSP Conference Control Failure | 0x0D | Data[0] Slot Data[1-4] Conference Handle Data[5-8] Conference Actions Data[9-12] Timeslot Conference Control Actions 0x00 - Create Conference 0x01 - Teardown Conference 0x02 - Add Leg 0x03 - Remove Leg 0x04 - Set Output Gain 0x05 - Set Input Gain 0x06 - Echo Suppression On 0x07 - Echo Suppression Off 0x08 - Noisegate On 0x09 - Noisegate Off 0x0A - Set Noise Time Constant 0x0B - Set Noise Margin 0x0C - Set Maximum Noise 0x0D - Set Maximum Hybrid Loss 0x0E - Set AGC Target Level 0x0F - Set AGC Time Constant 0x10 - AGC On 0x11 - AGC Off 0x12 - Set Broadcastgain 0x13 - Set Aux Input Gain

*Followed by an Alarm Cleared message

0x07 Node Alarms

Severity | Alarm (Number/Name) | Data Length | Data/Troubleshooting
Minor | 0x01 | Not Using Extended API | 0x06 | Data[0] Physical Node ID, MSB Data[1] Physical Node ID Data[2] Physical Node ID Data[3] Physical Node ID, LSB Data[4] Logical Node ID Data[5] Host Node ID
Inform. | 0x02 | Available Conferencing Timeslot Changed | 0x02 | Data[0] New Timeslot Count, MSB Data[1] New Timeslot Count, LSB
Inform. | 0x05 | Unable to Communicate with Node |  | Normally when this alarm is sent to the host, it includes the filename and line number where the error occurred. Send this information to Dialogic Technical Support.
Major | 0x06 | Remote SS7 Server Node Unavailable |  | Data[0] Node ID Data[1] Board Slot Number _____________________________ Check with network operations for other network alarms that could be related.
| 0x07 | 0x07 Remote SS7 CIC Matrix Node Unavailable |  | Check with network operations for other network alarms that could be related.
Major | 0x08 | Remote SS7 Card Unavailable |  | Data[0] Number of IDs (always 1) Data[1] 1=Active SS7 Card 2=Standby SS7 Card _____________________________ Ensure that the Ethernet cable is plugged in CCS I/O Ethernet Port A. Check for faulty hardware, (SS7PQ, SS7HP, CCS I/O, ethernet cable, and Ethernet switch). Check with network operations for other network alarms that could be related.
Major | 0x0A | Maximum Node Count Reached |  |
Major | 0x0B | H.100 Bus Failure |  | This alarm occurs if the H.100 bus fails. For example, if there are no clock signals to drive the H.100 bus.
Major | 0x0C | Clock B Failure |  | This alarm occurs if the clock B signal of the H.100 bus fails. This alarm notifies the host about the clock signal failure, so that the host can appoint another board to source the clock or take other actions.
Major | 0x0D | Clock A Failure |  | This alarm occurs if the clock A signal of the H.100 bus fails. This alarm notifies the host about the clock signal failure, so that the host can appoint another board to source the clock or take other actions.
Major | 0x0E | Cannot Be Primary A |  | This alarm occurs when the board could not become the primary master driving clock A, when instructed to do so. This alarm is sent to the host to enable it to appoint another board as primary master driving clock A or take other actions.
Major | 0x0F | Cannot Be Primary B |  | This alarm occurs when the board could not become the primary master driving clock B, when instructed to do so. This alarm is sent to the host to enable it to appoint another board as primary master driving clock B or take other actions.
Major | 0x10 | Cannot Be Secondary A |  | This alarm occurs when the board could not become the secondary master driving clock A, when instructed to do so. This alarm is sent to the host to enable it to appoint another board as secondary master driving clock A or take other actions.
Major | 0x11 | Cannot Be Secondary B |  | This alarm occurs when the board could not become the secondary master driving clock B, when instructed to do so. This alarm is sent to the host to enable it to appoint another board as secondary master driving clock B or take other actions.
Major | 0x12 | Momentary Failure of Clock A |  | This alarm occurs when a momentary failure of clock A is observed and clock A recovers.
Major | 0x13 | Momentary Failure of Clock B |  | This alarm occurs when a momentary failure of clock B is observed and clock B recovers.
Major | 0x14 | Taking Over As Primary A |  | This alarm occurs when the board is acting as the secondary master, driving clock A and the primary master, driving clock B fails. Since the primary master, driving clock B has failed, the secondary master driving clock A takes over as the primary master, driving clock A. The board is taking over as the primary master driving clock A.
Major | 0x15 | Taking Over As Primary B |  | This alarm occurs when the board is acting as the secondary master, driving clock B and the primary master, driving clock A fails. Since the primary master, driving clock A has failed, the secondary master driving clock B takes over as the primary master, driving clock B. The board is taking over as the primary master driving clock B.

*Followed by an Alarm Cleared message

0x08 DS3 Alarms

Severity | Alarm (Number/Name) | Data Length | Data/Troubleshooting
Major | 0x01 | DS3 Alarm | 0x07 | Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x32) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] DS3 Offset Data[6] Alarm (a bit mask that indicates what is being sent and received on the DS3): Bit 0 0x01 Receiving Red Bit 1 0x02 Receiving Remote Alarm Ind. / Yellow Bit 2 0x04 Receiving Loss of Signal Bit 3 0x08 Receiving Out of Frame Bit 4 0x10 Receiving AIS Bit 5 0x20 Sending AIS Bit 6 0x40 Sending Remote Alarm Ind. / Yellow Bit 7 Reserved _______________________________________________ Check for clock reference alarms that could be associated with this failure.
Inform. | 0x02 | Far End Alarm and Control (FEAC) | 0x01 If Severity is Informative 0x07 | Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x32) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] DS3 Offset Data[6] Alarm 0x00 Activate Span Offset 0 in Loopback Mode 0x01 Activate Span Offset 1 in Loopback Mode 0x02 Activate Span Offset 2 in Loopback Mode 0x03 Activate Span Offset 3 in Loopback Mode 0x04 Activate Span Offset 4 in Loopback Mode 0x05 Activate Span Offset 5 in Loopback Mode 0x06 Activate Span Offset 6 in Loopback Mode 0x07 Activate Span Offset 7 in Loopback Mode 0x08 Activate Span Offset 8 in Loopback Mode 0x09 Activate Span Offset 9 in Loopback Mode 0x0A Activate Span Offset 10 in Loopback Mode 0x0B Activate Span Offset 11 in Loopback Mode 0x0C Activate Span Offset 12 in Loopback Mode 0x0D Activate Span Offset 13 in Loopback Mode 0x0E Activate Span Offset 14 in Loopback Mode 0x0F Activate Span Offset 15 in Loopback Mode 0x10 Activate Span Offset 16 in Loopback Mode 0x11 Activate Span Offset 17 in Loopback Mode 0x12 Activate Span Offset 18 in Loopback Mode 0x13 Activate Span Offset 19 in Loopback Mode 0x14 Activate Span Offset 20 in Loopback Mode 0x15 Activate Span Offset 21 in Loopback Mode 0x16 Activate Span Offset 22 in Loopback Mode 0x17 Activate Span Offset 23 in Loopback Mode 0x18 Activate Span Offset 24 in Loopback Mode 0x19 Activate Span Offset 25 in Loopback Mode 0x1A Activate Span Offset 26 in Loopback Mode 0x1B Activate Span Offset 27 in Loopback Mode 0x1C Activate All Span Offsets in Loopback Mode 0x1D Activate DS3 in Loopback Mode
|  |  |  | 0x20 Deactivate Span Offset 0 in Loopback Mode 0x21 Deactivate Span Offset 1 in Loopback Mode 0x22 Deactivate Span Offset 2 in Loopback Mode 0x23 Deactivate Span Offset 3 in Loopback Mode 0x24 Deactivate Span Offset 4 in Loopback Mode 0x25 Deactivate Span Offset 5 in Loopback Mode 0x26 Deactivate Span Offset 6 in Loopback Mode 0x27 Deactivate Span Offset 7 in Loopback Mode 0x28 Deactivate Span Offset 8 in Loopback Mode 0x29 Deactivate Span Offset 9 in Loopback Mode 0x2A Deactivate Span Offset 10 in Loopback Mode 0x2B Deactivate Span Offset 11 in Loopback Mode 0x2C Deactivate Span Offset 12 in Loopback Mode 0x2D Deactivate Span Offset 13 in Loopback Mode 0x2E Deactivate Span Offset 14 in Loopback Mode 0x2F Deactivate Span Offset 15 in Loopback Mode 0x30 Deactivate Span Offset 16 in Loopback Mode 0x31 Deactivate Span Offset 17 in Loopback Mode 0x32 Deactivate Span Offset 18 in Loopback Mode 0x33 Deactivate Span Offset 19 in Loopback Mode 0x34 Deactivate Span Offset 20 in Loopback Mode 0x35 Deactivate Span Offset 21 in Loopback Mode 0x36 Deactivate Span Offset 22 in Loopback Mode 0x37 Deactivate Span Offset 23 in Loopback Mode 0x38 Deactivate Span Offset 24 in Loopback Mode 0x39 Deactivate Span Offset 25 in Loopback Mode 0x3A Deactivate Span Offset 26 in Loopback Mode 0x3B Deactivate Span Offset 27 in Loopback Mode 0x3C Deactivate All Span Offsets in Loopback Mode 0x3D Deactivate DS3 in Loopback Mode _______________________________________________ If a major alarm is indicated, check network operations for far-end CGA or other facility alarms. If the severity is informative, you can enable loopback mode or ignore. If the severity is major, sync with the carrier and verify Layer 1 integrity
Major | 0x02 | Far End Alarm and Control (FEAC) | 0x03 If Severity is Major 0x07 | Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x32) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] DS3 Offset Data[6] Alarm 0x01 DS3 Equipment Failure (Affecting Service) 0x02 DS3 Loss of Signal 0x03 DS3 Out of Frame 0x04 DS3 AIS 0x05 DS3 Idle 0x06 DS3 Equipment Failure (Not Affecting Service) 0x07 Common Equipment Failure 0x08 DS1 Multiple Loss of Signal 0x09 DS1 Equipment Failure (Affecting Service) 0x0A DS1 Single Loss of Service 0x0B DS1 Equipment Failure (Not Affecting Service)
Major | 0x03* | DS3 Application Mismatch | 0x07 | Alarm is send when the received DS3 Application bit does not match the configured DS3 framer mode. Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x32) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] DS3 Offset Data[6] Application ID bit received 0x00 - M13 0x01 - C-Bit

*Followed by an Alarm Cleared message

0x09 VoIP Module Alarms

Severity | Alarm (Number/Name) | Data Length | Data/Troubleshooting
Major | 0x00 | Module In Service | 0x06 | See 0x42 VoIP Module A VDAC-ONE or IPN2 module has come in service. The address information represents the slot and VDAC module ID. ___________________________________ No action required.
Major | 0x01 | Module Out of Service | 0x06 | See 0x42 VoIP Module ___________________________________ The VDAC or IPN2 module is out-of-service. The address information represents the slot and VDAC-ONE or IPN2 module ID. Verify the module is no longer needed for the operation.
Major | 0x02 | Module Dead | 0x06 | See 0x42 VoIP Module ___________________________________ The VDAC-ONE or IPN-2 module is no longer communicating. The address information represents the slot and VDAC-ONE/IPN-2 module ID. Review Field Bulletin O-4083 at www.cantata.com/support If problem persists, contact Dialogic Technical Support
Major | 0x03 | DSP Dead | 0x07 | Data[0] Address Method Data[1] Number of Address Elements Data[2] Address Type (0x42) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] Module Number Data[6] DSP Number 0x00-0x07 ___________________________________ The DSP on VDAC-ONE or IPN-2 card is no longer communicating. The address information represents the slot and VDAC/IPN2 module ID. Check the IP network for the source of the error. If the problem persists, contact Dialogic Technical Support.
Major | 0x04 | Module Reset | 0x06 | See 0x42 VoIP Module Check with the operations personnel to verify board reset.
Major | 0x05 | Module Resetting | 0x06 | See 0x42 VoIP Module ___________________________________ A VDAC-ONE or IPN2 module is currently resetting. The address information represents the slot and VDAC-ONE or IPN2 module ID. Software fault could have occurred or the VoIP card or the module is being reset by the host. If the host did not issue the reset request, then perform the Fault Log Query for the VoIP module indicated in the message and contact Dialogic Technical Support.
Major | 0x06 | DSP Reset | 0x07 | Data[0] Address Method Data[1] Number of Address Elements Data[2] Address Type (0x42) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] Module Number Data[6] DSP Number 0x00-0x07 ___________________________________ This alarm is sent to the host upon reset of a DSP Resource on a VDAC-ONE card’s VoIP Module or IPN-2 card’s VoIP Module. Too many fatal errors are detected on this DSP module. Check the IP network for the source of the error. If the problem persists, contact Dialogic Technical Support.
Major | 0x07 | VMOD Inaccessible | 0x06 | Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x42) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] Module Number ___________________________________ This alarm is sent to the host when a module becomes inaccessible from the motherboard. See also 0x42 VoIP Module
Major | 0x08 | Fatal Calisto Error | 0x07 | Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x42) Data[3] Data Length (0x02) Data[4] Module Number Data[5] Calisto Number _____________________________________ This alarm results from the host sending the Media Recovery Method TLV (0x01F4) in the Resources Attribute Configure (0x00E3) message.
Inf. | 0x09 | Media Recovery Procedure Started |  | Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x42) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] Module Number Datat[6] Calisto Number - set to 0xFF in case of Immedidate forced bleed-off. _____________________________________ This alarm results from the host sending the Media Recovery Method TLV (0x01F4) in the Resources Attribute Configure (0x00E3) message.
Inf. | 0x17 | Software Error | Variable | See 0x42 VoIP Module Data[0] Address Method (0x00) Data[1] Number of Address Elements (0x01) Data[2] Address Type (0x42) Data[3] Data Length (0x02) Data[4] Slot Number Data[5] Module Number Data[6-45] Filename (in ASCII) Data[46,47] Line Number Data[48-n] Diagnostic Data

*Followed by an Alarm Cleared message

0x1E TFTP Alarm NOTE: This alarm is resent every 20 seconds as long as the alarm condition remains Length Variable Data[0] Alarm Code 0x00 Cannot TFTP file 0x01 Invalid TFTP Configuration File Format 0x02 Invalid BRecord Format 0x03 RAM Corrupted 0x04 Old Timestamp 0x05 No timestamp supplied Data[1] Type 0x02 Alarm Status (See Data[2], below) All other types: Dialogic U se Only. Report to Dialogic T echnical Support. Data[2] Status Applies to Alarm Type 0x02 (Alarm Status) only. 0x00 No Status 0x01 TFTP device detected a protocol error (such as a non-Data packet received or expected ACK not received. Occurs when a file is not found). 0x02 TFTP device timed out (Incorrect IP Address) 0x03 TFTP device is out of sync 0x04 TFTP device has no more free socket IDs (Occurs when another TFTP Download was in progress but was aborted) 0x05 TFTP device cannot use a channel number given to it 0x06 TFTP device has not been initialized 0x07 No server IP Address has been given 0x08 No TFTP Configuration filename has been given 0x0 9 No timestamp has been given 0x0A A TFTP Configuration or BRecord File line is too long 0x0B Too much data for internal buffer 0x0C TFTP Configuration File line has no '=' 0x0D TFTP Configuration File line has no second '=' 0x0E TFTP Configuration File timestamp is missing a parameter 0x0F Load filename is greater than 127 characters 0x10 EX/CPU Label in TFTP Configuration file not set to SAVE_LOAD_TRUE 0x11 Not enough RAM on EX/CPU card to save all loads that are configured to be saved 0x12 BRecord File is out of sync. There is no 'B' starting the record. 0x13 BRecord receiver is out of sync. Expected a different record type. 0x14 Invalid BRecord Checksum 0x15 Invalid BRecord Count 0x16 Incorrect Number of Bytes in BRecord Load
0x17 Invalid Load Checksum 0x18 Incorrect Load for Card 0x19 Load is from a different software version than the version on the EX/CPU 0x1A Timeout waiting for response from internal download process 0x1B Host download is in progress 0x1C TFTP Download aborted by initiation of host download 0x1D Timeout waiting for buffer 0x1E Stopped by host starting another TFTP 0x1F Configuration file has a new save option for an existing load 0x20 Operating system general error 0x21 Operating system I/O error Data[3] Load Number 0x00 ST1LC 0x01 EX/CPU 0x02 MFDSP 0x03 Reserved 0x04 SE1LC 0x05 SJ1LC 0x06 SS7 0x07 ISDN PRI, DASS2/DPNSS 0x09 DSP-ONE 0x0B T-ONE, E-ONE 0xFF No Load
Data[4] Error Information 0x00 No Error 0x01 Battery-backed configuration validation 0x02 System data validation 0x03 Input parameter validation 0x04 TFTP device initialization 0x05 TFTP device open 0x06 TFTP device read 0x07 TFTP device control 0x08 Loading Configuration File 0x09 Validating Configuration File 0x0A Loading Load Information 0x0B Validating Load Information 0x0C Sending "Begin" to download the state machine 0x0D Sending BRecord to download the state machine 0x0E Verifying TFTP completion 0x0F Sending "Complete" to download the state machine 0x10 Sending data buffer to line card 0x11 Verifying data for line card completion 0x21 Host Connection Dropped (Major) (Indicates that a connection to a host has been dropped)

PPL Error Data

The data format for this alarm depends on the PPL component

E1/T1 Components:

Length 0x 14

Data[0] Component ID, MSB

Data[1] Component ID, LSB

Data[2] Logical Span ID

Data[3] Channel

Data[4-10] The Channel AIB

Data[4] Address Method (0x00)

Data[5] Number of Address Elements (0x01)

Data[6] Address Type (0x0D)

Data[7] Data Length (0x03)

Data[8] Logical Span ID, MSB

Data[9] Logical Span ID, LSB

Data[10] Channel

Data[11] PPL Protocol ID

Data[12] Blocked

Data[13] PPL Event, MSB

Data[12] PPL Event, LSB

Data[14] Initial State

Data[15] Next State

Data[16] Timestamp, MSB

Data[17] Timestamp, LSB

Data[18] Error Status, MSB

Data[19] Error Status, LSB

See "PPL Audit Query 0xDD" for values of the various PPL bytes.

ISDN and DASS Components:

Length 0x 1A

Data[0] Component ID, MSB

Data[1] Component ID, LSB

Data[2] Logical Span ID

Data[3] Channel

Data[4-10] The Channel AIB

Data[4] Address Method (0x00)

Data[5] Number of Address Elements (0x01)

Data[6] Address Type (0x0D)

Data[7] Data Length (0x03)

Data[8] Logical Span ID, MSB

Data[9] Logical Span ID, LSB

Data[10] Channel

Data[11] Subrate

Data[12] Call Reference, MSB

Data[13] Call Reference, LSB

Data[14] Reserved

Data[15] Reserved

Data[16] PPL Protocol ID

Data[17] Blocked

Data[18] PPL Event, MSB

Data[19] PPL Event, LSB

Data[20] Initial State

Data[21] Next State

Data[22] Timestamp, MSB

Data[23] Timestamp, LSB

Data[24] Error Status, MSB

Data[25] Error Status, LSB

See "PPL Audit Query 0xDD" for values of the various PPL bytes.

SS7 Components:

Length Variable

Data[0] Component ID, MSB

Data[1] Component ID, LSB

Data[2-n] See PPL Component Addressing for the AIB

Data[n] PPL Protocol ID

Data[n] Blocked

Data[n] PPL Event, MSB

Data[n] PPL Event, LSB

Data[n] Initial State

Data[n] Next State

Data[n] Timestamp, MSB

Data[n] Timestamp, LSB

Data[n] Error Status, MSB

Data[n] Error Status, LSB

VDAC-ONE and IP Network Interface Series 2 Component

Length Variable

Data[0] Component ID, MSB

Data[1] Component ID, LSB

Data[2-n] See PPL Component Addressing for the AIB

Data[n] PPL Protocol ID

Data[n] Blocked

Data[n] PPL Event, MSB

Data[n] PPL Event, LSB

Data[n] Initial State

Data[n] Next State

Data[n] Timestamp, MSB

Data[n] Timestamp, LSB

Data[n] Error Status, MSB

Data[n] Error Status, LSB

Data[n] External Initial State, MSB

Data[n] External Initial State, LSB

Data[n] External Next State, MSB

Data[n] External Next State, LSB

0x0B SIP Alarm

Severity | Alarm (Number/Name) | Data Length | Data/Troubleshooting
Inform. | 0x01 | Received destination unreachable ICMP error for the SIP message sent. | 0x16 | Data[0-6] Channel AIB (0x0D) Data[7] ICMP Type (0x03) - Destination Unreachable Data[8] ICMP Code - For example 0x03 - Port Unreachable. Refer to RFC 792. Data[9] Protocol of failed packet (0x11) UDP Data[10-13] Source address of failed packet - the CSP SIP IP Address Data[14-17] Destination address of failed packet Data[18-19] Source port of failed packet Data[20-21] Destination port of failed packet
Inform. | 0x02 | Received invalid response for the SIP message sent | 0x0A | Data[0-6] Channel AIB (0x0D) Data[7-8] Response Code Data[9] Error Code Error Codes: 0x00 Syntax Error 0x01 Transaction Not found 0x02 Invalid CSeq number 0x03 Tags mismatch 0x04 Invalid CSeq message type 0x05 Retransmitted response

A group of data bits in a specific format, with a flag at each end to indicate the beginning and the end of the frame.
Range of channels provided by T1 or E1 transmission service. A physical span is a group of channels taking up a single physical wire. A logical span is a group of channels taking up less than a single logical wire, or carried over more than one physical wire.
Digital Signal Processor
Voice over Internet Protocol. The delivery of voice information in digital form in discrete packets rather than in the traditional circuit-committed protocols of the public-switched telephone network (PSTN).
See Recorded Announcements.
See Address Information Block.
Setting up, monitoring, and tearing down calls.
Call processing layer of the CSP.
A digital communications link - voice, data, and video at a 2.048 Mbps rate; 30B/2D or 31B/1D (ISDN); non-North American version of T1.
See Programmable Protocol Language.
Protocol layer of the CSP.
See Signaling System Number Seven.
Message Transfer Part level 2 - data link level
Digital communications link - voice, data, and video at a 1.544 Mbps rate (24 64 Kbps channels)
Frequency Shift Keying
The protocol used in most local area PC networks. Typically, most Ethernet networks support data transmission speeds up to 10 Mbps, but 100 Mbps is also possible.
Most Significant Bit
Least Significant Bit
See Message Transfer Part.
See Integrated Services Digital Network User Part.
Destination Point Code
See Integrated Services Digital Network.
A number that addresses a node in a SS7 network.
The condition of a component at a given instant. The current "context" of a PPL object, such as Idle, Seizing, Answered. In PPL files, a State is represented by a circle.
A computer, attached to the Excel platform through an RS-232 or Ethernet link, from which you run the telecommunications application that controls the Excel platform.
Telephone User Part
Quick depress and release of the phone plunger of a handset to signal the PBX or Centrex of instructions to follow (e.g., Call Transfer).
Random Access Memory
Boot protocol for TCP/IP
Excel's open architecture, proprietary, 1.3 Gbps fiber optic network using a packet-based protocol.
Connection between nodes, physical connectivity
Positive acknowledgment to a message
Real-Time Transport Protocol. Supports transport of real-time data like interactive voice and video over packet-switched networks.
See Transaction Capability Application Part.
PCM and companding standard used in Europe to compress and expand the amplitude range of a signal before and after transmission. See µ-Law.
The point in the Excel platform where a DS0 connects to a network. Also known as a "socket."
American Standard Code for Information Interchange
See Circuit Identification Codes.
Tag-Length-Value block. A standardized block that allows data to inserted in a standard way into API messages.
Local Area Network
See Time Division Multiplexing.
Extended Super Frame
Data channel. One of two fundamental components of an ISDN interface, it provides a path (16Kbps for BRI, 64Kbps for PRI) for carrying control signals and call data in a packet-switched mode.
Internet Protocol Device Control. Controls connections and signaling information in environments where the service control logic is separated from the network access device. This protocol suite was defined by a consortium of companies and has been proposed as a standard to the ITU.
Voice Recorded Announcement System
See Common Channel Signaling.
A type of diagnostic test in which the transmitted signal is returned to the sending device after passing through a data communications link or network.
Internet Protocol. Part of the TCP/IP family of protocols used to route messages and tracks the addresses of nodes.
A 32-bit address, used in IP routing, which includes a Network address identifier assigned by a central authority and a Host ID (an end station identifier assigned by a LAN administrator).
A condition that, when met, drives a state machine from one state to another. A condition that drives a Component out of its current state by invoking an associated primitive.
Session-Initiation Protocol. A signaling protocol used for establishing sessions in an IP network. A session could be a simple, two-way telephone call, or it could be a collaborative multi-media conference session.