Alarm and Alarm Cleared messages

The CSP sends an Alarm message (0x00B9) to the host when the cards are taken out of service (OOS). When cards are brought back in service, the CSP sends an Alarm Cleared (0x00C1) message to the host.

For DSP modules, the CSP sends and Alarm Clear message to the host when the DSP Module is brought in service.

This functionality applies to all CSP cards except the following:

• I/O cards

• Matrix Controller card

• Virtual cards

The CSP sends information about the cards to the host in the Card Status Report message (0x00A6). Host applications act based on the Alarm and Alarm Cleared messages received from the CSP. This feature allows the application to track card status and take action without modifying the application.

Sent by

Host

Example Message
(Socket Log Output)

The following example message (socket log output for SwitchKit) takes channels 0x01 through 0x05 on span 0x01 out of service.

00 13 00 0A 00 00 FF 01 02 0D 03 00 01 01 0D 03 00 01 05 0F 00

Configuration

ServiceStateConfig (

Node = Integer,

Range = StartSpan:StartChan - EndSpan:EndChan,

Span = Integer,

Slot = Integer,

SIMM = Integer,

StackID = Integer,

LinkID = Integer,

Ring = Integer,

V5ID = Integer,

DS3 = Integer,

Action = Integer,

ForcedFlag = Integer);

C Structure

typedef struct {

UBYTE AddrInfo[30];

UBYTE Action;

UBYTE ForcedFlag;

} XL_ServiceStateConfig;

C++ Class

class XLC_ServiceStateConfig : public XLC_ChanRangeMessage {

public:

const UBYTE *getAddrInfo() const;

UBYTE *getAddrInfo();

void setAddrInfo(UBYTE *x);

XBYTE getStartSpan() const;

void setStartSpan(XBYTE x);

UBYTE getStartChannel() const;

void setStartChannel(UBYTE x);

XBYTE getEndSpan() const;

void setEndSpan(XBYTE x);

UBYTE getEndChannel() const;

void setEndChannel(UBYTE x);

UBYTE getDSPChip() const;

void setDSPChip(UBYTE x);

UBYTE getDSPSlot() const;

void setDSPSlot(UBYTE x);

UBYTE getDSPSIMM() const;

void setDSPSIMM(UBYTE x);

UBYTE getSlot() const;

void setSlot(UBYTE x);

UBYTE getStackID() const ;

void setStackID(UBYTE x);

UBYTE getLni() const ;

void setLni(UBYTE x);

UBYTE getSIMM() const;

void setSIMM(UBYTE x);

UBYTE getDS3() const;

void setDS3(UBYTE x);

XBYTE getSpan() const;

void setSpan(XBYTE x);

XBYTE getV5ID() const;

void setV5ID(XBYTE x);

UBYTE getAction() const;

void setAction(UBYTE x);

UBYTE getForcedFlag() const;

void setForcedFlag(UBYTE x);

};

EXS API Hex Format

Invalid Responses

NOTE: These invalid responses apply to the V5 ID address type only

• 0x01- The host could be attempting to bring the V5 interface in
service or out of service when the V5 Interface ID (4 bytes)
has not been configured. The host could be attempting to bring the V5 interface in service or out of service when the V5 ID is not configured.

• 0x04- The host could be attempting to bring the V5 interface in
service when the V5 Variant ID has not been configured for
that interface.

• 0x07- The host could be attempting to bring the V5 interface in
service when no user ports are configured for the V5 ID.

• 0x0A- The host could be attempting to bring the V5 interface in
service when no C Channels are assigned to this V5 ID.

• 0x0B-The host was attempting to bring a V5 interface in service
when a C Channel was found on an unconfigured link.

• 0x0D RESERVED
0x0E RESERVED
0x0F RESERVED

Notes:

1 When a DS3 is taken out of service, the CSP automatically takes all spans and channels on the DS3 out of service. When the DS3 is brought back in service, the spans and channels are not automatically brought back in service. You must manually bring the spans and channels in service. A DS3 must be in service before any spans can be brought in service. The CSP returns a status of DS3 Out of Service (0x5A) if you attempt to bring a span in service first.

2 When bringing a card in service that was previously out of service, the host must wait for a Card Status Report message on the appropriate slot before considering the card in service.

3 When a span is taken out of service, all channels on the span are automatically taken out of service by the CSP. When the span is brought back in service using this message, the channels are not automatically brought back in service. You must send this message again to bring the channels back into service.

4 The host should not consider a channel in service upon receiving the Response to this message. The host must receive a DS0 Status Change message with status of "In Service" before considering the channel in service.

5 If you are using E1 Channel 30 for purposes other than CAS (for example, CCS), you cannot include it in a range with other channels. Instead, you must bring E1 Channel 30 into service with a single separate Service State Configure message. Be sure that both the starting and ending spans and channels are set to the span and channel 30.

6 If you take an E1 PPL channel out of service using this message, the host receives the following:
-A DS0 Status Change message (0x42) that has a Channel Status field value of 0x01 (Out of Service).
-A DS0 Status Change message (0x42) that has a Channel Status field value of 0x00 (Purge) and a Purge Reason field value of 0x74 (Disabled While Non-dormant).The system sends this second message to the host as a result of meeting certain criteria but does not actually perform a purge. You can ignore this second message.