Bridge V16 / V18

[HannesCLP]

Hi everyone,

we have multiple V16 3CX instances running which are connected using the bridge feature of 3CX. We would like to upgrade one of the instances to V18. Are there any complications with the bridge feature connecting V18 und V16 instances? Is there anything else to consider running this "mixed" environment?

Thanks,
Hannes

 

[VasilisV_3CX]

Hi @HannesCLP,

Bridges do require both systems to run the same version.

Have a look at the following: https://www.3cx.com/blog/releases/v18-final/

 

[Alphabetic]

Hi everyone,

we have multiple V16 3CX instances running which are connected using the bridge feature of 3CX. We would like to upgrade one of the instances to V18. Are there any complications with the bridge feature connecting V18 und V16 instances? Is there anything else to consider running this "mixed" environment?

Thanks,
Hannes

Yes, it wont work if they're both not 18 (as mentioned above)

 

[HannesCLP]

Thanks a lot for your feedback That helps a lot!

 

[leejor]

In the past, Bridges between various versions of 3CX worked, for the most part. There may have been some features that did not pass, but basic calls were usually not a problem.

What is now different with the Bridge trunk options in version 18? Does this also mean that people attempting to use a Bridge trunk, to a non-3CX PBX shouldn't bother, as there is no possibility of it working?

Not being backwards compatible with version 16 (or earlier) installs, may throw a monkey wrench into plans that don't include upgrading all bridged installations, at the same time.

 

[Evolute IT]

In the past, Bridges between various versions of 3CX worked, for the most part. There may have been some features that did not pass, but basic calls were usually not a problem.

What is now different with the Bridge trunk options in version 18? Does this also mean that people attempting to use a Bridge trunk, to a non-3CX PBX shouldn't bother, as there is no possibility of it working?

Not being backwards compatible with version 16 (or earlier) installs, may throw a monkey wrench into plans that don't include upgrading all bridged installations, at the same time.

The reason is the new chat features like editing participants in a group. Some of the APIs the PBX use to talk to each other has changed.

Calling will still work tho. Only presence and chat doesn't work between versions.

 

[AWS2P]

Well,as I used for a while bridged pbxs but one linux V18 and an on premise windows in V16 , So bridge just loose the presence on each side but calls where always working fine
Now V18 for Windows is released and applyied on both ends everything came back to normal