SCCP/API:Alarms

From TBwiki
(Difference between revisions)
Jump to: navigation, search
(initial content)
 
 
(One intermediate revision by one user not shown)
Line 4: Line 4:
 
== Alarm ==
 
== 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 alarm (event) notification message is received by the host application when a SCCP is reporting an error. General explanation of the alarm event notification fields:
  
  
Line 13: Line 13:
  
  
−
*The category field (Category) indicates the category of the alarm. Possible values:
+
*The '''Category field''' indicates the category of the alarm. Possible values:
 +
 
  
 
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
Line 52: Line 53:
 
| Hop violation|| Out of range || Message discarded due to hop counter violation
 
| 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.
 
|}
 
|}
  
−
 
−
 
−
 
−
UNEQUIPPED
 
−
 
−
PROTOCOL_UNEQUIPPED
 
−
 
−
MTP-STATUS with indication remote SCCP unequipped.
 
  
  
Line 68: Line 61:
 
== LSAP Alarm ==
 
== 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 alarm (event) notification message is received by the host application when a SCCP LSAP is reporting an error. General explanation of the LSAP alarm event notification fields:
  
−
*The SCCP handle field (hSccp) specifies the handle of the SCCP instance
+
*The '''SCCP handle field''' specifies the handle of the SCCP instance
 
*The '''SCCP LSAP handle field''' specifies the handle of the SCCP LSAP 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 '''Category field''' indicates the category of the LSAP alarm. Possible values: see SCCP alarm category table at the beginning of this page
 
*The '''Event field''' specifies the event that cause the LSAP alarm
 
*The '''Event field''' specifies the event that cause the LSAP alarm
  
Line 79: Line 72:
  
  
−
*The cause field (Cause) specifies the cause of the Lsap alarm.
+
*The '''Cause field''' specifies the cause of the Lsap alarm.
  
  
 
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
−
! width="150" style="background:#efefef;" |Connection mode
+
|+ SCCP event and cause LSAP alarm under CATEGORY_PROTOCOL
−
! width="350" style="background:#efefef;" |Description
+
! width="150" style="background:#efefef;" |Event of Protocol Category
 +
! width="200" style="background:#efefef;" |Cause
 +
! width="200" style="background:#efefef;" |Description
 
|-
 
|-
−
| Normal|| MTP2 layer is used in conjunction with an above MTP3 layer
+
| Protocol bind-fail|| Unknown||Bind with service provider failed.
 
|-
 
|-
−
| HSL|| MTP2 layer high speed link is used in conjunction with an above MTP3 layer
+
| Protocol syntax error|| Invalid network message||Syntax error in message received from the network.
 
|}
 
|}
  
−
Table  SEQ Table \* ARABIC 92 - SCCP event and cause LSAP alarm under CATEGORY_PROTOCOL
 
  
−
Event of Protocol Category
 
  
−
TB640_SS7_SCCP_ALARM_EVENT_...
+
{| class="wikitable" border="1"
 +
|+ SCCP event and cause LSAP alarm under CATEGORY_INTERFACE
 +
! width="150" style="background:#efefef;" |Event of Interface Category
 +
! width="200" style="background:#efefef;" |Cause
 +
! width="200" style="background:#efefef;" |Description
 +
|-
 +
| Invalid lower interface event||
 +
*Out of range
 +
*Interface invalid SU
 +
*Interface protocol not active
 +
||Invalid lower interface event because of:
 +
*Parameter value out of range
 +
*Invalid suId
 +
*Protocol layer not active
 +
|}
  
−
Cause
 
  
−
TB640_SS7_SCCP_ALARM_CAUSE_...
+
== Userpart Alarm ==
  
−
Description
+
The alarm (event) notification message is received by the host application when a SCCP Userpart is reporting an error. General explanation of the Userpart alarm event notification fields:
−
 
+
*The '''SCCP handle field''' specifies the handle of the SCCP instance
−
PROTOCOL_BIND_FAIL
+
*The '''SCCP Userpart handle field''' specifies the handle of the SCCP Userpart instance
−
 
