Dialogic ControlSwitch Installation guide

Brand: Dialogic

Model: ControlSwitch

Type: Installation guide

Dialogic® ControlSwitch™

System

Installation Guide

CS Release 5.11.1.0

ControlSwitch Installation Guide

 Dialogic Inc. Proprietary Page 2

in writing from Dialogic Corporation at the address provided below.

All contents of this document are furnished for informational use only and are subject to change without notice and do not represent a

commitment on the part of Dialogic Corporation and its affiliates or subsidiaries (“Dialogic”). Reasonable effort is made to ensure the accuracy

of the information contained in the document. However, Dialogic does not warrant the accuracy of this information and cannot accept

responsibility for errors, inaccuracies or omissions that may be contained in this document.

INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY

ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN A SIGNED

AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC ASSUMES NO LIABILITY WHATSOEVER, AND DIALOGIC DISCLAIMS ANY EXPRESS OR

IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS

FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHT OF A THIRD PARTY.

Dialogic products are not intended for use in certain safety-affecting situations. Please see

http://www.dialogic.com/company/terms-of-use.aspx for more details.

Due to differing national regulations and approval requirements, certain Dialogic products may be suitable for use only in specific countries,

and thus may not function properly in other countries. You are responsible for ensuring that your use of such products occurs only in the

countries where such use is suitable. For information on specific products, contact Dialogic Corporation at the address indicated below or on

the web at www.dialogic.com.

It is possible that the use or implementation of any one of the concepts, applications, or ideas described in this document, in marketing

collateral produced by or on web pages maintained by Dialogic may infringe one or more patents or other intellectual property rights owned by

third parties. Dialogic does not provide any intellectual property licenses with the sale of Dialogic products other than a license to use such

product in accordance with intellectual property owned or validly licensed by Dialogic and no such licenses are provided except pursuant to a

signed agreement with Dialogic. More detailed information about such intellectual property is available from Dialogic’s legal department at

6700 Cote-de-Liesse Road, Suite 100, Borough of Saint-Laurent, Montreal, Quebec, Canada H4T 2B5. Dialogic encourages all users of its

products to procure all necessary intellectual property licenses required to implement any concepts or applications and does not condone or

encourage any intellectual property infringement and disclaims any responsibility related thereto. These intellectual property licenses may

differ from country to country and it is the responsibility of those who develop the concepts or applications to be aware of and comply with

different national license requirements.

Dialogic, Dialogic Pro, Dialogic Blue, Veraz, Brooktrout, Diva, BorderNet, PowerMedia, PowerVille, PowerNova, MSaaS, ControlSwitch, I-Gate,

Mobile Experience Matters, Network Fuel, Video is the New Voice, Making Innovation Thrive, Diastar, Cantata, TruFax, SwitchKit, Eiconcard,

NMS Communications, SIPcontrol, Exnet, EXS, Vision, inCloud9, NaturalAccess and Shiva, among others as well as related logos, are either

registered trademarks or trademarks of Dialogic Corporation and its affiliates or subsidiaries. Dialogic's trademarks may be used publicly only

with permission from Dialogic. Such permission may only be granted by Dialogic’s legal department at 6700 Cote-de-Liesse Road, Suite 100,

Borough of Saint-Laurent, Montreal, Quebec, Canada H4T 2B5. Any authorized use of Dialogic's trademarks will be subject to full respect of the

trademark guidelines published by Dialogic from time to time and any use of Dialogic’s trademarks requires proper acknowledgement.

The names of actual companies and products mentioned herein are the trademarks of their respective owners.

This document discusses one or more open source products, systems and/or releases. Dialogic is not responsible for your decision to use open

source in connection with Dialogic products (including without limitation those referred to herein), nor is Dialogic responsible for any present

or future effects such usage might have, including without limitation effects on your products, your business, or your intellectual property

rights.Document History.

ControlSwitch Installation Guide

 Dialogic Inc. Proprietary Page 3

Document History

Revision#

Version Date

Comments

April 2013

Updated for Release 5.9.1.10

April 2015

Updated for Release 5.10.2

1.0

December 2016

Updated for CS release 5.11.1.0 – Introducing the HP DL360 gen9

server-based and the virtualized CS installation, and virtualized CS

