XPhone Connect 7 System Requirements

The recommendations given here are based on average usage values. As system complexity increases, so do the system requirements.
Your ICT partner will be happy to advise you on the specific requirements for different systems or scenarios. C4B partners can find all information in the partner portal (XPhone Connect Sales Whitepaper).

 
 

Important Notes

The system requirements for the use of XPhone Connect depend on various factors: 

  • Operating mode (e.g. UC server, directory service & fax server or directory service only)
  • Frequency of use of the various UC services
  • Call volume
  • Number of users
  • Number of IP channels
  • Number of connected databases & contacts


Below you will find recommendations based on average usage values.

As system complexity increases, so do the system requirements. Your ICT partner will be happy to advise you on the detailed system requirements for different systems or scenarios, e.g.:

  • Use of an SQL Standard/Enterprise Server (on the same or another server)
  • Use of different databases and the number of their contacts
  • Effect on multiple PBX nodes, dialling parameters
  • Maximum number of simultaneous conference call participants
  • Use as a directory service with fax
  • Use as a directory service without fax/voicemail
  • DMZ: provision of Mobile/Analytics websites

C4B partners can find the detailed system requirements in the partner portal ("XPhone Connect Sales Whitepaper").

Notes on installation

Notes on installation

  • Current service packs of the operating system are required.
  • The XPhone Connect Server must NOT be installed on a terminal server.
  • Please install/upgrade the server components (XPhone Connect Server) first and then the client components (XPhone Connect Client).
  • The prerequisite for the installation is the .net framework 4.7. Please note that this may have to be installed on the respective PCs beforehand.
  • XPhone Connect Server version 6 is NOT compatible with XPhone Connect Client version 7.
  • If you want to use the latest features, the XPhone Connect Client in version 7 must be used.
  • XPhone Connect Client Version 6 can be operated (e.g. in migration scenarios) on XPhone Connect Server Version 7, but only with the feature set as described under Version 6.
  • If you also want to use the new functions with the XPhone Connect Mobile Client, it must be operated on an XPhone Connect Server Version 7.
  • For the Web-Meeting, the "Desktop Experience" feature is required, which must be installed manually under Windows Server 2008 R2.


Replaced components

  • inPcap was replaced by Npcap in version 7. Npcap offers extended possibilities for recording (tracing) network traffic with regard to VoIP.
  • Update of the Visual C++ redistributables (2017)
  • XCAPI is delivered in version 3.6.73

Expansion stages (Server | Conference | Softphone | Web-Meeting)

Server: Number of users

XPhone Connect as

Maximum number of XPhone users

UC server with Win 10 (SMB deployment)

20

UC server incl. CTI, presence & UM services

5.000

Directory Service with fax

10.000*

Directory Service without fax / voicemail

16.000


* The number of database entries and database types as well as the number of faxes per hour are decisive for the maximum expansion stage of the server.
Fax release over 5,000 users when using client-side rendering.

 
 

Softphone

The maximum expansion level of the softphone must always be calculated by the number of calls, as transcoding requires the most computing power. Please note that the following table shows simultaneous calls and that there is a considerable difference between internal and external calls. 

For the calculation, the number of cores for internal and external calls must be added.

 

XPhone Call Controller

Number of cores

(comparable Intel® Xeon® Prozessor E7 v4)

750 simultaneous internal calls

1

1.500 simultaneous internal calls

3

3.000 simultaneous internal calls

6

--------plus--------

----plus----

20 simultaneous external calls

1

40 simultaneous external calls

2

60 simultaneous external calls

3

80 simultaneous external calls

4

100 simultaneous external calls

5


 
 

Audio conference

  • Maximum number of participants in total: 250
  • Maximum number of participants in one conference: 25
  • Maximum number of conferences: 25
 
 

Web-Meeting

Maximum number of participants

The maximum number of participants depends on the available upload bandwidth, the CPU and the RAM.
If all requirements are met (see documentation for details), the maximum number of participants is calculated as follows.

  • Maximum number of participants in one Web-Meeting: 10
  • Maximum number of participants in total: 50


Resolution & Bandwidth

