SIP Profiles

A SIP profile is just a couple address/port to which FreeSWITCH is listening.

Let's say our server has IP address 194.20.24.11.
The "internal" SIP profile in example configuration will have FreeSWITCH listen to port 5060. So, the "internal" SIP profile is listening at 194.20.24.11:5060. This is the address/port to which we will make our internal phones to connect, register, authenticate, and send calls to.
Also, in the "internal" SIP profile definition, there is a "param" item, which name is "context" and value is "public". Calls arriving at this address/port will be routed to the "public" context in dialplan.

The "external" SIP profile in demo configuration will be listening at 194.20.24.11:5080. This is the address/port to which we will ask our ITSP to connect and send calls to us (ITSPs do not register themselves, usually they just send calls to us). So, if you need to set this explicitly in your ITSP account, remember to set the "external" SIP profile port, that is 5080 in demo configuration.
Also, in the "external" SIP profile definition, there is a "param" item, which name is "context" and value is "public". Calls arriving at this address/port will be routed to the "public" context in dialplan.

Ouch! What's wrong? Both SIP profiles use the "public" dialplan context, but we saw before that internal users and calls are serviced by the "default" dialplan context. We'll see about this in a moment.