Environment

ControlSwitch System Requirements and
Environment Guide
Release 5.5.5
Veraz Networks, Inc.
926 Rock Ave. Suite 20,
San Jose, CA 945131
phone: (408) 750-9400

E-mail: info@veraznet.com
www.VerazNetworks.com
Veraz Networks ControlSwitch and the Veraz Networks corporate logo are
trademarks of Veraz Networks, Inc.
All other trademarks are the property of their respective owners.
Revision record: <ControlSwitch System Requirements and Environment Guide >

Pub. Date Update Description
Rev.
01 June-03 First edition and printing. Ver. 5.4.5

02 March-04 Update complying with Ver.5.5.0
03 July-04 Update complying with Ver. 5.5.1
04 Sep-04 Update complying with Ver. 5.5.2
05 May-05 Update complying with Ver. 5.5.3
06 Sep-05 Update complying with Ver. 5.5.4
07 Nov-05 Update complying with Ver. 5.5.5
Publication No. <0306555-01>
Copyright © 2000, 2001, 2002, 2003, 2004, 2005 Veraz Networks Inc. All rights reserved.
Information in this document is subject to change without notice.
November, 2005
Contents
Preface
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Assumption) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii
Chapter 1 Deploying the System

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
Application Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
ControlSwitch Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
Additional Software (Included) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
Web Browser (Not Included). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9
Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
Host Platform Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
External Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–13
SS7 Signalling Interface Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–14
Supported Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–15
Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–16
Chapter 2 Planning Installation

Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Protecting the EMS Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2
Veraz Networks ControlSwitch Requirements and Environment Guide iii

Dual Lan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
Planning a Rack Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
Planning For Your Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7
Site Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7
Platform Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9
Network Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Connecting the Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11
Cable Pin Outs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13
Appendix A Site Survey

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–2
Site Survey/Pre-installation Questionaire . . . . . . . . . . . . . . . . . . . . . . . . . A–2
Veraz Networks Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–2
Customer’s Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–3
Technical Personnel Contact List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–3
Site Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–4
Site Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–6
Equipment Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–8
Equipment Floor Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–11
Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–13
System Power and Cooling Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . A–15
Appendix B Platform Planning

Worksheet for Sun Netra 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–2
Worksheet for Sun Netra 240 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–3
Worksheet for SunFire240 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–4
Worksheet for External Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–5
System Power and Colling Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . B–6
Host Name and IP Address Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–7
Cable Estimation Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–8
Appendix C Network Planning

IP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–2
IP Address Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–4
Digital Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–6
T1/E1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–7
DS3 Interace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–7
STMF1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–8
Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–9
iv Veraz Networks ControlSwitch Requirements and Environment Guide

SS7 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–10
Trunks and Trunk Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–12
Numbering and Dialing Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–13
Trunk Groups and Dialing Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–14
Special Number Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–15
Routing Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–16
Routing Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–16
Routing Profile Assignement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–16
CDRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–17
Appendix D Staging Process

Receive Platform, Gateway Chassis, and Components . . . . . . . . . . . . . . . . . D–2
Building Gateway Systemst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–2
Build ControlSwitch Platform Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–2
Installing and Configuring the Operating System Software . . . . . . . . . . . . . D–3
Installing the ControlSwitch Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–3
ControlSwitch Initial Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–4
I-Gate Provisioning from XMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–4
Integrated System Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–5
Pack and Shipt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–5
Glossary of Terms
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glossary–1
Index
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index–1
Veraz Networks ControlSwitch Requirements and Environment Guide v

:
vi Veraz Networks ControlSwitch Requirements and Environment Guide

List of Figures
Chapter 1 Depolying the System

Central System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5
Installation Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8

Netra 240 Rack Face Plant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5
Rack Configuration Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Dual Backbone VoIP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9
Veraz Networks ControlSwitch Requirements and Environment Guide vii

viii Veraz Networks ControlSwitch Requirements and Environment Guide
Preface
This Guide provides detailed instructions for installing the ControlSwitch. The following
topics are included in this preface.
• Audience
• Assumptions
• Organization
• Documentation Set
• Documentation Conventions
Veraz Networks ControlSwitch System Requirements and Environment Guide ix

:
Audience
This guide is written for system administrators, engineers and operators who will install
and configure the ControlSwitch.
Assumptions
Users of this guide must be familiar with the following tasks:
• running telecommunications networks and monitoring equipment
• configuring Sun Solaris platforms
• configuring IP Networks
• using Extensible Markup Language (XML)
Users who will maintain the ControlSwitch should be familiar with the following addi-
tional tasks, as appropriate:
• using the Oracle Database
• running web servers
• configuring NT platforms
Organization
This guide is organized as follows:
• Chapter 1, “Deploying the System,” describes the ControlSwitch hardware and soft-
ware system requirements.
• Chapter 2, “Planning Installation,” describes how to plan for your site and to install
and connect hardware.
• Appendix A, “Site Survey,” provides blank worksheets for gathering required infor-
mation before starting an installation.
• Appendix B, “Platform Planning,” provides blank worksheets for gathering required
information for platform planning.
• Appendix C, “Network Planning,” provides blank worksheets for gathering required
information for network planning.
• Appendix D, “Staging Process,” provides details on the staging process.
• Glossary of Terms
• Index
x Veraz Networks ControlSwitch System Requirements and Environment Guide

Documentation Set
Documentation Set
The ControlSwitch documentation set includes the following publications:
• ControlSwitch System Product Description Document
The ControlSwitch System Product Description Document provides a description of
the ControlSwitch features and functionality.
• ControlSwitch System Requirements and Environment Guide
The ControlSwitch System Requirements and Environment Guide provides hardware,
software, and network requirements information.
• ControlSwitch Installation Guide
The ControlSwitch Installation Guide provides instructions on how to install, upgrade
and re-install the ControlSwitch software.
• ControlSwitch Provisioning Guide
The ControlSwitch Provisioning Guide provides instructions on how to provision a
new ControlSwitch.
• ControlSwitch Reference Guide
The ControlSwitch Reference Guide provides details on the EMS GUI screens and
field definitions.
• ControlSwitch Maintenance Guide
The ControlSwitch Maintenance Guide provides instructions for periodic mainte-
nance activities, such as back-up and making changes to the initial setup.
• ControlSwitch Lawful Intercept Guide
The ControlSwitch Lawful Intercept Guide provides instructions and configuration
details for the Veraz Networks Lawful Intercept Solution.
• EMS Disaster Recovery Guide
The EMS Disaster Recovery Guide provides detailed instructions for the Veraz
Networks Disaster Recovery feature.
• ControlSwitch Release Notes
The ControlSwitch Release Notes provide information on new features, changes from
the previous release, and any known issues.
• ControlSwitch Patch Release Notes (if applicable)
The ControlSwitch Patch Release Notes provide information on issues resolved from
the previous release, and instructions on how to apply the patch.
Veraz Networks ControlSwitch System Requirements and Environment Guide xi

:
Online Documentation
The following PDF files of the ControlSwitch documentation guides that make up the
ControlSwitch documentation set can be found in the /cdrom/cdrom0/doc directory:
• pdd.pdf
• environment.pdf
• installation.pdf
• provisioning.pdf
• maintenance.pdf
• lidap.pdf
• reference.pdf
• disasterrecovery.pdf
• relnote.pdf
• patch.pdf
After installation of your ControlSwitch software, these same PDF files of the
ControlSwitch documentation guides that make up the ControlSwitch documentation set
can be found by selecting Documents from the Veraz View login display shown in the
following figure.
Note To view PDF format files, you must have an Adobe Acrobat Reader.
See http://www.adobe.com for information on obtaining the Adobe Acrobat
Reader software.
xii Veraz Networks ControlSwitch System Requirements and Environment Guide

Documentation Conventions
Documentation Conventions
The following typographical and style conventions are used in this guide.
Table i-1 Typographical Conventions
Convention Description
\, backslash Designates a break in a continuous line in a code example or command line

example. You may omit the backslash and type as a single line.
[ ], brackets Keyboard keys.
<text in angle brackets> Variable values.
Initial Capitals Buttons, menu items, field names and network elements.
Times New Roman Italics Font Times New Roman font in italics designates emphasis in text.
Times New Roman Bold Font Times New Roman font in bold designates emphasis in text.
Courier Font Code examples, directory names, paths, and filenames used in text.
Courier Italics Font Courier font in italics designates variables used in code examples to represent
specific data for your system.
Courier Bold Font Courier font in bold designates text that must be typed.
Courier Italics Bold Font Courier font in italics bold designates variables in text that must be typed.
The following icons and emphasized notes are provided to aid you in reading this guide.
Note Provides important background information.

! Caution Describes implications of an irreversible step in a process that can