Recommended maximum resolution of the presenter: Full-HD 1080p (1920 x 1080 pixels). The following information refers to a Full-HD resolution of the presenter.

1080p content

Idle

Average

PPT
PowerPoint presentation: Page change every 60 seconds.

0 kBit/s

100 kBit/s

Document
Working together on a document (e.g. Word)

0 kBit/s

300 kBit/s


The prerequisite for screen sharing in Web-Meetings is the Windows Desktop Display feature. In Windows Server versions 2012/2012 R2/2016, this feature is automatically enabled when the installation wizard is run. On Windows Server 2008 R2, the feature must be added manually using the Windows Server Manager. 

Server: Hardware

Users1

Memory RAM (GB)2

Hard disk drive capacity (GB)3

CPU cores4

<25

6 GB

200 GB

2

<100

8 GB

250 GB

2

<250

10 GB

350 GB

2

<500

12 GB

500 GB

4

<1.000

16 GB

1.000 GB

4

<2.000

21 GB

2.000 GB

6

<3.000

26 GB

3.000 GB

6

<4.000

31 GB

4.000 GB

8

<5.000

36 GB

5.000 GB

8


 
 

The following requirements are assumed for the above recommendations:

  • Simultaneously used XPhone UC services: analytics, CTI, presence, screen sharing, journal, chat, directory & UM (fax, voicemail, text message, Auto Attendant) with IP channels
  • XPhone Connect Server and SQL Server on one machine
  • Average usage behaviour (chat, telephony, mobile, Team Panel)
  • Connection to a telephone syste
  • Use of the included Microsoft SQL Express Server
  • Directory connection from an ODBC data source

For other application scenarios and quantity considerations, the system requirements may differ. Please contact your ICT partner for the following application scenarios. C4B partners can find the separate system requirements in the partner portal ("Sales Whitepaper").

Separate system requirements apply to the following application scenarios:

  • XPhone Connect and SQL Server on different machines
  • For more than 500 users, use of an SQL Server (Standard/Enterprise Edition) is required. This is usually installed on the same machine as XPhone Connect and provides the best possible performance. The use of XPhone Connect and SQL Server (Standard/Enterprise Edition) on different machines is also supported. This allows the use of an existing SQL Server.
  • Increased system requirements when using the Call Controller (XCC) with AnyDevice and/or Conferencing: The system requirements depend on the number of users who use these services as well as on the expected call volume.
  • Increased system requirements for additional UM IP channels (fax, voicemail, Auto Attendant) and PBX nodes
  • Use as a directory service with fax
  • Use as a directory service without fax/voicemail
  • DMZ: provision of Mobile/Analytics websites


Softphone: Increased CPU requirements depending on call volume

When using softphones, additional CPU cores are required depending on the call volume. An overview of the required cores in relation to the number of calls can be found under "Expansion levels" (see above).

1 From 500 users, the use of an SQL Standard/Enterprise Edition Server is required.
2 Memory for the entire system. XPhone as the only server application besides Microsoft SQL Express.
3 Free disk space for XPhone Connect. If the internal message memory (fax/voicemail) is used intensively, the capacity may need to be increased.
4 A core in the sense of the system requirements corresponds to the efficiency of a modern server CPU (comparable with Intel Xeon processor E7 V4) . In virtualised environments it must be ensured that the performance is available to the guest operating system at all times (dedicated core).

Server: Software

Operating system

  • Microsoft Windows Server 2019 
  • Microsoft Windows Server 2016 
  • Microsoft Windows Server 2012/2012 R2 (SP1)
  • Microsoft Windows Server 2008 R2 (SP1)
  • Microsoft Windows 10 Pro/Enterprise 64 bit (release for CTI/UM usage, maximum 20 users)
  • Current service packs are required.
  • The XPhone Connect Server must not be installed on a terminal server.

Restrictions

  • Microsoft Windows 10 Pro/Enterprise 64 bit: no release for XCC Call Control services (conference call, Follow-Me, AnyDevice & Softphone) and XPhone Connect Mobile
  • The "Desktop Experience" feature is only available from Microsoft Windows Server 2012 R2 onwards. This feature allows the compression of voicemails in MP3 for playback via XPhone Connect Mobile.

