OK - I have put a Wireshark trace across the router between FS and the internet, and it will not surprise you to hear that when I tried ot call from LAN-->WAN, FS was sending packets to the private IP of the remote phone (behind its own NAT).<br>
<br>So how to sort this?<br><br>I tried:<br><br>1. Commenting these out in the internal profile<br><br><!--all inbound reg will look in this domain for the users --><br> <!--<param name="force-register-domain" value="$${domain}"/>--><br>
<!--force the domain in subscriptions to this value --><br> <!--<param name="force-subscription-domain" value="$${domain}"/>--><br> <!--all inbound reg will stored in the db using this domain --><br>
<!--<param name="force-register-db-domain" value="$${domain}"/>--><br><br>2. then creating a n antry in the directory refering to the same default group of extensions as the default.xml, but with:<br>
<domain name="dns.aname.for.FS"><br><br>and in the variables:<br><br> <variable name="sip-force-contact" value="NDLB-connectile-dysfunction"/><br><br>which I hoped from what I read in the Wiki might do the trick vis a vis forceing FS to send the SIP packets to the public IP of the remote phone. <br>
<br>Alas it does not seem to work, and even phoning in from the WAS -->LAN now I see USER_NOT_REGISTERED errors . I get the same error in both directions.<br><br>Please please please could somebody put me out of my (your ;-) ) misery here ....?<br>
<br>What do I configure to tell FS to send outbound INVITE's to the public IP the remote phone registered from behind, rather than its private NAT'ed ip?<br><br>many thanks in advance.<br>Bruce<br><br><br><br><br>
<div class="gmail_quote">On 10 March 2010 22:04, Bruce Hopkins <span dir="ltr"><<a href="mailto:jbrucehopkins@gmail.com">jbrucehopkins@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Interestingly I <u>can</u> call outbound to the WAN a SIP client registered with FS via Fring. I wonder if Fring have some additional nat traversal/SBC malarkey going on as they proxy the calls.<br><br>I can't call outbound to an Eyebeam softphone registered directly wth FS though - although said Eyebeam is registered and can call inwards.<br>
<br>I must have my nat handling configured wrongly.<br><font color="#888888"><br>B</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">On 10 March 2010 21:28, Bruce Hopkins <span dir="ltr"><<a href="mailto:jbrucehopkins@gmail.com" target="_blank">jbrucehopkins@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hey Roly,<br><br>Are you getting anywhere? I'm still struggling, I'm afraid.<br><br>
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.<br>
<br>In sip_profiles/internal.xml I have:<div><br><br> <param name="aggressive-nat-detection" value="true"/><br></div><param name="ext-rtp-ip" value="$${external_rtp_ip}"/><br>
<param name="ext-sip-ip" value="$${external_sip_ip}"/><br>
<br><!-- the external_rtp_ip etc being defined in vars.xml --><br><br><br>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. <br>
<br>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.<br>
<br>Any thoughts?<br><br>cheers<br><font color="#888888">Bruce</font><div><div></div><div><br><br><br><br><br><br><br><div class="gmail_quote">On 10 March 2010 12:00, Bruce Hopkins <span dir="ltr"><<a href="mailto:jbrucehopkins@gmail.com" target="_blank">jbrucehopkins@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>Hi Roly,</div>
<div> </div>
<div>I hope to be able to have a go at this later today. I'll let you know what happens.</div>
<div> </div>
<div>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.</div>
<div> </div>
<div>cheers</div>
<div>Bruce<font color="#888888"><br><br></font></div><div><div></div><div>
<div class="gmail_quote">On 9 March 2010 19:08, Roly Maz <span dir="ltr"><<a href="mailto:rm@callrica.co.za" target="_blank">rm@callrica.co.za</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">Ah I see... what? Please share and lead this blind man out the FS<br>wilderness!<br><br>I don't understand...what happens to the external profile? Do you delete it?<br>
And how do you forward port 5060?<br><br>...and you thought you were a newbie!<br><br>Any insight would be much appreciated...loving the journey.<br>
<div>
<div></div>
<div><br>-----Original Message-----<br>From: <a href="mailto:freeswitch-users-bounces@lists.freeswitch.org" target="_blank">freeswitch-users-bounces@lists.freeswitch.org</a><br>[mailto:<a href="mailto:freeswitch-users-bounces@lists.freeswitch.org" target="_blank">freeswitch-users-bounces@lists.freeswitch.org</a>] On Behalf Of Bruce<br>
Hopkins<br>Sent: 09 March 2010 08:23 AM<br>To: <a href="mailto:freeswitch-users@lists.freeswitch.org" target="_blank">freeswitch-users@lists.freeswitch.org</a><br>Subject: Re: [Freeswitch-users] doublenat outgoing call issue<br>
<br>Ah I see. I will try again using the internal profile and forwarding<br>
port 5060. Presumably still creating a directory entry to enable the<br>outside-facing domain to be used.<br><br>Many thanks for your patient help of a newbie Brian.<br><br>Cheers<br>Bruce<br><br>Please excuse the brevity - sent from my mobile.<br>
<br>On 8 Mar 2010, at 17:21, Brian West <<a href="mailto:brian@freeswitch.org" target="_blank">brian@freeswitch.org</a>> wrote:<br><br>> ok you aren't catching one key thing here.. you no longer need two<br>
> profiles.<br>
><br>> /b<br>><br>> On Mar 8, 2010, at 11:12 AM, Bruce Hopkins wrote:<br>><br>>> Hi again,<br>>><br>>> Thanks for the help so far. Unfotrunately I must still be doing<br>>> something wrong here as I am still having difficulty, and still<br>
>> have the same problem.<br>>><br>>> I updated to build 16938 by means of "make current"<br>>><br>>> I'm not able to use UPNP or NATPMP so changed the port forwarding<br>>> to use 5080 instead of 5090.<br>
>><br>>> I got rid of the doublenat profile in sip_profiles, though I had to<br>>> retain an entry in the directory /usr/local/freeeswitch/conf/<br>>> directory/ext_dns.xml in order to give freeswitch the dns name of<br>
>> the server as a domain for the remote softphone to register on. I<br>>> left the group name in this entry the same as inthe default entry,<br>>> so that the remote phone could register on the same extension<br>
>> numbers (100, etc) as in the default build.<br>>><br>>> I still find that, if I initiate a call from the local (on same LAN<br>>> as freeswitch) phone to the remote phone, I get the message on the<br>
>> CLI:<br>>><br>>> [ERR] switch_ivr_originate.c2389 Cannot create outgoing channel of<br>>> type [user] cause: [USER_NOT_REGISTERED]<br>>><br>>> One possibly unrelated aside, I also found I needed to uncomment<br>
>> <param name="aggressive-nat-detection" value="true"/> in<br>>> external.xml, otherwise in the case of a call initiated by the<br>>> remote phone being hung up by the local phone, freeswitch sent the<br>
>> BYE to the private IP of the remote phone, rather than its public<br>>> ip - meaning that the remote phone didn't receive the BYE.<br>>><br>>> Any further ideas where I am going wrong here please?<br>
>><br>>> thanks again in advance<br>>> Bruce<br>><br>><br>> _______________________________________________<br>> FreeSWITCH-users mailing list<br>> <a href="mailto:FreeSWITCH-users@lists.freeswitch.org" target="_blank">FreeSWITCH-users@lists.freeswitch.org</a><br>
> <a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>> UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-</a><br>
> users<br>> <a href="http://www.freeswitch.org/" target="_blank">http://www.freeswitch.org</a><br><br>_______________________________________________<br>FreeSWITCH-users mailing list<br><a href="mailto:FreeSWITCH-users@lists.freeswitch.org" target="_blank">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org/" target="_blank">http://www.freeswitch.org</a><br><br><br>_______________________________________________<br>FreeSWITCH-users mailing list<br><a href="mailto:FreeSWITCH-users@lists.freeswitch.org" target="_blank">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org/" target="_blank">http://www.freeswitch.org</a><br></div></div></blockquote></div><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>