affect hardware or software systems.
a WARNING! Indicates a potential danger to hardware, software, or per-

sons.
The following variables are used in this guide to represent information that may vary
between host machines or networks.
Veraz Networks ControlSwitch System Requirements and Environment Guide xiii

:
Table i-2 Descriptions of Variables
Variable Description
domain.com Represents a domain name.
filename Represents the name of a file.
hostname Represents the name of a host computer.
icdr Represents the hostname of an Veraz Networks CDR element.
interfacename Represents the name of the network interface.
mountpointname Represents a mount point name.
n Represents a number from 0 to 9.
nnn.nnn.nnn.nnn Represents an IP Address or subnet mask.
PackageName Represents a software package name.
pid Represents a UNIX process identification number.
SIDname Represents an Oracle database SID name.
NewVersionNumber Represents the version number of new software to be installed.
OldVersionNumber Represents the version number of currently installed software.
versionnumber Represents a software or hardware version number.
mmddyy Represents a date, for example 000101 represents January 01, 2000.
yyyymmddHHMM Represents a time and date, a four digit year, month, day, hour and minute value.
xiv Veraz Networks ControlSwitch System Requirements and Environment Guide

Contact Information
Contact Information
For more information about Veraz Networks systems, please contact us:
Veraz Networks, Inc
926 Rock Avenue, Suite 20
San Jose, CA 95131
Phone: (408) 750-9400

Fax: (408) 546-0081
E-mail: info@veraznet.com
Web: http://www.Veraz Networks.com
Technical Assistance Centers (TAC)

USA
Tel: +1-214-6473397
Email: noc@cmsnoc.net
Israel
Tel: +972-3-9287077
Fax: +972-3-9268999
Veraz Networks ControlSwitch System Requirements and Environment Guide xv

:
xvi Veraz Networks ControlSwitch System Requirements and Environment Guide

Chapter 1 Deploying the System
This chapter describes the ControlSwitch System requirements. The following topics are
included in this chapter:
• Overview
• System Requirements
• Software Requirements
• Hardware Requirements
• Supported Equipment
• Installation Summary
Veraz Networks ControlSwitch System Requirements and Environment Guide 1–1

Chapter 1: Deploying the System
Overview
The ControlSwitch is comprised of the following network elements that must be installed
on the appropriate hardware platforms:
• Element Management System (EMS)
• Signaling Gateway (SG)
• Call Control Platform (CCP)
• Policy Server Element (PE)
• Event Collector (EC)
• Call Detail Record Generator Element (CDRE)
• IP Call Control Element (ICE)
• Service Execution Environment (SEE)
• ControlSwitch Platform (CSP)
The ControlSwitch elements are designed to be installed on separate UNIX platforms for
scalability and redundancy. Network level redundancy is supported on all elements. Most
elements are installed on at least two platforms for hardware redundancy. However, redun-
dancy does not apply to the EMS and CDRE. The CCP and SG can be installed together
on the same platform. The EC and CDRE can be combined as well, however if redun-
dancy is desired, then the EC must be installed on a separate host.
Application Configurations
This section illustrates the required configurations for supported ControlSwitch applica-
tions. See the ControlSwitch System Overview for more information about applications.
• Central System Configuration
• Distributed System Configurations
• Central System and Distributed Call Control Configurations
1–2 Veraz Networks ControlSwitch System Requirements and Environment Guide

Overview
Central System Configuration
Figure 1-1 Central Site
Distributed System Configurations

Figure 1-2 illustrates a sample ControlSwitch network layout for a Distributed Site. The
configuration supports redundancy for multiple Media Gateways. The second interface
displayed in this guide applies only to Media Gateways that support two network connec-
tions. (The AS5300 Media Gateway contains only one Ethernet interface.)
All elements of the ControlSwitch must be installed for this application. This example is
used throughout the installation instructions.

Figure 1-2 Distributed Site
Central System and Distributed Call Control Configurations

The ControlSwitch can be installed in distributed configurations that span multiple
geographic areas. Additional CCP, SG and EC elements can be installed as traffic and user
volume increase.
Note These are examples and elements can be distributed anywhere. How-
ever, distribution and network design will affect parameters such as latency.
Please contact one of our Professional Service Engineers (PSEs) for network
design assistance.

Overview
Media Gateways can also be installed in a distributed configuration. Additional Media

Gateways can also be installed as needed. See Figure 1-3.
Figure 1-3 Distributed Site

System Requirements
To install the ControlSwitch, your computer systems must meet the minimum require-
ments for each element. A summary of the minimum hardware and software requirements
is listed in Table 1-1.
Note For hot standby redundancy, failover, and failback capability, you must
have a minimum of eight UNIX servers in your ControlSwitch system. In this
release, hot standby redundancy does not apply to the EMS, CDRE or a com-
bined EC and CDRE.
Table 1-1 System Requirements Summary
Item Minimum Requirement Quantity
ControlSwitch Software ControlSwitch Software 1
SS7 Signalling Card Ulticom OMNI DGMS SS7 Signalling Card (PCI-bus 4-, 8- and 16-port T- 2
1/E-1 signalware adapter card)
Servers (host) Sun SPARC servers 8

Note: See “Host Platform Summary and Requirements” on page 1-10 for
additional information.
Disk Arrays Sun SE3120 or SE3320 2-4
Personal Computer (client) Windows or UNIX computer with a java-enabled web browser 1
Terminal Console terminal or laptop (for host configuration) 1
Internet browser supporting Netscape Communicator for Windows 1

frames and javascript. Netscape Communicator for UNIX
Internet Explorer for Windows

Software Requirements
This section provides descriptions of the required ControlSwitch software.
ControlSwitch Software
The Veraz Networks ControlSwitch software is provided on the Veraz Networks
ControlSwitch, Release 5.5.5 CD-ROM set. The software packages are listed in Table 1-2.
Table 1-2 ControlSwitch Software Packages
Package Name Platform Destination Description
IPVRccp CCE Call Control Element
IPVRcdr CDR CDR module
IPVRems EMS EMS module
IPVRtool EMS EMS Tools module
IPVRec EC EC module
IPVRmisc all hosts Setup module- misc. tools and scripts
IPVRrde RDE Routing Data Element
IPVRss7 SG SS7 Media Gateway Client
IPVRform EMS Oracle web forms
IPVRhtml EMS Oracle web HTML
IPVRnbi EMS SNMP north bound interface module
IPVRsmgr EMS SNMP manager module
IPVRdbutl EMS, CDR Oracle dataBase backup utility module
IPVRinst All Elements Software Installation
IPVRfms EMS Fault Management System
IPVRha EMS System Control Element
IPVRice ICE ICE module
IPVRsee SEE SEE module
IPVRcdrgui CDR CDR GUI
IPVRmed Mediation Mediation GUI
IPVRnea NE Agent NE Agents
IPVRregui Routing Routing Management GUI
IPVRsas Signaling Access Server Signaling Access Server

Table 1-2 ControlSwitch Software Packages
Package Name Platform Destination Description
IPVR3rdparty OpenSSL and TransNexus OpenSSL and TransNexus Application
IPVRers EC Event Relay Server
IPVRinapgui INAP GUI
IPVR Disaster Recovery
IPVlidap LIDAP Application
Additional Software (Included)

Table 1-3 lists additional software included with the ControlSwitch.
The Veraz Networks ControlSwitch, Release 5.5.5 CD-ROM contains the ControlSwitch
installer, the ControlSwitch software application and the Apache Server, Release 1.3.12
software.
The Solaris 8 Software (Release 02/04) CD-ROM set contains the required operating system software
for all elements.
The Veraz Networks Miscellaneous CD-ROM contains operating system patches. All of
the operating system patches will be applied automatically by a patch upgrade script.
The Oracle9 for Sun Sparc Solaris CD-ROMs contain database software for the EMS and
CDRE elements. All Oracle software will be automatically installed by the ControlSwitch
installer script.
The Oracle Forms and Reports, Release 6i for Sun Sparc Solaris CD-ROM contains forms
server software for the EMS. All Oracle software will be automatically installed by the
ControlSwitch installer script.
The OMNI CD-ROM contains Ulticom OMNI SS7 Stack and Patch software for the SG
element. All of the required SS7 packages and patches will be applied automatically
during installation.
Table 1-3 Additional Software (Included)
Item Minimum Requirement Quantity
Operating System Software Solaris 8 Release 02/04, Patch Level 2908, 117350- 1
08
Database Software Oracle9i 2
Web Forms Server Software Oracle Forms and Reports, Release 6i, Patch Level 4 1
Web Application Server Apache Server, Release 1.3.12 1

Software
SS7 Stack Software Ulticom OMNI SS7 Stack Software, 1

Release 8.02.sp4, ECN917

Web Browser (Not Included)

An Internet browser supporting frames and javascript is required to access the EMS. The
browser must be customized for use with the EMS as described in the ControlSwitch
Installation Guide.
• Netscape Communicator for Windows, 4.6.x (or higher), with Java Plug-in 1.1.3
• Netscape Communicator for UNIX, 4.0 (or higher), with Java Plug-in 1.1.2
• Internet Explorer for Windows 5.0.x (or higher), with Microsoft Virtual Machine
for Java

Hardware Requirements
This section provides detailed specifications on hardware listed in Table 1-3.
Host Platform Specifications

Table 1-4, describe the minimum computer type required for each network element and
the EMS Client. Table 1-5 and Table 1-6 provide additional details for each host type and
element.
Table 1-4 Host Platform Summary and Requirements
Element Host Type Quantity Requirements
EMS Sun Netra 240 1 • Disk mirroring is required. The

with Sun SE 3310 minimum required platform requires an
disk array external disk array.
• Hot standby redundancy does NOT
apply to an EMS.
CCP Sun Netra 240 2 • Two CCP elements are required for
redundancy.
SG Sun Netra 240 2 • Two SG elements are required for

redundancy.
PE Sun Netra 240 2 • A single PE supports multiple CCP

elements, however two PE elements are
required for element redundancy.
EC Sun Netra 240 with 2 • Can be installed together with the CDR
Sun SE 3310 disk on a single host. However, hot standby
array redundancy does NOT apply to a
combined EC and CDR.
• A single EC supports multiple CCP +
ICE elements, however two EC
elements are required for element
redundancy.
CDR Sun Netra 240, with 1 • Hot standby redundancy does NOT
Sun SE 3310 disk apply to a CDR, however disk mirroring
array can be implemented.
• Can be installed together with the EC, or
EMS on a single host. However, hot
standby redundancy does NOT apply to a
combined EC and CDR.
EMS Client Laptop, or PC or 1 • Can NOT be installed on the same

UNIX computer, for platform as any other element.
example, Sun Black
150

Table 1-4 Host Platform Summary and Requirements
Element Host Type Quantity Requirements
EMS (For Sun Netra 240 1 • Disk mirroring is required. The

Disaster with Sun SE 3310 minimum required platform requires an
Recovery) disk array external disk array.
• Hot standby redundancy does NOT
apply to an EMS.
EMS/CDR •
Combined
LIDAP • Can NOT be installed on the same

platform as any other element.
Table 1-5 Hardware Specification Summary for Host Platforms
Requirement SunFire 240 Sun Netra 240
CPUs One or two1.5 GHz One or two 1.5 GHz
RAM All elements 2 GB RAM; minimum All elements 2 GB RAM; minimum
Disk Space EMS - Requires six disk drives EMS - Requires six disk drives minimum,
minimum, five to seven disks five to seven disks prefered (73 GB).
prefered (73 GB). CCP and SG Separated-One 73 GB drive
CCP and SG Separated-One 73GB CDR - Requires four disks minimum (73
drive GB).
CDR - Requires four disks minimum All other elements require one disk (73
(73 GB). GB).
All other elements require one disk
(73 GB).
Disk Controllers Ultra 3 SCSI SE/LVD Ultra 3 SCSI SE/LVD
Built in IP Four 10/100/1000 Mb/sec Ethernet Four 10/100/1000 Mb/sec Ethernet

Network
Interface
Network Card None None
Operating Solaris 8 Release 02/04, Patch Level Solaris 8 Release 02/04, Patch Level 2908,
System 2908, 117350-08 117350-08
CD-ROM Drive CD-ROM or DVD drive CD-ROM or DVD drive
Serial Port Two RS-232 serial ports Two RS-232 serial ports
DC power -48/60VDC, two 400 watt modules

15 amp @ - 48 VDC
AC Power Two 90-264 VAC Optional with two 90-264 VAC
AC Service 6.1 amp 6.1 amp

Requirement

Table 1-5 Hardware Specification Summary for Host Platforms (Continued)
Requirement SunFire 240 Sun Netra 240
Maximum 400 watts 400 watts

Power
Consumption
Heat output
Operating -5 ºC to 45 ºC (23 ºF to 113 ºF) -5 ºC to 45 ºC (23 ºF to 113 ºF)

Temperature
Relative 5% to 93% 5% to 93%

Humidity,
Operating Non
condensing
Height 87.4 mm 87.4 mm

(3.44 in) (3.44 in)
2 RU 2 RU
Width 44.2 mm 44.2 mm

(17.4 in) (17.4 in)
Depth 508 mm 508 mm

(20 in) (20 in)
Weights 10 kg 10 kg
(22 lb) (22 lb)
Rack Mounting Standard-19inch, four post Standard-19inch, four post

Kit
Optional two post: Center mount Optional two post: Center mount 19inch or
19inch or 23 inches. 23 inches.
Or end slide mount four post end Or end slide mount four post end slide
slide mounts. mounts.
Table 1-6 Hardware Specification Summary for EMS Client

Requirement Laptop, PC or UNIX workstation (Ultra5)
CPUs One 1.6 GHz Pentium IV CPU, or 650 MHz RISC, or

SPARC CPU
RAM 256 MB RAM
Disk Space One 1 GB drive
Network Card Ethernet Network Interface Card
Operating System See Manufacturer Specifications.
CD-ROM Drive CD-ROM drive
Serial Port One RS-232 serial ports

Table 1-6 Hardware Specification Summary for EMS Client

Requirement Laptop, PC or UNIX workstation (Ultra5)
Standard Interfaces Keyboard, mouse, floppy drive
Video and Monitor SVGA video adapter (4 MB VRAM), SVGA monitor

(1024 x 768 capable)
External Storage
Table 1-7 provides a description of the external storage requirements for the EC and
CDRE.
Table 1-7 Hardware Specification for External Storage
Item Description
External Storage Type Sun Store Edge 3310 Storage Array
Disk Space Five to twelve 72 GB drives
Disk Controllers UltraSCSI3
DC power -48/60VDC nominal, two 360W, dual input

modules
AC Power Voltage 90-132 or 180-264 VAC (nominal)
AC Service Requirement Frequency 47 to 63 Hz Max. Operating current 5.0

amps Max. Surge current 22 amp peaks
Power Supply Two N+1 redundant, hot-swap
Heat output 260 Watts, 1092 BTU per hour
Operating Temperature 5C to 40C (41 F to 104F)
Height 17.5 cm (7.0 in.) 2 RU
Width 44.94 cm (17.6 in.)
Depth 53.25 cm (21.0 in.)
Weights Without disk drives 23.4 kg (51.5 lb.)

Fully loaded 2.3 kg (71 lb.)
Rack Mounting Kit Order 23, 19, or 24 inch rack kits or 600- mm
formats; front or center mounts

SS7 Signalling Interface Hardware

The SG requires SS7 Signalling cards to be installed in each SG platform. The following
types of SS7 Signalling cards are supported:
• Ulticom 4 link T1 card
The SG requires a dual private LAN connection and a serial port connection between the
two SG platform systems. The same requirement applie to a combined SG/CCP platform.
The Netra 240 and SFV 240 come with the required LAN and serial ports.
Figure 1-4 Dual Private LAN Connection
Requirements and Restrictions

Each SG host in a redundant pair must have an equal number of signaling cards. For
example, if the primary SG host contains two cards, then the secondary SG host must
contain two cards.
A maximum of three cards may be installed in each SG platform. For example, in a redun-
dant SG configuration (two host computers), the maximum number of cards allowed is
six.
For the serial connection, the Netra 240 serial cable an DB9 Null Modem Serial Cable
which is connected to the Serial B ports. For both platforms, the private LAN uses 2 RJ45
crossover cables.

Supported Equipment
Supported Equipment
The ControlSwitch is designed to interoperate with Media Gateways. An individual Media
Gateway can serve the VoIP, TDM Groomer, and ICD applications of the ControlSwitch.
The following Media Gateways are supported in this release:
Note For validated version information, see the ControlSwitch Release Note,
Release 5.5.5.
MGCP Media Gateways:

• Veraz Networks I-Gate 4000 Media Gateway
Xms: Version 3.4.0 Build 8
Software Version: Atlas 4.1.x
• Veraz Networks I-Gate 4000 Pro Media Gateway
Xms: Version 3.4.0 Build 8
Software Version: Mercury 2.2.x
• Cisco AS5300 Media Gateway (VoIP)
Software, Release 12.2(2)XB6;XB7;XB12, 12.2(5)a, 12.2(16), 12.2(11)T,
12.2(11)T2, 12.2(13)T;T1, 12.2(17). 12.3.1, 12.2(13)TB
Software, Release 12.2(2)XB;XB2;XB5;XB6;XB7;XB10;XB11;XB12,
12.2(11)T3, 12.2(13)T;T1;T2;T3, 12.2(15)T2;T5;T7, 12.3.5
12.2(11)T3, 12.2(13)T;T1;T2;T3, 12.2(15)T2;T5;T7, 12.3.5
• AudioCodes Mediant 2000: 4.60.018
H.323 GK and Gateways:

• Cisco 2620 Gatekeeper
Software, Release 12.2(2)XB;XB5;XB10, 12.2(6), 12.2(7)c, 12.2(13)T
Software, Release 12.2(2)XB;XB7, 12.2(8)T5, 12.2(10)B, 12.2(15)T8,
12.2(17)T1

Software, Release 12.2(2)XB;XB7, 12.2(8)T5, 12.2(10)B, 12.2(15)T8,

12.2(17)T1
• Cisco AS5300 Media Gateway (H.323)
Software, Release 12.2(2)XB6;XB7;XB12, 12.2(5)a, 12.2(16), 12.2(11)T,
12.2(11)T2, 12.2(13)T;T1, 12.2(17). 12.3.1, 12.2(13)TB
12.2(11)T3, 12.2(13)T;T1;T2;T3, 12.2(15)T2;T5;T7, 12.3.5
12.2(11)T3, 12.2(13)T;T1;T2;T3, 12.2(15)T2;T5;T7, 12.3.5
• Quintum
Media Servers:
• Cognitronics
Model-CX500 SW version 3.0(0.01)
• Convedia
Model CMS1000 SW version 3.7.1.2
MGCP IADs:
• Mediatrix:
• Audio Codes:
• Cisco ATAs:
SIP Call Agents:

• Vocal Data:
Software, Release 5.0
• Broadsoft
Software, Release 11.0
Lawful Intercept:
• Verint StarGate Mediation Device
• Verint Loop Device

Installation Summary
Installation Summary
The ControlSwitch includes an automated installation utility to enable installation of the
ControlSwitch software with minimal user intervention. Installation tasks for each
element are listed in the recommended order of use in this Guide. A typical installation
task flow is illustrated in Figure 1-5.
Note All tasks are required for a new installation.

The process includes the following tasks:
1. Checking hardware and software requirements.
2. Installing Hardware.
3. Installing the required operating system and patches on each host.
4. Installing ControlSwitch software.
5. Installing redundant elements.
6. Installing and Configuring a web browser.
7. Provisioning and Configuring the system.
8. Maintaining the system, (for example, start-up and shutdown, upgrade, re-install,
backup the system).

Figure 1-5 Installation Flowchart

This chapter describes how to install and set up hardware for the ControlSwitch. Use it to
install the ControlSwitch platform in your network rack and connect the appropriate
cables. The following topics are included in this chapter:
• Platform
• Protecting the EMS Database
• Dual LAN
• Planning a Rack Layout
• Planning For Your Site
• Site Planning
• Platform Planning
• Network Planning
• Connecting the Hardware
• Cable Pin Outs

Chapter 2: Planning Installation
Platform
The EMS (unless selected for disaster recovery) is a non-redundant element containing a
critical data base. The data base must be protected. The EMS element must be available to
manage the system.
There are three parts to data base protection:
• Mirroring the disk that contains the data base (/data or /u01,/u02,/u03).
• Backing up the data base on a regular basis (/backup).
• Archiving the transactions that occur between backups (/archive).
These three items must not reside on the same disk as any of the others to prevent a single
disk failure from compromising the ability to restore the data base.
Element availability is protected by mirroring the partitions on the root disk.(/ and swap
nms, reserved, archive).
Finally, another disk provides spare partitions to replace a failed mirror, which retains the
basic protections until the original failure is detected and repaired.
An additional EMS platform with the same or similar configuration of the primary EMS
platform is needed to support disaster recovery feature. High-speed network interface
and bandwidth between the primary and secondary platform are required for the data
transport. Sufficient disk space for the /archive and /backup location is also a requirement
for both EMS platforms.
Protecting the EMS Database

Protection of the EMS Database is profoundly important.
ALL deployed EMS systems MUST have the Veraz Backup Facility enabled to perform
periodic and regular Database backups.This is mandatory and should be enabled before
the completion of acceptance testing.
The Backup/Recovery scripts and programs are provided in the package:
/opt/IPVRdbutl.
You can run mainmenu.sh script for the starting menu.The schedule should be decided
with customer input, but lack of that input should not prevent a reasonable schedule from
being enabled. Veraz Networks highly recommends an online (hot) backup for EMS data-
bases on a regular basis (as often as daily) and use of cold backup before upgrades to the
elements.

Planning a Rack Layout
Beyond this, the movement of the Database backup files to another system or magnetic
media by the customer is definitely encouraged. Adding a well known commercial soft-
ware agent to the EMS system should not present a problem. Care must be taken in ascer-
taining the experience and capability of the customer to perform this activity. Also, the
customer software can impact the performance of the EMS. No agent software has been
tested with the ControlSwitch and installation and upgrade procedures do not account for
such software.
Dual LAN
The ControlSwitch architecture requires all of the elements to be connected to a dual LAN
topology. (This also applies to geographically separated systems as in Figure 1-2 and
Figure 1-3.) Dual LAN for the ControlSwitch elements provides an extra level of resil-
iency between real time call processing elements such as CCP and EC, thereby protecting
customer revenue. The benefits of having a dual LAN are:
• Network failure between CCP - CCP is transparent. The system tries the second
LAN before restart by EMS.
• Network failure between EMS and any element is transparent. The system tries
the second LAN before restart by the EMS.
• Network failure between CCP and EC, no CDR data is lost.
• Eliminates the single point of failure.

Use the following diagrams to plan your hardware rack layouts:
Figure 2-1 illustrates a typical rack layout for a Netra 240. Refer to it when planning your
equipment rack layouts. Use the empty rack diagram in Figure 2-2 to make a brief sketch
and plan your rack layouts.

Figure 2-1 Netra 240 Rack Face Plan

Figure 2-2 Rack Configuration Planner

Planning For Your Site
Site Planning
When planing for your site the following external connections to the ControlSwitch and
LAN need to be figured out:
• Type of cable
• Length of cable
• Type of connectors
Clocks
The I-Gate 4000 PRO supports external clocking in T1 level. Two different external T1
clocks can be configured and connected to the TPSI card.
The I-Gate 4000 supports only NRZ G.703 2 or 1.5 mhz. It does not support T1 level. A
single external clock can be configured and connected to the GIBO card.
For example:
• CAT5 shielded
• RR102.02 to RR106.05, 06, 07
• 9 - 50 ft. CAT V shielded
LAN Uplinks
To connect the Platform LAN switches to the Backbone switches the following LAN
uplinks are required. (LAN Uplinks generally depend on customer supplied equipment.)
For example:
• RR106.08, 09 to RR104.10, 11
• 2 runs - 15 meters MM fiber
• LC/SC connectors
SS7 Signal Patch Panel to Signaling Gateways

SS7 Signal Patch panel require:
Ulticom cards RJ45 with connectors for RJ48.
For example:
RR100.06 to RR106.09
4 runs - 50ft shielded CAT V with RJ45 one end wired for RJ48, wire wrap other end.

STM1
STM1 requires the following:
SC Connector single mode fiber, for example:
• RR104.10 to RR1206.05
• 2- runs 15 meters SM fiber
• SC/SC connectors
I-Gate 4000 Pro

The I-Gate 4000 and the I-Gate 4000 Pro provides one redundant 1000BaseT fiber optic
and four 100 BaseT copper connections.
Port use is determined by bandwidth requirements and LAN topology.
For example:
• RR102.02 to RR106.05
• 2 runs - 20 meters MM fiber
• LC/SC connectors
• 2 run - 20 meters CAT5e
• RJ45-RJ45 connectors
Sun Netra Servers
Each ControlSwitch server has two connections to the platform LAN switches.
For Example:
• RR100.06 to RR106.05
• 24 runs - 20 meters CAT 5e
• RJ45-RJ45 connectors
Table 2-1 Host Name Requirements

Host Machine Requirement
SG or The host name of the primary SG must
SG and CCP combined be alpha-numerically less than the host
name of the secondary SG.
The host name must be lowercase,
alphanumeric, and unique.
The host name must contain eight
characters or less.
CCP, CDR, EC, EMS, and PE The host name must be alphanumeric
and unique.