installation.

ControlSwitch  Installation Guide 
 
  Dialogic Inc. Proprietary  Page 4 
 
Table of Contents 
 
 INTRODUCTION ............................................................................................................................................ 5 
2.1 Glossary ....................................................................................................................................................... 5 
2.2 Contact Us ................................................................................................................................................... 5 
 PRODUCT FORMS ......................................................................................................................................... 6 
 INSTALLATION PROCEDURE STEPS ................................................................................................................ 7 
4.1 Kickstart....................................................................................................................................................... 7 
4.2 CS Element Installation ............................................................................................................................... 8 
4.3 Virtualization Prerequisites ......................................................................................................................... 9 
4.4 Virtualized Installation .............................................................................................................................. 10 
4.5 SSH Handshake .......................................................................................................................................... 10 
 DEPLOYMENT SCENARIOS ........................................................................................................................... 12 
 NETWORKING .............................................................................................................................................. 13 
6.1 Ethernet Interfaces ................................................................................................................................... 13 
6.2 Interface Bonding ...................................................................................................................................... 14 
6.3 ei_check .................................................................................................................................................... 15 
6.4 Static Routes ............................................................................................................................................. 16 
6.5 High Availability ......................................................................................................................................... 16 
 IP PORTS USAGE .......................................................................................................................................... 19 
 HP PLATFORM SPECIFICATIONS ................................................................................................................... 23 
8.1 Environmental Specifications .................................................................................................................... 23 
8.2 Panels and LEDs......................................................................................................................................... 24 
 Front Panel ............................................................................................................................................ 24 
 Systems Insight Display ......................................................................................................................... 25 
 Rear Panel ............................................................................................................................................. 28 
 Device Numbers .................................................................................................................................... 29 
 Hot-plug Drive LED Definitions ............................................................................................................. 29 
8.3 Safety Considerations ............................................................................................................................... 30 
 
 
   

ControlSwitch Installation Guide

 Dialogic Inc. Proprietary Page 5

Introduction

The document covers the ControlSwitch System (CS) installation process for two different product

forms.

This guide includes:

 Product Forms

 Installation Procedure Steps

 Deployment Scenarios

 Networking

 IP Ports Usage

 HP Platform Specifications

2.1 Glossary

For the purposes of this document the following abbreviations apply:

Abbreviation

Meaning

ControlSwitch System

Operating System

Virtual Machine

Table 1: Glossary

2.2 Contact Us

For a list of Dialogic locations and offices, please visit: https://www.dialogic.com/contact.aspx.

ControlSwitch Installation Guide

 Dialogic Inc. Proprietary Page 6

Product Forms

The ControlSwitch elements are provided in the following two forms:

 IU HP DL360 Gen9 hardware platform hosts the CS element(s).

 Any hardware selected by the customer as a Virtual Machine (VM) hosts the virtualized CS

element(s).

The CS has been ported to Linux Operating System (OS) Centos 7, and can be deployed in one of the

four verified deployment scenarios.

The following figure depicts the defined platforms:

The physical platform that has been verified to host the elements is the HP DL360 Gen9. The platform

offers DC/AC power supplies, 2 x 600GB HDD, 8 x 16GB RAM, HP 1U SFF Rack Mount Kit, 4 x Copper

ports 1GB (additional 2 x 600GB HDD is added to: EMS, EMS-DR, DSE and CDR to support the database).

For more details see HP Platform Specifications.

ControlSwitch  Installation Guide 
 
  Dialogic Inc. Proprietary  Page 7 
 
 Installation Procedure Steps 
→ To install the HP platform-based CS, follow the below steps: 
1. Run the kickstart.  
Note: 
During the elements installation (next step) that require database, the DB server activation license is required at the application 
installation phase. Also license is required for the EMS-DR element. 
2. Install the CS element (see CS Element Installation) 
3. Follow the steps in the SSH Handshake section 
→ To install the virtualized CS, follow the below steps: 
1. Study the prerequisites (see Virtualization Prerequisites) 
2. Install the virtualized CS element (see Virtualized Installation) 
3. Install the CS element (see CS Element Installation)  
4. Follow the steps in the SSH Handshake section 
See Networking for details on the interfaces and their connectivity, after the installation. 
4.1 Kickstart 
This physical platform should include, prior to the element's application installation, the following: 
 A running operating system (Linux CentOS 7.1) 
 The required storage partitions 
 An Installation script 
 The recent software release 
 Oracle database for the elements: EMS, EMS-DR, CDR and DSE. 
