Dialogic ControlSwitch Installation guide
- Type
- Installation guide
Copyright and Legal Notice
Copyright © 2013-2015 Dialogic Corporation. All Rights Reserved. You may not reproduce this document in whole or in part without permission
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 de la 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, ControlSwitch, I-Gate, Network Fuel, Mobile Experience
Matters, 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 de la 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
Revision#
Version Date
Comments
01
April 2013
Updated for Release 5.9.1.10
02
April 2015
Updated for Release 5.10.2
Refer to www.dialogic.com for product updates and for information about support policies, warranty
information, and service offerings.
ControlSwitch (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 3
Table of Contents
INTRODUCTION ............................................................................................................................................ 5 1.
1.1 About this Guide ......................................................................................................................................... 5
PLATFORMS INSTALLATION .......................................................................................................................... 6 2.
2.1 EMS (AX1) .................................................................................................................................................... 6
2.2 DR-EMS (AX1) .............................................................................................................................................. 6
2.3 CDR (AX3) .................................................................................................................................................... 7
2.4 Call Processing Server (X1) .......................................................................................................................... 7
2.5 Policy Server (X2) ........................................................................................................................................ 7
2.6 DSE (X3) ....................................................................................................................................................... 8
2.7 LIDAP (X4) .................................................................................................................................................... 8
2.8 Service Node (X5) ........................................................................................................................................ 8
NETWORKING CONFIGURATION ................................................................................................................... 9 3.
3.1 IP Network Multi-Pathing (IPMP) ................................................................................................................ 9
3.2 Static Routes Setup ..................................................................................................................................... 9
3.3 ei_check script ........................................................................................................................................... 10
3.4 Policy-based Routing ................................................................................................................................. 10
NETWORKING GUIDELINES .......................................................................................................................... 11 4.
4.1 Protocol Considerations ............................................................................................................................ 11
4.2 Configuration Requirements/Consideration ............................................................................................. 11
Dual LAN Network................................................................................................................................. 11 4.2.1
Dual Independent WAN Network for CMI/SCTP................................................................................... 12 4.2.2
IPMP ...................................................................................................................................................... 12 4.2.3
Network Quality .................................................................................................................................... 12 4.2.4
4.3 Network Connectivity Recommendations ................................................................................................ 12
Dual Network Connectivity ................................................................................................................... 12 4.3.1
X1 Platform Network Connectivity ....................................................................................................... 13 4.3.2
IBCF-ALG Platform Connectivity ........................................................................................................... 15 4.3.3
4.4 Bandwidth Requirements ......................................................................................................................... 16
CS Elements Layout - Normal Operation .............................................................................................. 16 4.4.1
CS Elements Layout - Worst-Case Scenario .......................................................................................... 16 4.4.2
4.5 Network Planning ...................................................................................................................................... 17
4.6 IP Ports Usage ........................................................................................................................................... 18
General Information ............................................................................................................................. 18 4.6.1
EMS ....................................................................................................................................................... 18 4.6.2
PE .......................................................................................................................................................... 19 4.6.3
SEE ........................................................................................................................................................ 19 4.6.4
CDR ....................................................................................................................................................... 19 4.6.5
CCP ........................................................................................................................................................ 20 4.6.6
ICE ......................................................................................................................................................... 20 4.6.7
EC-ERS ................................................................................................................................................... 20 4.6.8
SSE ......................................................................................................................................................... 21 4.6.9
ControlSwitch (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 4
BGCE ................................................................................................................................................. 21 4.6.10
NE to EMS or CDR Traffic .................................................................................................................. 21 4.6.11
4.7 MGCP Network Algorithms ....................................................................................................................... 22
Interface Selection ................................................................................................................................ 22 4.7.1
Source IP Selection and Retransmission ............................................................................................... 22 4.7.2
Algorithm Results .................................................................................................................................. 23 4.7.3
Default Timers/Retransmissions ........................................................................................................... 23 4.7.4
CCP Initiated Message Timers............................................................................................................... 24 4.7.5
Successful AUEP .................................................................................................................................... 24 4.7.6
AUEP Re-Transmit Flow ........................................................................................................................ 26 4.7.7
AUEP Retransmit Case .......................................................................................................................... 27 4.7.8
ControlSwitch (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 5
Introduction 1.
The document is provided for administrative and management-level users who install the ControlSwitch
System (CS). Users must be familiar with the following tasks:
Running telecommunications networks and monitoring equipment
Configuring Sun Solaris platforms
Using Extensible Markup Language (XML)
Users who maintain the CS should be familiar with the following additional tasks, as appropriate:
Using the Oracle Database
Running web servers
Configuring NT platforms
1.1 About this Guide
The CS installation is provided in the following stages.
Hardware and Operating System. Covered in the ControlSwitch Platform Specifications and
Deployment Guide.
Platforms Installation and Networking Configuration. Covered in this document.
System Provisioning. Covered in ConrolSwitch User's Manual document set.
This guide includes:
Platforms Installation
Networking Configuration
Networking Guidelines. Provides guidelines on networking and CS connectivity.
ControlSwitch (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 6
Platforms Installation 2.
This chapter describes the installation procedure for the ControlSwitch System on X86 platforms.
License key files based on host-ID contain information about the type of application to be installed on
the platform. License files are required for this installation; contact Dialogic Customer Support to obtain
license key files.
The following applications are currently supported for X86 platforms:
EMS (AX1)
DR-EMS (AX1)
CDR (AX3)
Call Processing Server (X1)
Policy Server (X2)
DSE (X3)
LIDAP (X4)
Service Node (X5)
2.1 EMS (AX1)
1. Obtain:
CS 5.10.2 software.
Oracle11g Server Enterprise Edition (Version 11.2.0)
Oracle Apex and Glassfish software
License key file for the platform
CS application license
CrystalClear license
2. Transfer the above software to the server.
3. Unzip and untar the CS software to /reserved/software directory.
4. Go to /reserved/software/<CS software>/Install directory, and run the install script:
./install
5. Follow the script's instructions, based on the Scope of Work (SOW).
6. Go to /opt/IPVRdbutl/dbbackup/, and run the mainmenu.sh script for setting up a backup.
Dialogic highly recommends an online (hot) backup for EMS databases on a regular basis (as often
as daily).
2.2 DR-EMS (AX1)
Note:
The Primary EMS must be installed with the Disaster Recovery feature enabled. See the Dialogic® EMS Disaster Recovery
Feature Guide for additional information.
1. Obtain:
ControlSwitch (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 7
CS 5.10.2 software.
Oracle11g Server Enterprise Edition (Version 11.2.0)
Oracle Apex and Glassfish software
License key file for the platform
2. Transfer the above software to the server.
3. Unzip and untar the CS software to /reserved/software directory.
4. Go to /reserved/software/<CS software>/Install directory, and run the install script:
./install
5. Follow the script's instructions, based on the Scope of Work (SOW).
6. After installing DR EMS, procedures need to be run on the Primary EMS to finish the EMS Disaster
Recovery setup. See the Dialogic® EMS Disaster Recovery Feature Guide for additional information.
2.3 CDR (AX3)
1. Obtain:
CS 5.10.2 software.
Oracle11g Server Enterprise Edition (Version 11.2.0)
License key file for the platform
2. Transfer the above software to the server.
3. Unzip and untar the CS software to /reserved/software directory.
4. Go to /reserved/software/<CS software>/Install directory, and run the install script:
./install
5. Follow the script's instructions, based on the Scope of Work (SOW).
2.4 Call Processing Server (X1)
1. Obtain:
CS 5.10.2 software.
License key file for the platform
2. Transfer the above software to the server.
3. Unzip and untar the CS software to /reserved/software directory.
4. Go to /reserved/software/<CS software>/Install directory, and run the install script:
./install
5. Follow the script's instructions, based on the Scope of Work (SOW).
2.5 Policy Server (X2)
1. Obtain:
CS 5.10.2 software.
License key file for the platform
2. Transfer the above software to the server.
3. Unzip and untar the CS software to /reserved/software directory.
4. Go to /reserved/software/<CS software>/Install directory, and run the install script:
ControlSwitch (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 8
./install
5. Follow the script's instructions, based on the Scope of Work (SOW).
2.6 DSE (X3)
1. Obtain:
CS 5.10.2 software.
Oracle11g Server Enterprise Edition (Version 11.2.0)
License key file for the platform
2. Transfer the above software to the server.
3. Unzip and untar the CS software to /reserved/software directory.
4. Go to /reserved/software/<CS software>/Install directory, and run the install script:
./install
5. Follow the script's instructions, based on the Scope of Work (SOW).
2.7 LIDAP (X4)
This chapter provides installation information for the Lawful Intercept Data Access Point (LIDAP) for the
Malvine and Verint/Oasis solutions.
1. Obtain:
CS 5.10.2 software.
Oracle11g Server Enterprise Edition (Version 11.2.0)
License key file for the platform
2. Transfer the above software to the server.
3. Unzip and untar the CS software to /reserved/software directory.
4. Go to /reserved/software/<CS software>/Install directory, and run the install script:
./install
Note:
To exit the Installer session at any time, press the [Ctrl] and [c] keys simultaneously. To re-start the Installer session, run
the Installer script. The script will continue the installation from the most recently completed section
5. Follow the script's instructions, based on the Scope of Work (SOW).
2.8 Service Node (X5)
1. Obtain:
CS 5.10.2 software.
License key file for the platform
2. Transfer the above software to the server.
3. Unzip and untar the CS software to /reserved/software directory.
4. Go to /reserved/software/<CS software>/Install directory, and run the install script:
./install
5. Follow the script's instructions, based on the Scope of Work (SOW).
ControlSwitch (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 9
Networking Configuration 3.
3.1 IP Network Multi-Pathing (IPMP)
IPMP is a facility used to provide fault-tolerance and load balancing with network interface cards (NIC).
With IPMP, two or more NIC cards are dedicated for each network to which the host connects. One of
these interfaces is marked as the primary, and the remainder are secondary interfaces. In the event of a
failure of the primary interface, the system will automatically switch to using the secondary interface
instead. IPMP is relevant for ICE, CCE, LSG/RSG, and SSE.
To configure the IPMP, follow the below steps:
1. Select two interfaces on the CSP/Service node platforms for the IPMP configuration. IPMP should
not be configured on the CMI interfaces.
2. For the selected interfaces edit the relevant interface hostname file: /etc/hostname.<interface-
name>:
<IPMP IP address> group <IPMP group name> up
group <IPMP group name> standby up
Note:
It is mandatory to use two sets of interfaces on the platform in case IPMP is used.
For this solution to work, verify that in the Network Elements > M3UA > ASPs window the ASP IP address for which the IPMP
is configured should be set to 0.0.0.0.
3.2 Static Routes Setup
For internal communication, primary and secondary network-based static routes must be used. For
external communication, static routes are recommended for all the CS platforms connectivity with
external entities (rather than using default routes).
Note:
Default routes can be configured on ICE, IBCF-ALG, EMS, DSE, and CDR platforms in order to avoid configuring a large number
of static routes to remote peers.
For CMI-SCTP, a network cross-over may occur if all of the following conditions are met:
The default routes are configured,
The routing table on the Sun platform uses a default route, and
The application is using the secondary interface, which is unavailable.
In this case, the source IP address (if the packet uses the primary interface) will be the primary IP
address and not the secondary IP address of the Sun Platform. This will cause the network cross-over to
occur. It is recommended to either (1) remove default routes or (2) disable cross-over routes in the
routers.
Note:
To exit the Installer session, press the [Ctrl] and [c] keys simultaneously. To re-start the Installer session, run the Installer script.
The script will continue the installation from the most recently completed section.
Use the following instructions to install the Static Routes Setup option:
ControlSwitch (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 10
3. Go to /etc/rc2.d/ directory.
4. Add the required routing information to S70staticroutes based on the below template:
<Destination IP address> <gateway-IP address>
5. Select option 5, Static Routes Setup, and follow the scrip's instructions.
3.3 ei_check script
Ei_check script allows a ControlSwitch Network Element to communicate to another network-entity
that is connected to a third network (for example, CCP communicating to MG network). Ei_check checks
the interface status and based on availability changes the routing table on the ControlSwitch platform
to use either the primary network router or the secondary network router. Only an X1 platform that
hosts SEE, CCP, ICE, SPICE, PE, EC, ERS, QOS, SSE, MRC, BGC, LSG and RSG may require the enabling of
ei_check script.
1. Go to the /opt/IPVRmisc/ei_tools directory
2. Add the required routing information to cfg.<interface-name>, based on the below template:
<Destination IP address> <gateway-IP address>
3.4 Policy-based Routing
Please refer to Service_Bulletin_RSIP Routing Procedure document.
ControlSwitch (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 11
Networking Guidelines 4.
This chapter provides network considerations and requirements for using ControlSwitch System High-
Availability architecture. The following information is included:
Protocol Considerations
Configuration Requirements/Consideration
Network Connectivity Recommendation
Bandwidth Requirements
Network Planning
4.1 Protocol Considerations
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)
FTP*/
Telnet
ODBC/
JDBC
AX1-EMS
x
-
-
-
-
-
-
-
x
AX2- EMS-CDR
x
-
-
-
-
-
-
x
x
AX3 - CDR
x
-
-
-
-
-
-
x
-
X1 - CSP
x
x
x
x
x
x
x
x
-
X2 - Policy
x
-
-
-
-
-
-
-
-
X3 - DSE
x
-
-
-
-
-
-
-
x
D - IBCF-ALG
x
-
-
x
x
-
-
-
-
X4 - LIDAP
x
-
-
-
-
-
-
-
x
X5 - Service Node
x
-
-
x
-
-
-
-
-
* SCP if ssh is used
The following sections describe the network connectivity recommendations.
4.2 Configuration Requirements/Consideration
Dual LAN Network 4.2.1
The ControlSwitch System architecture requires all elements to be connected to a dual LAN topology.
Dual LAN for the ControlSwitch System provides an extra level of resiliency between real-time call
processing elements and provides the following benefits:
Network failure between CCP and CCP is transparent. The system tries the second LAN before a
ControlSwitch EMS restart.
Network failure between EMS and any element is transparent. The system tries the second LAN
before a ControlSwitch EMS.
If a network failure occurs between CCP and EC, no CDR data is lost.
A dual LAN eliminates a the single point of failure in the network.
ControlSwitch (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 12
Dual Independent WAN Network for CMI/SCTP
4.2.2
Two independent WAN networks are required if the ControlSwitch System is deployed in a
geographically redundant mode. This arrangement addresses a mandatory requirement of 0 seconds
failover time between the WAN networks, which is achieved by having at least one network always
available between two geographical sites. Independently, each network can have impairments separate
from the other and still function properly. If a case occurs where the primary and secondary networks
are impaired simultaneously for longer than 3 seconds, an outage on the network is likely. Two
independent WAN networks can be deployed by using two separate WAN service providers when using
a third party transmission provider.
IPMP 4.2.3
IP Network Multi-Pathing (IPMP) is a facility used to provide fault-tolerance and load balancing with
network interface cards (NIC). With IPMP, two or more NIC interfaces are dedicated for each network to
which the host connects. One of these interfaces is marked as the primary, and the remaining are
marked as secondary. In the event of a failure of the primary interface, the system will automatically
switch to the secondary interface.
IPMP interfaces should not be shared with non-IPMP interfaces.
Network Quality 4.2.4
ControlSwitch System element communication depends on high quality network conditions (less than
200 ms round trip delay and less than 2% packet loss).
4.3 Network Connectivity Recommendations
Dual Network Connectivity 4.3.1
This network layout uses two interfaces (for example, igb0, igb1). Each interface is connected to
different network as describe above, and IPMP and ei_check are not enabled. The following network
connectivity should be used in these ControlSwitch System elements:
AX1 – EMS / EMS-DR
AX2 – EMS & CDR
AX3 – CDR
X2 – Policy
ControlSwitch (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 13
X3 – DSE
X1 Platform Network Connectivity 4.3.2
X1 platform hosts different call control elements, such as host SEE, CCP, ICE, SPICE, PE, EC, ERS, QOS,
SSE, MRC, BGC, LSG and RSG. The X1 platform communicates with many protocols and networks, such
as:
Other ControlSwitch System elements via CMI
Media Gateways products via MGCP, IUA, M3UA, H.248
SIP/H.323 peering networks
As a result, there are several options to an attached X1 platform to the network.
4.3.2.1 X1 Platform Network Connectivity – Option 1 (Default)
This option should be used as default network connectivity for X1 platforms.
In this option, X1 does not host BGC or MRC, and H.248 protocol is not in use. The X1 platform uses four
network interfaces. The following table and diagram describes the usage of the different interfaces:
Interfaces
Protocols
IPMP
Ei_check
NIC0+NIC1
CMI
no
no
NIC2+NIC3
SIP, H.323, MGCP, IUA, M3UA
yes
no
ControlSwitch (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 14
4.3.2.2 X1 Platform Network Connectivity—Option 2
This option supports the case in which X1 is equipped with BGC and MRC and H.248 protocol support is
needed.
In this case, CMI and H.248 protocol run on the same ports, and ei_check is enabled. In this option, four
network interfaces are in use. The following table and diagram describe the usage of the different
interfaces:
Interfaces
Protocols
IPMP
Ei_check
NIC0+NIC1
CMI, H.248
no
yes
NIC2+NIC3
SIP, H.323, MGCP, IUA
yes
no
4.3.2.3 X1 Platform Network Connectivity—Option 3
In this option, four network interfaces are in use. The following table and diagram describes the usage
of the different interfaces:
Interfaces
Protocols
IPMP
Ei_check
NIC0+NIC1
CMI, M3UA, H.248, MGCP, IUA
no
yes
NIC2+NIC3
SIP, H.323
yes
no
ControlSwitch (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 15
IBCF-ALG Platform Connectivity 4.3.3
IBCF-ALG network connectivity guidelines are as follows:
IBCF-ALG and ICE must be on the same subnet (Release 5.7)
IBCF-ALG (SIP) and ICE may be in different subnets, IBCF-ALG (H.323) and ICE must be on the
same subnet (Release 5.8.1)
IBCF-ALG primary and secondary platforms must be on the same subnet for Floating-IP to work
For 5.8.1+, when SIP-ICE and ALG are in different subnets/geography HSRP/VRRP is required
HSRP/VRRP is Mandatory for WAN/Optional for LAN and should
IBCF-ALG uses 6 network interfaces so additional NIC card should be installed in the Oracle/Sun
T2000 server. The following table and diagram describes the usage of the different interfaces
for IBCF-ALG:
Interfaces
Protocols
IPMP
Ei_check
Floating IP
NIC0+NIC1
CMI
no
no
no
NIC2+NIC3
Internal trusted SIP, H.323 to/from ICE
yes
no
no
NIC4+NIC5
External un-trusted SIP, H.323 to/from VSAP
yes
no
yes
ControlSwitch (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 16
4.4 Bandwidth Requirements
This section provides the IP network bandwidth requirements for ControlSwitch deployment for X4270
servers. Bandwidth measurements for normal operation and worst-case scenarios for TDM and IP traffic
are included.
CS Elements Layout - Normal Operation 4.4.1
The X1-CSP (ControlSwitch platform running on X4270 servers) was designed to include all real-time call
control elements in one machine. The recommendation for normal ControlSwitch platform operation is
to have all active call control elements (CCE, ICE, PE, SE, etc.) in one server and standby/redundant
elements in the other server. This layout provides high performance CSP, lower processing time and
minimal bandwidth consumption.
The following figure shows the ControlSwitch element layout in normal operation:
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 4.4.2
The bandwidth requirements in normal operation are minimal because all active call control elements
(with the exception of PE and EC) reside in the primary X1-CSP platform, and inter-element traffic stays
within the X1 server. 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. The following figure shows the ControlSwitch element layout for a bandwidth worst-case
scenario:
ControlSwitch (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 17
4.5 Network Planning
A geographically dispersed ControlSwitch System requires dual independent subnets between the
locations. Each location requires a primary and secondary ControlSwitch System subnet. The two
primary and two secondary subnets must be inter-connected independently, shown below.
Dual Backbone VoIP Connection
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 (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 18
4.6 IP Ports Usage
General Information 4.6.1
The following table lists the IP port ranges for each element.
Element
Port Range
Start
End
CCPA
13000
13999
CCE
14000
20999
NEA
10700
10999
NE*
21000
35999
SS7A
9500
9999
DGMS
3000
3250
TCAP Client
5000
5250
TCAP Agent
6000
6250
REA
11000
11999
RE (PE)
12000
12999
EC Agent
8300
8499
EC
18000
18999
CDR Agent
7300
7499
CDR
19000
19999
CCL Logger
7500
7550
*NE includes IBCF, SSE, ISUPSE, TCAPSE, SEE, ICE, SPICE, ERS, LIDAP, DSE, BGCE, MRCE, and so forth.
EMS 4.6.2
The following table lists the IP port information for EMS.
Start
End
Type
Description
80
80
HTML
EMS GUI access -- Java based
9000
9000
Oracle Forms
EMS GUI access -- Oracle forms based
7000
20000
UDP
Proprietary SCTP communications
161
163
UDP
SNMP
TCP
Telnet
TCP
SSH
1521
1521
UDP
Oracle DB
10500
10999
UDP
PEMGR
15000
15050
UDP
DAS
9000
UDP
SCE
13000
UDP
PSMON
18000
UDP
Notif Manager
17000
UDP
TRM
1091
UDP
FMS_JNDI_PORT
ControlSwitch (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 19
11000
UDP
SW_COORD_PORT_FMS
12000
UDP
SW_COORD_PORT_SNMP
10990
UDP
WEB_PORT_FMS
11500
UDP
FMS CMI Gateway
11990
UDP
WEB_PORT_SNMP
8000
UDP
TxMgr
8700
UDP
MML Handler
16000
UDP
Trap Receiver
17161
UDP
SNMP Brass Agent - Proxy port
17162
UDP
SNMP Emanate Master Agent - Proxy port
161
UDP
SNMP (REQ - RES) - Used by netsnmp, snmpd
162
UDP
SNMP Trap - Used by netsnmp, snmpd
14000
UDP
Syslog Manager
8182
TCP
Tomcat
7000
7499
UDP
CMI Gateway or Policy Test Tool
7500
7550
UDP
CCL Logger or Local Logger
37000
37999
UDP
Independent DAS (on aux-ems)
36000
36999
UDP
Independent Archive Logger (only for aux-ems)
PE 4.6.3
The following table lists the IP port information for PE.
Start
End
Type
Description
11000
11999
UDP
Proprietary SCTP - REA
12000
12999
UDP
Proprietary SCTP - RE
7500
7550
UDP
Proprietary SCTP - CCL Logger
TCP
Telnet
TCP
SSH
SEE 4.6.4
The following table lists the IP port information for SEE.
Start
End
Type
Description
10700
10999
UDP
Proprietary SCTP - For NEA
21000
35999
UDP
SCTP
7500
7550
UDP
Proprietary SCTP - CCL Logger
TCP
Telnet
TCP
SSH
CDR 4.6.5
The following table lists the IP port information for CDR.
Start
End
Type
Description
7300
7499
UDP
Proprietary SCTP CDRE Agent
ControlSwitch (v.5.10.2) Installation Guide
Dialogic Inc. Proprietary Page 20
19000
19999
UDP
Proprietary SCTP
7500
7550
UDP
Proprietary SCTP - CCL Logger
TCP
Telnet
TCP
SSH
TCP
FTP
TCP
SCP
1521
1521
UDP
Oracle DB
CCP 4.6.6
The following table lists the IP port information for CCP.
Start
End
Type
Description
2000
3000
UDP
MGCP communication with MGW*
9000
10000
SCTP
IUA/SCTP communication with MGW**
13000
13999
UDP
Proprietary SCTP - CCPA
14000
20999
UDP
Proprietary SCTP
7500
7550
UDP
Proprietary SCTP - CCL Logger
TCP
Telnet
TCP
SSH
*No specific range; this is just a recommendation.
**No specific range; 9900 is typically the default IUA port as per the RFC.
ICE 4.6.7
The following table lists the IP port information for ICE.
Start
End
Type
Description
1720
1720
TCP
H.323 signaling
5060
5060
UDP
SIP signaling
2000
3000
TCP/UDP
SIP and H.323 non-standard signaling ports
10700
10999
UDP
Proprietary SCTP - NEA
21000
35999
UDP
Proprietary SCTP
7500
7550
UDP
Proprietary SCTP - CCL Logger
TCP
Telnet
TCP
SSH
35000
68000
TCP
H.323 signaling
EC-ERS 4.6.8
The following table lists the IP port information for EC-ERS.
Start
End
Type
Description
8300
8499
UDP
Proprietary SCTP EC agent
18000
18999
UDP
Proprietary SCTP EC
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
-
1
-
2
-
3
-
4
-
5
-
6
-
7
-
8
-
9
-
10
-
11
-
12
-
13
-
14
-
15
-
16
-
17
-
18
-
19
-
20
-
21
-
22
-
23
-
24
-
25
-
26
-
27
Dialogic ControlSwitch Installation guide
- Type
- Installation guide
Ask a question and I''ll find the answer in the document
Finding information in a document is now easier with AI
Related papers
-
Dialogic ControlSwitch PRI Ring-back User guide
-
-
-
-
-
-
-
-
-