Software

  • Microsoft .NET Framework 4.7
  • Microsoft .NET Framework 3.5 SP1
  • Microsoft Messaging API and Collaboration Data Objects (MAPI) 1.2.1
  • Windows Installer 4.5
  • Windows Powershell 1.0

 

SQL Server

  • SQL Server 2017: Express / Standard / Enterprise*
  • SQL Server 2016: Express / Standard / Enterprise
  • SQL Server 2014: Express / Standard / Enterprise
  • SQL Server 2012: Express / Standard / Enterprise

*SQL Server 2017 is only approved as of XPhone Connect 7.

Webfrontend

(Administration)

  • Internet Explorer 11 / 10
  • Firefox 61
  • Chrome 65
  • Edge 42

C4B tests all browser versions available at product release. Using the mentioned versions provides the best performance. With older versions technical limitations may occur.

Virtualisation

  • VMware ESX / ESXi Server 
  • Microsoft Hyper-V
  • Citrix Xen Server

When connecting UM services in virtual environments, sufficient system capacities for the XPhone Connect IP channels (XCAPI interface) must be available at all times. A dedicated processor core is necessary. For more information, see the technical documentation for XCAPI.

In a virtual environment, the virtualised computer must also use the hardware timer of the host system, since purely virtualised timers are usually not precise enough for voice transmissions.

For detailed information regarding hardware/virtual timers, please refer to the documentation provided by the virtualisation provider.




Interfaces


 

CTI services

For CTI services a compatible PBX system with enabled CSTA/TAPI interface is required.

The TAPI driver must be able to monitor all lines of the PBX system.

IP channels (SIP/H.323)

TE-Systems XCAPI


ISDN channels

An ISDN connection requires a project-specific release and is possible for the following products:

  • Dialogic DIVA BRI-2 / 4 BRI-8 / PR I / E1-3
  • Funkwerk RT Router


Sending text messages

  • Certain web providers via HTTP (e.g. Mesmo)
  • LA REST (Swisscom)
    no support for long text messages


E mail server

  • Microsoft Exchange Server 2016, 2013 or 2010
    (Mixed operation on request, fee-based evaluation required)
  • Other e-mail servers with IMAP / SMTP support

 

LDAP
(PBX or device)

LDAP V2/V3

The features of the contact data integration depend on the particular LDAP-capable PBX/device and the UC clients being used.


 
 
 

Client

Operating system

  • Microsoft Windows 10 Pro/Enterprise (32/64 Bit)
  • Microsoft Windows 8.1 Pro/Enterprise (32/64 Bit)
  • Microsoft Windows 7 SP1 Pro/Enterprise (32/64 Bit)
  • Current service packs are required.
  • The use of XPhone Connect clients in the version 6 or 7 on XPhone Unified Communications or XPhone Connect 5 servers is not supported.

Terminal-Server

  • Microsoft Windows Server 2019 (64 Bit)
  • Microsoft Windows Server 2016 (64 Bit)
  • Microsoft Windows Server 2012 R2 / 2012 (64 Bit)
  • Citrix XenApp /XenDesktop (64 Bit)
  • The memory required depends greatly on the individual configuration (e.g. call load, connected databases, user behaviour). From the second user onwards, only a fraction of the memory demands of the first user are required.
  • Full XPhone Connect-Outlook integration is only guaranteed if both the XPhone Connect Client (including Outlook plug-in) and Outlook are installed on the terminal server.

The following restrictions apply when Outlook is running in a different environment than the XPhone Connect client:

  • The XPhone Connect Outlook plug-in (integration of CTI, UM, conference calls, presence) can not be installed.
  • Private Outlook contact folders must be connected centrally via the XPhone Connect Directory. A client-side connection is not possible.
  • The Outlook contact card can not be accessed from the XPhone Connect Client.

Webfrontend

(Analytics)

  • Internet Explorer 11 / 10
  • Firefox 61
  • Chrome 65
  • Edge 42

C4B tests all browser versions available at product release. Using the mentioned versions provides the best performance. With older versions technical limitations may occur.


Note: Parallel installation of XPhone Unified Communications and XPhone Connect clients is not supported by C4B.

 

