Update 8 Alpha - 3CX MS 365 Integration Made Easy!

[tronic]

Thank you for the quick reply and information. Then I want to hold on again. We have the Epos SDW flagships worth almost €100,000 in the company. And 3 CX simply removed the integration. I heard from Epos from developer circles that 3 CX has not communicated with EPOS. I note here again that Plantronics, Jabra and Epos are the largest headset manufacturers in this market. And to prescribe on the part of 3 CX that we should just change the headset. I don't see it. Here 3 CX has to admit that they did not communicate properly with the 3 largest headset manufacturers. I have different information from EPOS. It's me. To be honest, sorry too. That the blame is always shifted back and forth from one to the other. I can understand that 3 CX is not for every x random manufacturer. Support can be given, absolutely correct, but you should support at least the 3 largest ones on the market.

What exactly are you saying is not working?

I would assume that you are only talking EHS integration?

 

[jed]

Thank you for the quick reply and information. Then I want to hold on again. We have the Epos SDW flagships worth almost €100,000 in the company

Sorry, I don't want to be rude. But what did you pay for your 3CX?

We are running EPOS here, and we do not see any issues, use SDW Headset with my 3CXX softphone, and with my Cellphone, and is not interrupted. Right now I use the Universal Headset Driver and I do not have the EPOS Connect installed.

 

[N_G]

@Rifki.Razik OK we will check this out
@JupiterIT - lets look at your reasoning. So first off, you have a 32SC PRO license which costs 1100 euro per year, not 13,000. You spent 90,000 euros (???) on EPOS headsets - almost 90 times the cost of the 3CX license - and you expect 3CX to develop for and support these headsets for the lifetime of this hardware? Are these things gold plated or something? Why not ask EPOS to troubleshoot their universal driver support since you paid them a small fortune?

We did have a brief cooperation with Sennheiser I believe back in 2015 but the cooperation didn't work out. we still upheld the deal, the headsets of that time work with the legacy client of that time and still do to this day.

There are 2 big brands Plantronics and JABRA with Yealink up and coming. We bundled the drivers of Jabra and Plantronics (admittedly reluctantly because they do zero testing and support) and actively support Yealink. And of course we have our universal standards based driver. Those are the facts.

But i am happy to offer you a refund of your yearly license as well as 6 months free to have a smooth transition to an EPOS compatible PBX. No problem at all.

 

[jed]

Are you using the EPOS? I'm in contact with the developers here and I know what's going on behind the scenes.

Hi, we sure do use EPOS our self and we have sold hundreds of SDW, to our customers, and we therefore really rely on the good support for this headset. We haven't found a better headset especially headsets Noice cancelation (filtering out the background noise of colleagues and keyboards, no one we have tested beats EPOS
Our customers with the old v16 Softphone are using EPOS Connect, and we haven't had any issues in this regard, Customers using the Desktop App changed to the Universal Headset Driver (WebHDI) - which was created by 3CX a while back, and this is working as well, and I do hope this to continue, as we, as said also have pushed a lot of Headsets out to our 3CX Customers.

In regard to the Universal Headset Driver (WebHDI) - made by 3CX, I do recall the "Comunity Claims" was held in another tone - a less aggressive tone - and the WebHDI was released very quickly from 3CX. I do believe this is the way to go no matter where you do business, as there are humans on the other end of the community, and if we go with our own assume genes, we are often way out of reality seen from, in this case, both 3CX and EPOS´s perspective.

Thinking about the great contact you have to the EPOS development, may I ask where in the world you are located?

 

[N_G]

@jed - Thanks for the feedback - but I strongly advise against selling new epos headsets with 3CX. I cant comment on the audio quality but we look from a software point of view - at the quality of the API, the vendor support and how much they are willing to test their product against ours.

Stick to a supported solution. The webHID driver is meant for existing headsets already purchased.

The new 3CX softphone will support Yealink & Jabra natively.

 

[jhonku]

Great news about Reports and CRMs improvements!!

Something that could be great at future is to show some of these reports in real time (current day). For example, Team Queue and Agent Queue statistics have great information to monitor daily work agents/queue behaviour for supervisors. Perhaps adding an auto refresh per minute could be excellent.

