https://github.com/gonicus/bbb-clustersip

https://github.com/gonicus/bbb-clustersip

Last synced: 24 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/gonicus/bbb-clustersip
• Owner: gonicus
• Created: 2020-05-27T13:58:10.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2021-01-20T13:04:31.000Z (about 4 years ago)
• Last Synced: 2024-04-16T03:28:15.710Z (9 months ago)
• Language: Go
• Size: 187 KB
• Stars: 3
• Watchers: 6
• Forks: 4
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Problem

With BigBlueButton clusters (with Scalelite & Greenlight) one never knows on which Server the session will be processed.

This makes is quite difficult to route SIP-calls to the correct FreeSWITCH instance.

# Disclaimer

Please understand this project as a proof-of-concept. As there is no support for static voiceBridges within Greenlight the voiceBridge is not predictable at the moment. See security at the end of the readme as well.

# Approach

When a conference is created on a BBB-node, FreeSWITCH is instructed to send out a SIP REGISTER to a central SIP-Gateway for the cluster.

The registration contains the conference number (which is equivalvent to the voiceBridge of the room).

The SIP-Gateway run very little piece of dialplan to let the caller enter the desired conference number.

If the conference is already registered the caller gets routed to the corresponding FreeSWITCH.

If the conference is not registered the caller gets waited until the conference registers.

The SIP-Gateway gets connected to a SIP-Provider or to a PBX to be reachable from the PSTN.

The assigned phonenumber should be used for all your BBB-nodes as dialNumber.

![alt text][setup]

# Setup

* see folder astregbackend and ast_config for information on how to setup the SIP-Gateway.

* see folder fsconfregger for information on how to setup a BBB-node.

# Security

At the moment the is no authentication for the registrations.

So make sure to setup the ACL in pjsip.conf properly, so it machtes only your BBB-nodes and the Upstream.

Consider setting up a paket filter the SIP-Gateway as well.

[setup]: setup.png "Example setup"