We receive tens of messages on our dev-groups and private mailboxes every day. Without a commercial license, we only provide a best-effort support on opentelepresence group.
We're happy to help you to fix your issues but we'll not spend hours on them to understand what's wrong. If you want help, you must:
- Provide clear technical description of the issue.
- Change you telepresence.cfg to use INFO debug level. See here for more information.
- Attach the full logs to the message.
- Provide information about the SVN revisions (both Doubango and TelePresence). If the report is about building issues:
- Attach config.log files for both Doubango and TelePresence If the report is about video issues:
- Attach results from http://www.speedtest.net/ you should also:
- Provide the network (Wireshark) capture at the server-side
- Provide the client logs.
We'd recommend reading this thread.
I see "error while loading shared libraries: XXX.so.y: cannot open shared object file: No such file or directory" when I run the server. How can I fix this?
When a program is started the loader search for all dependencies (shared libraries) in a predefined list of folders. You're getting this error because the folder containing XXX.so.y is not in the list. To fix the issue, run:
# /!\IMPORTANT: change <path-to-XXX.so.y>
echo "<path-to-XXX.so.y>" >> /etc/ld.so.conf.d/telepresence.conf
ldconfig
To find <path-to-XXX.so.y>:
find / -name 'XXX.so.y'
I see "Remote party requesting DTLS-DTLS (UDP/TLS/RTP/SAVPF) but this option is not enabled". How can I fix this
DTLS-SRTP is required by some WebRTC implementations (e.g. Firefox). You MUST:
- use a new OpenSSL version with support for DTLS-SRTP as explained here. Linux almost always comes with OpenSSL pre-installed which means building and installing OpenSSL by yourself will most likely duplicate it.
- make sure you don't have more than one OpenSSL version installed (look for libssl).
- rebuild TelePresence and make sure the "CONGRATULATIONS" message says that you have DTLS-SRTP enabled.
- make sure you're using SSL certificates in your configuration (see here for more information). DTLS-SRTP requires at least a valid Public Key (could be self signed).