Solved Recurring Conferences with v18? Possible? Workaround still actually working?

[nzr]

Hi,

used this "end date in the far future workaround" from https://www.3cx.com/community/threa...pears-after-some-time-weeks.80364/post-370046 for setting up recurring conferences until the v18 upgrade. Which worked okay. After the upgrade to v18 this seems to stop working and the conferences seem to be kicked after a week again despite of the future end date.

So big question is: How to setup recurring conferences with v18? Or is this feature still not implemented? I am confused as in https://www.3cx.com/blog/news/v18-video-conferencing/ it sounds like recurrance was even possible with v16???

• If you have recurring meetings, those will need to be re-created to take place on the V18 platform.

So, can someone confirm recurring meetings now possible? Maybe I lived under a rock for some time and did not get to know it?

Thanks a lot.

 

[StefanW]

Hi NZR,

the workaround is still valid as it was in v16.
However, when you migrated to v18 there was a transitional period where we supported v16 and v18 meetings.
With v16 VC gone, you might need to re-create meetings for this reason.

https://www.3cx.com/blog/news/v18-video-conferencing/

 

[nzr]

Hi NZR,

the workaround is still valid as it was in v16.
However, when you migrated to v18 there was a transitional period where we supported v16 and v18 meetings.
With v16 VC gone, you might need to re-create meetings for this reason.

https://www.3cx.com/blog/news/v18-video-conferencing/

Hi Stefan,

thanks for your help! Well, then I have to re-check my setup as there must be a mistake in our conference creation process, as we did setup them as completly new conferences, set an enddate like in 2040 or so and set the conferences to start without the organizer logged on. this worked exactly for "one" meeting - like one week (weekly meetings here).

We use outlook ICS method and deliver the invitations links to a shared Exchange calendar

Will recheck and test again - glad, that the workaround should still work!