Re: ekiga not creating sockets

[Derek Smithies]

Hi,

On Mon, 1 Jun 2009, Andrew Errington wrote:


On Mon, June 1, 2009 06:43, Derek Smithies wrote:


See - it is simpler to just install Skype and use it.


Actually, from what you are saying, it is simpler just to install Windows
and use it.


Not the right conclusion.
 In about 6 months, when ubuntu have been through another iteration, Pulse
 might have settled down to something that does sound ok

In the meantime, never Windows. There are other hassles with Windows that
I did not bother to mention -you already know of those hassles.

A Mac - well, it is unix under the hood, but, hmm,

Derek.
--
Derek Smithies Ph.D.
IndraNet Technologies Ltd.
Email: de...@indranet.co.nz
ph +64 3 365 6485
Web: http://www.indranet-technologies.com/

Re: ekiga not creating sockets

[Andrew Errington]

On Mon, June 1, 2009 06:43, Derek Smithies wrote:

> See - it is simpler to just install Skype and use it.

Actually, from what you are saying, it is simpler just to install Windows
and use it.

A

Re: ekiga not creating sockets

[Derek Smithies]

On Sun, 31 May 2009, Andrew Errington wrote:


On Sun, May 31, 2009 20:37, Volker Kuhlmann wrote:

On Sun 31 May 2009 16:16:17 NZST +1200, Andrew Errington wrote:




No.  He said that "It is only on linux that Skype gets hard to setup".  I
merely pointed out that it was trivially easy on Linux.  For me.


Ok, let me clarify.
There are going to be problems in installing software on your computer.
Going on the number of requests for help that are seen, and the what the 
requests are, one can predict the likely trouble spots.


On Linux::
  For Ekiga, you are likely to get
sound issues and network configuration.

  For Skype, you are likely to get sound issues.

See - it is simpler to just install Skype and use it. 
==

Andrew - you are lucky - sound worked for you first time..

Why is sound such an issue on linux?
Observe the Huge number of sound related posts in the ubuntu user forums.

Because, as Volker so rightly said,
 "Sound is a mess under Linux"

Further, there are no specks of dust||wooden beams here.
I detest and loath sound under linux.

There is the potential of hope with Pulse.
I recently wrote a pulse plugin for ptlib that works well. 
Multiple applications can simultaneously read/write to the same sound 
device, all at different rates&sampling sizes.



 -- 
Derek Smithies Ph.D.

IndraNet Technologies Ltd.
Email: de...@indranet.co.nz
ph +64 3 365 6485
Web: http://www.indranet-technologies.com/

Re: ekiga not creating sockets

[Andrew Errington]

On Sun, May 31, 2009 20:37, Volker Kuhlmann wrote:
> On Sun 31 May 2009 16:16:17 NZST +1200, Andrew Errington wrote:
>
>
>> Hmm.  apt-get install skype, and, err, that's it.
>>
>
> That is presumably not what Derek is talking about. If your sound driver
> or hardware doesn't work (because it's a mess under Linux), simply
> installing skype won't make skype work.

No.  He said that "It is only on linux that Skype gets hard to setup".  I
merely pointed out that it was trivially easy on Linux.  For me.

A

Re: ekiga not creating sockets

[Volker Kuhlmann]

On Sun 31 May 2009 16:16:17 NZST +1200, Andrew Errington wrote:

> Hmm.  apt-get install skype, and, err, that's it.

That is presumably not what Derek is talking about. If your sound driver
or hardware doesn't work (because it's a mess under Linux), simply
installing skype won't make skype work.

Volker

-- 
Volker Kuhlmann is list0570 with the domain in header
http://volker.dnsalias.net/ Please do not CC list postings to me.

Re: ekiga not creating sockets

[Barry Marchant]

Andrew Errington wrote:

On Sun, May 31, 2009 12:56, Derek Smithies wrote:


On Sun, 31 May 2009, Andrew Errington wrote:



On Sun, May 31, 2009 06:04, Derek Smithies wrote:



The most surefire way of fixing this?
Use skype.
Seriously, you can fiddle for hours getting this to work.



Except that Skype is proprietary and closed.  SIP is the Right Answer,
so it's worth persevering.


Yes, you are right in one sense..


Picture yourself in a hotel, far away from home, and keen to ring the
wife and family. A skype call will (well, most often) get through




Or a "telephone", or a "mobile phone".  I hear these are capable of
sending "txt msgs" too.



Yes, you can fiddle with sip like phones. However, in my jaundiced
experience, they are filled with gobbledygoodk like words that make them
hard to setup. Look at Barry's problems. He is not a voip developer, but
he is capable enough to do many linux like things. And he had trouble
getting Ekiga to work. Skype, on the other hand, is sufficiently easy to
setup that people with the minimum of computer skills can make voip calls.



Or you could use Gizmo, the (proprietary) gateway drug to SIP.

