Most BBB integrations via their API is to load a new tab, redirect current tab or load the client in an iframe. What we did is quite conventional. In fact, the API is all about creating a meeting then loading the client. Jitsi’s api explicitly mentions iframe parent in their JS API.
Frankly, I don’t see the need for NC’s internal (or paid) signalling for webrtc (except maybe for the file-side chat which has a simple camera-only client – BBB does not have that yet). Another exception is for low-volume self-hosted NC instances … in which case you don’t need a full videoconf anyway. I don’t see a business-case for their high-performance server.
NOTES:
- We just made an improvement to Talk with BigBlueButton to show the BBB client full-width and hide all the sidebars when a call is launched (you can, of course reopen the right sidebar with the call info).
- There is an open-source nodejs signalling server here: https://gitlab.com/powerpaul17/nc_talk_backend – haven’t tried it and doc is skimpy