Basic Configurations

The Basic Configuration procedure configures the basic functionality of the 2020 IMG. Once the basic functionality is created the signaling and individual feature functionality can then be configured. Below is a Quick Start diagram displaying the objects. The Configuration <Filename> object is pre-populated when ClientView is initially started.

DG_Tree_ClientView_INIT_Config.png

 

Create Logical and Physical Node

Start by first configuring the Physical BDN Node. Under the Dialogic BDN object, the physical node can be configured. Follow procedure below to configure the Physical Node.

  1. Right Click on the IMG EMS object and select New Logical IMG. Enter a name for this logical node cluster. Refer to Logical IMG topic for more information.
  2. Right Click on the Logical IMG object and select New Physical IMG. Click in the IMG Name field and enter a name that will identify the node being configured.
  3. Click in the IP Address field and an Enter IP Address box will appear. Enter the IP Address being given to this node.
  4. Click on the Commit icon and the Node object will automatically get populated with information from the 2020 IMG. Refer to the Physical Node topic for feature and functionality information on this object.

 

Create Profiles

Some of the objects such as TDM Spans, IP Bearer Ports, and Signaling Gateways need to be associated with a specific profile in order for it to function in a network. The profiles are first created and then later associated to each of the items. Follow procedure below to create each of the Profiles.

  1. Right click on the IMG EMS object and select New Profiles. The Profiles object is a container object and no configuration is needed here. Refer to the Profiles for more information on this topic.

  2. Right click on the Profiles object and select New T1 or E1 Span Profile dependent on which protocol is being configured. The profile being configured will be used later in procedure when creating T1 or E1 Spans. For more information on configuring this object refer to T1 Span Profile or E1 Span Profile.

  3. Right click on the Profiles object and select New IP Bearer Profile. The IP Bearer Profile being configured will be used later in procedure when creating IP Ports. For more information refer to IP Profile.

  4. Right click on the Profiles object and select New SIP SGP. The SIP SGP object being created will be used later when configuring SIP Signaling, External Gateways, or ENUM Servers. Refer to the SIP SGP topic for more information on configuring this object.

 

Create VoIP Network Interfaces and IP Bearer Ports

To enable the 2020 IMG to function over an IP network the VoIP resources/ports must have an IP address assigned to them and must be configured to communicate through a specific interface located on the rear of the 2020 IMG. The steps below describe the configuration needed to configure the VoIP resources/ports and an associated network interface.

  1. Right click on the Physical Node and select New Network. The IP Network object that gets created is a container object and no configuration is applied here. For more information on this object refer to the IP Network (Interface) topic.

  2. Right click on the IP Network object that is created and select New IP Address. In the Physical Interface field select VoIP Processor from drop down menu. When VoIP Processor is selected, the Logical Interface is automatically populated with Data A port which is the port the RTP data will use to communicate with the network.

Note: In the procedure, the Physical Interface selected was VoIP Processor which is using the VoIP Resources for RTP. If however CPU was selected then the Logical Interface field would allow selecting Data A, Control, or Data B. The CPU Interface is used to configured an IP address for signaling such as SIP Signaling etc.

  1. Enter an IP address that will be used for RTP and enter the Default Gateway IP address. For more information refer to IP Address topic.

 

Create VoIP Signaling Resource

Configure an IP address and interface for IP Signaling such as SIP signaling.

  1. Right click on the IP Network object and select New IP Address. Select CPU from the Physical Interface drop down menu.

  2. In the Logical Interface field select which interface on rear of 2020 IMG will be the interface that the signaling will communicate through. Selections are Control, Data A, or Data B.

  3. Enter IP address of the interface and Default Gateway information. For more information on which IP addresses that can be utilized refer to IP address topic. This interface can be used for signaling such as SIP signaling.

 

Create Facility Object (VoIP and TDM spans)

  1. Right Click on the Physical Node object and select New Facility. It is at this point the decision to use the Optical Interfaces or the DS3 interfaces. If using the optical interfaces select 4 DS1 + Optical from drop down menu in the Circuit Facility Configuration field. If using the three DS3 interfaces select 4 DS1 + 3 DS3 from drop down menu in the Circuit Facility Configuration field.
 
4 DS1 + Optical = The  two optical interfaces and four T1/E1 ports on rear of 2020 IMG are enabled and can be configured.
4 DS1 + 3 DS3  = The three DS3 Interfaces and four T1/E1 ports on rear of 2020 IMG are enabled and can be configured.

 

Note: The selection of optical or DS3 interface needs to be accomplished even if the BDN is being used for IP to IP protocols only. The Facility object needs to be configured to be able to create the VoIP Resources / Ports. In this procedure the 4 DS1 + 3 DS3 selection in drop down menu will be chosen. Refer to the Configuring Facilities topic for more information on configuring the TDM interfaces on rear of BDN.

  1. Right click on the Facility object and select New Bearer - IP. The Network Interface field will default to VoIP Processor and Network IP address field will default to the IP address of the Data A interface. Refer to VoIP Resource topic for more information on this object.

 

Timing Synchronization Priority List

Before connecting the 2020 IMG to a network, it must be synchronized to a T1/E1 loop timing source such as a T1 or E1 span. Up to seven different clock sources can be configured through the various interfaces on the rear of the unit. The synchronization priority list sets a clock source priority (highest priority to lowest priority).

  1. Right click on the physical node object and select New Timing Synchronization Priority List. A timing synchronization priority list object will appear with a default order of timing priorities.

  2. The default priority list is set up as Primary Reference > Secondary Reference > Primary Loop > Secondary Loop > free running > Optical Working, and lastly Optical Protection. To modify, click in the Timing List field of the arrange items box and move the timing source either up or down the list. By moving the sources up or down the list, the priority is also being configured. The higher up on the list the higher the priority. For more information refer to Timing Synchronization Priority List topic.

 

Time Zone or UTC Offset Setting

The 2020 IMG needs to have an NTP server connected to set the time on the 2020 IMG. All log file timestamps use the NTP Server for keeping track of time. See Configure SNTP and configure the network time on the 2020 IMG before proceeding with setting the Time Zone object. If however the 2020 IMG is getting its time from an NTP server then continue on and set the Time Zone object.

  1. Right Click on the Physical Node and select New UTC Offset. Select from drop down menu the offset from UTC time needed for the area the 2020 IMG will reside. Refer to Time Zone Setting topic for more information.

 

Licensing

Licensing opens up different functionality on the 2020 IMG. The licensing object monitors and displays which licenses have been loaded onto the 2020 IMG through the license file created for that specific node. Create the licensing topic to view all licensing configured on the 2020 IMG.

  1. Right Click on the Physical Node and select New Licensing Info. A licensing Info object gets created and displays the licenses installed. For more information, refer to the License Info topic.

 

Configure Facilities / Spans

Because there are multiple types of interfaces that can be utilized for T1/E1 call processing, configuring spans is addressed in a separate topic. For information on configuring spans refer to the Configuring Facilities topic. Once the facilities/spans have been configured then come back to this procedure to finish configuring the basic objects.

 

 

Signaling

A Signaling object needs to be configured to allow SIP, SS7, and ISDN signaling to be utilized on the 2020 IMG. The signaling object creates the signaling stacks for the SIP, SS7, and ISDN protocols. Create the signaling needed through the signaling object. See procedure below.

  1. Right Click on the Physical Node and select New Signaling. A signaling object gets configured. The Signaling object is a container object and no configuration is needed here.

From here, any of the individual signaling functionality can be configured. For more information refer to the following links below:

Configuring SIP

Configuring SS7

Configuring ISDN