How to connect ONVIF cameras in different cases of Telecom VSaaS in Complex Networks

For Telcos and ISPs providing telecom VAS in accordance to different network topologies is not an easy task, the best example is VSaaS in complex networks. It’s an often occasion that the network infrastructure is already established and set up. At the same time, there’s a need to connect ONVIF cameras through them. Usually cameras with standard ONVIF protocol don’t support the NAT-network or complex routing environment for reliable operation. 

This can arise several challenges for rapid and efficient cloud video surveillance service provisioning by Telcos and ISPs as they have to deal with network requirements and limits:

• IP address and port overlap as well as other network constraints, especially inconvenient for scalability of the service 
• Cameras in an external or isolated network usually generate  port forwarding challenges   
• Latency issues or unwanted loading of media server as there is efficient optimization of routing for the most suitable traffic path option

So does it mean that you have to follow the connection requirement of ONVIF and adapt the network to it? In most cases, yes. And it may cause unsatisfying delays in telecom video surveillance service provisioning  with complicated process of system setup and control.

However, Aipix found out how to solve these challenges and provide a special level of ONVIF camera connection flexibility. Aipix platform is capable of adaptive camera connection via ONVIF. Users can adjust the system to the specific topology of the communication node. The activities and operation with various devices within the network is now adaptively applied. Implementation of such models allows the flexible topology adaptation to different networks and sites. 

Why Aipix solution is suitable for Telcos and ISPs to work with  telecom VSaaS in complex networks 

Flexible approach of adjusting telecom VSaaS in complex networks

The admin of the video surveillance system can choose the necessary connection configuration and camera operating mode based on architecture of the network and requirements for traffic distribution 

Internal network

This applies to environments where the IP camera and platform components communicate exclusively through a private network without Internet access. All devices operate within the internal network, and the IP camera connects directly without any Network Address Translation (NAT) devices in front of it.

The IP cameras and platform components can operate on different network segments, but the administrator must configure routing to allow communication between them. The network also requires static IP addresses for all devices because it does not support dynamic address assignment through DHCP.

Internal Network (NAT Intranet)

It is designed for scenarios where the IP camera and the platform components communicate within a private network that does not have Internet connectivity. In this setup, however, the IP camera is located behind a Network Address Translation (NAT) device.

The NAT device maps the camera’s private IP address, which cannot be accessed directly by the platform components, to a static private IP address assigned to the NAT device. As a result, the platform components communicate with the translated address rather than the camera’s original private address.

External Network (NAT Internet)

This configuration is appropriate when the IP camera is deployed in a remote network that is reachable over the Internet. In such a setup, the camera is positioned behind a Network Address Translation (NAT) device.

The NAT device converts the camera’s private IP address, which cannot be accessed directly by the platform components, into a static public IP address. This public address enables the platform components to establish communication with the remote camera through the Internet.

Managing the video streams: Direct or Proxy 

Aipix ONVIF connectivity provides support for multiple video data transmission methods, allowing the administrator to select the appropriate mode based on the desired network traffic flow.

Direct

In Direct mode, the camera and the VMS controller communicate directly without involving any additional servers in the data exchange. All traffic, including control requests, ONVIF event notifications, and video streams, flows directly between the camera and the VMS controller.  When subscribing to ONVIF events, the address of the server hosting the VMS controller is specified as the destination endpoint.

Proxy

In Proxy mode, communication between the IP camera and the VMS controller is performed through an intermediate media server. The media server acts as a relay, receiving video streams and ONVIF event messages from the camera and then transmitting them to the VMS controller. The address used by the event server, whether an internal or external IPv4 address, is automatically determined according to the selected camera connection configuration.

Adaptive work with platform

The platform adapts the customer’s existing network architecture, allowing organizations to meet VSaaS requirements without modifying or redesigning their infrastructure.

The tangible result of adaptive work with Telecom VSaaS in Complex Networks

Implementing this operating logic simplifies the connection of new customers and the scaling of the VSaaS service.

1. Scalability

The number of issues encountered during the onboarding of new sites is minimized. The system administrator can adjust and optimize camera connectivity based on the characteristics and requirements of each specific network environment.

2. Resource Optimization

Full control over network traffic distribution allows more efficient use of media server resources and available data transmission channels.

3. Reliability

The system achieves higher reliability and improved resilience when operating across unstable network segments. It is capable of maintaining consistent video stream delivery even in environments with complex routing configurations.

The Aipix architecture includes adaptive ONVIF camera connectivity and management features that simplify VSaaS deployment for telecom operators and Internet service providers across real-world network environments. By supporting multiple connection configurations, NAT-based scenarios, and both Direct and Proxy traffic transmission modes, the VSaaS Software Solution enables stable camera connectivity and efficient device management without requiring network infrastructure redesign.

For service providers, this approach leads to faster deployment of new sites, fewer configuration-related issues, optimized use of media server resources, and more reliable video stream delivery across geographically distributed customer networks.