Resource requirements

Hint

Our CSM-Webtools also contain a tool for automatically calculating the required system resources.

The XPhone Connect Server can be installed in three different operation modes.

Depending on the operating mode, different requirements are made on the respective hardware. These can be found in the following categories:

• XPhone Connect as UC solution for CTI, Softphone, Presence, TeamDesk, AnyDevice, UM, Chat, Meetings, Federation, Analytics, Directory, etc….

• XPhone Connect as a directory service for Skype for Business or other LDAP-enabled services

• XPhone Connect as directory service with the additional use of fax & voicemail

• XPhone Connect as web service for operating the web server in the DMZ (e.g. for XPhone Connect Mobile or Analytics)

Operating mode: UC solution

If the XPhone Connect Server is operated in a single server deployment (installation and operation on only one Windows server), the basic system requirements apply. If additional services are to be used, these requirements must be added to the basic requirements (e.g. when using softphone, meetings, etc…).

Quantity analysis and assumptions

The following load profile is assumed for the above volume considerations and recommendations:

XPhone Connect Server

• 20 calls per day and user

• 10 chat sessions per user per day with 10 messages each

• (1:1 chat, message length < 100 characters)

• 1 telephone system with one dialing parameter without special number conversions

• (Approximately 200 MB of additional memory is required for each PBX)

• 90 days call journal storage time

• 90 days storage time (persistence) for chats in the journal

• 5% Mobile usage: 5% of XPhone users use the mobile app at the same time.

XPhone Connect Directory

• 1 ODBC data source (256 MB RAM required per additional data source)

• 1 million records

• Maximum number of searches per hour and employee in the directory: 8

Team-Panel

• Users using team panel: 20%

• Server-side groups per user: 5

• Contacts per group on average: 50

• Users who have the Team panel open and visible at the same time: 25%

• Number of central groups: 20

• Entries (user, configuration group, location) per central group: 20

Federation

• Per user 40 external contacts

• 10 chat sessions per user per day with 10 messages each (1:1 chat, message length < 100 characters)

Basic requirements for the system

XPhone Connect Server and SQL Server on one machine

This recommendation assumes a Microsoft Server operating system.

User [1]	RAM [2]	HDD capacity [3]	CPU cores [4]
< 25	6 GB	8 GB	4 (e.g. Intel i5)
< 100	8 GB	12 GB	4 (e.g. Intel i7)
< 250	10 GB	18 GB	4 (e.g. Intel i7)
< 500	12 GB	28 GB	4 (e.g. Intel Xeon E5)
< 1000	16 GB	60 GB	6 (e.g. Intel Xeon E5)
< 2000	21 GB	100 GB	6 (e.g. Intel Xeon E7)
< 3000	22 GB	150 GB	8 (e.g. Intel Xeon E7)
< 4000	30 GB	200 GB	8 (e.g. Intel Xeon E7)
< 5000	34 GB	250 GB	10 (e.g. Intel Xeon E7)

[1]

From 500 users, the use of a SQL Standard/Enterprise Edition Server is required.

[2]

Working memory for the entire system. XPhone is the only server application besides Microsoft SQL Express.

[3]

Free hard disk space for XPhone Connect. If the internal message storage (fax, voice mail, chat, journal) is used intensively, the capacity may have to be increased.

[4]

Ein Core im Sinne der Systemvoraussetzungen entspricht der Leistungsfähigkeit einer modernen Server-CPU (vglb. Intel Xeon Prozessor E7 V4). In virtualisierten Umgebungen muss sichergestellt sein, dass diese Leistung dem Gastbetriebssystem jederzeit zur Verfügung steht (dedizierter Core).

XPhone Connect Server and SQL Server on different machines

For more than 500 users, the use of an SQL Server (Standard/Enterprise Edition) is required. This is usually installed on the same machine as XPhone Connect and offers the best possible performance. The use of XPhone Connect and SQL Server (Standard/Enterprise Edition) on different machines is also supported. This enables the use of an already existing SQL Server. The following system requirements apply for this:

This recommendation assumes Microsoft Server operating systems for XPhone and SQL Server respectively.

	XPhone Connect Server			External SQL server
