Journey

Half a century between one architecture and the next.

I didn't learn telecom in a course. I evolved with computing — from each hardware generation to the next, without skipping any. What I now call root-cause diagnosis was born from decades of debugging systems when there was no shortcut, no documentation and no internet to consult.

Architectures that were part of this story

Before IP networks, VoIP and today's communication platforms, Brazilian enterprise engineering was built on multiuser machines, branch processors, terminals, buses, operating systems and dedicated networks. Two of these equipment families help explain the technological transition lived through along this journey.

1985+

Medidata M1001 — the enterprise supermicrocomputer

The Medidata M1001 was a landmark of Brazilian enterprise technology, classified at the time as a 16-bit multiuser supermicrocomputer. Originally launched by Medidata Informática S/A in 1985, it kept running actively in companies and government agencies throughout the entire 1990s.

Unlike the ordinary personal computers of the era, such as the IBM PC clones built by Medidata itself, like the M301, the M1001 was designed for the heavy enterprise market. Its architecture used microprocessors from the Motorola 68000 family, such as the 68010, bit-slice technology and a multi-CPU bus-arbiter board to manage multiple processors working together.

A single central cabinet could process data simultaneously for several operators connected through video terminals. It was common to find installations with five or more terminals attached to a single machine. Later came versions such as the M1001 Slim and the M1001 Turbo, aimed respectively at more compact installations and at higher performance.

M1001

MUMPS, Unix and enterprise applications

The M1001's software architecture departed from the MS-DOS standard and favored multiuser environments with high data concurrency. One of Medidata's differentiators was adapting MUMPS — a language and environment known for its efficiency with databases — to run natively on the M1001.

As the 1990s advanced, the equipment also began running variants of Unix System V. At the application level, it ran commercial and financial automation systems, notably the ACU-Cobol compiler and systems dedicated to the capital markets and the stock exchange, such as FINANSIS.

Anos 90

Medidata → MLx Medidata Labo

Medidata Informática, originally founded in Rio de Janeiro, expanded and, in the early 1990s, merged with the Labo Eletrônica division, becoming MLx Medidata Labo S/A.

With the opening of the Brazilian IT market to imports, the company gradually stopped manufacturing its own hardware and shifted its focus to systems integration, support and network consulting.

Even so, the M1001 remained present through the decade as the central server of companies, universities and public agencies. In environments such as chemical companies, it was the heart of operations that relied on a robust, stable machine needing infrequent maintenance — a true workhorse.

DGR

Digirede — branch processors and automation

Digirede Informática S/A was one of the great forces of Brazilian banking and commercial automation during and at the end of the Market Reserve policy. Instead of focusing only on IBM PC clones, it specialized in robust distributed systems for bank branches, where the data flow had to survive power outages, process teller transactions simultaneously and communicate with the banks' mainframes.

In the automation terminology of the era, "processor" did not simply mean the silicon chip, but the central server cabinet — the enterprise CPU — responsible for the local intelligence of the branch or store. It concentrated data and controlled teller terminals, financial printers, check readers and barcode scanners.

DGR 8000

The robust legacy

The DGR 8000 family was conceived in the late 1980s and entered the 1990s as one of the solutions aimed at commercial and banking automation. Its evolution incorporated proprietary technologies and Intel-family processors, such as the 80286 and the early 80386, in architectures intended for continuous-operation environments.

The systems could run variants of Unix/Xenix-based multiuser systems or Digirede's proprietary solutions aimed at local financial transactions. In commercial automation, the processors controlled early points of sale and their serial peripherals, such as scales, reduced keyboards and displays, reducing the load on the network.

DGR
8500

The evolution toward high performance

The DGR 8500 family represented an evolution of Digirede's branch servers for the import-opening scenario of the 1990s. The engineering advanced to Intel 80486 microprocessors, including DX and DX2 versions, and later to the first Intel Pentium, in a modular architecture aimed at fast maintenance.

