editran/p - indraeditran.indra.es/en/doc/win_unix/editran/editran_p_en.pdf · editran/p...

EDITRAN/P

Application Generic Interface

Windows/Unix

User manual

INDRA 17/03/17

EDITRAN/P Windows/Unix User manual INDEX

INDRA. All rights reserved. EDITRAN/P

1. INTRODUCTION ................................................................................................................................... 1-1

2. DESCRIPTION ...................................................................................................................................... 2-1

2.1. FUNCTIONS ..................................................................................................................................................... 2-1 2.1.1. EDITRAN V2.0. ......................................................................................................................................................................................................................... 2-1 2.1.2. EDITRAN V2.1. ......................................................................................................................................................................................................................... 2-1 2.1.3. EDITRAN V2.2. ......................................................................................................................................................................................................................... 2-2 2.1.4. EDITRAN V3.0. ......................................................................................................................................................................................................................... 2-2 2.1.5. EDITRAN V3.1. ......................................................................................................................................................................................................................... 2-2 2.1.6. EDITRAN V4.0. ......................................................................................................................................................................................................................... 2-2 2.1.7. EDITRAN V4.1. ......................................................................................................................................................................................................................... 2-2 2.1.8. EDITRAN V5.0. ......................................................................................................................................................................................................................... 2-3

2.2. EMISSION AND RECEPTION BUFFERS ........................................................................................................... 2-3

3. EDITRAN/P MANAGER (UNIX)............................................................................................................ 3-1

3.1. DESCRIPTION OF THE USER INTERFACE ....................................................................................................... 3-1 3.1.1. SCREENS .................................................................................................................................................................................................................................... 3-1 3.1.2. HELP ............................................................................................................................................................................................................................................ 3-2 3.1.3. KEYS ............................................................................................................................................................................................................................................. 3-2

3.2. EDITRAN/P OPERATOR .................................................................................................................................. 3-3 3.2.1. Sessions query ........................................................................................................................................................................................................................ 3-3 3.2.2. Connection request ............................................................................................................................................................................................................... 3-4 3.2.3. Release request ...................................................................................................................................................................................................................... 3-4 3.2.4. Emission request .................................................................................................................................................................................................................... 3-4 3.2.5. Reception request ................................................................................................................................................................................................................. 3-4 3.2.6. End of emission....................................................................................................................................................................................................................... 3-4 3.2.7. End of reception ..................................................................................................................................................................................................................... 3-4 3.2.8. Message for the remote operator .................................................................................................................................................................................. 3-5 3.2.9. Monitoring the remote emission file ............................................................................................................................................................................. 3-5 3.2.10. Monitoring the remote reception file ............................................................................................................................................................................ 3-6

3.3. FILE MONITORING .......................................................................................................................................... 3-7 3.3.1. Monitoring the emission / reception log ...................................................................................................................................................................... 3-7 3.3.2. Monitoring the log file ......................................................................................................................................................................................................... 3-9 3.3.3. Sessions general monitoring ......................................................................................................................................................................................... 3-10

3.4. EDITRAN/P ADMINISTRATOR ...................................................................................................................... 3-11 3.4.1. Local Environment .............................................................................................................................................................................................................. 3-11 3.4.2. Sessions .................................................................................................................................................................................................................................. 3-14

4. EDITRAN/P MANAGER (WINDOWS) ................................................................................................... 4-1

4.1. DESCRIPTION OF THE USER INTERFACE ....................................................................................................... 4-1 4.1.1. SCREENS .................................................................................................................................................................................................................................... 4-1 4.1.2. HELP ............................................................................................................................................................................................................................................ 4-2 4.1.3. ABOUT......................................................................................................................................................................................................................................... 4-2

4.2. STARTING AND STOPPING EDITRAN/P ......................................................................................................... 4-2

4.3. EDITRAN/P OPERATOR .................................................................................................................................. 4-3 4.3.1. Connection ................................................................................................................................................................................................................................ 4-3 4.3.2. Release ....................................................................................................................................................................................................................................... 4-3 4.3.3. Emission ..................................................................................................................................................................................................................................... 4-3 4.3.4. End of emission....................................................................................................................................................................................................................... 4-4 4.3.5. Reception .................................................................................................................................................................................................................................. 4-4 4.3.6. End of reception ..................................................................................................................................................................................................................... 4-4 4.3.7. Message for the remote node .......................................................................................................................................................................................... 4-4

4.4. FILE MONITORING .......................................................................................................................................... 4-5 4.4.1. File local monitoring ............................................................................................................................................................................................................. 4-5 4.4.2. Remote monitoring of emission files ............................................................................................................................................................................ 4-6 4.4.3. Remote monitoring of reception files ........................................................................................................................................................................... 4-6 4.4.4. Log monitoring ........................................................................................................................................................................................................................ 4-6

4.5. EDITRAN/P ADMINISTRATOR ........................................................................................................................ 4-8 4.5.1. Local environment ................................................................................................................................................................................................................. 4-8 4.5.2. Sessions management ...................................................................................................................................................................................................... 4-11

4.5.2.1. General data ............................................................................................................................................................................................................ 4-11 4.5.2.2. TCP/IP tab ................................................................................................................................................................................................................. 4-13 4.5.2.3. X25 tab ...................................................................................................................................................................................................................... 4-14

EDITRAN/P Windows/Unix User manual INDEX

INDRA. All rights reserved. EDITRAN/P

4.5.2.4. X28 tab ...................................................................................................................................................................................................................... 4-15 4.5.2.5. SWIFT tab .................................................................................................................................................................................................................. 4-17 4.5.2.6. Options tab ............................................................................................................................................................................................................... 4-18 4.5.2.7. Cryptography tab................................................................................................................................................................................................... 4-20

5. ANNEXES ............................................................................................................................................. 5-1

5.1. EDITRAN COMPONENTS ................................................................................................................................. 5-1 5.1.1. CURRENT SCHEME ................................................................................................................................................................................................................. 5-1

5.2. DISTRIBUTION ................................................................................................................................................ 5-2 5.2.1. Components ............................................................................................................................................................................................................................. 5-2 5.2.2. EDITRAN/P and EDITRAN/G servers .............................................................................................................................................................................. 5-2 5.2.3. Clients ......................................................................................................................................................................................................................................... 5-3 5.2.4. Communications servers ..................................................................................................................................................................................................... 5-3

5.3. COMMANDS ..................................................................................................................................................... 5-3 5.3.1. EDItran ........................................................................................................................................................................................................................................ 5-3 5.3.2. editranp ...................................................................................................................................................................................................................................... 5-3 5.3.3. edix25 ......................................................................................................................................................................................................................................... 5-3 5.3.4. editcp ........................................................................................................................................................................................................................................... 5-3 5.3.5. edix28 ......................................................................................................................................................................................................................................... 5-3 5.3.6. editransw ................................................................................................................................................................................................................................... 5-3 5.3.7. makelog ...................................................................................................................................................................................................................................... 5-4 5.3.8. menup ......................................................................................................................................................................................................................................... 5-4 5.3.9. menucmd ................................................................................................................................................................................................................................... 5-4 5.3.10. copycfg ....................................................................................................................................................................................................................................... 5-5 5.3.11. printcfg ....................................................................................................................................................................................................................................... 5-6 5.3.12. resetkey ..................................................................................................................................................................................................................................... 5-6 5.3.13. importkey................................................................................................................................................................................................................................... 5-7 5.3.14. printlog ....................................................................................................................................................................................................................................... 5-8 5.3.15. EDITRAN/GT transmissions manager (WINDOWS) .................................................................................................................................................. 5-8 5.3.16. NL FILTER .................................................................................................................................................................................................................................. 5-8 5.3.17. ediperfi ....................................................................................................................................................................................................................................... 5-9

5.4. FILES ............................................................................................................................................................... 5-9 5.4.1. editranp.cfg .............................................................................................................................................................................................................................. 5-9 5.4.2. editranp.sdx .............................................................................................................................................................................................................................. 5-9 5.4.3. editran.html .............................................................................................................................................................................................................................. 5-9 5.4.4. ckds.des ...................................................................................................................................................................................................................................... 5-9 5.4.5. editranp.log ............................................................................................................................................................................................................................... 5-9 5.4.6. editranp.msg ............................................................................................................................................................................................................................ 5-9 5.4.7. editranp.out ........................................................................................................................................................................................................................... 5-10 5.4.8. licencia.dat ............................................................................................................................................................................................................................. 5-10 5.4.9. licencia.publick ..................................................................................................................................................................................................................... 5-10

5.5. CODES AND MESSAGES TO THE OPERATOR ............................................................................................... 5-10

5.6. EDITRAN RELEASE MESSAGES .................................................................................................................... 5-16 5.6.1. EDITRAN CAUSES AND DIAGNOSIS ............................................................................................................................................................................. 5-16 5.6.2. RELEASES CAUSES AND DIAGNOSIS FOR A CALL X.28. ..................................................................................................................................... 5-17 5.6.3. CONDITIONS FOR CONNECTION RETRIES ................................................................................................................................................................ 5-19

5.7. EDITRAN CRYPTOGRAPHY SYSTEM ............................................................................................................ 5-20 5.7.1. Introduction ........................................................................................................................................................................................................................... 5-20 5.7.2. Types of keys ....................................................................................................................................................................................................................... 5-20 5.7.3. Cryptography errors ........................................................................................................................................................................................................... 5-21

EDITRAN/PWindows/UnixUser manual 1.INTRODUCTION

INDRA. All rights reserved. EDITRAN/P Pg. 1-1

1. INTRODUCTION

Indra’s EDITRAN platform has two essential components:

Communications Platfors (EDITRAN/P).

It includes all the common services which are related to communication facilities

(protocol, interfaces with TCP transmission services, X.25, X.28, LU6.2, local networks,

etc.).

Generic Module of Application Interfaces (EDITRAN/G).

It isolates the communication services provided by EDITRAN/P for user applications, and

it is also the nexus among them and the transmission processes.

EDITRAN/G Downloading in Receiver

Translation and conversion

Unzipping

Deciphering

EDITRAN/G Uploading in Issuer

Translation and conversion

Zipping

Ciphering

EDITRAN/P

Connection management

Node authentication

Synchronization

Transmission sessions

Display session

RECEIVER APPLICATION

EDITRAN/P

Connection management

Node authentication

Synchronization

ISSUER APPLICATION

Online

EDITRAN/P Windows/Unix User manual 2.DESCRIPTION


2. DESCRIPTION

EDITRAN transfers files, with a certain structure, from a local node to another. These files

are named emission and reception buffers.

To obtain emission buffers from application conventional files, and also to obtain this

application files from reception buffers, it is necessary to use uploading and downloading

programs (a group of them is called application interface).

These interfaces can have a great variety of functionality and possibilities, from the

treatment of a certain file to the treatment of any kind of file. In this last case, we would be

having an application generic interface.

The current Application Generic Interface (from now on EDITRAN/G) has been developed

with two objectives: to increase the funcionalities of the existing interfaces, and at the same

time to be compatible with the previous ones. In this way, a company which installs the late

EDITRAN/G version will be able to:

Leave aside the previous interfaces.

Exchange data with companies that have previous versions of EDITRAN/G, using

compatibility mode with that version.

Exchange data with companies that have the same EDITRAN/G version, both in

compatible mode (the same funcionality than the previous interfaces, with

improvements in the process), or in native mode (extended functionalities).

2.1. FUNCTIONS

Here it will be presented the evolution of the display and application functions (which are

optional) in the different versions of EDITRAN.

2.1.1. EDITRAN V2.0.

Totals control. This option has been used very little, and it is to put a numeric field

(which is usually an amount) in every emission block, corresponding to the logical

records within the block. Here are included records of totals by sections, so it is

possible to make an especial synchronism and the receiver can check whether the

total is the sum of the amounts of the section.

Zipping. Three or more repeated characters are replaced by 3 before sending. When

receiving, the inverse operation is made.

CRC. We add a cyclic redundancy code in the emission message, and we check it in

the reception.


Totals control, zipping and CRC.

Optional cryptography. Interface with several hardware and software cryptography

products.

Parameters notification. The remote EDITRAN version is added to the session profile.

It it’s V2.1, the calling node notifies the remote one the session, cryptography,

zipping, totals control, CRC, and transmission lenght parameters (in a SAP message).

The remote node verifies and accepts or rejects it. If the version is V1.0 or V2.0, the

two nodes have to agree about the parameters to be used for the transmission.




Zipping, CRC and cryptography.

The totals control is replaced by Application Synchronism or Batches, as we

understand that the application functions must be in the interfaces and not in

EDITRAN. Meanwhile, EDITRAN has enough mechanisms to guarantee information

integrity.

Appears the Transmission Interruption Procedure, executed by EDITRAN when an

outage occurs.

The most relevant feature of this version is the change in the session identification

length, which had 6 and now has 12 characters.


Code extension (NIF): EDITRAN codes change from 6 numeric digits to 9 digits, from

which the first and the last one are alphanumeric, and the rest are numeric. This is

the NIF (Número de Identificación Fiscal / Tax Identification Number) format.

Multienvironment, allows EDITRAN to act with different local identifications.


This last version has the same functionalities than EDITRAN 3.0, but having in

account the effect 2000. It incorporates 4 digits in dates (YEAR 2000).


Incompatibility EDITRAN/P V2.2. An important feature of this version is the fact that

is not compatible with the EDITRAN versions prior to 3.0. The EDITRAN/G versions

2.1, 3.0 and 3.1 are still compatible with EDITRAN/G 4.0.

Distributed EDITRAN.

Local-remote address rotation (x25, tcp).


Indication of the EDITRAN version in the EDITRAN Administrator and Operator.

Inclusion of the Triple DES algorithm to the 3.0 EDITRAN cryptography mode.

Inclusion of the origin code in the users’ data of TCP/IP connections, to make

possible the definition of more than 10 subenvironments per application with a

single remote node.

Control, in the emission starting request (SCP), of the local and remote buffers’

content synchronization.

Translation, during reception, according to the introduction profile.

