Adding support for static SIP Pins

[SebastianAppDev]

Dear bigbluebutton/greenlight team,

I hope this message finds you well. I am writing to propose the introduction of a new feature in the upcoming version 3 of the greenlight platform.

Specifically, I would like to suggest the implementation of static SIP pins for conference participants. Currently, participants are assigned a dynamic SIP pin upon entering a conference, which changes each time they join a new session. While this system works well for many users, it can be inconvenient for others who may need to use the same SIP pin consistently or want to share the SIP pin before starting a meeting.

By introducing static SIP pins, we can provide a more flexible and reliable system for users who require a consistent pin for their meetings. This feature would allow users to set a unique, static SIP pin that they can use for all future conferences, making it easier for them to join meetings quickly and efficiently.

A similar request for this feature was made for v2. (#2739)

I believe that this feature would greatly enhance the user experience and functionality of greenlight, and I am excited to contribute to its development. Please let me know if you have any questions or concerns regarding this proposal and implementation.

Thank you for your time and consideration.

Best regards,

Sebastian

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
5.6% Duplication

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
2.4% Duplication

[ThomasAppDev]

We are really looking forward to this feature - can we do something to / what is needed for it to be merged?

[M-Schiborr]

We are very interested in this feature, are there any news if and when it will be merged?

[scouillard]

Hi,
Thank you so much for the work on Greenlight - we are also very excited for this feature!
However, we are focusing on stabilising Greenlight before we start working on improvements and new features.
We are getting close to where we want to be and we will be adding the dial-up feature as soon as possible.
Thank you again.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.3% Duplication on New Code

See analysis details on SonarCloud

[cwaidelich]

Hi,
is there anything I can do to help get this to v3?
Again, we are using this feature together with #5102 with 250 active users daily in a 1200 big company.

Let me know,
Chris

[SebastianAppDev]

@farhatahmad Do you have any idea why the rspec test fails? I cannot figure it out. On my machine the results are different.

Also if anyone else has an idea any help would be greatly appreciated.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[q16marvin]

that would be soooooo awesome, we need also static SIP Pins

[legrex]

@SebastianAppDev OT: I saw that you have a forked Greenlight on your profile, is that one you changed to support static pins? I'm shorty before migrating a BBB-Installation to a newer server but my users are crying for the static pin function but it seems that your implementation is still not merged to the main repo if i'm correct.
If i checkout your Greenlight Repo would this include the static pin changes? Thank you for your time!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[SebastianAppDev]

@legrex You probably want to create your own fork of Greenlight and then merge my PR and PR #5102. This will ensure you get the latest updates from main.

[sonarqubecloud]

Quality Gate passed

Issues
4 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[legrex]

@legrex You probably want to create your own fork of Greenlight and then merge my PR and PR #5102. This will ensure you get the latest updates from main.

Sadly i'm still struggling with it. I was hoping it would get finally reviewed and merged but my hopes are "gone"...

Forking and merging is the one thing i'm able to. But then i need to create a local docker image of greenlight, but then this it won't start because of a missing "application.css" and so on. I did it a lot in GL 2 but in GL 3 it seems a little bit more complicated. I guess i could point in docker-compose.yml manually to all your changed files, but then the database won't get the migration/entrys it needs. I'm a little lost.