Compatibility and Performance with Arc Pro Version 6.0.0

Compatibility and Performance with Arc Pro Version 6.0.0
Compatibility and
Performance with
Arc Pro
Version 6.0.0
Released: August 2013
This document provides a comprehensive overview of Arc Pro version 6.0.0 and
compatibility with operating environments, software, hardware and the utilization of
bandwidth.
You can access the most current Arc Pro documentation at this URL:
http://enghouseinteractive.co.uk/console-cisco-enterprise-edition-technicaldocumentation
You can access the Arc Solutions website via:
http://www.arcsolutions.com
Join the Arc Solutions Forum at:
http://forum.arcsolutions.com
Registered partners can access the Arc Solutions Extranet via
www.arcsolutions.com/extranet
Contents
Related Arc Documents ................................................................................................................... 3
Compatibility ...................................................................................................................................... 3
VMWare Platform Support ............................................................................................................ 4
Citrix Support................................................................................................................................... 5
Cisco Unified Communications Manager Compatibility ......................................................... 6
Known issue in CUCM 8.6.2 ........................................................................................................... 6
SQL Server Support......................................................................................................................... 6
Technologies Matrix ....................................................................................................................... 7
System Requirements ...................................................................................................................... 10
Console Server and Client (Console) Computer .................................................................... 10
Arc Pro Server ............................................................................................................................... 10
Anti-Virus Compatibility ............................................................................................................... 11
Exclusions ................................................................................................................................... 12
Cisco UCS Servers ..................................................................................................................... 12
Arc Pro Client ................................................................................................................................ 13
Supported Handsets ........................................................................................................................ 15
Performance and utilisation ........................................................................................................... 20
General bandwidth recommendations ................................................................................... 20
Codec Considerations ............................................................................................................ 20
Network Latency Limitations ...................................................................................................... 20
Attendant Console ...................................................................................................................... 20
Directory and Busy Lamp ........................................................................................................ 21
Presence integration................................................................................................................ 21
Server ............................................................................................................................................. 22
Database Synchronisation with CUCM (Arc 5.1.1 onwards).............................................. 22
Server Resilience (Replication with SQL 2008 Enterprise) .................................................... 22
LDAP or equivalent integration .............................................................................................. 23
Voice Connect............................................................................................................................. 23
Supervisor ...................................................................................................................................... 24
Wallboard (tests based on the 1.4.2 example configuration) .............................................. 24
Compatability and Performance with Arc Professional Version 6.0.0
2
Related Arc Documents
When using this document please also consult the following:•
•
•
•
•
Arc Compatibility Matrix for the Cisco Unified Communications Manager supported by Arc
software versions
Arc Design Guide for a wealth of best practices and detail on planning your deployment
Arc Pro Edition Installation Manual v 6.0.0 or for older versions of Arc, the individual installation
documents for your server component or client applications
Arc Pro Configuration Manual v 6.0.0 provides a comprehensive overview of the configuration of
the server component.
CUCM Configuration Manual for Arc Pro v6.0.0 provides description on the configuration
requirements within the Cisco Unified Communication Manager software for versions 7.x, 8.x and
9.x. (These are also provided as three separate documents)
Compatibility
This section describes CUCM and OS compatibility in both hardware-based and virtual
environments. The virtual environment is VMWare (ESX/ESXi).
CUCM
7.1
8.0
Server 2003
R1

(1)(3)
Server 2003
R2

(1)(3)
Server 2008 R1
Server 2008
R2
32bit
64bit
64bit



(2)





8.5




8.6














9.0
9.1
Definition of
Limited Support
(1)
(2)
(2)
(2)
(2)
(2)


