Re: [GnomeMeeting-devel-list] register/cancel breakage
- From: Damien Sandras <dsandras seconix com>
- To: GnomeMeeting development mailing list <gnomemeeting-devel-list gnome org>
- Subject: Re: [GnomeMeeting-devel-list] register/cancel breakage
- Date: Sat, 18 Mar 2006 14:22:10 +0100
Le samedi 18 mars 2006 à 23:44 +1030, Geoffrey D. Bennett a écrit :
> Hi there,
>
> There seem to be some oddities in Ekiga's register/cancel handling.
> This is on startup:
>
> First transmit of REGISTER message:
>
> 2006/03/18 23:33:15.392 0:02.548 GMAccounts...t:0a36bee0 SIP Sending PDU on udp$203.16.231.11:5060<if=udp$203.16.231.153:5061>
> REGISTER sip:alice.netcraft.com.au SIP/2.0
> CSeq: 1 REGISTER
> Via: SIP/2.0/UDP 203.16.231.153:5061;branch=z9hG4bKdcfb2c3b-edb4-da11-9266-001125d23952;rport
> [...]
> 2006/03/18 23:33:15.395 0:02.551 SIP Transport:a403fa8 SIP Read thread started.
> 2006/03/18 23:33:15.395 0:02.551 SIP Transport:a403fa8 SIP Waiting for PDU on udp$203.16.231.11:5060<if=udp$203.16.231.153:5061>
>
> Retransmit:
>
> 2006/03/18 23:33:15.441 0:02.597 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 1
> 2006/03/18 23:33:15.442 0:02.598 Housekeeper SIP Sending PDU on udp$203.16.231.11:5060<if=udp$203.16.231.153:5061>
> REGISTER sip:alice.netcraft.com.au SIP/2.0
> CSeq: 1 REGISTER
> Via: SIP/2.0/UDP 203.16.231.153:5061;branch=z9hG4bKdcfb2c3b-edb4-da11-9266-001125d23952;rport
>
> 407 from server:
>
> 2006/03/18 23:33:15.675 0:02.831 SIP Transport:a403fa8 SIP PDU Received on udp$203.16.231.11:5060<if=udp$203.16.231.153:5061>
> SIP/2.0 407 Proxy Authentication Required
> Date: Sat, 18 Mar 2006 13:03:21 GMT
> CSeq: 1 REGISTER
> Via: SIP/2.0/UDP 203.16.231.153:5061;branch=z9hG4bKdcfb2c3b-edb4-da11-9266-001125d23952;rport=5061;received=203.16.231.153:5061
>
> REGISTER with credentials:
>
> 2006/03/18 23:33:15.675 0:02.831 SIP Transport:a403fa8 SIP Transaction 1 REGISTER completed.
> 2006/03/18 23:33:15.675 0:02.831 SIP Transport:a403fa8 OpalUDP Ended connect, selecting 203.16.231.153:5061
> 2006/03/18 23:33:15.675 0:02.831 SIP Transport:a403fa8 SIP Received Proxy Authentication Required response
> 2006/03/18 23:33:15.676 0:02.832 SIP Transport:a403fa8 SIP Adding authentication information
> 2006/03/18 23:33:15.677 0:02.833 SIP Transport:a403fa8 SIP Sending PDU on udp$203.16.231.11:5060<if=udp$203.16.231.153:5061>
> REGISTER sip:alice.netcraft.com.au SIP/2.0
> CSeq: 2 REGISTER
> Via: SIP/2.0/UDP 203.16.231.153:5061;branch=z9hG4bK06a1583b-edb4-da11-9266-001125d23952;rport
>
> Duplicate 407 from server (because of the retransmit):
>
> 2006/03/18 23:33:15.677 0:02.833 SIP Transport:a403fa8 SIP Waiting for PDU on udp$203.16.231.11:5060<if=udp$203.16.231.153:5061>
> 2006/03/18 23:33:15.755 0:02.911 SIP Transport:a403fa8 SIP PDU Received on udp$203.16.231.11:5060<if=udp$203.16.231.153:5061>
> SIP/2.0 407 Proxy Authentication Required
> Date: Sat, 18 Mar 2006 13:03:22 GMT
> CSeq: 1 REGISTER
> Via: SIP/2.0/UDP 203.16.231.153:5061;branch=z9hG4bKdcfb2c3b-edb4-da11-9266-001125d23952;rport=5061;received=203.16.231.153:5061
>
> Then it gets weird -- Ekiga sends a CANCEL for the REGISTER that had
> the credentials?!
>
> 2006/03/18 23:33:15.755 0:02.911 SIP Transport:a403fa8 SIP Transaction 1 REGISTER completed.
> 2006/03/18 23:33:15.756 0:02.912 SIP Transport:a403fa8 SIP Sending PDU on udp$203.16.231.11:5060<if=udp$203.16.231.153:5061>
> CANCEL sip:alice.netcraft.com.au SIP/2.0
> CSeq: 2 CANCEL
> Via: SIP/2.0/UDP 203.16.231.153:5061;branch=z9hG4bK06a1583b-edb4-da11-9266-001125d23952;rport
>
> The server responds to the REGISTER:
>
> 2006/03/18 23:33:16.161 0:03.317 SIP Transport:a403fa8 SIP PDU Received on udp$203.16.231.11:5060<if=udp$203.16.231.153:5061>
> SIP/2.0 200 OK
> Date: Sat, 18 Mar 2006 13:03:22 GMT
> CSeq: 2 REGISTER
> Via: SIP/2.0/UDP 203.16.231.153:5061;branch=z9hG4bK06a1583b-edb4-da11-9266-001125d23952;rport=5061;received=203.16.231.153:5061
>
> Ekiga shows that the user is logged in now, but RFC 3261 Section 9.1
> says "A CANCEL request SHOULD NOT be sent to cancel a request other
> than INVITE." I'm not sure what the purpose of trying to CANCEL that
> REGISTER is anyway?
>
It had been like that in OPAL since years, and I left it like it was. I
do not think it is not compliant, the RFC says "SHOULD NOT", not "MUST
NOT".
However, I think it would be good if I removed it.
Can you double-check that and post a bug report (ideally with a patch)?
Thanks,
--
_ Damien Sandras
(o-
//\ Ekiga Softphone: http://www.ekiga.org/
v_/_ FOSDEM 2006 : http://www.fosdem.org/
SIP Phone : sip:dsandras ekiga net
sip:600000 ekiga net
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]