Note Please refer to Appendix A for related forms
Platform Planning
LAN configuration requires the following information:
• Host Address space
• Host Name of servers and any customer naming conventions
• ControlSwitch in a private address space
• Media Gateway and ICE access - should be in a public address space
• Access and Routing
• Access to TAC (Veraz Customer Support Centers)
• Access to Media Gateways from TAC
• Static Routes for Media Gateways and remote subnet hosts (TAC)
• Use of ei.check for access to single interface MGW and IAD
• LAN Switch Port mirror configuration for diagnostics
• NTP Servers to be configured on the EMS
• Any firewall issues for SIP, H.323, and TAC access
• Terminal Servers or management LANfor system consoles
• Gateways
This is important for calculating LAN port requirements.The I-Gate 4000 Pro
provides redundant physical ports to be used as active and standby ports.
• I-Gate 4000 Pro is an L2 switch and requires 3 to 14 addresses depending on
hardware configuration
Solaris OS and Oracle Database configuration requires the following questions to be
answered:
• Is there a particular person to be involved with the OS install and RAID configu-
ration issues?
• Is SSH required?
• Veraz provides database backup programs for automated cyclical backup’s to
local storage. How will the back up be moved to other media (tape, remote disk,
backup server)?
Note Please refer to Appendix B for related forms.


Network Planning
A geographically dispersed ControlSwitch requires dual independent subnets between the
locations. Each location requires a primary and secondary ControlSwitch subnet. The two
primary and two secondary subnets must be inter-connected independently, see Figure 2-
3.
Figure 2-3 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.
Please refer to Appendix C for related forms.

Connecting the Hardware

Use the following form to estimate the number and type of cables required to connect the
ControlSwitch in your network.
ControlSwitch host platforms require the following types of additional cables:
• Ethernet (CAT 5e, 8 wire, RJ-45 both ends)
• Ethernet Cross Over (CAT 5e, 8 wire, RJ-45 both ends)
• DS1 (RJ-48 both ends)
• RS 232 (Serial connection to console)
Table 2-2 summarizes the additional cables that are required to support the interconnection
layout illustrated in Figure 1-1.
Table 2-2 Example of Additional Cables Needed
Start Location End Location Quantity Cable Type
Host Platform Description Description
EMS Client Ethernet Switch - Client subnetwork 1 Ethernet

For OS installation and configuration 1 RS 232
EMS Ethernet Switches - Primary and Secondary subnetworks 2 Ethernet
Primary SG Ethernet Switches - Primary and Secondary subnetworks 2 Ethernet

SS7 link-1 1 DS1
Secondary SG - Private Subnetwork 3 and 4 2 Crossover
Null modem-SG to SG, serial port B 1 Serial
Secondary SG Ethernet Switches - Primary and Secondary subnetworks 2 Ethernet

SS7 link 1 1 DS1
Primary SG - (see above)
CCP Ethernet Switches - Primary and Secondary subnetwork 2 Ethernet
CDR Ethernet Switches - Primary and Secondary subnetworks 2 Ethernet
PE Ethernet Switches - Primary and Secondary subnetworks 2 Ethernet
PE (Redundant) Ethernet Switches - Primary and Secondary subnetworks 2 Ethernet
EC Ethernet Switches - Primary and Secondary subnetworks 2 Ethernet
EC (Redundant) Ethernet Switches - Primary and Secondary subnetworks 2 Ethernet
ICE Ethernet Switches - Primary and Secondary subnetworks 2 Ethernet
ICE (Redundant) Ethernet Switches - Primary and Secondary subnetworks 2 Ethernet
SEE Ethernet Switches - Primary and Secondary subnetworks 2 Ethernet

Connecting the Hardware
Table 2-2 Example of Additional Cables Needed
LIDAP Ethernet Switches - Primary and Secondary subnetworks 2 Ethernet
Use Table 2-3 to estimate the number and type of additional cables needed to connect the
host platforms to your network.
Table 2-3 Cables Required for Your System

Cable Pin Outs

This section provides cable pin out information for Ethernet, SS7 and T1 connections.
SS7 and T1 Cabling

T1 and SS7 signaling links require RJ-48, shielded, twisted pair cables to connect to the
SS7 network. Their pin outs are indicated in Table 2-4.
Table 2-4 SS7 Cable Pin Outs
Pin Signal Wire Color Description
Pin 1 Rx Tip orange and white Receive from network
Pin 2 Rx Ring white and orange Receive from network
Pin 3 Rx Shield no connection Shield
Pin 4 Tx Tip blue and white Transmit to network
Pin 5 Tx Ring white and blue Transmit to network
Pin 6 Tx Shield no connection Shield
Pin 7 None Drain from Blue No connection
Pin 8 None Drain from Orange No connection

Appendix A Site Survey
This appendix provides a blank worksheets forms that can be copied and used to complete
the site survey. The following worksheets and forms are included in this appendix:
• Main Contact Person
• Site Contact Person
• IP Network Administrator/Planner
• Switch Engineer
• Site Identification and Location
• Site Location
• Site Security
• Site Access Details
• Equipment Details
• Mounting Options
• Floor Construction/Type
• Cross Connection Convertors and Adaptors
• DC Power
• AC Power
• Uninterrupted Power Supply (UPS)
• System Power and Cooling Estimation Form
• Cable Estimation Form
Veraz Networks ControlSwitch System Requirements and Environment Guide A–1

Appendix A: Site Survey
Introduction
This appendix provides Veraz Networks information about the site installation condi-
tions.This site survey must be performed before on-site installation begins.
Note Installation of the equipment can only be scheduled after the Site/Sur-
vey/Pre-installation Questionnaire form is fully completed. This will ensure a
more efficient installation.
The questionnaire must be returned to the Veraz Networks project manager, preferably by
e-mail. If you are uncertain about how to reply to any of the questions, please contact the
Veraz Networks project manager.
Site Survey/Pre-installation Questionnaire

The questionnaire includes the following sections:
• Veraz Networks contact person
• Customer’s contact person
• Customer’s technical personnel contact list
• Site information
Veraz Networks Contact Information
Table A-1 Main Contact Person

Required Information Details
Name
Location
Telephone Number
Mobile Phone
Fax Number
Email Address
A–2 Veraz Networks ControlSwitch System Requirements and Environment Guide

Customer’s Contact Person
Customer’s Contact Person
Table A-2 Site Contact Person

Name
Location
Telephone Number
Mobile Phone
Fax Number
Email Address
Technical Personnel Contact List

The following table refers to the contact person handling the technical issues relating to
the IP Network (network addresses, firewall, Proxy, routers etc.)
Table A-3 IP Network Administrator/Planner

Name
Location
Telephone Number
Mobile Phone
Fax Number
Email Address
The following table refers to the contact person handling Switch configuration/mainte-
nance.
Table A-4 Switch Engineer

Name
Location
Telephone Number
Mobile Phone
Fax Number
Email Address

Site Information
Table A-5 Site Identification and Location

Customer Name or ID
SIte Name or ID
Customer Equipment P.O.
Numbers
Table A-6 Site Location

Site Address
Directions to installation site
Recommended hotels and their

telephone numbers

Site Information
Table A-7 Site Security

Security gate/reception area Yes / No
Any site specific procedures, requirements, or Yes / No
clearances
If Yes, please explain or attach forms
Intruder alarm where equipment is located Yes / No

Security contact Names (s)
Security Contact telephone number(s)

Site Access
Table A-8 Site Access Details

Main site telephone number
Main site fax numbers
After business hours telephone numbers
Normal site working hours
Site access available beyond normal hours
If Yes, describe access procedure
Hours when certain work cannot be

performed
Standard maintenance window
Site contact outside normal working

hours (including telephone number)
Card-key access system

Site Access
Table A-9
Courtesy phone/fax number within the area of the
equipment
Is it dedicated for maintenance purposes Yes
No
Availability of a spare telephone line Yes
No
Remote access support Analog Line
IP Access
ISDN BRI Line

Equipment Installation
Table A-10 Equipment Details

Does the equipment need to be moved to installation location Yes
from loading dock? No
Door access (for 24W, 35D, 74H inch un-crated cabinet) Yes/No
Width of Narrowest door Inches
Is there an elevator available (in multi-story building)? Yes
No
For see able space contractions within elevators, hallways, or
stairs
Floor load bearing (KG/m, lb/ft)
Total floor load bearing

Loading dock or ramp Yes
No
Does carrier need to provide “inside delivery” Yes
No

Table A-11 Mounting Options

