[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] wrong local address and proxies and routes

From: Simon Morlat
Subject: Re: [Linphone-developers] wrong local address and proxies and routes
Date: Mon, 27 Oct 2008 21:40:52 +0100
User-agent: KMail/1.9.9


Somebody else from asked me the same questions, here is what I 

Unfortunately because of lack of support from the eXosip2 sip stack, linphone 
can only have one ip address in the from, contact, and via fields of the sip 
messages. This IP address is determined by retrieving the local address that 
can connect to the internet.
Fortunately I made some recent improvements in 3.0.0 version, so that linphone 
does a double registration: the second register has contact guessed from the 
rport and received parameters set by the proxy in the first REGISTER's 
So bug 1 is fixed.
For the second one, I don't understand how linphone could use a different 
address in registers and in invites. A log file would help.


Le Thursday 23 October 2008 22:09:19 Nomad Arton, vous avez écrit :
> salu,
> there is a bug reported on the debian version of Linphone 2.1.1 here
> two problems I have with that version below; excuse if they are both
> fixed in the mean time in linphone3.
> 1) linphone sometimes sends a wrong contact address on multihomed
> systems. It gets it from connecting instead of the registrar
> (they may be on different networks!) One may easily fix that by
> modifying the kernel routing table, eg: "route add tap0" and
> the local address of tap0 gets used in a registration.
> 2) even if an outbund proxy is declared in the preferences, linphone
> connects to the registrar directly, and only later call-invites will be
> sent through the proxy. so the proxy does not get a chance to rewrite
> non-routable addresses in the registration.
> FIX: the proxy/registrar pane allows for two hosts: "proxy" and "route".
> linphone should use these to find the local address and also should send
> the registration through the "route".

reply via email to

[Prev in Thread] Current Thread [Next in Thread]