Communication interfaces
For each of the communication modes, there is an interface that makes the upper layers of the network independent.

EDItran can transmit simultaneously with different sessions that can use different interfaces.

The network and transport protocols used are X.25, X.28 (PAD) and TCP/IP, thus EDItran can transmit using any network architecture that supports these protocols.


This is an EDItran component that dialogs with the different X.25 management modules of every machine.
  • NPSI/GATE NPSI/DATE, Isard.X.25 in mainframe environments.
  • X.25 cars drivers for Windows environments.
  • X.25 API for AS/400.
  • X.25 API for each UNIX system (AIX-Link, Wan Support, Sun-link, HP-J2793).


EDItran component that dialogs with the MODEM driver using AT commands through a series port for Windows and Unix.


EDItran component for IP networks in all their variations (Internet, corporate intranets, MPLS, ...) or for communication links RDSI, Frame Relay, ATM, local networks, etc.


This is an alternative to the use of the 3745 communication controller in X.25 connections for mainframe environments (CICS and IMS). It also can be used to replace the X.25 card in AS/400 environments.

This module leads the competition with 3745 maintenance costs, and it also solves the problem that EDItran users have since IBM announced the maintenance discontinuity for this communication controller.

It consists of a TCP/IP connection between the host and a UNIX or Windows machine, and it transforms the protocol TCP/IP to X.25 and viceversa.


Given the existing sensitivity to connect the machines where the corporate applications are running to internet public networks, we have developed a middle connection element among these corporate machines and public networks.

This middle connection element is place in the network DMZ and it provides the tranquility ot not having to expose the application files in a public network. It also simplifies the treatment of the firewall rules, as they don't need to be modified each time a new extreme node wants to connect our EDItran by TCP/IP.


To avoid having to connect an X.25 line to our Windows machine, there is the possibility of working with the module EDIX25 in distributed mode. Thus, EDITRAN can be placed along with the application files withing the local network, and the X.25 interface can be placed in a different DMZ machine.