- Joined
- Jul 9, 2019
- Messages
- 6
- Reaction score
- 0
We’ve discovered that WebMeeting reports/recording links and invitations sent via “3CX (direct email)” are no longer being received. We usually send invitations via iCal and the recording feature isn’t used frequently, so I’m not sure when this started. The last time I'm aware of anyone receiving an email with a link to a recording was in late June. Email notifications from 3CX and voicemails still function as expected.
We are currently on 16.0.6.655, but also experienced this with 16.0.6.641. TCP 443 is accessible from the Internet and we have a valid SSL certificate. I’ve tried opening up every other port and disabling our IPS, AV, and Content Filter. There isn’t any relevant activity showing up in the 3CX System Service log as far as I can tell, whereas I can see when emails are being sent for things like voicemails. There are other forum posts with similar issues, but I believe the above covers the suggestions from those.
I see there are some potentially relevant items in the change log for the current alpha build:
Fixed issue related to WebMeeting links due to invalid data stored in the database
Fixed sending of conference events
Does anyone have other suggestions or happen to know if this is something being addressed in the next build?
We are currently on 16.0.6.655, but also experienced this with 16.0.6.641. TCP 443 is accessible from the Internet and we have a valid SSL certificate. I’ve tried opening up every other port and disabling our IPS, AV, and Content Filter. There isn’t any relevant activity showing up in the 3CX System Service log as far as I can tell, whereas I can see when emails are being sent for things like voicemails. There are other forum posts with similar issues, but I believe the above covers the suggestions from those.
I see there are some potentially relevant items in the change log for the current alpha build:
Fixed issue related to WebMeeting links due to invalid data stored in the database
Fixed sending of conference events
Does anyone have other suggestions or happen to know if this is something being addressed in the next build?