Vocabulary: 
Kickstart: The process for preparing the platform with the items mentioned above is named as Kickstart.  
PXE Boot server: Virtual server including Veraz Linux software, OS repositories and Kickstart configurations running on an x86 
based workstation. 
Target server: The target Linux server (HP) to be installed 
Follow the bellow steps to run the Kickstart: 
1. Prepare your laptop to run as VM, using VirtualBox (https://www.virtualbox.org/wiki/Downloads) 
2. Download the latest kickstart.ova to your laptop. 
3. Disconnect the laptop's connection to network, and connect the HP platform's NIC1 to the laptop. 
4. Run the VM using the VirtualBox menu. 
5. Select File  Import Machine  kickstart.ova to import the Kickstart to the HP platform. 
6. Change the network settings according to the workstation's ethernet network adapter (bridged 
mode) 
7. Ensure that there is a direct or a L2 hub ethernet connection between the workstation and the HP 
server on NIC1 

ControlSwitch Installation Guide

 Dialogic Inc. Proprietary Page 8

8. Start Kickstart VM (no further action needed with VM)

9. Boot target server from network (F12) and select PXE menu

10. In the displayed menu, select the element to be installed (EMS, CDR. CSP,…)

11. Wait for the process to finalize ( – Finish – ). Press Enter (might take up to 40 minutes)

12. System starts.

13. Disconnect the platform from the network.

4.2 CS Element Installation

Follow the bellow steps to install a CS element, in customer's site:

1. Enter the host with admin/veraz privilege (temporary)

2. From the host, go to the location: /reserved/software

cd /reserved/software

3. Extract the tar file

sudo tar xvzf 5.11.1.x-y.tgz

4. Open the veraz_installer.conf file to edit the configuration parameters:

sudo vi veraz_installer.conf

veraz_installer.conf example:

# ==================================================================

# ControlSwitch installation user inputs config file

# This file can be used for the "silent" mode installation of

ControlSwitch elements

# APPS=CCP,SEE,PE,EC,ICE,SSE,MRCE,BGCE,DCA,SPICE,LSG,DCS

# ==================================================================

SCRIPTS=/reserved/software/5.10.2.2-06/Install/

PKGS=/reserved/software/5.10.2.2-06/PKGS

APPS=CCP,SEE,PE,EC,ICE,SSE,MRCE,BGCE,DCA,SPICE,LSG

DB_COMPONENT=0

OMNI_COMPONENT=0

EnableSSH=y

USE_SSH=1

RCP=rcp

RSH=rsh

SSH_PATH=

DualEthernet=y

PRIMARY=eno1

SECONDARY=eno2

SEC_NET_ADDR=192.168.7.0

My.NETMASK=24

EMS_IP=192.168.6.222

My.PRIMARY_IP_ADDRESS=192.168.6.224

My.HOSTNAME=bmcsp3

My.SECONDARY_IP_ADDRESS=192.168.7.224

EMS.HOSTNAME=emscdr

EMS.SECONDARY_IP_ADDRESS=192.168.7.222

EMS.PRIMARY_IP_ADDRESS=192.168.6.222

ControlSwitch Installation Guide

 Dialogic Inc. Proprietary Page 9

CCP.SEPARATE_IAD=n

ACCESS_METHOD=LOCAL_PATH

PKGS_LOCATION=/reserved/software/5.10.2.2-06/PKGS

DEFAULT_GATEWAY=192.168.6.229

"veraz_installer.conf" 32L, 972C

5. Enter:

cd 5.11.1.x-y/Install/linux_install

6. Install the software:

sudo ./install.pl -config ../../../veraz_installer.conf

7. Reboot the server

→ For database server installation:

1. Enter the host with admin/veraz privilege (temporary)

2. From the host, go to the location: /reserved/software

cd /reserved/software

3. Enter:

cd 5.11.1.x-y/Install/linux_install

4. Install the software:

sudo ./install.pl -config ../../../veraz_installer.conf

