I have activated multitenancy on the LB
and have set up the following tenants:
lb01.example.org (LB01)
lb02.example.org (LB02)
I set up the following load balancer on the CGS: LB02. in thins Case "lb02.example.com".
To the first problem (Bug):
If I don't set the FSAPI_PASSWORD switch, I should be working with the load balancer secrets from the tenants.
However, this only works with the LOADBALANCER SECRET or with the FSAPI_PASSWORD, not with the secrets from the tenants.
Is this still a feature that will be added in later versions?
Here I only get a "[ff2f87c0-64b1-443a-880b-231c0dda35e8] Completed 401 Unauthorized in 0ms (ActiveRecord: 0.0ms | Allocations: 53)
" in the log files of the load balancer
Now for the strange behavior:
If I now go with a Frontend via LB02, I can also connect to the meeting that was set up via LB01 by telephone.
So the CGS is set up at the moment with a common key FSAPI_PASSWORD and dial-in points to the LB02. If I now set up a meeting on the Frontend via LB01, i can use the number and room number displayed there and connect to the meeting.
At this point, the LB02 knows something about the meetings of LB01 and can also connect me to them.
But shouldn't that happen? The tenants are separated from each other?
But, I also use the FSAPI_PASSWORD / LOADBALANCER_SECRET because the tenants passwords don't work and the LB responds with a 401.
For example, if I do a getmeetings via the API, then I only see the meetings via the
correct LB .
I expected her to say something like , Wrong conference number, please re-enter
Hi @Tecumtha - just so I understand correctly, the underlying issue is that you can't use the tenant's secret with the FS api? I don't believe that was implemented in the initial release
I have a strange behavior with Scalelite
My Setup:
Greenlight 3.0.2 (Frontend) Freeswitch Call Gateway Server 1.10.9 (CGS) Scalelite 1.5.1.1 (LB) BBB-Node 2.6.9 (BBB)
I have activated multitenancy on the LB and have set up the following tenants:
lb01.example.org (LB01) lb02.example.org (LB02)
I set up the following load balancer on the CGS: LB02. in thins Case "lb02.example.com".
To the first problem (Bug):
If I don't set the FSAPI_PASSWORD switch, I should be working with the load balancer secrets from the tenants.
However, this only works with the LOADBALANCER SECRET or with the FSAPI_PASSWORD, not with the secrets from the tenants.
Is this still a feature that will be added in later versions?
Here I only get a "[ff2f87c0-64b1-443a-880b-231c0dda35e8] Completed 401 Unauthorized in 0ms (ActiveRecord: 0.0ms | Allocations: 53) " in the log files of the load balancer
Now for the strange behavior:
If I now go with a Frontend via LB02, I can also connect to the meeting that was set up via LB01 by telephone.
So the CGS is set up at the moment with a common key FSAPI_PASSWORD and dial-in points to the LB02. If I now set up a meeting on the Frontend via LB01, i can use the number and room number displayed there and connect to the meeting.
At this point, the LB02 knows something about the meetings of LB01 and can also connect me to them.
But shouldn't that happen? The tenants are separated from each other? But, I also use the FSAPI_PASSWORD / LOADBALANCER_SECRET because the tenants passwords don't work and the LB responds with a 401.
For example, if I do a getmeetings via the API, then I only see the meetings via the correct LB . I expected her to say something like , Wrong conference number, please re-enter
*The last part was not translated.