Solved 3CX WebMeeting API - "WebMeeting is disabled for this user"

[Kris G.]

I have been testing the web meeting API with a 3CX instance running version 18.0.237 and am running into issues on a single instance:



If I try on another instance it works perfectly fine - exactly as expected; however, on this one in particular it does not. I have confirmed the Click2Talk/Click2Meet" tabs are identical for each user

User 101 on server A with error:



User 400 on server B without error:

 

[Evolute IT]

I have been testing the web meeting API with a 3CX instance running version 18.0.237 and am running into issues on a single instance:

View attachment 25498

If I try on another instance it works perfectly fine - exactly as expected; however, on this one in particular it does not. I have confirmed the Click2Talk/Click2Meet" tabs are identical for each user

User 101 on server A with error:

View attachment 25501

User 400 on server B without error:

View attachment 25500

Set it as "requires you to connect to the meeting first" and it should work. That's a requirement for instant meetings (adhoc.)

 

[Kris G.]

Set it as "requires you to connect to the meeting first" and it should work. That's a requirement for instant meetings (adhoc.)

Interestingly enough after doing that, I still get "WebMeeting is disabled for this user"

 

[Evolute IT]

Interestingly enough after doing that, I still get "WebMeeting is disabled for this user"

Hmm interesting. Can you check the "approve participants" box and try again?

During our testing we did not experience this but our settings were as I specified above.

 

[Kris G.]

Same error, unfortunately.



I figured it out, though. An extension must have either a first or last name (or both) filled out, if both the first name and last name fields in the extension are blank, the error above is reported; however, as soon as I put anything in either field, it worked exactly as I expected it to.

 

[Evolute IT]

I figured it out, though. An extension must have either a first or last name (or both) filled out, if both the first name and last name fields in the extension are blank, the error above is reported; however, as soon as I put anything in either field, it worked exactly as I expected it to.

Interesting! Could potentially be a bug of the API. @VasilisV_3CX is this by design?

 

[Kris G.]

I filed a bug report via a ticket just to be sure, I’ll let you know what they say.

 

[Kris G.]

This appears to be by design:

“This is correct first name or last names are required in the extension as well as an email address to be able to schedule meetings.”

 

[Evolute IT]

This appears to be by design:

“This is correct first name or last names are required in the extension as well as an email address to be able to schedule meetings.”

Good to know!