Re: [Ekiga-list] Invalid Contact header field, or bug in ekiga.net?

[Eugen Dedu <Eugen Dedu pu-pm univ-fcomte fr>]

On 25/10/10 04:27, Stuart Gathman wrote:
> I am new at SIP, but I got tired of googling to try and find why I keep getting 606 from ekiga.net, and dived into the protocol myself with wireshark and RFC3261.  So feel free to correct me.
>
> STUN is used, and returns the correct public IP and port.  Ekiga doesn't use the port (assuming consumer nat with port forwarding, I guess).
>
> The REGISTER packet contains this Contact header field:
>
> Contact:<sip:SDGathman 72 209 xxx xxx>;q=1,<sip:SDGathman 192 168 1 105>;q=0.500
>
> RFC3261 section 8.1.1.8 says there can be only one sip uri, but that seems to be for INVITE only (and 10.3 talks about iterating over all sip uris).  So I believe that ekiga.net is barfing on the private ip in the 2nd contact.  Other services seem to ignore it, including ekiga call-out (sip.diamondcard.us).  ekiga.net gives this response:
>
> Status-Line: SIP/2.0 606 Not Acceptable

I do not think the error comes from Contact, since I have myself:
REGISTER sip:ekiga.net SIP/2.0
[...]
Contact: <sip:eugen dedu 169 254 8 166>;q=1, 
<sip:eugen dedu 82 238 108 175>;q=0.667, 
<sip:eugen dedu 192 168 0 1>;q=0.334

and ekiga works.

You said something about ekiga not using the advertised port.  Such a 
bug was fixed in ekiga 3.2.7, do you use this version or more ancient 
one?  However, that bug prevented the packet to reach ekiga client, not 
making the sender send 606...

Send us the whole conversation (REGISTER and 606 answer I suppose).

--
Eugen