Typical installations are two post or four post
(cabinet)
Two post rail manufacturer (to determine hole

spacing and accessory requirements)
Provide rack model number or hole spacing and
screw thread size
Two post rail size
Mount Width (19”, 23”, or specify)
Available Height
Preferred equipment mount method (Face mount or Face

center mount) Center
Four post (cabinet) installation. Please provide Width:
details of the cabinet Height:
Note that most equipment has front to back air flow Depth:
and doors may have to be removed
Distance between rails, front side to back
side (in.):
hole spacing and screw thread size
Are cabinets equipped with fans? Yes

No
Are Media Gateways to be installed in Veraz Yes
Networks cabinets? No
Cabinet already installed Yes
No
If No, when will it be available for the installation to
take place
Cabinet installation be performed by Veraz Yes

Networks No

Table A-12 Floor Construction/Type

Type of existing floor Concrete
Suspended
Thickness of the concrete
Distance from concrete to suspended floor
Height of the ceiling (between suspended floor and

ceiling)
Cables from floor or overhead cable trays Yes

No
Distance from floor to overhead cable trays
Overhead hard-points (to secure cabinets) Yes

No
Is the raised floor carpeted Yes
No
If yes, is the carpet anti-static Yes
No
If no, is an anti-static pad provided Yes
No
Is there any under flooring bulkhead or firewall Yes
No

Equipment Floor Plan

Please mark the position of racks and cabinets. Indicate front or rear. Indicate type of
equipment to be installed in each (media gateways-MG, servers-S, LAN switched-LAN,
DS3 Patch Panels-PP). Show locations of other items related to the installation.
Mark grid scale here: each tile square = ________ cm or _________ cm or inches.

.
Table A-13 Cross Connection Convertors and Adaptors
Is there a cross connection, D&I units requirement Yes
No
If yes, please specify the details
Equipment Type
Manufacture
Model/Type
Is there a requirement for COnverters or Adaptors Yes
between Veraz Networks equipment and customer’s No
equipment
If yes, please specify the details
Equipment Type
Manufacture
Model/Type
Is CSU or DSU required Yes
No
If yes, please specify the function it will serve in the
Network
Please specify the required interface between Veraz
Networks equipment and customer’s equipment
Does Veraz Networks provide DSU/CSU Yes
No
In case Veraz Networks provides the DSU/CSU complete the section below
What is the distance from the commercial service
providers to the proposed location of the equipment
Please provide the channels being used
In case the customer provides the DSU/CSU please complete the section below
Please specify type and model of units
What type of data connection is needed V.35
X.21
Other

Power Supply
Power Supply
Table A-14 DC Power

Is there an existing-48 VDC power supply Yes
No
Redundant DC power supply available (A-B) Yes
No
What is the maximum current available
Ground wire and lug available Yes

No
If not, specify the length of the required ground wire
Distance between DC power supply and terminals
Typical wire size (AWG) to each rack
Typical amps to each rack
Typical rack fuse panel manufacturer and model/

type
Fuse type
max amps each circuit
number od circuits
Typical circuit wire to fuse panel connection is made
by spade terminal, clamping screw, or specify

Table A-15 AC Power

AC power available Yes
No
If yes, what is the voltage
What is the plug type
Number of phases
Value of single phase voltage available (AC)
Power distribution wiring size (gage)
Table A-16 Uninterrupted Power Supply (UPS)

Is there UPS Yes
No
On-site telecom MUXes serviced by UPS
UPS spare capacity (kVA)

Power Supply
System Power and Cooling Estimation
Table A-17 System Power and Cooling Estimation Form
Description (or Hostname) Quantity -48 V DC -48 120 240 Fuse Maximum
A side VDC B VAC VAC BTU/hour
side
System Totals:

Table A-18 Cable Estimation Form


Appendix B Platform Planning
This appendix provides a blank worksheets forms that can be copied and used to prepare
for an installation. The following worksheets and forms are included in this appendix:
• Worksheet for Sun Netra 240
• Worksheet for SunFire240
• Worksheet for External Storage
• System Power and Cooling Requirements
• Host Name and IP Address Form
• Cable Estimation Form
Veraz Networks ControlSwitch System Requirements and Environment Guide B–1

Appendix B: Platform Planning
Table B-1 Worksheet for Sun Netra 240

Requirement Sun Netra 240 Your Platform
CPUs Two 1.8 GH
RAM All elements-2 GB RAM
Note: The amount of RAM can be
increased, if necessary.
Disk Space EMS 5-73 GB drives
CCP and SG Separated-One 73 GB drive
Disk Controllers UltraSCSI
Built in IP 4 10/100/1000 -Mb/sec Ethernet
Network Interface
Operating System Solaris 8 Release7/03, Patch Level
108528-29, 117006-01
DVD DVD
Serial Port Two RS-232 serial ports
DC power -48/60VDC nominal,570W, mat dual
input
Rack Mounting Standard 19in. 4 post
Kit 19in., 23in. 2 post center mount
19in. 4 post slider rack kits.
Dimensions 3.44 in. H (2RU)
17.4 in. W
20 in D
Weight 41.16 (18.6 kg)
B–2 Veraz Networks ControlSwitch System Requirements and Environment Guide

Table B-2 Worksheet for SunFire240
Requirement SunFire240 Your Platform
CPUs Two 12.8 GH
RAM All elements-2 GB RAM
Note: The amount of RAM can be increased,
if necessary.
Disk Space EMS 5-73 GB drives
CCP and SG Separated-One 73 GB drive
Disk Controllers UltraSCSI
Built in IP 4 10/100/1000 -Mb/sec Ethernet
Network Interface
Operating System Solaris 8 Release7/03, Patch Level 108528-29,
117006-01
DVD DVD
Serial Port Two RS-232 serial ports
AC Power
AC Service
Requirement
Power Supply 2, universal input
Rack Mounting Standard 19in. 23i., 4 post only
Kit

Table B-3 Worksheet for External Storage
Item Description Your Storage Device
External Storage Type SE 3310
Disk Space 5-12 73 GB drives
Disk Controllers Ultra 160 SCSI (LVD)
DC power -48/60VDC nominal, 18amps, dual input
Power Supply Two N+1 redundant, hot-swap
Heat output 260 Watts, 785 BTU per hour (fully populated)
Operating Temperature 5C to 40C (41 F to 104F)
Height 3.5in. (2RU)
Width 44.94 cm (17.6 in.)
Depth 53.25 cm (21.0 in.)
Weights Without disk drives 31.85 lbs

Fully loaded 50 lbs (22.7kg)
Rack Mounting Kit 19, 23 or 24 inch rack kits or 600- mm formats;

front or center mounts

System Power and Cooling Requirements
Table B-4 System Power and Cooling Requirements

Description or Hostname Quanti -48 -48 120 240 Fuse Max
ty VDC VDC B VAC VAC BTU/
A side side hour

Table B-5 Host Name and IP Address Form

Host Type Hostname Primary Secondary
IP Address IP Address

Table B-6 Cable Estimation Form


Appendix C Network Planning
This chapter provides a blank worksheets forms that can be copied and used to prepare for
an installation. The following worksheets and forms are included in this appendix:
• IP Network Component (The LAN or WAN)
• IP Addresses
• I-Gate 4000Pro
• I-Gate 4000
• Cables and Switches
• T1/E1 Interface
• DS3 Interface
• STMF 1 Interface
• ISDN PRI
• General - SS7
• Links
• Trunks and Trunk Groups
• Ingress Trunk Group Profiles
• Egress Trunk Groups Profiles
• Trunk Group Numbering and Dialing Profiles Assignment
• General - routing plan
• Routing Profiles
• CDRs
Veraz Networks ControlSwitch System Requirements and Environment Guide C–1

Appendix C: Network Planning
IP Network
Table C-1 IP Network Component (The LAN or WAN)

Type of Interface 100MBs (RJ45)
In case of 1-Gigabit interface please specify the following parameters
Connector Type SC
LC
MT-RJ
ST
Transmit Mode Single
Multi
Wave Length 850mm
1300mm
1500mm
Cable distance between veraz Networks Media Gateway and ____________meters
LAN Interface (Switch/Router)
Are there firewalls protecting the Veraz Networks systems Yes / No
If yes, type the manufacturer and model number
Is Proxy server NAT server involved in the network Yes / No
connecting the Veraz Networks systems
If yes, pleas type the manufacturer and model number
Must the network’s routers be re-configured to support the Yes / No
Veraz Networks systems
If yes, who will be responsible for configuring the router
If yes, please type manufacturer and model
Is the IP Network between the Veraz Networks equipment Yes / No
available for use and fully established
If not, when will it be ready
Is the network part of a Domain Yes / No
If yes, specify the Domain name
Available Domain name for Veraz Networks
To what type of network device will the Veraz Networks
equipment be connected, Router (L3), LAN Switch (L2), other
Will the connection above be full duplex Yes / No
How far will the Veraz Networks equipment be from the above
connecting equipment
Where will the xMS be connected
What will the IP Address be
Are these IP networks connected to Internet
C–2 Veraz Networks ControlSwitch System Requirements and Environment Guide

