Voip

See notice on first age
Lucent VoIP Solution

Engineering Guide
Release 6.2.1
280-100-006R6.2.1
Issue 1
October 2006
Lucent Technologies - Proprietary

This document contains proprietary information of Lucent Technologies and
is not to be disclosed or used except in accordance with applicable agreements.
Copyright 2006 Lucent Technologies
Unpublished and Not for Publication
All Rights Reserved
See notice on first age
This material is protected by the copyright and trade secret laws of the United States and other countries. It may not be reproduced,
distributed, or altered in any fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable
agreements, contracts or licensing, without the express written consent of Lucent Technologies and the business management owner of the
material.
Trademarks
All trademarks and service marks specified herein are owned by their respective companies.
Notice
Every effort has been made to ensure that the information contained in this information product was accurate at the time of printing. However,
information is subject to change. This IP describes certain hardware, software, features, and capabilities of Lucent Technologies products. The
hardware, software, features, and capabilities described may not be the same as the equipment that you have. The IP is for information
purposes, and you are cautioned that it may not describe your specific equipment.

See notice on first page
Contents
About this information product

Purpose
.............................................................................................................................................................................................
Audience
..........................................................................................................................................................................................
Systems supported
........................................................................................................................................................................
Technical Support
.........................................................................................................................................................................
..................................................................................................................................................................................................
Tasks
Related documentation
..............................................................................................................................................................
vi
........................................................................................................................................................................
vi
.................................................................................................................................................................................
vi
Technical support
How to order
How to comment
.........................................................................................................................................................................
vi
Lucent VoIP Solution Engineering

Overview
......................................................................................................................................................................................
1-1
...............................................................................................................
1-2
......................................................................................................................................................................................
2-1
Lucent VoIP Solution Engineering Overview

Lucent VoIP Architecture
Overview
.....................................................................................................................................
2-2
......................................................................................................................................................................................
3-1
Lucent VoIP Solution architecture

3
vi
...................................................................................................................................................
Information product support
...................................................................................................................................
How to use this information product
Lucent Gateway Platform

Overview
...................................................................................................................................................................................................................................
280-100-006R6.2.1
iii
Issue 1, October 2006
Revision 0, October 2006
Contents
Lucent Gateway Platform Engineering

4
...........................................................................................................................
3-2
......................................................................................................................................................................................
4-1
BroadWorks Servers
Overview
......................................................................................................................................
4-2
......................................................................................................................................................................................
5-1
BroadWorks Servers Engineering

5
Session Border Controllers

Overview
.........................................................................................................................
5-2
......................................................................................................................................................................................
6-1
Session Border Controllers Engineering

6
AnyPath Messaging System

Overview
AnyPath Messaging System Engineering

7
.......................................................................................................................
6-2
Lucent Security Manager and VPN Firewall

Overview
......................................................................................................................................................................................
Lucent Security Manager and VPN Firewall Engineering
......................................................................................
7-1
7-2
Glossary
...................................................................................................................................................................................................................................
280-100-006R6.2.1
Revision 0, October 2006
iv

Purpose
The Lucent VoIP Solution Engineering Guide contains a solution-level overview of the
items necessary for planning an installation site, and provides an overview of tools or
applications available to determine hardware capacities and traffic thresholds for the
Lucent VoIP Platform distributed solution.
This information can be used as reference material and background information.
Audience
Engineers with reponsibility for network planning, design, configuration or

optimization of the Lucent VoIP Solution elements.
How to use this information product
This IP contains conceptual information about the Lucent VoIP Solution.

In this information product references are made to external documents. In the PDF
version this is indicated with the path leading to the correct information.
Systems supported
This document applies to the Lucent VoIP Solution release 6.2.1 used in combination
with Lucent Gateway Platform release 6.2.0.1, BroadWorks Release 14.0, AnyPath
R8.2, AcmePacket R4.0.1, and LSMS and VPN Firewall Brick R9.0.
Technical Support
Please contact your Lucent Technologies Local Customer Support Team (LCS) for
technical questions about the information in this document.
Tasks
This information product provides references to network and site planning,

configuration, monitoring, and optimization information for Lucent VoIP Solution
elements.
....................................................................................................................................................................................................................................
280-100-006R6.2.1
v
,
Related documentation
Following are the manuals provided for the Lucent VoIP Solution:
Lucent VoIP Solution Operations, Administration, Maintenance and Provisioning,

280-100-001
Lucent VoIP Solution Backup and Restore Procedures, 280-100-002
Lucent VoIP Solution Troubleshooting Manual, 280-100-003
Lucent VoIP Solution Alarms Reference Manual, 280-100-004
Lucent VoIP Solution Installation Guide, 280-100-005
Lucent VoIP Solution Engineering Guide, 280-100-006
Lucent VoIP Solution Reference Manual, 280-100-007
Information product support
The document support telephone numbers are:
1 888 727 3615 (for the continental United States)

1 630 713 5000 (for all countries).
Technical support
For technical support, contact your local customer support team. Reach them via the
web at https://support.lucent.com/ or the telephone number listed under the Technical
Assistance Center menu at http://www.lucent.com/contact/.
How to order
This information product is only available on CD-ROM, and it can be ordered with the
order number 280-100-006R6.2.1 at the Customer Information Center (CIC). Refer to:
http://www.lucentdocs.com .
How to comment
To comment on this information product, go to the Online Comment Form

