...
The Destinations menus allow to create a destination endpoint with its settings which then can be reused for many routes defined in the Routing plan. The entries in the routing refer to the destinations by name. Each menu let you add a new instance of a given type and manage the existing definitions grouped in the lists.
Gateway
By a gateway we mean here an endpoint which location is known and explicitly provided as an IP address or FQDN. A gateway will not register to voipswitch’s SIP registrar. Usually they are SIP servers, softswitches or PSTN gateways which provide a bridge between SIP and traditional telephony. The gateway type objects are stored in the voipswitch.gateways table.
...
If the carrier has more than one gateway you should create separate entries in the gateways list each with different host address and other details.
Registrar
This type of destination endpoint is for SIP registrars in the meaning that voipswitch itself is the client endpoint registering to the remote registrar server.
...
If the registration is not required you should always use the gateway type.
Lookup
The Lookup is a voipswitch function allowing to run a customized SQL query on voipswitch database or to send an http request to a specified URL. When adding a new lookup entry you have to enter the query string. The variable in the query is the dialed number and several other call details (the full list described further). When a call comes the dialed number is passed to the lookup function which triggers the query. The result is sent back to the routing procedure as a new number so the voipswitch can make a new search in the Routing plan to find the destination for the new number.
...
Enum route
An enum route is a DNS server which resolves phone numbers to SIP URIs. The examples of enum providers are e164.arpa and e164.org. They store information on user’s phone numbers and their mappings to SIP accounts on different domains.
Callback route
The Callback route type instances allow to define different settings of callback services. The instances are triggered by associated with them callback scenarios. More on the Callback configuration in a dedicated chapter further in the document.