(2)
(2)
(2)
If a problem is diagnosed as being a fault in Arc software and
not relating to the server platform itself, Arc will investigate the
problem via the normal process and consider the option of
providing bug fixes for the software. However, if the problem is
diagnosed as being directly related to the server platform, Arc
Solutions reserves the right to request that the server platform is
upgraded to one fully supported before further diagnosis and
Compatability and Performance with Arc Professional Version 6.0.0
3
be completed and any bug fixes considered.
(2)
Windows 2008
support
Supported by Arc Solutions and Cisco Systems. Refer to Cisco TSP
documentation at http://developer.cisco.com/web/tapi/docs
Support for
Windows 2003
ended 13/07/2010
Windows 2003:
http://support.microsoft.com/lifecycle/search/default.aspx?sor
t=PN&alpha=windows+server+2003&Filter=FilterNO
(3)
Windows 2003 R2:
http://support.microsoft.com/lifecycle/search/default.aspx?sor
t=PN&alpha=windows+server+2003+R2&Filter=FilterNO
Note: Currently there is no support for Windows Server 2012 and SQL 2012.
VMWare Platform Support
Arc Server is not supported in Remote Desktop (RDP) and Terminal Services (TS)
environments as these applications can cause problems with the required Wave Driver
operation.
Arc does offer support for VMWare virtual server environments. Arc Pro is only supported in
a live environment on VMWare EXSX and ESXi version 4.0, 4.1, 5.0 and 5.1 only.
Arc Pro is not supported in a live environment on HyperV or any other virtual based
operating system.
Deploying Arc Pro in a VMWare environment
System requirements
Operating System
environment
32bit
64bit
Type of CUCM
deployment
Recommended VMWare
environment specification
Hard disk (GB)
Memory
(GB)
Processor
cores
Single cluster
100
4
2
Multiple clusters*
100
4
2
Single cluster
100
4
2
Multiple clusters
100
8
2
*we recommend that multiple cluster solutions are deployed in 64bit environments
Moving a VMWare Environment and licence consideration
If you are working in a VMWare environment and have a requirement to move the
environment you will need to take into consideration the following rules to retain the UUID
user and Arc License.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayK
C&externalId=1541
Compatability and Performance with Arc Professional Version 6.0.0
4
Citrix Support
Arc Pro 6.0.0 is compatible with the following Citrix products.
XenApp 6.5
Fundamentals
Advanced Enterprise
Platinum




VDI
Enterprise
Platinum



XenDesktop* 5.6
*Testing was performed using Windows 7 64bit operating system in 'Dedicated' and 'Pooled random'
configurations
Important Information
The following observations were made during testing:
•
XenDesktop 5.6 (Pooled Random) was fully functional provided that the user had
Administrative rights.
Except that user setting changes and logging is lost when the user logs off from
XenDesktop
•
XenApp 6.5 was fully functional provided that Windows User Authentication Control
(UAC) was switched off.
Except with logging issues. Logging settings point to a physical location that is
shared amongst XenApp session users and thus they are overwritten if more than
one XenApp session is run simultaneously. This can be prevented by modifying the
logging location to a session independent location. User setting changes ARE
remembered for different each XenApp session.
Compatability and Performance with Arc Professional Version 6.0.0
5
Cisco Unified Communications Manager Compatibility
Arc Pro version 6.0.0 is compatible with the following Cisco Unified Communication
Managers (CUCM) and the respective Cisco TAPI TSP.
A full compatibility matrix can be found on the website (see page 1 for web links)
CUCM
7.1.5
8.0.0 *
8.0.2 *
8.0.3
8.5.1
8.6.1
8.6.2 **
9.0.x
9.1.x
Cisco
TAPI TSP
7.1
(5.2)
8.0
(1.6)
8.0
(1.6)
8.0
(3.5)
8.5
(1.1)
8.6
(1.3)
8.6 (2.2)
9.0
(1.1)
9.1
(1.4)
* See the section Cisco Unified Call Manager 8.x Compatibility.
** See the section Known issue in Cisco Unified Communications Manager 8.6.2.
Known issue in CUCM 8.6.2
(Updated January 20th, 2012)
Installers, engineers and customers are advised that an issue exists in version 8.6.2 of Cisco
Unified Communications Manager whereby CTI ports fail to register in certain
circumstances, causing significant problems with call control within the Arc Pro server.
This issue is observed on CUCM build version 8.6.2.20000-2 with TSP version 8.6(2.2) on
Windows 2008 Service Pack 2 32 bit.
The Cisco ticket reference is CSCtw79059.
Since this is solely a CUCM issue and is outside of Arc Solutions domain, you are advised to
contact Cisco for updated status on this issue.
SQL Server Support
SQL
2005 32bit
2008 32bit
2008 64bit
Windows 2003 R1



