...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Enhanced Network Proxy (ENP)
...
Note: If you do not want to duplicate the usernames and passwords on the Vega you can simply trust your entire subnet. This will tell the Vega to accept all registrations from the LAN without requesting a password. If the ITSP is up then a password will be requested from each phone. Only in the event of the ITSP failure will a password not be required from the specified LAN. For details on how to configure this go to http://wiki.sangoma.com/vega-configuration-enp-trust-lan.
...
...
Step 2: Continue scroll down the page until you see the following sections. You can leave the filters empty, but this can be used to white list and blacklist certain IPs. Now go to the SIP ITSP Proxies section and enter your FreePBX's IP and port into the fields provided. You can also decrease the test interval as shown here down to a lower value of 10ms. Decreasing the test interval will cause options messages to be sent to your FreePBX more often, therefore when if the FreePBX goes down ENP will know about this within 10ms. Also ensure proxy test is set to "options".
Step 3 : Scrolling down to the Trunk Gateways section you can enable calls from to and from the PSTN, below all options are set to always to allow all directions. Next ensure the single trunk gateway is "separate" and check of "Is PSTN Gateway?", to ensure the Vega is being used as a trunk. Next you can enable (it is not enabled below) certain numbers like 911, to be dialed out the trunk gateway (FXO/PRI/BRI) directly. This is good for 911 because it will always go out the local POTS line rather than SIP. The last section should be set to "all" in the first column, this indicates that all trunks will be used in failover, so leave this as it is the default.
...