Can I please have some clarification on this. We, like many others, have clients using the Teams integration for the sole purpose of using the Teams client as the users handset. I have seen that Nick has said that is not where the 3CX software is going, but none the less, this is what we have.
From what I understand the "Teams and 3CX forking" is what allows the Teams client to ring when someone calls the users 3CX extension. It obviously works for the moment. Am I to understand that one random day Microsoft may make a change, that will break the forking, and 3CX are no longer going to fix it? At which point there will be a mad scramble to install the 3CX client on hundreds of machines followed quickly by a migration to a native Teams telephony system.
I am just wanting to know when the wheels are going to come off, so I can prepare for it.
From what I understand the "Teams and 3CX forking" is what allows the Teams client to ring when someone calls the users 3CX extension. It obviously works for the moment. Am I to understand that one random day Microsoft may make a change, that will break the forking, and 3CX are no longer going to fix it? At which point there will be a mad scramble to install the 3CX client on hundreds of machines followed quickly by a migration to a native Teams telephony system.
I am just wanting to know when the wheels are going to come off, so I can prepare for it.