Drug here: www.gizmoproject.com
(about: http://en.wikipedia.org/wiki/Gizmo_Project)

Using Ekiga discussion:



It is only on linux that Skype gets hard to setup - mainly cause of the
"Welcome to the jungle phenomenon" talked about on slashdot recently.
Which was (effectively): linux sound is a mess.



Hmm.  apt-get install skype, and, err, that's it.

I have no more problems with software on my Linux systems than I do with
Windows.  Specks of sawdust and wooden beams come to mind.



Chris & I have tried skype. There is no problem with text, only a little 
with speech, but video is a different beast. Sometimes the camera will 
be activated but I get no picture, other times my image will be split in 
two only the top half respnding to movement. This split image is 
transmitted to Chris.


skype sometimes does not grab the xv port because another app has 
grabbed it. I can shut down every running app without freeing the port, 
when this happens the only option left is to reboot, even restarting X 
fails to cure the problem. I have found some aspects of skype ok, others 
decidedly flakey, and a call to skype and their offer of a reply within 
2 days or so was ignored.


Barry

Re: ekiga not creating sockets

[Andrew Errington]

On Sun, May 31, 2009 12:56, Derek Smithies wrote:
> On Sun, 31 May 2009, Andrew Errington wrote:
>
>> On Sun, May 31, 2009 06:04, Derek Smithies wrote:
>>
>>> The most surefire way of fixing this?
>>> Use skype.
>>> Seriously, you can fiddle for hours getting this to work.
>>>
>>
>> Except that Skype is proprietary and closed.  SIP is the Right Answer,
>> so it's worth persevering.
> Yes, you are right in one sense..
>
>
> Picture yourself in a hotel, far away from home, and keen to ring the
> wife and family. A skype call will (well, most often) get through


Or a "telephone", or a "mobile phone".  I hear these are capable of
sending "txt msgs" too.

> Yes, you can fiddle with sip like phones. However, in my jaundiced
> experience, they are filled with gobbledygoodk like words that make them
> hard to setup. Look at Barry's problems. He is not a voip developer, but
> he is capable enough to do many linux like things. And he had trouble
> getting Ekiga to work. Skype, on the other hand, is sufficiently easy to
> setup that people with the minimum of computer skills can make voip calls.

Or you could use Gizmo, the (proprietary) gateway drug to SIP.

Drug here: www.gizmoproject.com
(about: http://en.wikipedia.org/wiki/Gizmo_Project)

Using Ekiga discussion:


> It is only on linux that Skype gets hard to setup - mainly cause of the
> "Welcome to the jungle phenomenon" talked about on slashdot recently.
> Which was (effectively): linux sound is a mess.

Hmm.  apt-get install skype, and, err, that's it.

I have no more problems with software on my Linux systems than I do with
Windows.  Specks of sawdust and wooden beams come to mind.

A

Re: ekiga not creating sockets

[Derek Smithies]

On Sun, 31 May 2009, Andrew Errington wrote:

On Sun, May 31, 2009 06:04, Derek Smithies wrote:

The most surefire way of fixing this?
Use skype.
Seriously, you can fiddle for hours getting this to work.


Except that Skype is proprietary and closed.  SIP is the Right Answer, so
it's worth persevering.

Yes, you are right in one sense..

Picture yourself in a hotel, far away from home, and keen to ring the wife 
and family. A skype call will (well, most often) get through the various

firewalls in the way and get through. This has huge WAF.
That you can get through to home and talk increases the chance that you
will get her acceptance for the next trip away.

Yes, you can fiddle with sip like phones. However, in my jaundiced 
experience, they are filled with gobbledygoodk like words that
make them hard to setup. Look at Barry's problems. He is not a voip 
developer, but he is capable enough to do many linux like things.

And he had trouble getting Ekiga to work.
Skype, on the other hand, is sufficiently easy to setup that people with 
the minimum of computer skills can make voip calls.


It is only on linux that Skype gets hard to setup - mainly cause of the
"Welcome to the jungle phenomenon" talked about on slashdot recently.
 Which was (effectively): linux sound is a mess.

Derek.
--
Derek Smithies Ph.D.
IndraNet Technologies Ltd.
Email: de...@indranet.co.nz
ph +64 3 365 6485
Web: http://www.indranet-technologies.com/

Re: ekiga not creating sockets

[Andrew Errington]

On Sun, May 31, 2009 06:04, Derek Smithies wrote:
>


> The most surefire way of fixing this?
> Use skype.
> Seriously, you can fiddle for hours getting this to work.

Except that Skype is proprietary and closed.  SIP is the Right Answer, so
it's worth persevering.

A

Re: ekiga not creating sockets

[Barry Marchant]

Derek Smithies wrote:


On Sat, 30 May 2009, Barry Marchant wrote:


Thanks for the replies, it now works.

The problem was in the original configuration druid which set NAT to 
STUN when it was not required. I have just altered it to "None" and now 
get a test reply. now to test it with Chris.


Barry

Re: ekiga not creating sockets

[Derek Smithies]

On Sat, 30 May 2009, Barry Marchant wrote:

I have been trying for some days to get ekiga-2.0.12 to operate.  Iget
connected to the Ekiga OK but test calls to 5...@ekiga.net fail with an
error msg reading ' STUN could not create RTP/RTCP socket pair;'.

google reports plenty of instances of this but I have not found
a solution yet.

Ekiga usess the sip protocol to send & manage the voice stream. The actual
voice packets are encoded into UDP packets. The layout of the data in the
UDP packets is known as the RTP format.

The management of the media stream is handled with other UDP packets.
The management packets contain information about which codec is to be 
used, which ports for the media stream, what the name of the software 
application is etc.


So- the voice between you and the other person (caller and callee) goes in 
these RTP packets - which firewalls inevitably tend to block. To get the 
RTP through the firewalls, there are several approaches.
1)Use firewalls that understand SIP. These firewalls understand the 
management packets and so knows which udp ports to open to let the media 
stream go through. The media stream can be on any udp port number 
(well, any port above 1200 or so.) If you are using the firewall on 
your linux box, you might be able to turn on sip proxy in the firewall.
2)Extra code has been added to the Ekiga code base to get around this. 
There is STUN (simple traversal udp over nat) TURN (Transfer Udp with 
Relay Network). ICE was another, but cannot remember all it stands for.
3)Try adjusting your firewall. There is, I think, a firewall test utility 
in Ekiga. You might have a cone symmetric or something. Cannot remember 
all the details, but there is a firewall type that is really bad with voip

