Re: [Ekiga-list] Dropped call after approximately 30s, "Failed to receive ACK!"
- From: Jānis Rukšāns <thedogfarted gmail com>
- To: Ekiga mailing list <ekiga-list gnome org>
- Subject: Re: [Ekiga-list] Dropped call after approximately 30s, "Failed to receive ACK!"
- Date: Sun, 28 Nov 2010 17:53:03 +0200
Hi,
On Sat, Nov 27, 2010 at 9:34 AM, Felix Lechner <felix lechner gmail com> wrote:
> A short log of 'siproxd' is included below.
> Nov 25 07:41:54 buffalo-linkstation siproxd[1482]: plugin_logcall.c:120
> INFO:Incoming Call: +16172295005 10 176 159 3 -> 7476686228@
> Nov 25 07:41:56 buffalo-linkstation siproxd[1482]: plugin_logcall.c:120
> INFO:ACK Call: +16172295005 10 176 159 3 -> 7476686228 74 125 46 80
> Nov 25 07:41:56 buffalo-linkstation siproxd[1482]: plugin_logcall.c:120
> INFO:ACK Call: +16172295005 10 176 159 3 -> 7476686228 74 125 46 80
> Nov 25 07:42:28 buffalo-linkstation siproxd[1482]: plugin_logcall.c:120
> INFO:Ending Call: 7476686228 74 125 46 80 -> +16172295005 10 176 159 3
> Can anyone tell from the attached Ekiga log what is causing the dropped
> calls? Looks like the clue is in the line
> 2010/11/25 07:42:29.780 0:44.681 Housekeeper:0xb6cdbb70 SIP Failed to
> receive ACK!
> Opal then ends the call due to a temporary failure.
> Any help would be very much appreciated.
Judging from the logs, I suspect the siproxd is the point of failure -
Ekiga never reiceives an ACK to it's 200 OK and therefore terminates
the call after 32 seconds. A wireshark/tcpdump capture of SIP from
your gateway (Ekiga <-> siproxd and siproxd <-> provider) could shed
some light onto what's going on here.
Cheers
--
Ian
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]