3CX WebMeeting Roadmap

Status
Not open for further replies.

LeonidasG_3CX

Product Manager
Staff member
Joined
Nov 19, 2008
Messages
2,174
Reaction score
658
Over the past few weeks home working and remote communications have become the norm for many. 3CX WebMeeting has become a driver supporting this type of communication. For many companies, this was already an integral way of keeping in touch with customers and co-workers, while others have needed to adapt to this form of communication. Certainly, th...
Continue reading the Original Blog Post.
 
thank you! :)
 
  • Like
Reactions: Nick W
Great! love the preview of whats comming...
The great work is noted.
 
Greet to see this roadmap and I appreciate your efforts to be transparent on the product trajectoy
 
Good roadmap, can I confirm if improved scheduling is on the cards? I.e. the ability to move/reschedule meetings?
 
Wonderful, thanks!

I remember you also were developing hosted version of Webmeeting running on the same server as customer's PBX, but I don't see any mention in the roadmap. Is that still being developed?
 
It's not (or at least it shouldn't be) on the same server as the customer's PBX. That wouldn't make any sense.
Yeah I meant that. Well, anyway I meant hosted webmeeting
 
Good roadmap, can I confirm if improved scheduling is on the cards? I.e. the ability to move/reschedule meetings?

Editing meetings. Yes this will eventually be added.


Wonderful, thanks!

I remember you also were developing hosted version of Webmeeting running on the same server as customer's PBX, but I don't see any mention in the roadmap. Is that still being developed?

Due to the recent events in the world, our development priorities have fully shifted towards providing the best possible user experience in WebMeeting. Hosted WebMeeting will come later and will of course contain these improvements.
 
Thanks for the update LeonidasG, honestly I am waiting for the on-premise MCU to get out of zoom...
By the way, great work you all are doing.
Day to day improvements are noted.
 
Last edited:
Current requests from our clients:
1. Ability to route audio from pc direct to webmeeting (We are trying to virturalize our on-boarding process)
2. enhancements to webmeetings, right now classrooms vs webmeeting seems to be an "all or nothing" for access for the clients. ideally, only the owner of the meeting would be able to apply settings such as muting audio etc.
 
Estou exigindo muito para usar o Webmeeting na empresa e tivermos surgido várias dúvidas, poderia esclarecer por favor?
  1. É possível colocar o LOGO Microcity do lado ou junto com a barra 3CX para webmeeting?
  2. O que pode afetar a reunião na web em termos de degradação e quedas em videoconferências?
  3. É possível configurar como padrão que apenas tenha uma pessoa como organizador, limitando como atividades do participante?
  4. É possível iniciar o padrão como conferências com 256k e não 1MB através do portal do meu PABX?
  5. É possível destacar a tela da pessoa que está falando (no Skype e Equipes e outras soluções que são padrão)?
  6. É possível avisar quando alguém entra na reunião?
 
Hi George,
have you had already a look at the following forum post?

https://www.3cx.com/community/threads/status-monitor-info.72678/

There, you see different FQDNs for different "Zones" and their MCUs.
Please also have a look here: https://www.3cx.com/community/threa...he-new-webmeeting-qos-fqdn.69780/#post-325440
hi Michael,
i saw this post yesterday and configured it accordingly, how ever 3CX should inform us this kind of major changes though an email update, right?
 
Editing meetings. Yes this will eventually added

When do you expect this coming productive? If we have to shift schedules with 10 or more participants it's very uncomfortable to delete and recreate meetings...
 
@cobaltit Actually the onboard MCU will run on the PBX. But no worries, it will not take much processor time because in this case the "de-centralized" architecture we chose will help a lot with the server not doing any encoding of the streams (just as in SIP this is offloaded to the client). And the smartphones are perfect to handle this and have these video functions natively on the chip itself. (in fact an average smartphone often outperforms a desktop machine on 3CX meetings)

The idea of an onboard MCU is that in our view video communications/meetings should not be a separate after thought process (or worse an entirely separate platform) but be integrated into the PBX - or communication system - as we prefer to call it nowadays. A PBX that cant handle video will be a relic of the past very soon. So we are building video/meeting capability into the PBX. Of course this will require bandwidth and some processing power (surprisingly little) but the cost is trivial these days and the productivity gains will be immense (and of course you can turn it off if you dont want it).

Now as to a time frame, i can say that the MCU is ready but we decided to focus on improving our meeting platform first, but when ready we can integrate it very easily and quickly. So think summer time but dont hold me to that date. Also keep in mind the MCU will be mainly for meetings of 4+ people and outside participants. The PBX from update 5 with the new iOS/Android apps can handle video itself in normal calls so for one to one video (and soon 3/4) you can just make a call and switch to video. No more"shall we use whatsapp or Zoom or whatever" - "whats your mobile, let me call you back" etc etc.

As for changing scheduled meetings, this is in fact an easy task but we just have to get it done given that we have some important things to do such as move to Debian 10. Again summer time. The reason we cant do it so quickly is because actually we store all customer data on the PBX and try to store as little as possible on the portal servers. This makes things temporarily more complex (easier once we have onboard MCU), but then again i believe the design thought is the correct one and one that customers will insist upon more and more in the future. This is the only way to guarantuee meeting data won't be copied...
 
Last edited:
@cobaltit Actually the onboard MCU will run on the PBX. But no worries, it will not take much processor time because in this case the "de-centralized" architecture we chose will help a lot with the server not doing any encoding of the streams (just as in SIP this is offloaded to the client). And the smartphones are perfect to handle this and have these video functions natively on the chip itself. (in fact an average smartphone often outperforms a desktop machine on 3CX meetings)

I'm curious, will the recording of meetings still occur server side, or will this be changed to occur on the local PBX side?
 
Status
Not open for further replies.

Forum statistics

Threads
111,995
Messages
590,194
Members
164,934
Latest member
bunthoeun.may