Hey Roly,

Are you getting anywhere?  I'm still struggling, I'm afraid.

I'm able to call from WAN --> LAN using the internal profile on port 5060, but I still can't call out from LAN --> WAN so there is obviously something really basic I'm still not getting.

In sip_profiles/internal.xml I have:

 <param name="aggressive-nat-detection" value="true"/>
<param name="ext-rtp-ip" value="$${external_rtp_ip}"/>
<param name="ext-sip-ip" value="$${external_sip_ip}"/>

<!-- the external_rtp_ip etc being defined in vars.xml -->


In this example I have left <param name="force-register-domain" value="$${domain}"/> etc uncommented to force the registration to go to default.xml in the dialplan. 

I thought maybe this was my problem and tried putting a separate file in the directory to enable the WAN phone to register using the external DNS name for the server as its domain, and uncommenting force-register-domain, etc.  But then I got an error saying that the local (to Freeswitch) phone in the LAN was not registered when I tried to make the call from the WAN.

Any thoughts?

cheers
Bruce






On 10 March 2010 12:00, Bruce Hopkins <jbrucehopkins@gmail.com> wrote:
Hi Roly,
 
I hope to be able to have a go at this later today.  I'll let you know what happens.
 
I have my FS box behind a hardware router/firewall, so I'm assuming I just forward SIP port 5060 from the WAN to the FS box and use internal profile, instead of using external profile with port 5080 forwarded as I have at the moment.  We'll see what happens.
 
cheers
Bruce

On 9 March 2010 19:08, Roly Maz <rm@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@lists.freeswitch.org
[mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Bruce
Hopkins
Sent: 09 March 2010 08:23 AM
To: freeswitch-users@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@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@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@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@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org