Really really really appreciate that. Thank you so much. Yep. I've been doing pretty much all of that for several weeks now and things are actually starting to gell now. It looks like the issue may wind up being this consumer grade router that is forwarding external traffic to 5060. All it has are built-in rules without logging or option to create a custom rule. I should have wiresharked this days ago but being new to all of this I thought I just didn't have the config's right. But thanks to everyone's help, documentation, and this awesome book, it looks like the router is the last place this issue can be hiding out. I'll set it to bridge and pass everything to a different device and wireshark the traffic too. I'll get there. Many many thanks for taking the time to point out those things. Really appreciate it. Best regards, Nate On Wed, Aug 9, 2017 at 4:18 PM, jungle boogie <jungleboogie0@gmail.com> wrote:
Thus said Nate on Wed, 9 Aug 2017 13:53:56 +1200
Many thanks for that JB, I had already reviewed those variables under SIP profiles, but it wasn't clear what to change.
Both internal/external profiles are enabled (which seems appropriate).
yes, you want both enabled but re-read what Giovanni wrote, then compare your vars.xml to this one: https://freeswitch.org/stash/projects/FS/repos/freeswitch/br owse/conf/vanilla/vars.xml
lines 422 & 428. Do they match? external calls go to the public profile, port 5080 by default.
2017-08-09 10:13:51.482817 [WARNING] sofia_reg.c:1792 SIP auth challenge (INVITE) on sofia profile 'internal' for [6468808998@newplymouth.poiema .org] from ip 192.241.183.87
That's a public IP.
You'll want to read page 45 of the latest freeswitch book under the heading of Extensions, Contexts and Profiles.
On the other hand, the calls that are incoming to a profiles with a public Internet address, that is the calls that are reaching us passing through the router from the outside of our internal LAN, those calls are directed to a context that only allows for the call to be connected to one of our coworkers' phone. This specific profile will have only the feature to allow for external incoming calls to reach an internal phone, without any possibility to originate PSTN calls. That is, strangers cannot use our paid gateway to reach the PSTN. So, different address:port couple, different profile, different context. It is actually so simple!
Check out the diagram on freeswitch here: https://freeswitch.org/confluence/display/FREESWITCH/Default+Configuration
I wouldn't think to swap ports or anything like that.
Can anyone suggest anything else?
Again, many apologies that I am so lacking of knowledge here. I really have been reading and researching for a long time.
It's not an easy concept to grasp at first, so read the book a few times, check out the confluence pages, read the mailings list.
public inbound DIDs go here: /usr/local/freeswitch/conf/dialplan/public/
outbound DIDs go here: /usr/local/freeswitch/conf/dialplan/default/
external registrations (to ITSP) go here: /usr/local/freeswitch/conf/sip_profiles/external/
If you installed freeswitch from a package,the locations will vary (as pointed out in the book), so adjust accordingly.
Many thanks again to everyone.
Nate
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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