V18 Beta 1 - Gearing up for release

[SKDamon]

Does TAPI still work in V18 with the new Desktop App?
I think after V15, the "MultiLine TAPI" vanished from the edition comparison page,
and the install docs refer to V15 Plugins: https://www.3cx.com/docs/installing-multi-line-tapi/

Some customers prefer the integrated "Call" button in their Programs over selecting the phone number and hitting a hotkey...

 

[imerecom]

Thanks, missed the new mail.send in the list on the page made the changes waiting propagation.

This is still not working after making the changes yesterday that @Frederick Marcoux suggested. Can we get the specific settings that need to be added to an already working sync setup for this new feature?

 

[Evolute IT]

This is still not working after making the changes yesterday that @Frederick Marcoux suggested. Can we get the specific settings that need to be added to an already working sync setup for this new feature?

Redo the whole config, sometimes it is needed. However, I didn't have to.

Are you sure you did the "Grant Admin consent"?

 

[dallaskincaid]

Question about the teams integration. Is the 24 hour sync time a limitation from 3CX or from Microsoft?

 

[Constantinos Constantinou]

@dallaskincaid from Microsoft side, but in the majority of the cases is faster than that.

 

[edossantos]

Does TAPI still work in V18 with the new Desktop App?
I think after V15, the "MultiLine TAPI" vanished from the edition comparison page,
and the install docs refer to V15 Plugins: https://www.3cx.com/docs/installing-multi-line-tapi/

Some customers prefer the integrated "Call" button in their Programs over selecting the phone number and hitting a hotkey...

Multiline TAPI still works with the old Windows client. 3CXPlugins v15 works with the Windows client for 3CX v16 or v18. A PRO license is required.

 

[Stephen Quam]

One issue with the teams integration is that when calling another 3cx extension from teams, it truncates the first digit off on the caller id.

 

[Constantinos Constantinou]

One issue with the teams integration is that when calling another 3cx extension from teams, it truncates the first digit off on the caller id.

Hello @Stephen Quam ,

Can you please clarify if in your case you are calling a bridge extension?

If your setup involves bridge, then you need to adjust the dial plan normalization rules to handle those bridge extensions.

 

[ENCOM-GEFFRAY]

One issue with the teams integration is that when calling another 3cx extension from teams, it truncates the first digit off on the caller id.

In the operational mode to declare the teams 3CX requires the creation of a subdomain that will carry the SBC.
In order to apply the certificate to the subdomain it is necessary to provide the certificate issuing authority with the CSR of the host web server.

In our understanding of all this it is that the SBC / web server is the 3CX.
There is no way to generate the CSR.

How did you do it?

Also the script that will be generated later that we have to run, does it automatically register the SBC on the teams side or does it have to be declared upstream in the TEAMS tenant.

@Nick Galea Can we have a modus operandi for the commissioning of Teams direct routing on 3CX ?

 

[ENCOM-GEFFRAY]

@Nick Galea We are pleased to see all these new features on the V18. This will allow us to continue to attack the market with a powerful product!

In the browser plugin or windows client version in all previous versions it was possible to have keyboard shortcuts. What about v18?

Also it has always been possible from the dialer to modify its status. Will we find this feature used by all our users again?

 

[NikosT_3CX]

@Holonet lets clear things up

So, for example, you have domain " holonet.com " which is also your email domain as you have email " [email protected] " in Microsoft 365.

Now lets say your PBX is with FQDN " holonet.3cx.eu " which is kind of different with your email domain.
No problem at all, go and generate a CSR (https://csrgenerator.com/) for "teams.holonet.com" (Common Name).
Take the CSR and paste it at a Certificate Provider, the Certificate not the key (this copy it somewhere and keep it) and generate your SSL Certificate.

Then you take this you make it.pem , also the key you make it .pem and you upload it to the PXB and also specify FQDN "teams.holonet.com " .
You must put an A Record on IPv4 for "teams.holonet.com" at your DNS to point to the Public ip of the PBX.
That's it for the connection between the PBX and Teams.
Also open port 5062 TCP for this..

 

[Alphabetic]

How does one change the display name of the 3CX Wallboard?

 

[ChrisC_3CX]

@kieferschild

How does one change the display name of the 3CX Wallboard?

You need to click on the "3 dots >> Settings >> View" and scroll down to where it says "Wallboard".

 

[Alphabetic]

@kieferschild

You need to click on the "3 dots >> Settings >> View" and scroll down to where it says "Wallboard".

Where?

 

[ChrisC_3CX]

@kieferschild

Is this extension perhaps not a member of a Queue or is not a Queue Manager?

 

[Alphabetic]

@kieferschild

Is this extension perhaps not a member of a Queue or is not a Queue Manager?

Ah, now I can see it

 

[Stephen Quam]

Hello @Stephen Quam ,

Can you please clarify if in your case you are calling a bridge extension?

If your setup involves bridge, then you need to adjust the dial plan normalization rules to handle those bridge extensions.

No bridge involved.

 

[Constantinos Constantinou]

@Stephen Quam
Share more information about it via PM please

 

[Ulmer]

Hello,
we use a 3cx Pro (Build 18.0.1849) with waiting queues in the cloud (not hosted by 3cx).

If Microsoft Teams Direct Routing disable, waiting queues works fine.
If Microsoft Teams Direct Routing enable, incoming and outgoing calls work great, until call from waiting queues.
Answering (with 3cx app) the queue calls does not work if the agent also has MS Teams. has also observed this?

Thanks

 

[Evolute IT]

Hello,
we use a 3cx Pro (Build 18.0.1849) with waiting queues in the cloud (not hosted by 3cx).

If Microsoft Teams Direct Routing disable, waiting queues works fine.
If Microsoft Teams Direct Routing enable, incoming and outgoing calls work great, until call from waiting queues.
Answering (with 3cx app) the queue calls does not work if the agent also has MS Teams. has also observed this?

Tanks

I didn't test that yet, good thing to test.

However, I did notice some bugs here and there but as specified, it's a Beta version with the Alpha version of Direct Routing, so let's give them some time lol