Le lundi 05 mars 2007 à 16:46 +0100, Maurizio Avogadro a écrit : > ael wrote: > > > > And what sort of NAT did ekiga report? > > > > ael > > > "Cone NAT" in my home setup and "Limited ports NAT" in my office setup > (worst case). > While I could configure my office router in order to have a working SIP, > I can't do anything for my home setup (please make sure to read my > previous posts for some details). >
I have examined your logs, and there is a hint. REGISTER sip:ekiga.net SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 213.140.19.115:44271;branch=z9hG4bK6ec00191-ddc9-db11-8239-000c6ea583aa;rport User-Agent: Ekiga/2.0.3 Authorization: Digest username="m.avogadro", realm="ekiga.net", nonce="45eca730d437e660b99a2373c77b56c4b9898c5e", uri="sip:ekiga.net", algorithm=md5, response="8846174ff5ae991950a6a709a2ff3bd6" From: <sip:[EMAIL PROTECTED]>;tag=eee9f890-ddc9-db11-8239-000c6ea583aa Call-ID: [EMAIL PROTECTED] To: <sip:[EMAIL PROTECTED]> Contact: <sip:[EMAIL PROTECTED]:44271;transport=udp> Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 See the Contact field -> Contact: <sip:[EMAIL PROTECTED]:44271;transport=udp> It is the public IP address. Then in the answer from the server : SIP/2.0 200 OK CSeq: 2 REGISTER Via: SIP/2.0/UDP 86.64.162.35:5060;branch=z9hG4bK6ec00191-ddc9-db11-8239-000c6ea583aa;rport=44271;received=213.140.19.115 Server: Sip EXpress router (0.9.6 (i386/linux)) From: <sip:[EMAIL PROTECTED]>;tag=eee9f890-ddc9-db11-8239-000c6ea583aa Call-ID: [EMAIL PROTECTED] To: <sip:[EMAIL PROTECTED]>;tag=12d18c5009a2de32fca8ae9d70ad0321.7906 Contact: <sip:[EMAIL PROTECTED]:5063;transport=udp>;expires=3600 Warning: 392 86.64.162.35:5060 "Noisy feedback tells: pid=4163 req_src_ip=213.140.19.115 req_src_port=44271 in_uri=sip:ekiga.net out_uri=sip:ekiga.net via_cnt==1" Content-Length: 0 See the Contact field -> Contact: <sip:[EMAIL PROTECTED]:5063;transport=udp>;expires=3600 It means that the router has been rewriting the SIP packet !!! It has replaced the public IP address by your personal IP address. It is a bug in the router. I suggest you to try the following : - do not use STUN at all. I do not think you are in a real NAT, 23.X.X.X does not sound like a private address too me. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] _______________________________________________ ekiga-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list