4.3 Virtualization Prerequisites

Verify that the below prerequisites are met, before the installation:

1. Dialogic recommends the following minimum requirements for the VM that hosts the virtualized

element:

Category

Minimum Requirements

Server

Any x86 hardware, compatible with the VMWare vSphere (ESXi version 6.0 or higher)

Hypervisor.

CPU

For vCSP and vCDR: 32 CPU

For vEMS, vPolicy, vDSE, and vLIDAP: 16 CPU

Memory

For vCSP: 128GB

For vEMS, vPolicy, vCDR, vDSE, vLIDAP: 64GB

Disk Space

For vCSP, vPE, vLIDAP: 300GB

For vEMS, vDSE - 600GB

For vCDR: minimum 600GB

It is recommended to select the 'thin' mode (ESXi provisioning) for the OVF storage

allocation, and set a minimum size and grow as needed.

Network Interfaces

Four 1GbE interfaces

Table 2: Minimum Hardware Requirements

Note:

In general Dialogic does not provide product or support services for VMware vSphere ESXi or the underlying x86- platform. It is

the customer's responsibility to provide and maintain an x86 server(s) compatible with the VMware vSphere.

ControlSwitch Installation Guide

 Dialogic Inc. Proprietary Page 10

2. Power and network cabling is completed, IP Connectivity is established, and all the interfaces are

activated.

3. Install and configure the VMware vSphere ESXi 6.0 or higher.

4. Install the VMware management tool(s) to manage the hypervisor environment.

5. Create 2 separate vSwitches, where each connected to a different interface.

6. Logical networks must be created in the hypervisor environment: 2 for CMI, and 2 for bonding (for

protocols such as SIP, and management protocols for vEMS).

7. Prepare the setup diagram with relevant IP addresses and networking.

4.4 Virtualized Installation

The virtualized image is delivered in an Open Virtualization Format (OVF), packaged as an .ova archive.

Use the following procedure to deploy the virtual appliances:

1. Download ova files from https://dialogic.signin.aws.amazon.com/console/s3?bucket=veraz-

catalog&prefix=hp/

(obtain credentials offline)

1. In this folder the following OVA files are found: linux.csp.ova & linux.db.ova.

2. Select Download of the selected element OVA file to a local location

3. Deploy the VM using VMware vSphere client.

4. The OVA is configured with a minimal configuration.

5. During deployment you may configure desired vCPU's and memory resources. For storage use

ALWAYS Thin Provisioning.

6. After deploying the image, start the VM guest.

7. Go to Console tab in order to start installation.

4.5 SSH Handshake

After the installation there is a need for SSH Handshake. There is no difference in the SSH environment

between the Linux and the Solaris implementations. The following applies to both:

1. Login to the platform machine as user

2. Enter:

su – ics

ssh-keygen -t rsa

3. For Linux:

ssh-copy-id user@<destination hostname or IP address>

Enter the user’s password when prompted.

4. For Solaris:

ssh icsftp@<CSP machine hostname or IP address> mkdir –p .ssh (password is icsftp)

cat .ssh/id_rsa.pub | ssh icsftp@<CSP machine hostname or IP address> 'cat >>

ssh/authorized_keys

Originating Elements

Originating User

Destination Elements

Destination User

EMS

oracle

CDR

oracle

EMS

oracle

DSE

oracle

CDR

ics

icsftp

ControlSwitch Installation Guide

 Dialogic Inc. Proprietary Page 11

DSE

oracle

DSE

oracle

EMS

root

ANY

root

ANY

root

EMS

root

Table 3: SSH Handshake

ControlSwitch Installation Guide

 Dialogic Inc. Proprietary Page 12

Deployment Scenarios

The following table lists the various deployment scenarios:

Scenario

Description

Scenario A – EMS has not

ported to Linux (it is based on

Solaris)

Adding new Linux-based CS element when the EMS is not upgraded

to Linux (existing customers).

Upgrade the EMS to Solaris/Oracle release that is equivalent to CS

element Linux release (5.11.1.x)

Same for other CS elements that communicate with the new

element.

Scenario B – EMS upgrades

to Linux-based EMS

The Linux-based EMS needs to manage the Solaris-based CS

elements. Options:

 CS has been upgraded to the new release.

 EMS needs to manage a mix Linux and Solaris based CS components

Scenario C – new CS domain

- brown field

A new domain is added, including EMS and CS elements. All

elements are Linux-based.

The Linux-based elements are fully interoperable with Solaris-based

elements in a different domain (release 5.9.2.x).

Scenario D – new CS (new

customer) - green field

A new CS network is build, including EMS and all CS elements. All

elements are Linux-based.

ControlSwitch Installation Guide

 Dialogic Inc. Proprietary Page 13

Networking

The matrix below illustrates which protocols are applicable to a network element.

Network Element

CMI/ SCTP

(UDP)

IUA/

SCTP

M3UA

/SCTP

SIP

(UDP)

H.323

(TCP)

MGCP

(UDP)

H.248

(UDP)

SFTP/

SSH

ODBC/

JDBC

AX1-EMS

AX3 - CDR

X1 - CSP

X2 - Policy

X3 - DSE

X4 - LIDAP

CS elements communication depends on high quality network conditions (less than 200 ms round trip

delay and less than 2% packet loss).

Four ethernet interfaces are required. Relevant static routing tables should be set.

6.1 Ethernet Interfaces

The CS physical platform architecture requires 2 ethernet interfaces pairs:

1. One pair for internal communication (CMI/SCTP) and MGCP - each interface connected to a

different network. ei_check script setup is required to allow communication between the CS

entities from a different network.

2. One pair for protocol (IUA/SCTP, M3UA/SCTP, SIP, H.323, H.248) communication. IPMP mechanism

is required for IP fault tolerance.

