V18 Update 1 Beta: Fine-Tuning Teams Integration

[Gravité Managed IT]

@Gravité Managed IT

1) Yes, so you can have the correct users per 3CX system
2) this makes it a bit simpler as you could get away with only one dial plan assuming users always dial the area code (02 or 03) for outbound calls. In this case, you have to create a second SBC connection (you can copy the general idea from it from the script New-CsOnlineVoiceRoute) After creation you need to modify per user which SBC they should be using in the voice route.

Thanks @StefanW , unfortunately employees will only use 02, 03, 07, 08 for number they're not geographically located in...e.g. if I am in Melbourne Australia (03) then when I call a local number here I won't use the 03, but would use the other 02, 07 and 08 for other states I may be calling.

When you say when I add the second SBC can I modify your script and run it the same way or do it manually, or I should not need to run any script and just mod the users to use the correct PBX (using your New-CSOnlineVoiceRoute) script?

Sorry, it will be a big "thing" for us as we have plenty of customers sitting on the fence that are all in similar boats.

 

[StefanW]

then you need to create multiple dial plans covering the prefixes to accommodate common dialling patterns for the user. Generate one script and update the dial plan name so you can save it for each need. This dial plan you assign then the user in MS Teams Admin.

For simplicity, run the default the Set-CsUser creation and then later change the policy the user should follow and with this also to which SBC (3CX). You have to do some groundwork to understand the gears and how they work together in MS Teams. I can confirm 100% that it is possible to do what you are looking for as we have the same (or even worse) construct.

SBCs

Policy

Dial Plans

Routes

 

[bgrattan]

V18 is already released for Linux.

Update 1 is compatible with Windows, but it is a beta right now.

It should be released officially within a few weeks IMO.

Thank you for this quick response. It gives me hope my issue will soon be resolved.

 

[snits35m]

@sentrianjames thanks for the headsup! What kind of REST API are you referring to? As in what functions are you expecting? We already have a REST API to create conferences for example and will expand this to live chat and calls as well....

I am also eagerly waiting for an API and am hoping for the following functionality:
- To be able to query and set extension status (available, absent, calling, ...)
- Query data of the current call from an extension
- Start a call on an extension
- Query queue statistics
- And so on

In my case, this would be for integration into our own "jack of all trades" system, but I think that many other customers also urgently want this functionality (again).

 

[N_G]

@snits35m There will definitely be an API to trigger and stop a call. Probably also to set extension status as we do it for teams. However the other functions such as query queue stats or data from a call are unlikely to make it into the PBX.

 

[Evolute IT]

@snits35m There will definitely be an API to trigger and stop a call. Probably also to set extension status as we do it for teams. However the other functions such as query queue stats or data from a call are unlikely to make it into the PBX.

Querying current calls with ability to at least filter by extension or trunk would be a great middle ground

As for extension status with Teams... that means it's gonna be synced? If so, NICE.