While the o= line shouldn't matter we have fixed sofia to honor the
info we give it and correctly give the right ip in that line also. So
please update to 13621 and see if that corrects your issue.
Thanks,
Brian
On Jun 4, 2009, at 4:41 AM, Jason White wrote:
Michael Jerris <[email protected]> wrote:
Can you please re-test with current svn trunk. we added some new nat
busting code yesterday that may assist with this. You will need to
specify the new <param name="local-network-acl"
value="localnet.auto"/
param in the sofia profile (see
http://fisheye.freeswitch.org/browse/FreeSWITCH/conf/sip_profiles/internal.xml?r1=13389&r2=13595
)
If I apply this to the external profile (using it on the internal
profile has
no effect), the Via headers now receive the external IP address,
i.e., the
publicly routable address provided by the ISP.
However, the session description still has the private address in
it, which
causes the remote end to issue the following:
SIP/2.0 488 Invalid Session Description
Warning: 301 203.2.134.1 "invalid transport IP address"
I assume (but may be wrong - full traces can be provided if
necessary) that
the problem is in the SDP that we're sending out:
o=FreeSWITCH 7801931346801551648 4196891485744912323 IN IP4
192.168.0.2
Can this be fixed up?
Thanks.
Jason.
_______________________________________________
Freeswitch-users mailing list
[email protected]
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
Brian West
[email protected]
-- Meet us at ClueCon! http://www.cluecon.com
_______________________________________________
Freeswitch-users mailing list
[email protected]
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