IP Network
Table C-2 IP Addresses

Control Switch Primary Subnet Secondary Subnet
Network Address
Network Mask
Range of Address assigned
Media Gateways Subnet
Network Address
Network Mask
Range of Address assigned
Please attach a detailed IP Network diagram showing ControlSwitch, Media Gateway, and
external connecting subnetworks. Include firewalls, switches, and routers. Annotate with
IP addresses, host names, and where needed port numbers.

IP Address Assignment
Table C-3 I-Gate 4000Pro

Host Type Name IP Address Network Mask Default
Gateway
Address
TPSM
DSPK 1
DSPK 2
DSPK 3
DSPK 4
DSPK 5
DSPK 6
D32M 1
D32M 2
D32M 3
D32M 4
D32M 5
D32M 6
Table C-4 I-Gate 4000

Host Type Name IP Address Network Default Gateway Address
Mask
AHME
IGWM 1
IGWM 2
IGWM 3
IGWM 4
IGWM 5
IGWM 6
IGWM 7
IGWM 8

IP Address Assignment
Table C-5
Host type and Primary IP Mask Default Secondary IP Mask Default
name Address Gateway Address Gateway
Address Address
EMS
CCP
SG
PE
EC
CDR
ICE

Digital Lines
Table C-6 Cables and Switches

Switch service carrier
Telecom switch for providing circuits make
and model
Are you using Veraz Networks supplied Customer
cable or customer cable Veraz Networks
If customer cable, please specify type
(please attach sample)
Number of Spans provided
Date of Spans availability
Are all Spans connected to the same switch Yes
No
If 75Q cable, what type of connectors at the
switch side
If 120Q cable (not applicable, DS3 or Terminated with RJ-45
above) Not terminated
If terminated with RJ-45 connector, Rec tip:
provide wiring information Rec ring:
Xmit tip:
Xmit ring:
If Fiber (optical) cable state connectors at
the switch site
Fiber (optical) cable type Muli mode
Single mode
Cable distance between the Veraz Networks
Media Gateway and DDF/Switch, Length of
cables required

T1/E1 Interface
T1/E1 Interface
Table C-7 T1/E1 Interface

Type of Span E1
Balanced (75 Ohm)
Unbalanced (120 Ohm)
Cable distance between customer’s switch ________meters
and Veraz Networks Media Gateway
Line Equalizer (For T1 only) ________feet
Framing E1
• MF CRC
• MF no CRC
T1
• SF
• ESF
Line Code (For T1 only) B8ZS
AMI
DS3 Interface
Table C-8 DS3 Interface

Cable distance between customers switch and Veraz
Networks Media Gateway
Number of DS3 to be connected
Are all Spans (28 DS1 /21/E1) assigned Yes

No
If no, please specify the Spans that are assigned
Mapping (varies depending on the existing M13 (M23)
configuration) C bit
Framing (framing varies depending on the existing EI
configuration) • CRC
• Co CRC
DS1 (T1)
• SF
• ESF

STMF1 Interface
Table C-9 STMF 1 Interface

Mode Type SDH
other
Cable distance between customer’s switch and Veraz
Networks Media Gateway
Interface Connection Electrical

• RJ45 (LC-NRZ)
• BNC (LC-CMI)
• Other
Optical
• 1310 nm
• 1550 nm
STMF1 Configuration Framed
Unframed
Are all time slots available for bi-directional operation Yes
No
What is the power output (indbm) Receive Level:
Transmit Level:
Package Method AU4
AU3 x 3
Overhead Identifiers Enable
(Bytes J0, J1, J2) Disable
Configuration Point to point
Ring
Link Redundancy Yes
No

Signaling
Signaling
Table C-10 ISDN PRI

ISDN PRI Standard ETSI
ANSI
Other (Specify)
Please specify the flavor standard name and details
National Specific Messages
National Specific Parameters
PRI Signaling Type (T1 only) NFAS
Please attach detailed
configuration information
FAS
Circuit Selection Mode Preferred
Exclusive
Switch Side ISDN MOde User (TE)
Network (NT)
Number of PRI Spans
Type of physical interfaces E1 120 Ohm
E1 75 Ohm
T1
T1 type of line encoding AMI
B8ZS
E1 type of line encoding AMI
HDB3
T1 Framing Format SF/D4
ESF
CRC Mode CRC Enabled
CRC Disabled

SS7 Interface
Table C-11 General

Type of signaling standard used ISUP
• ETSI Version 2
• ANSI
• UK
• India
• Japan
Other
• Specify type and standard
National Specific Messages
National Specific Parameters
Type of Point Code standard used ITU14
ITU24
ANSI
Other
Type of signaling link physical interfaces E1 120 Ohm
E1 75 Ohm
T1
V.35
Bit rate of the signaling links 64K
56K
48K
Other
Spans are used for voice and signaling (Associated Mode) Yes / No
Number of Spans
If not (quasi/non-associated mode) specify the arrangement of the signaling links within the
physical signaling span (number of time slots used for signaling)
How many T.S. are used for voice 30 (PCM30) or 31 (PCM31)
Line encoding of Signaling spans interface HDB3
B8ZS
AMI with Zero code
suppression
Frame format of signaling link interface E1-Double frame or Multiframe
T1 -ESF or D3/D$
CRC Mode CRC Enabled
CRC Disabled

SS7 Interface
Please provide detailed diagram of the Signaling network including all SS7 Entities and
the information listed in the following tables.
Table C-12 Links

Link Set Link ID Time Slot SLC
Add more if required.

Trunks and Trunk Groups
Table C-13 Trunks and Trunk Groups

Trunk Group ID SSP PC ControlSwitch PC CIC Range
Add more if required.

Numbering and Dialing Plan
Numbering and Dialing Plan

Please specify the Dialing Format Profile to be used on trunk groups.
Table C-14 Ingress Trunk Group Profiles

Profile Dialed Number Format Signaling Message or
Sent to ControlSwitch Parameter specifications
Table C-15 Egress Trunk Groups Profiles

Profile Dialed Number Format Signaling Message or
Sent to ControlSwitch Parameter specifications

Trunk Groups Numbering and Dialing Profiles Assignment
Table C-16 Trunk Group Numbering and Dialing Profiles Assignment

Trunk Group Ingress Trunk Group Egress Trunk Group Profile
Profile

Special Number Handling
Special Number Handling

Please provide requirements for any specific treatment for specific numbers.
Table C-17

Routing Plan
Table C-18 General

Routing Policy Called Party Number
Calling Party Number
Other_Originating trunk group
Time of Day Routing required Yes
No
If minimum / maximum number of digits is Min number of digits for routing ______
required for routing please specify Max number of digits for routing ______
Other specific Call Routing requirements
Routing Profiles
In the case there are specific routing profiles required please indicate their requirements
and assignment for each trunk group.
Profile Routing Specification
Routing Profiles Assignment
Ingress Trunk Group Routing Profile

CDRs
CDRs
Table C-19 CDRs

ControlSwitch Required to provide CDRs Yes
No
Billing server available Yes
No
Vendor of billing server Unix Server_____________________
CDR Format Please attach detailed example of the CDR
format
Billing server IP address
Method of CDR transfer


Appendix D Staging Process
The ControlSwitch Staging process contains all of the steps required to prepare a customer
system for a successful deployment. When staging is complete, the systems are packed
and shipped to the customer site(s). This process insures that all of the required compo-
nents are present and operational for the customer deployment. The process steps are:
• Receive Platform, Gateway Chassis, and Components
• Build Gateway Systems
• Install and Configure the Operating System Software
• Install the ControlSwitch Software
• ControlSwitch Initial Provisioning
• I-Gate Provisioning from XMS
• Integrated System Test
• Pack and Ship
Veraz Networks ControlSwitch System Requirements and Environment Guide D–1

Appendix D: Staging Process
Receive Platform, Gateway Chassis, and Components
As components arrive complete the following steps:

1. Move shipping documents and boxes to Staging Lab.
2. Check all shipments against their packing lists.
3. Record each Sun system’s serial number and ethernet address on Platform Build Spec-
ification spreadsheet (PBS).
Build Gateway Systems

