ates seems to have multiple ekiga-list trailers so it looks
like some sort of loop in the mailer?
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list
your router
so I suppose that is what you are missing. I think it is documented
in the ekiga wiki.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list
gs are static which
is probably your case.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list
nfo nf_conntrack_sip
...
parm: ports:port numbers of SIP servers (array of ushort)
...
it looks as if I need to load with the port range. I am not even sure
whether this is for servers or clients behind the firewall (or both).
Has anyone any experience or suggestions?
tle concerned about the tracker modifying the contents of
SIP packets: commercial routers with "SIP ALG" which I suspect are based
on these modules seem to fail.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list
d.
echo "testing" 2>&1 >/tmp/test.txt works properly.
I think that I am closing the output stream on ekiga just by choosing
"Quit" from the ekiga menu.
Am I forgetting/overlooking something elementary? I do hope it is not
systemd fouling things up as usual...
ael
PS
On Sat, Feb 07, 2015 at 10:20:50PM +0100, Eugen Dedu wrote:
> On 07/02/15 17:21, ael wrote:
> >This is weird. On Debian testing
> > ekiga -d 4 2>&1 > /tmp/ekiga.dmp
> >produces no output: ekiga.dmp is created but is empty.
>
> It is a tricky thing in shell,
imple and short.
Thanks in advance for any enlightenment.
ael
|Time | shelf.conquest|
| | | ekiga.net |
|19.710059000| INVITE SDP (Speex g7 |SIP From: "ael"
(5060) |
|19.733743000
rror packets *were* passed
back through the firewall to ekiga (well the right port). Should ekiga
not have repackaged the INVITE? Or at least reported the error?
Maybe this is in the wiki: I ought to check.
ael
___
ekiga-list mailing list
"cone nat" for the ekiga traffic.
The simplest is to forward ports.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list
updated recently. Likewise my router configuration has not changed.
Checking with gconf-editor, the stun server is set to stun.ekiga.net.
The failure message from ekiga-net is "Globally not acceptable".
This may, or may not, be useful informatio
sipgate, so also used the sipgate stun server) the problem
goes away.
No time to look further just now...
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list
king just now, I find that I can connect again. You were probably
just unlucky to try when there was a problem.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list
...@sipgate.co.uk
debug trace working. A simple diff of the two cases wasn't useful (for
me: far too much noise, and the traces differed almost every where).
The two gzipped traces are 41K and 48K long so quite compact.
Any help with debugging these?
On Mon, Oct 19, 2015 at 05:59:49PM +0200, Eugen Dedu wrote:
> On 15/10/15 15:36, ael wrote:
> >Running ekiga on linux some numbers just silently disconnect while
> >others work. Calling the same numbers from my Grandstream ATA always
> >works.
> >
> >This is usi
On Mon, Oct 19, 2015 at 10:44:37PM +0200, Eugen Dedu wrote:
> On 19/10/15 21:13, ael wrote:
>
> After a quick look at the log, I see a BYE packet send by sipgate. This
> means it wants to close the connection, hence the reason you point above:
> EndedByRemoteUser.
Thanks f
Will version 2.0.11 appear on www.ekiga.com soon? 2.0.9 seems to the
latest there.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
en updated in a typical system.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
en it should be ok. I am not sure that is what
you have above is it? I can't make out the first line ending in
5000-5100: how does that relate to the two following lines?
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
P laliberte wrote:
> ael wrote:
>> Philippe Laliberte wrote:
>>
>>> Hello,
>>>
>>> I am running into a little problem. I did dig into the wiki but to no
>>> avail.
>>>
>>> Set-up:
>>>
>>> Fedora 7.
>>&g
Philippe Laliberte wrote:
> Damien Sandras wrote:
>> Le lundi 22 octobre 2007 à 11:52 +0100, Philippe Laliberte a écrit :
>>
>>> ael wrote:
>>>> P laliberte wrote:
>>>>
>>>>> ael wrote:
>>>>>
perfectly. Contact me off list if you have problems.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
ndytone with the default 5060 as shown here:
http://homepage.ntlworld.com/lawrence_a_e/handytone/handy.png
I have used the gconf editor to change the ekigas on different machines
to use 5062, 5064, etc.
I think the HT-386 shares the same firmware with the HT-386, so I would
expe
>>
>
> I'm not sure it is supposed to work (the same account).
It works here. at least with sipgate which seems to be asterisk based.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
t; In next step I have set up redirects like this:
>> 5000-5099 -> redirected to Grandstream
>> 5100-5199 -> redirected to my PC.
>> GS accounts on 5060 port 0 , 5062 port 1, Ekiga bound to 5160.
I don't think that you need any r
minor problem with installing it: the
configuration assistant, which insisted on running on first
installation, hung. That was cured by running as root first which seemed
to clear what was perhaps a permissions problem. Thereafter I could run
ekiga as a normal user. (Yes, reported to Kilian who d
dstream might do one.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
I could compile SIP and H.323
> support into my NAT box
If you are implementing your own NAT then it should be easy to fix.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
e wiki is not well flagged: http://wiki.ekiga.org/. One
archive is
http://mail.gnome.org/archives/ekiga-list/
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
ts/debian/Release:-
Architectures: i386 amd64 source
Codename: unstable
Components: main
Date: Mon, 27 Oct 2008 21:30:05 UTC
Description: Ekiga SVN snapshot
Label: Ekiga SVN Snapshots
Origin: Ekiga team (Eugen Dedu)
Suite: unstable
....
??
ael
___
e
Business Manager Jeremiah O'Neal wrote:
> Hi everyone,
>
> This question sort of goes with the question I had asked before about
> looking for a VOIP phone that works with Ekiga.
I use a Grandstream Handytone 486 and ekiga together. I make sure that
they use different ports.
if one works, so should the other
ael
>> I use a Grandstream Handytone 486 and ekiga together. I make sure that
>> they use different ports. Works well.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
the
Grandstream and ekiga. Actually my unit is a T-Com 300GSM, but that is
just a badge-engineered Pirelli. I did have to upgrade the original
firmware.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
iga solution, but compatible: look into the Handytone adaptor
series from Grandstream. Works here. www.grandstream.com IIRC.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Victoria Wilson wrote:
>
> pointers you may have. I've read the FAQ and nothing seemed obvious.
> I've opened the ports for Ekiga SIP and STUN service on my router but
Are you using dynamic port triggering as described on the wiki?
ael
___
H. S. wrote:
Hello,
This is intended for whoever is maintaining this mailing list. I was
wondering if this list can be made available via gmane.org.
IIRC you simply make the request to gmane. So you are asking in the
wrong place: instead visit the gmane website and enter the request.
ael
You might be better off with port triggering on that linksys: details on
the ekiga wiki.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
clue about whether this is a
problem with username/password (presumably not in this case since I was
working with previous versions), a timeout, or something else. Newbies
won't want to get into -d4 stuff...
ael
___
ekiga-list mailing list
and triggers on outgoing port 3478 as
described in the wiki.
Before investigating or reporting further, here is the -d2 report:
http://homepage.ntlworld.com/lawrence_a_e/debug/ekiga2.dmp
Is there enough information there to identify the basic problem?
ael
forwarding" should surely also
mention "Port triggering" as well which is superior if it works - which
it should.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Eugen Dedu wrote:
ael wrote:
I have just upgraded to 3.2.5 (debian 3.2.5-1) on one of my machines,
and am a bit baffled by the
"Could not register (Globally not acceptable)"
message displayed in the Accounts window when I try to register with
ekiga.net. My other two sip accounts r
again.
Maybe I will post a -d4 dump to see if that helps clarify what is
happening, before getting wireshark running again.
Busy right now, so this will have to wait for now.
Thanks for the reply,
ael
___
ekiga-list mailing list
ekiga-list@gnom
on is complete?
I will reach for wireshark to investigate properly eventually, so this
is just speculation until then.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
ekiga. Actually even that isn't
necessary because the NAT router changes ports anyway.
Your public IP address
+ port
^^
is used to register the Ekiga instance.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailma
Rob wrote:
ael wrote on Sat, 05 Dec 2009 15:49:
John Feagans wrote:
Two instances of Ekiga on the same PC cannot work,
but you may also have the same problem if you have
two PC's each running Ekiga behind the same home router.
I have been doing this for years. Just use gconf-edit
to a
esigned to bounce 3rd party incoming traffic. Hence the
extra complication.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
gt; 10.1.1.1, and yet other sites claim it is 10.1.1.10. Some have even
> suggested my router ip number should be 192.168.15.1. This is all very
> confusing.
Indeed. What about using wireshark to find out what is going on?
Or just type "route"? (On ubuntu, maybe that is sudo route?)
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
default
setting for your router/modem.
> >>confusing.
> Thanks for the response ael.
>
> My unsuccessful efforts to create NAT Rule Entries for the modem was
> my feeble attempt to follow the Ekiga-behind-a-NAT-router
> instructions on the wiki. These rules were manipula
only used bridge mode when gatewaying onto a local subnet.
I suspect it is a problem in configuring the modem/router, but I don't know
the model and have no experience with a combined modem/router. So I hope
someone with the right background or experience will come in here.
ael
___
amp; understood the relevant documents including the STUN rfc
then perhaps one can make some tentative suggestions.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
s go directly rather than via the server. Thus
in effect the server introduces a 3rd party. There has to be a mechanism
to get that 3rd party traffic through the NAT: hence STUN. Otherwise
any "3rd party" spam etc. would get through.
Above is a very simplistic explanation
My sound card is rather complex as viewed by ALSA. To use ekiga, I need
to launch alsamixer or one of its variants and set at least 4 different
controls which are not very memorable.
Instead I have used alsactl to store the configuration in a special
"ekiga-alsa.cfg" file. Then I can use
alsactl -
Damien Sandras wrote:
> Le vendredi 22 décembre 2006 à 23:43 +0000, ael a écrit :
>
>>My sound card is rather complex as viewed by ALSA. To use ekiga, I need
>>to launch alsamixer or one of its variants and set at least 4 different
>>controls which are not very memorable.
Damien Sandras wrote:
> Le samedi 23 décembre 2006 à 16:16 +0000, ael a écrit :
>
>>>The real question is : why do you have to do that? Mixer settings should
>>>be remembered accross reboots, and should not be changed while you are
>>>logged.
>>>
>>
> Le samedi 30 décembre 2006 à 12:14 +, Fabrizio Lippolis a écrit :
>>The receiver complains often doesn't hear me much though I have raised the
>>microphone slider in the audio tab in Ekiga and in the volume settings in
>>Gnome. I have to talk with the microphone on my mouth and loud voice t
Background:
--
I use an ATA (Analogue Telephone Adapter, a sip based unit) connected to
a standard handset, to my landline and to a cordless unit. This works
even when my computers are not booted and allows me to make and accept
voip calls away from my desktop. Also I prefer a conventional
Damien Sandras wrote:
> Le mercredi 03 janvier 2007 à 22:57 +0000, ael a écrit :
>
>>Background:
>>--
>>
>>I use an ATA (Analogue Telephone Adapter, a sip based unit) connected to
>>a standard handset, to my landline and to a cordless unit. This wo
George Boyd wrote:
> Unfortunately, I can't help you with your problem. But I have been
> trying to find a reasonably priced ATA to use with Ekiga. Which one are
> you using and where could I get one.
Well I am using a Grandstream Handytone 486 which fairly cheap and
widely available. There are se
ael wrote:
> Damien Sandras wrote:
>>>
>>>Ekiga makes the STUN checks at startup as described above?
>>>
>>
>>
>>It does.
>>
>>However, if STUN detects "Partially blocked NAT", it is because the
>>forwarded ports on t
Damien Sandras wrote:
> Le jeudi 04 janvier 2007 à 23:20 +0000, ael a écrit :
>
> [...]
>
>
>
>>The "magic" manipulation of the Network setting was logged as
>>
>>2007/01/04 22:57:41.372 0:48.346GMStunClient:0853daa0 OPAL
>>STUN s
Damien Sandras wrote:
> Le vendredi 05 janvier 2007 à 13:53 +0000, ael a écrit :
>>I played for a fair time with the router settings, but I think the
>>problem is that I don't know what the HandyTone ATA is actually doing.
>>It is at the front end just after the cabl
Damien Sandras wrote:
> Le samedi 06 janvier 2007 à 00:05 +0000, ael a écrit :
>
>>Damien Sandras wrote:
>>
>>>Le vendredi 05 janvier 2007 à 13:53 +, ael a écrit :
>>
>>>>I played for a fair time with the router settings, but I think the
>>&g
Damien Sandras wrote:
> Le vendredi 05 janvier 2007 à 13:53 +0000, ael a écrit :
>
> [...]
>
>
>>>Check if there is not something to configure at the router level.
>>
>>I played for a fair time with the router settings, but I think the
>>problem is t
Julien Puydt wrote:
> ael a écrit :
>
>>Initially there are 14 packets exchanged. This is while ekiga is
>>starting up. At this point attempted calls to, say [EMAIL PROTECTED], fail
>>usually with abnormal call termination.
>
>
> You mean ekiga wasn't regis
Simon Wood wrote:
> Hi, Just thought I'd add my $0.02 on this. I have a set up of 3
> machines (all running Ekiga) and 1 hard phone running behind a single
> OpenWrt router.
>
> To get this working I altered the port settings on Ekiga(s) using
> gconf-editor, and enabled both STUN and Proxy (fwdna
Keith Powell wrote:
> Hello.
>
> I have just bought a web cam and am trying to get Ekiga working, but
> without much success! As this is my first attempt at setting up 'web
> chatting', I am very much a newbie. So sorry if this is a very basic
> question.
>
> When I run Ekiga, without even try
Damien Sandras wrote:
> Le mercredi 03 janvier 2007 à 22:57 +0000, ael a écrit :
>
>>Background:
>>--
>>
>>I use an ATA (Analogue Telephone Adapter, a sip based unit) connected to
>>a standard handset, to my landline and to a cordless unit. This wo
ion rule" set up in the router :
http://wiki.ekiga.org/index.php/Dynamic_navigation_of_NAT_routers
It sounds as if you have a symmetric NAT by default (for which the STUN
protocol is non deterministic).
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
, I forgot to ask whether you had checked that the
various instances of ekiga and XTen(?) are all using distinct ports. But
you say that you have read the documentation and FAQs, so you must have
done that ...
ael
___
ekiga-list mailing list
>>
And I can confirm that ekiga works with sipgate.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
r services for pc>pstn, and be
> able to use it as a POTS.
I have already reported on this list that the Grandstream Handytone 486
ATA works here with linux, cable modem. landline and ekiga with at
least 4 sip registries.
ael
___
ekiga-list
displayed in the "general History" window and
maybe the output from -d 4 if you want help. "I got a timeout" is a bit
too vague. Was this before or after registration, for example
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
help if you show us the messages displayed in the "General
History" Window (under the Tools menu). Perhaps also -d 4 later.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Maurizio Avogadro wrote:
> W.P. wrote:
>>
>>
>> Unfortunately yes. With a NAT'ed connection you have to use STUN
>> (and/or) proxy.
>> Take a look at ekiga wiki.
>> W.P.
>>
> Of course I _did_ use STUN (stun.ekiga.net) when beh
alogue signal in any way beyond, presumably,
detecting the ring tone so that it can switch.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
/wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router ?
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Am I the only one having trouble with an entry (from the wiki) of
deb http://www.ekiga.org/admin/downloads/latest/debian/etch_x86 ./
in my /etc/apt/sources.list?
I can download the debs from there manually, but I cannot browse
http://www.ekiga.org/admin/downloads/latest/debian/etch_x86
(403 forbi
yannick wrote:
> Le mercredi 23 mai 2007 à 11:40 +0100, ael a écrit :
>> Am I the only one having trouble with an entry (from the wiki) of
>>
>> deb http://www.ekiga.org/admin/downloads/latest/debian/etch_x86 ./
>
> Try adding a / at the end of etch_x86:
>
ael wrote:
> yannick wrote:
>> Le mercredi 23 mai 2007 à 11:40 +0100, ael a écrit :
>>> Am I the only one having trouble with an entry (from the wiki) of
>>>
>>> deb http://www.ekiga.org/admin/downloads/latest/debian/etch_x86 ./
> I suppose the Packages fi
e: Registration
>>> failed,because of timeout
>>>
>> It means the server is not reachable or the answers do not reach you...
>>
>>
>>
> Mmh, ok, but what should i do? I'm running with open suse Linux 10.2 an
> KDE. I'm opening the udp ports 5xxx that ekiga needs. Is their anything
> else i can do?
? Open the STUN ports as well? (3478-3479)
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
press 1 for support or press two for
> account information'
Do you not have the "dialpad"? Probably the 3rd icon/subwindow across
the top? Or it can be selected from the [View] menu.
If by any chance that doesn't work, check that you have
"sent DTMF as: RFC2833&q
previous reply, if you mean by "locked", nothing
seems to happen when you click on the buttons, it is likely to be
that configuration option that I mentioned.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list
ting
the entries under apps->ekiga->protocols-> ports/sip in
gconf-editor?
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list
phone still does. I haven't tried ekiga for a long time:
unless you are going to take over maintenance, I would forget it.
ael
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list
84 matches
Mail list logo
