https://docs.telcobridges.com/mediawiki/index.php?action=history&feed=atom&title=SCCP%2FAPI%3AAlarms
SCCP/API:Alarms - Revision history
2026-06-01T05:01:06Z
Revision history for this page on the wiki
MediaWiki 1.18.1
https://docs.telcobridges.com/mediawiki/index.php?title=SCCP/API:Alarms&diff=10541&oldid=prev
Sylvain Fontaine: moved SCCP:Alarms to SCCP/API:Alarms
2012-05-01T16:39:38Z
<p>moved <a href="/tbwiki/SCCP:Alarms" class="mw-redirect" title="SCCP:Alarms">SCCP:Alarms</a> to <a href="/tbwiki/SCCP/API:Alarms" title="SCCP/API:Alarms">SCCP/API:Alarms</a></p>
<table class='diff diff-contentalign-left'>
<tr valign='top'>
<td colspan='1' style="background-color: white; color:black;">← Older revision</td>
<td colspan='1' style="background-color: white; color:black;">Revision as of 16:39, 1 May 2012</td>
</tr></table>
Sylvain Fontaine
https://docs.telcobridges.com/mediawiki/index.php?title=SCCP/API:Alarms&diff=2611&oldid=prev
Ktrueman: cleaned up
2009-09-04T20:05:24Z
<p>cleaned up</p>
<a href="https://docs.telcobridges.com/mediawiki/index.php?title=SCCP/API:Alarms&diff=2611&oldid=2609">Show changes</a>
Ktrueman
https://docs.telcobridges.com/mediawiki/index.php?title=SCCP/API:Alarms&diff=2609&oldid=prev
Ktrueman: initial content
2009-09-04T17:35:53Z
<p>initial content</p>
<p><b>New page</b></p><div>Toolpack currently offers three types of alarms.<br />
<br />
<br />
== Alarm ==<br />
<br />
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:<br />
<br />
<br />
*The '''SCCP handle field''' specifies the handle of the SCCP instance<br />
<br />
<br />
----<br />
<br />
<br />
*The category field (Category) indicates the category of the alarm. Possible values:<br />
<br />
{| class="wikitable" border="1"<br />
! width="150" style="background:#efefef;" |Alarm Category<br />
! width="350" style="background:#efefef;" |Description<br />
|-<br />
| Protocol|| Protocol related alarms<br />
|-<br />
| Interface|| Interface related alarms<br />
|}<br />
<br />
<br />
----<br />
<br />
<br />
*The '''Event field''' specifies the event that cause the alarm<br />
<br />
<br />
----<br />
<br />
<br />
*The '''Cause field''' specifies the cause of the alarm<br />
<br />
<br />
{| class="wikitable" border="1"<br />
! width="150" style="background:#efefef;" |Event of Protocol Category<br />
! width="200" style="background:#efefef;" |Cause<br />
! width="200" style="background:#efefef;" |Description<br />
|-<br />
| Protocol|| Invalid Event<br />
Decode Error<br />
||Invalid network message<br />
*Message decoding error<br />
*Invalid message type<br />
|-<br />
| Routing error|| Invalid Route || Routing error<br />
|-<br />
| Hop violation|| Out of range || Message discarded due to hop counter violation<br />
|-<br />
| Interface|| Interface related alarms<br />
|}<br />
<br />
<br />
<br />
<br />
UNEQUIPPED<br />
<br />
PROTOCOL_UNEQUIPPED<br />
<br />
MTP-STATUS with indication remote SCCP unequipped.<br />
<br />
<br />
<br />
== LSAP Alarm ==<br />
<br />
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:<br />
<br />
*The SCCP handle field (hSccp) specifies the handle of the SCCP instance<br />
*The '''SCCP LSAP handle field''' specifies the handle of the SCCP LSAP instance<br />
*The '''Category field''' indicates the category of the LSAP alarm. Possible values: see Table 90 - SCCP alarm category 08D0C9EA79F9BACE118C8200A.<br />
*The '''Event field''' specifies the event that cause the LSAP alarm<br />
<br />
<br />
----<br />
<br />
<br />
*The cause field (Cause) specifies the cause of the Lsap alarm.<br />
<br />
<br />
{| class="wikitable" border="1"<br />
! width="150" style="background:#efefef;" |Connection mode<br />
! width="350" style="background:#efefef;" |Description<br />
|-<br />
| Normal|| MTP2 layer is used in conjunction with an above MTP3 layer<br />
|-<br />
| HSL|| MTP2 layer high speed link is used in conjunction with an above MTP3 layer<br />
|}<br />
<br />
Table SEQ Table \* ARABIC 92 - SCCP event and cause LSAP alarm under CATEGORY_PROTOCOL<br />
<br />
Event of Protocol Category<br />
<br />
TB640_SS7_SCCP_ALARM_EVENT_...<br />
<br />
Cause<br />
<br />
TB640_SS7_SCCP_ALARM_CAUSE_...<br />
<br />
Description<br />
<br />
PROTOCOL_BIND_FAIL<br />
<br />
UNKNOW<br />
<br />
Bind with service provider failed.<br />
<br />
PROTOCOL_SYNTAX_ERROR<br />
<br />
PROTOCOL_INV_NETWORK_MSG<br />
<br />
Syntax error in message received from the network.<br />
<br />
Table SEQ Table \* ARABIC 93 - SCCP event and cause LSAP alarm under CATEGORY_INTERFACE<br />
<br />
Event of Interface Category<br />
<br />
TB640_SS7_SCCP_ALARM_EVENT_...<br />
<br />
Cause<br />
<br />
TB640_SS7_SCCP_ALARM_CAUSE_...<br />
<br />
Description<br />
<br />
INTERFACE_INVALID_LI_EVENT<br />
<br />
OUT_OF_RANGE<br />
<br />
INTERFACE_INV_SU<br />
<br />
INTERFACE_PROTOCOL_NOT_ACTIVE<br />
<br />
Invalid lower interface event because of:<br />
<br />
- Parameter value out of range.<br />
<br />
- Invalid suId.<br />
<br />
- Protocol layer not active.<br />
<br />
== Userpart Alarm ===<br />
<br />
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.<br />
<br />
<br />
General explanation of the field of event notification Userpart alarm:<br />
<br />
- The SCCP handle field (hSccp) specifies the handle of the SCCP instance.<br />
<br />
- The SCCP Userpart handle field (hSccpUserpart) specifies the handle of the SCCP Userpart instance.<br />
<br />
- The category field (Category) indicates the category of the Userpart alarm. Possible values: see Table 90 - SCCP alarm category 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000E0000005F005200650066003100320034003700350033003000340039000000 .<br />
<br />
*The event field (Event) specifies the event that cause the Userpart alarm.<br />
<br />
<br />
----<br />
<br />
<br />
*The'''Cause field''' specifies the cause of the Userpart alarm<br />
<br />
<br />
{| class="wikitable" border="1"<br />
! width="150" style="background:#efefef;" |Connection mode<br />
! width="350" style="background:#efefef;" |Description<br />
|-<br />
| Normal|| MTP2 layer is used in conjunction with an above MTP3 layer<br />
|-<br />
| HSL|| MTP2 layer high speed link is used in conjunction with an above MTP3 layer<br />
|}<br />
<br />
Table SEQ Table \* ARABIC 94 - SCCP event and cause USERPART alarm under CATEGORY_PROTOCOL<br />
<br />
Event of Protocol Category<br />
<br />
TB640_SS7_SCCP_ALARM_EVENT_...<br />
<br />
Cause<br />
<br />
TB640_SS7_SCCP_ALARM_CAUSE_...<br />
<br />
Description<br />
<br />
PROTOCOL_IN_SERVICE<br />
<br />
PROTOCOL_USER_INITIATED<br />
<br />
SCCP user came in-service (user initiated request).<br />
<br />
PROTOCOL_OUT_OF_SERVICE<br />
<br />
PROTOCOL_USER_INITIATED<br />
<br />
SCCP user going OOS (user initiated request).<br />
<br />
Table SEQ Table \* ARABIC 95 - SCCP event and cause USERPART alarm under CATEGORY_INTERFACE<br />
<br />
Event of Interface Category<br />
<br />
TB640_SS7_SCCP_ALARM_EVENT_...<br />
<br />
Cause<br />
<br />
TB640_SS7_SCCP_ALARM_CAUSE_...<br />
<br />
Description<br />
<br />
INTERFACE_INVALID_UI_EVENT<br />
<br />
OUT_OF_RANGE<br />
<br />
INTERFACE_INV_SP<br />
<br />
INTERFACE_PROTOCOL_NOT_ACTIVE<br />
<br />
Invalid upper interface event because of:<br />
<br />
- Parameter value out of range.<br />
<br />
- Invalid spId.<br />
<br />
- Protocol layer not active.</div>
Ktrueman