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





On Tue, Mar 22, 2011 at 7:32 PM, Eugen Dedu <Eugen Dedu pu-pm univ-fcomte fr> wrote:

  ========================   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


Hi.
Thanks for your insight. I tested by renaming the account to ekiga.net%limit, restarted ekiga. Register problem still exists with above mentioned differing Call-ID values.
Just to be sure, tested also renaming the account to ekiga.net%limit% but the result was the same.

-Jani



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