Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 34

Thread: Real-time communications (RTC) out of GAFAM

  1. #21
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    2,559

    Default Re: Real-time communications (RTC) out of GAFAM

    Quote Originally Posted by MrNice View Post
    Started Linphone from CLI. No crash as long as I don't use the webcam.
    You have never mentioned which Desktop GUI you're using.

    Despite Linphone being a Gtk application (GNOME Desktop), it started and ran and coupled perfectly with a Laptop Webcam from a KDE Plasma 5 Desktop.

    Please realise that, graphical applications rely on the underlying communications bus of the GUI Desktop of choice, to connect with devices which the GUI Desktop "knows about" …
    If you run such applications from a CLI, unless you specify the communications bus and the port on that bus for the physical device on your system in the CLI command, the graphical application will not be able to connect to the physical device …

  2. #22

    Default Re: Real-time communications (RTC) out of GAFAM

    * I run MATE version 1.18
    * I first tried Linphone started from the GUI. As I got errors, I started it from CLI to get the errors messages.

    As I wrote, the webcam is working fine with VLC. Unfortunately I don't have another one.
    What could I do now to find the issue?

  3. #23
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,976
    Blog Entries
    14

    Default Re: Real-time communications (RTC) out of GAFAM

    Quote Originally Posted by MrNice View Post
    * I run MATE version 1.18
    * I first tried Linphone started from the GUI. As I got errors, I started it from CLI to get the errors messages.

    As I wrote, the webcam is working fine with VLC. Unfortunately I don't have another one.
    What could I do now to find the issue?
    Any 'extra' repos involved?
    Code:
    zypper lr -d
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  4. #24
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,368
    Blog Entries
    2

    Default Re: Real-time communications (RTC) out of GAFAM

    Quote Originally Posted by MrNice View Post
    <snip>
    When I start webcam, I get error message in the desktop CLI:
    Code:
    ** Message: Video used=0, video requested=1, automatically_accept=1
    libv4l2: error turning on stream: No space left on device
    Desktop webcam is not working.
    <snip>[/CODE]
    This suggests to me that your app isn't finding adequate disk space at some location.
    This might be because you're really running low on disk space or a machine mis-configuration or a coding error.

    Recommend you start by verifying you have a large amount of free space available, you can get a readout of your system with the following
    Code:
    df -h
    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  5. #25

    Default Re: Real-time communications (RTC) out of GAFAM

    As requested by you both
    Code:
    zypper lr -d
    Repository priorities are without effect. All enabled repositories share the same priority.
    
    #  | Alias                               | Name                        | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                                       | Service
    ---+-------------------------------------+-----------------------------+---------+-----------+---------+----------+--------+-------------------------------------------------------------------------------------------+--------
     1 | download.nvidia.com-leap            | nVidia Graphics Drivers     | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://download.nvidia.com/opensuse/leap/42.3                                            |        
     2 | download.opensuse.org-non-oss       | Main Repository (NON-OSS)   | Yes     | (r ) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/leap/42.3/repo/non-oss/                         |        
     3 | download.opensuse.org-non-oss_1     | Update Repository (Non-Oss) | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/42.3/non-oss/                                    |        
     4 | download.opensuse.org-oss           | Main Repository (OSS)       | Yes     | (r ) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/leap/42.3/repo/oss/                             |        
     5 | download.opensuse.org-oss_1         | Main Update Repository      | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/42.3/oss                                         |        
     6 | http-download.opensuse.org-0ffdd9f2 | devel:libraries:c_c++       | No      | ----      | ----    |   99     | rpm-md | http://download.opensuse.org/repositories/devel:/libraries:/c_c%2B%2B/openSUSE_Leap_42.3/ |        
     7 | http-download.opensuse.org-20e33d2c | home:ecsos:messenger:tox    | No      | ----      | ----    |   99     | rpm-md | http://download.opensuse.org/repositories/home:/ecsos:/messenger:/tox/openSUSE_Leap_42.3/ |        
     8 | http-download.opensuse.org-40a07015 | utilities                   | No      | ----      | ----    |   99     | rpm-md | http://download.opensuse.org/repositories/utilities/openSUSE_Leap_42.3/                   |        
     9 | http-download.opensuse.org-9bc5ce62 | multimedia:libs             | No      | ----      | ----    |   99     | rpm-md | http://download.opensuse.org/repositories/multimedia:/libs/openSUSE_Leap_42.3/            |        
    10 | http-download.opensuse.org-d90cad41 | home:qantas94heavy          | No      | ----      | ----    |   99     | rpm-md | http://download.opensuse.org/repositories/home:/qantas94heavy/openSUSE_Leap_42.3/         |        
    11 | http-download.opensuse.org-ebbf0662 | home:szotsaki               | No      | ----      | ----    |   99     | rpm-md | http://download.opensuse.org/repositories/home:/szotsaki/openSUSE_Leap_42.3/              |        
    12 | opensuse-guide.org-repo             | Libdvdcss Repository        | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://opensuse-guide.org/repo/openSUSE_Leap_42.3/                                        |        
    13 | packman.inode.at-suse               | Packman Repository          | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://packman.inode.at/suse/openSUSE_Leap_42.3/                                          |        
    
    df -h
    Filesystem      Size  Used Avail Use% Mounted on
    devtmpfs        3.9G     0  3.9G   0% /dev
    tmpfs           3.9G  344K  3.9G   1% /dev/shm
    tmpfs           3.9G  2.5M  3.9G   1% /run
    tmpfs           3.9G     0  3.9G   0% /sys/fs/cgroup
    /dev/sda3        40G  8.6G   29G  23% /
    tmpfs           3.9G     0  3.9G   0% /var/tmp
    /dev/sda1       156M  4.6M  152M   3% /boot/efi
    /dev/sda4       182G   26G  156G  14% /home
    /dev/sdb1       3.6T  680G  2.8T  20% /store
    tmpfs           794M   36K  794M   1% /run/user/1000

  6. #26
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,368
    Blog Entries
    2

    Default Re: Real-time communications (RTC) out of GAFAM

    Reading up on LinPhone Video a bit,
    It looks like Linphone is only a shell client that switches to OpenMCU-ru for video.

    Here is the website
    https://videoswitch.ru/eng.htm

    You can run OpenMCU standalone...
    Sparse documentation (Most docs last updated for openSUSE 13)
    https://wiki.videoswitch.ru/en/start

    You may want to verify old dependencies are installed
    (re https://wiki.videoswitch.ru/en/install/bin_linux)
    Code:
    zypper install freetype libjpeg8 libvpx1 libopus0
    Some personal comment...
    I'm amazed, this is the first time in... well over a decade since I've come across an app that uses the h.323 codec. It was the foundation for the Microsoft Messenger app then, and hasn't been used or developed since maybe the WindowsXP days. Instead of being built on the old consumer grade (ie completely open and unsecured) Messenger Directory Service, it appears to have been re-invented by OpenMCU on top of the SIP stack for directory services. I don't know if there are any drawbacks except that unless updated I question whether multimedia (video and audio) can be encrypted. Directory Services (ie User Accounts and everything related) is separate so <should> be encrypted (but needs verification). From what I can tell, it looks like an OpenMCU Server is still required and isn't pure P-P which is unsurprising and could be considered typical by many competitors. Closer inspection is required if the Server is required for its own directory services as I suspect and if it's required for your video connections (I suspect not required).

    You can install OpenMCU directly from the 42.3 OSS repo as follows, and might even be recommended to support Linphone
    Code:
    zypper in openmcu openmcu-codecs
    Once installed, there may be more installed documentation you should inspect.

    HTH,
    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  7. #27

    Default Re: Real-time communications (RTC) out of GAFAM

    @tsu2

    This is not the way I'd like to go. My first target is to have audio/video chats with people with some privacy and security..
    Even if I am ready to help debugging LinPhone with developers, I am not skilled enough to go where I can't see the end. Moreover, I don't want to jeopardise my Opensuse install.
    If you know LinPhone developers, let them know this thread.

    Now I'll try again Tox and Ring with the same 2 computers and at the end I'll try all with the person I'll call.

    Anyway, thank you for your help and involvement.

  8. #28
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    2,559

    Question Re: Real-time communications (RTC) out of GAFAM

    Quote Originally Posted by MrNice View Post
    My first target is to have audio/video chats with people with some privacy and security..
    If that's the case, and we're talking VoIP then, the big question is, "Who's providing the SIP?"

    My advice is, assuming that, your "normal" telephone contract is using VoIP and is via your ISP, "Trust your ISP." -- "Use their SIP" (If they allow it … ) «Assuming that, you're living in a reasonably democratic country … »

  9. #29

    Default Re: Real-time communications (RTC) out of GAFAM

    For you information

    I did a new Linphone test on another desktop hardware with the same Opensuse Leap 42.3 and the same Android tablet.
    In that case no crash in the desktop.
    Conclusion: The issue is due to the install in this particular desktop.
    As I'll use the tablet in the real call, this is good for now.

    Thank you for your help and advices.

  10. #30
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    2,559

    Cool Re: Real-time communications (RTC) out of GAFAM

    @MrNice:
    Please be aware that, Linphone also have a public VoIP SIP available within their services but:
    1. I have absolutely no idea where that SIP is physically located on the planet Earth.
    2. You can only connect to people who are also registered with the Linphone SIP.

    If you use the SIP of your VoIP (DSL ISP) provider then, you can simply dial any normal telephone number. But, be aware that, the SIP/UDP port 5060 is often used by the integrated VoIP client in the Router and therefore the Linphone instances have to be configured to use another SIP/UDP port such as 5061. You'll also have to configure your DSL Router to open the SIP/UDP port being used by Linphone.

    Alternatively you could check this list of VoIP providers: <https://en.wikipedia.org/wiki/List_of_VoIP_companies>.

    You could, possibly, configure the Linphone instances as VoIP telephones on your DSL Router assuming that, your VoIP service is part of your DSL connection. For example, on the AVM FRITZ!Box 7490, it's possible to setup a LAN/WLAN IP-Telephone to which a Linphone instance on that Router's LAN/WLAN can connect to by means of the Router's private domain name ("fritz.box"), empty proxy, username and password from the DSL router's setup.

Page 3 of 4 FirstFirst 1234 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •