
Fasfox developed a management portal that enables telecom operator Legos to expand into the German market
Legos, a telecommunications company, provides tailored communication solutions to businesses worldwide. Legos makes fixed and mobile phone number ranges available on behalf of its customers, with the option of activating many services on these lines.
Seeking to expand its presence in Europe, Legos identified Germany as a strategic market. This expansion required significant changes to its existing B2B platform to meet the requirements of the German market, particularly regulatory ones: unlike France, Germany requires identity documents to be collected before lines are activated. Legos asked Fasfox to design these changes.
Mission
Fasfox had to adapt the platform to the German market without disrupting operations in France. The project covered non-destructive changes to the database, the development of a new API, the collection of the identity documents required in Germany, and improvements to the interface used by operators who do not use the API.
Challenges
Legos offers a wide range of services, including IP telephony, messaging services, international numbering solutions and unified communications platforms.
Legos provides its B2B customers with a webcare portal to buy phone number ranges, port numbers and activate services on these numbers. The platform was only available to French customers, with limited features and an unintuitive interface.
The project had a dual objective: extend the API to bring the service to the German market with its specific telecommunications regulations, and redesign the platform’s front end accordingly.
The main challenges were:
- Adapting the existing platform: changing the database non-destructively to incorporate the specifics of the German market, without interrupting service for existing French customers.
- New API v2: developing an API to manage orders in the German format, including trunk/DDI orders and mobile number orders, while remaining compatible with French orders.
- Identity document collection: complying with the German requirement to collect identity documents before lines are activated.
- Improving the interface: updating the interface for operators not connected via the API, to make it easier for them to work with the new API v2.
Solutions
Database and API
The first and most delicate workstream concerned the existing MariaDB database: the requirement was to start from the existing database and make only non-destructive changes, in production, without interrupting service for French customers.
To ensure smooth integration, we implemented the API routes needed to handle ordering scenarios and operations related to end users, trunks/DDIs, numbers and services. The API follows the REST model. It is documented according to the OpenAPI specification with Swagger and Redoc, to make integration easier for third-party developers. The APIs are designed to work with French products, although the initial orders are limited to German products.
Managing DDIs (Direct Dial-In) requires a direct connection to external equipment. These operations used to be performed directly in the view, a fragile approach that the new portal replaces with a dedicated SSH communication module providing a secure connection to the equipment.
Identity document collection
To meet the German requirement for identity verification before lines are activated, the portal lets customers create, edit and manage the end users of the lines, whether businesses or individuals. For Germany, this includes collecting and validating identity documents, in line with the market’s regulatory requirements.
User interface
The webcare v2 portal had to remain usable by operators not connected via the API, in both France and Germany. The interface is built with React.js.

The portal manages the following:
Numbers
This is the core of the portal: customers can manage different types of phone numbers for the end users they have declared:
- Allocated numbers: Legos customers can request number ranges, which are added to their inventory. They can then choose numbers on which to activate services for their end users.
- Hosted numbers: Legos customers can declare number ranges to be hosted and view the inventory of hosted numbers.
The portal handles number porting, allowing customers to transfer their existing numbers to another operator.
Services
On allocated or hosted numbers, customers can activate various services (voice trunk, SMS trunk or mobile), view the inventory of services activated per end user, and activate, modify or remove them.
Technical architecture
The portal back end is built with Django (Python). The user interface is built with React.js. The existing database runs on MariaDB.

Results and benefits
The webcare v2 portal enables Legos to grow its business in the German market in compliance with local identity collection requirements, while remaining compatible with its business in France and providing a single management interface. The non-destructive changes to the database ensured a smooth transition: Legos maintained continuity of service in France while expanding into Germany.
The new portal has enabled Legos to manage its services more efficiently, with a simpler interface for both its customers and its internal administrators. Expansion into other national markets, within the same portal, is now under consideration: the v2 portal was designed from the outset with the integration of other countries in mind.