VoIP Engineering / Telecommunications Network Architecture ยท 2025

Multi-Network VoIP Routing and SIP Media Interworking Platform

In January 2025, I completed a telecommunications infrastructure project for THE GOAL, India, on behalf of CRTLHOST. The customer needed to connect its Internet-facing VoIP platform to a landline SIP-trunk provider operating over a separate, dedicated network. I designed and implemented a virtualised architecture using Debian, Proxmox, CentOS and Asterisk 16, with separate network interfaces and provider-specific routing. The completed solution enabled end-to-end voice calls using SIP signalling and RTP media while restricting general Internet connectivity on the Asterisk gateway. The customer subsequently confirmed the successful delivery and operation of the solution.

Role

Lead VoIP / Network Infrastructure Engineer

Duration

Completed January 2025; exact development duration not documented.

Client

THE GOAL, India (delivered on behalf of CRTLHOST)

The challenge

The customer, THE GOAL, operated an Internet-facing VoIP platform but needed to establish reliable connectivity with a landline SIP-trunk provider accessible through a separate network.

The existing network arrangement could not simply be extended to the provider without addressing several technical requirements. SIP signalling and RTP media needed to reach the correct provider endpoints, while the Asterisk gateway also had to communicate with the internal VoIP system.

A further requirement was to restrict general Internet connectivity from the Asterisk gateway without preventing the specific connections required for voice services.

The challenge was to bring these separate network environments together, maintain reliable call routing and ensure that the gateway used the designated network paths.

This required more than configuring an ordinary SIP trunk. It involved designing the virtualised infrastructure, separating network interfaces, establishing selective routing and integrating the different components into a working telecommunications platform.

The solution

I designed and implemented a multi-virtual-machine architecture using Debian, Proxmox virtualisation, CentOS and Asterisk 16.

The solution separated the Internet-facing VoIP environment from the dedicated SIP-trunk network. One virtual machine operated the softswitch, while a second virtual machine provided the Asterisk gateway responsible for interworking with the landline provider.

I configured the Asterisk gateway with two network interfaces. The first connected it to the internal VoIP network, and the second provided access to the dedicated provider network.

Rather than allowing unrestricted routing, I configured specific static routes towards the provider's Session Border Controller and designated RTP media endpoint. This allowed the gateway to communicate with the required infrastructure through the appropriate interface.

I also configured the SIP peers and dialplan routing, integrated the softswitch with the Asterisk gateway and tested connectivity between the different network environments.

The completed design provided a controlled communication path between the customer's Internet-facing VoIP platform and the landline SIP-trunk provider.

My responsibility covered the architecture, configuration, network integration, troubleshooting and delivery of the technical implementation on behalf of CRTLHOST.

The outcome

The project was completed in January 2025 and successfully established end-to-end voice communication between THE GOAL's Internet-facing VoIP environment and its landline SIP-trunk provider.

According to the customer's signed confirmation, SIP signalling and RTP media operated through the designated network paths, allowing the two telecommunications environments to interconnect as required.

The implementation also met the customer's requirement for controlled SIP-trunk connectivity with restricted general Internet access for the Asterisk gateway.

The project demonstrated how virtualisation, network segmentation and selective IP routing could be combined to solve a practical telecommunications interworking problem.

THE GOAL subsequently confirmed my responsibility for the architecture, configuration, integration and implementation, as well as the successful delivery of the completed solution.

Key specifications

Project Type: Telecommunications Infrastructure Engineering and Systems Integration

Customer: THE GOAL, Kolkata, India

Delivery Organisation: CRTLHOST

Project Role: Lead VoIP / Network Infrastructure Engineer

Completion: January 2025

Virtualisation Platform: Proxmox VE

Host Operating System: Debian Linux

Virtual Machine 1: CentOS 6.2 softswitch

Virtual Machine 2: CentOS 7 with Asterisk 16

Network Architecture: Separate Internet-facing, internal VoIP and dedicated SIP-trunk networks

Asterisk Gateway: Dual network interfaces for internal communication and dedicated provider connectivity

Routing Method: Provider-specific static host routes

Provider Interconnection: Dedicated network connection to the provider's Session Border Controller and RTP media endpoint

Call Signalling: SIP

Voice Media: RTP

SIP Integration: SIP peer configuration and dialplan routing

Connectivity Requirement: Controlled provider access with restricted general Internet connectivity from the Asterisk gateway

Implementation Activities: Architecture design, virtual machine configuration, IP routing, SIP integration, network troubleshooting and connectivity testing

Confirmed Result: Successful end-to-end voice calls through the designated SIP and RTP network paths

Customer Confirmation: THE GOAL, signed 21 September 2026

Supporting Documentation: CRTLHOST employment confirmation, customer confirmation, retrospective architecture diagram and selected 2026 configuration screenshots

Evidence Scope: The 2026 configuration captures demonstrate a later network state and are not original January 2025 handover records.

Technology

VoIPSIPSDPRTPAsterisk 16Debian LinuxProxmox VECentOS 6.2CentOS 7VirtualisationMulti-Network RoutingStatic IP RoutingDual-NIC ConfigurationSIP TrunkingSIP Peer ConfigurationDialplan RoutingNetwork SegmentationNAT NetworkingSession Border Controller (SBC)Telecommunications Systems Integration