For virtualized CS, two virtual interfaces are sufficient (one fir CMI, and one for the other protocols.

ei_check and IPMP are not relevant.

In the below example, the H.248 protocol is not in use. Four interfaces are used, as described below:

Interfaces

Protocols

IPMP

Ei_check

NIC0+NIC1

CMI, MGCP

yes

NIC2+NIC3

SIP, H.323, IUA, M3UA

yes

ControlSwitch Installation Guide

 Dialogic Inc. Proprietary Page 14

6.2 Interface Bonding

Network interface bonding (similar to IP Network Multi-Pathing (IPMP) on Solaris) is also known as

terminologies such as port trunking, channel bonding, link aggregation, and NIC teaming. It combines

multiple network connections into one logical interface, increasing the throughput by load balancing or

providing redundancy by allowing failover from one component device to another. By default, a bonded

interface appears like a normal network device to the kernel, but it sends out network packets over the

available slave devices by using a simple round-robin scheduler.

→ To configure an interface bonding:

1. Edit the file /etc/sysconfig/network-scripts/ifcfg-bond0 and insert the parameters as shown in the

following example:

DEVICE=bond0

BONDING_OPTS="mode=1 miimon=500"

ONBOOT=yes

BOOTPROTO=none

NETMASK=255.255.255.0

IPADDR=10.243.98.62 -- *FLOATING IP*

GATEWAY=10.243.98.1

USERCTL=no

2. Edit the interface configuration files /etc/sysconfig/network-scripts/ifcfg-[interface Name] for the

two NIC's that conform the combined interface:

DEVICE=ens160

ONBOOT=yes

BOOTPROTO=none

MASTER=bond0

SLAVE=yes

DEVICE=ens192

ONBOOT=yes

BOOTPROTO=none

MASTER=bond0

SLAVE=yes

ControlSwitch Installation Guide

 Dialogic Inc. Proprietary Page 15

3. For both interfaces we use bond0 as Master, where each interface acts as Slave for bond0

interface. Add the following line to /etc/modprobe.d/bonding.conf file:

alias bond0 bonding

→ To Activate the bonding:

1. Run the following two commands:

modprobe bond0

Service network restart

→ To test the bonding:

1. Run a ping against the floating IP and disconnect the primary interface, the recovery time is very

quick, but it is possible to lose one packet during the switchover.

→ To view the status of a bond:

1. View the /proc/ file by running the following command:

cat /proc/net/bonding/bond0

1. The following is displayed in the window:

Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: fault-tolerance (active-backup)

Primary Slave: None

Currently Active Slave: ens224

MII Status: up

MII Polling Interval (ms): 500

Up Delay (ms): 0

Down Delay (ms): 0

Slave Interface: ens224

MII Status: up

Speed: 10000 Mbps

Duplex: full

Link Failure Count: 1

Permanent HW addr: 00:0c:29:5e:c7:78

Slave queue ID: 0

Slave Interface: ens256

MII Status: up

Speed: 10000 Mbps

Duplex: full

Link Failure Count: 1

Permanent HW addr: 00:0c:29:5e:c7:82

Slave queue ID: 0

6.3 ei_check

The following two algorithms are used to determine the MGCP availability

 Source IP Selection and Retransmission. Running in the CCP, selects the source IP address for

the MGCP packets, based on AUEP message ACKs arriving from the MG, handles the AUEP

transmissions, and determines the failures based on configured timers.

ControlSwitch Installation Guide

 Dialogic Inc. Proprietary Page 16

 Interface Selection. Selects one of the two physical ports that send the MGCP messages, using

the ei_check script. If there is no connection, the script changes the IP routing table so that all

the packets destined to the MG are directed to the other interface, within milliseconds.

ei_check script is available only for X1 platforms.

→ To enable the ei_check script:

 Go to the /opt/IPVRmisc/ei_tools directory

 Add the required routing information to cfg.<interface-name>, based on the template:

6.4 Static Routes

The primary/secondary network-based Static Routes are used for internal CMI/SCTP. Default Routes

should be configured on elements in order to avoid configuring large number of static routes to remote

peers. It is recommended to use static routes on all CS platforms for communicating with external

entities rather than using default routes.

→ To install the Static Routes Setup option:

 Static route configuration can be stored per-interface in /etc/sysconfig/network-scripts/route-

<interface> file.

 Add the required routing information to route-<interface> based on the below template:

<Destination IP address> /<prefix> via <gateway-IP address> dev

6.5 High Availability

The EMS Disaster Recovery (DR) mechanism, maintains the path between the active and standby

databases, available for both HP platform-based and virtualized elements.

For physical platforms, are provided with 2 pairs of interfaces, ei_check and IPMP mechanisms to

enable network redundancy.

In virtualized platform implementations, since the VMs cannot provide the physical network separation

between the vNIC interfaces (primary and secondary), it is the customer's responsibility to implement

the high availability scenarios, by using external routers for reroute in case of interfaces failure. The VM

network reachability is provided by the service provider’s routers, and route changes between the

physically-separated subnets do not rely on the ei_check mechanism.

For network planning consider the below issues:

 CS Elements Layout - Normal Operation. The X1-CSP platform includes all the real-time call

control elements in one machine. It is recommended to have all the active elements on one

server and the standby elements on the other. This layout provides high performance CSP;

lower processing time and minimal bandwidth consumption, as shown below:

ControlSwitch Installation Guide

 Dialogic Inc. Proprietary Page 17

Note:

PE and EC operate in Active-Active mode, compared to all other elements that run in Active-Standby mode. PE load sharing is

optional, and SEEs may be configured to work with a single PE only. The EC pair works by default in Active-Active mode, and all

elements send events to both ECs simultaneously.

 CS Elements Layout - Worst-Case Scenario. In order to plan and allocate IP network bandwidth

that ensures solid and stable performance and functionality, the worst-case scenario should be

considered. From a bandwidth consumption perspective, the worst-case scenario is where

several active elements are running on one X1-CSP platform and the rest are running in the

mate X1-CSP platform. This may be initiated by manual failover used for maintenance

operations or automatic failover to overcome some issue in the element itself:

A geographically dispersed CS requires dual independent subnets between the locations. Each location

requires a primary and secondary CS subnet. The two primary and two secondary subnets must be

inter-connected independently, as shown below:

ControlSwitch Installation Guide

 Dialogic Inc. Proprietary Page 18

If a single interconnecting network is used, an outage on that network greater than three seconds

would begin to degrade call processing services, interrupt the voice path, and waste customer network

resources because of improper status information.

ControlSwitch Installation Guide

 Dialogic Inc. Proprietary Page 19

IP Ports Usage

Dialogic ControlSwitch Installation guide

Dialogic ControlSwitch Installation guide

Dialogic ControlSwitch Installation guide

Related papers

Other documents