Ekiga sound from echo test missing: inbound RTP packets cannot get in.

[ealthuis]

Binary package hint: ekiga

In Intrepid all tests provided sound. I cannot say anything about actual phone calls. as I know nobody using ekiga.
Upgraded to Jaunty, and most functionality of Ekiga remains, except sound when either echo test or call back test is done.

On the call back test (<email address hidden>) my phone rings, but there is no subsequent sound from the call just accepted.

In the volume control all is set to default, and nothing is muted that I can see

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/ekiga
Package: ekiga 3.2.0-0ubuntu1
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: ekiga
Uname: Linux 2.6.28-11-generic i686

[Andreas Moog (ampelbein)]

Thanks for reporting, please check in Edit->Preferences->Audio-Devices that all devices are set correctly.

[ealthuis (ealthuis)]

I checked as suggested, all audio devices, Ringing, Output and Input are set to "Default (PTLIB/ALSA)"

I tried the other options, there was no change. In addition, any radio comes through OK through the speakers or the headset.

The sound card is Audigy 2 ZS [SB0353] (PTLIB/ALSA)

[ealthuis (ealthuis)]

I decided to try and make Ekiga work on an old Intrepid Ibex machine, after some fussing and a mistake or two on my part I got Ekiga to work. Tried both <email address hidden> and <email address hidden> and both worked perfectly.

On the Jaunty computers there is no sound after the callback rings.

[ealthuis (ealthuis)]

I just installed an update to Ekiga. Tried the callbacks again, and though the phone rings, there is no further sound, suggesting that the sound problem was not fixed in this update.

[ealthuis (ealthuis)]

My original problem is on a dual boot XP/Linux system. XP is running on one disk drive, Linux on another.

I installed Ekiga on the XP system and all sound tests work fine.

I also noted, that nobody is assigned to this problem???

If more info is required to solve this problem, ask and I will provide all I can.

[Yannick Defais (sevmek)]

Hi,

Try to use this setup: all audio devices, Ringing, Output and Input are set to "Default (PTLIB/ALSA)"

There is a volume control inside Ekiga (in the call panel, just below the video). Make sure you have the levels up.

Do you hear the welcome message (female voice) when calling 500 or nothing?

If this gives nothing, please attach a debug output using this command:
$ ekiga -d 4 2>output.txt
Then call the echo test and close Ekiga. Attach the file "output.txt" here.

Best regards,
Yannick

[ealthuis (ealthuis)]

Yannick Defais wrote:
> Hi,
>
> Try to use this setup: all audio devices, Ringing, Output and Input are
> set to "Default (PTLIB/ALSA)"
>
> There is a volume control inside Ekiga (in the call panel, just below
> the video). Make sure you have the levels up.
>
> Do you hear the welcome message (female voice) when calling 500 or
> nothing?
>
> If this gives nothing, please attach a debug output using this command:
> $ ekiga -d 4 2>output.txt
> Then call the echo test and close Ekiga. Attach the file "output.txt" here.
>
> Best regards,
> Yannick
>
>
Since the ekiga runs on another computer, dualboot with XP, I cannot
(because I do not know how) copy the file output.txt and attach it to
this email. the contents are obviously inconclusive, but here is what
is in the file:

2009/08/08 17:16:26.206 0:00.077 Version 3.2.0 by on Unix Linux
(2,6,28-14- generic -i686) with PTlib (v2.6.1)) at 2009/08/08 17:16:26.205
2009/08/08 17:16:26.206 0:00.077 Ekiga SVN revision : unknown
2009/08/08 17:16:26.208 0:00.079 Ekiga registered on D-Bus:
org.ekiga.Ekiga

At this point I must have hung the phone up
There was no sound at all
When I try 520, The phone rings but no other sound is heard.

on a computer with 8.04, both 500 and 520 work

On XP, (this computer runs XP from a 160GB disk and Linux from a second
40GB disk) Ekiga 500 and 520 calls work to the extent, that I hear the
female voice but not what I say in response.

That may be caused by my mike.

Hope all this helps.

