I just pushed to svn and git a possible workaround: it restarts the register with the real local address as seen by the server, after the 404 failure. So the expected behaviour should be first the same 404 error, then a second register going to the server, but this time with correct contact information.
Unfortunately I have no server on my hands to test with for this use case. At least I could verify this patch does not break the behaviour for the main case. Can you do the test and send me back the log in case of failure again ? Thanks Simon Le mardi 1 septembre 2009 15:32:21, Matěj Cepl a écrit : > Dne 1.9.2009 09:52, Simon Morlat napsal(a): > > Indeed. > > Thank you Enrique. The modification I did was that the hostname/ipaddress > > given as firewall address is used within SIP messages (before it was only > > used in SDP). > > Note that this should not be necessary to do all that if the SIP proxy is > > NAT- capable. If using openser and its clones, you have to use a > > configuration that uses "nat_helper". I can provide one if needed. > > I am sorry, but I tried with the today's git checkout > (6b23aeb56f16a39d6a0c960a0dc3242b0c06c2a8, that's svn 615 if I > understand the URL correctly) and the result is exactly the same (both > with and without STUN). Not found for registration and service not > available for calling, and linphone seems to suggest that it is actually > on 192.168.1.*. See attached logs. > > Best, > > Matěj _______________________________________________ Linphone-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/linphone-users
