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

Timeout for viewing presentation in meeting #24

Closed
magnusolsson80 opened this issue Feb 17, 2016 · 13 comments
Closed

Timeout for viewing presentation in meeting #24

magnusolsson80 opened this issue Feb 17, 2016 · 13 comments

Comments

@magnusolsson80
Copy link

When attending a meeting, I get a dialogue box to accept a shared presentation. After accepting, I get the dialogue message "Couldn't create stream, Connection timed out".

OS: Ubuntu 16.04
PPA: https://launchpad.net/~sipe-collab/+archive/ubuntu/ppa

Attaching pidgin log file.

pidgin-log.txt

@xhaakon
Copy link
Contributor

xhaakon commented Mar 1, 2016

The initial exchange of connection candidates in the log looks sane, but unfortunately there isn't much more information as to why Pidgin wasn't able to find any workable connection route.

In past weeks I implemented changes that should eliminate some connectivity issues, so first please try updating your pidgin-sipe and libnice packages from the PPA. If you still experience problems, increase verbosity of your log so that it includes also debug traces from connection establishment subsystem:

G_MESSAGES_DEBUG=all NICE_DEBUG=all,libnice-nice-verbose pidgin --debug

@xhaakon xhaakon added the bug label Mar 1, 2016
@magnusolsson80
Copy link
Author

First of all, I want to thank you all for your great work. Here is the log with the above switches. I hope that you will find something. Just let me know if you need anything else.

pidgin-log.txt

@magnusolsson80
Copy link
Author

Question. The timeout, could it have something to do with remmina and proxy?

@xhaakon
Copy link
Contributor

xhaakon commented Mar 2, 2016

Timeout means Pidgin wasn't able to establish connection with the remote party within 30 seconds. Remmina shouldn't have much in common with that.

@xhaakon
Copy link
Contributor

xhaakon commented Mar 2, 2016

Unusual network configuration like with VPN or proxy may affect your connectivity. In that case it would be good if you could describe your setup in more detail.

@magnusolsson80
Copy link
Author

Yes, the problem seems to be just joining conferences. Desktop sharing between Lync/Skype works. So I think the network/proxy setup is the problem. This presents a problem. I have limited insight on how the network/proxy typology looks like against MS. So, I need guidance to exactly what you are looking for.

@magnusolsson80
Copy link
Author

Strange thing is happening. Someone can't share their desktop to me unless I have shared mine first to them. After the initial procedure above, desktop sharing works fine after that. Unfortunately, I was not able to get a log of what is happening. I will get one the next time it is happening.

I have updated to the latest in the ppa.

@xhaakon
Copy link
Contributor

xhaakon commented May 6, 2016

The latest PPA version of libnice produces more verbose debug output that could help us analyzing your problem. If you still experience these difficulties, you may try to get a log from Pidgin run with the following settings:

G_MESSAGES_DEBUG=all NICE_DEBUG=all,libnice-nice-verbose pidgin --debug

You'll need at least this version of libnice installed:

libnice10 0.1.14~sipe-0+201605051056~ubuntu16.04.1

@magnusolsson80
Copy link
Author

Sorry for the late response. I have been away on business. I see improvements. Now when accepting a presentation, remmina starts but crashes.

Here is the debug file.
pidgin_debug.txt

@xhaakon
Copy link
Contributor

xhaakon commented May 19, 2016

Here is the debug file.

Thanks for the log. I see from the file, and it is also your direct observation, that the original problem has gone away and Sipe now successfully connects to the meeting.

remmina starts but crashes.

As to the crash, we are aware of one such problem in remmina affecting some users: https://github.com/FreeRDP/Remmina/issues/747 (a short analysis in my post). We still don't have a solution for it but hope to find one soon with the help of Remmina developers.

To be sure you've hit the same bug, would it be possible for you to run remmina in gdb and get a stack trace of your crash by following the steps described on our wiki?

@xhaakon
Copy link
Contributor

xhaakon commented Jun 20, 2016

Closing this ticket as @magnusolsson80 reported the original problem has been solved.

@nowres
Copy link

nowres commented Mar 24, 2018

I still have the same issue using latest packages from ppa on Ubuntu 17.10

I get:
(10:15:34) sipe: MESSAGE >>>>>>>>>> SIP(0x1813cd0)
(10:15:39) g_log: Failed to GET http://10.42.2.148:0/: Not Found, retrying in 10 seconds

That repeats until saying:
(10:15:49) sipe: sipe_schedule_allocate timeouts count 7 after addition
(10:15:49) sipe: scheduling action timeout 30 seconds

That a prompt appears saying that the request has timed out
This happened for me only for receiving presentation but then happened also for audio in a meeting that was working just before I exited then joined

NOTE: Audio stopped working after I restarted pidgin in debug mode:
G_MESSAGES_DEBUG=all NICE_DEBUG=all,libnice-nice-verbose pidgin --debug

@ghost
Copy link

ghost commented May 1, 2019

I'm not sure if this is exactly the same issue, but it looks similar.

I can make calls and join meetings, but any attempt to connect to a presentation (More -> Show Presentation) causes Pidgin to segfault. Of course, if I run this under GDB, it doesn't segfault. It doesn't work, but it doesn't segfault -- it just doesn't open any windows.

  • Pidgin 2.13.0
  • Sipe 1.24.0-1
  • Linux 4.19.34-1-MANJARO Adium "sip:" contact add #1 SMP PREEMPT x86_64 GNU/Linux
  • WM: i3-gaps 4.16.1-1
  • Compositor: Compton 6.2-2

I just tried with strace and it didn't segfalt or work; I'll poke around some more and see if I can get any debugging information out of it.

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

No branches or pull requests

3 participants