Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Configure Network Interfaces

To enable the IMG 2020 to function over an IP network the network interfaces on the rear of the IMG 2020 must be configured to pass data. There are two steps involved in configuring the network interfaces. The first step is to configure one or more IP addresses to pass data through a specific interface. Second would be to specify whether the IP address would be used for RTP data or Services data such as SIP signaling, DNS Services, RADIUS, and SNMP. Below is a screen captures of the rear panel of the IMG 2020 and its respective IP Interfaces. Once the interfaces on the rear panel are configured, they can be used to pass the specific type of data it is configured for. The information below describes the steps needed to configure the network interfaces for either RTP or Services.

The IP addresses 10.31.42.x and 10.31.43.x (Subnet: 255.255.255.0) are reserved for the IMG 2020. Do not attach to any external network with this address.


IMG 2020 Rear Panel DATA A0 Location

Interfaces CTRL 0/1, Data A0/1, and Data B0/1 all can be configured to pass either RTP data, IP Services data, or both. It is up to the administrator to decide which interface will be used for each function.

By default, the CTRL 0/1 interfaces will already have an IP address assigned to them. This was achieved when initially setting up the system for OAMP functionality such as software downloading and communicating with the Web GUI. The IP addresses were assigned through use of either the bootup.cfg file or the dhcpd.conf file depending on your situation. The CTRL 0/1 interfaces can also have SIP signaling and the IP Services function through these interfaces but cannot be addressed to the same network that was configured through the bootup.cfg or dhcpd.conf.

Configuration Procedure

The first procedure assigns an IP address to the CTRL interface to be used for passing SIP signaling. This IP address will be considered Service IP address. In all the examples below, the CTRL is already configured with a private 192.168.10.10 address using the bootup process.

Configure the CTRL Network Interface for IP Services

The first interface configured will be configured on the CTRL Interface and can be used to pass Services such as SIP Signaling, DNS Services, SNMP, and a host of other services supported on the IMG 2020.

  • Right click the IMG 2020 physical node object and select New Network. The IP Network object that gets created is a container or parent object. The Denial Of Service functionality (IP Firewall) is by default set to Enabled. Modifying this will leave the IMG 2020 susceptible to IP based attacks through the CPU based Services. Refer to the IP Network Interface topic for more information on this object.

  • Right click on the IP Network object created and select New Logical Interfaces. The Logical Interfaces object is a parent or container object and no configuration is needed here. Refer to the Logical Interfaces topic for more information on this topic.

  • Right click on the Logical Interfaces object and select New Logical Interface. Since the SIP signaling will be streamed through the CTRL interface, select Control from the drop down menu of the Interface field. Refer to the Logical Interface topic for more information on this object.

  • Right click on the Logical Interface object and select New IP Address. Configure the interface for the SIP signaling service by selecting Services from the drop down menu of the Source Endpoint field.

  • Enter an IP address into the IP address field. This will be the IP address that will be used for SIP signaling.

  • Enter the Default Gateway address that the IMG 2020 communicates with when sending and receiving SIP signaling. Refer to the IP Address topic for more information on configuring the other fields in this object. Below is screen capture displaying the IP address object configured.

 

Configure the Data A Network Interface for RTP Data

The second interface configured will be configured on the DATA A Interface and will be used in this procedure to pass RTP Media data.

  • Right click on the Logical Interfaces object and select New Logical Interface. The Media will be streamed through the Data A interface located on the rear of the IMG 2020. Select Data A from the drop down menu of the Interface field. Refer to the Logical Interface topic for more information on this object.

  • Right click on the Logical Interface object and select New IP Address. Since this interface will be used to stream RTP data, select Media 0 from the drop down menu of the Source Endpoint field.

  • In the IP Address field, enter the IP Address field that will be used for RTP data.

  • Enter the IP Address of the Default Gateway the IMG 2020 communicates through when sending and receiving RTP data. Refer to the IP Address topic for more information on configuring the remaining fields in this object. Below is screen capture displaying the IP address object configured.

 

Create IP Resources/Packet Facilities for Audio

Once the network interfaces have been configured, the IP Facilities/resources can be configured. Follow the procedure below to configure the IP Facilities that will be used to communicate through the interfaces configured.

  • Right click on the Profiles object and select New IP Profiles. The IP Profiles object is a container or parent object and no configuration is needed here. Refer to the IP Profiles topic for more information on this object.

  • Right click on the Profiles object created and select New IP Profile. In the Name field, either enter a name that identifies this IP Profile or accept the default name. Refer to the Profile topic for more information on configuring the fields in this object.

  • Right click on the IP Profile object and select New Vocoder Profile. Select the vocoders that will be offered from the drop down menu. Refer to the Vocoder Profile topic for more information on configuring the individual fields. Create as many Vocoder Profiles as needed.

  • Click on the Profiles object again. At this point there will be a yellow exclamation point indicating the configuration has not been sent to the IMG 2020. Click on the Download Profiles button in the object pane and the profiles will be sent to the IMG 2020.

  • Right click on the IMG 2020 physical node object and select New Facility. The facilities object is a container object and no configuration is needed here. Refer to the Facility topic for more information on this object.

  • Right click on the Facility object created and select New Packet Facilities. The Packet Facilities object is a container object and no configuration is needed here. Refer to the Packet Facilities topic for more information on this object.

  • Right click on the Packet Facilities object and select New Packet Facility. The Packet Facility object configures the IP Facilities/resources. Enter a Name that identifies this Packet Facility.

  • The Media Endpoint field is automatically defaulted to Media 0 and the RTP data will be passed to the IP address configured below.

  • In the Network field, select the IP address that will be used to pass the RTP Media.

  • In the Packet Facility Channel Type field, select Packet Audio since this procedure is for audio and not video. Refer to the Packet Facility topic for more information on configuring this object. Refer to screen capture below.

At this point in the configuration, the CTRL 0/1 interface is configured with an IP address that can be used for any IP Services. The Data A interface has been configured with an IP address to pass RTP media data and the IP Facilities/Resources object has been configured for RTP audio and will use the Data A port. Any SIP signaling/IP Services being configured will be given the IP address configured on the CTRL port.

This is just a basic example. The CTRL 0/1, Data A0/1, and Data B0/1 interfaces can all be configured for either IP Services or RTP Media/Multimedia. How the interfaces are configured determines what functionality will be used on them.

  • No labels