Language:
  • Francais
  • English

Skip to main content

  • Features
  • Screenshots
  • Getting started
  • Download
  • Contacts
  • Code review
  • Contribute
  • F.A.Q
  • Links
  • Commercial support

Welcome / F.A.Q

F.A.Q

Frequently Asked Questions

  • Q: Where can I have a ~/.linphonerc config file ?
    • A: You don't need a ~/.linphonerc config file: linphonec automatically creates one during the first startup. There are commands within linphonec to set various parameters. Only a few ones will require to modify manually the config file.
  • Q: Is there any windows port of linphone ?
    • A: Yes there is. It is under development so not all features are available. A setup.exe file can be downloaded from the download page.
  • Q: I have many compilation errors when cross-compiling for ARM-linux !
    • A: Cross compilation is not easy: follow the instructions given in the README.arm within linphone's source.
  • Q: I have audio problems during calls, what can I do ?
    • A: Especially on ARM-linux or old versions of linux, the audio devices are often managed with OSS drivers. Linphone, because it uses full-duplex audio and needs low-latency I/O, doesn't work very well with OSS drivers. You should prefer using ALSA drivers and choose the ALSA default device from the Sound Tab of the property box or using the 'soundcard' command of linphonec.
  • Q: Does linphone work behind firewalls ? What are the ports used ?
    • A: Yes it works in most cases. The simplest way to achieve this is to active STUN support from the configuration box. You 'll need to enter the name of a STUN server, for example stunserver.org. If your firewall or gateway does UDP masquerading, it should work without problem.
      You may want to restrict the open ports on the firewall: you need at least to preserve the SIP port (udp/5060), the audio rtp port (udp/7078) and the video rtp port (udp/9078). All those ports are configurable from linphone, but keeping 5060 for SIP is highly recommended.
    • Customising audio and video ports is recommended when using several linphone behind a same NAT so that they don't share same port numbers on the NAT. They must be even numbers.
  • Q: the video quality is awful ! I don't even recognize the person I'm talking with !
    • A: this is probably because the video stream is overflowing your internet connection bandwidth, resulting in truncated, dropped or late video packets which makes the image really awful. It is important that you tell linphone about the bandwidth limits (upload and download) of your internet connection. For that go to the 'codec' tab of the property box. Note that a minimum of 128 kbit/s are necessary in upload and download for video to work.

Right menu

News

Current developments and roadmap

Despite it's been a long time no new release was published, linphone's development is still running, with some new features and enhancement to come soon...


Linphone-2.0.0 is out

After months of development, linphone-2.0.0 is finally out. It is a major since linphone upgraded its SIP stack to eXosip2, bringing lots of improvements, new features, and increased interoperability.

It finally also solves the compilation issues with libosip-2.2.x series, and the recurrent warnings concerning the use of deprecated functions of ffmpeg.


Easy start of linphone on windows

This article explains how to pack linphone together with its config file inside a auto-expand file so that you can share it with friends that aren't familiar with IP telephony, proxies and so on.

An interesting use-case is to have it on a USB key you bring with you to use in an internet cafe.


Antisip & Belledonne Communications partnership for commercial support

Antisip and Belledonne Communications (company created by the author of linphone) had and have today a strong partnership in the development of mediastreamer2, the multimedia streaming engine of linphone.


Copyright 2007 Linphone.org - Hosting & Design Choup.net
Powered by eZ Publish™ Content Management System.