3CX Webmeeting

[THCO]

Ive been on 3CX for about a year and everything is going smooth. Im starting to play with the web-meeting part of 3CX. I can copy the link and email it out and different users can connect. If I am in my web-meeting and I add a participant it fails. After looking at my firewall I see ip addresses trying to connect on port 5001. I have port 5001 blocked at my firewall because I do not want the management port open to the outside world.

Can anyone tell me why web-meeting needs port 5001. If I email the link out though my email client the participants can still connect with no issues.

 

[LeonidasG_3CX]

Everyone is suddenly very interested in WebMeeting.

You can block port 5001, that's fine. You'll need to allow communication to webmeeting.3cx.net on port 443. The whole WebMeeting platform is located there, not on your PBX. This is why a communication channel between the two is required in order for the platform to know how to setup your meeting.

-If you won't tell webmeeting.3cx.net who is invited to your meeting, how does it know who is invited and what his name is in order to show it in the meeting and what unique meeting URL key this user has?
-Another example is, if you don't tell webmeeting.3cx.net what your meeting title is, how can it set a title for your meeting?


There's load of examples i can make, but i hope the above give you the point on why the 5001 to webmeeting configuration is required.


Now in regards to the issue you're facing with the inviting of participants, having port 5001 open to webmeeting.3cx.net is a requirement and it wont work without because of the following:

1) You connect you a WebMeeting room. This means you are connected to webmeeting.3cx.net.
2) You invite someone via the in-built invite function inside the meeting room.
3) webmeeting.3cx.net tells your PBX via it's MyPhone port that it needs to send an e-mail invite to X user.
4) If the port is closed, we cant tell your PBX to send an invite to X user.

WebMeeting doesn't send any e-mails directly to any user. It instructs your PBX to send an e-mail. WebMeeting will not be responsible for sending your own e-mails, it makes more sense that you send them. This gives you more control over them.

I hope this answers your question.

 

[THCO]

Everyone is suddenly very interested in WebMeeting.

You can block port 5001, that's fine. You'll need to allow communication to webmeeting.3cx.net on port 443. The whole WebMeeting platform is located there, not on your PBX. This is why a communication channel between the two is required in order for the platform to know how to setup your meeting.

If you won't tell webmeeting.3cx.net who is invited to your meeting, how does it know who is invited and what his name is in order to show it in the participant pane;?

Another example is, if you don't tell webmeeting.3cx.net what your meeting title is, how can it set a title for your meeting?

There's load of examples i can make, but i hope the above give you the point on why the 5001 to webmeeting configuration is required.


Now in regards to the issue you're facing with the inviting of participants, having port 5001 open to webmeeting.3cx.net is a requirement and it wont work without because of the following:

1) You connect you a WebMeeting room. This means you are connected to webmeeting.3cx.net.
2) You invite someone via the in-built invite function inside the meeting room.
3) webmeeting.3cx.net tells your PBX via it's MyPhone port that it needs to send an e-mail invite to X user.
4) If the port is closed, the mail send fails. If the port is open, the mail send succeeds.

WebMeeting doesn't send any e-mails directly to any user. It instructs your PBX to send an e-mail. WebMeeting will not be responsible for sending your own e-mails, it makes more sense that you send them. This gives you more control over them.

I hope this answers your question.

Thanks for explaining this. does webmeeting.3cx.net have a static ip address or does it change?

 

[LeonidasG_3CX]

It's a static IP, however there can be instances where it may or may not change. This is why there are 3 IP's white-listed by default in your 3CX PBX's Blacklist.

It's suggested to whitelist the FQDN rather than the IP as some day the IP could change for some unexplainable reason.

 

[THCO]

It's a static IP, however there can be instances where it may or may not change. This is why there are 3 IP's white-listed by default in your 3CX PBX's Blacklist.

It's suggested to whitelist the FQDN rather than the IP as some day the IP could change for some unexplainable reason.

Thanks, I will make the changes to the firewall. Is there any plans to separate the management port from 5001 in the future?

 

[LeonidasG_3CX]

Thanks, I will make the changes to the firewall. Is there any plans to separate the management port from 5001 in the future?

Not something i know anything about unfortunately. I only know there's a thread on the Ideas forum for this. The more people that'll upvote it, the better.

 

[THCO]

Not something i know anything about unfortunately. I only know there's a thread on the Ideas forum for this. The more people that'll upvote it, the better.

Thank You