V18 Alpha 3 - Fixes and Features

[NickD_3CX]

1) User Sync: Common Special Characters in the users 365 Office Phone and Mobile Phone numbers are synced to 3CX. When editing the extension these must be removed because 3CX is not allowing these, but they come back on the next sync. If they are left alone they impact dialing rules or other functions. Specifically, dashes and parentheses, and possibly periods. Could 3CX possibly allow these to be stored, but strip them from dialing functions? An alternative would be to strip them when importing.

In V18 these should be now stripped

2) Calendar Sync: Outlook appointments set to "Working Elsewhere" could be mapped to 3CX "Available 2". It would also be preferable to allow 3CX admins to map the status desired as I can see where some may want Outlook "Out of Office" mapped to 3CX "Away 2".

We shall consider this, but I would suggest maybe posting this in the 'Ideas' section

we do have to use a starting extension number when creating new users, but existing email addresses that match when sync is setup will sync the user to that extension. This seems to work well, but I am wondering what happens if the user has two or more extensions with the same email address.

Of course, the option to start from a certain Extension Number is for when creating/syncing new Extension.
If 3CX though sees that the email of an existing extension matches the email/principal name of a Azure AD user, then it will be mapped to the existing extension with whatever is existing extension number is.

Now if there are multiple extensions in 3CX with the same email, a random one will be synced (usually the first one that was created).
Of course when you plan on syncing existing extensions with O365, you should make sure that duplicates emails don't exist, at least not for the AD Users you will be syncing.

 

[accentlogic]

In V18 these should be now stripped

Thanks @NickD_3CX - Is that coming after alpha 3? If so, thanks in advance!

 

[NickD_3CX]

Thanks @NickD_3CX - Is that coming after alpha 3? If so, thanks in advance!

The fix should already be in Alpha 3.

 

[accentlogic]

The fix should already be in Alpha 3.

I upgraded our test instance from Alpha 2 to Alpha 3, and then enabled 365 User sync. Below is a screen shot of what happened to existing users mobile and outbound caller id fields. PM me if you need any more details.

 

[NickD_3CX]

I upgraded our test instance from Alpha 2 to Alpha 3, and then enabled 365 User sync. Below is a screen shot of what happened to existing users mobile and outbound caller id fields. PM me if you need any more details.

View attachment 21678

We shall be checking that, thanks!

 

[Securify]

Furthermore we are making steady improvements to our PUSH reliability. We are in constant contact with Google and Apple and are making changes and improvements. You should already see better PUSH performance with more to come. Let us know how we are doing in V18 with PUSH!

Is it possible to imagine simple scenario with iPad Pro connected to local access point or even better connected to USB-C hub with ethernet

There is no need to use a VoIP provider – if you have a good telecoms provider PSTN lines can still provide a very reliable service.

Build local push connectivity for restricted networks - WWDC

• appropriate for use cases where an iOS device operates on a local, restricted network that doesn't have access to APNs

@Jimesh

Due to security restriction I can't allow internet to my on premise 3cx server.

I want to use web meeting / web conference internally via LAN but can't allow Internet to to client & 3cx Server.

This forum would like to send you push notifications.

 

[cobaltit]

Then it sounds like you need a different product.

 

[ross.downie1]

Can we expect to see Cisco 3PCC Multi Platform phones such as the 7821, 7841, 6851, 8841 added to the supported devices?? Please......

 

[N_G]

@ross.downie1 I am afraid not, likelyhood close to zero. A lot of work has to be done on Cisco end and also 3CX. You already have a good selection of phones....

 

[SelfDesigner]

I hope there is an option for people to utilize SSO without having to use a cloud provider. For example, having the capability to utilize OpenID Connect from your own provider, or a SAML IDP would be far better for those who would like to stay away from the cloud services. After all, that's why we're running our own PBX right? To maintain control?

LDAP would also e a great complement to automatically load a user table (and authenticate without sso)

 

[ross.downie1]

@ross.downie1 I am afraid not, likelyhood close to zero. A lot of work has to be done on Cisco end and also 3CX. You already have a good selection of phones....

Hi Nick, thank you for taking the time to reply i really appreciate it.

You are correct and i agree there is a great selection of phones already, our preference is Yealink which i think are great, but it is some of our clients who request Cisco Phones, or new opportunities arise and they currently have Cisco and we would like to migrate them to 3CX.

I think the Cisco handsets would make an excellent addition to the supported handsets and fully compliment the 3CX system.

I'll wait in hope that perhaps one day they appear on the supported device list...

I mean you did say "close to zero" which in my book isn't completely zero... hahah lol

Again thank you for taking the time to reply to me i know you are a very busy man.

 

[N_G]

@ross.downie1 No problem at all! I think if customers insist on CISCO handsets tell them to buy a Cisco phone system.

Close to zero for me means something like one in a million. Think that scene of the movie where Jim Carrey asks a girl what his chances are

 

[ross.downie1]

@ross.downie1 No problem at all! I think if customers insist on CISCO handsets tell them to buy a Cisco phone system.

Close to zero for me means something like one in a million. Think that scene of the movie where Jim Carrey asks a girl what his chances are

Thanks Nick,

I think I know the film you are talking about.... but did he not get her in the end??

I just think its a shame that they aren't supported as they are on other platforms as standard. maybe one day.

have a great day and thanks again for replying.

 

[N_G]

@ross.downie1 hahaha i dont think he did but i will need to check. this is the movie in question Trust me to support a phone is a lot of work these days. Some older platforms dont have the level of integration we do so they can get basic stuff working. But these days to get it working in a secure manner - on premise or in the cloud - supporting all the features needed and with in depth interop testing its not easy. And ongoing over the years is another point. Not all integration is equal. There is "other pbx" integration, then there is 3CX integration... So it requires a lot of work from both parties and neither party is interested at this point.

 

[DinoMueller]

LDAP would also e a great complement to automatically load a user table (and authenticate without sso)

+1 for LDAP authentication

In my new workplace we are just searching for a new PBX for ~400 employees and because I have experience with 3CX over the last years we considered 3CX.

But unfortunately the missing LDAP authentication is the deal breaker here. We cannot sync to O365 and login with the SSO option, because we are not using O365 or even Active Directory. We just use a plain and simple OpenLDAP-Server.

And I really cannot understand why there is no support for such basic functions. Or the broken phonebooks on hardware phones for years. A PBX should have a working phonebook at least.

If I do a search for "LDAP" here in the forum I think there would be lots of happy people if 3CX would support LDAP authentication.

Regards,
Dino

 

[N_G]

@DinoMueller - I dont think people choose a PBX based on LDAP authentication, and the number that use OpenLDAP is very small indeed. But for those that do, you can simply use the inbuilt authentication. So unfortunately it seems you need to look elsewhere for your solution.

 

[DinoMueller]

It seems so. At my old workplace we sold 3CX and we had so many customers where LDAP was mandatory and we had to let them go.

 

[Evolute IT]

It seems so. At my old workplace we sold 3CX and we had so many customers where LDAP was mandatory and we had to let them go.

Here's a good trick: don't sell 3CX. Sell VoIP Solutions.

You evaluate the customer needs and sell them something that works for them. If they need LDAP, 3CX is definitely not the right choice. However, many free PBXs or other brands do support LDAP Auth (in some capacities at least.)

We never tell a customer that we sell 3CX only. We sell a solution.

 

[DinoMueller]

We never tell a customer that we sell 3CX only. We sell a solution.

I know that. That's why it is my "old" workplace now ;-)

 

[AlanRamsay]

Is there a v18 SBC for PI that we can test too?