We are testing CRMs and will come back with some feedback.

Thanks!

 

[N_G]

@jhonky - yes a leaderboard with inbound and outbound real time statistics i much needed! Its in the roadmap....

 

[tronic]

@jhonky - yes a leaderboard with inbound and outbound real time statistics i much needed! Its in the roadmap....

That would just be an extension to "Panel" in the client I assume?

 

[N_G]

Yes indeed or maybe the dashboard, we are thinking about it

 

[Guillaume Bourgeois]

@jhonky - yes a leaderboard with inbound and outbound real time statistics i much needed! Its in the roadmap....

@Nick Galea
Oh yes! That's great!
You seem to know the secrets of whoever manages the roadmap ! LOL
Without promising anything, is there anything else in this roadmap that you can "leak" for the greatest pleasure of your enthusiasts ? No eta , just hints !
We know that .. (Please correct me if I am wrong)
- Your team is working on (or will work on) ;
• The REST API for calls,
• Status synchronization with Microsoft Teams,
• Leaderboard (with real time statistic),
• Split DNS will *maybe* mandatory for On Premise PBXs
• Password Hashing *maybe* extended to other fields where passwords are required (SIP)
• On Premise WebMeeting

Obviously, one or more elements can change or be abandoned, we understand that.
What does 3CX hold for us ?

thx a lot !

Cordially,

 

[N_G]

@Guillaume Bourgeois Thanks for the heads up. I did see the roadmap yes We are working on all those things but i cant say when and if they will make it into the next version immediately.

What i can say for sure is that Split DNS will be a requirement. Its already a requirement for new installs although existing installs can stay on v18 but will have to do split DNS to go to V20.

 

[Alphabetic]

@Nick Galea whilst i've dabbled in the new admin portal via web client I noticed that If I have several live chats, I am unable to decipher the woods from the trees. Has this/will this be addressed so we can modify the names to make them more identifiable?

 

[arillera]

Just trying Update 8 Alpha and seems like trunks are also available in the web client admin console for all roles except Manager, Receptionist, and User.

This is kind of dangerous especially if we give our clients System Administrator Role just for managing their own basic call flow. The client might delete the trunks by mistake or otherwise, then blame us for issues.

 

[Evolute IT]

This is kind of dangerous especially if we give our clients System Administrator Role just for managing their own basic call flow.

Then give them the manager role instead? Or group manager.

 

[arillera]

Then give them the manager role instead? Or group manager.

Group Admin, Group Owner, System Admin, and System Owner roles all have access to the trunks.

Manager does not have access to call flows.

 

[sam.phillips]

Just want to chime in to say very excited about the 365 and CRM improvements in Update 8.

But it annoys me dev time has been spent on enable TAPI in the Desktop App when we don't have features like shared parking in the mobile app, or customisable dashboards in the Panel.

Frankly, if you're an organisation relying on an application that needs TAPI, you should be doing everything in your power to migrate to a modern, secure, platform. I think it's a bit rubbish to put the pressure on 3CX to support a protocol from the early 90s because you're too lazy to get your other internal systems upgraded. Same goes for the effort thats been spent on the headset stuff. WebHID worked perfectly for us with a large fleet of Jabra Engage headsets. Buy the good (basically anything except Sennheiser/EPOS lol) products, and you won't get issues!! 3CX shouldn't have to waste dev time on things that have such simple answers to rectify,

 

[N_G]

@sam.phillips phillps Thank you for the headsup on Tapi and WebHID! Shared parking and the configurable Panel, yes this is on our radar, just we have been caught up with other things. I promise by end of year!

 

[tropicsoftde]

Hi,
why can't I see the Tapi download?



My current version



That should be the Alpha 8, right?

Jan

 

[SweetAction]

That's the desktopapp or that's the webclient/PWA?

Needs to be the electron app

 

[tropicsoftde]

That's the desktopapp or that's the webclient/PWA?

Needs to be the electron app

Oooops, my mistake. I thought it would also work with the web client. Thanks for the info.
Jan