- Joined
- Jun 2, 2014
- Messages
- 5,571
- Reaction score
- 1,981
It seems like you are on to something with the fragmentation, yes.Hello @NickD_3CX ,
I think I found the culprit in my case - I saw ICMP "need fragmentation" packets at a terminating gateway in Frankfurt directed to the problematic 3cx MCUs. I think some of them set "don't fragment" flags in their SSL server hello packets, which causes trouble with our smaller MTUs down the path due to encapsulation.
Will need to investigate further.One thing I noticed today:
Started a web meeting and looked at the connection stats page. It says at the top:
Server IP: 10.132.0.4:48025
(It's new to me to see a private IP here.)
And below:
Server-Info
Host: mcu-wmr-eu-00016.3cx.net
IP: 34.140.8.40
Land: BE Belgium
This IP 34.140.8.40 is not among those listed in the DNS record qos.3cx.net. Has there been another change to this mechanism?
Regarding this IP you found, indeed it is not currently in the qos.3cx.net resolution. Thisi s because a few days ago we made a mechanism that automatically scales our WebMeeting infrastructure. For the time being these new machines are not updated in time in the qos.3cx.net FQDN, but we are working to make it so that it is updated when these changes happen.