Re: [Ekiga-list] Timeout? Call out OK call in from Diamon unseen or broken



Damien Sandras wrote:
Le lundi 22 octobre 2007 �1:52 +0100, Philippe Laliberte a �it :
ael wrote:
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.
kernel-2.6.22.9
Firewall disabled. selinux disabled
Ekiga 2.0.11

Router Modem ADSL SpeedTouch 780
Firewall disabled (once I get Ekiga working I'll test what I can close)
VoIp turned off

Modem routing Configuration

Protocol Port Range Translate To ... Trigger Protocol Trigger Port Any 5000 - 5100 5000 - 5100 - - UDP 3479 - 3479 3479 - 3479 UDP 3479 UDP 3478 - 3479 3478 - 3479 UDP 3478
I can't quite decode the above. If you trigger on 3478 (UDP) and then
open 5000 -5100 (UDP) then 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
Just missing a cariage return

Protocol    Port Range    Translate To ...    Trigger Protocol  Trigger
Port   Any            5000 - 5100    5000 - 5100    -    -
UDP           3479 - 3479    3479 - 3479    UDP   3479
UDP           3478 - 3479    3478 - 3479    UDP   3478


What you mean is that I should just do :

UDP         5000 - 5100    3479 - 3479    UDP   3479
UDP         5100 - 5100    3478 - 3479    UDP   3478
Looking at that again, why are you translating 3479 into 5000-5100? Or
am I misunderstanding the web interface (I assume)?

Once you see a packet on 3478, then open 5000-5100. Do not translate
3478 into 5000... if that is what the above means. 3478 and 3479 should
be (con) tracked properly by the router. It is just that it will block
5000-5100 unless it is told otherwise.

I have not encountered a SpeedTouch router so I may be misunderstanding
its configuration.

ael
The error is mine, late doing too many thing at the same time. You did
understand it correctly the first time.
UDP         5000 - 5100    5000 - 5100    UDP   3479
UDP         5100 - 5100    5000 - 5100    UDP   3478
I'll test it later this afternoon thanks.


Why 5100 - 5100 ?


Well unconclusive:

UDP    5000 - 5100    5000 - 5100    UDP    3479
UDP    5000 - 5100    5000 - 5100    UDP    3478


Wizard, still in symetric NAT

Manual STUN: No sound on 500 ekiga net, no calls in from Diamoncard even after a fresh restart None: 500 ekiga net ok, no calls in from Diamoncard even after a fresh restart.


Back to no trigger definition, same as above.

Back to TCP/UDP

Any    5000 - 5100    5000 - 5100    Any    3478
Any    5000 - 5100    5000 - 5100    Any    3479

Wizard, still in symetric NAT

STUN: No sound on 500 ekiga net, Calls in from Diamoncard OK even after a while, after manual changes back and forth it does not work anymore

None: 500 ekiga net ok, no calls in from Diamoncard even after a fresh restart.

Back to no trigger definition, same as above.

Wireshark shows SIP activity for the 500 ekiga call but nothing coming in from Diamoncard.

Can all this working not working be related to a slowness from diamoncard or the router to react to changes? I am connected to eugw.ast.diamondcard.us. If I try to setup my VoIp on the modem, it never seems to register.

I'll go back to STUN (with trigger of the router) and shutdown Ekiga for an hour or so to see if when I come back It will work.

Cheers,

Philippe



begin:vcard
fn:Philippe Laliberte
n:Laliberte;Philippe
email;internet:arsphl davidbowie com
tel;home:SIP:arsphl ekiga net
tel;cell:+44 7890 628 541
version:2.1
end:vcard



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]