Ubuntu
ekiga package

ekiga and LTSP

Asked by zekus on 2007-12-19

Ekiga cannot be used in a LTSP environment. I can just open one session of ekiga for all the terminals. Starting from the second one, it says "Error while starting the listener for the SIP protocol
You will not be able to recieve incoming SIP calls. Please check that no other program is already running on the port used by Ekiga".
Another session of ekiga is running for another user but in the same server!
How can I handle that? I cant find any solution on google till now.
Please help.

Question information

Language:: English Edit question

Status:: Solved

For:: Ubuntu ekiga Edit question

Assignee:: No assignee Edit question

Solved by:: Yannick Defais

Solved:: 2007-12-21

Last query:: 2007-12-21

Last reply:: 2007-12-19

Link existing bug

Revision history for this message

Yannick Defais (sevmek) said on 2007-12-19:

Hi,

http://wiki.ekiga.org/index.php/Internet_ports_used_by_Ekiga

Regards,
Yannick

Revision history for this message

zekus (zekus-one) said on 2007-12-19:

Thank you Yannick but, maybe, I've not been clear enough in my question. The point is that I cannot open ekiga in every terminal user session but I can open just one at time. Are you suggesting me to change the port for every ekiga session I need to start? Changing sip port in gconf affects the global application and does not resolve the problem.
Any other suggestion? I hope I have explained the situation better!

Revision history for this message

Yannick Defais (sevmek) said on 2007-12-19:

gconf can be set on a per user basis:

"Configuration Sources

GConf looks for each value in a series of storage locations called configuration sources. These are specified in a file called /etc/gconf/<version>/path. Each configuration source has a backend that knows how to read it - for now, this is always the "xml" backend, which stores data in XML files.

By default, GConf comes configured as follows:

   xml:readonly:/etc/gconf/gconf.xml.mandatory
   include "$(HOME)/.gconf.path"
   xml:readwrite:$(HOME)/.gconf
   xml:readonly:/etc/gconf/gconf.xml.defaults

If a value is set in the first source, which is read only, then users can't delete that value, and thus can't set a value of their own. These settings become mandatory for all users.

The "include" line allows users to insert their own configuration sources into the search path by creating a file in their home directory called .gconf.path.

The readwrite source ~/.gconf is where user settings are normally written.

The last source is where schemas are usually stored - see the next section. A different default schema source can be specified by creating the file /etc/gconf/schema-install-source; this file changes the return value of gconftool-2 --get-default-source, which causes applications and RPM/deb packages to install schemas to the new source.

In addition to $(HOME), the variable $(USER) can be used, and any variable $(ENV_FOO) will be replaced by the value of the environment variable FOO. So $(ENV_DISPLAY) might be handy, for example."

Source: http://www.gnome.org/projects/gconf/

The key for the listen port (SIP) is here on my system:
~/.gconf/apps/ekiga/protocols/sip/%gconf.xml
Use gconf-editor to edit keys...

Regards,
Yannick