GNOME.org
 

Re: [Ekiga-list] Nat issues (cont) - REGISTER & Auth

On 17/03/11 12:40, Jani Patanen wrote:

Hi.
Not sure if my initial email made it to the list, so short summary to start
with:
Using ekiga with Fedora 14. I can make calls no problems. I can receive
calls when I'm on wired connetion.
On wireless, the connection is NATed. I have set port forwarding for 1720,
3478-3479, 5000-5100 and I've verfied them working with nmap&  wireshark.
I've looked to the output from ekiga -d 4 and it appears that on WLAN, when
receiving "401 Unauthorized" there is no additional register request with
authentication tokens being sent.
What could cause that?
Why does it happen only on WLAN?
With wired connection Register with the auth token follows the 401.
Help much appreaciated.
I was not able to register myself with telepathy either, but I think that
boils down to TP using and unforwarded port number in my sip URI.




Note: "jani.patanen@" replaced with "jani.patanen-" just in case some
spambot is harvesting this.

The successful "handshake" goes with wired session as:
========================   0:21.814 Opal Liste...0x94915700 SIP PDU
received: r
em=udp$86.64.162.35:5060,local=udp$88.114.147.27:5060,if=88.114.147.27%eth0
SIP/2.0 401 Unauthorized
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 88.114.147.27:5060
;branch=z9hG4bK8648606b-df4e-e011-993e-001c25
9e810c;rport=5060
Server: Kamailio (1.5.3-notls (i386/linux))
From:<sip:jani.patanen-ekiga.net>;tag=18a8f16a-df4e-e011-993e-001c259e810c
Call-ID: 9a94f16a-df4e-e011-993e-001c259e810c@oc7228322058.myhost
To:<sip:jani.patanen-ekiga.net>;tag=c64e1f832a41ec1c1f4e5673ac5b80f6.d27e
Content-Length: 0
WWW-Authenticate: Digest realm="ekiga.net",
nonce="4d81c855000106f9459ee8af765bd
b66cfc1f52047dbdc06"


========================   0:23.668 Pool:0x94893700 SIP Sending PDU (826
bytes) to: rem=udp$86.64.162.35:5060,local=udp$88.114.147.27:5060
,if=88.114.147.27%eth0
REGISTER sip:ekiga.net SIP/2.0
CSeq: 2 REGISTER
Via: SIP/2.0/UDP 88.114.147.27:5060
;branch=z9hG4bK1ada896c-df4e-e011-993e-001c259e810c;rport
User-Agent: Ekiga/3.2.7
Authorization: Digest username="jani.patanen-ekiga.net", realm="ekiga.net",
nonce="4d81c855000106f9459ee8af765bdb66cfc1f52047dbdc06", uri="sip:ekiga.net",
algorithm=MD5, response="69fa70458d61cc34f313eea3a10d6d74"
From:<sip:jani.patanen-ekiga.net>;tag=18a8f16a-df4e-e011-993e-001c259e810c
Call-ID: 9a94f16a-df4e-e011-993e-001c259e810c@oc7228322058.myhost
To:<sip:jani.patanen-ekiga.net>
Contact:<sip:jani.patanen-88.114.147.27>;q=1,
<sip:jani.patanen-192.168.0.101>;q=0.667,
<sip:jani.patanen-9.12.227.129>;q=0.334
Allow:
INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING
Expires: 3600
Content-Length: 0
Max-Forwards: 70

  ========================   0:23.766 Opal Liste...0x94915700 SIP PDU
received: rem=udp$86.64.162.35:5060,local=udp$88.114.147.27:5060
,if=88.114.147.27%eth0
SIP/2.0 200 OK
CSeq: 2 REGISTER
Via: SIP/2.0/UDP 88.114.147.27:5060
;branch=z9hG4bK1ada896c-df4e-e011-993e-001c259e810c;rport=5060
Server: Kamailio (1.5.3-notls (i386/linux))
From:<sip:jani.patanen-ekiga.net>;tag=18a8f16a-df4e-e011-993e-001c259e810c
Call-ID: 9a94f16a-df4e-e011-993e-001c259e810c@oc7228322058.myhost
To:<sip:jani.patanen-ekiga.net>;tag=c64e1f832a41ec1c1f4e5673ac5b80f6.2d51
Contact:<sip:jani.patanen-88.114.147.27>;q=1;expires=1200,
<sip:jani.patanen-192.168.0.101>;q=0.667;expires=1200,
<sip:jani.patanen-9.12.227.129>;q=0.334;expires=1200
Content-Length: 0


======================= END WIRED =========================

the unsuccessful goes as:







  ========================   0:06.889 subscriber:0x5a9a1700 SIP Sending PDU
(570
bytes) to: rem=udp$86.64.162.35:5060,local=udp$88.114.144.25:5060
,if=192.168.0.1
01%wlan0
REGISTER sip:ekiga.net SIP/2.0
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 88.114.144.25:5060
;branch=z9hG4bK0880495f-e44e-e011-8190-00216bc2f158;rport
User-Agent: Ekiga/3.2.7
From:<sip:jani.patanen-ekiga.net>;tag=c85db15e-e44e-e011-8190-00216bc2f158
Call-ID: ba57b15e-e44e-e011-8190-00216bc2f158@oc7228322058.myhost
To:<sip:jani.patanen-ekiga.net>
Contact:<sip:jani.patanen-88.114.144.25>;q=1,
<sip:jani.patanen-192.168.0.101>;q=0.500
Allow:
INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING
Expires: 3600
Content-Length: 0
Max-Forwards: 70


  ========================   0:06.964 Opal Liste...0x85078700 SIP PDU
received: rem=udp$86.64.162.35:5060,local=udp$88.114.144.25:5060
,if=192.168.0.101%wlan0
SIP/2.0 401 Unauthorized
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 192.168.0.101:5060
;branch=z9hG4bK0880495f-e44e-e011-8190-00216bc2f158;rport=5060
Server: Kamailio (1.5.3-notls (i386/linux))
From:<sip:jani.patanen-ekiga.net>;tag=c85db15e-e44e-e011-8190-00216bc2f158
Call-ID: ba57b15e-e44e-e011-8190-00216bc2f158@192.168.0.101
To:<sip:jani.patanen-ekiga.net>;tag=c64e1f832a41ec1c1f4e5673ac5b80f6.808a
Content-Length: 0
WWW-Authenticate: Digest realm="ekiga.net",
nonce="4d81d0a400015e25c5d1975f622928b0f245e25bc4d50f4d"


============================== END WLAN ====================================
And there is no other requests, just following output:



2011/03/17 11:12:38.054   0:06.965      Opal Liste...0x85078700 SIP
Queueing PDU "1 REGISTER<401>",
transaction=z9hG4bK0880495f-e44e-e011-8190-00216bc2f158,
token=z9hG4bK0880495f-e44e-e011-8190-00216bc2f158
2011/03/17 11:12:38.054   0:06.966      Opal Liste...0x85078700 Opal
Transport clean up on termination
2011/03/17 11:12:38.054   0:06.966      Opal Liste...0x85078700 Opal
Transport Close
2011/03/17 11:12:38.054   0:06.966              Pool:0x84ff6700 SIP
Handling PDU "1 REGISTER<401>" for
transaction=z9hG4bK0880495f-e44e-e011-8190-00216bc2f158
2011/03/17 11:12:38.055   0:06.966              Pool:0x84ff6700 SIP
REGISTER transaction id=z9hG4bK0880495f-e44e-e011-8190-00216bc2f158
completed.
2011/03/17 11:12:38.055   0:06.966              Pool:0x84ff6700 SIP
Response received for unknown handler ID:


The line above contains the key to your problem.
For wlan, the Call-ID field of the sent packet ends in "@oc7228322058.myhost", while in the received packet its "@192.168.0.101". 

For wired, they always end in "@oc7228322058.myhost".
Try the workaround http://wiki.ekiga.org/index.php/Troubleshooting#Cannot_register_to_sip.1und1.de_or_some_other_registrar_with_ekiga_.3C.3D_3.2.x 

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