Re: [GnomeMeeting-devel-list] sip reregister timeout from ekiga.net after 2h
- From: Daniel Huhardeaux <devel tootai net>
- To: GnomeMeeting development mailing list <gnomemeeting-devel-list gnome org>
- Subject: Re: [GnomeMeeting-devel-list] sip reregister timeout from ekiga.net after 2h
- Date: Mon, 30 Jan 2006 20:09:35 +0100
thomas schorpp a écrit :
Hi Thomas
[...]
here is it, some unauthorized msgs...
2006/01/30 17:06:15.966 1:43:43.375 SIP Transport:8389230 SIP Received Authentication Required response
2006/01/30 17:06:15.968 1:43:43.379 SIP Transport:8439938 SIP PDU Received SIP/2.0 401 Unauthorized on udp$213.186.62.145:5060<if=udp$192.168.1.100:5061>
2006/01/30 17:06:16.090 1:43:43.500 SIP Transport:8389230 SIP Adding authentication information
2006/01/30 17:06:16.115 1:43:43.525 SIP Transport:8389230 SIP Sending PDU REGISTER sip:sipgate.de on udp$217.10.79.9:5060<if=udp$85.212.147.219:5072>
2006/01/30 17:06:16.216 1:43:43.625 SIP Transport:8389230 SIP PDU Received SIP/2.0 200 OK on udp$217.10.79.9:5060<if=udp$85.212.147.219:5072>
I don't see anything wrong. The first registration failed and then you
register to the second server. From my notes (asterisk), sipgate doesn't
allow registring if you don't give the domain, eg sipgate.de
Anyway, for me, you're registred.
--
Daniel
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]