Created attachment 33243 [details] GST_DEBUG I am trying to establish voice/video session in pidgin behind address and port-restricted nat (freebsd+pf) with upnp. So, only voice chat works carefully, and problem starts when video or voice/video chat is called. I had checked that libnice makes port-redirection using upnp. Then i ran pidgin with NICE_DEBUG=all and -d option. I found, that (Pidgin:3703): libnice-DEBUG: Agent 0x883df30 : changing conncheck state to COMPLETED. (10:19:00) media: farsight-component-state-changed: component: 1 state: FAILED (10:19:00) media: farsight-error: 108: Could not establish connection (10:19:00) media: farsight-component-state-changed: component: 2 state: FAILED Then, i tried to run pidgin with GST_DEBUG=*:5 and got a bunch of log. Next i ran make check, to determine that farsight works properly. And got 4 of 11 tests failed. So, i'm attaching two logs, and may do all checks you want on my side.
Created attachment 33244 [details] make check
Can you go to tests/checks and run GST_CHECKS=test_nicetransmitter_with_filter make transmitter/nice.gdb and get the backtrace once it crashes. The fsrtpcodecs tests failures should have been fixed in git master. And the msn one is because you're missing the mimic plugin from gst-plugins-bad. Can you attach the whole log from running pidgin with NICE_DEBUG=all too ?
(In reply to comment #2) > Can you go to tests/checks and run > GST_CHECKS=test_nicetransmitter_with_filter make transmitter/nice.gdb gdb-logs > and get the backtrace once it crashes. The fsrtpcodecs tests failures should > have been fixed in git master. And the msn one is because you're missing the > mimic plugin from gst-plugins-bad. ok > Can you attach the whole log from running pidgin with NICE_DEBUG=all too ? > pidgin-debug.log
Created attachment 33259 [details] pidgin-debug.log
Created attachment 33260 [details] gdb-logs seems, that there is bug in threading test sometimes works, sometimes not, and often hangs gdb
Don't worry about the crash, it's a known bug in gobject (property notications are not thread-safe...). The connectivity problem sounds like a libnice problem, so forwarding it that way.
(In reply to comment #6) > Don't worry about the crash, it's a known bug in gobject (property notications > are not thread-safe...). seems to be truth, because not only transmitter/nice fails with that error > > The connectivity problem sounds like a libnice problem, so forwarding it that > way. maybe, but 'make check' in libnice sources executes correctly so, what next?
In the log I see : "Integrity check failed" and "Incorrectly multiplexed STUN message ignored." Could you provide us with a wireshark dump *and* a NICE_DEBUG=all log of the same session as the wireshark dump ? This way I can figure out why the STUN message is wrong... Also, what are you using on the other side? is it also pidgin with libnice ?
(In reply to comment #8) > In the log I see : > "Integrity check failed" and > "Incorrectly multiplexed STUN message ignored." > Could you provide us with a wireshark dump *and* a NICE_DEBUG=all log of the > same session as the wireshark dump ? This way I can figure out why the STUN > message is wrong... logs.tar.bz2 > Also, what are you using on the other side? is it also pidgin with libnice ? > this time, on other side is echo bot, using Telepathy components installed are: libgstfarsight0.10-0-0.0.17-2 libtelepathy-farsight0-0.0.13-1 libtelepathy-glib0-0.10.0-1 python-farsight-0.0.17-2 python-telepathy-0.15.15-1 python-tpfarsight-0.0.13-1 telepathy-gabble-0.8.9-1 but the same situation is with pidgin+libnice on other side. i tested it before
Created attachment 33323 [details] wireshark and pidgin logs wireshark log, pidgin log
Today i installed ubuntu server with iptables NAT. Now video chats working properly. Seems, that problem caused by freebsd's pf.
I assume that your pf configuration was too restrictive.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.