Re: [Linphone-users] Wrong "via" header IP address

[Simon Morlat]

Hi Casper,

Yes I confirm the behaviour you are observing.
However the server SHOULD be able to answer correctly, despite the via
is not correct. The standarts specifies that received= and rport=
parameters can be added by the server to the via so that responses comes
back normally.
I'm really suprised to see that there are still SIP servers that are
un-aware of received/rport parameters.

Simon

Le mardi 03 août 2010 à 08:35 +0200, Casper Langemeijer a écrit :
> Yes I did.
> 
> For clarification maybe it's good to mention that in the 'Your resulting
> SIP address:' field on the 'Manage SIP Accounts' tab the correct IP
> address is showing (172.24.4.3)
> 
> Linphone detects the correct IP address, it just doesn't put it in the
> 'via' header. The source address of the IP packet is correct
> (172.24.4.3) As you can see below the 'Contact' header also has the
> right IP: <sip:address@hidden>
> 
> Thanks, Casper
> 
> On Tue, 2010-08-03 at 11:44 +0530, Pankaj Chhabra wrote:
> > Hi,
> > 
> > Linphone is still using  192.168.1.22 as the local IP address and not
> > using the address of your ppp0. Did you try restarting Linphone?
> > 
> > Thanks,
> > Pankaj
> > 
> > 
> > On Tue, Aug 3, 2010 at 2:17 AM, Casper Langemeijer <address@hidden> wrote:
> > > Hi All,
> > >
> > > I try to connect from my home through a VPN connection to an asterisk
> > > server. VPN and office network addresses are 172.24.x.x. My local
> > > network is 192.168.1.x
> > >
> > > linphone is advertising 192.168.1.22 (my local network IP) as host in
> > > the "via" header.
> > >
> > > I can see my asterisk server contacting 192.168.1.22 in my office
> > > firewall error log. Apparently it receives the REGISTER packet and
> > > responds to the IP in the "via" header.
> > >
> > > Originally the sender address of the packets was my local network IP as
> > > well. According to bugreport
> > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500512#25 a possible
> > > solution was to add an explicit route to my asterisk server, so I did.
> > >
> > > $ route add 172.24.1.8 ppp0
> > >
> > > It fixed that part of the problem. This seems to be the same issue as
> > > mentioned in this debian bugreport.
> > >
> > > Here is one of the REGISTER packets sent, copied from the Linphone debug
> > > window:
> > >
> > > message: cb_sndreq_retransmission (id=4)
> > > message: eXosip: timer sec:4 usec:10000!
> > > message: DNS resolution with 172.24.1.8:5060
> > > message: getaddrinfo returned the following addresses:
> > > message: 172.24.1.8 port 5060
> > > message: Message sent: (to dest=172.24.1.8:5060)
> > > REGISTER sip:172.24.1.8 SIP/2.0
> > > Via: SIP/2.0/UDP 192.168.1.22:5060;rport;branch=z9hG4bK898566468
> > > From: <sip:address@hidden>;tag=1790236968
> > > To: <sip:address@hidden>
> > > Call-ID: 952225778
> > > CSeq: 4 REGISTER
> > > Contact: <sip:address@hidden>
> > > Max-Forwards: 70
> > > User-Agent: Linphone/3.3.2 (eXosip2/3.3.0)
> > > Expires: 600
> > > Content-Length: 0
> > >
> > > If I can help you by providing any other information, please let me
> > > know.
> > >
> > > Thank you,
> > >
> > > Casper
> > >
> > >
> > >
> > > _______________________________________________
> > > Linphone-users mailing list
> > > address@hidden
> > > http://lists.nongnu.org/mailman/listinfo/linphone-users
> > >
> 
> 
> 
> 
> _______________________________________________
> Linphone-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/linphone-users