Académique Documents
Professionnel Documents
Culture Documents
1a
Disclaimer
This documentation is provided for reference purposes only and does not fully describe the capabilities of each Product and related features. Therefore, ALE International declines any liability
for inaccuracies contained herein. For an exhaustive view on features list and product limits for the current product release please see the required Feature List/Product Limits document
available through the ALE eBusiness Portal web site.
In the interest of continued product development, ALE International reserves the right to make improvements or other changes to this document and the products it describes at any time
without prior notice.
Copyright
Copyright ALE International 2017. Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder.
Distribution of the work or derivative of the work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder.
The objective of this presentation is to introduce a tool aimed at sizing a physical server or a
Virtual Machine for the OpenTouch system, depending on its configuration (in terms of media
ports, codec used, etc...) :
The present edition includes the evolutions brought by OTCP v2.2.1 / v2.2.1a version
1. Introduction
2. Software modeling
3. Graphical User Interface
4. Use cases
5. Reference documents
Since OT R1.2
- Various dimensioning steps
- Based solely on users figures
CPE
Determine platform suitability to handle a (*) not delivered by Alcatel-Lucent
Virtualized environment
Private Data Center
given deployment Enterprise
CPE - Cloud / UCaaS
SUPPORTED SYSTEMS
OTMS OTMC (*) OTBE
(***) the pre-requisites of a non virtualized OTBE system include OXE and OV8770 components, and can include the
optional OXE-MS and DCS components
OTBE-V is not taken into account as OTCP does not modelize OXE-V, OV8770-V, virtual machines
SUPPORTED RELEASES
OpenTouch R2.2.1
OTCP sizing now accounts for the average number of OTC clients per user (from 0 to 2)
Disk characteristics (throughput, read/write IOPS) are added in OTCP results
- Backup partition and inactive partition are also taken into account in non virtualized deployments
Two exclusive OpenTouch High Availability modes are available: local HA / HA over extended LAN
- Impact on both CPU consumption and network bandwidth for inter-server HA traffic
Support of OpenTouch networking, which impacts the global network bandwidth computation of the OpenTouch system
Computed and custom modes have been merged as the processor architecture choice imposes the number of cores
The CPU consumption chart, in case of OTMS-V, is labeled in vCPUs rather than % CPU
Processors list update, with new processors up to December 2016
ALE OTBE server ONE based on Lenovo X.3250 M6 has been added
A Help tab is added to provide a description of OTCP main window
1. Introduction
2. Software modeling
3. Graphical User Interface
4. Use cases
5. Reference documents
Dynamic +
limits search
Platform OK or
System overload
OTCP uses software modeling based on actual measures to predict server load, without the need
of specific test campaign on the concerned deployment profile
- Reference data established through measurements of individual media interaction
CPU used to sustain one interaction of a given usage and using a certain codec
3 party conference, voicemail deposit, voicemail consultation, Automated Attendant call, system prompts,
Used for OpenTouch Media Server modeling
- Reference data based on measures conducted in busy hour OTMS test campaign
Activity of a Connection /Conversation user for non media-related interactions
- The model assumes that each user is using a software client
Telephony traffic assumption : 4 calls/hour/user, 0.16 erlangs
Used for Connection/Conversation user modeling
These reference data being release dependent, each OpenTouch release will have its own
version of OTCP tool
OpenTouch Capacity Planning tool v2.2.1 / v2.2.1a Ed01a 11
Pre-Sales COPYRIGHT 2017 ALE International. ALL RIGHTS RESERVED.
INPUTS : PROVISIONING
USERS
Possibility to modulate the sizing based on the average number of OTC clients per user
- OTCP allows values from 0 up to 2 clients per user
Concerns OTC PC (Windows/Mac), OTC smartphone (iPhone/Android), OTC tablet (iPad/Android), OTMC for Android smartphone
Automated
11 25 44 69 25 75
Voice Mail Attendant
VOICE MAIL
Conferencing
(3 party & Ports not quotable in Actis but linked to H/W platform
N party, audio & Ports not chargeable (per user price)
video)
AUTOMATED ATTENDANT
Ports quotable in Actis
Ports chargeable
CONFERENCING
No capacity trading between the various
pools of ports Ports are quotable in Actis
Static management of ports Ports chargeable
low high
Number of users and OTC clients, Backup partition & inactive partition
Number of media ports (non virtualized deployments only)
NEW
Deployment profile (codecs usage)
Disk throughput and IOPS
System options (HA, networking, )
Network storage pre-requisites
Processor generation : NETWORK BANDWIDTH Direct Attached Storage: add disk
throughput to network bandwidth
Modulation of the computed pre- Computed value, based on :
requisite based on the targeted
processor Provisioning (number of users, media ports)
Deployment profile (codecs usage, HA )
1. Introduction
2. Software modeling
3. Graphical User Interface
4. Use cases
5. Reference documents
Input : Parameters
characterizing
the deployment
Provisioning figures
Nominal :
Actis recommended
values
Output :
Max CPU% :
Typically between
70% and 80%
NEW
Actis 19.4
min.
Low level
Medium level
Reminder: maximum 10 ports for OTMS/OTBE embedded fax
High level server. For more ports, a stand alone OTFC has to be considered
Compression
OTMS
Headquarter due to CAC Remote site
PSTN/SIP
PSTN/SIP
WAN p trunks
n trunks
Compression
OTMS
Headquarter due to CAC Remote site
Ratio = p/(n+p)
Narrowband-only deployment
- Parameter to check when OpenTouch Media Server configured to enforce narrowband interaction only
Platform pick-list :
I am just interested by the OTMS-V I have a hardware platform amongst the I have a hardware platform with a given
Virtual Machine pre-requisites, pre-defined ones and I want to know if I processor type, that is not amongst the
based on the physical host can use it for this OpenTouch deployment pre-defined ones ,and I want to know if
processor type I can use it for this deployment
List of hardware platforms qualified by ALE The pre-defined OTMS G7, OTMS G8 and OTMS G9
entries correspond to servers provided by ALE, so with
- A BP may add hardware platforms commonly used Actis user limitation to resp. 1500 and 3000 (*)
Platform name OTBE Max users Server type CPU index CPU type CPU cores CPU MHz Total MHz RAM (GB) Disk (GB) Eth (Gbps)
Computed OTMS-V Virtual Machine 0 5000 -
Computed OTMS server 0 5000 -
Custom OTMS server 0 5000 -
ALE OTBE 500 G7 1 500 HP DL120 G7 27 Xeon E3-1230 1 x 4 cores 3.2 GHz 4 3,20 12800 20 500 1
ALE OTBE 500 G8 1 500 HP DL320e G8 28 Xeon E3-1230 v2 1 x 4 cores 3.3 GHz 4 3,30 13200 20 500 1
ALE OTBE 1500 G7 1 1500 HP DL380 G7 4 Dual Xeon E5620 2 x 4 cores 2.4 GHz 8 2,40 19200 20 500 1 Ethernet parameter
ALE OTBE 1500 G8 1 1500 HP DL380p G8 63 Dual Xeon E5-2620 2 x 6 cores 2.0 GHz 12 2,00 24000 24 1000 1 should be restricted
ALE OTBE Server One 1 1000 Lenovo X3250 M5 31 Xeon E3-1231 v3 1 x 4 cores 3.4 GHz 4 3,40 13600 20 1000 1
ALE OTMS G7 0 1500 HP DL380 G7 4 Dual Xeon E5620 2 x 4 cores 2.4 GHz 8 2,40 19200 20 500 1
to 1 GB as OpenTouch
ALE OTMS G8 0 3000 HP DL380p G8 63 Dual Xeon E5-2620 2 x 6 cores 2.0 GHz 12 2,00 24000 24 1000 1 systems have not
ALE OTMS G9 0 3000 HP DL380 G9 65 Dual Xeon E5-2620 v3 2 x 6 cores 2.4 GHz 12 2,40 28800 24 1000 1 been qualified with
OTMS G9 - HP reseller 0 5000 HP DL380 G9 65 Dual Xeon E5-2620 v3 2 x 6 cores 2.4 GHz 12 2,40 28800 24 1000 1 10 GB interfaces
Undefined 0 5000 Custom platform 2 34 Xeon E3-1240 v3 1 x 4 cores 3.4 GHz 4 3,40 13600 20 850 1
Undefined 0 5000 Custom platform 3 34 Xeon E3-1240 v3 1 x 4 cores 3.4 GHz 4 3,40 13600 20 850 1
GUI window help online tab Deployment profiles pick list customization tab
29
n
.7
sio
sio
G
d
es
es
an
g
in
pr
pr
eb
rc
m
m
id
fo
nd
co
co
en
ba
ng
g
g
s
in
in
ss
w
er
i
us
us
us
r ro
ce
us
s
s
ac
na
CV
er
er
er
us
us
us
TN
e
rc
of
CV
PS
CT
CT
Fo
Profile Comments
%
Input :
Parameters
characterizing the
deployment
Provisioning figures
Nominal :
Actis recommended
values
1. Introduction
2. Software modeling
3. Graphical User Interface
4. Use cases
Pre-requisites optimization
Platform & provisioning limit
Ports adaptation
Over-limit deployment
Ports provisioning flexibility
5. Reference documents
OpenTouch Capacity Planning tool v2.2.1 / v2.2.1a Ed01a 28
Pre-Sales COPYRIGHT 2017 ALE International. ALL RIGHTS RESERVED.
USE CASE 1 : PRE-REQUISITES OPTIMIZATION
CPU core GHz : 2.4 GHZ (host with Dual Xeon E5-2620 v3)
vCPUs 18 10 5
2380 users 1020 users Applicative services given to the users + OTMS HA
150 trunks (PSTN) 50 trunks (No specific needs in term of ports)
Use nominal values (same as Actis) if All users have a wideband capable device (Premium Deskphone)
no specific requirements are given and G.722 codec is activated on the OXE
OpenTouch Capacity Planning tool v2.2.1 / v2.2.1a Ed01a 30
Pre-Sales COPYRIGHT 2017 ALE International. ALL RIGHTS RESERVED.
USE CASE 2 : PLATFORM & PROVISIONING LIMIT platform suitability to
handle the specified
OTMS deployment
Entry added in Platform tab
Pre-requisites computed
by OTCP for the specified
deployment and the
given Max CPU %
The Media Server CPU usage increase with the number of cores it will run on (for similar processor generation)
OpenTouch Capacity Planning tool v2.2.1 / v2.2.1a Ed01a 31
Pre-Sales COPYRIGHT 2017 ALE International. ALL RIGHTS RESERVED.
USE CASE 2 : PLATFORM & PROVISIONING LIMIT
CAUTION : Any future add-on will require a change of hardware platform if there is no margin left
Use of lower value in Max CPU % to include a margin for future add-on
Maximum CPU load expected during the busy hour (typically Enter the processor characteristics of the targeted
comprised between 70 and 80%) to preserve some resource hardware platform: OTCP will determine its suitability
for maintenance operations or user activity spikes
Note : if the same platform is often used by the BP, it can be
included in the pick-list via the Platform tab
Features add-on
OpenTouch Capacity Planning tool v2.2.1 / v2.2.1a Ed01a 35
Pre-Sales COPYRIGHT 2017 ALE International. ALL RIGHTS RESERVED.
USE CASE 4 : OUT OF RANGE DEPLOYMENT
I want to determine the Virtual Machine pre-requisites of this 100% Connection deployment
All users have IP Touch EE (wideband capable)
OTMS-V, result of a migration from ICS/ACS No remote site enforcing compression
No SIP Trunking
Applicative services given to the users
ACS/ICS migration towards OTMS
450 users (No specific needs in term of ports, except Conferencing)
Specific requirements :
800 conferencing audio ports
(ACS current sizing)
Voice Mail Conferencing
The OTMS needs to be virtualized
OTMS
The required host has to accommodate a virtual machine with the following characteristics :
Hypervisor overhead
included in the
Computed CPU GHz
value
This deployment
requires 13 vCPUs
whereas the
processor has only
12 cores
OTMC Compression
Headquarter Remote site
The specific edition of OTCP tool, dedicated to OTMC, has to be used instead of the OTMS edition
Provides additional pre-requisites optimization: removal from the software model of components unused by OTMC
OpenTouch Capacity Planning tool v2.2.1 / v2.2.1a Ed01a 39
Pre-Sales COPYRIGHT 2017 ALE International. ALL RIGHTS RESERVED.
USE CASE 6 : OTMC
As of Actis 20.0, it is possible to quote the number of messaging ports (voicemail & AA) in order to benefit
from the flexibility introduced by OTCP, as well as improved product limits
- Refer to slide 15 for more details
- In previous Actis versions, the license was automatically generated with a fixed number of Voicemail and AA ports
1. Introduction
2. Software modeling
3. Graphical User Interface
4. Use cases
5. Reference documents
Pre-Sales documents
OpenTouch Suite for MLE in virtualized environment, overview (updated for H2 2016 offer)
OpenTouch Suite for MLE - Virtualization Design Guide (updated for H2 2016 offer)
Facebook.com/ALUEnterprise
Youtube.com/user/enterpriseALU
Slideshare.net/tagged/Enterprise
Storify.com/ALUEnterprise
Busy-hour performance testing consists in simulating the load generated by a target user
population during the busiest hour of the busiest day of the year
On a given platform
User activity spans as many relevant usages as possible, inducing significant CPU load
Using nominal traffic assumptions for all usages
Using certain deployment assumptions
All users are logged on using hard phone + software client UDA search + click-to-call
- Average number of OTC clients per user: from 0 to 2 Media interactions to occupy all available ports
Device monitoring enabled for CT and CV users System guides
All CV users have 2 devices on which all calls are forked Voicemail record + consultation
SIP registration renewals + OPTIONS keep Alive + Automated attendant access
applicative subscribe/notify for all devices
3-way and 6-way conferencing
Supervision enabled up to the supported link limit
With or without High Availability
1pcc telephony: 4 calls/hour/user, 0.16 erlangs
With or without OpenTouch networking
Client login + eventing
With or without multi-partitioning
OpenTouch Capacity Planning tool v2.2.1 / v2.2.1a Ed01a 45
Pre-Sales COPYRIGHT 2017 ALE International. ALL RIGHTS RESERVED.