> 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/connection-retry-conditions.md).

# Connection retry conditions

The conditions under which editran performs a CONNECTION RETRY with the same characteristics (NRI, facilities and user data) are the following.

* When all of the following conditions are met:
  * CALLING END = "L" (Local) or "X" (any).
  * CONNECTION TYPE = “I”,” Y”. (TCP, editran/PR)
  * Release Diagnosis other than:
    * 04: A call collision has occurred.
    * 05: There is already a CVC for that Session.
    * 06: Error in reverse charging.
    * 07: Error in payment type.
    * 08: Release by Operator.
    * 09: Release by Restart.
    * 0A: Invalid facilities.
    * 0C: Incorrect transmission time.
    * 0E: Invalid Calling End.
    * 11: Error in resid returned by NPSI.
    * 12: Error in termid returned by NPSI.
    * 5D: LACB not available.
    * 7F: Node error. Disconnection at the Host's request.
  * Cause = 00 or 80 and Diagnosis other than:
    * 0F: Generic editran release.
    * 58: Incorrect terminal.
  * Cause = 00 or 80, session pending connection, and Diagnosis other than:
    * 00: Remote transport level down. However, it is retried if transmission is in progress.

The conditions under which editran performs CONNECTION RETRY with another remote or local NRI (or IP address) are the following:

* When all the following conditions are met if it is a Release message, REPORT NPSI V3R8, or rejection of a call request.
  * CALLING END = "L" or "X".
  * CONNECTION TYPE = “I”,” Y”. (TCP, editran/PR)
  * Diagnoses not included among the previous editran ones.
  * The Backup retry sequence is as follows: 
    * REMOTE-IP (1)
    * REMOTE-IP (2)
    * And so on....


---

# 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/connection-retry-conditions.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.