IMG 1010 - Configuring Network Interfaces

Owned by Kelli Higdon
Last updated: Mar 04, 2024
2 min read

 

The network Interfaces are configured using ClientView. By configuring these interfaces, you provide physical and logical interface data which then configures how the network traffic is organized over the subnets.

The IP Address 10.31.42.x (Subnet: 255.255.255.0) is reserved for the IMG's. Do not attach to any external network with this address.

 

Overview:

There are three types of IMG streams:

  • Control (Management)

  • Signaling (H.323/SIP)

  • Data (RTP)

 

Important Note: The Network Interface for Network Management (Ctrl 0) is configured automatically during the BootP process and the connection is made when logging into ClientView.

Important Note: The Data and Control ports must be segregated (on separate hubs). See the or topic for sample scenarios that can be considered when configuring the network interfaces.

Depending on the network configuration, the IMG can be configured to either separate rtp data and signaling data into separate network interfaces or they can be combined onto one interface. The IMG supports both scenarios

 

Guidelines

  • When configuring the Network Interface for H.323 or SIP Signaling you provide the IP address. When configuring H.323 or SIP Signaling, select this IP address from the drop down list. This will associate the signaling to the physical IP address over which it is running.

  • The two VoIP modules are allowed only on data ports so their IP addresses must be on the same subnet.

  • If the CPU is configured to go through the Control port, the IP address of that profile should be on the same subnet as the IMG's IP address (CTRL 0/1 IP addresses).

  • If the CPU is configured to go through the Data ports, the IP address of that profile should be on a different subnet from the IMG's CTRL 0/1 subnet. This IP can be on the same subnet as the VoIP modules or a different one.

  • Do not delete the VoIP module 0/1 if that profile is used to configure the VoIP modules 0/1 under Facility. Also, if a CPU network interface is configured and used for NFS traffic, do not delete it.

 

Return to Documentation Home I Return to Sangoma Support