Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support anonymous join fallback for conferences #175

Open
kvanopdorp opened this issue Mar 16, 2018 · 2 comments
Open

Support anonymous join fallback for conferences #175

kvanopdorp opened this issue Mar 16, 2018 · 2 comments

Comments

@kvanopdorp
Copy link

I sometimes have a need to join meetings as an external participant, i.e. participating in a meeting with an organization where I don't have an account or am not federated. According to this pretty detailed document, to do this the client must support anonymous join fallback.

https://blogs.technet.microsoft.com/scottstu/2015/04/03/anonymous-join-from-skype-for-business-and-lync-clients/

I'm seeing in the debug logs the expected 504 response code that the document notes but pidgin does not respond by trying an anonymous join process. The ms-diagnostics in my case does not come back with the noted 1017 code but rather 1034

ms-diagnostics: 1034;reason="Previous hop federated peer did not report diagnostic information"

If fallback is not simple, maybe a checkbox when joining a meeting to do so anonymously would be another option though a fallback mechanism would be cleaner.

I've started looking at the source code but it could take me a while to figure out any kind of patch. If anyone has any ideas before I do, I am happy to test.

@msbentley
Copy link

This would be great! My organisation has just moved to SfB and pidgin+SIPE works fine for me, but some of the external teams we work with have linux users, and they are currently out of luck...

@edbennett
Copy link

I'm also hitting this; if anonymous join can't be implemented, it would be an improvement if the error message generated indicated what the problem was, since the current message is not helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants