SCCP/API:Alarms

From TBwiki
Revision as of 12:35, 4 September 2009 by Ktrueman (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Toolpack currently offers three types of alarms.


Alarm

The alarm (event) notification message is received by the host application when a SCCP is reporting an error. General explanation of the field of event notification alarm:


  • The SCCP handle field specifies the handle of the SCCP instance




  • The category field (Category) indicates the category of the alarm. Possible values:
Alarm Category Description
Protocol Protocol related alarms
Interface Interface related alarms




  • The Event field specifies the event that cause the alarm




  • The Cause field specifies the cause of the alarm


Event of Protocol Category Cause Description
Protocol Invalid Event

Decode Error

Invalid network message
  • Message decoding error
  • Invalid message type
Routing error Invalid Route Routing error
Hop violation Out of range Message discarded due to hop counter violation
Interface Interface related alarms



UNEQUIPPED

PROTOCOL_UNEQUIPPED

MTP-STATUS with indication remote SCCP unequipped.


LSAP Alarm

The alarm (event) notification message is received by the host application when a SCCP LSAP is reporting an error. General explanation of the fields of LSAP alarm notification event:

  • The SCCP handle field (hSccp) specifies the handle of the SCCP instance
  • The SCCP LSAP handle field specifies the handle of the SCCP LSAP instance
  • The Category field indicates the category of the LSAP alarm. Possible values: see Table 90 - SCCP alarm category 08D0C9EA79F9BACE118C8200A.
  • The Event field specifies the event that cause the LSAP alarm




  • The cause field (Cause) specifies the cause of the Lsap alarm.


Connection mode Description
Normal MTP2 layer is used in conjunction with an above MTP3 layer
HSL MTP2 layer high speed link is used in conjunction with an above MTP3 layer

Table SEQ Table \* ARABIC 92 - SCCP event and cause LSAP alarm under CATEGORY_PROTOCOL

Event of Protocol Category

TB640_SS7_SCCP_ALARM_EVENT_...

Cause

TB640_SS7_SCCP_ALARM_CAUSE_...

Description

PROTOCOL_BIND_FAIL

UNKNOW

Bind with service provider failed.

PROTOCOL_SYNTAX_ERROR

PROTOCOL_INV_NETWORK_MSG

Syntax error in message received from the network.

Table SEQ Table \* ARABIC 93 - SCCP event and cause LSAP alarm under CATEGORY_INTERFACE

Event of Interface Category

TB640_SS7_SCCP_ALARM_EVENT_...

Cause

TB640_SS7_SCCP_ALARM_CAUSE_...

Description

INTERFACE_INVALID_LI_EVENT

OUT_OF_RANGE

INTERFACE_INV_SU

INTERFACE_PROTOCOL_NOT_ACTIVE

Invalid lower interface event because of:

- Parameter value out of range.

- Invalid suId.

- Protocol layer not active.

Userpart Alarm =

The TB640_MSG_ID_SS7_SCCP_NOTIF_USERPART_ALARM (event) notification message is received by the host application when a SCCP Userpart is reporting an error.


General explanation of the field of event notification Userpart alarm:

- The SCCP handle field (hSccp) specifies the handle of the SCCP instance.

- The SCCP Userpart handle field (hSccpUserpart) specifies the handle of the SCCP Userpart instance.

- The category field (Category) indicates the category of the Userpart alarm. Possible values: see Table 90 - SCCP alarm category 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000E0000005F005200650066003100320034003700350033003000340039000000 .

  • The event field (Event) specifies the event that cause the Userpart alarm.




  • TheCause field specifies the cause of the Userpart alarm


Connection mode Description
Normal MTP2 layer is used in conjunction with an above MTP3 layer
HSL MTP2 layer high speed link is used in conjunction with an above MTP3 layer

Table SEQ Table \* ARABIC 94 - SCCP event and cause USERPART alarm under CATEGORY_PROTOCOL

Event of Protocol Category

TB640_SS7_SCCP_ALARM_EVENT_...

Cause

TB640_SS7_SCCP_ALARM_CAUSE_...

Description

PROTOCOL_IN_SERVICE

PROTOCOL_USER_INITIATED

SCCP user came in-service (user initiated request).

PROTOCOL_OUT_OF_SERVICE

PROTOCOL_USER_INITIATED

SCCP user going OOS (user initiated request).

Table SEQ Table \* ARABIC 95 - SCCP event and cause USERPART alarm under CATEGORY_INTERFACE

Event of Interface Category

TB640_SS7_SCCP_ALARM_EVENT_...

Cause

TB640_SS7_SCCP_ALARM_CAUSE_...

Description

INTERFACE_INVALID_UI_EVENT

OUT_OF_RANGE

INTERFACE_INV_SP

INTERFACE_PROTOCOL_NOT_ACTIVE

Invalid upper interface event because of:

- Parameter value out of range.

- Invalid spId.

- Protocol layer not active.

Personal tools