The private address in the SDP's o= line is fine. If the far end is
rejecting that then something is broken on their side. The c= line is
all that matters in this case... For the record we do provide the
complete correct SDP to sofia but the lib overrides the o= line and
replaces it. I have narrowed down the exact lines of code that causes
this in soa.c in sofia... I have emailed the author of the lib to ask
why and how to keep sofia from messing with that o= line.
/b
On Jun 4, 2009, at 4:41 AM, Jason White wrote:
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.
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
