Re: [Ekiga-list] Invalid Contact header field, or bug in ekiga.net?
- From: Jānis Rukšāns <thedogfarted gmail com>
- To: Ekiga mailing list <ekiga-list gnome org>
- Subject: Re: [Ekiga-list] Invalid Contact header field, or bug in ekiga.net?
- Date: Wed, 27 Oct 2010 18:12:45 +0300
On Tue, Oct 26, 2010 at 11:09 PM, Stuart D Gathman <stuart gathman org> wrote:
> On 10/25/2010 07:38 PM, Stuart Gathman wrote:
>>
>> On Mon, 25 Oct 2010 11:26:40 +0200
>> Eugen Dedu<Eugen Dedu pu-pm univ-fcomte fr> wrote:
>>
>> Send us the whole conversation (REGISTER and 606 answer I suppose).
>>
>>
>>
>> Source: 86.64.162.35 (86.64.162.35)
>> Destination: 192.168.1.105 (192.168.1.105)
>> User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
>> Source port: sip (5060)
>> Destination port: sip (5060)
>> Length: 460
>> Checksum: 0x45c1 [validation disabled]
>> [Good Checksum: False]
>> [Bad Checksum: False]
>> Session Initiation Protocol
>> Status-Line: SIP/2.0 606 Not Acceptable
>> Status-Code: 606
>> [Resent Packet: False]
>> [Request Frame: 122]
>> [Response Time (ms): 95]
>> Message Header
>> CSeq: 8 REGISTER
>> Sequence Number: 8
>> Method: REGISTER
>> Via: SIP/2.0/UDP 192.168.10.6:5060;branch=z9hG4bKf83e1be0-3ade-df11-9109-0017c410a448;rport=5060;received=72.209.xxx.xxx
>>
> How did that 192.168.10.6 get in there? That is probably what ekiga.net is
> complaining about? It is certainly not in the REGISTER packet.
Now something is really strange here. From the trace I guess that your
local (private) IP is 192.168.1.105. If so, the what is the
"192.168.10.6"?? Could it be the case that 192.168.10.6 is your
gateway, trying to be a SIP ALG (Application Level Gateway) by
rewriting packets, and failing badly.
Wherever the 192.168.10.6 came from, it *IS* the reason why ekiga.net
barfs, and that is a *BUG*. Myself and others have complained about
that since long ago, to no avail. *NOWHERE* in the SIP standards it
says that a registrar should barf on private IPs in Via. Even more, it
breaks clients that use SIP outbound + ICE instead of STUN to traverse
NAT (as SIP outbound *REQUIRES* to have non-NATed address in Via).
--
Ian
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]