To build a gateway system complete the following steps:
1. Mount gateway chassis in the staging racks.
2. Record serial numbers on the PBS.
3. Install all gateway interface line cards.
4. Connect to power.
5. For initial provisioning connect the 100Mbs interface to the staging subnet.
Build ControlSwitch Platform Systems

To build a a ControlSwitch Platform system complete the following steps:
1. Unpack each Sun server to the workbench.
2. Install internal options according to the PBS.
Internal options may include DVD drives, additional disks, additional memory,
Ethernet interface cards, SCSI interface cards, and Ulticom cards.
3. For Ulticom cards:.
a. If the card is for E1 service, move the card jumpers from the T1 to E1 position.
b. Affix an E1 label to the mounting plate.
c. Record card serial numbers on PBS.
4. When the system is assembled affix host name labels to front and back.
5. Move the system to the staging shelves.
6. Attach power and LAN cables (lab subnet).
7. For disk arrays:
a. Fix labels that identify the host system, front and back.
b. shelve the array with its host and attach power.
c. When connecting SCSI cables connect HA port 1 to array port A, HA port 2 to
array port B.
D–2 Veraz Networks ControlSwitch System Requirements and Environment Guide

Install and Configure the Operating System Software
To install and configure the operating system software complete the following steps:
1. Enter the host name, the ethernet address, and the preliminary IP address information
into the Jumpstart server from the PBS.
2. Add the correct disk size parameter.
3. Check the Jumpstart profiles for the proper disk controller number and Solaris version
and patch level.
4. Boot each system for Solaris installation.
5. Configure Disk Suite on the EMS, EC, and CDR systems.
6. Re-address the systems for Customer IP addresses.
7. Attach the LAN switch to the staging router configured for the customer address
space.
Install the ControlSwitch Software

To install and configure the ControlSwitch software complete the following steps:
1. Install the ControlSwitch software on each system.
2. Fully configure the EMS hosts and static routes files for use by other elements.
At this time the ControlSwitch configuration is complete and initial provisioning can
begin.
The following sections define the provisioning steps and refer to the source of the infor-
mation required. Following this initial provisioning the entire system will be tested. INET
Spectra analyzers are typically used to originate and terminate traffic.

ControlSwitch Initial Provisioning
Table D-1 ControlSwitch Provisioning

Components Source Information
EC, CDR, RE, CCP, and SG elements, Acceptance Test Plan (ATP)
creation, and provisioning
Media Gateway resources creation on EMS Acceptance Test Plan (ATP)
ANSI SS7 Signaling Gateway creation Acceptance Test Plan (ATP)
ANSI ISUP Trunk Group creation Acceptance Test Plan (ATP)
PRI Trunk Group creation Acceptance Test Plan (ATP)
Routing Plan creation Acceptance Test Plan (ATP)
Routing Policy Acceptance Test Plan (ATP)
Rule Nodes creation for routing logic Acceptance Test Plan (ATP)
I-Gate Provisioning from XMS
Components Source Information

Terminal Chassis Parameters creation Acceptance Test Plan (ATP)
IO card and Media Gateway cards creation Acceptance Test Plan (ATP)
Resource distribution to the various media Acceptance Test Plan (ATP)

gateways
Downloading the Maps tot he Terminal/ Acceptance Test Plan (ATP)

Chassis

Integrated System Test
ISUP to ISUP call Acceptance Test Plan (ATP)
ISUP to PRI call Acceptance Test Plan (ATP)
PRI to ISUP call Acceptance Test Plan (ATP)
Rule Nodes creation for routing logic Acceptance Test Plan (ATP)
Pack and Ship

To pack and ship the system complete the following steps:
1. Shutdown all systems.
2. Remove power and LAN cables.
3. Re-pack the Sun servers and Disk Arrays in original packaging.
4. Insure all parts are repacked (e.g. power cords, SCSI cables, mounting hardware).
5. To facilitate on site- racking mark the box with the host name.
6. To prevent wear on contact pins and mating surfaces ensure that gateway cards are
removed and packaged separately for shipping.
The chassis slot number can be written on the card’s box.
7. E-mail shipping information and tracking numbers to the customer and project
leaders.
8. Forward shipping waybill to accounting.


Index
Index
A M
acronyms P-4 media gateway
audience P-2 supported hardware 1-14
B N
blank forms 3-1 network cabling 2-8
C O
cable operating system patche1-9
estimating cable needs 2-8 operating system software 1-9
Ethernet cable 2-10 Oracle software 1-9
pin-outs 2-10
configuration P
distributed system 1-5 power and cooling estimation tables 2-2
examples 1-5
R
D rack layout planning 2-3
disk space requirements
external storage specification 1-13 hardware 1-9
distributed system configuration 1-5 software1-9
documentation P-2
S
signaling gateway
E
cable 1-10
element overview 1-2
Ethernet cable 2-10 installation 1-10
software
F requirements 1-8
forms SS7 signalling interface hardware 1-14
blank forms 3-1
T
system power and cooling worksheet 2-2
terminology P-4
H
V
hardware
variables, conventions used in this guide P-8
SS7 signalling interface1-14 Voice over Internet Protocol (VoIP) application 1-2
hardware planning tables 1-10
hardware specifications 1-9 W
web browser requirement 1-9
I
installation
cable 1-10
hardware 2-7
rack layout 2-3
requirements 1-7
tasks 1-16
Internet Call Diversion (ICD) application 1-4
Veraz Networks ControlSwitch System Requirements and Environment Guide Index–1

Index
Index–2 Veraz Networks ControlSwitch System Requirements and Environment Guide

Environment

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Environment

Caricato da

Copyright:

Formati disponibili

ControlSwitch System Requirements and

phone: (408) 750-9400

All other trademarks are the property of their respective owners.

Revision record: <ControlSwitch System Requirements and Environment Guide >

01 June-03 First edition and printing. Ver. 5.4.5

Publication No. <0306555-01>

Information in this document is subject to change without notice.

Chapter 1 Deploying the System

Chapter 2 Planning Installation

Veraz Networks ControlSwitch Requirements and Environment Guide iii

Appendix A Site Survey

Appendix B Platform Planning

Appendix C Network Planning

iv Veraz Networks ControlSwitch Requirements and Environment Guide

Appendix D Staging Process

Veraz Networks ControlSwitch Requirements and Environment Guide v

vi Veraz Networks ControlSwitch Requirements and Environment Guide

Chapter 1 Depolying the System

Chapter 2 Planning Installation

Veraz Networks ControlSwitch Requirements and Environment Guide vii

Veraz Networks ControlSwitch System Requirements and Environment Guide ix

x Veraz Networks ControlSwitch System Requirements and Environment Guide

Veraz Networks ControlSwitch System Requirements and Environment Guide xi

xii Veraz Networks ControlSwitch System Requirements and Environment Guide

Table i-1 Typographical Conventions

\, backslash Designates a break in a continuous line in a code example or command line

[ ], brackets Keyboard keys.

<text in angle brackets> Variable values.

Note Provides important background information.

! Caution Describes implications of an irreversible step in a process that can

a WARNING! Indicates a potential danger to hardware, software, or per-

Veraz Networks ControlSwitch System Requirements and Environment Guide xiii

Table i-2 Descriptions of Variables

domain.com Represents a domain name.

filename Represents the name of a file.

hostname Represents the name of a host computer.

icdr Represents the hostname of an Veraz Networks CDR element.

interfacename Represents the name of the network interface.

mountpointname Represents a mount point name.

n Represents a number from 0 to 9.

nnn.nnn.nnn.nnn Represents an IP Address or subnet mask.

PackageName Represents a software package name.

pid Represents a UNIX process identification number.

SIDname Represents an Oracle database SID name.

NewVersionNumber Represents the version number of new software to be installed.

OldVersionNumber Represents the version number of currently installed software.

versionnumber Represents a software or hardware version number.

xiv Veraz Networks ControlSwitch System Requirements and Environment Guide

Phone: (408) 750-9400

Technical Assistance Centers (TAC)

Veraz Networks ControlSwitch System Requirements and Environment Guide xv

xvi Veraz Networks ControlSwitch System Requirements and Environment Guide

Veraz Networks ControlSwitch System Requirements and Environment Guide 1–1

1–2 Veraz Networks ControlSwitch System Requirements and Environment Guide

Central System Configuration

Figure 1-1 Central Site

Distributed System Configurations

Veraz Networks ControlSwitch System Requirements and Environment Guide 1–3

Figure 1-2 Distributed Site

Central System and Distributed Call Control Configurations

1–4 Veraz Networks ControlSwitch System Requirements and Environment Guide

Media Gateways can also be installed in a distributed configuration. Additional Media

Figure 1-3 Distributed Site