ekiga

[Anonymous]

I am thinking to swithc from Skype to Ekiga. I did check FreeBSD ports and there is 2.0 version but on the Ekiga site is 3.2. I am asking because I am talking with Windows user and they have the last version of Ekiga and I don't know how will works "new' with "old" and I don't want to spent time for compiling the old version if I will have a problem.
Thanks.

 

[Oko]

Ekiga is a client for SIP (Session Initiation Protocol) commonly used for VoIP. The protocol is described by RFC 3261

http://tools.ietf.org/html/rfc3261

Ekiga is to my knowledge somewhat correct implementation of a SIP client.
Ekiga versions on the another hand refer to idiotic GUI (which is changed from time to time) and user friendliness. By that they mean that you have to know less and less about topology of your network and firewall settings in order to configure Ekiga correctly.

Actually, I have to be honest and say that most users use Ekiga in two different ways. First way is as a SIP client. The second is as a SIP client for Ekiga SIP proxy server. Namely users who do not have fixed IP address commonly use SIP proxy servers as an intermediate step to talk to other users. Normally if you had fixed IP I could just talk to you from my pjsua SIP client as

m sip:your-ip-address

But your IP address is constantly (every couple days or weeks) changing which causes problems. One idiotic way to over come that is to assign
you an account on Ekiga server which has a fixed IP address. Your Ekiga program then acts as a client for SIP protocol but also as a client for Ekiga server. You can think of Ekiga server as a Phone Central which relays the phone conversations and help people find each other. Instead of
trying to locate your computer our conversation is relayed on Ekiga server which both yours and my computer can locate easily.


Skype does the same thing except that uses its own proprietary protocol instead of SIP protocol. In both cases your phone calls get recorded by Skype or Ekiga server and they are sold to various Intelligence organizations like CIA for instance who are paying for your "free phone calls".

A very popular SIP server until recently was Free World Dialup which is not free any more. You can Google for the list of free sip proxy server which is very small and changes often.

I am not sure that Ekiga proxy server is 100% implementation of SIP proxy server as I have not being able to use it with other SIP clients.
My favorite as I said earlier is PJSUA but you can find half a dozen of other SIP clients among FreeBSD ports.

The better way to talk to people is that you actually get fixed IP address or in the worst case scenario DyDNS account which will enable anybody on the internet to find you using just a regular DNS server and your domain name. In that case you can completely avoid using SIP proxy servers.Even further you do not even have to use SIP protocol. You can use just OpenSSH and audio server on your FreeBSD machine as described in this cool post on misc@openbsd

With the recent work done to the audio system on OpenBSD, a buddy of
mine and I figured it should be easy to setup two-way voice-chat
between two OpenBSD clients using nothing more than aucat(1) and
ssh(1). As we found out, it is both very easy and very usable! We
have telephone-quality chatting working with a <= 1 second delay in
the audio (after a few minutes of chatting, this is unnoticeable).

First, a hearty thanks to Jacob Meuser and the other OpenBSD
developers who have worked hard on this recently. Your efforts are
both noticed and greatly appreciated.

Second, I have a couple of questions...

1. We, the two users chatting (users neal and ryan) have ssh accounts
on each other's machines. To voice-chat with each other, what we did
boils down to the following:

ryan# aucat -l
ryan# aucat -o - | ssh <email removed>-machine aucat -i -

User neal would do the same, only to my (ryan's) machine.
When aucat is run in server-mode ('aucat -l') it creates a socket in
"/tmp/aucat-USERID/default" where USERID is the uid of the user who
ran the command (aucat -l). For another user (neal) to bind to this
socket, we had to make this socket available to the other user, namely

ryan# grep ryan /etc/passwd
(find ryan's uid, call it RYANSID)
ryan# grep neal /etc/passwd
(find neal's uid, call it NEALSID)
ryan# aucat -l
ryan# cd /tmp/
ryan# chmod 755 aucat-RYANSID
ryan# ln -s aucat-RYANSID aucat-NEALSID

Neal would do the same on his machine, only reversed.
Question: is it possible to run aucat(1) in such a way that the socket
it creates in 'global', such that other users can connect to it?
A quick perusing of the man/archives and the source says no... but I
may be missing something.

2. After doing the above, we would both simply do the following...

ryan# aucat -b 1 -r 11000 -o - | ssh <email removed>-machine aucat -b 1 -r 11000 -i -

With the above -b and -r flags, the audio was not choppy at all, quite
high-quality (equal to telephone quality), and overall very nice. We
had about a ~1 second delay in the audio, however (neal's in Chicago,
I'm in Cincinnati... we expected this), but could any of the
developers familiar with the audio system see a way to perhaps
decrease this delay? We played with other rates (-r values), but
below 11000 the delay was about the same, and the audio became
"deeper" and more "muted". Any other options, to aucat or \
perhaps
audioctl, that one could play with to reduce this?

Since I know that some of the people who talk to you are Windows users I would like to mention that all of above can be done on Cygwin i.e. on Windows.

 

[Anonymous]

Ekiga is a client for SIP (Session Initiation Protocol) commonly used for VoIP. The protocol is described by RFC 3261


Since I know that some of the people who talk to you are Windows users I would like to mention that all of above can be done on Cygwin i.e. on Windows.

Oko, thank you very much.

Should be any problems if I use Ekiga version 2 and the Windows user version 3. I think about video. A windows user has a webcam. I remember that was problem (looong time ago).