PBXs supported

The PBXs were tested by C4B and officially approved.

Alcatel

Model	Version	CTI		UM			XCC
		CSTA	TAPI	ISDN	SIP	H.323
OmniPCX Office (OXO) Octopus Open	from V8.1	◼		◻ [1]	◼ [2]		◼ [3]
OmniPCX Enterprise [6] (OXE) Octopus EP	from V9.1 Patch 26	◼ [4]		◻ [1]	◼		◼ [5]

[1] (1,2)

Project specific ISDN release.

[2]

No MWI signaling when connected via SIP.

[3]

XCC tested with Version 10.0

[4]

Restriction: Call forwarding during a call impossible due to pbx restrictions.

[5]

XCC tested with Version 11.1

[6]

XPhone Connect support Alcatel-Lucent OXE with trunking scenarios with node numbers.

Auerswald

Model	Version	CTI		UM			XCC
		CSTA	TAPI	ISDN	SIP	H.323
Commander 6000	from V8.1	◼ [7]	-	-	-	-	-

[7]

With LAN-TAPI.

Avaya

Model	Version	CTI		UM			XCC
		CSTA	TAPI	ISDN	SIP	H.323
Communication Manager (ACM)	6.3	◼ [8] Phase 3	-	◻ [9]	◼	◼	◼ [10]
IP Office 500 and IP Office Server Edition	9.1.7.0.163	-	◼ [8]	-	◼ [11]	◼	◼ [12]

[8] (1,2)

CTI control of DECT devices is not supported.

[9]

Project specific ISDN release.

[10]

XCC tested with Version 6.3.

[11]

UM tested via SIP, MWI not functional.

[12]

Rejected XCC calls are not signalled to the caller. Clip No Screening is not supported. Automatic authentication for conference calls using the phone number is not supported.

CISCO

Model	Version	CTI		UM			XCC
		CSTA	TAPI	ISDN	SIP	H.323
Unified Communications Manager (CUCM), BE6000, BE7000	CUCM V5.0 - V12.5	- _	◼	◻ [13]	◼ [14]	-	◼ [15]

[13]

Project specific ISDN release.

[14]

T.38 Fax: TLS/SRTP not supported.

[15]

XCC tested with Version 11.0.

Supported client versions

• Cisco Jabber Client: Version 12, 11.9, 11.8, 11.0 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 IP-Phones versions

IP-Phones with “Cisco IP Phone Services” Interface not supported.

• Series 79xx

• Series 89xx

• Series 99xx

Deutschland LAN Cloud PBX (Telekom)

Model	Version	CTI		UM			XCC
		CSTA	TAPI	ISDN	SIP	H.323
Cloud PBX	Stand 12.2019	◼ [16]	-	-	-	-	-

[16]

Internet connection and account for Cloud PBX (MyPortal) required.

Innovaphone

Model	Version	CTI		UM			XCC
		CSTA	TAPI	ISDN	SIP	H.323
Innovaphone	12R1	- _	◼ [17]	-	◼ [18]	◼ [19]	◼

[17]

DoNotDisturb not supported.

[18]

MWI via SIP not supported according to TE-Systems.

[19]

UM tested with H.323.

Mitel

Model	Version	CTI		UM			XCC
		CSTA	TAPI	ISDN	SIP	H.323
MiVoice Office 400 MiVoice Office 415 MiVoice Office 430 MiVoice Office 470	VR6.1	◼ [20]	-	-	◼	-	◼ [21]

[20]

Mitel Twinning and DoNotDisturb not supported.

[21]

XCC - Consultation and Reject not supported.

Unify

Model	Version	CTI		UM			XCC
		CSTA	TAPI	ISDN	SIP	H.323
OpenScape Business X3/X5/X8/S Octopus FX3/X5/X8/FX8S	V1 R3 V2 V3	◼ [22] [23] Phase 3	-	-	◼ [24]	-	◼ [25]
OpenScape Office MX Octopus F470 UC		◼ Phase 3	-	◻ [26]	-	-	◻ [27]
OpenScape Office LX/HX Octopus F670 UC		◼ Phase 3	-	◻ [26]	◼ [24]	-	◻ [27]
OpenScape Voice (former HiPath 8000)	V3.1 V8 V9	◼ XML	-	-	◼	-	◻ [28]
OpenScape 4000 (ehem. HiPath 4000) Octopus F900	V6/V8	◼	-	◻ [26]	◼	-	◻ [29]

[22]

Openscape Buiness S: CTI connection via „Master Node“ directly.

[23]

Openscape Buiness X: Till V2 mainboard CTI connection via Booster Card/Server. From V3 mainboard with CSTA licences.

[24] (1,2)

MWI not supported.

[25]

XCC tested with version 3.3.0_552 / In OSBiz a networking license is required.

[26] (1,2,3)

Project specific ISDN release.

[27] (1,2)

Hint: AnyDevice / Conference on demand.

[28]

XCC tested with Version V8 R0.34.8 / V9 R0.12.4

[29]

XCC tested with Version V8.

Further PBX systems

The connection between XPhone Connect and the PBX is realised with TAPI, CSTA and SIP/H323. Therefore, compatibility is often ensured even if the system was not specifically tested and approved by C4B.

Use and possible limitations of XPhone Connect with the PBXs can be tested. C4B provides test licenses for their partners free of charge.

Hint: Trunking between PBX systems

The maximum number of SIP gateways that can be configured is 50. Phone numbers must always be signaled/configured in E.164 format (FQTN) for site networks. Virtual numbering (VNR) or virtual node numbers cannot be supported. An additional SBC may be required for this.

Recommendation: XPhone Connect as directory service for Skype for Business - installation path

The XPhone Connect Server for Skype for Business can be installed in a virtual environment or on a server.

An installation of XPhone Connect for Skype for Business front-end server is not recommended. If there is no alternative to this solution, the minimum requirements of the XPhone Connect Server must also be considered during planning.

The installation of the XPhone Connect Server on a Skype front-end server impairs the CPU by a factor of 1.5-2. If the Skype for Business front-end server runs near is maximum capacity, the number of CPU kernels must be increased by a factor of 1.5-2.

Have you found a mistake on this page?

Or is something not formulated well or too vague? Then we look forward to receiving an e-mail, preferably with a suggestion for improvement, to doku@c4b.de. Thank you very much!