Windows 2003 R2



(1)(3)
(1)(3)
(1)(3)
(1)(3)
(1)(3)
(1)(3)
Server 2008 R1
Server 2008 R2
32bit/64bit
32bit/64bit






Note: Currently there is no support for Windows Server 2012 and SQL 2012.
Important Information
Microsoft SQL 64bit Support
Support for Microsoft SQL Server (2005 and 2008) 64bit is provided in Arc Pro 6.0. x on
CUCM 8.6.2 and above.
However, in older versions of Arc Pro (5.1.4 and below) support for Microsoft SQL Server
(2005 and 2008) is offered for 32bit versions of the operating system only.
Compatability and Performance with Arc Professional Version 6.0.0
6
Technologies Matrix
The following table outlines the compatibility between Arc Pro version 6.0.0 and other
vendor software.
Technology
Arc Enterprise
(Pro)
Microsoft Presence Integration (Presence)
Live Communication Server 2005 (LCS)
Microsoft Office Communicator 2007 (OCS)
Microsoft Office Communicator 2007 R2 (OCS)
Microsoft Office Communicator 2010 (OCS)
*
*
* *
* *
1
1
1 5
1 5
Cisco Unified Presence Server Integration (Presence)
7.x (7.1.x)
8.0 (8.0.?)
8.5 (8.5.x)
8.6 (8.6.x)
9.0 (9.0.x)
9.1 (9.1.x)

*
*
*
*
*
4
4
4
4
4
Accessibility
JAWS v11.x
JAWS v12.x


Mail Integration (Calendar)
Microsoft Exchange\Outlook XP (2002)
Microsoft Exchange\Outlook 2003
Compatability and Performance with Arc Professional Version 6.0.0
*
*
2
2
7
Microsoft Exchange\Outlook 2007
Microsoft Exchange\Outlook 2010
*
*
2
2
Mail Integration (Send Email)
Microsoft Exchange\Outlook XP (2002)
Microsoft Exchange\Outlook 2003
Microsoft Exchange\Outlook 2007
Microsoft Exchange\Outlook 2010




Directory Integration
Microsoft Active Directory (LDAP)
Netscape\iPlanet\SunOne (LDAP)
DC Directory (LDAP)
Call Manager User Directory (XML\SOAP)
Microsoft Active Directory Application Mode (ADAM)
Novell eDirectory (LDAP) v8.8
Estos Metadirectory v2/3
*

3

*
*


3
3
Call Recording Integration
Witness Server v7.8.3
CallRex 4.3


Short Message Service (SMS Send)
HTTP

Email

Compatability and Performance with Arc Professional Version 6.0.0
8
Native\ActiveX
Modem