EA

[Yannick Defais (sevmek)]

Hi,

Thank you for your answer.

Unfortunately I still need the full output.txt file. If you open a terminal, it should point to your home folder by default. (You can access this file using nautilus -the default file manger-, press F9 key and select the top entry, named after your nickname in ubuntu).
Then go to the URL of this bug:
https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/367478
At the bottom you have an entry field "Attachment" to attach the file here.

Best regards,
Yannick

[ealthuis (ealthuis)]

Good morning,
Thanks for the help. I have attached the output.txt file as requested

[Yannick Defais (sevmek)]

Thank you.

Is that the file from Ubuntu Jaunty 9.04 using this command "ekiga -d 4 2>output.txt"?

It seems pretty much incomplete...

Please remove the old output.txt and try again. From what I can see from the previous one, you should not be able to even see the Graphic User Interface...

Best regards,
Yannick

[Yannick Defais (sevmek)]

Or maybe you did not closed Ekiga first: Ekiga has an icon in the systray in the form of a big green dot, right click on it and choose quit.

Erase the file output.txt (You can access this file using nautilus -the default file manger-, press F9 key and select the top entry, named after your nickname in ubuntu)

Then, start ekiga using the command in a terminal:
ekiga -d 4 2>output.txt
Wait a bit for the registration to succeed, then call the echo test and close Ekiga. Attach the file "output.txt" here.

Best regards,
Yannick

[ealthuis (ealthuis)]

Yannick Defais wrote:
> Thank you.
>
> Is that the file from Ubuntu Jaunty 9.04 using this command "ekiga -d 4
> 2>output.txt"?
>
> It seems pretty much incomplete...
>
> Please remove the old output.txt and try again. From what I can see from
> the previous one, you should not be able to even see the Graphic User
> Interface...
>
> Best regards,
> Yannick
>
>
Yes it was the complete file after I terminated the call, some 15
seconds into the callback. I can see and use the GUI.

By the way the same problem exists on this computer which has an Asus
P5L-MX motherboard with integrated sound. The output.txt showed similar
data when I ran the test here.

I will try again and let it run longer before I close Ekiga and the
Terminal.

Emanuel

[ealthuis (ealthuis)]

Yannick Defais wrote:
> Or maybe you did not closed Ekiga first: Ekiga has an icon in the
> systray in the form of a big green dot, right click on it and choose
> quit.
>
> Erase the file output.txt (You can access this file using nautilus -the
> default file manger-, press F9 key and select the top entry, named after
> your nickname in ubuntu)
>
> Then, start ekiga using the command in a terminal:
> ekiga -d 4 2>output.txt
> Wait a bit for the registration to succeed, then call the echo test and close Ekiga. Attach the file "output.txt" here.
>
> Best regards,
> Yannick
>
>
Right, that was the file problem, I will send you the new file right away.

Emanuel

[ealthuis (ealthuis)]

This is the new file.

EA

[Yannick Defais (sevmek)]

The issue is Ekiga did not received any packets from the internet. It is interesting as, correct me if I'm wrong, the same computer using Windows with Ekiga do work.

Relevant line in the output:
packetsReceived = 0

The RTP session for audio was:
RTP_UDP Session 1, SetRemoteSocketInfo: data channel, new=86.64.162.35:18554, local=65.38.46.60:5064-5065, remote=0.0.0.0:0-0

IMHO, it is a network issue not an issue with your sound card.

It will be very nice from you if you could give me the output from Windows, I'll be able to compare them.

Under windows, run ekiga with the following arguments
ekiga.exe -d 5 1>x 2>x
It will produce 2 files: stdout.txt and stderr.txt in the same directory. Please attach both of them here.

Best regards,
Yannick

[ealthuis (ealthuis)]

