Introduction

This document outlines the compatibility matrix among various Fusion for Broadworks releases and the dependencies they rely on. These dependencies may include Fusion for Broadworks (internal) component dependencies, operating system dependencies or sub-system dependencies, for example PostgreSQL serving as the database.

Fusion for Broadworks compatibility matrix

In this section the compatibility is shown between the internal components of the Fusion for BroadWorks solution.

Remark: As the APIO Core release is independant from the self-care portal (UC Control Hub) and the BroadWorks gateway, the table shows a minimum APIO Core version. The recommended version of the APIO Core is always the latest General Available (GA) version. The BroadWorks gateway shows a recommended version as there is more dependency between the gateway and the self-care portal.

F4B_UCCH	BKWS Gateway (recommended version)	APIO Core-Python based (minimum version)	APIO Core-GO based (minimum version)
2.5	1.9.3	0.23.2	2.0.1.rc12
2.5	1.9.4	0.23.2	2.0.1.rc12
3.0	1.9.4	0.23.2	2.0.1.rc12
3.1.0	1.9.5	0.23.2	2.10.0
3.1.1	1.9.5	0.23.2	2.10.0
3.1.2	1.9.5	0.23.2	2.10.0
3.1.3	1.9.5	-	2.11.2
3.1.4	1.9.5	-	2.11.2
3.1.5	1.9.7	-	2.11.2
3.1.6	1.10.2	-	2.11.2
3.2	1.10.3	-	2.12.0
3.3.0	1.10.2	-	2.13.1
3.3.1	1.10.2	-	2.13.1
3.3.2	1.10.2	-	2.13.1
3.3.3	1.10.2	-	2.13.1
3.3.4	1.10.2	-	2.13.1
3.4	1.10.5	-	2.13.2
3.5	1.11.1	-	2.14.0
3.6	1.11.2	-	2.15.1

F4B - Subsystem compatibility matrix

		Docker	ALMA		CentOS		RedHat (*)			Postgresql
	Versions	23	8	9	7	8	7	8	9	12	13	14	15
Netaxis solution	latest Rls (GA)
APIO Core	2.14.0	✅	✅	✅	✅		✅	✅	✅			✅	✅
BKWS Gateway	1.11.2		✅		✅	✅	✅	✅		✅		✅

(*) The same compatibility counts for Oracle Linux as for the RHEL.