*1 Presence information is collected via a direct connection between the attendant console application and
the Microsoft Office Communicator (MOC) client.
*2 Calendar information is collected via a direct connection between the attendant console application and
Microsoft Office. Redemption is used to work around the Outlook security dialog introduced in Service
Pack 2 of Office 2002/2003/2007/2010.
*3 Support for Directories running on supported Server Operating System/CUCM platforms.
*4 Support for SIP connectivity only.
*5 Presence information is collected via a direct connection between the attendant console application and
the Arc OCS Presence Server.
Compatability and Performance with Arc Professional Version 6.0.0
9
System Requirements
Console Server and Client (Console) Computer
The following specification is given as a guide only. It is recommended as a base
specification to allow Arc Pro to run at its optimum. You should try to supply this
specification of machine or better.
Arc Pro Server
PC Server – Arc Pro Connect is a client server application. The server side will need to run
on a dedicated PC Server. No other applications must run on this server.
The tables in this section detail the minimum specification required by the Arc Pro Server
application.
Applies to
Arc Pro
Connect
Server
PC Specification
For deployments with a high call load or large directory sync source,
then the following hardware is required (or better).
For setups including Multi Cluster, then the following hardware is also
recommended:
2.40 GHz Core 2 Duo each (2 Processors)
8.0 GB RAM
64 bit Windows 2008 R2 Server
For systems not regarded as having to handle high call throughput
then the following is required (or better):
2.40 GHz Core 2 Duo
4.0 GB RAM
32 bit Windows 2008 Server
For both versions:
100 GB Hard Drive or better
CD-ROM/DVD-Rom
100mbps Network Card
.Net Framework v3.5
SQL Server Standard or Enterprise 2008, or SQL 2008 Express for smaller
installations where resilience is not required.*
Microsoft Excel for Directory Exporting.
Microsoft Office Communication Server 2007 R2, Core Components for
running Arc OCS Server. (Note: Microsoft OCS R1 is not supported).
If an Off-box (remote) SQL server is used within your configuration then
it must have .Net Framework v3.5 installed.
Please consult your Microsoft representative if you are looking to
license managed or hosted solutions
Compatability and Performance with Arc Professional Version 6.0.0
10
SQL Server
2005/2008
Licensing
There are two methods of licensing:
“Per Processor” license or “SQL Server & CALS” license
It is at the Partners discretion as to which SQL license option is selected.
The URL below details the SQL Server licensing requirements.
http://www.microsoft.com/sql/howtobuy/default.mspx
CAL requirements:
SQL
Scalability
•
The Arc Server uses 2 SQL CALS, and each Arc application client
uses 1 SQL CAL per instance.
•
If in any doubt when designing your Arc installation, simply
ensure you have a SQL processor license in place.
•
Please consult your Microsoft representative if you are looking
to license managed or hosted solutions
The performance limitation that SQL Server Express possesses is that it
can access only a single CPU and 1 GB of RAM with a maximum
database size of 4Gb.
In sites where one or more of the following are expected;•
A large number of operators - more than 10,
•
A high call volume - greater than 500 calls per operator per
day,
•
A Large Directory - greater than 10,000 contacts;
The use of SQL Server Standard or Enterprise should be strongly
considered. Where a system outgrows the SQL Express
deployment, or issues are experienced related to the use of SQL
Express, the Standard or Enterprise versions of SQL can be used
to upgrade the existing implementation with minimal effort.
Please consult your Microsoft representative if you are looking
to license managed or hosted solutions
The Server should be connected to the network via the TCP/IP protocol.
The Arc Server will require the appropriate Operating System Licenses.
The Arc Server is not supported on a domain controller.
With Windows 2008 Server, the Admin, CT Server Manager & LDAP Server Manager must
be run as an Administrator to enable them to read and write to the configuration
files/registry.
If the report functionality is required then it is advisable to disable the User Account
Control when operating the Arc Pro Connect Server is running on Windows 2008 and
Windows 7.
Anti-Virus Compatibility
There are many different Anti-Virus products that are supported on an Arc Pro system
server. Typically, the most commonly used products are McAfee VirusScan and Norton
AntiVirus.
Compatability and Performance with Arc Professional Version 6.0.0
11
Both of these products are supported, although any AntiVirus program is supported on an
Arc Pro Server, as long as it is configured as below:-
Exclusions
It is important that the AntiVirus product supports “Exclusions”. This is the ability for the user
to specify specific files and/or folders that will NOT be scanned by the AntiVirus program.
The following exclusions should be set when using AntiVirus on an Arc Pro Server
File Location
Use
\\ArcData
This folder is where the System Configuration
Databases are located
Error! Hyperlink reference not valid.
This is where all the system log files are stored.
\\Temp\Cisco\Trace
This is where the Cisco TSP Trace files are
located
N.B. The “File Locations” and “File Names” may be changed by your System Administrator.
The files in the above table are constantly being written to and updated during standard
operation of the Arc Pro system.
Due to this, these files are permanently being accessed – an Anti-Virus “Scan on access”
policy for these files will mean that the files are constantly being scanned for Viruses. This
will in turn slow down the operation of the Server. Therefore, excluding these files from
being continuously scanned will allow the Server to function as expected.
Cisco UCS Servers
Arc Pro supports both UCS-B and UCS-C Servers with the following caveats taken into
consideration.
Cisco UCS-B Servers
Cisco UCS-B servers are industry standard platforms featuring a physical chassis with the
ability to insert a number of hardware blades, onto which a server operating system (OS)
can be deployed. UCS-B features the ability for those server blades to contain a number
of Cisco application servers, including Cisco Unified Communications Manager (CUCM)
and Unity Messaging. The remaining blades are capable of running standard operating
systems and as such it is possible to install third party applications on them. The benefit of a
chassis based system is that the blade/server components are connected across a
backbone that facilitates high speed and error free communication between each
blade.
Arc Solutions offers support in Arc Pro version 5.1.4* and above for Cisco UCS-B servers with
the following caveats:• Support is provided for VMWare ESXi and ESX 4.x and 5.x with VSphere and
VMotion.
• If Arc is to be deployed on its own blade within the UCS-B, the VMWare image
deployed must meet the minimum processor and memory specification as defined
by Arc Solutions.
• If Arc Pro Server is installed on the same blade as (is co-resident with) another Cisco
application, including Cisco Unified Communications Manager and Unity, the Arc
Pro VMWare image must conform to the specifications defined both by Arc
Solutions (described in VMWare Platform Support, page 4) and by Cisco Systems, as
Compatability and Performance with Arc Professional Version 6.0.0
12
defined at Cisco's Server Virtualization Guidelines at
http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Sizing_Guideli
nes.
Cisco UCS-C servers
Cisco UCS-C servers are single processor, multi-core, non-chassis machines that are
increasingly used to run Cisco Unified Communications Manager. They are available in a
number of sizes depending on their application.
Arc Solutions offers support in Arc Pro version 5.1.4* and above for Cisco UCS-C servers with
the following caveats:•
•
•
Support for Arc Pro on UCS-C servers is allowed by Cisco with CUCM version 9.x and
above only, as defined by Cisco Systems.
Arc Pro is supported on UCS-C servers provided it resides on a separate VMWare
image to CUCM
The VMWare image deployed must meet the minimum processor and memory
specification as defined by Arc Solutions. See the Compatibility and Performance
Guide for your release of software.
*Most recent in-house testing was performed on Arc 6.0 software which is due for public release in December
2012. Because of the testing performed, users experiencing issues with Arc 5.1.4 on a UCS deployment from
January 2013 may be asked to upgrade their software to 6.0.0 if Arc support team issue diagnosis process
dictates it.
Arc Pro Client
The tables in this section detail the minimum specification required by the Arc Pro Client
applications.
PC Specification
Applies To the
following
applications
Pentium 4 CPU or better
2 GB RAM
10GB available Hard Drive space (this is not required by the app, but
should be unused for healthy running of the system)
CD-ROM/DVD-ROM
100mbps Network Card
Supervisor
Connected to Network via TCP/IP
1280x1024 or better display card (higher resolution recommended for
best results)
Windows 7 recommended
Note:
(1) Windows 7 32 bit and 64bit clients are supported
(2) If the report functionality is required then it is advisable to disable the
User Account Control when operating Supervisor on Windows 2008,
Vista and Windows 7
Console
Pentium 4 CPU or better (Core Duo recommended)
Compatability and Performance with Arc Professional Version 6.0.0
13
Operator
Arc
Wallboard
2GB RAM
10GB available Hard Drive space (this is not required by the app, but
should be unused for healthy running of the system)
CD-ROM/DVD-ROM
100mbps Network Card
Connected to Network via TCP/IP
1280x1024 display card or better (for Arc Pro attendant console we
recommend that the resolution is at least 1600 x 1200)
19” widescreen monitor highly recommended for Arc Pro console
Windows 7 recommended
USB 1.0/2.0 Port for Arc Console Keyboard (if purchased)
Sound card and speakers are required for the Console Operator and
Arc Wallboard.
Note
(1) The console Calendar integration requires a Microsoft Exchange
Server 2007 or better. For users’ calendars to be available to Arc Pro,
users’ Calendars must be set as public folders.
Pentium 4 CPU or better (Core Duo recommended)
2GB RAM
10GB available Hard Drive space (this is not required by the app, but
should be unused for healthy running of the system)
CD-ROM/DVD-ROM
Arc Agent
Network Card
Connected to Network via TCP/IP
1280x1024 display card or better (higher resolution recommended for
best results)
Windows 7 recommended
* The Arc Pro client software is supported in 32 bit and 64 bit (running under WOW64
emulation mode) environments.
Compatability and Performance with Arc Professional Version 6.0.0
14
Supported Handsets
The following phone types are supported as attendant console handsets, or as End Points
(display line state and can receive transferred calls).
Note:
•
•
•
Shared lines (multiple lines with the same number) are not supported for
attendant console handsets.
Third-party SIP phones cannot be supported as attendant console handsets
or for line state.
Arc Pro does not support logging on any device that has a duplicate DN, or
that uses Extension Mobility.
= supported, = unsupported.
Model
Image
SCCP
SIP
Console
SIP
SCCP
End
point
3905