+
*The '''Category field''' indicates the category of the Userpart alarm. Possible values: see Table 90 - SCCP alarm category 0350033003000340039000000 .
−
UNKNOW
+
*The '''Event field''' specifies the event that cause the Userpart alarm.
−
 
+
−
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.
+
  
  
Line 162: Line 117:
  
  
−
*The'''Cause field''' specifies the cause of the Userpart alarm
+
*The '''Cause field''' specifies the cause of the Userpart alarm
  
  
 
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
−
! width="150" style="background:#efefef;" |Connection mode
+
|+ SCCP event and cause LSAP alarm under CATEGORY_PROTOCOL
−
! width="350" style="background:#efefef;" |Description
+
! width="150" style="background:#efefef;" |Event of Protocol Category
 +
! width="200" style="background:#efefef;" |Cause
 +
! width="200" style="background:#efefef;" |Description
 
|-
 
|-
−
| Normal|| MTP2 layer is used in conjunction with an above MTP3 layer
+
| Protocol in-service|| Protocol user-initiated||SCCP user came in-service (user initiated request)
 
|-
 
|-
−
| HSL|| MTP2 layer high speed link is used in conjunction with an above MTP3 layer
+
| Protocol out-of-service|| Protocol user-initiated||SCCP user going OOS (user initiated request)
 
|}
 
|}
  
−
Table  SEQ Table \* ARABIC 94 - SCCP event and cause USERPART alarm under CATEGORY_PROTOCOL
 
  
−
Event of Protocol Category
+
{| class="wikitable" border="1"
−
 
+
|+ SCCP event and cause LSAP alarm under CATEGORY_INTERFACE
−
TB640_SS7_SCCP_ALARM_EVENT_...
+
! width="150" style="background:#efefef;" |Event of Interface Category
−
 
+
! width="200" style="background:#efefef;" |Cause
−
Cause
+
! width="200" style="background:#efefef;" |Description
−
 
+
|-
−
TB640_SS7_SCCP_ALARM_CAUSE_...
+
| Invalid upper interface event||
−
 
+
*Out of range
−
Description
+
*Interface invalid SP
−
 
+
*Interface protocol not active
−
PROTOCOL_IN_SERVICE
+
||Invalid upper interface event because of:
−
 
+
*Parameter value out of range.
−
PROTOCOL_USER_INITIATED
+
*Invalid spId.
−
 
+
*Protocol layer not active.
−
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.
+

Latest revision as of 11:39, 1 May 2012

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 alarm event notification fields:


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



  • The Category field 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
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 LSAP alarm event notification fields:

  • The SCCP handle field 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 SCCP alarm category table at the beginning of this page
  • The Event field specifies the event that cause the LSAP alarm



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


SCCP event and cause LSAP alarm under CATEGORY_PROTOCOL
Event of Protocol Category Cause Description
Protocol bind-fail Unknown Bind with service provider failed.
Protocol syntax error Invalid network message Syntax error in message received from the network.


SCCP event and cause LSAP alarm under CATEGORY_INTERFACE
Event of Interface Category Cause Description
Invalid lower interface event
  • Out of range
  • Interface invalid 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 alarm (event) notification message is received by the host application when a SCCP Userpart is reporting an error. General explanation of the Userpart alarm event notification fields:

  • The SCCP handle field specifies the handle of the SCCP instance
  • The SCCP Userpart handle field specifies the handle of the SCCP Userpart instance
  • The Category field indicates the category of the Userpart alarm. Possible values: see Table 90 - SCCP alarm category 0350033003000340039000000 .
  • The Event field specifies the event that cause the Userpart alarm.



  • The Cause field specifies the cause of the Userpart alarm


SCCP event and cause LSAP alarm under CATEGORY_PROTOCOL
Event of Protocol Category 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)


SCCP event and cause LSAP alarm under CATEGORY_INTERFACE
Event of Interface Category Cause Description
Invalid upper interface event
  • Out of range
  • Interface invalid SP
  • Interface protocol not active
Invalid upper interface event because of:
  • Parameter value out of range.
  • Invalid spId.
  • Protocol layer not active.
Retrieved from "https://docs.telcobridges.com/mediawiki/index.php?title=SCCP/API:Alarms&oldid=10541"
Personal tools