Webmeeting creation issues

[bwitzig]

Good afternoon,

is anyone having issues with webmeeting creation? we are able to create meetings, however, when we try to join a newly created meeting. we get redirected to a 3cx troubleshooting page. I have tried restarting the 3cx system service. no change, I am able to use the option to make an "instant" webmeeting which works normally. previously created meetings work, but it seems that any newly created meeting I try to create fails.

I checked that our instance is mapped to our FQDN, and our SSL certificate has not expired. Any ideas?

 

[StefanW]

Dear @bwitzig,

this sound like you have no more a synchronization to the web meeting platform. As we made some change in v16 U5 RC, could you be so kind and update to this version and let us know if the issue still exists.

thx

 

[bwitzig]

Good morning,

than you for your reply.

I updated to the new V16 U5 RC last night (would be about 12 hours ago now) and have noticed no changes. new meetings are still being redirected to the troubleshooting page.

I know there are a couple MCU's listed as having issues, we are using the north american MCU's which currently are not showing a status error.

 

[nitrox]

hi, here is the same. We are not able to make webmeeting anymore and we are redirected to the troubleshoot page. I have tried to change MCU, to restart services, to restart pbx but nothing worked. I have no problem in others customer's pbxs because they are not on latest version (RC version) of course.
I have tried automatic MCU and different web meeting server in europe but it is still not working

 

[Juan Marriott]

hi, here is the same. We are not able to make webmeeting anymore and we are redirected to the troubleshoot page. I have tried to change MCU, to restart services, to restart pbx but nothing worked. I have no problem in others customer's pbxs because they are not on latest version (RC version) of course.
I have tried automatic MCU and different web meeting server in europe but it is still not working

Ohhh i have been busting my head, I thought it was my problem, I even installed another test server... it works on the test server but not production one.
did everything you guys did, updated everything, still not working. We can’t schedule meetings from web extension.
looks like my server can’t create the meeting on 3CX servers; firewall test are ok.

 

[bwitzig]

Ohhh i have been busting my head, I thought it was my problem, I even installed another test server... it works on the test server but not production one.
did everything you guys did, updated everything, still not working. We can’t schedule meetings from web extension.
looks like my server can’t create the meeting on 3CX servers; firewall test are ok.

Interestingly, reverting our VM to a previous version of 3cx from a backup does not seem to help with this issue. it's almost as if any new meetings are being "rejected" from the 3cx side. It's odd that the issue follows on our setup to a backup.

 

[Ronin]

Hello,

We have the exact same problem.
Restarting the 3cx system services does not seem to help either.
This happened after installing the latest RC version.

 

[Jeff Harlan]

Same issue here! Users on the war path...

 

[Saqqara]

Same issue here , running 16.0.5.610

After trying to refresh the license key, this is the email message I get

'The FQDN you configured at installation time is not linked to the license key which is currently activated. As a result, video conferences cannot work. Activate the license used at FQDN creation time or re-install and use your new license key and link it to a new FQDN.'

The FQDN has not changed, the only thing was I upgraded to V16 Update 5 RC

I am running Debian OS

 

[Curtis C]

Ok so I am not alone I am getting the exact same message as Saqqara except mine install is Windows. Updated to RC last Thursday or Friday

 

[bwitzig]

Interesting sidenote, I have a personal 3cx instance (I use for personal webmeetings not work) that I upgraded to the new RC that was not impacted.

The personal instance was recently created with the PBXexpress google cloud instance option. I'm curious if there is any pattern to what is causing this to fail in one location but work in another.

for those having issues, are you using a static IP or a dynamic IP address?

Our work setup which is not working has a dedicated static IP address, my personal GCE interface does not have a static ip.

 

[Curtis C]

Update
So I checked another Linux machine that we upgraded to RC also and that instance is fine.
FQDN for that machine is https://PBX.mi.3cx.us.xxxxx
And the Windows machine is https://PBX.3cx.us.xxx (no.mi) its was installed Feb.2011)
Dont know if this information helps in resoving the issue, but thought I would share

 

[bwitzig]

Good catch Curtis,

For those having issues, are you using the 3cx provided FQDN or did you use a custom one?

My "working" setup is using 3cx to manage the certificates and is using their provided url.
The not working setup is using our own "url" (the management/personal portal do not contain the .3cx.xxx)

Just trying to narrow down possibilities.

 

[nitrox]

i am using my own FQDN with our certificate of course.

 

[Juan Marriott]

Good catch Curtis,

For those having issues, are you using the 3cx provided FQDN or did you use a custom one?

My "working" setup is using 3cx to manage the certificates and is using their provided url.
The not working setup is using our own "url" (the management/personal portal do not contain the .3cx.xxx)

Just trying to narrow down possibilities.

Same here. another linux install with xxx.3cx.xxx works fine; our custom FQDN has these isues....

 

[Juan Marriott]

Interesting sidenote, I have a personal 3cx instance (I use for personal webmeetings not work) that I upgraded to the new RC that was not impacted.

The personal instance was recently created with the PBXexpress google cloud instance option. I'm curious if there is any pattern to what is causing this to fail in one location but work in another.

for those having issues, are you using a static IP or a dynamic IP address?

Our work setup which is not working has a dedicated static IP address, my personal GCE interface does not have a static ip.

I did the same; same results. pbxexpress working fine; custom FQDN cant schedule meetings...

 

[Juan Marriott]

I think we found something... @3cx comments??
custom FQDN!

 

[StefanW]

@Juan Marriott
@Curtis C
@bwitzig
@Jeff Harlan


Our WM Team could identify a situation, which is independent of v16 U5 RC build or customer's using their own FQDN. If a system (PBX) has disabled extensions, then the save of newly created extensions or scheduled meetings failed to be processed in our cloud platform. Apologies to all customers who had been affected by this. We are working on a solution on how to monitor and proactively inform OPS Teams about this going forward. Ops is rolling out the update right now and will be available for all customers within the next 30 minutes. You may restart the 3CX System Service for an immediate resynchronization or wait up to 8h until your install will perform this task on schedule.

@Saqqara

The mail you received is not related to the above and indicates a configuration mismatch between Key, FQDN and Portal. The reason I would like to evaluate with you. Plz check your PM so we can debug this with the 3CX WM Team.

 

[nitrox]

@Juan Marriott
@Curtis C
@bwitzig
@Jeff Harlan


Our WM Team could identify a situation, which is independent of v16 U5 RC build or customer's using their own FQDN. If a system (PBX) has disabled extensions, then the save of newly created extensions or scheduled meetings failed to be processed in our cloud platform. Apologies to all customers who had been affected by this. We are working on a solution on how to monitor and proactively inform OPS Teams about this going forward. Ops is rolling out the update right now and will be available for all customers within the next 30 minutes. You may restart the 3CX System Service for an immediate resynchronization or wait up to 8h until your install will perform this task on schedule.

I have tried and now it is working. Thank you.

 

[StefanW]

@nitrox thank you for the feedback!