This appendix describes the results that are returned with ATM signaling requests. The cause codes and diagnostic information that are described are returned when an ATM request is rejected at the other endpoint or anywhere along the connection. The numerical values for ATM UNI causes and diagnostics are those assigned by the ATM standards; the values for Silicon Graphics messages are specific to IRIS ATM.
Table A-1 lists the cause codes that are used by implementations that conform to the ATM User-Network Interface Specification (ATM UNI) standard. The Comments column points out codes that are specific to particular versions of the ATM UNI (for example, 3.0 and 3.1). Table A-4, summarizes the diagnostic information that accompany some of the cause codes. Table A-2, lists implementation-specific cause codes used by the IRIS ATM Signaling software.
Table A-1. ATM UNI Cause Codes
Text for ATM UNI Cause | Cause Number | Comments |
|---|---|---|
Unallocated / Unassigned Number | 1 | Additional information is supplied. See Table A-4. |
No Route to Specified Transit Network | 2 |
|
No Route to Destination | 3 | Additional information is supplied. See Table A-4. |
Unacceptable VPCI_VCI | 10 |
|
Normal_3.1 | 16 | Not used with UNI 3.0 Used only with UNI 3.1 |
User Busy | 17 |
|
No User Responding | 18 |
|
Call Rejected | 21 | Additional information is supplied. See Table A-4. |
Number Changed | 22 | Additional information is supplied. See Table A-4. |
User Rejects Calls With Calling Line Identification Restriction (CLIR) | 23 |
|
Destination Out of Order | 27 |
|
Invalid Number Format | 28 |
|
Response to STATUS ENQUIRY | 30 |
|
Normal_3.0 | 31 | Used only with UNI 3.0 Not used with UNI 3.1 |
Requested VPCI/VCI Unavailable | 35 |
|
VPCI Assignment Failure | 36 |
|
User Cell Rate Unavailable | 37 | Not used with UNI 3.0 Used only with UNI 3.1 |
Network Out of Order | 38 |
|
Temporary Failure | 41 |
|
Access Information Discarded | 43 | Additional information is supplied. See Table A-4. |
No VPCI/VCI Available | 45 |
|
Resource Unavailable, Unspecified | 47 |
|
QOS Unavailable | 49 | Additional information is supplied. See Table A-4. |
User Cell Rate Unavailable | 51 | Used only with UNI 3.0 Not used with UNI 3.1 Additional information is supplied. See Table A-4. |
Bearer Capability Not Authorized | 57 |
|
Bearer Capability Not Presently Available | 58 |
|
Service or Option Unavailable, Unspecified | 63 |
|
Bearer Capability Not Implemented | 65 |
|
Unsupported Combination of Traffic Parameters | 73 |
|
AAL Parameters Cannot Be Supported | 78 | Not used with UNI 3.0 Used only with UNI 3.1 |
Invalid Call Reference | 81 |
|
Identified Channel Does Not Exist | 82 | Additional information is supplied. See Table A-4. |
Incompatible Destination | 88 | Additional information is supplied. See Table A-4. |
Invalid Endpoint Reference | 89 |
|
Invalid Transit Network Selection | 91 |
|
Too Many Pending Add Party Requests | 92 |
|
AAL Parameters Cannot Be Supported | 93 | Used only with UNI 3.0 Not used with UNI 3.1 |
Mandatory Information Element Missing | 96 | Additional information is supplied. See Table A-4. |
Message Type Non-existent or Not Implemented | 97 | Additional information is supplied. See Table A-4. |
Information Element Non-existent or Not Implemented | 99 | Additional information is supplied. See Table A-4. |
Invalid Information Element Contents | 100 | Additional information is supplied. See Table A-4. |
Message Not Compatible With Call State | 101 | Additional information is supplied. See Table A-4. |
Recovery On Timer Expiry | 102 | Additional information is supplied. See Table A-4. |
Incorrect Message Length | 104 |
|
Protocol Error, Unspecified | 111 |
|
Text for SGI Cause | Cause Number | Comments |
|---|---|---|
Local Error | 128 | Unknown driver or signal-daemon error |
Already | 129 | Registration denied: BLLI already taken, or application already registered |
Invalid Best Effort | 130 | Best Effort requires that both directions be Best Effort and QOS_0 |
Invalid Cell Rate | 131 | Invalid cellrate field |
Invalid BLLI | 132 | Invalid broadband low layer information (blli) code specified |
Invalid Bearer Class | 133 | Invalid bearer class |
Invalid Dress FMT | 134 | Invalid address format |
Not Multipoint | 135 | Add or drop party on a point-to-point call |
Party Handle In Use | 136 | Trying to add a party using the a party handle that has already been used |
Invalid Party Handle | 137 | Request was dropped because the party handle was not found |
Table A-3. ATM UNI Failure Locations
Text for ATM UNI Location | Location Number | Comments |
|---|---|---|
User | 0x00 | Local host |
Private Network Serving the Local User | 0x01 | Private local switch |
Public Network Serving the Local User | 0x02 | Public local switch |
Transit Network | 0x03 | Transit network |
Public Network Serving the Remote User | 0x04 | Remote public switch |
Private Network Serving the Remote User | 0x05 | Remote private switch |
International Network | 0x07 | International network |
Network Beyond Interworking Point | 0x0A | Network beyond interworking point |
Table A-4. ATM UNI Diagnostics
Accompanying ATM UNI Cause | ATM UNI Diagnostic Provided | Diagnostic Values |
|---|---|---|
Unallocated / Unassigned Number | One octet | The diagnostics provide a number to indicate the condition, and text to indicate whether the condition is normal or abnormal and who supplied the diagnostic, as follows: |
| 0x80 Unknown normal provider 0x81 Permanent normal provider 0x82 Transient normal provider 0x84 Unknown abnormal provider 0x85 Permanent abnormal provider 0x86 Transient abnormal provider 0x88 Unknown normal user 0x89 Permanent normal user 0x8A Transient normal user 0x8C Unknown abnormal user 0x8D Permanent abnormal user 0x8E Transient abnormal user | |
Call Rejected | Two octets | The diagnostics provide the following information: the first octet contains a number indicating the reason, and a description of the condition. The second octet contains either user-specific values or the identifier for the ATM UNI information element (IE), whichever is appropriate. |
| 0x80 user specific unknown 0x81 user specific permanent 0x82 user specific transient 0x84 IE missing unknown 0x85 IE missing permanent 0x86 IE missing transient 0x88 IE missing unknown 0x89 IE missing permanent 0x8A IE missing transient | |
No Route to Destination | One octet | Same as Unallocated Number. |
Number Changed | 6 to 25 octets | The new destination address formatted with a Called Party Number information element. |
Access Information Discarded | One or more octets | Each octet specifies one ATM UNI information element identifier. |
QOS Unavailable | One octet | Same as Unallocated Number. |
User Cell Rate Unavailable | One or more octets | Each octet specifies one subfield identifier from the ATM UNI User Cell Rate information element. |
Identified Channel Does Not Exist | 4 octets | Most significant two octets specify VPCI value. Least significant two octets specify VCI value. |
Incompatible Destination | 1 octet | The ATM UNI information element identifier. |
Mandatory Information Element Missing | 1 or more octets | Each octet is one ATM UNI information element identifier. |
Message Type Non-existent or Not Implemented | One octet | Specifies one ATM UNI message type: for example, SETUP, RELEASE, CONNECT. |
Information Element Non-existent or Not Implemented | 1 or more octets | Each octet is one ATM UNI information element identifier. |
Invalid Information Element Contents | 1 or more octets | Each octet is one ATM UNI information element identifier. |
Message Not Compatible With Call State | One octet | Specifies one ATM UNI message type: for example, SETUP, RELEASE, CONNECT. |
Recovery On Timer Expiry | Three octets | Each octet specifies one IA5 character to indicate one numeral identifying an ATM UNI timer. For example, for the timer called T308, the first octet specifies 3, the second 0, and the third 8. |