I think the problem is only that linphone does not uses the port given in the STUN response. It implicitely assumes no port changes occurs when going through the firewall, which is in several case wrong: if the nat is a windows machine, if the port is already used on the firewall, then the firewall chooses another one.
The stun support in linphone is still experimental, there are lots of things to do, such as ICE support that are planned for next months. Sorry for this trouble. However this problem should not produce with equipments that assume symmetric-RTP and thus always return audio back to the port it comes from. This is the case of linphone and freephonie.net's gateways. Simon Le mercredi 23 mai 2007 17:58, Stefan Schwarzer a écrit : > Hi Luca, > > On 2007-05-23 16:13, Luca Olivetti wrote: > > If you remember I reported a similar issue with eutelia (private > > address in the sip headers, but not in the call setup data): > > http://thread.gmane.org/gmane.comp.voip.linphone.user/2337 > > Eutelia now accepts the "broken" headers but it didn't at the time, so > > I couldn't register. > > There was no problem with call setup and another provider, though, so > > maybe it's not the same problem. > > Stefan, you could try to hardcode your public ip address in > > exosip/jrequest.c, function generating_request_out_of_dialog, variable > > locip. If that works it's probably the same problem. > > Setting the IP address in jrequest.c doesn't seem to have an > effect. Setting it manually ("Specify firewall address manually") > doesn't seem to work either. > > Stefan > > > _______________________________________________ > Linphone-users mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/linphone-users _______________________________________________ Linphone-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/linphone-users