User [5]	RAM [6]	HDD [7]	Cores [8]	RAM [6]	HDD [7]	Cores [8]
< 25	2 GB	5 GB	2 (e.g. Intel i5)	4 GB	8 GB	2
< 100	4 GB	5 GB	2 (e.g. Intel i7)	4 GB	10 GB	2
< 250	6 GB	5 GB	2 (e.g. Intel i7)	5 GB	14 GB	2
< 500	8 GB	6 GB	3 (e.g. Intel Xeon E5)	5 GB	25 GB	2
< 1000	8 GB	11 GB	6 (e.g. Intel Xeon E5)	8 GB	45 GB	3
< 2000	10 GB	21 GB	6 (e.g. Intel Xeon E7)	11 GB	85 GB	4
< 3000	14 GB	30 GB	8 (e.g. Intel Xeon E7)	12 GB	120 GB	4
< 4000	15 GB	40 GB	8 (e.g. Intel Xeon E7)	16 GB	160 GB	5
< 5000	16 GB	50 GB	8 (e.g. Intel Xeon E7)	20 GB	200 GB	6

[5]

From 500 users, the use of a SQL Standard/Enterprise Edition Server is required.

[6] (1,2)

Working memory for the entire system. XPhone is the only server application besides Microsoft SQL Express.

[7] (1,2)

Free hard disk space for XPhone Connect. If the internal message storage (fax, voice mail, chat, journal) is used intensively, the capacity may have to be increased.

[8] (1,2)

A core in terms of system requirements corresponds to the performance of a modern server CPU (cf. Intel Xeon processor E7 V4). In virtualized environments, it must be ensured that this performance is available to the guest operating system at all times (dedicated core).

Additional performance requirements

Additional system requirements for XPhone Connect Server, in addition to the basic requirements.

CTI gateways

CTI gateways	RAM
+ 5	+ 1 GB
+ 10	+ 2 GB
+ 25	+ 5 GB

UM IP channels

Additional system requirements for XPhone Connect Server, in addition to the basic requirements.

Channels	Resources
+ 2-8	+ 1 GB RAM
+ 9-32	+ 2 GB RAM + 1 CPU Core
+ 64	+ 3 GB RAM + 1 CPU Core
+ 128	+ 4 GB RAM + 2 CPU Cores

TeamDesk users

Additional system requirements for XPhone Connect Server, in addition to the basic requirements.

TeamDesk User	Resources
Up to 10	-
11 - 499	+ 1 GB RAM + 1 CPU Core
500 - 1000	+ 2 GB RAM + 2 CPU Cores

Softphone calls

Additional system requirements for the XPhone Connect Server, in addition to the basic requirements - if the XPhone CallController has not been outsourced, but is operated as a service on the XPhone Server (single server deployment). A softphone call is defined as a softphone desktop call and a softphone mobile call.

Hint

The maximum expansion level of the softphone should always be calculated per call, since the transcoding requires the most processing power. It should be noted that the following table deals with simultaneous calls and that there is a serious difference between internal and external calls. For the calculation, it has to be taken into account that the number of cores for internal and external calls have to be added.

Internal calls

Calls	Resources
750	+ 1 GB RAM + 1 CPU Core
1500	+ 2 GB RAM + 3 CPU Cores
3000	+ 2 GB RAM + 6 CPU Cores

External calls

Calls	Resources
20	+ 1 CPU Core
40	+ 2 CPU Cores
60	+ 3 CPU Cores
80	+ 4 CPU Cores
100	+ 5 CPU Cores

Using the Mobile App

Additional system requirements for XPhone Connect Server, in addition to the basic requirements.

Active mobile app users	Resources
1-100	+ 8 GB RAM + 2 CPU Cores + 1 GB HDD
101-250	+ 16 GB RAM + 3 CPU Cores + 1 GB HDD

Hint

If the number of users exceeds 250 (maximum 2,000 users), the web applications must be outsourced to another system (see Web-Anwendungen auf separatem Rechner). When using Softphone Mobile in the XPhone Connect app, it is also recommended to outsource the XPhone CallController to the DMZ (see XPhone Call Controller).

Use of meetings (audio conference)

Additional system requirements for XPhone Connect Server, in addition to the basic requirements.

Active Meeting participants	Resources
1-100	+ 2 GB RAM + 1 CPU Cores
101-200	+ 4 GB RAM + 2 CPU Cores
201-250	+ 6 GB RAM + 3 CPU Cores

Resources of the XPhone Connect Server host (CPU, memory) are required for each meeting participant. It does not matter whether all participants are in one meeting or distributed over several meetings running in parallel. One additional CPU core must be planned for every 100 meeting participants.

XPhone Connect Server resources are shared by all XPhone services. A CPU/memory utilization above 80% can cause impairments and quality losses of the XCC voice transmission (conference, AnyDevice, softphone). By allocating additional CPU cores or memory for the XPhone Connect server, interference can be reduced or additional participants can be supported.

Microsoft Windows 10/11 Pro 64 Bit

When using XPhone Connect Server (CTI, UM), under Windows 10 Pro 64 Bit, the following reduced system requirements apply.

Max. User [9]	RAM	HDD- capacity [10]	CPU cores n. virtual	CPU cores virtual
20	4 GB	20 GB	2 (e.g. Intel I3)	2

[9]

The upper limit of 20 users is given by the Windows 10/11 - license agreement. Use with CTI and UM.

[10]

Recommendation for typical use. When using the internal message memory intensively (fax / voicemails), the capacity must be increased if necessary.

Attention

Using Windows 10 / 11 excludes the use of XPhone Call Controller.

Hint

These are general recommendations. The actual requirement depends on many factors. Some of the basic requirements will be explained in the following sections. Some other parameters are difficult to quantify (e.g. hard disk performance, network performance, telephony behavior, etc.), so the recommendations may have to be adjusted when used in practice.Please note the restrictions in item Software.

Operating mode: Directory service

If XPhone Connect Server is used exclusively as a directory service/server, reduced system requirements apply (CPU, RAM, HDD). In a smaller installation (up to 100 users), XPhone Connect Directory is often installed on a machine with existing UC services. The specifications for RAM, HDD capacity and CPU cores therefore refer to the additional requirements on the machine for the operation of XPhone.

Hint

The maximum number of contacts depends on the Microsoft SQL Server used. Please read this chapter: Microsoft SQL Server.

Quantity analysis and assumptions

The following load profile is assumed for the above volume considerations and recommendations:

• Maximum number of searches per hour and employee in the directory: 8

• Use of the included SQL Express edition for the basic configuration up to about 500 users.

  However, this number serves only as a rough guide and varies with the size of the actual contacts or database type (see section: Microsoft SQL Server).

• Per user: 1 x personal Outlook folder with 50 contacts per user and 1 ODBC data source with 500,000 contacts.

• Use of client-side fax rendering (reduces the load on the XPhone server).

The RAM requirement is mainly determined by the number of connected data beacons. In the basic configuration for directory use, 1 GB RAM is required for XPhone Connect. For each additional connected data source, 256 MB are required.

The disk space requirement of SQL Server is mainly determined by database type and number of contacts. For Microsoft SQL Express edition, the maximum size of the index table is limited to 10 GB. For Microsoft SQL Standard/Enterprise edition, 1 GB of storage is required for 25,000 - 300,000 contacts (depending on the data type). For more information, please refer to the section: “Planning notesâ€.

The CPU requirement is mainly determined by the number of queries to the directory, e.g. user search queries or queries triggered by the UC client for caller identification. Based on typical user behavior, 1 CPU core per 1,000 users is recommended to process the requests sufficiently fast.

When running XPhone Connect Directory and SQL Server on different machines, there is an increased (shared) performance requirement in both machines, e.g. for additional data sources.

Basic configuration

Up to 100 users and 1 personal Outlook folder and 1 ODBC data source:

• 6 GB RAM

• 8 GB hard disk space

• 1 CPU core

Additional power requirements for data sources and contacts

• 2 GB RAM…

  • for each additional data source.

• 1 GB hard disk space and 250 MB RAM for SQL Standard/Enterprise…

  • 30000 contacts each in a Simple ODBC contact database without relations.

  • per 100000 CRM contact (ODBC with few relations).

  • 45000 Outlook private contacts each.

  • 25000 Outlook public contacts each.

  • per 50000 Active Directory contacts.

• 1 CPU core…

  • per additional 1,000 directory users (from 1,000 users).

Additional power requirements for UM IP channels (fax, voicemail, auto attendant)

• For 2 to 8 IP channels

  + 1 GB RAM and no additional CPU cores.

• For 9 to 32 IP channels

  + 2 GB RAM and 1 more CPU core.

• For 64 IP channels

  + 3 GB RAM and 1 more CPU core.