Yannick Defais wrote:
> The issue is Ekiga did not received any packets from the internet. It is
> interesting as, correct me if I'm wrong, the same computer using Windows
> with Ekiga do work.
>
> Relevant line in the output:
> packetsReceived = 0
>
> The RTP session for audio was:
> RTP_UDP Session 1, SetRemoteSocketInfo: data channel, new=86.64.162.35:18554, local=65.38.46.60:5064-5065, remote=0.0.0.0:0-0
>
> IMHO, it is a network issue not an issue with your sound card.
>
> It will be very nice from you if you could give me the output from
> Windows, I'll be able to compare them.
>
> Under windows, run ekiga with the following arguments
> ekiga.exe -d 5 1>x 2>x
> It will produce 2 files: stdout.txt and stderr.txt in the same directory. Please attach both of them here.
>
> Best regards,
> Yannick
>
>
I will of course do as you ask. I must reiterate however, that with
Linux 8.04 on a very old computer Ekiga does work. It is one of four
attached to the same router a D-Link DI-824VUP

Regards,
Emanuel

[ealthuis (ealthuis)]

Yannick Defais wrote:
> The issue is Ekiga did not received any packets from the internet. It is
> interesting as, correct me if I'm wrong, the same computer using Windows
> with Ekiga do work.
>
> Relevant line in the output:
> packetsReceived = 0
>
> The RTP session for audio was:
> RTP_UDP Session 1, SetRemoteSocketInfo: data channel, new=86.64.162.35:18554, local=65.38.46.60:5064-5065, remote=0.0.0.0:0-0
>
> IMHO, it is a network issue not an issue with your sound card.
>
> It will be very nice from you if you could give me the output from
> Windows, I'll be able to compare them.
>
> Under windows, run ekiga with the following arguments
> ekiga.exe -d 5 1>x 2>x
> It will produce 2 files: stdout.txt and stderr.txt in the same directory. Please attach both of them here.
>
> Best regards,
> Yannick
>
>
Hi again,

I am not having much luck creating the above mentioned files, when I
start ekiga, I get a dos type black log screen as well as the ekiga
GUI. I then double click on the echo test, and almost immediately the
lady starts telling me the reason for the test. When I finally get a
chance to speak, the words I say are _not _echoed. I hang up, then
close the GUI and try to close the Dos style screen but I cannot do
that. it finally ends with XP's end now question.

I cannot find the two files you asked for, unfortunately.

sorry about that,

Emanuel

[Yannick Defais (sevmek)]

Thank you for your efforts.

As you behind a NAT, did you setup some port forwarding for SIP? Or you're using the standard configuration of the router?

Can you check if your router has support for SIP built-in? Usually the name for it is "Application-level gateway" or ALG; http://en.wikipedia.org/wiki/Application-level_gateway

If the router has AGL for SIP please disable it.

If you have already port forwarding setup, make sure it follow the range 5000 to 5100 in UDP.

Best regards,
Yannick

[ealthuis (ealthuis)]

Yannick Defais wrote:
> Thank you for your efforts.
>
> As you behind a NAT, did you setup some port forwarding for SIP? Or
> you're using the standard configuration of the router?
>
> Can you check if your router has support for SIP built-in? Usually the
> name for it is "Application-level gateway" or ALG;
> http://en.wikipedia.org/wiki/Application-level_gateway
>
> If the router has AGL for SIP please disable it.
>
> If you have already port forwarding setup, make sure it follow the range
> 5000 to 5100 in UDP.
>
> Best regards,
> Yannick
>
> ** Summary changed:
>
> - Ekiga sound from echo test missing
> + Ekiga sound from echo test missing: inbound RTP packets cannot get in.
>
> ** Changed in: ekiga (Ubuntu)
> Status: Incomplete => Confirmed
>
>
As far as I know I am using the standard configuration,
There is no indication that the router supports or not any sip:
activity. I bought it on 31 Jan 2006.

Is not port forwarding a Firewall service?
It has not been set up anywhere.

These are the results of all tests:

Linux 8.04 responds to calls with female voice, calls back when asked,
but does not echo any voice.
Linux 9.04 calls out, but no sound results when connected. Call back
rings the phone but no other sound.
Windows XP responds to calls with female voice and calls back ringing
the phone, speaks the message but my voice is not echoed.

