edgerouterx section created, other updates on content and images (#161)

* image add * edit image path * Update advanced_dialplans.rst * Update advanced_dialplans.rst * Update destinations.rst * Update firewall_devices.rst * Update firewall_devices.rst * Update firewall_devices.rst * Create edgerouterx.rst * ubnt images add * Update edgerouterx.rst * Update edgerouterx.rst * ubnt image upload * Update other.rst
fusionpbx · Dec 8, 2018 · 4456938 · 4456938
1 parent 0a7eea5
commit 4456938
Show file tree

Hide file tree

Showing 11 changed files with 90 additions and 0 deletions.
diff --git a/source/_static/images/dialplan/fusionpbx_dialplan_destination.jpg b/source/_static/images/dialplan/fusionpbx_dialplan_destination.jpg
diff --git a/source/_static/images/firewall/fusionpbx_ubnt_edgerouterx.jpg b/source/_static/images/firewall/fusionpbx_ubnt_edgerouterx.jpg
diff --git a/...ges/firewall/fusionpbx_ubnt_firewall_policies_enable_outside_lan_gui_access.jpg b/...ges/firewall/fusionpbx_ubnt_firewall_policies_enable_outside_lan_gui_access.jpg
diff --git a/...es/firewall/fusionpbx_ubnt_firewall_policies_enable_outside_lan_gui_access1.jpg b/...es/firewall/fusionpbx_ubnt_firewall_policies_enable_outside_lan_gui_access1.jpg
diff --git a/source/_static/images/firewall/fusionpbx_ubnt_port_forward.jpg b/source/_static/images/firewall/fusionpbx_ubnt_port_forward.jpg
diff --git a/source/_static/images/firewall/fusionpbx_ubnt_static_route_other_router.jpg b/source/_static/images/firewall/fusionpbx_ubnt_static_route_other_router.jpg
diff --git a/source/dialplan/advanced_dialplans.rst b/source/dialplan/advanced_dialplans.rst
@@ -36,6 +36,14 @@ Once you enter data into the empty fields at the bottom and click save, more bla
         :scale: 85%
 
 
+Enable a Dialplan Destination
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Dialplans that have a value in the **Number** filed can be enabled and used in `Dialplan > Destinations <../dialplan/destinations.html>`_. Setting the **destination** field to **True** will enable the dialplan to be visable and used as an action in `Dialplan > Destinations <../dialplan/destinations.html>`_.
+
+.. image:: ../_static/images/dialplan/fusionpbx_dialplan_destination.jpg
+        :scale: 85%
+
 Dialplan example
 ^^^^^^^^^^^^^^^^^^
 

diff --git a/source/dialplan/destinations.rst b/source/dialplan/destinations.rst
@@ -36,6 +36,8 @@ To add a destination **click** on the **plus** button on the right.
 * **Destination:** This is usually the DID a caller will call.
 * **Context:**  This will usually be public.
 * **Actions:** Choose where the call will go after it enters FusionPBX.
+        * Dialplans can also be used as an action. To enable a dialplan to be visable go to `Dialplan > Dialplan Manager <../dialplan/advanced_dialplans.html#enable-a-dialplan-destination>`_ and edit a dialplan.  Select **True** from the **Destination** field and click save.  This applies to dialplans that have a value in the **Number** field.
+
 * **Caller ID Name Prefix:** Adds a name to the Caller ID that will display to the endpoint and call detail records.
 * **Record:** Record all calls made to the destination.
 * **Account Code:** Used in some billing systems.

diff --git a/source/firewall/firewall_devices.rst b/source/firewall/firewall_devices.rst
@@ -11,6 +11,7 @@ Firewall device settings that help with SIP connections.
 * `Sonicwall_TZ_Soho-`_
 * `Zyxel-`_
 * `pfSense`_
+* `Ubnt EdgerouterX`_
 
 
 
@@ -49,5 +50,6 @@ Most of the time this setting is set to off or disabled and varies.  Rarely this
 .. _Sonicwall_TZ_Soho: http://docs.fusionpbx.com/en/latest/firewall/firewall_devices/sonicwall_tz_soho_sip_alg.html
 .. _Sonicwall_TZ_Soho-: http://docs.fusionpbx.com/en/latest/firewall/firewall_devices/sonicwall_tz_soho.html
 .. _pfSense: http://docs.fusionpbx.com/en/latest/firewall/firewall_devices/pfsense.html
+.. _Ubnt EdgerouterX: http://docs.fusionpbx.com/en/latest/firewall/firewall_devices/edgerouterx.html
 
 
diff --git a/source/firewall/firewall_devices/edgerouterx.rst b/source/firewall/firewall_devices/edgerouterx.rst
@@ -0,0 +1,77 @@
+######################
+Ubiquity EdgerouterX
+######################
+
+
+Ubiquity EdgerouterX Advanced Gigabit Ethernet Router.
+
+.. image:: ../../_static/images/firewall/fusionpbx_ubnt_edgerouterx.jpg
+        :scale: 85%
+
+
+Port Forwarding
+^^^^^^^^^^^^^^^^^
+
+Go to top first menu item Firewall/NAT then second top menu item Port Forwarding.
+
+.. image:: ../../_static/images/firewall/fusionpbx_ubnt_port_forward.jpg
+        :scale: 85%
+
+
+* Optional: SSH port 22 is optional.
+* Required: Sip port range 5060-5090 is recomended.
+* Required: HTTPS port 443 is required in order to access your FusionPBX installation and phone provisioning.
+* Optional: HTTP port 80 is used by some phone manufactures for provisioning.
+* Required: RTP port range 16384-32768.
+
+.. note::
+       In order to Port Forward and still have access to the EdgerouterX GUI you must change the port number for the EdgerouterX GUI.
+
+
+
+
+Access from another LAN Subnet
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+If you are behind NAT and are going to use the EdgerouterX subnet in addition to an existing subnet (behind another router) also some setting changes are required. These settings are only recommended in this scenerio.
+
+* Go to First top menu Firewall/NAT tab.
+* Go to Second top menu Firewall Policies.
+* Edit WAN_LOCAL at the right menu item Actions > Edit RuleSet 
+
+
+.. image:: ../../_static/images/firewall/fusionpbx_ubnt_firewall_policies_enable_outside_lan_gui_access.jpg
+        :scale: 85%
+
+
+
+* From the Configuration tab, Change the radio button to "Accept" and click "Save Ruleset".
+
+
+.. image:: ../../_static/images/firewall/fusionpbx_ubnt_firewall_policies_enable_outside_lan_gui_access1.jpg
+        :scale: 85%
+
+
+.. warning::
+         Be sure you want to do this and that you are behind either a firewall appliance or another router.
+
+
+Add Static Route (Double NAT)
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+This will look different depending on the other router that you might have and what IP range you use.
+
+* A static route is needed on the other router in order for traffic to reach your FusionPBX installation and is only needed if the EdgerouterX is the double NAT.
+
+Scenerio: Router A is the primary router that has a public IP address and a LAN subnet of 10.10.2.1. From this pool of IP addresses, the EdgerouterX gets IP 10.10.2.209. *Be sure that router A has DHCP reservation or the ability to make 10.10.2.209 a static IP*. 
+
+* **Router A Router name:** This is a label for organizing.
+* **Router A Destination IP address:** 192.168.1.38 This is the IP that the EdgerouterX gave to your FusionPBX install.
+* **Router A Subnet mask:** 255.255.255.0 is the subnet mask used in this example.
+* **Gateway:** 10.10.2.209 is the IP Router A gave to the EdgerouterX WAN eth0.
+* **Interface:** LAN is a label on Router A to show it's a local area network address.
+
+.. image:: ../../_static/images/firewall/fusionpbx_ubnt_static_route_other_router.jpg
+        :scale: 85%
+
+
diff --git a/source/other.rst b/source/other.rst
@@ -18,6 +18,7 @@ Other section is bits of info that needs indexed for the PDF to populate all sec
   firewall/firewall_devices/asus_rt_ac66u.rst
   firewall/firewall_devices/asus_rt_ac66u_sip_alg.rst
   firewall/firewall_devices/cisco_ea6500.rst
+  firewall/firewall_devices/edgerouterx.rst
   firewall/firewall_devices/pfsense.rst
   firewall/firewall_devices/sonicwall_tz_soho.rst
   firewall/firewall_devices/sonicwall_tz_soho_sip_alg.rst