[Ekiga-list] Trouble setting up Ekiga for BroadVoice

Sick Twist thesicktwist at hotmail.com
Tue Sep 26 07:22:52 UTC 2006

>From: Jan Schampera <jan.schampera at web.de>
>Reply-To: Ekiga mailing list <ekiga-list at gnome.org>
>To: ekiga-list at gnome.org
>Subject: Re: [Ekiga-list] Trouble setting up Ekiga for BroadVoice
>Date: Mon, 25 Sep 2006 20:25:14 +0200
>On Mon, 25 Sep 2006 14:13:27 -0400
>"Sick Twist" <thesicktwist at hotmail.com> wrote:
> > Ekiga Preferences:
> > NAT Traversal Method: None
>Yea, I understand.
> > Audio Codecs: Make sure that _only_ PCMU 64 kbps 8 kHz is checked.
>Mh, I don't understand that one. Does the provider refuse connection
>when Ekiga provides more than that codec? If not, does it work when
>it's the first codec in the list?
> > When I start Ekiga I can place one telephone call sucessfully. After
> > that, Ekiga displays "Security check failed" when I attempt to make
> > additional calls. Does anyone have any ideas? Thanks in advance.
>Uh. We would need a complete debug output of the SIP session.
>"ekiga -d 4"
>Best is, you post it somewhere (pastebin.ca). The "security check
>failed" is a subsequent message from some SIP error message the
>provider sent.

I'm running Ekiga on Ubuntu's development version, Edgy Eft. Ekiga was 
version 2.0.2 but it was just upgraded to version 2.0.3 and now I can't 
place any calls at all. When I try to place a call it says "No common 

When I was using Ekiga 2.0.2, I could only make calls when the PCMU codec 
was the only audio codec selected. If I moved PCMU to the top of the codec 
list but had the other codecs checked, I would get an authentication error 
when trying to make calls.

There is definitely something strange going on with BroadVoice and the way 
that Ekiga announces what audio codecs are available. Here is the Ekiga 
2.0.3 debug output:


More information about the ekiga-list mailing list