On Fri, May 20, 2011 at 12:30 AM, Bart Vandewoestyne <[email protected]> wrote: > On Thu, May 19, 2011 at 11:15:58PM +0200, Bart Vandewoestyne wrote: >> >> I've updated the file, i think we now have the full information. >> The new version is at the same url, namely >> >> http://www.kuleuven-kortrijk.be/~bartv/sip_capture.pcap >> >> Please let me know if this is enough info to debug my problem. >> If not, then let me know what to do. I'm glad to be able to help >> here! > > OK. I've done some more searching, and this is what I have so > far. If I try with Ekiga on my laptop, then this is how a typical > REGISTER message looks like: > > > REGISTER sip:ekiga.net SIP/2.0 > CSeq: 2 REGISTER > Via: SIP/2.0/UDP > 178.117.245.74:5060;branch=z9hG4bK1c2c966b-cb80-e011-82e5-00216b30c960;rport > User-Agent: Ekiga/3.2.7 > From: > <sip:[email protected]>;tag=282f826b-cb80-e011-82e5-00216b30c960 > Call-ID: 7a1e826b-cb80-e011-82e5-00216b30c960@maverick > To: <sip:[email protected]> > Contact: <sip:[email protected]>;q=1, > <sip:[email protected]>;q=0.500 > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING > Expires: 3600 > Content-Length: 0 > Max-Forwards: 70 > > > If I use my Android phone, then i have > > > REGISTER sip:ekiga.net SIP/2.0 > Call-ID: [email protected] > CSeq: 8429 REGISTER > From: "Bart.Vandewoestyne" <sip:[email protected]>;tag=4156217873 > To: "Bart.Vandewoestyne" <sip:[email protected]> > Via: SIP/2.0/UDP > 192.168.1.138:45061;branch=z9hG4bK686f4bc2b5692c50ca09b29d1f26e6283531;rport > Max-Forwards: 70 > User-Agent: SIPAUA/0.1.001 > Contact: * > Expires: 0 > Content-Length: 0 > > > The most important differences that I notice are: > > * Ekiga uses the public WAN address of my router in the Via header, whereas my > android phone has the local LAN address and port. > > * Ekiga uses both the public WAN address and the local LAN address in the > Contact header, whereas my Android phone simply sets the '*'-symbol. > > My question to this list is still the same: > > Is this a bug or a missing feature (STUN) in the native Android client, or is > the problem on the ekiga.net server side?
This is something I didn't expect at all - the message your phone sends actually asks ekiga.net to unregister everyone from sip:[email protected]. I can only guess why. It could be that the phone is trying to ensure it is only device registered. Whatever the reason, I expected at least two REGISTER messages - the first with the private IP in both Via and Contact (to discover it's public IP), followed by a second one with the public IP in Contact. The unregister could be a bug, but it is also possible that the phone is using it as a way to get the public IP, but doesn't send the second REGISTER because of the 606 error code. -- Ian _______________________________________________ ekiga-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list
