I updated the DNS Zone to stun.sipgate.net...
Le lundi 06 avril 2015 à 22:13 +0200, Eugen Dedu a écrit :
> Damien, stun.ekiga.net is down...
>
> On 06/04/15 21:14, Damien Sandras wrote:
> > stun.ekiga.net is an alias to stun.voipbuster.com
> >
> > Perhaps they are down ?
> >
> > If that's the c
Damien, stun.ekiga.net is down...
On 06/04/15 21:14, Damien Sandras wrote:
stun.ekiga.net is an alias to stun.voipbuster.com
Perhaps they are down ?
If that's the case, I can change the alias to stun.sipgate.de
We used to have our own STUN server, but that's not the case anymore...
Le vendre
It looks as if stun.sipgate.net might be a possibility from trying with
the stun command:
~$ stun stun.voipbuster.com
STUN client version 0.96
Primary: Blocked or could not reach STUN server
Return value is 0x1c
~$ stun stun.sipgate.de
STUN client version 0.96
error was 110
stun.sipgate.de
stun.ekiga.net is an alias to stun.voipbuster.com
Perhaps they are down ?
If that's the case, I can change the alias to stun.sipgate.de
We used to have our own STUN server, but that's not the case anymore...
Le vendredi 03 avril 2015 à 17:02 +0100, ael a écrit :
> On Fri, Apr 03, 2015 at 03:14
On Sat, Apr 04, 2015 at 08:26:42PM +0100, John Talbut wrote:
> In other words it seems to work with stun.sipgate.net but not with
> stun.ekiga.net.
>
> Is the problem with the ekiga stun server?
I can confirm this. If I change from the ekiga stun server (I also have
an account on sipgate, so also
On 04/04/15 15:23, mdbug wrote:
On 04/04/2015 12:15 AM, John Talbut wrote:
On 03/04/15 17:08, mdbug wrote:
On 04/03/2015 10:10 AM, John Talbut wrote:
I had checked and have rechecked my router and ports 3478 - 3479 are
allowed. Also I can successfully ping and run traceroute to
77.72.174
On 04/04/2015 12:15 AM, John Talbut wrote:
On 03/04/15 17:08, mdbug wrote:
On 04/03/2015 10:10 AM, John Talbut wrote:
I had checked and have rechecked my router and ports 3478 - 3479 are
allowed. Also I can successfully ping and run traceroute to
77.72.174.167.
I would suggest running
On 03/04/15 17:08, mdbug wrote:
On 04/03/2015 10:10 AM, John Talbut wrote:
I had checked and have rechecked my router and ports 3478 - 3479 are
allowed. Also I can successfully ping and run traceroute to
77.72.174.167.
I would suggest running a VOIP port check.
Change _registar to your si
On 04/03/2015 10:10 AM, John Talbut wrote:
I had checked and have rechecked my router and ports 3478 - 3479 are
allowed. Also I can successfully ping and run traceroute to 77.72.174.167.
I would suggest running a VOIP port check.
Change _registar to your sip provider in the attached script
On Fri, Apr 03, 2015 at 03:14:17PM +0100, John Talbut wrote:
> I am getting the "Ekiga did not manage to configure your network settings
> automatically" message. I have followed the instructions and checked my
I too have *suddenly* started getting those messages from ekiga, which
seems to work p
On 03/04/15 15:38, Eugen Dedu wrote:
On 03/04/15 16:14, John Talbut wrote:
I am getting the "Ekiga did not manage to configure your network
settings automatically" message. I have followed the instructions and
checked my router settings, which seem correct (I think I have used
Ekiga before with
On 03/04/15 16:14, John Talbut wrote:
I am getting the "Ekiga did not manage to configure your network
settings automatically" message. I have followed the instructions and
checked my router settings, which seem correct (I think I have used
Ekiga before without this problem).
Using the command:
I am getting the "Ekiga did not manage to configure your network
settings automatically" message. I have followed the instructions and
checked my router settings, which seem correct (I think I have used
Ekiga before without this problem).
Using the command: ekiga -d 4 2>&1 | grep STUN
I get:
13 matches
Mail list logo
