|
|
| Diagnostic Messages |
|
|
| X.25 Diagnostic Messages |
Table | Call Setup, Call Clearing, or Registration Problem | ||
|
|
|
|
| Diagnostic | ISO | Explanation |
| Description | ||
|
|
| |
|
|
|
|
| 65 (CLEAR) | Facility/ | Packet size negotiation, Window Size |
|
| registration | Negotiation or Throughput Class |
|
| code not | Negotiation facility codes found in the |
|
| allowed. | facility field of the call setup packet |
|
|
| when corresponding negotiation had |
|
|
| not been configured. In CALL |
|
|
| REQUEST, condition results in error |
|
|
| returned to user instead of generation |
|
|
| of CLEAR. |
|
|
| If facility checking was configured, a |
|
|
| facility code not allowed by configured |
|
|
| level (1980 or 1984) was found before |
|
|
| the first facility marker. In CALL |
|
|
| REQUEST, this condition results in an |
|
|
| error returned to user instead of |
|
|
| generation of CLEAR. |
|
|
| If facility checking was configured |
|
|
| along with rejection of duplicate |
|
|
| facilities, a combination of invalid |
|
|
| facility codes was detected. |
|
|
| The combination may indicate that the |
|
|
| basic and extended format of given |
|
|
| facility are present or that both the |
|
|
| Closed User Group and Closed User |
|
|
| Group with Outgoing Access facilities |
|
|
| are present. In CALL REQUEST, this |
|
|
| condition results in an error instead of |
|
|
| a CLEAR. |
|
|
| Facility marker 00 3B (hex) found, |
|
|
| which corresponds to “internal” |
|
|
| facilities. This facility marker is not |
|
|
| allowed by either application or |
|
|
| network. In CALL REQUEST, this |
|
|
| condition results in an error returned |
|
|
| to the user instead of CLEAR. |
|
|
|
|
Appendix C | 255 |