[Freeswitch-users] doublenat outgoing call issue

Sun Mar 14 11:41:48 PDT 2010

Hi Bruce/Brian, 

Success on my side too! 

Thanks for sharing your experience. I too reset my FS and made minimal
changes to my config. Voila! 

Anyone new to FS, and running it on Windows server- I strongly recommend you
pull a copy of Wireshark off the net. It has great tools for analysing
SIP/IP packets. 

I'll be adding my config and service provider setup to the wiki this week. 

Rgds

From: freeswitch-users-bounces at lists.freeswitch.org
[mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Bruce
Hopkins
Sent: 14 March 2010 12:57 AM
To: freeswitch-users at lists.freeswitch.org
Subject: Re: [Freeswitch-users] doublenat outgoing call issue

Hi Roly,

I promised I'd let you know when I got it working - so here it is:

As Brian said, doublenat is no longer needed.

It looks like I must have just been confusing things horribly by using
various things I'd read about, including:

<variable name="sip-force-contact" value="NDLB-connectile-dysfunction"/>

<param name="aggressive-nat-detection" value="true"/>

These, and who knows what other mucking about I had been doing, must have
confused everything as none of this is now necessary.

All I did - after a reinstall - to get everything working through double
NATs is:

1.  In vars.xml 

<X-PRE-PROCESS cmd="set" data="external_rtp_ip=<my.fs.ext.ip>"/>

<X-PRE-PROCESS cmd="set" data="external_sip_ip=<my.fs.ext.ip>"/>

2.  Then in prefix/sip_profiles/internal.xml

<param name="ext-rtp-ip" value="$${external_rtp_ip}"/>

<param name="ext-sip-ip" value="$${external_sip_ip)"/>

Then as the man says, it just works.  

I decided not to enable options pings to keep the far-end NAT open to enable
calling the remote phone - instead I configured it to send keep-alives.

And that's it.  I can't believe the knots I was tying myself in.  It just
works !

cheers

Bruce

On 9 March 2010 19:08, Roly Maz <rm at callrica.co.za> wrote:

Ah I see... what? Please share and lead this blind man out the FS
wilderness!

I don't understand...what happens to the external profile? Do you delete it?
And how do you forward port 5060?

...and you thought you were a newbie!

Any insight would be much appreciated...loving the journey.

-----Original Message-----
From: freeswitch-users-bounces at lists.freeswitch.org
[mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Bruce
Hopkins
Sent: 09 March 2010 08:23 AM
To: freeswitch-users at lists.freeswitch.org
Subject: Re: [Freeswitch-users] doublenat outgoing call issue

Ah I see.  I will try again using the internal profile and forwarding
port 5060.  Presumably still creating a directory entry to enable the
outside-facing domain to be used.

Many thanks for your patient help of a newbie Brian.

Cheers
Bruce

Please excuse the brevity - sent from my mobile.

On 8 Mar 2010, at 17:21, Brian West <brian at freeswitch.org> wrote:

> ok you aren't catching one key thing here.. you no longer need two
> profiles.
>
> /b
>
> On Mar 8, 2010, at 11:12 AM, Bruce Hopkins wrote:
>
>> Hi again,
>>
>> Thanks for the help so far.  Unfotrunately I must still be doing
>> something wrong here as I am still having difficulty, and still
>> have the same problem.
>>
>> I updated to build 16938 by means of "make current"
>>
>> I'm not able to use UPNP or NATPMP so changed the port forwarding
>> to use 5080 instead of 5090.
>>
>> I got rid of the doublenat profile in sip_profiles, though I had to
>> retain an entry in the directory /usr/local/freeeswitch/conf/
>> directory/ext_dns.xml in order to give freeswitch the dns name of
>> the server as a domain for the remote softphone to register on.  I
>> left the group name in this entry the same as inthe default entry,
>> so that the remote phone could register on the same extension
>> numbers (100, etc) as in the default build.
>>
>> I still find that, if I initiate a call from the local (on same LAN
>> as freeswitch) phone to the remote phone, I get the message on the
>> CLI:
>>
>> [ERR] switch_ivr_originate.c2389 Cannot create outgoing channel of
>> type [user] cause: [USER_NOT_REGISTERED]
>>
>> One possibly unrelated aside, I also found I needed to uncomment
>> <param name="aggressive-nat-detection" value="true"/> in
>> external.xml, otherwise in the case of a call initiated by the
>> remote phone being hung up by the local phone, freeswitch sent the
>> BYE to the private IP of the remote phone, rather than its public
>> ip - meaning that the remote phone didn't receive the BYE.
>>
>> Any further ideas where I am going wrong here please?
>>
>> thanks again in advance
>> Bruce
>
>
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-
> users
> http://www.freeswitch.org

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

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20100314/9f6b3b0c/attachment-0002.html 