Solved No webmeeting recordings since May

[CBX]

Hi,

the last time we used the webmeeting recording function successfully was in late April. After this we didn't really need it, so ignored the issue. However, even after the latest update of the 3CX-PBX we're still not getting any e-mails after meetings anymore. We tested this just yesterday unsuccessfully.

 

[StefanW]

Dear CBX,

it is ensured that your PBX is accessible from the WAN with a valid SSL cert?
This is needed to send to you the meeting report and download link for the recording!

 

[CBX]

Hi StefanW,

thanks for your response. To answer your question: Yes and no. For webmeetings to work we openend our firewall in so far that we gave a range of 3cx.net-related hosts access to our PBX. However, in generally the PBX is only accessible from the intranet and via VPN. Just now I made a test with unrestricted access to the PBX and the report actually arrived. So you're quite right that it is a firewall issue. Is there a documentation about what port and what hosts we need to make accessible to get these reports reliably? I've read the general 3CX firewall documentation but it isn't specific about what feature actually requires access to what port.

My hope was since the meetings themselves work, these reports should arrive just as well. In other words, I had hoped this was using something like a URL callback instead of requiring incoming connections.

 

[CBX]

Okay, after another test I found out, it's apparently TCP port 5001 that needs to be open for incoming connections which is already accessible for many 3CX-related hosts but obviously not enough. My concern is that this port 5001 is used for everything else as well i.e. the webclient. So, if we open this port to the world, we're relying solely on password security and the firewall restrictions are relatively meaningless.

 

[StefanW]

allow the NAT to your HTTPS port of 3CX from

• zone-a.3cx.net
• zone-b.3cx.net
• zone-c.3cx.net
• zone-d.3cx.net
• zone-e.3cx.net
• zone-f.3cx.net
• zone-i.3cx.net

 

[CBX]

Thank you very much for your help. Now it's working fine again.

 

[SteveITS]

allow the NAT to your HTTPS port of 3CX from

• zone-a.3cx.net
• zone-b.3cx.net
• zone-c.3cx.net
• zone-d.3cx.net
• zone-e.3cx.net
• zone-f.3cx.net
• zone-i.3cx.net

Not g and h? They resolve...

 

[StefanW]

no, currently i is the end...