TCAP:TCAP Alarms
From TBwiki
(Difference between revisions)
(initial content) |
(clean up) |
||
Line 1: | Line 1: | ||
== Alarm == | == Alarm == | ||
− | The | + | The alarm (event) notification message is received by the [[TCAP]] service user when TCAP is reporting an error. |
General explanation of the fields of previous structure: | General explanation of the fields of previous structure: | ||
− | *The '''TCAP handle field''' specifies the handle of the TCAP instance | + | |
+ | *The '''TCAP handle field''' specifies the handle of the TCAP instance | ||
Line 15: | Line 16: | ||
{| class="wikitable" border="1" | {| class="wikitable" border="1" | ||
− | ! width="150" style="background:#efefef;" | | + | ! width="150" style="background:#efefef;" |Alarm category |
! width="350" style="background:#efefef;" |Description | ! width="350" style="background:#efefef;" |Description | ||
|- | |- | ||
− | | | + | | None|| No category |
|- | |- | ||
− | | | + | | Protocol|| Protocol related alarms |
+ | |- | ||
+ | | Interface|| Interface related alarms | ||
+ | |- | ||
+ | | Internal|| Internal software error related alarms | ||
+ | |- | ||
+ | | Resources|| System resources related alarms | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Line 67: | Line 48: | ||
|- | |- | ||
| Invalid event|| Invalid network message | | Invalid event|| Invalid network message | ||
+ | |- | ||
+ | | Invalid timer event|| Invalid timer expiration event | ||
+ | |- | ||
+ | | Invalid MI event|| Invalid layer manager event | ||
+ | |- | ||
+ | | Bind failure|| Bind with service provider failed | ||
+ | |- | ||
+ | | Message allocation failed|| Message allocation failed | ||
+ | |- | ||
+ | | Duplicate invoke ID|| Duplicate invoke ID | ||
+ | |- | ||
+ | | Mandatory missing|| Mandatory element is missing | ||
+ | |- | ||
+ | | Unexpected RX message|| Received unexpected message | ||
+ | |- | ||
+ | | Unknown RX message|| Received unknown message | ||
+ | |- | ||
+ | | Invalid dialog ID|| Invalid dialog ID | ||
+ | |- | ||
+ | | Unrecognized invoke ID|| Unrecognized invoke ID | ||
+ | |- | ||
+ | | Allocation dialog failure|| Dialog allocation failed | ||
+ | |- | ||
+ | | Hash failure|| Hash table operation failed | ||
+ | |- | ||
+ | | Max configuration|| Reached configuration limit | ||
+ | |- | ||
+ | | Invalid component|| Invalid component | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Line 135: | Line 82: | ||
− | *The '''Cause''' | + | *The '''Cause field''' specifies the cause of the alarm. |
− | |||
− | |||
− | + | {| class="wikitable" border="1" | |
− | + | ! width="150" style="background:#efefef;" |Alarm Cause | |
− | + | ! width="350" style="background:#efefef;" |Description | |
− | + | |- | |
− | No cause | + | | Unknown|| No cause |
− | + | |- | |
− | + | | Invalid SAP|| Invalid SAP | |
− | + | |- | |
− | Invalid SAP | + | | Invalid SP|| Invalid service provider (out-of-range) |
− | + | |- | |
− | + | | Invalid SU|| Invalid service user (out-of-range) | |
− | + | |- | |
− | Invalid service provider (out-of-range) | + | | Protocol not active|| Protocol layer is not active |
− | + | |- | |
− | + | | Interface version|| Invalid interface version | |
− | + | |- | |
− | Invalid service user ( | + | | Unbound|| SAP unbound |
− | + | |- | |
− | + | | Dialog allocation failed|| Dialog allocation failed | |
− | + | |- | |
− | Protocol layer is not active | + | | Invoke allocation failed|| Invoke allocation failed |
− | + | |- | |
− | + | | User-part association failed|| User-part association failed | |
− | + | |- | |
− | Invalid interface version | + | | SP SAP association failure|| Interface association failed |
− | + | |- | |
− | + | | Decoding failure|| Message decoding problem | |
− | + | |} | |
− | SAP unbound | + | |
− | + | ||
− | + | ||
− | + | ||
− | Dialog allocation failed | + | |
− | + | ||
− | + | ||
− | + | ||
− | Invoke allocation failed | + | |
− | + | ||
− | + | ||
− | + | ||
− | User-part association failed | + | |
− | + | ||
− | + | ||
− | + | ||
− | Interface association failed | + | |
− | + | ||
− | + | ||
− | + | ||
− | Message decoding problem | + | |
Latest revision as of 14:03, 9 September 2009
Alarm
The alarm (event) notification message is received by the TCAP service user when TCAP is reporting an error.
General explanation of the fields of previous structure:
- The TCAP handle field specifies the handle of the TCAP instance
- The Category field indicates the category of the alarm. Possible values:
Alarm category | Description |
---|---|
None | No category |
Protocol | Protocol related alarms |
Interface | Interface related alarms |
Internal | Internal software error related alarms |
Resources | System resources related alarms |
- The Event field specifies the event that caused the alarm.
Alarm Event | Description |
---|---|
None | No event |
Invalid UI event | Invalid upper interface event |
Invalid LI event | Invalid lower interface event |
Invalid event | Invalid network message |
Invalid timer event | Invalid timer expiration event |
Invalid MI event | Invalid layer manager event |
Bind failure | Bind with service provider failed |
Message allocation failed | Message allocation failed |
Duplicate invoke ID | Duplicate invoke ID |
Mandatory missing | Mandatory element is missing |
Unexpected RX message | Received unexpected message |
Unknown RX message | Received unknown message |
Invalid dialog ID | Invalid dialog ID |
Unrecognized invoke ID | Unrecognized invoke ID |
Allocation dialog failure | Dialog allocation failed |
Hash failure | Hash table operation failed |
Max configuration | Reached configuration limit |
Invalid component | Invalid component |
- The Cause field specifies the cause of the alarm.
Alarm Cause | Description |
---|---|
Unknown | No cause |
Invalid SAP | Invalid SAP |
Invalid SP | Invalid service provider (out-of-range) |
Invalid SU | Invalid service user (out-of-range) |
Protocol not active | Protocol layer is not active |
Interface version | Invalid interface version |
Unbound | SAP unbound |
Dialog allocation failed | Dialog allocation failed |
Invoke allocation failed | Invoke allocation failed |
User-part association failed | User-part association failed |
SP SAP association failure | Interface association failed |
Decoding failure | Message decoding problem |
Userpart Alarm
An alarm (event) notification message is received by the TCAP service user when a TCAP userpart is reporting an error.
- The TCAP handle field specifies the handle of the TCAP instance.
- The TCAP Userpart handle field specifies the handle of the TCAP Userpart instance.
- The Category field indicates the category of the Userpart alarm. Possible values: see the 'TCAP alarm category' table in TCAP Alarms.
- The Event field specifies the event that cause the Userpart alarm. Possible values: see the 'TCAP alarm event' table in TCAP Alarms.
- The Cause field specifies the cause of the Userpart alarm. Possible values: see the 'TCAP alarm cause' table in TCAP Alarms.