• For 128 IP channels

  + 4 GB RAM and 2 more CPU cores.

Hint

These are general recommendations. The actual demand depends on many factors. Some additional parameters are difficult to quantify (e.g. hard disk performance, network performance, telephony behavior, etc.), so the recommendations might have to be adjusted when used in practice.

The provision of sufficient CPU and RAM plays a crucial role for the smooth use of XPhone Connect. This is especially true when using the XPhone Call Controller (XCC), e.g. for real-time voice transmission in the conference service, AnyDevice, TeamDesk & Softphone.

Xphone installation Mode: Web service

The XPhone Server as Web Service operating mode enables the installation of web applications on a separate computer, e.g. in a DMZ (XPhone Connect Mobile, Web Meeting, Analytics, UM Settings). The hardware requirements for the server in the DMZ for this deployment scenario are described in this section. It should be noted that this should be seen in combination with the operating mode as a UC solution. Standalone operation as a web service is not possible.

Quantity analysis and assumptions

The following load profile is assumed for the above volume considerations and recommendations:

• XPhone Connect Mobile App:

  • 200 contacts per user

  • 100 journal entries per user

  • 5,000 actions/minute (such as load contact list, load journal list, send chat)

• Applications/minute:

  • 200 logins/minute of the mobile app (up to a maximum of 1,000 users)

  • 166 mobile app logins/minute (from 1,000 to 2,000 users)

Basic requirement for the system

• 4 CPU Cores [11]

• 8 GByte RAM

• 20 GByte hard disk space

[11]

A core in terms of system requirements corresponds to the performance of a modern server CPU (cf. Intel Xeon processor E7 V4). In virtualized environments, it must be ensured that this performance is available to the guest operating system at all times (dedicated core).

Additional performance requirements when using the Mobile APP

Additional system requirements, in addition to the basic requirements.

Active mobile apps [12]	RAM (in GB)	HDD (in GB)	additional Cores [13]
> 250	8 GB	1 GB	0
> 1000	24 GB	1 GB	2
> 1500	40 GB	1 GB	5
up to 2000	56 GB	1 GB	8

[12]

Anzahl der Mobile Apps (gesamt) die innerhalb der letzten 2 Stunden in Verwendung waren. Ab 250 Benutzer müssen Anpassungen in der Datenbankverbindung und am Web-Server (IIS) vorgenommen werden. Lesen Sie dazu die Hinweise in der Dokumentation.

[13]

A core in terms of system requirements corresponds to the performance of a modern server CPU (cf. Intel Xeon processor E7 V4). In virtualized environments, it must be ensured that this performance is available to the guest operating system at all times (dedicated core).

Bandwidth requirements for WebMeeting

When operating XPhone Connect Server and Web Application/IIS together on one computer or on separate servers.

Sessions	Participants per session	Total participants	Recommended upload (MBit/s)	Upload min. (MBit/s)
1	1	1	0,8 Mbit/s	0,3 Mbit/s
1	2	2	1,5 Mbit/s	0,5 Mbit/s
10	1	10	1,9 Mbit/s	0,6 Mbit/s
10	2	20	3,8 Mbit/s	1,3 Mbit/s
2	10	20	7,5 Mbit/s	2,5 Mbit/s
5	5	25	4,8 Mbit/s	1,6 Mbit/s
10	5	50	9,5 Mbit/s	3,2 Mbit/s
20	5	100	11,5 Mbit/s	6,2 Mbit/s

Hint

To support peak loads with multiple parallel sessions, a GBit network should be available internally:

• 1 GBit/s to XPhone Server

• 1 GBit/s between XPhone Server and DMZ

Resolution & Bandwidth

The number of participants depends on upload bandwidth, CPU & memory. If all requirements (see documentation) are met, we recommend a resolution of max. 1,920 x 1,080 pixels (Full-HD) for the presenter.

• PowerPoint presentation: 100kbps average bandwidth

• Document: 300kBit/s average bandwidth

Hint

These are general recommendations. The actual requirement depends on many factors. Some of the basic requirements will be explained in the following sections. Some other parameters are difficult to quantify (e.g. hard disk performance, network performance, telephony behavior, etc.), so the recommendations may have to be adjusted when used in practice.

Have you found an mistake on this page?

Please send us a hint about this error by mail to doku@c4b.de. Thank you very much!