Removing Teams based routing.

[CFP]

Are there any instructions on removing teams based routing?
As it's being deprecated, no point us testing it anymore... our teams room equipment will need to be changed, unless at somepoint in the future 3CX can work with the teams client. (would be nice to have it all unified under that client)

 

[Evolute IT]

Are there any instructions on removing teams based routing?
As it's being deprecated, no point us testing it anymore... our teams room equipment will need to be changed, unless at somepoint in the future 3CX can work with the teams client. (would be nice to have it all unified under that client)

Teams will still be integrated, but on a trunk level, which will disable forking but still allow for usage of the 3CX trunks through Teams.

 

[CFP]

Teams will still be integrated, but on a trunk level, which will disable forking but still allow for usage of the 3CX trunks through Teams.

sorry for the leymans question but how does that differ from the current routing? - would we no longer need to run the user script to get people setup in order to see the dialer on the Teams client? - just trying to get my head around how this would actually be implemented and how it would look / feel to our end users.. and our Teams room equipment..

 

[Evolute IT]

sorry for the leymans question but how does that differ from the current routing? - would we no longer need to run the user script to get people setup in order to see the dialer on the Teams client? - just trying to get my head around how this would actually be implemented and how it would look / feel to our end users.. and our Teams room equipment..

We have no details yet on what 3CX is planning. Only that forking won't work anymore (so one user won't be assigned to a Teams user and ring both.) It will work more like independant users on each side, using the same trunks. (That's our understanding at the moment.)

 

[CFP]

gotcha.. in that case i may sit tight and let it carry on as is for now..

 

[N_G]

Yes, just to jump in here for now the integration is staying the same..... We just dont recommend using the teams client as a full replacement for 3CX just to have 3CX and Teams users, i.e. Teams client for Teams users and 3CX client for 3CX users but calls can be made easily between systems and also routed to Teams.....

 

[Guillaume Bourgeois]

Yes, just to jump in here for now the integration is staying the same..... We just dont recommend using the teams client as a full replacement for 3CX just to have 3CX and Teams users, i.e. Teams client for Teams users and 3CX client for 3CX users but calls can be made easily between systems and also routed to Teams.....

Hello Mr.Galea,
do we know a little more about the changes to come in this regard?

Am I on the wrong track by perceiving the future like this:

Thus, the functionality of Call Forking 3CX Client & Teams will be removed but, it will have a Teams "Outbound Rule" in the 3CX SIP Trunk .. the equivalent of a "3CX Bridge" ? For calls from Teams Users to 3CX users.., same principle as 3CX Bridge.. no need for InboundRule ?

If correct,
Am I wrong in assuming that 3CX will support sending the string ;ext= to a trunk / SIP third party ?
for now, if try send call to ; 8197407894;ext=1234 it is automatically reformatted to 8197407894ext1234 .

I know, I know, I'm ahead, but I'm investigating the possibility of using "Ring My Mobile Simultaneously" to ring Teams at the same time as 3CX . Of course, we understand the impacts on the 3CX license (simultaneous calls) but if it can satisfy our customers who insist on ringing both, it would be an alternative solution to "Call Forking" Teams & 3CX .



The goal is obviously to prepare us for the new realities to come.

Thx