I am grateful for your help and patience with me, I am somewhat computer
literate, but new with Linux., and command language is very new to me, I
need all the assistance available.

I will continue to try to get you the Windows reports.

Regards,

Emanuel

[Yannick Defais (sevmek)]

Hi,

It is most probably an issue with the router preventing some ports to work.

I suggest you to try this if available on your router:
http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#Symmetric_NAT:_Dynamic_navigation_of_NAT_routers

Or do port forwarding to one computer of the network:
http://wiki.ekiga.org/index.php/Enable_port_forwarding_manually

Best regards,
Yannick

[ealthuis (ealthuis)]

Yannick Defais wrote:
> Hi,
>
> It is most probably an issue with the router preventing some ports to
> work.
>
> I suggest you to try this if available on your router:
> http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#Symmetric_NAT:_Dynamic_navigation_of_NAT_routers
>
> Or do port forwarding to one computer of the network:
> http://wiki.ekiga.org/index.php/Enable_port_forwarding_manually
>
> Best regards,
> Yannick
>
>
Thank you for your help so far, I do not believe this problem to be
solved. I will try all of the suggestions and see what happens. I will
keep you apprised of any developments.

I would like to reiterate, that Ekiga on the dual boot system with Linux
8.10 worked as expected, I would always hear myself talk in every echo
test I did. No physical changes have been made to my computer systems,
except for trading the CRT monitors for LCD monitors.

My own test of the router will be this: I will connect the dual boot
computer directly to the modem and try again... see what happens.

So for now, until next time we meet,

Emanuel

[kapetr (kapetr)]

Hello,

I had also problems with Ekiga behind NAT and FWs.

I'm connected to Internet via ADSL router (with NAT and SPI firewall):

To get echo working, I had on my Ubuntu 9.10 - Ekiga 3.2.5/6 to do:

1. on my ADSL router (ZyXEL 660HW)
- enable in NAT port forwarding (ports 5000-5100)
- in firewall add rule WAN2LAN to allow these ports

2. running Ubuntu FW "ufw" don't make problems ( I have to see why !!!)

3. In Ekiga Preferences
- must be enabled network detection (also not checked)
- in audio codec disabled PCMU and enabled PCMA (don't ask me why)

I hope it will help someone :-)

--kapetr

[Yannick Defais (sevmek)]

Hi,

We have a patch wich modify the network part of the audio and video streams when behind a NAT. As this is the case here (after a quick look), this patch might solve the issue. Would you be kind enough to test it?

Get Ekiga 3.2.6 for Karmic with this patch here (same code as Ekiga 3.2.6 with just the patch which is a small one):
https://launchpad.net/~sevmek/+archive/ppa

Best regards,
Yannick

[ealthuis (ealthuis)]

I installed the patch as indicated without errors, checked help > about : Ekiga 3.2.6

Ran Ekiga, used the self test <email address hidden>. Result: call was made and immediately disconnected with message "Call completed"

Ditto for <email address hidden>, no return call was made

Tried both on another computer with the same results, this was with Ekiga 3.2.5

Seems to me that there is little sense in pressing on with this, as in Ubuntu 10.04 Ekiga is not even included. In addition I have never been able to make a call.

 All of the tests worked for me on a computer still running Hardy Heron.

Emanuel Althuis

[Yannick Defais (sevmek)]

Hi,

Thank you althuis for the testing. As of now, 4 people reported an improvement(1) (means they were able to connect to <email address hidden>), while you still have an issue.

Would you be kind enough to provide a new debug ouput using the patched version just like you did in comment #10?

Best regards,
Yannick

(1)
https://bugs.launchpad.net/bugs/517580
https://bugs.launchpad.net/bugs/534618
https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/332543
+another one directly to our mailing list:
http://mail.gnome.org/archives/ekiga-list/2010-March/msg00135.html

[ealthuis (ealthuis)]

I did the <email address hidden>, as well as <email address hidden>, I also tried to call myself. The results were:one message "online" and "Call completed" and finally "user not available".

The output file is attached.

Emanuel