Hi, Most of the time you need to register against your provider. When you declare your gateway to provider in the external profile FreeSWITCH will send REGISTER with 5080 port in contact. Provider will send your calls to 5080 because of it. If you don't need to register most probably your provider will ask you for IP to send calls. Don't forget to include 5080 port in that case. The whole concept is really nice since enterprise can have some phones in their LAN and FreeSWITCH will have only private (rfc1918) ip. In the meantime 5080 can be forwarded from the internet via firewall and calls will reach the server without possibility of brute force attacks to 5060. Also you can use different contexts for profile and for users. Regards, Alex On 6/12/18, Rick Jarvis <rick@magicmail.mooo.com> wrote:
Ok kind of FreeSWITCH 101 here I know, but something I’ve never understood completely:
A provider wants to send us calls as number@our-ip-address - fine, but it’s hitting us on port 5060 (whereas external is set up as 5080). So can’t use external, have to use internal profile, right?
So I can create a ACL to allow their IPs onto Internal, ‘inbound’ ACL I think?
But how do I handle call routing for inbound calls from provider’s IPs, vs my registered users dialling out?
If anyone can simplify this for me that would be great :)
Thanks __ R
-- Alex Sibyakin | Support Engineer FreeSWITCH Solutions | 17345 Civic Drive #2531 Brookfield, WI 53045 <https://maps.google.com/?q=17345+Civic+Drive+%232531+Brookfield,+WI+53045&entry=gmail&source=g> Email: alex@freeswitch.com Website: https://www.FreeSWITCH.com <https://www.freeswitch.com/> Need commercial support? Contact sales@freeswitch.com for details.