Another important point was distributed connectivity: synchronous and asynchronous communication controller boards allowed communication with mainframes, including IBM SNA/SDLC standards, over dedicated Embratel lines.

Storage used hard drives of early SCSI or IDE technologies, in capacities ranging roughly from 80 MB to 500 MB, with mechanisms meant to increase fault tolerance. In a banking environment marked by hyperinflation, losing local data before its transmission to the mainframe was simply unacceptable.

1994+

DGR 486SX and the commercial transition

In mid-1994, the need to cut costs in the face of competition from imported computers led Digirede to branch its engineering into lines such as the DGR 486SX. The modular cabinets — desktop, tower, mini-tower and network — served everything from manager workstations to small local processors.

As happened with Medidata, maintaining proprietary hardware factories became progressively less sustainable against the global competition of manufacturers such as IBM, Compaq and HP. Digirede gradually migrated from heavy hardware to banking software, logical security and enterprise network integration services.

Legado

From the enterprise CPU to the IP network

The M1001, DGR 8000 and DGR 8500 belong to a generation in which reliability meant knowing the hardware, the bus, the operating system, the peripherals and the equipment-to-equipment communication deeply. That experience did not stay isolated in the past: it formed the basis of a way of working in which each layer must be understood before a failure can be attributed to another.

The move from superminis and branch processors to standard servers, enterprise networks, IP, VoIP and NGN did not represent a complete rupture. It was a succession of architectures, each adding new layers of complexity — exactly the continuous line that runs through this journey.

From foundational electronics to Oracle Communications

One continuous line: a solid technical grounding, two decades at Tier-1 carriers and, today, independent consulting in signaling, networks and software.

1974

The first curiosity

The beginning in foundational electronics — understanding the circuit before trusting it. The discipline of looking at the signal, not the assumption, which I still carry today.

80s

Technical training and the first architectures

Electronics Technician, graduated in the early 1980s. The era of the Zilog superminis and then Motorola — each new architecture learned from the inside, from the bus to the software.

90s

Systems Analysis and the Intel era

Systems and Telecommunications Analyst. From superminis to the enterprise PC — the bridge between the hardware I already mastered and the software that was starting to govern the networks.

1999

Two decades at Tier-1 carriers

The turn toward IP networks, VoIP and NGN, working at Tier-1 carriers. About 22 years of real operation — from Senior Technician to NOC Supervisor — where downtime is measured in minutes per year and the diagnosis cannot be wrong.

1999
2000

Embratel — Business Dial and corporate Internet access

Business Dial, later evolved into IP Business Dial, was a strategic corporate service launched by Embratel at the turn of the millennium, between 1999 and 2000, just after the company's privatization and the opening of the telecommunications market in Brazil. It emerged at the peak of commercial Internet adoption and the need for corporate network interconnection.

Unlike ordinary residential dial-up Internet, Business Dial was a high-performance dial-up access service aimed at the corporate market. It allowed a company's employees — working from home, in small branches or on the move — to connect remotely to the public Internet or to the company's own private Intranet, using conventional telephone lines.

IP

IP connectivity, remote access and corporate management

The service used Embratel's IP Backbone and Digital Network infrastructure to provide IP connections based on modem dial-up, seeking greater stability compared with the ordinary Internet providers of the era. Access was via 0800992190 and 0800992156.

One of its main uses was to act as an access node for virtual private networks (VPNs). The employee dialed a specific number provided by Embratel and, after authentication, obtained a secure channel to reach the company's internal headquarters systems.

The product also featured POP Master, an admin panel in which IT managers could manage accounts, define access profiles, audit traffic and control passwords. This management interface remained active for many years on dedicated carrier domains, such as the IP Business Dial portal.

Integration with Embratel On Line let customers monitor usage, open trouble tickets and view consolidated invoices directly over the Internet.

NOC

The NOC role — Lucent MAX TNT