(http://www.lucent-info.com/comments/enus/) or e-mail your comments to the
Comments Hotline (comments@lucent.com).
...................................................................................................................................................................................................................................
280-100-006R6.2.1
,
vi
1 ucent VoIP Solution

L
Engineering
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter gives an overview of Lucent VoIP Solution engineering.

Contents
1-2
...................................................................................................................................................................................................................................
280-100-006R6.2.1
1-1
Lucent
VoIP Solution Engineering Overview
...................................................................................................................................................................................................................................
Purpose
This topic provides an overview of engineering at the solution level. Use the
information in this chapter as guidelines of how to estimate network capacity and use
the estimates as input to configure a solution.
After the solution is configured, use the information at the network element level to
prepare for an installation of the configuration, analyze system performance, or add
additional network elements to optimize the solution.
Discrete Data Acquisition
This section provides examples of some discrete data points and estimates that can be
viewed as inputs to the VoIP application.
The following list shows some of the types of data that can be collected and monitored
to help calculate an estimate of traffic and usage within the network:
The number of VoIP subscribers.

The average number of VoIP call attempts made by each subscriber per busy hour.
The percentage of VoIP calls made between two VoIP-capable UEs. Each UE (user
equipment) call origination and termination should be counted as a call attempt
(two attempts per UE to UE call). A UE can be a SIP phone, SIP soft client, or
MGCP endpoint.
The percentage of VoIP calls made from a UE to a PSTN (TDM) subscriber. A UE
to PSTN call is a call origination and should be counted as one call attempt.
The percentage of VoIP calls from PSTN to UE. This should be viewed as a call
termination and counted as one call attempt.
Call flows for the bearer and signaling paths for each scenario. The call flow can
be used to determine how many messages (SIP, DNS, charging messages, etc.) are
generated for each bearer or signaling scenario. The number of messages generated
per call scenario can be used as an input to estimating the network element
capacity that will be needed.
Number of UE registrations and de-registrations per busy hour.
Percentage of VoIP calls for subscriber features. This can impact total call volume
and capacity on media gateway servers.
Derived Data Calculations
Use the gathered network data as inputs to the VoIP application to calculate or estimate
the amount of traffic generated within the network. These estimates along with the
individual capacity requirements of each network element can be used to determine
how many of each element will be needed for the Lucent VoIP Solution.
...................................................................................................................................................................................................................................
280-100-006R6.2.1
1-2
The following are some examples of calculations that can be made to estimate network
traffic and capacity. This is for data collected at the solution-level. Any calculations
needed to determine capacity for a network element will be included in the vendor
document for that element and referenced in this manual.
The following are example calculations for a VoIP application:
The Number of UE to PSTN calls = (Number of VoIP Subscribers) x (Number of

calls per subscriber Busy Hour) x (Percentage of UE to PSTN calls per subscriber
per Busy Hour)
The Number of PSTN to UE calls = (Number of VoIP Subscribers) x (Number of
calls per subscriber Busy Hour) x (Percentage of PSTN to UE calls per subscriber
per Busy Hour)
The Number of UE to UE calls = (Number of VoIP Subscribers) x (Number of
calls per subscriber Busy Hour) x (Percentage of UE to UE calls per subscriber per
Busy Hour divided by 2)
The Number of Registrations per Busy Hour = (Number of VoIP Subscribers) x
(Number of Registrations per Subscriber per Busy Hour)
The Number of De-registrations per Busy Hour = (Number of VoIP Subscribers) x
(Number of De-registrations per Subscriber per Busy Hour).
Configuring the Lucent VoIP Solution
The following diagram illustrates using the calculated network capacity in addition to
network element capacity requirements in order to configure and optimize the solution:
...................................................................................................................................................................................................................................
280-100-006R6.2.1
1-3
The following list defines the terms in the diagram:
General VoIP Inputs: The subscriber estimates and other discrete data for your
installation.
VoIP Engineering Rules: The derived data calculations performed on the inputs to
the VoIP application. The output could be several sets of estimated outputs for
varying scenarios of inputs.
Network Element (NE) Inputs: Reviewing the output from the VoIP engineering
rules (calculations), and gathering additional inputs defined by the various network
elements. Refer to the capacity information provided in this manual for each
network element.
Network Element Engineering Rules: The calculations performed for each network
element.
Optimized VoIP Solution: Reviewed calculations of the individual elements to
validate the balance of the network elements.
The solution-level data calculations can be used as input along with the capacity
requirements of each network element to configure the solution prior to an initial
installation. The derived data and network element capacity requirements can also be
...................................................................................................................................................................................................................................
280-100-006R6.2.1
1-4
used to analyze solution capacity needs after the network elements have been installed
and in use in the network. Refer to the capacity information provided in this manual
for each network element.
Performance Monitoring and Optimization
After the solution is configured based on the calculations of the network and individual
elements, monitor and review the network element performance and capacity. This will
validate the quantity selected of each element. Network elements may need to be added
to optimize the estimated volume. In addition, reengineering will be required as the
number of subscribers and call sessions increases. Refer to the performance monitoring
information in this manual for each network element in the solution.
Site Preparation
After configuring the solution, prepare the installation site. Refer to the network
element site preparation and installation planning guidelines in this manual for each
network element that needs to be installed or added.
System Description
For descriptions of each network element, refer to the corresponding chapter in this
manual.
The following BroadWorks applications run on Sun Solaris-based servers and
Linux-based servers:
Network Server
Application Server
Media Server
Conferencing Application Server
Conferencing Media Server
External Web Server
For descriptions and requirements for the server hardware, refer to: The BroadWorks
Recommended Hardware Guide.
The following Lucent VoIP Solution applications also run on the Sun Solaris server
platform:
Lucent Element Management System (EMS)

AcmePacket Element management System (EMS)
Lucent Billing Transaction Server (BTS)
Use the following URL to access Sun Microsystem server documentation:

http://www.sun.com/products-n-solutions/hardware/docs/Servers/index.html
...................................................................................................................................................................................................................................
280-100-006R6.2.1
1-5
Specifications
Hardware and software specifications for the configured network elements that make
up the solution are provided per network element in this manual. Refer to the
corresponding chapter for specifications for each network element.
Relief Strategy
To correct any capacity or performance issues, refer to the fault and performance
management sections in the Lucent VoIP Solution Operations, Administration,
Maintenance and Provisioning Manual. Also, refer to the Lucent VoIP Solution
Troubleshooting Manual, or, if a threshold alarm has been triggered, the Lucent VoIP
Solution Alarms Reference Manual.
...................................................................................................................................................................................................................................
280-100-006R6.2.1
1-6
L ucent VoIP Architecture

2
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter gives an overview of the Lucent VoIP Solution architecture and a short
description of the network elements.
Contents
2-2
...................................................................................................................................................................................................................................
280-100-006R6.2.1
2-1
Lucent
VoIP Solution architecture
...................................................................................................................................................................................................................................
Introduction
This topic shows the architecture of the Lucent VoIP Solution and gives a short
description of the elements.
Diagram
Architecture of the Lucent VoIP Solution with the main elements:

OSS
BMD
SS7 network
PSTN
switch
CM
NS
AS
Lucent NG
MS
CS
POTS
WS
Broadworks
Lucent GP
POTS
Lucent NG
IP network
SBC
Firewall
AnyPath
Internet
Virtual link
Physical link
SBC
Firewall
TDM
PBX
IAD
CCM
IP PBX
IP (hardphone)
SIP
endpoints
soft client
MGCP, end clients
...................................................................................................................................................................................................................................
280-100-006R6.2.1
2-2
Common elements
Element
Description

(Lucent GP)
The Lucent Gateway Platform Network Controller

performs the signaling control function for SS7, SIP, and
MGCP signaling. The Lucent Network Controller also
performs the media gateway control (MGC) function for
IPDC and H.248 gateways. The Lucent Signaling Gateway,
performing the signaling gateway (SG) function, sends and
receives SS7 signaling messages to/from media gateway
controllers or other signaling gateways.
BroadWorks
The Integrated Access Device Application Server (IAD

AS) terminates SIP and MGCP end-users.
Lucent Network Gateway

(Lucent NG)
Performs the media gateway (MG) function of coding and

decoding between the TDM network and the IP network as
part of the Lucent Gateway Platform.
AnyPath
Voice mail system which offers mail services for IP

end-users.
Session Border Controller

(SBC)
Element to add functionalities such as security and service

assurance at IP network borders.
Call Manager (CM)
Web portal to allow operators and users to access and

manage telephony services.
Operation Support System

(OSS)
Platform to perform network operations such as fault

management and performance management.
Billing Mediation Device

(BMD)
Platform used for user billing based on the CDRs from the
Lucent Gateway Platform, call events from the
BroadWorks platform and other systems.
Firewall
Element to provide security management with session

border controllers between networks.
BroadWorks elements
Element
Description
Application Server (AS)
SIP server to perform registration for SIP and MGCP

end-users.
Network Server (NS)
SIP server to determine the routing destination for IP

subscribers. Destinations can be (other) application servers
or Lucent Gateway Platform.
...................................................................................................................................................................................................................................
280-100-006R6.2.1
2-3
Element
Description
Media Server (MS)
Media server to provide media interaction for the SIP and

MGCP IP end-users registered to the application servers.
Conference Server (CS)
Dedicated conference server to provide conference servers.
Web Server (WS)
Server that acts as an access interface to an application

server for SIP and MGCP IP end-users.
...................................................................................................................................................................................................................................
280-100-006R6.2.1
2-4
L ucent Gateway Platform

3
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter provides references to the following engineering and planning

information: Capacity and performance monitoring, site preparation, system
specifications and system descriptions for Lucent Gateway Platform elements in the
Lucent VoIP Solution.
Contents
3-2
...................................................................................................................................................................................................................................
280-100-006R6.2.1
3-1
Lucent
Gateway Platform Engineering
...................................................................................................................................................................................................................................
Purpose
This topic provides capacity and performance monitoring, site preparation, system
descriptions, and system specifications for the Lucent Gateway Platform elements in
the Lucent VoIP Solution.
Capacity and Performance Management
The solution-level data calculations can be used as input along with the capacity
requirements and calculations of each network element to configure the solution. For
network level planning of the Lucent Gateway Platform, refer to: Lucent Gateway
Platform System Capacity, Monitoring, and Engineering (SCME) Guidelines, chapter:
Lucent Gateway Platform Engineering Rules, section: Network Level Planning.
To determine capacity and configure the Lucent Network Controller for the solution,
refer to: Lucent Gateway Platform System Capacity, Monitoring, and Engineering
(SCME) Guidelines, chapter: Lucent Gateway Platform Engineering Rules, section:
Lucent Network Controller.
To determine capacity and configure the Lucent Network Gateway for the solution,
refer to: Lucent Gateway Platform System Capacity, Monitoring, and Engineering
(SCME) Guidelines, chapter: Lucent Gateway Platform Engineering Rules, section:
Lucent Network Gateway.
To determine capacity and configure the Lucent Signaling Gateway for the VoIP
solution, refer to: Lucent Gateway Platform System Capacity, Monitoring, and
Engineering (SCME) Guidelines, chapter: Lucent Gateway Platform Engineering
Rules, section: Lucent Signaling Gateway.
The EMS is used to set thresholds and access reports for Lucent Gateway Platform
elements. For information about selecting data, setting thresholds, and viewing
performance via the EMS, refer to: OMC-P for Lucent Gateway Platform Management
Reference Guide, chapter: Switch Administration and Maintenance.
Performance Monitoring
To monitor critical capacity measurements to optimize the Lucent Gateway Platform

elements, refer to: Lucent Gateway Platform System Capacity, Monitoring, and
Engineering (SCME) Guidelines, chapter: Critical Triggers and Measurements.
To monitor the Lucent Gateway Platform elements using traffic reports and traffic data
for network elements including Quality of Service (QoS) measurements, refer to:
Lucent Gateway Platform System Capacity, Monitoring, and Engineering (SCME)
Guidelines, chapter: Monitoring the Lucent Gateway Platform.
...................................................................................................................................................................................................................................
280-100-006R6.2.1
3-2
Safety & Regulations
For safety and regulations information regarding the Lucent Gateway Platform, refer
to: Lucent Gateway Platform Planning and Engineering Guide, chapter: Safety and
Regulations.
Installation Planning
For information regarding site planning for installation of Lucent Gateway Platform
elements, refer to: Lucent Gateway Platform Planning and Engineering Guide,
chapter: Planning for Installation, sections:
Location of the Switch

Building Requirements
Chassis Dimensions
Space Requirements
Grounding Requirements
Power Requirements
System Interfaces
Slot Assignments
Tools and Equipment
Installation Planning Task Checklist
Switch Configuration
If preparing for an installation of Lucent Gateway Platform Release 6.2, also refer to:
Lucent Gateway Platform System Capacity, Monitoring, and Engineering (SCME)
Guidelines, chapter: Ethernet Interfacing, IP Addressing and SS7 Transport
Provisioning.
Before the Lucent Gateway Platform elements can be placed in service after
installation, they must be provisioned. To plan for initial provisioning, refer to: Lucent
Gateway Platform Planning and Engineering Guide, chapter: Planning for
Provisioning.
For configuration procedures for the Lucent Gateway Platform elements, refer to:
Lucent Gateway Platform Operation Manual, section: Detailed Level Procedures. For
upgrade tasks and procedures for the Lucent Gateway Platform, refer to: Lucent
Gateway Platform Maintenance and Troubleshooting Guide, section: Detailed Level
Procedures.
...................................................................................................................................................................................................................................
280-100-006R6.2.1
3-3
Geographic Redundancy
To provide failover capabilities for the Lucent Gateway Platform, the Lucent GP
elements can be installed in a geographically redundant configuration. This section
provides procedures to provision the Lucent GP elements for geographic redundancy
using the EMS, and upgrade or modify an existing Lucent GP configuration for
geographic redundancy in the Lucent VoIP Solution.
For procedures regarding upgrading and adding a geographically redundant Lucent
Gateway Platform configuration for the solution, refer to: Lucent Gateway Platform
Software Change Procedures, chapter: A Geographically Redundant System. Also refer
to: Lucent Gateway Platform Software Change Procedures, chapter: Task List Index,
section: Out-of-Service Upgrades or Downgrades, procedure: Upgrading
Geographically Redundant Switches to Version 6.2.
To provision geographic redundancy for the Lucent Gateway Platform elements in the
solution using the EMS, refer to: OMC-P User Guide for Lucent Gateway Platform
Management, chapter: Provisioning Geographic Redundancy.
For a description of Geographic Redundancy and the failover processess and events on
the Lucent Gateway Platform, refer to: Lucent Gateway Platform System Capacity,
Monitoring, and Engineering (SCME) Guidelines, chapter: Geographic Redundancy.
System Specifications
For system specifications for the Lucent Gateway Platform, refer to: Lucent Gateway
Platform Planning and Engineering Guide, chapter: System Specifications.
System Description
This section provides system requirements for each element of the Lucent Gateway
Platform distributed solution. The elements are the Lucent Network Gateway, Lucent
Network Controller, and Lucent Signaling Gateway.
For a description of the Lucent Gateway Platform hardware to be installed, refer to:
Lucent Gateway Platform Planning and Engineering Guide, chapter: System
Description.
Connectors and Cables
Refer to: Lucent Gateway Platform Planning and Engineering Guide, chapter:
Interconnect Drawings for all drawings and specifications regarding Lucent Gateway
Platform connectors and cabling.
...................................................................................................................................................................................................................................
280-100-006R6.2.1
3-4
B roadWorks Servers
4
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter provides references to the following engineering and planning

information: Capacity and performance monitoring, site preparation, system
specifications and system descriptions for BroadWorks servers in the Lucent VoIP
Solution.
Contents
4-2
...................................................................................................................................................................................................................................
280-100-006R6.2.1
4-1
BroadWorks Servers
BroadWorks
Servers Engineering
...................................................................................................................................................................................................................................
Purpose
This chapter provides references to capacity, performance monitoring, installation

planning, specifications, and system descriptions of the BroadWorks servers in the
Lucent VoIP Solution.
Capacity and Performance
This section provides references to processing capacity information and descriptions of

how capacity metrics are calculated for each BroadWorks server in the Lucent VoIP
solution. Also, to help plan for a BroadWorks configuration as part of the Lucent VoIP
Solution, refer to: BroadWorks System Capacity Planner.
To calculate the capacity for each server, refer to: BroadWorks System Engineering
Guide, chapter: Capacity, sections:
Application Server
Network Server
Media Server
Web Server
Conference Server.
For information regarding server resource requirements and calculating traffic volume,
refer to: BroadWorks System Engineering Guide, chapter: Traffic Modeling.
For a description of performance characteristics and how they are calculated for each
server, refer to: BroadWorks System Engineering Guide, chapter: Performance,
sections:
Application Server
Network Server
Media Server
Conference Server.
Engineering rules regarding the scalability of a BroadWorks server configuration are

provided in this section. For an overview of scalability, refer to: BroadWorks System
Engineering Guide, chapter: Scalability.
For a description of engineering rules including how to calculate the number of
subscribers to be supported by each server, refer to: BroadWorks System Engineering
Guide, chapter: Scalability, section: Engineering Rules, subsections:
Application Server
Network Server
...................................................................................................................................................................................................................................
280-100-006R6.2.1
4-2
BroadWorks Servers
Media Server
Conference Server.
Performance Monitoring and Reporting
For details regarding how to set the preferred limits and thresholds for the servers
before an alarm is triggered, refer to: BroadWorks Maintenance Guide, chapter:
Threshold Alarms. Also refer to: BroadWorks Maintenance Guide, chapter:
Performance Measurements. The CPU, memory utilization, and other limits and
thresholds should be determined based on the capacity calculations and estimates for
each server.
For a description of the performance measurements and monitoring scripts available for
each BroadWorks server in the Lucent VoIP Solution, refer to: BroadWorks
Performance Measurement Interface Specification, chapter: Performance
Measurements.
For reports information and a description of the reporting tools available for each
server, refer to: BroadWorks Performance Measurement Interface Specification,
chapter: Reports. To view performance reports using the EMS, refer to: BroadWorks
Element Management System Administration Guide Part 2, chapter: Performance
Management.
For a detailed description of generating and storing call detail records (CDRs) for
BroadWorks servers, refer to: BroadWorks Call Detail Record Interface Specification,
chapter: Functional Description.
Failover and Rollback Capabilities
For a description of Failover capabilities, refer to: BroadWorks Redundancy Guide,

chapter: BroadWorks Redundancy Solution. For more information regarding Failover,
also refer to: BroadWorks Call Detail Record Interface Specification, chapter: Call
Scenarios.
For a description of Rollback capabilities for the application server, refer to:
BroadWorks Redundancy Guide, chapter: BroadWorks Redundancy Solution, section:
BroadWorks Redundancy Walkthrough. Also, refer to: BroadWorks Redundancy Guide,
chapter: BroadWorks Redundancy Solution, section: BroadWorks Redundancy Key
Capabilities. To perform the Rollback procedure, refer to: BroadWorks Software
Management Guide, chapter: BroadWorks Rollback Procedure.
Installation Planning
This section provides references to upgrade procedures information, and details

regarding configuration during an initial installation. Refer to the: BroadWorks Software
Management Guide. To perform the upgrade procedure, refer to: BroadWorks Software
...................................................................................................................................................................................................................................
280-100-006R6.2.1
4-3
BroadWorks Servers
Management Guide, chapter: BroadWorks Upgrade Procedure. Configuration details

for an initial installation can be found in the BroadWorks Software Management Guide,
chapter: BroadWorks Initial Installation Procedure.
For information about configuring the BroadWorks server configuration for the VoIP
solution, refer to: BroadWorks System Engineering Guide, chapter: Hardware. Refer to:
BroadWorks Redundancy Guide for information about all server clusters in a
redundancy configuration.
For a complete list of specifications and hardware requirements for each server needed
in the solution, refer to: BroadWorks Recommended Hardware Guide.
Optimization and Testing
This section provides information about testing the performance, capacity, and
scalability characteristics of each server. Testing results can indicate if more
BroadWorks server capacity is needed in order to optimize the solution capacity.
For more information about validating these system characteristics as well as CPU and
memory utilization, refer to: BroadWorks System Engineering Guide, chapters:
Testing
Test Methodology
Test Suites - Summary
Test Suites - Detailed
Specifications
For a complete list of specifications of the hardware requirements for each server
needed in the solution, refer to: BroadWorks Recommended Hardware Guide.
System Description
For a description of server network architecture, management software and services,

refer to: Lucent VoIP Solution Solution Reference Manual.
...................................................................................................................................................................................................................................
280-100-006R6.2.1
4-4
S ession Border Controllers

5
Overview
...................................................................................................................................................................................................................................
Purpose
This chapter provides references to planning and engineering information for the
AcmePacket session border controller in the Lucent VoIP Solution.
Contents
Session Border Controllers Engineering
5-2
...................................................................................................................................................................................................................................
280-100-006R6.2.1
5-1
Session Border Controllers
Session
Border Controllers Engineering
...................................................................................................................................................................................................................................
Purpose
This topic provides references to system aspects of the AcmePacket session border
controllers. Use the information in this chapter to plan the installation and monitor the
performance of session border controllers in the Lucent VoIP solution.
AcmePacket
For information regarding planning for an AcmePacket installation, refer to: Net-Net
System Hardware Installation Guide, chapter: System Installation, section:
Preinstallation.
To prepare for the installation of the AcmePacket session director EMS, refer to:
Net-Net EMS Installation Guide, chapter: Installation Net-Net EMS, section: Before
You Start.
AcmePacket Specifications
To access technical specifications for the AcmePacket session border controller, refer
to: Net-Net System Hardware Installation Guide, chapter: Specifications.
Performance Monitoring
Performance data and measurements can be gathered and used to analyze SBC
performance and capacity and optimize the solution.
For AcmePacket session border controllers, refer to: Net-Net Session Director
Maintenance and Troubleshooting Guide, chapter: Performance Management.
...................................................................................................................................................................................................................................
280-100-006R6.2.1
5-2
A nyPath Messaging System

6
Overview
...................................................................................................................................................................................................................................
Purpose
AnyPath Messaging System in the Lucent VoIP Solution.
Contents
AnyPath Messaging System Engineering
6-2
...................................................................................................................................................................................................................................
280-100-006R6.2.1
6-1
AnyPath Messaging System
AnyPath
Messaging System Engineering
...................................................................................................................................................................................................................................
Purpose
This chapter provides references to system aspects of the AnyPath Messaging System.
Use the information in this chapter to plan the installation and use of the AnyPath
Messaging System as part of the Lucent VoIP Solution.
Planning and Engineering Overview
For an overview of how to plan and engineer the AnyPath Messaging System, refer to:
AnyPath Messaging System Online Documentation, chapter: Engineering Guide.
Also, refer to: AnyPath Messaging System Online Documentation, chapter: System
Description , section: Physical Design Specifications for an overview of AnyPath
Messaging System hardware and system functions.
Capacity and Performance Monitoring
For information regarding system aspects, capacity data, and data representation and
reporting for the AnyPath Messaging System, refer to: AnyPath Messaging System
Online Documentation, chapter: Engineering Guide.
For performance data and reporting of the messaging system, refer to: AnyPath
Messaging System Online Documentation, chapter: Preventive Maintenance , section:
Monitor the LAN/WAN.
Optimization
System resources can be grown and de-grown to optimize performance and perform
load balancing. Refer to: AnyPath Messaging System Online Documentation, chapter:
Engineering Guide, sections: Growth; De-Growth.
Engineering
For information regarding network connectivity, refer to: AnyPath Messaging System
Online Documentation, chapter: Engineering Guide, section: TDM Network
Connectivity.
For all other system aspects including planning for resource growth, refer to: AnyPath
Messaging System Online Documentation, chapter: Engineering Guide.
Specifications
Refer to: AnyPath Messaging System Online Documentation, chapter: System

Description , section: Physical Design Specifications for all system specifications for
the AnyPath Messaging System.
...................................................................................................................................................................................................................................
280-100-006R6.2.1
6-2
7 ucent Security Manager and

L
VPN Firewall
Overview
...................................................................................................................................................................................................................................
Purpose
Lucent Security Manager and VPN Firewall in the Lucent VoIP Solution.
Contents
7-2
...................................................................................................................................................................................................................................
280-100-006R6.2.1
7-1
Lucent
Security Manager and VPN Firewall Engineering
...................................................................................................................................................................................................................................
Purpose
This chapter provides references to system aspects of the Lucent Security Management
System (LSMS) and VPN Firewall Brick. Use the information in this chapter to
determine system capacity, monitor performance, and plan the installation and use of
the LSMS and VPN Firewall Brick as part of the Lucent VoIP solution.
Capacity and Performance Monitoring
To determine the hardware capacity requirements needed for the LSMS software, refer
to: Lucent Security Management Server Administrative Guide, chapter: Appendix B:
Sizing Guidelines. For capacity and performance information for the VPN Firewall
Brick, refer to: Lucent Security Management Server Technical Overview, chapter:
VPN Firewall Brick , section: Capacity/Throughput.
For performance data reporting using the LSMS, refer to: Lucent Security Management
Server Reports, Alarms, and Logs Manual, chapters: Administrative Events Report;
Sessions Logged Report.
To configure and monitor an LSMS redundancy configuration, refer to: Lucent Security
Management Server Administrative Guide, chapter: LSMS Redundancy.
VPN Brick Installation
To prepare for the installation of the VPN Brick hardware, refer to: Lucent VPN
Firewall Model 150 Brick Users Guide, chapter: Introduction, and Lucent VPN
Firewall Model 1100/1100A Brick Users Guide, chapter: Introduction. Also, refer to
the Lucent VoIP Solution Reference Manual for a description of the VPN Brick
firewall hardware.
Lucent Security Manager Installation
To plan for an installation of the LSMS software, and review the hardware and
software requirements, refer to: Lucent Security Manager Server Installation Guide,
chapters: Installing LSMS on a Windows Server Platform; Installing LSMS on a
Solaris Server Platform.
Specifications
The VPN Brick is available in different models for different applications. For system
specifications of each model of VPN Brick hardware, refer to: Lucent VPN Firewall
Model 150 Brick Users Guide, chapter: Specifications, and Lucent VPN Firewall
Model 1100/1100A Brick Users Guide, chapter: Specifications.
...................................................................................................................................................................................................................................
280-100-006R6.2.1
7-2
System Description
For a system description of the Lucent VPN Firewall system, refer to: Lucent Security
Management Server Technical Overview.
...................................................................................................................................................................................................................................
280-100-006R6.2.1
7-3
Glossary
....................................................................................................................................................................................................................................
ALG
Application Layer Gateway

API
Application Programming Interface

AS
Application Server
....................................................................................................................................................................................................................................
BE
Border Element
BGCF
Breakout Gateway Control Function

....................................................................................................................................................................................................................................
CA
Call Agents (also referred to as Media Gateway Controllers)

CCE
Call Control Element

CCITT
Comite Consultatif International Telegraphique et Telephonique or International

Telegraph and Telephone Consultative Committee
CDR
Call Detail Record

CDS
Call Detail Server
....................................................................................................................................................................................................................................
280-100-006R6.2.1
GL-1
Glossary
CLI
Command-line Interface
COPS
Common Operations: A software breakthrough by researchers at Bell Labs that will

enable global roaming across all wireless network types, including third-generation (3G)
technologies such as CDMA2000, UMTS and other high-speed data access technologies.
CPE
Customer Premises Equipment

CSCF
Call Session Control Function

....................................................................................................................................................................................................................................
DMZ
Demilitarized Zone (In access routers can be an intermediate network between outside
world port and inside LAN neither visible from outside nor from inside. Some
applications that do not run over a firewall, due to connection restrictions from outside
can run using DMZ).
DND
Dialled Number Display

DNS
Domain Name System

DoS
Denial of Service
DTMF
Dual Tone Multi Frequency

....................................................................................................................................................................................................................................
EML
Element Management Layer

EMS
Element Management System

ENUM
tElephone NUmber Mapping: protocol that makes a machine readable DNS address from
a phone number. The DNS can use this last address to link caller and recipient via
telephone, pager, mobile telephone, email, or personal digital assistant.
...................................................................................................................................................................................................................................
280-100-006R6.2.1
GL-2
Glossary
eTOM
enhanced - Telecom Operations Map: The enhanced Telecom Operations Map is the
most widely used and accepted standard for business process in the telecom industry.
The eTOM describes the full scope of business processes required by a service provider
and defines the key elements and how they interact, creating a guidebook that is fast
becoming the common business language of the telecom industry.
ETSI
European Telecommunications Standards Institute

EWS
External Web Server

....................................................................................................................................................................................................................................
FCAPS
Fault, Configuration, Accounting, Performance, Security Management

FQDN
Fully Qualified Domain Name

FTP
File Transfer Protocol

FXO
Foreign Exchange Office

....................................................................................................................................................................................................................................
GSM
Global System for Mobile Communications

GUI
Graphical User Interface

....................................................................................................................................................................................................................................
H.248
International standard for multimedia communication over PS networks (LAN, WAN,

Internet) defined by ITU in 1996. ITU-T recommendation for MEGACO.
HSS
Home Subscriber Server

HTTP
HyperText Transfer Protocol (The Internet standard protocol for transferring data over
the World Wide Web; WWW; This is the internet protocol used to fetch hypertext
objects from remote hosts. It is based on TCP/IP; protocol used for file retrieval on the
Web; usenet; a NNTP like internet protocol).
...................................................................................................................................................................................................................................
280-100-006R6.2.1
GL-3
Glossary
HTTPS
HyperText Transfer Protocol Secure

....................................................................................................................................................................................................................................
IAD
Integrated Access Device

ICD
Internet Call Diversion

IDS
Information Delivery System

IETF
Internet Engineering Task Force

IM-SSF
IP Multimedia Service Subsystem Switching Function

IMAP4
Internet Mail Access Protocol version 4

IMS
IP Multimedia Subsystem: IP terminated at handset. All packet, including voice. A data

paradigm for wireless real-time services including voice. IMS is a multimedia control
platform, i.e. it enables operators to support and to control SIP-based applications and
communications services. 3GPP has defined the IP Multimedia Core Network
Subsystem as part of UMTS Releases 5. 3GPP reuses existing IETF protocols wherever
possible (SIP, SIMPLE, IPv6, IPSec, COPS, MeGaCo,..).
IP
Internet Protocol
IP BE
IP Border Element
IP CENTREX
IP version of Centralized Telephone Communications Exchange Service

IPDC
Internet Protocol Device Control

IPS
Information Processing System

IPSec
Internet Protocol Security

...................................................................................................................................................................................................................................
280-100-006R6.2.1
GL-4
Glossary
IPv6
Internet Protocol version 6

ISC
IMS Services Control

ISG
Intelligent Services Gateway (MiLife)

ITU
International Telecommunication Union

IVR
Interactive Voice Response

....................................................................................................................................................................................................................................
JASS
JumpStart Architecture and Security Scripts. The JASS toolkit simplifies and automates
the process of securing Solaris Operating Environment systems.
....................................................................................................................................................................................................................................
KPI
Key Performance Indicator

KQI
Key Quality Indicator

....................................................................................................................................................................................................................................
LAN
Local Area Network

LDAP
Light/Lightweight Directory Access Protocol: Protocol for accessing directory servers,

e.g., to find a person or service, or locate a user. Example: X.500 - Directory (Layer 7.
X.500 describes several protocols that implement a world wide directory service. This is
like an electronic phone book, where you can search persons, institutions, servers,
routing tables, management information, document stores, network addresses, etc.
LMT
Local Maintenance Terminal

LocationAPI
Network Server Portal API
...................................................................................................................................................................................................................................
280-100-006R6.2.1
GL-5
Glossary
....................................................................................................................................................................................................................................
M2UA
SS7 MTP2-User Adaptation Layer

MAC
Media Access Controller

MC
Module Controller
MCP
Media Server Control Protocol

MeGaCo
Media Gateway Control

MG
Media Gateway
MGC
Media Gateway Control

MGCF
Media Gateway Control Function

MGCP
Media Gateway Control Protocol

MIBS
Multiple Independent Bwm Stream

MPLS
Multi-Protocol Label Switching: Internet; Procedures that allow for the attaching of
labels to packet cells, and therefore simplified switching of cells in a connectionless
manner; Helps provide QOS in IP networks; MPLS is a label swapping and forwarding
technology which integrates label swapping and network layer routing. Label swapping
refers to the changing of a label value in the packet header as the packet traverses the
MPLS network; Procedures that allow for the attaching of labels to packet cells, and
therefore simplify switching of cells in a connectionless manner.
MRFC
Media Resource Function Control

MRFP
Media Resource Function Processor

MS
Media Server
...................................................................................................................................................................................................................................
280-100-006R6.2.1
GL-6
Glossary
MSS
Media Server Selection

MTP
Message Transfer Part

MTTR
Mean Time To Repair/Recover/Replace/Restore / Mean Time Trouble Repair

MWI
Message Waiting Indicator

....................................................................................................................................................................................................................................
NAPT
Network Address Port Translation

NAT
Network Address Translation. System or protocol for translating network addresses on

one network to those usable by another; NATs are one technique to keep up with the
growth of IP address use, and can help to avoid having to renumber hosts, and to
provide some network security.
NEL
Network Element Layer

NGBE
Network Gateway Border Element

NIC
Network Interface Card

NML
Network Management Layer

NMS
Network Management Subsystem

NRE
Network Routing Engine

NS
Network Server
NTP
Network Time Protocol
...................................................................................................................................................................................................................................
280-100-006R6.2.1
GL-7
Glossary
....................................................................................................................................................................................................................................
OAM&P
Operations, Administration, Maintenance, and Provisioning

OMC
Operations Maintenance Center

OMC-CN
Operation Maintenance Center Core Network

OSA
Open Services Architecture

OSA-SCS
Open Services Architecture-Service Capability Server

OSS
Operation/s Support System / Operational Support System / Operations Systems and

Software
....................................................................................................................................................................................................................................
P2P
Peer-to-Peer: architecture model used in the Internet. P2P is to truly replace the
well-established client-server model as the computing paradigm of the future, but needs
more efficient decentralized algorithms.
PAT
Port Address Translation

PBX
Private Branch Exchange

PDP
Packet Data Protocol

PIM
Personal Information Manager

POP
Point of Presence
POP3
Post Office Protocol version 3

PRI
Primary Rate Interface
...................................................................................................................................................................................................................................
280-100-006R6.2.1
GL-8
Glossary
PS
Packet Switched/Packet Services

PSTN
Public Switched Telephone Network

....................................................................................................................................................................................................................................
QoE
Quality of Experience
QoS
Quality of Service
....................................................................................................................................................................................................................................
RAS
Remote Access System

RFC
Request For Comments (Internet document; An archived series of documents in the

IETF; The official publication channel for standards and standards-track documents for
the internet. Publisher is the IAB (Internet Architecture Board). Refer to: NIC Network
Information Center) at the SRI (Stanford Research Institute). RFCs are available
electronically from the Internet Network Information Center.
RPC
Remote procedure call (Executing what looks like a normal procedure call (or method
invocation) by sending network packets to some remote host; System).
RS-232
Digital communication standard

RSYNC
Remote file Synchronization

RTCP
Real Time Control Protocol (H.323)

RTP
Real Time Protocol

RTP
Real-time Transport Protocol

....................................................................................................................................................................................................................................
SB
Service Broker
...................................................................................................................................................................................................................................
280-100-006R6.2.1
GL-9
Glossary
SBC
Session Border Controller

SCCP
Signaling Connection Control Part

SCIM
Service Control Interface Manager

SCP
Service Control Point

SCS
Service Capability Server

SD
Session Director (i.e. AcmePacket Session Director)

SDP
Session Description Protocol

SG
Signaling Gateway
SGBE
Signaling Gateway Border Element

SIP
Session Initiation Protocol

SMS
Switch Maintenance Subsystem / Systems Management Server / Subnetwork

Management System
SMTP
Simple Mail Transport Protocol

SNE
Sub-Network Element
SNMP
Simple Network Management Protocol

SoIP
Services over Internet Protocol

SS7
Signaling System 7
...................................................................................................................................................................................................................................
280-100-006R6.2.1
GL-10
Glossary
SSH
Secure Shell
SSL
Supplementary Service Layer

Sub NEL
Sub-Network Element Layer

....................................................................................................................................................................................................................................
TAOS
True Access Operating System

TCP
Transmission Control Protocol (A highly reliable, DoD standard host-to-host protocol

used over packet-switched computer communication networks; Transport Control
Protocol; TCP is a major Internet protocol, at higher level than IP; enables two hosts to
establish a connection and reliably exchange data).
TDM
Time Division Multiplex

TELNET
Telecommunications Networking (Remote terminal login program and protocol used on

the Internet.)
TMN
Telecommunication Management Network

....................................................................................................................................................................................................................................
UM
Unified Messaging
UMTS
Universal Mobile Telecommunication System

URI
Uniform Resource Identifier

URL
Uniform Resource Locator/Location

....................................................................................................................................................................................................................................
VIP
Virtual IP Address
...................................................................................................................................................................................................................................
280-100-006R6.2.1
GL-11
Glossary
VLAN
VPN Local Area Network: 3 fully meshed functional subnets across all sites in an
application providing Access-Bearer, Access-Signal and Control functions.
VoIP
Voice over IP
VoPM
Voice over Packet Markets

VPN
Virtual Private Network

VR
Virtual Router
VRF
VPN Routing and Forwarding

VRRP
Virtual Router Redundancy Protocol

....................................................................................................................................................................................................................................
WAN
Wide Area Network

WDM
Wave Division Multiplexing
...................................................................................................................................................................................................................................
280-100-006R6.2.1
GL-12

Voip

Caricato da

Informazioni sul documento

Titolo 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

Voip

Caricato da

Copyright:

Formati disponibili

See notice on first age

Lucent VoIP Solution

Lucent Technologies - Proprietary

See notice on first age

Lucent Technologies - Proprietary

About this information product

Lucent VoIP Solution Engineering

Lucent VoIP Solution Engineering Overview

Lucent VoIP Solution architecture

Information product support

How to use this information product

Lucent Gateway Platform

Lucent Gateway Platform Engineering

BroadWorks Servers Engineering

Session Border Controllers

Session Border Controllers Engineering

AnyPath Messaging System

AnyPath Messaging System Engineering

Lucent Security Manager and VPN Firewall

Lucent Security Manager and VPN Firewall Engineering

About this information product

Engineers with reponsibility for network planning, design, configuration or

This IP contains conceptual information about the Lucent VoIP Solution.

This information product provides references to network and site planning,

About this information product

Lucent VoIP Solution Operations, Administration, Maintenance and Provisioning,

Information product support

The document support telephone numbers are:

1 888 727 3615 (for the continental United States)

To comment on this information product, go to the Online Comment Form

1 ucent VoIP Solution

This chapter gives an overview of Lucent VoIP Solution engineering.

Lucent VoIP Solution Engineering

The number of VoIP subscribers.

Derived Data Calculations

Lucent VoIP Solution Engineering

Lucent VoIP Solution Engineering Overview

The Number of UE to PSTN calls = (Number of VoIP Subscribers) x (Number of

Configuring the Lucent VoIP Solution

Lucent VoIP Solution Engineering

Lucent VoIP Solution Engineering Overview

The following list defines the terms in the diagram:

Lucent VoIP Solution Engineering

Lucent VoIP Solution Engineering Overview

Lucent Element Management System (EMS)

Use the following URL to access Sun Microsystem server documentation:

Lucent VoIP Solution Engineering

Lucent VoIP Solution Engineering Overview

L ucent VoIP Architecture

Lucent VoIP Architecture

Architecture of the Lucent VoIP Solution with the main elements:

MGCP, end clients

Lucent VoIP Architecture

Lucent VoIP Solution architecture

Lucent Gateway Platform

The Lucent Gateway Platform Network Controller

The Integrated Access Device Application Server (IAD

Lucent Network Gateway

Performs the media gateway (MG) function of coding and

Voice mail system which offers mail services for IP

Session Border Controller

Element to add functionalities such as security and service

Call Manager (CM)