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

pidgin-sipe doesn't consistently find sip: URIs in Office365 Skype URIs #138

Closed
dlenski opened this issue Jan 19, 2017 · 4 comments
Closed

Comments

@dlenski
Copy link

dlenski commented Jan 19, 2017

I frequently use the "Join scheduled conference…" option to join scheduled meetings. (pidgin-sipe 1.21.1+sipe-0+201612161027~ubuntu16.04.1)

I'm typically getting URLs like this from Skype meeting invites: https://meet.lync.com/mycompany/some.body/5DEADBEEF (URL structure for Office365 Skype For Business).

Sometimes Pidgin parses these fine and handles them without a hitch, but sometimes I get an error:

Can't find a conference URI on this page:

https://meet.lync.com/mycompany/some.body/5DEADBEEF

or

Can't find a conference URI on this page:

https://webpoolbl20a23.infra.lync.com/Meet/?origurl=[base64 encoded version of original URL]

This is somewhat puzzling, because when I run curl and inspect the HTML/XML response body of the URI in question, I find numerous instances of the meet:sip: or conf:sip: URIs, e.g. meet:sip:some.body@mycompany.com;gruu;opaque=app:conf:focus:id:5DEADBEEF.

Is there a particular XML structure or tag that pidgin-sipe is looking for to find the sip: URI?

@simark
Copy link

simark commented Sep 19, 2017

I got the same error. I was able to join the meeting using the bottom fields, where organizer email is some.body@organization.com and the meeting ID 5DEADBEEF (according to your example).

@Zmegolaz
Copy link

Zmegolaz commented Oct 6, 2017

There is a compatibility part of the web page source which hints at adding "?UseCdn=false" to the end of the meeting URL, which seems to work.

@dlenski
Copy link
Author

dlenski commented Oct 6, 2017

Very good find, @Zmegolaz.

My guess is that Microsoft's CDN doesn't recognize Pidgin as the browser trying to connect to it (probably a strange User-Agent?), and sends it a CAPTCHA or some other DDOS-prevention redirect.

Adding ?UseCdn=false does seem to allow Pidgin to retrieve the meeting details in more cases for me…

@xhaakon
Copy link
Contributor

xhaakon commented Mar 7, 2018

Should be fixed by upstream commit and already in PPA.

@xhaakon xhaakon closed this as completed Mar 7, 2018
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

4 participants