VoIP Mailing List Archives

[kokoska.rokoska at pos...]

Hi all,

I have just upgarded my (a little bit old FreeSWITCH to current
trunk and now i have troubles with IP addresses in SIP & SDP, while
before upgrade everything work fine...

My FreeSWITCH is behind NAT and all relevant sip profiles have set:

<param name="ext-rtp-ip" value="1.2.3.4"/>
<param name="ext-sip-ip" value="1.2.3.4"/>

But when I send INVITE thru the profile to the gateway associated with
it i see local IP in "Via" header and in SDP "m" line too.
BTW: The "Contact" header is populated with "external" IP (1.2.3.4)

Could you, please, point me how could I modify IP in Via and in SDP?
Thank you.

Best regards,

kokoska.rokoska


_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

[brian at freeswitch.org]

You have to set the local-network-acl on the profile so it knows when
or not to fix up the VIA
/b

On Aug 16, 2009, at 11:41 AM, kokoska rokoska wrote:

[kokoska.rokoska at pos...]

Thank you very much, Brian, for your help!

Now are all IPs correct (BTW: In my previous post I mean "c" line in
SDP, not "m" line). Thanks once more!

Well, signaling works fine, but I still have troubles with RTPs:
I can see with ngrep RTPs going to FreeSWITCH from both legs (a, b) but
there are not outgoing RTPs from FreeSWITCH to any of the call legs.
And, of course, caller and callee hear nothing

Could you, please, help me to solve this? Thanks.

Best regards,

kokoska.rokoska




Brian West napsal(a):

[brian at freeswitch.org]

Ok update in a few I now recall why we had that && !
sofia_test_pflag(tech_pvt->profile, PFLAG_AUTO_NAT) in there.

/b

On Aug 16, 2009, at 2:40 PM, kokoska rokoska wrote:

[kokoska.rokoska at pos...]

Thank you very much, Brian, for your help!

I have just upgraded to curent trunk, but all remains the same - RTPs
from both endpoints arrives to the FreeSWITCH but no RTPs are send back
from FS (using ngrep I can't see even single RTP packet comming from FS).

I think it is due to my misconfiguration, but I have no idea where.

I have trid to blindly modify followed params to (I hope) all possible
values combination (including manual ones , but with no luck:

<param name='apply-nat-acl' value='rfc1918.auto'/>
<param name='local-network-acl' value='localnet.auto'/>
<param name='disable-rtp-auto-adjust' value='false'/>
<param name='rtp-autofix-timing' value='false'/>


Best regards,

kokoska.rokoska


Brian West napsal(a):

[kokoska.rokoska at pos...]

After some testing I found following:

1. When I try to bridge call between endpoints, there are always no RTPs
from FreeSWITCH (like I wrote before).
2. When I just answer call on FS and play something localy (i.e. music)
everything works fine - FS sends RTPs like expected.

All tested with various endpoints (Linksys, Snom, Nokia, Asterisk
and from public IPs, private IPs at foreign LAN, private IPs at the same
LAN as FreeSWITCH is (yes, I have separate profile for phones in the
same LAN). And I found no difference.

Any hint is really appreciated

Best regards,

kokoska.rokoska


kokoska rokoska napsal(a):

[brian at freeswitch.org]

Update, Math refactored the functions that caused some of the problems.

/b

On Aug 17, 2009, at 1:29 AM, kokoska rokoska wrote:

[kokoska.rokoska at pos...]

Brian West napsal(a):

[brian at freeswitch.org]

if all else fails get me access to the machine please.

/b

On Aug 17, 2009, at 9:09 AM, kokoska rokoska wrote:

[kokoska.rokoska at pos...]

Brian West napsal(a):

[brian at freeswitch.org]

shinzon.pub and get on IRC and msg bkw_ and i'll take a look.

/b

On Aug 17, 2009, at 11:46 AM, kokoska rokoska wrote:

[kokoska.rokoska at pos...]

Brian West napsal(a):

[kokoska.rokoska at pos...]

Let me apologize to waste your time, Brian (and others too).

I'm still not 100% sure where problem is, but I'm nearly sure it is not
related to FreeSWITCH.

I found similar problems with SMB - with IPv6 active some clients (even
with only IPv4 stack) can't connect to server. Disabling IPv6 solves the
issue => it has to be network problem...

Thank you very very much for your help!

Best regards,

kokoska.rokoska



kokoska rokoska napsal(a):