|
...
Further in this document, we refer to the standard FreeSWITCH configuration as "vanilla". The vanilla configuration introduces a dialplan that demonstrates lots of FreeSWITCH features, but it takes too much time to clean it up for your future production configuration. Also the vanilla configuration aliases all domains to the server's IPv4 address, making the domain name part in user registrations indistinguishable. The minimal configuration enables the "multi-tenant" scenario, where the domain name part of SIP address makes a difference. Even if you're not planning multiple domains on our FreeSWITCH server, a multi-tenant configuration still has its benefits. One of the benefits is that you can mix SIP users that connect via IPv4 and IPv6 in the same domain and let them communicate to each other.
DNS
...
Configuration
First of all, you need to choose a domain name for your SIP service. Or even better, two different domain names: 1) for internal users to use for SIP client registration; 2) for external SIP peers to send unauthenticated calls to your server.
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
;;; inside the zone file for example.net pbx01 IN A 198.51.100.10 pbx01 IN AAAA 2001:DB8::0A _sip._udp.int IN SRV 10 0 5060 pbx01 int IN NAPTR 110 100 S SIP+D2U "" _sip._udp.int _sip._udp.pub IN SRV 10 0 5080 pbx01 pub IN NAPTR 110 100 S SIP+D2U "" _sip._udp.pub |
Dialplan
...
Contexts
The FreeSWITCH dialplan consists of contexts — independent sets of matching rules and actions for the calls. Each call enters a context, and later it may be transferred to another context, or bridged with some remote party, or a dialplan application can be executed on it according to the matching rules and actions.
...
