Solved 3cx meeting report is sent out early

[antrill]

Hello,
we have multiple reports of meetings (planned and quick) which trigger the "3cx meeting report" email before the meeting ended.
Sometimes the email arrives 2 minutes into the meeting. It is confusing and would probably mean we would not get a full recording if that was enabled.

 

[StefanW]

This is super strange and I will have the team check this out.

 

[antrill]

In addition, if someone drops out of such a meeting after the email has been sent, he / she cannot rejoin and gets the message "Meeting has not started yet". It works after the initiator ended the meeting and re-started it. (In this case a quick meeting in the form FQDN/meet/username)

 

[antrill]

Let me know if I can help with additional information.

 

[LeonidasG_3CX]

Hi there,

We've tried reproducing what you've reported unsuccessfully. Reports are sent only after a meeting has ended and not before.

Can you reproduce 1 more time and provide steps on how you produced this issue? Also are you the administrator of your system? Are you restarting any PBX services during the meeting?

 

[antrill]

Hello,
I am the administrator of our system. No services were restarted.
I got reports about this behaviour from a couple of users, today I saw it myself. I attended a quick meeting started by someone else. I and one other user joined by FQDN/meet/username. After a few minutes, the initiator got the email report. A few minutes later, the 3rd person got disconnected and could not rejoin (also after more than 30 seconds). Only stopping the meeting completely (by the initiator) and restarting it (same link as it was a quick meeting), we could all connect again.
All 3 users were in the office (where the 3cx instance is also running). We have fiber internet 1Gbps symmetrical, MCU was in Amsterdam (about 20ms latency). Connection was excellent until the drop.

Other people reported this with planned meetings also. It never happened before the update to V18.

 

[LeonidasG_3CX]

Hi there,

I've sent you a PM

 

[LeonidasG_3CX]

Additionally, could you tell me what you see under the extension of the user who's meetings are being utilized?
Specifically under the Extension > Click2Talk/Click2Meet > Click2Meet Settings.

Which one of the two options is ticked there?

 

[antrill]

Hi,
regarding the last question: Click2Meet is enabled. (I tried turning it off, but then the user cannot start Webmeetings at all.) Friendly name is firstnamelastname. The URL is [3cxIP:5001/meet/friendlyname]
The second radio button is selected, "Requires you to connect to meeting first".
"Approve participants" is not selected.

Click2Talk is not enabled.

I think it might be better to have the FQDN here instead of the IP, but I see no way to change this here.
I will answer the other question via PM.

 

[Ronin]

Hello,

We are experiencing the same problems like @antrill .
1) Web meeting report is sometimes sent before the meeting ends.
(I have verbose logs from a specific meeting that I could send to an admin for review)
2) Also:

n addition, if someone drops out of such a meeting after the email has been sent, he / she cannot rejoin and gets the message "Meeting has not started yet". It works after the initiator ended the meeting and re-started it. (In this case a quick meeting in the form FQDN/meet/username)

 

[StefanW]

We have identified the cause and will ship with U2 an improvement.

The main cause is that your 3CX disconnects from the meeting server and fail to reconnect within 2 minutes of the meeting. The current implementation is very aggressive and marks the meeting at this moment as ended (even it is running itself fine, new joins however are not possible anymore). This timer will be relaxed in U1 beta 2. Effectively it is a protection but not a cure as the question remains why the system disconnect and cannot reconnect at this moment. The 3CX Meeting log will indicate more information.

 

[Ronin]

Hello @StefanW ,

Thank you for the quick answer.
I could provide a 3cx Meeting log if it's helpful.
Is there an estimation date of the U2 beta 2?

 

[StefanW]

Feel free to PM me the log, however log level must be set to verbose and you must be able after to replicate the case. I can forward this for you to ensure you are facing the same "case".

 

[StefanW]

Logs received and frwd to the Team

 

[StefanW]

the logs show a clear issue with the connection stability from your 3CX deployment to the service.
Can you share more about where 3CX is installed on (host) how it connects to the network (wifi, lan, docking station, USB dongle) and what you internet access is (dsl, fiber, let / firewall) please.

 

[Ronin]

Hello,

1) Deployment is on premise in VMWare from a 3cx ISO (Debian 10).
2) Connected with LAN.
3) Sophos UTM 9 firewall
4) Internet connection is Fiber with 300Mbit down / 120Mbit up.

Our problems are the exact same like Mr. @antrill.
Everything was working perfectly with v16 (never had any connectivity problems).
After upgrading to v18, we had web meeting problems since day 1.

 

[StefanW]

In v16 the meeting was running completely off the cloud, in v18 the meeting is running from your own installation. This provides processing of meeting data locally without 3CX having the need to know about who you invite etc. A big plus for your privacy.

I am not an expert in Sophos firewalls, a quick google showed me this
https://community.sophos.com/sophos...ons/119760/long-held-tcp-connections-dropping
https://community.sophos.com/utm-firewall/f/general-discussion/21386/set-tcp-connection-timeout

could you evaluate this?

PS v18 U1 B2 is coming out today which includes the local updates to the processing.
Please update to this version later and let me know.

 

[Ronin]

Hello,

I will check the web meetings again after the v18 U1 B2 and get back to you.

These are the timeouts from our Sophos firewall:

:/root # cc get packetfilter timeouts
{
          'ip_conntrack_generic_timeout' => 600,
          'ip_conntrack_icmp_timeout' => 30,
          'ip_conntrack_tcp_timeout_close' => 10,
          'ip_conntrack_tcp_timeout_close_wait' => 60,
          'ip_conntrack_tcp_timeout_established' => 86400,
          'ip_conntrack_tcp_timeout_fin_wait' => 120,
          'ip_conntrack_tcp_timeout_last_ack' => 30,
          'ip_conntrack_tcp_timeout_max_retrans' => 300,
          'ip_conntrack_tcp_timeout_syn_recv' => 60,
          'ip_conntrack_tcp_timeout_syn_sent' => 120,
          'ip_conntrack_tcp_timeout_time_wait' => 120,
          'ip_conntrack_udp_timeout' => 30,
          'ip_conntrack_udp_timeout_stream' => 180
        }

 

[Ronin]

Hello,

We have updated to the latest beta version and a user reported the same problem again:
A web meeting was started but the user could not join as before.
I have sent the logs to @StefanW

 

[Ronin]

Maybe the following issue is also relevant to the meeting e-mail coming earlier than what it's supposed to.
This is the syntax of a 3cx Meeting report:

Start: 2021-10-01T11:59:39Z
End: 2021-10-01T12:57:06Z
Duration: 00:57:27
Invited participants: 12

Also, the meeting ended at 13:10 and not at 12:57.