Mobile

  • Android 9*
  • Android 8
  • Android 7
  • iOS 12
  • iOS 11
  • iOS 10

*  Under Android 9 only connections to the XPhone server via SSL (HTTPS) are possible. An update in the Google Play Store is in preparation.

Solutions

Exchange/Outlook
IBM Notes
Cisco Jabber
Skype for Business
SAP
Salesforce
Microsoft Dynamcis
proALPHA

Microsoft Exchange / Microsoft Outlook

  • Microsoft Office 365 Business
  • Microsoft Office 365 Business Premium
  • Microsoft Office 2019 (Outlook) (32/64 Bit)
  • Microsoft Office 2016 (Outlook) (32/64 Bit)
  • Microsoft Office 2013 (Outlook) (32/64 Bit)
  • Microsoft Office 2010 (Outlook) (32/64 Bit)

Application integration functions across various locations, PBX systems and manufacturers. Support of the Exchange Server is through configuration only. A software / add-in installation on the Exchange Server is not required. CTI, UM and conference functions are provided with an Outlook add-on.

 
 

Hosted Exchange / Microsoft Outlook 365

If the Exchange Server is not on the company network, as with Microsoft Office 365, there are functional limitations and special technical requirements for the XPhone Connect Server due to the lack of MAPI connectivity. For more information, see: Microsoft Outlook

  • IBM Notes 10
  • IBM Notes 9
  • IBM Notes 8

Supported Versions: Jabber Client

  • Cisco Jabber Client Versions 12, 11.9, 11.8, 11 and 10.6.0 for Windows
  • Cisco Jabber Client Version 11.8 and 10.6.0 for Mac
  • Cisco Jabber Client Version 10.5.2 for iOS (iPhone / iPad)

Supported Versions: IP-Phones

Supported are IP-Phones with the "Cisco IP Phone Services"-Interface e.g.:

  • 79xx Cisco IP Phone Serie
  • 89xx Cisco IP Phone Serie
  • 99xx Cisco IP Phone Serie

Version

Contact data integration

Dashboard support

Skype for Business 2016 for Windows

Funktion vorhanden

Funktion vorhanden

Skype for Business 2015 for Windows

Funktion vorhanden

Funktion vorhanden

Skype for Business for Android 6.0.0.8 1

Funktion nicht vorhanden 1

Funktion nicht vorhanden

Skype for Business for iOS 6.2.0

Funktion vorhanden

Funktion nicht vorhanden


1 The Skype for Business Mobile Client (Android) displays the presence information under a search result. If, however, the result is from the XPhone Connect Directory, "update running" is permanently displayed. This behaviour has been investigated and is caused by the Skype for Business Mobile Client (Android).

2 The Microsoft Lync Mobile Client 2013 does not allow searches that include umlauts. It is currently unknown whether or when Microsoft will provide new Lync 2013 Mobile Clients with modified search behaviour.

 
  • SAP R3

  • Salesforce Lightning
  • salesforce.com 

Microsoft Dynamics CRM

  • Microsoft Dynamics 365 for Sales
  • Microsoft Dynamics CRM 2016
  • Microsoft Dynamics CRM 2013
  • Microsoft Dynamics CRM 2011
 
 

Microsoft Dynamics AX

  • Microsoft Dynamics AX 2013
  • Microsoft Dynamics AX 2012
 
 

Microsoft Dynamics NAV

  • Microsoft Dynamics NAV 2017 (on premise)
  • Microsoft Dynamics NAV 2016 
  • Microsoft Dynamics NAV 2015
  • Microsoft Dynamics NAV 2013 
  • Microsoft Dynamics NAV 2009
  • proALPHA V5.3
  • proALPHA V5.2
  • proALPHA V5.1

Release Notes

An overview of all release notes can be found here: XPhone Connect Release Notes

Subscribe to our Newsletter

 
 
 
 
 
 
 

Thank you for subscribing. To confirm your subscription, please click the link in your registration email.

 
 

An error occured. Please try again.



Cookies ermöglichen eine bestmögliche Darstellung unserer Dienste. Mit der Nutzung der Seiten von C4B Com For Business, erklären Sie sich damit einverstanden, dass wir Cookies verwenden. mehr Infos