EDITRAN/G V1.0 and 2.0 incompatibilitiy. EDITRAN/G versions 2.1, 3.0, 3.1 and 4.0

are still compatible with EDITRAN/G 4.1.

New parameter to validate the calling remote node.

Inclusion of a new module (optional) for the transmission management (EDITRAN/GT,

only for Windows).

New functionality in Windows for X25 with EICON motherboards. This allows to set

the motherboard to be used, in case we have more than one, and also the board port,

if we have more than one per board.




Extension of the number of local and remote lines. The number of lines has been

extended from 3 to 6 (nris, ips), in order to make possible to have more alternative

routes if network falls.

Automatic version update. It has been implemented a protocol by which EDITRAN

entities can exchange their versions. In case they both are 5.0 or higher, the profiles

will be updated to the minimum installed version of both of them.

Validations before the reception. They avoid some problems that were detected so

far in the download after transmission. In particular, is validated whether the upload

version is known, and whether the zipped/encrypted file has license.

Addition of a new module (optional) for the file transmission through the SWIFT

network.

Backup in connection types. For each session, a main network protocol is defined.

Optionally, we can define other networks that will be used as back up for the failed

connections.

Application files, whose size is more than 2 Gb, are supported.

2.2. EMISSION AND RECEPTION BUFFERS

They are the ones used by EDITRAN.

A buffer file contains data about a unique transmission session.

The log length can be (including the key) from 13 up to 9999 characters. When the

remote node is a HOST, the only valid characters are 252 or 4050.

The buffers are composed of:

A first control log, with the key sequence number to zero. This log contains, among

other data, the following (which can affect the interface):

Total number of logs.

Number of confirmed logs.

Indicator of whether emission or reception are completed.

Indicator of disponibility for EDITRAN.

Number of exchange session.

Several data logs with the key correlative sequence number, from 1 to the total

exchanged number.



3. EDITRAN/P MANAGER (UNIX).

EDITRAN/P manager is introduced now:

+-----------------------------------------------------------------------------+

| dd/mm/aa - GESTOR DE EDITRAN/P - EDItran/P V5.0.x |

| 16:13:04 X.25 X.28 TCP FTP |

+-----------------------------------------------------------------------------+

| |

| |

| |

| 1.- OPERADOR DE EDItran |

| |

| 2.- CONSULTA DE FICHEROS |

| |

| 3.- ADMINISTRADOR DE EDItran |

| |

| OPCION : |

| |

| |

| |

| |

| |

| |

| |

| F1 ? Ayuda On-Line F2 Campo por defecto F3 Fin entrada |

| F4 Pantalla por defecto F6 Shell OS ESC Menu previo |

+-----------------------------------------------------------------------------+

If it is the first time we run EDITRAN, we must fill the data of the local environment (see

chapter 3.4.1 Local environment) and then reboot EDITRAN.

3.1. DESCRIPTION OF THE USER INTERFACE

3.1.1. SCREENS

In the EDITRAN UNIX screen we can distinguish three areas:

+-----------------------------------------------------------------------------+

| dd/mm/aa - GESTOR DE EDItran/P - EDItran/P V5.0.x |

|(1)16:17:54 - OPERADOR DE EDItran/P - X.25 X.28 TCP FTP |

+-----------------------------------------------------------------------------+

| 1.- CONSULTA DE SESIONES |

| 2.- PETICION DE CONEXION |

| 3.- PETICION DE LIBERACION |

| 4.- PETICION DE EMISION |

| 5.- PETICION DE RECEPCION |

| 6.- FIN DE EMISION |

| 7.- FIN DE RECEPCION |

| 8.- MENSAJE PARA EL OPERADOR REMOTO |

| E.- CONSULTA FICHERO EMISION REMOTO |

| R.- CONSULTA FICHERO RECEPCION REMOTO |

| OPCION : |

| SESION : |

| |


|(2) F4 Pantalla por defecto F6 Shell OS ESC Menu previo |

+-----------------------------------------------------------------------------+

| SESION : EMISION : / ESTADO : |

| RECEPCION : / ESTADO : |

|(3) |

+-----------------------------------------------------------------------------+



(1) Title

In the title area appears general information about EDITRAN system:

Current date and time (in the same moment we activate the screen).

Target of the screen: administrator, operator, etc.

Version and operating system.

(2) Options

In this area can appear the different menu options, the parameters to be filled by

the operator, or the requests results..

(3) Information

In this area appears the information that EDITRAN sends to the operator:

Session.

Emission and reception status.

Emission and reception counters.

Information text or messages from the remote operator.

3.1.2. HELP

EDITRAN UNIX has available a help system, sensitive to context. In this way, when we click

on F1 or ?, appears a window with the help text associated to the field or the screen where

the cursor is.

3.1.3. KEYS

In EDITRAN UNIX, we can use the following keys within the menu:

F1, ? Help sensitive to context.

F2 Enters the default values of the current field, whenever possible.

F3 Ends the current screen data input, validating all the fields.

F4 Enters the default values of the current screen, whenever possible.

F6 Performs an exit to the operating system to execute other commands (shell),

remaining EDITRAN resident. To go back to EDITRAN we must execute the

exit command.

Enter Finishes the data input in the current field, updating its value. If no value has

been entered, the system enters the value of the last request.

Spacebar Selects the field value from a list of enumerated values:

A (o) B ( ) C ( )

or activates/deactivates the field value from two possible values:

D [X]

Esc Aborts the data introduction and goes back to the previous menu.

Del Deletes the character before the cursor.

Tab Goes to the next field without updating or modifying its value.

Arrows Moves the cursor, within the same screen, to the next/previous field or to the

next/previous value in the field.

PgUp

Control-U

Page back.

PgDn

Control-D

Page forward.



3.2. EDITRAN/P OPERATOR

To manage Exchange sessions, we need to select the option 1 in the main menú, GESTOR

DE EDItran/P (EDITRAN/P MANAGER), which has the following options:

+-----------------------------------------------------------------------------+

| dd/mm/aa - GESTOR DE EDItran/P - EDItran/P V5.0.x |

| 16:17:54 - OPERADOR DE EDItran/P - X.25 X.28 TCP FTP |

+-----------------------------------------------------------------------------+

| 1.- CONSULTA DE SESIONES |

| 2.- PETICION DE CONEXION |

| 3.- PETICION DE LIBERACION |

| 4.- PETICION DE EMISION |

| 5.- PETICION DE RECEPCION |

| 6.- FIN DE EMISION |

| 7.- FIN DE RECEPCION |

| 8.- MENSAJE PARA EL OPERADOR REMOTO |

| E.- CONSULTA FICHERO EMISION REMOTO |

| R.- CONSULTA FICHERO RECEPCION REMOTO |

| OPCION : |

| SESION : |

| |



+-----------------------------------------------------------------------------+



| |

+-----------------------------------------------------------------------------+

3.2.1. Sessions query

Select the option 1 from the menu OPERADOR DE EDItran (EDItran OPERATOR).

Query of active sessions can be performed in a general or in a particular way.

To consult a particular session, we must fill the SESSION and click Enter. In the screen

information area (at the bottom) will appear the information about the status and the

emission/reception counters for the requested session.

To perform a general query, we need to fill the field SESSION with zeros. The screen that

will appear will be similar to the following one:

+-----------------------------------------------------------------------------+

| dd/mm/aa - GESTOR DE EDItran - EDItran/P V5.0.x |

| 16:21:24 - CONSULTA DE SESIONES - X.25 X.28 TCP FTP |

+-----------------------------------------------------------------------------+

| |

| SESION ESTADO EMISION ESTADO RECEPCION CONTADOR-EMI CONTADOR-REC |

| ============== ================ ================ ============ ============ |

| SOLARIS-X.25 DESCONECTADO DESCONECTADO 000000000000 000000000000 |

| PC-X.28 EMITIENDO CONECTADO 000000000000 000000000000 |

| PC-X.32 SINCRONIZADO RECIBIENDO 000000000000 000000000000 |

| |

| |

| |

| |

| |

| |

| |



+-----------------------------------------------------------------------------+

| SESION : INDRA-TEST EMISION : 00000000/00000000 ESTADO : DESCONECTADO |

| RECEPCION : 00000000/00000000 ESTADO : DESCONECTADO |

| Consulta de estado |

+-----------------------------------------------------------------------------+



3.2.2. Connection request

To establish manually the physical connection with a remote EDITRAN, in order to start the

transmission process, we must select option 2 from the menu OPERADOR DE EDItran

(EDItran operator). The request is not allowed when the EDITRAN operation mode is

Server.

This request is automatically generated when we ask for an emission or reception request,

if we specify S value in the parameter LLAMADA AUTOMATICA (AUTOMATIC CALL) in the

session profile.

In the information area appear indications about the result of the request (connection

fulfilled or not).

3.2.3. Release request

To release manually the existing connection for a session, we must select the option 3

from the menu OPERADOR DE EDItran (EDItran OPERATOR).

3.2.4. Emission request

To start the local emission of a file, we must select the option 4 from the menu OPERADOR

DE EDItran (EDItran OPERATOR).

The request is not allowed if the local EDITRAN operation mode is Server.

3.2.5. Reception request

To start a file reception, which must be emitted by the remote node, we have to select

option 5 from the menu OPERADOR DE EDItran (EDItran OPERATOR).

The request is not accepted when the local EDITRAN operation mode is Server.

3.2.6. End of emission

To request the forced end of the local emission (emission interruption) we must select the


The request is not accepted when the EDITRAN operation mode is Server.

3.2.7. End of reception

To request the forced end of the local reception (reception interruption) we must select the





3.2.8. Message for the remote operator

There must be a connection with the remote EDITRAN which will be the receiver of the

message from the operator.

The following screen, in which we will have to write the text to send, will appear:

+-----------------------------------------------------------------------------+


| 16:41:38 - MENSAJE PARA EL OPERADOR REMOTO - X.25 X.28 TCP FTP |

+-----------------------------------------------------------------------------+

| |

| SESION : INDRA-TEST |

| |

| |

| MENSAJE : |

| |

| |

| |

| |

| |

| |

| |

| |



+-----------------------------------------------------------------------------+



| |

+-----------------------------------------------------------------------------+

3.2.9. Monitoring the remote emission file

To monitor the remote emission file, we will have to select the option E from the menu

OPERADOR DE EDItran (EDItran OPERATOR).

The local EDITRAN program will send the monitoring message to the remote node, and the

local node will be expecting to receive the answer from the remote one. This answer will be

displayed through the next screen. It is necessary to have established first a connection

between both nodes.

+-----------------------------------------------------------------------------+

| dd/mm/aa - CONSULTA REGISTRO EMISION/RECEPCION - EDItran/P V5.0.x |

| 16:44:02 - REMOTO - X.25 X.28 TCP FTP |

+-----------------------------------------------------------------------------+

| |

| FICHERO : E SESION : INDRA-TEST |

| |

| FECHA CREACION : 21/03/2010 HORA CREACION : 08:07:07 |

| FECHA ULT. INSERCION : 00/00/00 HORA ULT. INSERCION : 00:00:00 |

| |

| FECHA INIC TRANSMISION : 17/10/2014 HORA INIC TRANSMISION: 08:07:07 |

| FECHA ULT CONFIRMACION : 17/10/2014 HORA ULT CONFIRMACION: 08:07:17 |

| |

| NUMERO TOTAL REGISTROS : 000000000004 |

| N. REG. CONFIRMADOS : 000000000004 N. REG. ENVIADOS : 000000000004 |

| ESTADO FICHERO : INTERRUMPIDO |

| CODIGO RESULTADO : ERROR DE SINCRO |

| ESTADO TRANSMISION : NO SE HA EMITIDO COMPLETO |

| ULT SINCRONISMO ENVIADO: 000000000000 ULT SINCRONISMO CONFI: 000000000000 |

| ULT SINCRONISMO INTERCA: 000000000000 NUM SESION INTERCAMB : 000000000270 |

| |

| |

| Pulse una tecla para continuar |

+-----------------------------------------------------------------------------+



3.2.10. Monitoring the remote reception file

To monitor the remote reception file, we must select the option R from the menu

OPERADOR DE EDItran (EDItran OPERATOR).

The local EDITRAN program will send the monitoring message to the remote node, and the

local node will remain waiting for the answer from the remote one. The answer will be

displayed in the following screen. First, is necessary to have established a connection

between both nodes.

+-----------------------------------------------------------------------------+


| 16:45:50 - REMOTO - X.25 X.28 TCP FTP |

+-----------------------------------------------------------------------------+

| |

| FICHERO : R SESION : INDRA-TEST |

| |



| |



| |




| CODIGO RESULTADO : SATISFACTORIO |

| ESTADO TRANSMISION : NO SE HA RECIBIDO COMPLETO |



| |

| |


+-----------------------------------------------------------------------------+



3.3. FILE MONITORING

+-----------------------------------------------------------------------------+


| 16:46:56 - CONSULTA DE FICHEROS - X.25 X.28 TCP FTP |

+-----------------------------------------------------------------------------+

| |

| |

| |

| 1.- CONSULTA DE REGISTRO EMISION/RECEPCION |

| |

| 2.- CONSULTA DE LOG |

| |

| 3.- CONSULTA GENERICA DE SESIONES |

| |

| OPCION : |

| |

| |

| |

| |

| |

| |

| |



+-----------------------------------------------------------------------------+

3.3.1. Monitoring the emission / reception log

To obtain information about the control log of the local emission or reception control file,

select option 1 from the menu CONSULTA DE FICHEROS (FILE MONITORING).

The following menu will appear:

+-----------------------------------------------------------------------------+

| dd/mm/aa - CONSULTA DE FICHEROS - EDItran/P V5.0.x |

| 16:47:50 - CONSULTA REGISTRO EMISION/RECEPCION - X.25 X.28 TCP FTP |

+-----------------------------------------------------------------------------+

| |

| |

| |

| |

| FICHERO (E/R) : |

| |

| SESION : |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |



+-----------------------------------------------------------------------------+

We must select the TIPO DE FICHERO (emisión E o recepción R) / TIPE OF FILE (emission E

or reception R) and enter the SESIÓN (SESSION).

Two screens, with the data of the local remission or reception file control log for the

specified session, will be presented.



For monitoring a local emission file (when we enter an E in the field TIPO DE FICHERO /

FILE TYPE), we can obtain the following information:

+-----------------------------------------------------------------------------+


| 16:49:06 - LOCAL - X.25 X.28 TCP FTP |

+-----------------------------------------------------------------------------+

| |

| FICHERO : E SESION : INDRA-TEST |

| |



| |



| |




| CODIGO RESULTADO : ERROR DE SINCRO |

| ESTADO TRANSMISION : NO SE HA EMITIDO COMPLETO |



| |

| |


+-----------------------------------------------------------------------------+

For monitoring the reception file (when we enter a R in the field TIPO DE FICHERO / FILE

TYPE), we can obtain a similar information, but relative to the direction of the reception.

+-----------------------------------------------------------------------------+


| 16:49:54 - LOCAL - X.25 X.28 TCP FTP |

+-----------------------------------------------------------------------------+

| |

| FICHERO : R SESION : INDRA-TEST |

| |



| |



| |




| CODIGO RESULTADO : SATISFACTORIO |

| ESTADO TRANSMISION : NO SE HA RECIBIDO COMPLETO |



| |

| |


+-----------------------------------------------------------------------------+



3.3.2. Monitoring the log file

It will display all the informative messages sent by EDITRAN to the operator.

To monitor these logs, we must select option 3 from the menu CONSULTA DE FICHEROS

(FILE MONITORING). The following menu will appear:

+-----------------------------------------------------------------------------+


| 16:51:16 - CONSULTA DE LOG - X.25 X.28 TCP FTP |

+-----------------------------------------------------------------------------+

| |

| |

| |

| |

| SESION : |

| |

| FECHA (DD/MM/AA) : / / |

| |

| HORA (HH/MM/SS) : : : |

| |

| |

| |

| |

| |

| |

| |

| |



+-----------------------------------------------------------------------------+

Optionally, we will fill the fields SESION (SESSION), FECHA (DATE) and HORA (TIME). If we

don’t specify any filter, the last registered entries will be displayed.

In case it is a general query, we have to write zeros in the field SESION (SESSION).

To see more logs, we will use the keys PgDn/Control-D to go forward or PgUp/Control-U to

go back.

The file editranp.log is treated cyclically.

+-----------------------------------------------------------------------------+


| 16:52:19 - CONSULTA DE LOG - X.25 X.28 TCP FTP |

+-----------------------------------------------------------------------------+

| SESION : INDRA-TEST FECHA : 22/03/10 HORA : 01:00:00 |

| |

|SESION FECHA HORA MENSAJE |

+-----------------------------------------------------------------------------+

|INDRA-TEST 17/10/2014 13:22:11 Conexion realizada |

|INDRA-TEST 17/10/2014 13:22:11 Asociacion establecida |

|INDRA-TEST 17/10/2014 13:22:11 Comienzo de la transmision |

|INDRA-TEST 17/10/2014 13:22:12 Principio de sesion. Emision local |

|INDRA-TEST 17/10/2014 13:22:21 Emision correcta y finalizada |

|INDRA-TEST 17/10/2014 13:22:21 Se ha lanzado batch posterior a emision |

|INDRA-TEST 17/10/2014 13:22:21 Liberacion de la transmision |

|INDRA-TEST 17/10/2014 13:22:21 Posterior a emision finalizado correctamente |

|INDRA-TEST 17/10/2014 13:22:22 Fichero tampon cargado |

|INDRA-TEST 17/10/2014 13:22:22 Peticion batch de inicio de emision IGA21 |

|INDRA-TEST 17/10/2014 13:22:22 Peticion de asociacion |

|INDRA-TEST 17/10/2014 13:22:22 Se realiza la llamada |

|INDRA-TEST 17/10/2014 13:22:22 Conexion realizada |

+-----------------------------------------------------------------------------+

| PgUp Ctrl-U Pagina Anterior PgDn Ctrl-D Pagina Siguiente ESC Salir |

+-----------------------------------------------------------------------------+



3.3.3. Sessions general monitoring

It will display all the sessions defined in the profile file.

To monitor these logs, we must select option 4 from the menu CONSULTA DE FICHEROS

(FILE MONITORING). The following screen will appear.

+-----------------------------------------------------------------------------+


| 16:53:09 - CONSULTA GENERICA DE SESIONES - X.25 X.28 TCP FTP |

+-----------------------------------------------------------------------------+

|SESION NOMBRE REMOTO NOMB APLICACION NRI LOCAL NRI REMOTO |

+-----------------------------------------------------------------------------+

|INDRA-TEST INDRA Pruebas 21586342417 21586342416 |

+-----------------------------------------------------------------------------+

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| |

| PgUp Ctrl-U Pagina Anterior PgDn Ctrl-D Pagina Siguiente ESC Salir |

+-----------------------------------------------------------------------------+



3.4. EDITRAN/P ADMINISTRATOR

To access the EDITRAN administration menu, we must select option 3 from the main menu

GESTOR DE EDItran (EDItran MANAGER).

The following options, for the management of the local environment and the sessions, will

be presented.

3.4.1. Local Environment

The EDITRAN/P primary local environment is managed with the option 1 from the menu

ADMINISTRADOR (ADMINISTRATOR). In those entities that don’t have multienvironment

license, i.e., the possibility to be presented as multicenter is not necessary to define a specific

profile for secondary environments. It will be enough to specify the new code in the

correspondant sessions.

We must fill the following requested data:



LOCAL

We will write the identification number of the EDITRAN user entity. With this

identification number, the entity will be recognized by all the interconnected entities.

The entity codes in EDITRAN have nine characters (NIF) with the format xnnnnnnnx.

NAME

We will write the installation description. This is just an informative field.

MAXIMUM NUMBER OF SESSIONS

We can specify the maximum number of exchange sessions than can be concurrently

executed in a certain moment.

For example, in the EDITRAN X.25 version, the maximum value we can take will match

the number of logical channels that will be set for the card X.25. For the X.28 version, it

will be the number of available modems.

X.25 ADDRESS

We will write the IBERPAC network number of the local user entity.

For example, in X.25 connections we can enter up to 3 NRI's with variable lenght, with a

maximum of 15 digits.

IP ADDRESS

The address of an own machine in a TCP/IP network admits up to 3 different addresses

with 3 listening ports for each address.

TCP TIMEOUT CONNECTION

It is the maximum timeout since the connection from a remote socket is accepted until

the session data, which definitely establish a TCP connection in EDITRAN/P, are

exchanged. This timeout prevents other applications to connect indefinitely to the port

used by EDITRAN. If we don’t want to enable this timeout, we need to put 0.



In facilities with SWIFT network license, we also need other parameters, correspondant to

concepts of this network. It is advisable to contact the Swift Alliance Gateway (SAG) product

administrator to know the values that these fields must have.

SWIFT security context

We will indicate the user and password correspondant to the certificate we asked to

SWIFT, with the needed permissions to use the FileAct functionality.

Store-And-Forward context

It is the resources we need to Access Swift SnF services. With this delivery mode, the

files remain temporarily stored in a Swift server, until the entity collects them.



3.4.2. Sessions

To connect and to make emissions and/or receptions with a remote EDITRAN, we have to

specify the parameters that describe the session profile. It is also necessary to have

previously registered the local environment (see 3.4.1 Local Environment).

We will register as many sessions as different connections we want to establish.

Then we will select option 2 from the menu ADMINISTRADOR DE EDItran (EDItran

ADMINISTRATOR).

In every option we will have to specify:

SESSION

Session identification. Except for the registration, it is admitted to specify a search filter.

In this case, it will show a list of the sessions that fit a certain mask, so that the user can

choose.



Once it is selected, will appear the screens in which the user can fill or visualize (depending

on the chosen option) the parameters or features that define the session.

In Alta (Register) and Modificación (Modification) all the fields, except the session

identificator, are unprotected. To perform this option we must reach the last screen.

In Consulta (Monitoring), every field is protected.

The first screen shows the parameters that affect the connection:

The description of the fields that appear in this screen is the following:

LOCAL

Identification code for the local center.

LOCAL NAME

Name of the local associated to the session. This is just an informative field.

REMOTE

Identification code for the remote center.

REMOTE NAME

Name of the remote center associated to the session. This is just an informative field.

APPLICATION

Identification code for the user application of the EDITRAN system transmission service.

APPLICATION NAME

Name of the user application. This is just an informative field.

VERSION NUMBER

Version of the remote EDITRAN/P system. It can be 5.1, 5.0, 4.1 or 4.0. It must be

coincident with the correspondant value of the session in the remote node.



MAIN NETWORK

Stack of lower level protocols, used for the transmissions to the remote entity. The

EDITRAN/P protocol will use this red as the priority in outoing connections. Only when

the recovery mechanisms fail (address rotation and attempts), we will try to access the

remote node through the backup networks. Is mandatory to specify which is the

network we consider to be the main one.

The possible values are:

X X.25. Public (IBERPAC) or private network. Synchronous transmission in packet

mode.

P public or private X.28-PAD. Asynchronous connection to a packet

assembler/disassemble device. Asynchronous transmission in character mode.

L SNA network with LU6.2. Connection through any kind of communication service

supported by the installation (X.25, Token Ring, Ethernet, FDDI, etc.).

T TCP/IP netword. Connection to a network which contains the TCP/IP protocol.

F When the protocol to be used is FTP. It is only admitted as main network.

S SWIFT network. File transmission through the FileAct service. It is only admitted as

main network.

BACKUP NETWORK

Protocol of network level, used as backup for the EDITRAN/P transmissions when the

main network is not available. It is not allowed to specify as backup network the same

we are using as main network. With main protocol FTP or SWIFT is not admitted to

define backup.

The possible values are:

X X.25. Public (IBERPAC) or private network. Synchronous transmission in packet

mode.

P X.28-PAD.

L SNA network with LU6.2.

T TCP/IP network.

ACCESS ID

A numeric value from 0 to 9, needed for X25 connections, that along with the remote

code and the application, identifies the session correspondant to the call.

CALLING EXTREME (L/R/X)

L It can call only the LOCAL extreme.

R Only the REMOTE extreme can call.

X Any of both extremes can call.

TRAFFIC DIRECTION (E/R/X)

E It is possible only to emit in this session.

R It is possible only to receive in this session.

X It is possible to emit and receive simultaneously.

AUTOMATIC CALL (S/N)

S The connection will be automatically established when we request the emission or

reception to start.

N We have to establish a previous connection before the emission/reception request.

AUTOMATIC DISCONNECTION (S/N)

S The disconnection request is generated automatically when the emission or reception

finishes.

N The disconnection is not generated automatically.



TIME-OUT (Seconds)

Is the time interval, in seconds, in which EDITRAN expects to receive from the remote

node an answering message to a previously sent control message.

If the TIME-OUT interval is over and we didn’t get an answer, the same request will be

sent again, and a new waiting interval will start. This is also equivalent to the

connection requests.

MAXIMUM NUMBER OF RETRIES

Is the number of times that the previous TIME-OUT procedures are repeated.

SAVE ROTATIONS (S/N)

S In case we request a call, when the connection is established by addresses (nri / ip)

that are not in the profile in the first position, they remain stored in that position. The

purpose is to achieve the connection without retrying the call in future transmissions.

N The profile addresses are not updated in any case.

Once the values for this screen are entered and validated, it will appear a new one for each

type of network we are going to use in this session. In these screens we will define the

specific parameters for each network.

Now we will explain all the possibilities, although the most common is that one session

only needs some of them to be defined.

The parameters associated to TCP networks are the following:

REMOTE IP ADDRESSES

IP address and port of the remote node we want to connect. We can indicate up to 6 IP

different addresses.

VALIDATE REMOTE IP (S/N)

S In incoming calls, is validated whether the IP address of the entity which is trying to

connect is in the list of remote IP addresses.

N Connections from any remote IP are allowed.



USE EDItran PROXY (S/N)

With S value the outcoming transmission requests will be performed through an

EDITRAN module (EDITRAN/PX) which acts as a proxy server. The incoming connections

can come through the proxy or directly, regardless of this parameter value.

IP PROXY ADDRESSES

IP address and acces port to the EDITRAN/PX server. Up to 2 possible addresses can be

indicated.

The parameters associated to the X.25 protocol are:

LOCAL NRIs

They are the IBERPAC (NRI) Network Numbers that the local equipment has.

We can specify up to 3 different numbers. EDITRAN uses these NRI's to validate

incoming calls, and in outcoming calls, they rotate the orden in which they appear, until

the connection is made.

A local NRI can be also specified by its link logical identificator. This value is established

by the X.25 drivers administrator, and it can vary depending on the platform we use.

REMOTE NRIs

They are the network numbers or network addresses belonging to the EDITRAN remote

node which we call. We can specify up to 6 different numbers.

In case it is necessary to retry the call, by each local NRI there will be a try with all the

given remote nodes.

PROTOCOL ID

Protocol identifier. It is part of the user data from the X.25 call packet. It must be

coincident with the one of the remote session. Rank = "00-FF". Value by default = "C0".

VALIDATE NRIs (S/N)

Selector to validate the NRIs of the income call pack.

S The NRIs called and caller must be coincident with the ones of the profile.

N There are no validations.



REVERSE CHARGE (S/N)

Incoming calls are admitted, or not, when reverse charge facility is asked.

METHOD OF PAYMENT (L/R/X)

Payment of the connection

L Metered call to the local node.

R Metered call to the remote node. Outcoming calls will be performed with the reverse

charge facility.

X Indistinct.

ACCEPT PAD CALLS (S/N)

Controls the access when the remote calls come from PAD.

S They are accepted. In this case, remote NRIs are never validated.

R They are rejected.

The parameters to set in the X.28 protocol are:

REMOTE NRI's

They are the network numbers or network addresses belonging to the EDITRAN remote

node which we call.

We can specify up to 6 different numbers. If the session is also set for X.25 connections,

the list of remote NRIs is common.

DATA BITS (7/8)

Number of data bits during the exchange of characters between the asynchronous

terminal and the PAD.

7-bit PAD

8-bit PAD

CONNECTION COMMAND

Character, or sequence of characters, from the PAD connection command.

This command can exist or not, and it begins straight from the called NRI or the

password. It depends on the PAD we connect with, and it can be case sensitive. For

example: CON

In case there is a public PAD, we don’t have to enter any value for this parameter.



PROTOCOL DELIMITER

Character, or sequence of characters, that begin to identify the protocol in the X25 call

packet.

If our PAD has insertion option for the protocol identifier in the X25 call packet, we will

indicate it here.

For example: #

USER’S DATA DELIMITER

Character, or sequence of characters, that begin to identify the user’s data in the X25

call packet. For example: *

If the PAD is public (7-bits), we don’t have to enter any value for this parameter.

SERVICE REQUEST

Depending on which PAD we are going to connect, we will need to send its activation

sequence.

8-bit PAD: it can be no necessary

7-bit PAD: ..

I.U.R.

Identificación de Usuario de Red (Network User Identification).

This facility is established by subscription, and it allows the IBERPAC network to identify

the DTE that establish communications from the RTC through general access doors. This

identification can be unnecessary.

If the PAD is public, it has the following format:

NXXXX/YYYYYY-

being:

N character that identifies the I.U.R. facility.

XXXX user identificator, provided by Telefónica.

/ delimiter of I.U.R. fields

YYYYYY user key, provided by the subscriber.

- indicator of facilities field end.

TELEPHONE NUMBER

PAD telephone number.

SERIAL DEVICE

Name of the device to which the modem is connected.

Example: "/dev/cua/a".

SPEED

Transmission speed of the modem, in baud. The following values are valid: 300, 600,

1200, 2400, 4800, 9600, 14400, 19200, 28800, 38400 and 57600.

Si se introduce otro valor numérico toma el valor 2400.

DISCONNECTION TIME OUT

Disconnection time out.

Time during which the RTC connection is kep up after releasing the CVC.

The unit time is the second.

INITIAL COMMAND

Modem initialization command.

For example: &C1&D2X4



DIAL (T/P)

Modem dialling command.

T Rings (multifrequency).

P Pulses.

In SNA networks (only available for SO AIX), the parameters we need to set are the

following:

CONNECTION PROFILE NAME

Is the name of the SNA profile corresponding to the LU6.2 connection we have set for

the remote node.

REMOTE TP NAME

Is the name of the transaction program the remote node uses to manage the LU6.2

connection.

In FTP transmissions, the user must specify:

HOST

Is the remote node IP address or the name of the host we want to connect.

USER

Is the name of the FTP user we want to use to connect.

PASSWORD

Is the password of the FTP user we want to use to connect.



The specific parameters for the SWIFT network (only available for SunOS) are:

LOCAL DN

Distinguished Name (DN) of the entity originating the sending. Is the name that

identifies uniquely our node in the SWIFT network.

REMOTE DN

Distinguished Name (DN) of the receiving entity. Is the name that identifies uniquely the

remote node in the SWIFT network.

SERVICE

Name that identifies the business area of the exchanged data. It is a string agreed by

SWIFT and the service provider.

REQUEST TYPE

It complements the service name in some cases.

STORE-And-FORWARD

We have to check whether it is a Swift transmission in Store-And-Forward mode. When

the transmission is made in SnF mode, we can only start emissions from EDITRAN/P. The

reception will be always started by the Swift server.

SIGNED

NON-REPUDIATION

Both flags determine the security level required for the Swift transmission.

ACK

If we wish the remote Swift server confirmed us the delivery of the sent file, we will

have to fill the field with S. The files arriving to EDITRAN are confirmed if the remote

node asks for it.

ACK REQUEST TYPE

Request Type where we want the ack file to be sent.



Once the network values are set, appears the screen in which we have to specify the

session parameters that determine the main features of the transmission.

SERVER/CLIENT (OPER)

Operation mode:

S Neither emissions nor receptions can be requested (server).

C Both emissions and receptions can be requested (client).

CRC (S/N)

S For every transmitted message, a cyclic redundance code will be generated; the CRC

of every received message will be validated.

N The CRC is not calculated for outgoing messages, and is not validated for incoming

messages, except when the data come from PAD.

COMPRESSION (S/N/V)

S Compressed data transmission.

N Data are transmitted in the original format of the application.

V Data are transmitted compressed or in the original format, depending on the best

result.

ASCII/EBCDIC (A/E)

A The remote node uses ASCII alphabet (UNIX, VAX, DOS, OS/2 environments).

E The remote node uses EBCDIC alphabet (CICS, IMS, AS/400 environments).

START TIME (HH:MM:SS)

It specifies the time of the date from which it will be possible to start the transmission.

It will be expressed in hours (HH), minutes (MM) and seconds (SS).

END TIME (HH:MM:SS)

It specifies the hour of the day until we can start the transmission. It is expressed in

hours (HH), minutes (MM) and seconds (SS).

BUFFER LENGHT

Length of the buffer file logs. Values from 13 to 9999 bytes are allowed (with HOST

environments only values 252 or 4050 are allowed).



EMISSION BURST

Number of logs emitted before receiving the confirmation from the remode node.

SINCHRONIZATION TIME OUT (Seconds)

Is the lapse of time, in seconds, during which EDITRAN waits to receive from the remote

node a synchronization message to confirm the sending of a block of data (burst). If this

time is finished and the answer is not received, the data send is repeated, maximum to

meet the number of retries.

APPLICATION SYNCHRONISM (S/N)

S Application synchronism control, generated by the EDITRAN/G V2.1 applications that

require it.

N The application synchronism is not performed.

TEMPORARY DIRECTORY

Root directory for temporary files created by EDITRAN during the transmission (buffers,

list with the last issued/received files, etc.). All the sessions can have the same

directory, since from it is created automatically the tree <local>/<remoto>/. If we don’t specify a value, the system will take as root the directory where EDITRAN is

installed.

PROCEDURES NAME

EMISSION PROCESSES

Name of the interface that controls the emission process.

RECEPTION PROCESSES

Name of the interface that controls the reception process.

Then, we have to set the values that will determine the safety applied in the data

transmission:

The parameters that appear in the screen are:

CRYPTOGRAPHY (S/N)

S If you wish EDITRAN/P cryptography.

N If you don’t want to use EDITRAN/P cryptography.

CRYPTOGRAPHIC VERSION



This field is mandatory if cryptography is activated.

2.2 For the security subsystem of the EDITRAN/P 2.2 version.

3.0 When the keys exchange is performed externally to EDITRAN/P.

KEY CHANGE V2.2 (S/N)

Selector to easily change the cryptographic key in the connection preamble. It only

affects when the cryptography version is 2.2.

S Key change activated.

N Key change inhibited.

KEY MANAGEMENT V3.0

When this facility is selected in cryptography 3.0 versions, the EDITRAN/GC module will

be responsable for supplying the labels corresponding to the active keys for the

subsystems referred to in the parameters CLAVE LOCAL (LOCAL KEY) and CLAVE

REMOTA (REMOTE KEY).

S Labels supplied by EDITRAN/GC.

N Labels supplied by the user.

CONFIDENTIALITY ALGORITHM

Algorithm we must use to cypher data. We will leave it blank to issue without cyphering.

DES DES cyphering with simple key.

TD2 DES cyphering with double key.

TD3 DES cyphering with triple key.

AUTHENTICATION ALGORITHM

Algorithm we must use to protect the session key and the exchanged data, to

authentify the extreme nodes. Is mandatory if a confidentiality algorithm exists.

DES if you wish to authenticate the extreme nodes with DES algorithm (valid with

cryptography versions 2.2 and 3.0).

RSA if you wish to authenticate the extreme nodes with RSA algorithm (valid only for

3.0 version).

PKI if you wish to authenticate the extreme node with digital certificates (valid only

for 3.0 version).

SNC if you wish to authenticate the extreme nodes with the SNCE keys. This option is

available only for HP-UX.

LOCAL KEY

Label of the DES auxiliary key, the RSA private key or the alias of a PKI certificate. It is

only necessary for the cryptography version 3.0.

REMOTE KEY

Label of the DES auxiliary key, the RSA public key of the remote node or the DN of the

PKI remote certificate. It is only necessary for the cryptography version 3.0.

PIN

PIN to access the private key associated to a certificate. It is needed only when the

cryptography version is 3.0 and when there is PKI authentication.



4. EDITRAN/P MANAGER (WINDOWS)

If we click on the menu option EDITRAN P, the EDITRAN/P manager menu will appear.

If this is the first time we boot EDITRAN, we will have to enter the data of the local

environment (see chapter 4.5.1 Local environment) and then boot EDITRAN.

4.1. DESCRIPTION OF THE USER INTERFACE

4.1.1. SCREENS

In the EDITRAN WINDOWS screen, we can distinguish three areas:

(1) Menus

In the menu area we can choose the different options to manage EDITRAN:

Starting and stopping EDITRAN, reports, system administration…

(2) Toolbar

In this area appear different icons indicating actions equivalent to the ones in the

menus; if we place the mouse hover on any icon, we will see the related

information about its action in the bottom of the screen.

(3) Information

In this area we can see the information that EDITRAN sends to the operator:

Session.

Emission and reception status.

Emission and reception counters.

Information text or messages from the remote operator.



4.1.2. HELP

EDITRAN WINDOWS has a help system available. In this way, when we click on F1 or on the

button Temas de ayuda (Help topics), a window with the help text will display.

4.1.3. ABOUT

It indicates the EDITRAN version and the date of compilation, apart from two informative

buttons: licenses and distribution.

4.2. STARTING AND STOPPING EDITRAN/P

To start and stop EDITRAN we must select the option Archivo (File) from the menu, and

then choose the option Arrancar EDItran (Boot Editran) or Parar EDItran (Stop EDItran).

This icon from the toolbar is equivalent to starting and stopping EDITRAN using menus:

Placing the hover on the traffic light and clicking on it, we will start EDITRAN/P and

EDITRAN/G, and the light will remain green.

Placing the hover on the traffic light and clicking on it when it is green, we will stop

EDITRAN/P and EDITRAN/G, and the light will remain red:



4.3. EDITRAN/P OPERATOR

To manage the Exchange sessions, we will have to select the tab EDItran/P from the main

menu. The following options will be displayed:

4.3.1. Connection

To manually establish the physical connection with a remote EDITRAN, in order to start the

transmission process, we must have selected previously a specific session (to do this, we have

to place the mouse hover on the chosen option and click on it). Then, we have to choose the

menu option Conexión (Connection). The request is not allowed when the EDITRAN operation

mode is Server.

This request will be automatically performed when we ask for an emission or reception

request, if we specify the value S in the parameter LLAMADA AUTOMATICA (AUTOMATIC CALL) of the session profile.

In the information area will appear indications about the request result (association

established or not).

If we click on this option of the toolbar, the system will perform the same action as if we

used the menu:

4.3.2. Release

This is used to manually release the existing connection for a specific session.

If we click on this option in the toolbar, we will perform the same action as if we used the

menu:

4.3.3. Emission

To start the local emission of a file or several files, we will have to select the option

Emisión (Emission).

The request is not allowed when the local EDITRAN operation mode is Server.

If we click on this option in the toolbar, we will perform the same action as if we used the

menu:



4.3.4. End of emission

To ask for a forced end request of the local emission (emission interruption) we must select

the option Fin de Emisión (End of emission).


If we click on this option from the toolbar, we will perform the same action as if we used

the menu:

4.3.5. Reception

This option is used to start the reception of a file or files that must be emitted by the

remote node.



the menu:

4.3.6. End of reception

To ask for a forced end request of the local reception (reception interruption) we must

select the option Fin de Recepción (End of reception).



the menu:

4.3.7. Message for the remote node

It is used to send a text message to the remote node. Is necessary to have a connection

with the remote EDITRAN node that will be the receiver of the message from the operator.

The following screen will appear, and we on it will have to write the text to be sent:


the menu:



4.4. FILE MONITORING

4.4.1. File local monitoring

To obtain information about the control log of the local emission or reception buffer file,

we must select the option Consulta local de ficheros (File local monitoring).


We must select Tipo de fichero (Emisión ó Recepción) / File type (Emission or Reception)

and then choose the session.

After that we have to fill the different fields with the data corresponding to the control log

local emission or reception buffer file for the specified session.

If we monitor the local emission file (introducing Emisión/Emission in the field Tipo de

fichero/File type), we will obtain the following information:



4.4.2. Remote monitoring of emission files

To monitor the remote emission file we will have to select the option Consulta remota de

ficheros (File remote monitoring) and then choose Emisión (Emission). The local EDITRAN

program will send the query message to the remote node, and the local node will remain

waiting for the answer from the remote one. This answer will be displayed through the next

screen. Is necessary to have previously established a connection between both extreme

nodes.

4.4.3. Remote monitoring of reception files

To monitor the remote reception file, we will need to select the option Consulta remota de

ficheros (File remote monitoring) and then choose Recepción (Reception). The local EDITRAN

program will send the monitoring message to the remote node, and the local node will remain

waiting for the answer from the remote one. This answer will be displayed through the next

screen. Is necessary to have previously established a connection between both extreme

nodes.

4.4.4. Log monitoring

It displays all the informative messages that EDITRAN sent to the operator.

To monitor these logs, we will need to select the option Consulta del log (Log monitoring).


We will select the session, the date and the time, and then Selección OK (Selection OK).



In case it is a general monitoring, we will have to select <todas> (<all>) in the combo

Sesión (Session).

It will display the messages from the defined date to the current date of the query.

If we define 00:00:00 in Hora (Time) it will show all the messages, regardless of the time.

The file editranp.log is treated cyclically.



4.5. EDITRAN/P ADMINISTRATOR

To access the EDITRAN administration menu we have to select the option Administrador

(Administrator) from the EDITRAN/P menu.

The following options will be displayed:

4.5.1. Local environment

If we select this option, the following screen will appear:



We have to fill the requested data:

Local environment code

We will write the identification number of the EDITRAN user entity. With this number,

the entity will be recognized by all the interconnected entities.

Name

We will write the description of the local environment. This field is only informative.

Maximum number of sessions

It can be specified the maximum number of Exchange sessions that can be concurrently

executed.

For example, in the EDITRAN X.25 version, the maximum value that can be taken should

be defined with the number of logical channels set for the X.25 card.

TCP/IP Connection TimeOut (seconds)

Is the maximum timeout since the connection from a remote socket is accepted until the

system exchanges the session data that definitely establish a TCP connection in

EDITRAN/P. This timeout prevents other applications from connecting indefinitely to the

port used by EDITRAN. If we don’t want to enable this timeout, we must select 0.

LOCAL PORTS (only X.25 version)

We must specify here the port of the EICON board where the X.25 address is connected.

We can specify different x25 boards and ports from the same server.

X.25 ADDRESS (only X.25 version)

We will write the IBERPAC network number of the local user entity.

In X.25 connections we can enter up to 3 NRI’s with variable length, with a maximum of

15 digits.

IP ADDRESS

The private IP address of the own machine in a TCP/IP network admits up to 3 different

addresses with 3 listening ports for each adress.

If we define 0.0.0.0 EDITRAN, it will listen from all the machine IP’s.



Installations licensed for SWIFT network, the sytem requires other parameters

corresponding to own concepts for this network. Is advisable to contact the Swift Alliance Gateway (SAG) product administrator to know the values that these fields must have.

SWIFT security context

We will indicate the “usuario” (user) and “password” corresponding to the certificate that

has been requested to SWIFT, with the needed permission to use the FileAct

functionality.

Store-And-Forward context

Recursos necesarios cuando se accede a servicios Swift SnF. En este modo de entrega,

los ficheros quedan temporalmente en un servidor Swift almacenados hasta que la

entidad los recoge.

The following screen is an example of the interface that would be displayed in an

installation unlicensed for x25 and licensed for swift.



4.5.2. Sessions management

To connect and to perform emissions and/or receptions with a remote EDITRAN, we must

specify the parameters that describe the session profile. Is essential to have previously

registered the local environment (see 4.5.1 Local environment).

We will register as many sessions as different connections we want to establish.

Then we must select the option Gestión de sesiones (Sessions management) from the

menu Administrador (Administrator).

4.5.2.1. General data

We will have to specify the Datos Generales (General data).

If we click on Defecto (Default), the default fileds will be filled.

If we click on the button Borrar (Delete) we will remove the whole EDITRAN session.

Session

Session identification.

Version

Version of the remote EDITRAN system (for example: 5.1, 5.0, 4.1, …)

Local

Identification code of the local environment.

Local name

Designation of the local environment associated to the session. It is just an informative

field.

Remote

Identification code of the remote center.

Remote name

Designation of the remote center associated to the session. It is justa n informative

field.



Application

Identification code of the user application for the transmission service of the EDITRAN

system.

Application name

Designation of the user application. It is just an informative field.

Access ID

A numeric value from 0 to 9, needed for X25 connections, that along with the remote

code and the application, identifies the session correspondant to the call.

Main protocole (X.25 ,TCP/IP, X.28, SWIFT)

Type of connection through which we will communicate mainly with the remote

EDITRAN system. The possible values are:

X.25: public (IBERPAC) or private network. Synchronous transmission in packet mode.

TCP/IP: TCP/IP network.

X.28: PAD-X.28. Asynchronous connection to a packet dis/assembler through 7/8 bits

commands. Asynchronous transmission in character mode.

Network Swift: SWIFT. File transmission through the FileAct service It is admitted

only as main network.

Backup protocol (X.25 ,TCP/IP, X.28)

Protocol that will be used in case the main protocol doesn’t make the connection with

the remote node. Its use is optional and limited to the available protocols.

It is not allowed to specify as a backup network the same that is being used as main

one. With main SWIFT protocol is not allowed to define backup.

By each protocol it will be necessary to fill the corresponding tab: TCP/IP, X.25 and X.28

Modem.



4.5.2.2. TCP/IP tab

The TCP/IP tab contains the following fields:

Remote IP address

They are the IP or DNS addresses and TCP ports of the remote machine we want to

connect. We can define up to 6 addresseses.

Validate remote IP address

If it is activated, the system will validate the IP addresses of the remote machine from

which we are waiting for receiving a connection. In case the IP doesn’t match, the

incoming connection is rejected.

Save rotations

If we select this option and if we have more than one remote address, the order will be

altered and the system will place in the first place the IP we have been able to connect.

Use EDITRAN proxy

It indicates whether the session will use EDITRAN/PX to reach out over TCP/IP.

Proxy IP address

It indicates the IP address or the name of the EDITRAN/PX server to connect.

Proxy port

EDITRAN/PX listening TCP port.



4.5.2.3. X25 tab

In case we choose X.25, the following screen will appear:

LOCAL NRI's

They are the IBERPAC network numbers (NRI) that the local equipment owns.

We can specify up to 3 different numbers. In case we use EICON boards, we can specify

the motherboard port along with the local NRI.

REMOTE NRI's

They are the network numbers or network addresses (NRI) owned by the EDITRAN

remote extreme we call.

We can specify up to 6 different numbers.

In case it is necessary to retry the call, the system will do it by each local NRI, with all

the given remote nodes.

VALIDATE NRI´S

If we activate it, the incoming NRIs will be validated and compared to the remote NRI’s.

In case they don’t match, the connection will be rejected with 0x0D diagnosis.

SAVE ROTATIONS

Sí (Yes) It saves in the first position the NRI’s with which we established the

connection. The purpose is to avoid calls from being retried for further transmissions.

No The profile is unchanged.

Method of payment

Local The local extreme always pays for the transmission.

Remote The remote extreme always pays for the transmission.

Indistinct The caller extreme node pays.

Collect calls

Sí (Yes) Collect calls are accepted.

No Collect calls are not accepted.



Protocol ID

Protocol identificator. It is part of the user data from the X.25 calling packet. It must

match the one from the remote session. Range = "00-FF". Default value = "C0".

Accepting calls from PAD

It controls the access when the remote calls come from PAD.

Sí (Yes) Calls are accepted. In this case, remote NRI’s will be never validated.

No Calls are rejected.

4.5.2.4. X28 tab

In case we choose X.28, the following screen will appear:

REMOTE NRIs

They are the network numbers or the network addresses (NRI) owned by the EDITRAN

remote node we call.

We can specify up to 6 different numbers.

BITS (7/8)

Number of data bits within the carácter exchange between the asynchronous terminal

and the PAD.

7-bit PAD (the most common)

8-bit PAD

SERVICE REQUEST

Depending on the PAD we are going to connect, we will have to send its activation

sequence.

Private PAD: It might be not necessary

Public PAD: It will be: ..

CONNECTION COMMAND

Character, or sequence of characters, from the PAD connection command.



This command may not exist, then the session will begin straight from the called NRI or

the password. It depends on the PAD we connect, and it can be case sensitive. For

example: CON.

In case we use a public PAD (7-bits), we don’t have to enter any value for this parameter.

USER DATA DELIMITER

Character, or sequence of characters, from the beggining of the user data in the X25 call

packet. For example: *

If the PAD is public, we don’t need to enter any value for this parameter.

I.U.R.

Identificación de Usuario de Red (Network User Identification).

This facility is stablished by subscription, and it allows the IBERPAC network to identify

the DTE which stablish communications from the RTC through the main doors access.

This identification can be unnecessary.

If the PAD is public, it has the following format:

NXXXX/YYYYYY-

being:

N Character identifyind the I.U.R. facility.

XXXX User identificator, provided by Telefónica.

/ I.U.R. fields delimiter.

YYYYYY User key, provided by the subscriber.

- Indicator of facilities field end.

PROTOCOL DELIMITER

Character, or sequence of characters, for the beggining of the protocol identification in

the X25 calling packet.

If our PAD has the option to insert the protocol identificator in the X25 calling packet,

we will indicate it here.

For example: #

This is not applicable if the PAD is public.

PHONE NUMBER

PAD phone number for X.28, or number of the remote installation for RTC (it usually is

1247).

SPEED

Transmission speed of the modem, in baud. The values 300, 600, 1200,2400, 4800,

9600,14400, 19200, 28800, 38400, and 57600 are valid.

FIRST COMMAN

Command to initializate the modem.

For example: &C1&D2X4

COMMUNICATIONS PORT

Name of the device to which the modem is connected.

Example: COM1, COM2, COM3, COM4, etc.

If it is USB, we will have to check the associated COM in the modem device options.

DISCONNECTION TIMEOUT

Is the duration of the RTC connection after releasing the CVC.

The time unit is the second.

DIAL (T/P)

Modem dialling command.

T Tones (multifrequency).



P Pulses.

4.5.2.5. SWIFT tab

In installations licensed for local SWIFT network, and if we select Swift as main protocol,

we will have to fill the tab Swift.

Local DN

Distinguished Name (DN) of the entity that origins the sending. It is the name that

identifies uniquely our node in the SWIFT network.

Remote DN

Distinguished Name (DN) of the receiver entity. It is the name that identifies uniquely

the remote node in the SWIFT network.

Service Name

Name that identifies the business scope of the exchanged data. It is a string agreed

between SWIFT and the service provider.

Request Type

It complements the service name in some cases.

SwFileInfo

File information, that will be included in the corresponding field of the FileAct message.

SwTransferInfo

Information about the transmission, that will be included in the corresponding field of

the FileAct message.

Store-And-Forward

We will have to check whether it is a Swift transmission in Store-And-Forward mode.

When transmitting in this mode, from EDITRAN/P only emissions can be started. The

reception will be always started by the Swift server.

Signed

Non-repudation



Both flags determine the security level required for the Swift transmission.

Ask for Ack

If we wish the Swift server confirmed us the delivery of the sent file, we will check this

option. Files reaching EDITRAN are confirmed, as long as the remote node ask for it.

Ack Request Type

Request Type where we want the file Ack to be sent.

4.5.2.6. Options tab

We will have to specify the tab Opciones (Options).

If we click on the button Defecto (Default), the default fields will be filled.

If we click on the button Borrar (Delete), the whole session will be removed.

Number of records by emission block

Length of the transmission burst (number of records emitted before receiving a

confirmation from the remote node).

We recommend defining the following parameters for each type of connection:

X28= 010

X25= 025

TCP= 100

Buffer length

Length of the buffer files logs. Values from 13 to 9999 bytes are allowed (with AS400

environments only 0252 or 4050 values are allowed).

Calling extreme node

Local: Only the local extreme node can call.

Remoto (Remote): Only the remote node can call.

Indistinto (Indistinct): Either extreme can call.

Traffic direction

Emisión (Emission): We can only emit in this session.



Recepción (Reception): We can only receive in this session.

Emisión/Recepción (Emission/Reception): We can emit and receive simultaneously.

Automatic call

Si (Yes) The session will be automatically established when we request for the

emission or the reception to start.

No We have to establish a connection before requesting for the emission/reception.

CRC

Si (Yes) For each transmitted message, a cyclic redundance code will be generated.

The CRC of each message will be validated.

No The CRC won’t be calculated for outcoming messages and won’t be validated for

incoming messages.

Automatic disconnection

Si (Yes) A disconnection request is automatically generated when ending an emission or

a reception.

No The disconnection is not generated automatically.

Operation mode

Servidor (Server) Emissions or receptions can’t be requested (server). Only remote

requests will be accepted.

Cliente (Client) Both emissions and receptions can be requested (client).

Charset

ASCII The remote node uses ASCII alphabet (UNIX and Windows environments).

EBCDIC The remote node uses EBCDIC alphabet (CICS, IMS, AS/400 environments).

Zipping

Si (Yes) Zipping protocol data packets.

No Transmission without zipping.

Variable Transmitting zipped files only when the size of the resulting data packet is

smaller than the original one.

Hora de inicio / Start time (HH:MM:SS)

Specifies the hour of the limit day from which the transmission can start, in hours (HH),

minutes (MM) and seconds (SS).

Hora de finalización / End time (HH:MM:SS)

Specifies the hour of the limit day to which the transmission can start, in hours (HH),

minutes (MM) and seconds (SS).

Time-out (Seconds)

It is the lapse of time, in seconds, during which EDITRAN waits to receive from the

remote node an answering message to a control message previously sent.

If the TIME-OUT ends and we didn’t get an answer, the same request will be resent, and

a new timeout will start. This is also equivalent for the connection requests.

Synchronization Time-out (Seconds)

It is the lapse of time, in seconds, during which EDITRAN waits to receive from the

remote node a synchronization message regarding the sending of the data block (burst).

If this time ends and we didn’t get an answer, the message will be resent, maximum to

meet the number of retries.

Maximum number of retries

Is the maximum number of times the previous mentioned TIME-OUT is repeated.

Application synchronism



Sí (Con totales) / Yes (With totals) Application synchronism control, generated by the

V2.1 applications that require it.

Sí (Sin totales) / Yes (Without totals) Obsolete option, provided for compatibility with

old versions (tending to disappear), for the I.G.A. V1.x applications that require an

exchanged totals control during the transmission process (e.g., when finishing the

receipts transmitted in the same file for each bank, according to standard CSB 19 with

old format).

No The application synchronism is not performed.

EDITRAN temporary folder

Root folder for temporary files, created by EDITRAN during the transmission (buffers, list

of the last emitted/received files, etc.). By default, the system creates automatically the

tree .\<local>\<remoto>\ in the chosen folder.

If we don’t specify a value, the sytem takes as root the folder where EDITRAN is

installed.

Emission processes

Name of the interface that controls the emission process.

Reception processes

Name of the interface that controls the reception process.

4.5.2.7. Cryptography tab

We must specify the Criptografía / Cryptography for the session.

Criptografía (Cryptography)

Sí (Yes) If we wish EDITRAN/P cryptography.

No If we don’t wish to use the EDITRAN/P cryptography.

Versión de criptografía (Cryptography version)

This field is mandatory if cryptography is activated.

2.2 For the security subsystem of the EDITRAN/P 2.2 version.

3.0 When the key Exchange is performed externally to EDITRAN/P.



Cambio de clave V2.2 (V2.2 key change)

Selector to easily change the chryptographic key in the connection preamble.

Sí (Yes) Key change activated.

No Key change inhibited.

Intercambio de Claves V3.0 (V3.0 key exchange)

When this facility is selected in 3.0 cryptography versions, the EDITRAN/GC module will

be the one to provide the labels corresponding to the active keys for the subsystems

indicated in the parameters CLAVE LOCAL (LOCAL KEY) and CLAVE REMOTA (REMOTE

KEY).

Algoritmo de confidencialidad (Confidentiality algorithm)

Algorithm to be used to cypher data.

We will leave it blank if we don’t want to cypher data.

DES DES cyphering with simple key.

TD2 DES cyphering with double key.

TD3 DES cyphering with triple key.

Algoritmo de autenticación (Authentication algorithm)

Algorithm to be used to cypher keys, mandatory if there is a confidentiality algorithm.

DES if you wish to authenticate the extreme nodes (valid for versions 2.2 and 3.0).

RSA if you wish to authenticate the extreme nodes (valid for version 3.0).

PKI if you wish to authenticate the extreme nodes (valid for version 3.0). If we choose

this field, we will need to fill the key PIN.

Clave local (Local key)

Label of the DES auxiliary key, the RSA private key or the alias of a PKI certificate. Is

only necessary for the 3.0 cryptography version.

Clave remota (Remote key)

Label of the DES auxiliary key, the RSA remote public key or the DN of the PKI remote

certificate. Is only necessary for the 3.0 cryptography version.

PIN

PIN to access the private key associated to a certificate. It only appears when the

cryptography version is 3.0 and there is PKI authentication.



5. ANNEXES

5.1. EDITRAN COMPONENTS

5.1.1. CURRENT SCHEME

editrang

editranp

editra

nf

ftp

ediapp

c

edix28

editcp

menup

menug

igacmd

(API)

editra

ntr

edix25



5.2. DISTRIBUTION

5.2.1. Components

As we saw in the previous image, we can distinguish three types of components:

P and G servers.

Clients.

Communications.

All the components use the TCP communication to talk to each other, regardless of

whether they are in the same machine or not.

Components can talk to each other, regardless of the platform where they are executed.

5.2.2. EDITRAN/P and EDITRAN/G servers

Their functionalities and associated files are the following:

User scripts

Converters + source/destination folders

Presentations and sessions profiles

Cryptography, zipping, transformation, etc.

Log/output/trace/alarms

User files, CSB and buffers

editra

ng

editra

np

ediapp

c

edix28

editcp

menup

menug

igacmd

(API)

edix25

User

files,profi

les,log,lic

ense,buffer

s,cryptogra

phy

TCP

NET



5.2.3. Clients

Accessing server – operation methods.

Accessing files associated to servers - monitoring.

Accessing profiles - administration.

5.2.4. Communications servers

They allow EDITRAN/P server to access the supported networks.

They Access the EDITRAN/P local settings.

5.3. COMMANDS

5.3.1. EDItran

Description

Is a program which boots and stops EDITRAN system.

Syntax

The syntax of the command is:

EDItran [–t] [-f] start | stop | status [–s]

-t Boots EDITRAN with a trace

-f Ignores a different EDITRAN already booted

-s Only for Windows. We will use this option if we don’t want to display the window

with the result of the command.

start Boots EDITRAN system

stop Stops EDITRAN system

status Obtains the EDITRAN system status

5.3.2. editranp

Is the main process of the EDITRAN system. Is responsible for dialoguing with the different

communication processes, and also with EDITRAN/G. It is launched in the background when

we boot the EDITRAN system (EDIstart/EDItran start).

5.3.3. edix25

Communication process when the protocol to be used for the connection is X.25.

5.3.4. editcp

Communication process when the protocol to be used for the connection is TCP/IP.

5.3.5. edix28

Communication process when the protocol to be used for the connection is X28.

5.3.6. editransw

Communication process when the network used is Switf.



5.3.7. makelog

Description

It creates an event file, called editran.log, which will contain a summary of the operations

performed through EDITRAN.

Syntax


makelog –n N

where N is the maximum number of entries (number of events) that we wish to keep in the

file.

Example

We wish to create an event file, editran.log, with a capacity of 500 different entries.

We must execute the command:

makelog –n 500

In case we use the system with a large number of concurrent sessions, we recommend to

use 500 entries.

5.3.8. menup

Description

It allows straight access to the EDITRAN manager menu.

5.3.9. menucmd

Description

It establishes a communication mechanism between user applications or programs and

EDITRAN/P, allowing to invoke operations unattendedly and authomatically.

Syntax


menucmd s sesion x

Where s is the signal sent to request EDITRAN an operation, sesión is the session and x

other options, depending on the type of operation or requested signal to EDITRAN.



Specifically, the exact syntax of the command, depending on the value of s, is the

following:

menucmd {E00|E11|ECP|ECR|EDP|EDR|EPE|EPR|EOI} <sesion#>

menucmd EOP <sesion#> <texto>

menucmd {A1R|A2R|A3R|A4R} <sesion#> <S|N> <retcode#>

The possible signals are:

E00 asks EDITRAN for a connection request.

E11 asks EDITRAN for a release request.

ECP asks EDITRAN for an emission start.

ECR asks EDITRAN for a reception start.

EDP asks EDITRAN for an emission end.

EDR asks EDITRAN for a reception end.

EPE asks EDITRAN for a remote monitoring of the emission file.

EPR asks EDITRAN for a remote monitoring of the reception file.

EOI asks EDITRAN for a monitoring of a session status.

EOP asks EDITRAN for the sending of a message to the remote operator.

A1R with S qualificator, it originates batch request of emission start.

A1R with N qualificator, it originates an emission previously to an emission correctly ended.

A2R with S qualificator, it originates a batch request of reception start.

A2R with N qualificator, it originates a reception previously to a reception correctly ended.

A3R sends EDITRAN an end after emission.

A4R sends EDITRAN an end after reception.

Example

We wish that at the end of the reception of a certain session, an emission of the INDRA-

TEST session will be generated.

For this, the file of automatism associated to the end of the reception will include the

following call:

menucmd ECP INDRA-TEST

When EDITRAN invoques the I.G.A. user script associated to the end of reception, menucmd

will send will send, in turn, a signal to EDITRAN indicating the the user has request an

emission start operation for INDRA-TEST.

5.3.10. copycfg

Utility to copy EDITRAN profiles from another one used as a template.

Syntax


Use: copycfg -s ses_origen [-d ses_destino] [-n] [-r cod_remoto] [-p | -a]

Being:

-n : number of sessions to be created.

-s : source session.

-d : target session.

-r : remote code of the target.

-p : only EDItran/P sessions copy.

-a : creates EDItran/G applications.



Description

This command allows creating EDITRAN profiles from a session used as a template. The

source session is given in the option –s. By default, the EDITRAN/P is created, as well as its

corresponding presentation in EDITRAN/G. But this behavior can be changed using the option

–p if we want to create only the session profiles.

The created profiles will depend on the chosen option:

Option –n <n>: We create <n> sessiones. These sessions are named as the original ones,

adding an index. For example, if we start from PRUEBA and we want to generate 5 more, we

will create from PRUEBA-1 up to PRUEBA-5.

Option –d: In this case, the user decides the name for the created session, but this option

is incompatible with the previous one.

Option –r: By default, the created sessions are generated with the same local and remote

code than the original. With this option, the user is allowed to change the remote code of the

new profile.

Example

To duplicate the session INDRA-TEST for a different remote node, renaming the new one

as EDITRAN-TEST, execute:

>copycfg –s INDRA-TEST –d EDITRAN-TEST –r 000001230

To created 10 sessions from PRUEBA, execute:

>copycfg –s PRUEBA –n 10

5.3.11. printcfg

Description

Utility to print EDITRAN sessions.

Syntax

Use : printcfg [ -lgrapsv ]

Being :

-l : Local EDItran/G.

-g : Presentations EDItran/G.

-r : Remote nodes EDItran/G.

-a : Applications EDItran/G.

-p : Local EDItran/P.

-s : Sessions EDItran/P.(default)

-v : Prints headers.

Example

SESION LOCAL REMOTO APLIC DIR LOCAL DIR REMOTA

========================= ========= ========= ====== =============== ================

INDRA-TEST W00005100 000099990 PRUEBA TCP editran.indra.es

5.3.12. resetkey

Description

Restarts the encrypted exchange keys of a determined session.



It must be used with caution, as it leaves the keys in a different status than the original

one. Is essential to perform the same operation in the remote node, to make possible the

synchronization during the keys exchange.

It has to be executed only if this is the first time we use the keys, or if we lost the keys of

the last exchange in the profiles file.

Syntax


resetkey [session]

where session is the EDITRAN/P session. We have to write it with capital letters, and if

there is a blank, it will be with double quotation marks: “

Example

In an installation we wish to assign the TEST-INDRA session key to an initial value.

We have to execute the command:

resetkey TEST-INDRA

5.3.13. importkey

Description

The file ckds.des keeps the master key and auxiliary keys DES in the EDITRAN system. In

the version 5.02, the format has changed to allow storing simple and double keys. For this, in

some cases it can be necessary to import keys from previous versions.

For safety, to export the keys, the user must know the value of the HMK he is keeping. And

he also must provide the two first octets in hexadecimal format, as a password to access the

file. It can be provided as a command argument, but if it is not filled, the user will be asked for

it.

Syntax


Use: importkey [ -s ] [-k<k>] -f<f> [--] [etiquetas]

-- : End of options. The rest of arguments are labels

-s : The soucer file contains simple keys

-k<k> : Key to access the file (HMK)

-f<f> : File that stores the keys to be exported

etiquetas: Labels of the keys to be imported

If no label is provided, the command will incorporate all the keys of the source file, whose

label is not SI0000000000XX.

If the label of the key to be imported already exists in the target file, the key will be

updated with the value of the old one.

Example

To incorporate the auxiliary key used by EDITRAN for session with cryptography 2.2, we

must execute the command:

> importkey –s –fc:\editran.510\ckds.des SI000000000016



To incorporate the auxiliary user keys providing the access password as an argument, we

will execute:

> importkey –s –fckds.des.510 –kA1A3

5.3.14. printlog

Description

Utility to print the EDITRAN log.

Syntax

printlog

Command options:

-P EDItran/P log

-G EDItran/G log

-s session

-f date DDMMAAAA

-h time HHMMSS

All the parameters are optional

5.3.15. EDITRAN/GT transmissions manager (WINDOWS)

Currently exists a tasks planner (EDITRAN/GT).

To use this module is necessary a special license including the authorization.

For further information, see the specific manual for EDITRAN/GT.

5.3.16. NL FILTER

Description

The filter nl is used to convert lines from a system to another. This filter just reads and

writes lines. The utility of the filter lies in the physical difference between one systems and

anothers while representing text lines.

Usually, a file containing lines is structured in one of two ways:

With fixed length records (a fixed number of characters are kept for each line; for example,

100 characters for each line).

With variable length records (end of line delimiters are used to separate lines). These, in

turn, have different separators in each system. The filter recognizes the UNIX ones.

To use the filter we just need to tell it which is the source structure (for example fixed

records with 50 characters, or variable records with UNIX type delimitator) and the structure

we want to obtain. The filter will change the file structure in order to obtain the desired

structure, with the same content in each line.

Syntax

Use: nl [ -<#> | -v ] -i<f> -o<f> [--] [ficheros]

-- : End of options. The rest of arguments are files

-<#>: # length records (fixed) without delimiters (E.g.: -80)

-v : Variable length records (by default)

-i<f>: Input format (E.g.: -id)

-o<f>: Output format (E.g.: -on)

<f> can be: u (UNIX), d (MSDOS), n (no delimiter)

files: files to be translated (stdin->stdout by default)



To indicate the type of record we will be using (fixed or variable), we will use the following

options:

option -N (where N is a number, e.g. 80): fixed records with N characters.

option -v: variable records.

To indicate the end of line delimitator used in the input file, we use the option -iX (where

X is 'n', 'u' or 'd').

If X is n, the filter expects that there is no end of line delimitator in the input file (in this

case, we must have used -N to indicate the length of the record, as they must be fixed length

records).

If X is u, the filter expects that there is a '\n' delimitating each record (unix type).

If X is d, the filter expects that there is a '\r\n' delimitating each record (MSDOS type).

To indicate the end of line delimitator to be used in the output file, we use the option -oX

(where X is 'n', 'u' or 'd').

If X is n, the filter doesn’t write any delimiter after each line.

If X is u, the filter writes a '\n' after each record.

If X is d, the filter writes a '\r\n' after each record.

5.3.17. ediperfi

This is the command to manage EDITRAN/P profiles.

You can see the user manual EDITRAN/GP Profile management for further information

about this utility.

5.4. FILES

5.4.1. editranp.cfg

EDITRAN settings file. It stores the local profile and the sessions profile for remote entities.

It is exclusively used by EDITRAN.

5.4.2. editranp.sdx

EDITRAN settings index file. It is exclusively used by EDITRAN.

5.4.3. editran.html

EDITRAN documentation which contains settings and consultation quick guides.

5.4.4. ckds.des

File where we can find the exchange keys for the cyphered EDITRAN sessions.

5.4.5. editranp.log

File created by the command makelog. It stores, cyclically, the summary of the operations

performed by EDITRAN. Once the maximum number of entries is reached, it overwrites the

oldest one.

It can be monitored from the EDITRAN menus and also through the command printlog.

5.4.6. editranp.msg

File in which there are stored the messages presented by EDITRAN to the EDITRAN

operator. It is used exclusively by EDITRAN.



5.4.7. editranp.out

File where are registered all the outputs performed by the editranp process and by the

procedures and commands launched by it. It is generated by the redirection of the standard

output of the process editranp.

5.4.8. licencia.dat

EDITRAN license file. It is always verified before starting the EDITRAN communications

processes. If this file doesn’t exist, or if its content is altered, the EDITRAN processes can’t be

executed.

5.4.9. licencia.publick

File containing the public key given by Indra to verify the license. Like the file licencia.dat,

is not to be manipulated.

5.5. CODES AND MESSAGES TO THE OPERATOR

These codes are reflected in the file editranp.log to indicate the different status through

which a session passes. In the screen of the EDITRAN/P operator, they appear as messages.

Listed below are the messages, with a brief explanation or recommended action,

accordingly:

MESSAGE EXPLANATION/RECOMMENDE ACTION

Established association Request of local association, accepted by the remote node.

Remote association accepted Association among applications, accepted by the local extreme

node.

Start of transmission The emission to the remote node starts.

Connection made A circuit with the remote node has been established.

Remote connection rejected (Profiles) Disagreement between the remote and the local profiles.

Monitoring status Answer to a query about a session’s status.

Monitoring remote transmitter file The monitoring of the control log for the remote emission buffer

file has been requested.

Monitoring remote receiver file The monitoring of the control log for the reception buffer file has

been requested.

Mismatch of totals in emission process In applications with totals control, the confirmed exchanged totals

are mismatched (synchronism).

Mismatch of totals in reception process In applications with totals control, the confirmed exchanged totals

are mismatched (synchronism).

Aborted emission The emission of a file to the remote node has been aborted.

Correct and ended emission An emission has finished correctly.

Local emission Start of the local emission of a file.

Error while opening file An error has occurred while opening a file.

Error while closing file An error has occurred while closing a file.

Error while writing file An error has occurred while writing a file.

Error while reading file An error has occurred while Reading from a file.

Error while executing SCRIPT An error has occurred while executing a shell script.

Error in remote batch process An error has occurred while executing a remote shell script.

General error in the interface An error has occurred while executing a shell script.

Remote cryptography error (ERR##) A cryptography error has occurred. See 5.7.3 Cryptography errors

Remote error while zipping/unzipping An error of zipping/unzipping has occurred in the remote extreme

node.

Connection retries are timed out The connection retries have been timed out, according to the

number of retries in the EDITRAN session profiles.

Synchronism retries are timed out The synchronism retries have been timed out, according to the

number of retries in the EDITRAN session profiles.

Retries in emission process are timed out The retries of the emission process of messages that require an

answer have been timed out.

Retries in reception process are timed out The retries of the reception process of messages that require an

answer have been timed out.

Retries to emit are timed out The retries for starting an emission have been timed out, according



to the number of retries in the EDITRAN session profiles.

Retries to establish session are timed out The retries for establishing a session have been timed out,

according to the number of retries in the EDITRAN session profiles.

Retries to end emission are timed out The retries for ending an emission have been timed out, according


Retries to receive are timed out The retries for starting an emission have been timed out, according


There is connection. Batch request is ignored A connection has been requested and it already exists.

Invalid caller extreme (profiles) Incompatibility in the values of the field in the profile log.

Profiles file is empty, or doesn’t exist An error has occurred while accessing the EDITRAN profiles file.

Reception file is not ready The information of the control log, exchanged between both

extreme nodes, doesn’t allow to start the data Exchange in the

request for starting the transmission. The number of exchange

session, contained in the control logs, doesn’t match. The file of

emission/reception is not uploaded, or is not available for EDITRAN

(it starts the batch process specified in the profiles).

Emission buffer file is not ready Answer for a remote file monitoring.

Buffer files in not compatible situation The remote node rejects the local request, as it doesn’t have the

buffer file ready. Likely, it has launched its previous automatism

corresponding to the request.

End of emission asked by the operator When the operator asks for the end of the forced emission.

End of emission asked by the remote operator When the remote operator asks for the end of the forced emission.

End of reception asked by the operator When the operator asks for the end of the forced reception.

End of reception asked by the remote operator End of the transmission asked by the remote operator.

End of local transmission asked by the remote node When the remote node asks for the end of the reception (end of

local transmission).

Impossibility of reception, due to profiles Check over processes defined in the session profile.

Impossibility of remote reception, due to profiles Check over processes defined in the session profile.

Start of reception When the reception of the remote file starts.

Release of remote application The connection has been released by the remote application.

Release of the XX XX transmission Message about a circuit release.

Release of the remote operator It occurs as a consequence of a release request by the remote

operator.

Release due to crossed calls There is a cross of calls between the remote and the local nodes,

and the system only accepts one.

Release by the operator It occurs as a consequence of a release request by the operator.

Release due to a zipping error Release is requested when occurs an error in any file

zipping/unzipping.

Release when another established channel exists A circuit is released when another one exists for a certain session.

Release due to invalid facilities We will check what kind of facilities will be used when requesting a

connection. EDITRAN will only manage the use of charged calls.

Release due to incorrect timing Check in the session profile the time, and modify it.

Release because the charged call is not accepted Check in the session profile the field CHARGED CALL.

Release because there are no free channels Circuit limitation. The connection will be established when the

already established one is released.

Release due to network restart A circuit release has occurred, due to the network restart.

Release due to invalid type of payment (profiles) Check session PAYMENT, anticipating conflicts. Some of the

extreme nodes will have to support cost.

Rejected call (invalid time) Request of connection out of time. Check over profiles.

Rejected call due to invalid remote address (profiles) Check NRI/IP of the session remote in profiles.

Remote call accepted The connection request of the remote node has been accepted.

The connection has been established.

Remote call accepted (cross) Both extreme nodes lost the connection establishment and the

local one was the first to be managed.

Remote call rejected (charged call) The specification for that parameter doesn’t match in both extreme

nodes.

Remote call rejected (cross) The incoming call from the remote node is rejected.

Remote call rejected (calling extreme node) The specification for that parameter doesn’t match in both extreme

nodes.

Remote call rejected (payment) The specification for that parameter doesn’t match in both extreme

nodes.

Local is not able to emit (profiles) Request of emission rejected, when the parameter TRAFFIC

DIRECTION, with value E or X, is not specified as it doesn’t have the

proper license.

Local is not able to call (profiles) Request of connection rejected, when we specify R in the

parameter CALLER EXTREME NODE, as only the remote can call.

Local can’t receive (profiles) Check on the parameter TRAFFIC DIRECTION and license for the



direction.

Incorrect notification message An error has occurred while establishing the session, due to the

format of the notification message.

There is no connection A request, than previously required the establishment of the

connection, has been made.

There is no session in profiles Register the session in profiles.

There are no resources available The connection can be established once the already established

one is released. This is due to the limitation of physical circuits in

the local environment.

There is no network service The local extreme node doesn’t have service X.25.

There is no session The request requires the existance of a connection among

applications.

Batch after emission is not launched An emission batch request has been received, but it won’t be

processed as the system is emitting.

Batch after reception is not launched A reception batch request has been received, but it won’t be

processed as the system is receiving.

Batch before emission is not launched A reception batch request has been received, but it won’t be

procesed as the system is receiving.

Batch before reception is not launched A reception batch request has been received, but it won’t be

processed as the system is receiving.

Connection is pending The request requieres the existence of a connection among

applications. The connection is not yet completed.

Lost sequence in emission process A jump of number in the sequence of the message has been

detected.

Lost sequence in reception process A jump of number in the sequence of the message has been

detected.

Incompatible profiles (zipping) The specified value for the zipping parameter doesn’t match in

both extreme nodes.

Reception rejected due to profiles (transmission

direction)

The specified value for the parameter ‘direction of the

transmission’ doesn’t match in both extreme nodes.

Batch request for downloading emission A batch request for downloading emission has been received.

Batch request for starting emission A batch request for starting a local transmission has been received.

Batch request for starting reception A batch request for starting a local reception has been received.

Batch request for preparing and starting emission A request for launching a work specified in profiles has been

received from batch.

Batch request for preparing and starting reception A request for launching a work specified in profiles has been


Batch request after emission A request for launching a work specified in profiles has been


Batch request after reception A request for launching a work specified in profiles has been


Request for association A request for connecting applications has been requested.

Request for reception A request for reception from the local or remote operator has been

requested.

Request not accepted. Server operation mode A request not allowed in server operation mode has been

requested.

After emission correctly ended An answer about a process correctly ended is received from batch.

After reception correctly ended An answer about a process correctly ended is received from batch.

Before emission correctly ended An answer about a process correctly ended is received from batch.

Before emission correctly ended An answer about a process correctly ended is received from batch.

Start of emission. Local emission The first burst of the transmission has been sent.

Reboot of remote operator network A network reeboot, requested by the remote operator, has

occurred.

Reception aborted The reception of a file has been aborted.

Reception correct and finished The reception of a file has been successful.

Message with invalid CRC received A message from the remote has been received, in a session defined

in profiles with CRC validation, being its CRC incorrect.

Incorrect message received from batch Correct type of ASP request.

Incorrect message received during emission process Message out of protocol.

Incorrect message received during reception process Message out of protocol.

Remote without session / Registering NRI (profiles) The NRI of an inconming call doesn’t match with the one for the

session registered in the profiles.

SBP with incorrect status received Message out of protocol.

SBR with totals mismatch Negative response to a synchronism of totals, as the totals in the

reception process don’t match.

SCP with incorrect status received Message out of protocol.

SEP with incorrect status received Message out of protocol.



A batch after emission has been launched A batch process according to profiles has been launched.

A batch after reception has been launched A batch process according to profiles has been launched.

A batch before emission has been launched A batch process according to profiles has been launched.

A batch before reception has been launched A batch process according to profiles has been launched.

A call has been made before A connection request has been received when a previous one in

the same session was already being processed.

The call is made There is a try to connect the remote EDITRAN system.

Local key change is requested The local extreme node has requested a key change when

establishing an association among applications.

Remote key change is requested The remote node has requested a key change when establishing an

association among applications.

Session rejected by profiles (Ascii/Ebcdic) Correct the parameter in the session profile.

Sessión rejected by profiles (CRC calculus) Correct the parameter in the session profile.

Session rejected by profiles (Service quality) Correct the parameter in the session profile.

Session rejected by profiles (Zipping) Correct the parameter in the session profile.

Session rejected by profiles (Totals control) Correct the parameter in the session profile.

Session rejected by profiles (Cryptography) Correct the parameter in the session profile.

Session rejected by profiles (Length of the log) Correct the parameter in the session profile.

Session rejected by profiles (Type of application) Correct the parameter in the session profile.

Session rejected by profiles (Type of connection) Correct the parameter in the session profile.

Session rejected by profiles (Version) Correct the parameter in the session profile.

Remote sending buffer inaccessible An error has occurred while accessing the remote sending buffer

file.

Remote receiving buffer inaccesible An error has occurred while accessing the remote receiving buffer

file.

There is yet an ongoing transmission The request was not processed, as there is an ongoing

transmission.

There is already a connection A connection request has been made for a session that was already

connected.

The system is already receiving A duplicate request by the operator is received.

The system is already transmitting A duplicate request by the operator is received.

Incorrect remote receiving file (previous launching) The remote node is preparing its reception buffer.

Incorrect remote receiving file (there is no previous) The remote node didn’t prepare its reception buffer because there

is no previous.

Incorrect remote receiving file (previous possible

executing)

The remote reception file is probably being prepared.

Incorrect remote receiving file (session number) The number of session of the remote receiving file doesn’t match

the local one.

Incorrect remote receiving file (total number of logs) The number of total logs for the remote receiving file doesn’t

match the local one.

Incorrect remote transmission file (previous

launching)

The remote node is preparing its emission buffer.

Incorrect remote transmission file (there is no

previous)

The remote node didn’t prepare its transmission buffer because

there is no previous.

Incorrect remote transmission file (previous possible

executing)

The remote transmission file is probably being prepared.

Local EDITRAN/G refuses batch request EDITRAN/G doesn’t execute the requested request.

Buffer file uploaded EDITRAN/G notifies the uploading of the transmission buffer.

Error. Cyphered transmission buffer and profile

without cryptography

IGA profile with cryptography and EDITRAN profile without

cryptography.

Error. Cyphered transmission buffer and profile with

key change

Cyphering IGA is not allowed, as well as key change in EDITRAN.

Error. Transmission buffer key and transmission key

don’t match

The key used by IGA to encrypt the buffer doesn’t match the

current EDITRAN key.

Error. Length of the transmission buffer and of the

profile are different

The length of the buffer uploaded by EDITRAN/G doesn’t match the

current length of EDITRAN/P.

Error. Transmission buffer zipped, and profile with

zipping

The data have been zipped in EDITRAN/G, and zipping is requested

in EDITRAN/P.

Error. Length of the reception buffer and of the

profile are different

Error. Transmission buffer cyphered, and profile with

zipping

The data have been cyphered in EDITRAN/G, and the profile of

EDITRAN/P is zipped.

RTC – Port is being used by other application Serial port is being used by another EDITRAN connection.

RTC – Port out of range The port specified in the profile doesn’t exist.

Network adapter is not installed or is not operating The network adapter (modem, X.25 card, etc.) doesn’t work.

RTC – The modem doesn’t respond The modem doesn’t respond.

RTC – Conveyor is not detected or is lost



Error while starting network adapter

RTC – There is no dial tone

RTC – Remote node is busy The network identifies the dialled ETD as busy with another

communications, and therefore unable to accept the incoming call.

RTC – There is no response from the remote node

RTC – Unrecognized response of the modem

RTC – Blank RTC number

X.28 – Release by the ETD(P) The distant terminal has released the communication.

X.28 – Local procedure error The DEP detects a procedure error caused by the ETD.

X.28 – Network congestion Condition within the network:

- Temporary congestion.

- Temporary failure.

X.28 – Out of service The dialled number is out of service.

X.28 – Error in remote procedure The network detects, in the distant extreme ETD/ETCD, a

procedure error caused by the ETD.

X.28 – Busy number The network identifies the dialled ETD as busy with another

communications, and therefore unable to accept de incoming call.

X.28 – Invalid facility request Invalid facility requested by the calling ETD.

X.28 – Forbidden acces The calling terminal is not authorized to obtain communication with

the dialled ETD.

X.28 – Unobtainable The address of the dialled ETD is not in the numbering plan or has

not been asigned to any ETD.

X.28 – Release by the PAD The communication has been released by the local DEP as a

response to a release invitation from the distant ETD.

X.28 – Number without reverse charge The dialled terminal is not subscribed to the reverse charge facility.

X.28 – Incorrect IUR The network user identificator is wrong.

X.28 – Without additioal information Release with 000 diagnosis from network.

X.28 – Invalid command Release with 016 diagnosis from network.

X.28 – Not allowed command Release with 032 diagnosis from network.

X.28 – Timer expiration Release with 048 diagnosis from network.

X.28 - Error while connectiong the PAD

Session rejected by profiles (Confidentiality) Correct the parameter in the session profile.

Session rejected by profiles (Authentication) Correct the parameter in the session profile.

Session rejected by profiles (Automatic

disconnection)

Correct the parameter in the session profile.

Session interrupted Verify the interruption code.

Remote certificate accepted The remote certificate is correctly accepted.

TCP – Connection reset

TCP – Destination address requested The remote IP must be specified.

TCP – Address not available The dialled address is not available.

TCP – Unreachable network The dialled address is not available.

TCP – Connection rejected

TCP – Host is down Verify the remote computer status.

TCP – There is no path for the host

TCP - Host not found

TCP – Unrecoverable error

Incorrect local receiving file (total number of logs) The number of total logs in the transmission extreme node doesn’t

match the number of logs expected to receive.

Incorrect local receiving file (creation date) The date of the local receiving file doesn’t match the creation date

of the remote extreme node.

Ignored version due to date control

Association timed out

Message with unknown header received Message with invalid protocol.

Rejected remote call (network license) The session doesn’t have license for the type of incoming call.

SWIFT – GetFile request made Informative.

SWIFT – GetFile request received Informative.

SWIFT – PutFile request made Informative.

SWIFT – PutFile request received Informative.

SWIFT – Accepted request Informative.

SWIFT – Rejected request Informative.

SWIFT – Incorrect status Informative.

Option not available for SWIFT sessions Informative.

Batch after emission is not launched. Data in SWIFT Informative in Swift gateway operation.

SWIFT. Incompatible buffer status Informative in Swift gateway operation.

SWIFT. Message with unknown identifier Informative in Swift gateway operation.

SWIFT answer Informative.



Reception rejected by profiles

Remote call rejected (session data) Check over whether is session for the received Id: local-remote-

application.

Call from PAD rejected Check over the corresponding field in the X25 parameters of the

session profile.

Release due to maximum number of sessions

(profile)

Check over the corresponding field in the local profile.

Current session released Informative.

Remote EDITRAN version is different (admitted) Check over the field in the session profile.

Release due to inactivity time out

Remote downloading timed out

Remote reception monitoring

Remote downloading in progress

Notes:

ETD - Equipo terminal de datos / Data terminal computer.

ETCD - Equipo conversor de señales (módem) / Signal converter computer (modem).

I.U.R. - Identificativo usuario de red / Network user identifier.



5.6. EDITRAN RELEASE MESSAGES

When is not possible to establish the connection in EDITRAN, or when the transmission

stops, the system generates release messages that identify the reason with two codes (cause

and diagnosis).

Is hard to document all the possible causes and diagnosis that EDITRAN/P can receive, as in

many cases it depends on the network protocol used, and on the driver provider. So in this

guide we will focus only on the releases made by the EDITRAN own protocol.

In this chapter there are also included the conditions for the connection retry, as it acts

according to the received releases.

5.6.1. EDITRAN CAUSES AND DIAGNOSIS

Now we will specify the EDITRAN cause and diagnosis codes for releasing or rejecting calls.

Cause = x'00'.

Diagnosis = x'XX'. Where "XX" is the following:

03 The maximum number of sessions defined in the local

environment (maximum number of circuits) has reached

its limit so there is no available channel.

04 There has been a crossing of calls on the fly. The system

will release the one whose EDITRAN installation code is

minor.

05 There has been a release as there is already a channel

established for the current session.

06 The incoming call is not allowed to be a reverse charged

one, according to the parameters in the profile session.

07 Rejected call due to the type of payment. In the

parameters of the session profiles, the payment is defined

as "R" (Remote), while the incoming call is a reverse

charge one.

08 Release of EDITRAN by the operator.

09 A network reboot has been made by the operator.

0A The incoming call is rejected, due to the use of invalid

facilities.

0B A circuit is released due to an error of compaction-zipping.

0C An incoming call is rejected because the incoming time is

wrong, according to the session specifications (STARTING

TIME and ENDING TIME).

0D The call is rejected because the session has not been

registered in Profiles, or because the remote NRI doesn’t

match any of the ones defined for the session.

0E The call is rejected because the extreme caller defined in

the session doesn’t match the one which is making the

call.

0F EDITRAN generic release (files not ready, automatism

booting, etc.).



5.6.2. RELEASES CAUSES AND DIAGNOSIS FOR A CALL X.28.

While establishing a communication, it could happen that the call is not established for

some reason that prevents it. In these cases, the user will receive a signal whose format is:

CLR AAA NNN

CLR – Release indicator.

AAA – Indicative code of the cause.

NNN – Indicative code of the diagnosis.

In the following table, we will indicate the codes for causes and diagnosis that the user can

receive from the Iberpac network.

CAUSE CODES: AAA

Mnemonic

expressions

Service signal

Release indication

Explanation

OCC Busy number The network identifies the dialled ETD as busy

with other communications.

NC Network congestion Condition within the network:

- Temporary congestion.

- Temporary failure.

INV Facility request The facility requested by the caller ETD is not

valid.

NA Forbidden access The caller terminal computer is not allowed to

obtain communication with the dialled ETD.

ERR Local procedure error The DEP detects a procedure error caused by

the ETD.

RPE Distant procedure error The network detects, in the ETD/ETCD distant

interface, a procedure error caused by the ETD.

NP Unobtainable The address of the dialled ETD is not in the

numbering plan, or no ETD has been assigned.

DER Out of service The dialled number is out of service.

PAD Release by the

dissasembler assembler

of DEP packs

The communication has been released by the

local DEP, as a response to a release invitation

from the distant ETD.

DTE Release by the ETD (P) The distant terminal computer has released the

communication.

RNA The number is susbcribed

to uptaking reverse

charge calls

The dialled terminal computer is not subscribed

to uptaking reverse charge calls.



NUI Wrong I.U.R The network user identifier is wrong.

DIAGNOSIS CODES: NNN

Numeric Codes Notes

000 No additional

information

ETD - Equipo Terminal Datos / Data terminal computer

016 Invalid command ETCD – Equipo conversor de señales (módem) / Signal

converter computer (modem)

032 Command not

allowed

048 Timer expiration IUR – Identificativo usuario de red / Network user identifier



5.6.3. CONDITIONS FOR CONNECTION RETRIES

The EDITRAN protocol has a recovery mechanism for temporary failures, based on retrying

the connection. The only cases in which it doesn’t retry are:

If the EXTREME CALLER field is Remote

If the release code is Cause = 0 and Diagnosis:

04 There has been a calls crossing.

05 There was already a connection for that session.

08 Release by the operator.

0F EDITRAN generic release.

00 No additional information. The retry is only performed if the connection is

being established, not while the transmission is down.

In every case, when retrying the connection, we will rotate to the following remote node, if

we have defined several ones in the profile. In X.25, the cause of the release will be used to

rotate or not the local NRI.



5.7. EDITRAN CRYPTOGRAPHY SYSTEM

5.7.1. Introduction

The chrytography system used in EDITRAN is based on the DES algorithm.

In every EDITRAN UNIX implementation environment, there is a file ckds.des in which we

have the Host Master Key (HMK) of the installation and also the keys that cipher keys.

EDITRAN uses a local key and a remote key.

There is no action to be made by the EDITRAN user on this file.

The EDITRAN cryptography considers an online bidirectional cyphering for both the

transmission and the reception. The outgoing data will be encrypted with a key, and the

incoming ones will be deciphered with another. In this way, both extreme nodes have two

homonym data keys.

5.7.2. Types of keys

HMK - Host Master Key

Its function is ciphering the keys of the local user entity, and it is masked in the file

ckds.des.

AK - Auxiliary Key

Its function is ciphering the EDITRAN master key.

It is randomly generated, and is incorporated to the file ckds.des with a label.

EMK – EDITRAN Master Key

Its function is ciphering the transmission and reception keys of a session. It is stored in the

EDITRAN profiles file editranp.cfg, encrypted under the local AK key.

TKE – Transportation Key for Emission

Its function is ciphering the data of EDITRAN user applications sent to the remote node.

It is stored encrypted under the EMK key in the profiles file.

TKR – Transportation Key for Reception

Its function is deciphering the data received from a remote user application.

It is stored encrypted under the EMK key in the profiles file.

When establishing a connection, the authentication of the TKE and TKR keys from both

extreme nodes is resolved, regardless of a change of key is performed. Namely, the system

validates whether TKE local = TKR remote and whether TKR local = TKE remote.



5.7.3. Cryptography errors

Any cryptography error will generate information for the local operator, as well as a

disconnection.

The errors that can occur are the following:

Cryptography errors v2.2

ERR1 The extreme node requesting a connection couldn’t perform the re-encryption of its

file keys.

ERR2 The extreme node requesting its TKE key authentication couldn’t cipher the

authentication code, although it could perform the re-ciphering.

ERR3 The extreme node requesting a connection with key change couldn’t generate a new

TKE emission key.

ERR4 The extreme node receiving the Remote Notification Indication had an error while re-

ciphering its file TKR key.

ERR5 The extreme node receiving the Notification Indication couldn’t decipher the

Authentication Code sent by the Remote, although it could perform the re-ciphering.

ERR6 The extreme node receiving a Notification Indication with Key Change had an error

while re-ciphering the new Reception key from the remote node (new TKR).

ERR7 The extreme node which is going to send a user data or an Operator Message had an

error in the online ciphering.

ERR8 The extreme node receiving a user data or an Operator Message from the Remote had

an error in the online de-ciphering.

ERR9 The extreme node receiving a Notification from the Remote (with or without Key

Change) has decipher the Authentication Code, but it is incorrect (despite the old

reception key is stored). Is possible that any extreme node Deleted and Created the

Profile EDITRAN Session. This is the biggest error. We only can get out of this

situation Deleting and Creating the Session in Profiles in both extreme nodes.



Cryptography errors v3.0 RSA or DES

ERR1 There was an error while obtaining the local key, either because it was not supplied in

Profiles or either because of an error in the External Keys Interface.

ERR2 While sending an association or answer request, there is an error when the signature

or the uncertainty is generated. If the used algorithm is DES, the error will be found in

the local key. If the error is RSA, the error is from the local key when the signature is

generated, or from the remote key when uncertainty is generated.

ERR3 Error while trying to generate the session key. If the algorithm used is DES, the error

concerns the local key. If it is RSA, the wrong key is the remote one.

ERR4 There was an error while obtaining the remote key, either because it was not supplied

in Profiles or either because of an error in the External Keys Interface.

ERR5 While processing a request or an answer from the remote node, there is an error

trying to decipher the uncertainty or the signature. If the algorithm used is DES, the

wrong key is the remote one. If we use RSA, the error is from the remote key while

deciphering the signature, or from the local key while deciphering the uncertainty.

ERR6 While processing a request or an answer from the remoet node, there is an error

deciphering the session key. If the algorithm used is DES, the error comes from the

remote key. If it is RSA, the wrong key is the local one.

ERR7 The extreme node which is going to send a user data or an Operator Message had an

error in the online ciphering.

ERR8 The extreme node which is receiving a usar data or an Operator Message from the

Remote node had an error in the online deciphering.

ERR9 While processing a request or an answer, we decipher the session key and the

signature, but either the uncertainty doesn’t match, or either the signature doesn’t

match (this case only in RSA).

The error occurs because the exchange keys don’t match in both extreme nodes.

If we used an External Keys Interface, the message must be accompanied by the last

8 bytes of the used label.

If the algorithm used is DES, the wrong key is the local one of the extreme node that

generated the message. If it is RSA, the wrong key is the local one (if the error occurs

while validating the uncertainty) or the remote one (if the error occurs while verifying

the signature).



Cryptography errors v3.0 PKI.

ERR1 The Certificate Server communicates an error while signing the text using the local

certificate from the server, described as NAME PSS and PIN PSS of the session.

ERR2 The Certificate Server communicates an error while validating the signature received

from the remote node.

ERR3 The Certificate Server communicates an error while ciphering the text using a

certificate received from the remote node.

ERR4 The Certificate Server communicates an error while deciphering text using the local

certificate located on the server referred to as NAME PSS and PIN PSS of the session.

ERR5 The Certificate Server communicates an error while extracting the certificate of the

signature received from the remote node.

ERR6 While processing the session key received from the remote node, it is wrong and the

uncertainty is not deciphered. The certificate used is the local certificate located in

our server.

ERR7 While verifying the digital signature received, the obtained DN doesn’t match the DN

referred to as REMOTE DN. The certificate used by the remote node is not the

expected one, or the session DN was not written correctly.

If the error occurs when the session is already established, the system indicates an

error while ciphering the emission extreme node.

ERR8 During the association process, there is an error while accessing cryptography

modules.

If the error occurs with an already established session, the system indicates an error

while deciphering data from the receiver extreme node.

ERR9 During the process of establishing an association, there is an error in the Client or in

the Certificate Server in the TCP/IP access, in the cryptography rutines, in the access

to files, or the server is timed out. An additional message will indicate what is the

reason for the error.


Centros de Competencia

eCommerce

Avda. de Bruselas 35

28108 Alcobendas.

Madrid, España

T. +34 91 480 80 80

T. +34 91 480 50 00

www.indracompany.com

editran/p - indraeditran.indra.es/en/doc/win_unix/editran/editran_p_en.pdf · editran/p...

Documents