> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-cics-en/utilities-and-codes/appendix-c.-release-causes-and-diagnostics/onesait-editran-causes-and-diagnostics.md).

# Onesait · Editran causes and diagnostics

Below, the cause and diagnosis codes for call release or rejection provided by editran are specified. In the case of editran releases for TCP/IP connections, consult [TCP.](/documentacion-editran/ibm-editran-v5.3-cics-en/tcp.md)

* Cause = x'00'.
  * Diagnosis = x'XX'. Where "XX" means the following:
    * 03 - The maximum number of sessions defined in Local Environment (Maximum Number of Circuits) has been reached and therefore no channel is available.
    * 04 - A call crossing in flight has occurred. The one with the lower editran Installation Code is released.
    * 05 - A release has occurred because a channel is already established for that session.
    * 06 - The collect call facility is not accepted in the incoming call according to the Session parameters in Profiles.
    * 07 - Call rejected by Payment Type. In the Session Profile parameters, the payment type is defined as "R" (Remote), while the incoming call comes with collect.
    * 08 - editran release by the Operator.
    * 09 - A network restart has occurred by the Operator.
    * 0A - The incoming call is rejected for using invalid facilities.
    * 0B - Not used (in editran versions < 2.1, circuit is released due to Compactation-Compression error).
    * 0C - An incoming call is rejected because the entry time is incorrect according to the Session specifications (START TIME and END TIME).
    * 0D - The call is rejected because:
      * Session not registered.
      * The local or remote NRI (or their lengths) of the incoming call packet does not match those specified in the session.
      * The version does not match.
      * &#x20;The terminal code through which the call enters does not match the one defined in profiles.
      * The fictitious LU through which the call enters does not match the one defined in profiles.
      * The connection type does not match.
      * The access identifiers do not match.              &#x20;
      * A match between an X25 diagnosis and an editran diagnosis.
    * 0E - The call is rejected because the Calling End defined in the Session does not correspond to the one making the call.
    * 0F - Generic editran release (files not prepared, automation startup, etc.).
    * 10 - NPSI-DATE requests that a specific channel be released.
    * 11 - Error in resid range (NPSI-DATE or GATE). It occurs when the one defined for a Session is not within the range given by NPSI.
    * 12 - Error in termid range (NPSI-DATE or GATE). It occurs when the resid calculated by NPSI determines the terminal that must be activated and it does not exist or cannot be connected. In these cases, the Session record should be reviewed, specifically the first terminal field.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-cics-en/utilities-and-codes/appendix-c.-release-causes-and-diagnostics/onesait-editran-causes-and-diagnostics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.