I worked as NOC supervisor, configuring and monitoring the MAX TNT equipment from Lucent Technologies, responsible for dial-up network access.

Inside Embratel's computing center, the MAX TNT acted as a NAS (Network Access Server). The corporate user used the home or branch computer to dial, over a conventional telephone line (PSTN), an Embratel access number. The call arrived directly at the MAX TNT line cards, which converted the telephony signals into IP data traffic and established the channel using PPP (Point-to-Point Protocol).

AAA

Corporate remote authentication — RADIUS and Realm

Ensuring that a user dialing from an ordinary line entered securely into the restricted Intranet of a large company required a security architecture based on the three AAA pillars: Authentication, Authorization and Accounting. The base protocol used was RADIUS (Remote Authentication Dial-In User Service).

1

Access request — PPP handshake

As soon as the physical modem connection was established, PPP came into play on the user's machine. The credentials entered, usually in the format user@company.com.br and password, were forwarded using methods such as CHAP (Challenge-Handshake Authentication Protocol) or PAP, depending on the configuration adopted.

2

RADIUS gateway — routing by domain (Realm)

Lucent Technologies' MAX TNT did not store the customers' passwords. On receiving the data, it generated a RADIUS Access-Request packet and sent it to the "Navis Radius" authentication servers.

The segmentation element was the suffix, or Realm. On identifying the @company.com.br, Embratel's RADIUS server determined which corporate domain and service that connection belonged to.

3

Integration with the company's security — RADIUS Proxy

There were two paths to validate whether the employee was authorized: a shared database, pre-populated by the company with the list of allowed users, or the RADIUS Proxy, in which the request was forwarded in real time over a secure dedicated link to the company's own internal authentication server.

That server could be integrated with LDAP directories, Microsoft Active Directory or TACACS+ servers. In this way, disabling a user at headquarters could directly affect dial-up access control.

4

Authorization and isolation — L2TP / VPDN

After a RADIUS Access-Accept, the user had to be isolated from the public Internet. The MAX TNT received the network parameters sent by the server and applied the corporate access instructions.

The traffic could be encapsulated in a direct-communication tunnel using L2TP (Layer 2 Tunneling Protocol) or VPDN (Virtual Private Dial-up Network). This tunnel connected the Lucent chassis at Embratel directly to the Firewall/Gateway at the company's headquarters.

The employee received an IP address valid in the context of the company's internal network, completing the connection transparently, as if physically connected to the office network.

1999+

Business Link, Office Dial and Virtual Dial

Business Dial was part of a family of Embratel connectivity products aimed at different corporate needs:

Business Link: dedicated, permanent circuits and links for large corporations.

Business Dial / Office Dial: flexible dial-up access for smaller offices, branches or remote workers.

Virtual Dial: a service aimed at access providers that outsourced their connections using Embratel's nationwide network.

2001+

The evolution to broadband and the end of the Dial era

With the advance of broadband, including ADSL through services such as Velox and Speedy and cable access, from 2001 and 2002 solutions based exclusively on dial-up lines began to lose ground.

Business Dial was gradually integrated into and replaced by native IP VPN solutions and higher-speed corporate broadband links offered by Embratel. The service stopped being a flagship catalog product and came to represent a legacy technology of corporate connectivity.

Hoje

Ositron — independent consulting

Senior consulting in Oracle Communications, SIP signaling, Software Engineering and Databases. The same rigor as always, now serving those who need the problem solved at its cause — not worked around at the symptom.

0 years

Of engineering, following each architecture generation without skipping any. From the crystal radio and Citizen Band to the IP Backbone and up to the cloud.

0 years

At Tier-1 carriers — from Telecommunications Specialist to NOC Supervisor. And then DevOps, with the creation of the SBC Express.

Root cause

The method that runs through the whole journey: evidence before assumption.

I don't seek approval. I seek consistency — and the problem solved where it really is.
Talk to a specialist →