packets from sip&h323 applications.



error msg reading ' STUN could not create RTP/RTCP socket pair;'.

your error message is basically,
  "Ekiga tried to get audio through to the other end, but failed, cause
  (most likely) a firewall got in the way."

The most surefire way of fixing this?
 Use skype.
Seriously, you can fiddle for hours getting this to work.

To get skype to work, you only have to hassle your way through sound card 
issues.


To get ekiga to work, you have to hassle your way through sound card 
issues and firewall issues.


Derek.
 -- 
Derek Smithies Ph.D.

IndraNet Technologies Ltd.
Email: de...@indranet.co.nz
ph +64 3 365 6485
Web: http://www.indranet-technologies.com/

Re: ekiga not creating sockets

[Christopher Sawtell]

2009/5/30 Barry Marchant 

> Hi All,
>
> I have been trying for some days to get ekiga-2.0.12 to operate.  Iget
> connected to the Ekiga OK but test calls to 5...@ekiga.net fail with an
> error msg reading ' STUN could not create RTP/RTCP socket pair;'.
>
> google reports plenty of instances of this but I have not found
> asolution yet.
>
> Camera works OK, sound test in setup works ok. Running Mandriva 2008
> with  2.6.22.9-desktop-1mdv kernel & 512 M memory.
>
> Any ideas how to fix the problem welcome.


You need to check that all the ports required by ekiga are open and
forwarding correctly.

A possible way might be to use the netcat tool to test that you can connect
using the ports and protocols ekiga wants from your machine to another one
on the outside of your firewall and vice versa.

We could do this tomorrow afternoon.

-- 
Sincerely etc.
Christopher Sawtell

Re: ekiga not creating sockets

[Tim]

Barry Marchant wrote:
> I have been trying for some days to get ekiga-2.0.12 to operate.  Iget
> connected to the Ekiga OK but test calls to 5...@ekiga.net fail with an
> error msg reading ' STUN could not create RTP/RTCP socket pair;'.

> google reports plenty of instances of this but I have not found
> asolution yet.

> Camera works OK, sound test in setup works ok. Running Mandriva 2008
> with  2.6.22.9-desktop-1mdv kernel & 512 M memory.

> Any ideas how to fix the problem welcome.

Hey! No ideas, but I can at least tell you that ekiga-2.0.12 is working
well for me on Ubuntu 8.04 LTS. If there's any way I can help with
trouble shooting, please feel free to get in touch.

Tim
--
Timothy Musson FSF Associate Member
http://russianclub.wikidot.com/http://www.fsf.org/

ekiga not creating sockets

[Barry Marchant]

Hi All,

I have been trying for some days to get ekiga-2.0.12 to operate.  Iget
connected to the Ekiga OK but test calls to 5...@ekiga.net fail with an
error msg reading ' STUN could not create RTP/RTCP socket pair;'.

google reports plenty of instances of this but I have not found
asolution yet.

Camera works OK, sound test in setup works ok. Running Mandriva 2008
with  2.6.22.9-desktop-1mdv kernel & 512 M memory.

Any ideas how to fix the problem welcome.

TIA

Barry