[1]
3911





3951





6901





6911





6921





6941





6945





Compatability and Performance with Arc Professional Version 6.0.0
15
6961





7905





7906





7910





7911





7912





7920





7925





7925G-EX





7926





7931

[3] [3] [3] 
7935


Compatability and Performance with Arc Professional Version 6.0.0



16
7936





7937





7940




[2]
7941





7941G-GE





7942





7945





7960




[2]
7961





7961G-GE





7962





7965





7970





7971





Compatability and Performance with Arc Professional Version 6.0.0
17
7975





7985





8961


[3] 

9951


[3] 

9971


[3] 

7925G





7937G





7942-G





7945G





7965G





8941





Compatability and Performance with Arc Professional Version 6.0.0
18
8945





IP
Communicator





[1]. No BLF, but can receive transfer.
[2]. Supported for SCCP only.
[3]. Support with disable rollover.
Compatability and Performance with Arc Professional Version 6.0.0
19
Performance and utilisation
This section is an extract from Arc Pro Design Guide June 2011
General bandwidth recommendations
Location-based Call Admission Control may be implemented to control the bandwidth
usage across the WAN. A maximum amount of bandwidth may be configured for calls to
and from each remote location.
When an Arc controlled CTI Route Point or CTI Port is created, the location should be set to
None. This will effectively ensure that no bandwidth limits will apply to that device,
however
Locations MAY be implemented which will account for bandwidth ACCORDING to Region
settings, to define the codec used between two endpoints.
Codec Considerations
Call type
Bandwidth
Calls routed across a LAN typically use the G711 codec
64 Kbps
Calls routed across the WAN may use the G729 codec
8 Kbps
If different compression types are to be used to reduce the amount of bandwidth needed
across the WAN, then a transcoder will be needed (See Codec Considerations - above)
In addition, further bandwidth is used by IP communications between the Arc Server and
the Console Attendant as described in the following sections.
Network Latency Limitations
Arc Pro can operator over WAN (Wide Area Networks), however there are requirements as
to the maximum latency that the system can operate under before the user experience
begins to deteriorate.
Between the Arc Pro Server and the Cisco Unified Call Manager, where the TAPI
communication takes place, the maximum latency permitted is defined by Cisco. This
value can be found in Cisco’s TAPI documentation at
http://developer.cisco.com/web/tapi/docs.
Between the Arc Pro Server and any Arc Pro Clients, the maximum latency permitted for
each direction is 150ms (300ms round trip).
In cases where the SQL Server that Arc Pro is using is not located on the Arc Pro Server, the
maximum latency permitted for each direction is 150ms (300ms round trip). This applies to
the Arc Pro Server and any clients connections to the SQL Server.
Attendant Console
The following log-in tests used a directory of 250 contacts. The console by default pulls
back a maximum of a 1000 contacts with any one SQL search therefore the recorded
values represent the maximum log-in bandwidth required regardless of directory size.
Activity as measured from the Client
Client login (Operator – direct
access mode)
Download
Bandwidth (KB)
Upload Bandwidth
(KB)
1,092
12.7
843.70
11.65
Compatability and Performance with Arc Professional Version 6.0.0
20
With 1000 Contacts
+193%
+85%
Client login (Operator – direct
access mode)
333.28
11.65
2,134
8.4
NA
NA
NA
NA
With 100 Contacts
Client login (Operator – memory
mode)
With 1000 Contacts
Directory and Busy Lamp
Every search made of the Contact Directory will return a number of matches within the
SQL database. The bandwidth requirements will depend on the number of contacts being
returned and the amount of data within each contact.
Activity as measured from the Client
20 contact SQL search using
attendant console
20 contact SQL search using
attendant console with Scalable
Busy Lamp Enabled (New
subscriptions)
20 contact SQL search using
attendant console with Scalable
Busy Lamp Enabled (Cached
subscriptions)
Download
Bandwidth (KB)
Upload Bandwidth
(KB)
8.7
4.5
19.51
8.81
+13.10%
+22.53%
33.2
8.3
17.88
9.98
+69.90%
-20.96%
13.42
7.21
+42.61%
+28.98%
Presence integration
Activity as measured from the Client
CUPS searching ‘get’ for typical
directory view of 20 contacts (New
subscriptions)
Download
Bandwidth (KB)
Upload Bandwidth
(KB)
8.9
4.5
70.74
32.96
CUPS searching ‘get’ for typical
directory view of 20 contacts
(Cached subscriptions)
18.57
7.18
93.97
54.89
OCS presence ‘get’ for typical
directory view of 20 contacts with a
short note (New subscriptions)
24.58
8.42
22.77
8.07
27.83
8.04
24.81
12.47
OCS presence ‘get’ for typical
directory view of 20 contacts with a
Compatability and Performance with Arc Professional Version 6.0.0
21
short note (Cached subscriptions)
Calendar (using Outlook interface)
‘get’ for typical directory view of 20
contacts
NA (Data obtained
from outlook
session)
NA (Data obtained
from outlook
session)
Server
Database Synchronisation with CUCM (Arc 5.1.1 onwards)
The other major requirement for Arc attendant console outside of the call handling
requirements is the initial synchronizing of the Contacts DB. This is undertaken via an LDAP
synch with CUCM. Again the amount of bandwidth required depends on the amount of
contacts and the amount of data within each contact.
Activity as measured from the Arc
Server
Initial synchronisation of the Arc
directory contacts database using
LDAP synchronisation with a CUCM
source of 50 basic contacts (3x
fields).
Initial synchronisation of the Arc
directory contacts database using
LDAP synchronisation with a AD
source of 50 basic contacts (8x
fields).
Initial synchronisation of the Arc
directory contacts database using
LDAP synchronisation with a AD
source of 20,000 basic contacts (8x
fields).
Download
Bandwidth (KB)
Upload Bandwidth
(KB)
376.4
461
1,043.05
185.08
+302.75%
-52.02%
103.2
135
109.50
118.23
-71.77%
-80.09%
33,596
49,918
31,570
104,950
-4.65%
-5.61%
Server Resilience (Replication with SQL 2008 Enterprise)
Activity as measured from the
Subscriber
Initial Full Sync based on the
following :50 Agents
Download
Bandwidth (KB)
Upload Bandwidth
(KB)
7,144
3,494
356.44
108.38
-86.77%
+13.77%
(Each agent has 1 skill assigned)
50 Operators
Compatability and Performance with Arc Professional Version 6.0.0
22
(Each operator has 1 queue
assigned)
10 Supervisors
1 Wallboard user
1 Community
2 Permission Groups
25 Agent Skills
25 Agent Queues
10 Console Queues
Directory containing 1000 contacts
Typical bandwidth per individual
change in this example adding a
new console queue.
214
9.5
193
7.4
-10%
-22%
LDAP or equivalent integration
Activity as measured from the Arc
Server
Initial connection
Maintaining (contact update in AD
source in this example a phone
number edit)
Download
Bandwidth (KB)
Upload Bandwidth
(KB)
20
10
22.43
7.86
+91.05%
+38.42%
4.3
7.4
4.10
2.53
+27.32%
-57.55%
Voice Connect
Activity as measured from the Arc
Voice Server
Service start-up with all waves
locally cached
Server start-up with all waves locally
cached
Download
Bandwidth (KB)
Upload Bandwidth
(KB)
13
3.6
0.86
0.05
-93.47%
-98.70%
2,916
39
41.60
0.09
-98.47%
-99.77%
Streaming of WAV files per queue/call, based on our standard messages:Compatability and Performance with Arc Professional Version 6.0.0
23
Voice Connect activity (playing of
prompts)
Default voice messages (all of the
canned voice messages produce
very much the same bandwidth
results, the recorded result is for
“Your call will be answered shortly,
thank you for holding”)
Download
Bandwidth (KB)
Upload Bandwidth
(KB)
25
38
N/A
N/A
N/A
N/A
Supervisor
Activity as measured from the Client
Client login
System Monitor, per client, per
broadcast
Reporting
Online updates, per change
Download
Bandwidth (KB)
Upload Bandwidth
(KB)
340.7
6.6
345.04
4.39
-11.57%
-57.66%
35
0
35.05
0
0%
0%
Typically <100 per
report dependent
to the type of the
report and the
amount of data it
contains
Typically <5
<1
Typically <5
Wallboard (tests based on the 1.4.2 example configuration)
Activity as measured from the Client
Client login
Updates -per broadcast per
Wallboard
Download
Bandwidth (KB)
Upload Bandwidth
(KB)
301.7
0.33
232.66
0.39
+1.51%
0%
35
0
35.05
0
0%
0%
Compatability and Performance with Arc Professional Version 6.0.0
24
© 2003 - 2014 Arc Solutions (International) Ltd. All rights reserved
No part of this documentation may be reproduced in any form or by any means or used to make any derivative work (such
as translation, transformation, or adaptation) without permission from Arc Solutions (International) Limited.
Arc Solutions (International) Limited reserves the right to revise this documentation and to make changes to its content from
time to time without obligation on the part of Arc Solutions (International) Limited to provide notification of such revision or
change.
Cisco is a registered trademark of Cisco Systems, inc.
Unless otherwise indicated, Arc Solutions (International) Limited registered trademarks are registered in the United Kingdom
and may or may not be registered in other countries.
All trademarks acknowledged
Europe
Americas
Asia Pacific
Arc Solutions
(International) Ltd.
Arc Solutions
(International) Inc.
Arc Solutions
(International) Ltd.
Innovation House
Pincents Lane,
Reading, Berkshire.
RG31 4UH
Research Triangle Park
4819 Emperor Blvd
Durham
North Carolina 27703
2 Marks Street
Naremburn
NSW 2065
Australia
T: +44(0) 118 943 9200
f: +44(0) 118 943 9201
T: +1 877 956 0272
f: +1 919 313 4794
T: +61 409 692 480
f:+61 (0)2 9437 4595
e: info@arcsolutions.com
e: inquiries@arcsolutions.com
e: apac-info@arcsolutions.com
Support
+44(0) 118 943 9205
Support
+1 877 956 0272
Support
+61 1300 797 724
+44(0) 118 943 9212
Compatability and Performance with Arc Professional Version 6.0.0
25
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising