1. Send an Email to Support (support@rabbit.run) requesting to purchase a POTS Kit with the following details for shipping.
   • • Customer Details
       • Customer Organization Name
       • Complete Address
       • Contact Number
     • Shipping Details
       • Contact Person
       • Complete Shipping Address
       • Contact Number
     • Any special requests.
2. Support will process the POTS Kit License and an invoice will be sent to customer for the Kit.

1. For Second ISP Internet Backup sites, the license to be ordered is FALSAFE + Overlay.
   • Note: The license has a 10GB Overlay Bandwidth Monthly allowance included. Usage more than the allocation, an overage fee may apply.

1. For LTE Backup sites, the license to be ordered is FALSAFE LTE + 1GB LTE DATA + Overlay. The 1GB Monthly data and Overlay Add-on are both automatically added to the order when selecting the base license.
   Note: The license has a 1GB LTE Data and 10GB Overlay Bandwidth Monthly allowance included. Usage more than these allocations, an overage fee may apply.

1. RRT-200-LTE
   
2. RRT-300-LTE
   

1. 1. Logged in to the Customer Portal, click on the DEVICES tab to access the Devices Portal.

• Note: The user should be allowed access to the Devices Portal upon creation.

1. Under DEVICES view, click on the PENCIL icon to edit device information.
   
2. Device Section
   • Under DEVICE, edit the Hostname, Location of the site, Organization the device will be assigned to and click on the ACTIVATE THIS DEVICE checkbox upon installation.
     
3. License Section
   • Under LICENSE, check the CHECKBOX of the license and the addon the device was ordered for.
     

If the Partner/Customer wants to be sent Email Alerts 30 minutes and not immediately after a LINK or the DEVICE is DOWN, this can be done with the Escalation Alerts. Escalation Alerts can be setup for 30 minutes, 1 hour or 2 hours.

• Setting up Escalation Alerts.
  1. Click on the Pencil Icon to edit the device information.
  2. Under the ALERTS tab, scroll down to ESCALATION ALERTS
  3. Select the TIME DURATION you want to be sent Email Alerts after the LINK or the DEVICE is DOWN (make sure that LINK STATUS or DEVICE STATUS is selected).
  4. Add the EMAIL ADDRESS you want the alerts to be sent to.
  5. Click on SAVE UPDATE.

1. Logged into the Devices Portal, edit the DEVICE INFORMATION (Pencil Icon).
2. Click on the Alerts Tab.
   
3. Put a check on the Checkbox for the Alerts the user wants to receive notification from.
   • Device Uptime – This alerts the user when the device goes offline.
   • Team Status – This sends an email alert to the registered email when Link1, Link2 or Link3 goes down.
   • Link1 Status – This sends an email alert to the registered email when Link1 goes down.
   • Link2 Status – This sends an email alert to the registered email when Link2 goes down.
   • Link3 Status – This sends an email alert to the registered email when Link3 goes down.
     
4. At the very bottom, type in the email address the user wants to send the alerts to. Multiple emails are accepted provided that they are added individually.
   

1. Organization – This section shows all MSP or Organizations within the MMSP / MSP.
   • New Organizations can also be added by clicking the ADD button.
2. Users – This section shows all users within the MMSP/MSP.
   • New Users can also be added by clicking the ADD button.
     
3. Devices – This section shows all the devices within the MMS/MSP.
   
4. Report – This section shows the Overview Summary of the devices, Licenses, Devices online, etc.
   

1. Device Offline/Online email Alerts
   • Site OFFLINE
     
   • Site ONLINE
     

1. Link(#) down/restore email Alerts.
   • Link(#) DOWN
     
   • Link(#) UP
     

1. Log in to the Device WebUI
   
2. Navigate to SDWAN > ETHERNET PORTS & VLANS
   
3. In the WAN VLAN Configuration, click on EDIT Button of the Interface you want to setup.
   
4. Set PROTOCOL to STATIC.
   
5. Type in the IP ADDRESS, GATEWAY ADDRESS and the SUBNET MASK.
   
6. Click on SAVE.

1. Under CONFIG, click the APN dropdown and type in the preferred APN in the CUSTOM field.
   
2. Click on SAVE & APPLY to make changed and reconnect 4GLTE
   

Carrier Switch by Probe is an RRT feature that allows 4GLTE to automatically cycle through all carriers available and select the network with the most stable MOS.

1. To activate, navigate to SDWAN > TEAM LINKS
2. Under LINK2 Section’s PROBE tab, click on the ENABLE CARRIER SWITCH BY PROBE checkbox. The user can edit the CARRIER FLAP PERIOD and CARRIER MIN MOS as desired.
   
3. Click on SAVE & APPLY
   

1. Navigate to SDWAN > TEAM LINKS
   
2. Under LINK2 Section’s GENERAL tab, click on LINK ACTION dropdown and select BACKUP
3. 
4. At the very bottom of the page, click on SAVE & APPLY
   

1. Under the UTILS tab, click on RESET MODEM
   
2. In the 4GLTE LOGS section, the user should be able to see “reset_4gtle done” message indicating that the modem was successfully reset.
   

LAN Jump is an RRT Service that allows the user to access the UI of a device under the RRT on ports 443 and 80 given that it is enabled on the LAN device.

1. To enbale, navigate to SDWAN > LAN JUMP
2. Edit the DESCRIPTION for the desired name for the device to be accessed.
3. Select the LAN IP of the device the user wants to jump.
4. If the user wants to test which port is allowed in the LAN Device, select the DESTINATION PORT and the PROTOCOL then click on the TEST LAN DEVICE button to see if the port is allowed.
5. Select the time limit for activation, check the ENABLE checkbox and click on SAVE&APPLY.
6. Back at DEVICES PORTAL, a new ICON beside the WEBJUMP and TERMINAL icon should appear. This would allow the user to access the LAN Device setup for LAN JUMP.
7. Clicking the new ICON should lead to the UI of the Device in the Network.

1. Navigate to SDWAN > ETHERNET PORTS & VLANS.
2. Under the LAN VLAN CONFIGURATION Section, click the EDIT button of the interface (LAN, LAN2, LAN3) the user wants to set up.
3. Edit the IPV4 ADDRESS field to the subnet preferred by the user.
   • START and END set the range of the lease.
   • If the user desires to DISABLE the DHCP SERVER of the LAN interface, uncheck the DHCP SERVER ENABLED box.
4. Hit SAVE and SAVE to apply the changes.
5. Hit SAVE and SAVE SWITCH CONFIG buttons to save the changes made.
6. Repeat the process for LAN2 and LAN3 to configure.

1. Navigate to SDWAN > QoS
2. Type in the URLs, IPs, Ports, Networks, etc to all CLASSES of the QoS that the user wants to prioritize traffic of.
   
   • Note: Traffic from CLASS 1 comes first than the traffic from CLASS 2, CLASS 2 first than CLASS 3, etc.
     • Support usually adds phones to CLASS 2 and other apps like POS to CLASS 3.
3. Click on SAVE & APPLY to save the changes.
   

1. Navigate to SWAN > TEAM LINKS
   
2. Under the LINK1 section:
   
   • LINK PATH – Select the INTERFACE the user wants to assign to LINK 1 (ex. WAN,WAN2,4G LTE,MyFi2G,MyFi5G)
   • Description – used to be edited accordingly and give the user a hint of the ISP used for the LINK1 Path (ex. WAN – Spectrum)
   • LINK ACTION – select whether the LINK should be a PRIMARY LINK or BACKUP LINK. The user also has an option to DISABLE the link.
   • LINK TRAFFIC DISTRIBUTION BY WEIGHT – edit as user desires. This assigns the traffic weight to pass on the link.
   • QOS RATE LIMIT – used to limit the OUTBOUND BANDWIDTH of the Link.
   • ESTIMATE UPLOAD SPEED – This action will disable Link1 QoS, do a Speedtest on the Link and give an upload speed result which can be used for the QOS RATE LIMIT.
3. Under the Steering Tab, the user can add the Urls, Ports, etc. that is desired to be steered to LINK1 specifically.
   
4. Under the probe tab:
   • LINK QUALITY – This is the ‘PROFILE’ that sets the sensitivity of the Link for failover. Usually used to desensitize the probes if the site has Internet connection issues.
   • FLAP CHECK – when failed over to BACKUP LINK, the device will check for LINK 1 connectivity. If LINK1 passes the check for duration set in FLAP CHECK, the device will failback to the PRIMARY LINK.
   • TARGET – IP used to send probe packets.
   • FALSE CHECK BW – this prevents failover false positives during high bandwidth usage. Set in K in kbits/sec or M mbits/sec (ex. 1M IN and 100K OUT).
     
5. Click on SAVE AND APPLY at the bottom of the page to save changes made.
   

1. General setup is the same as with LINK1.
2. SAFEGUARD DATA USAGE – When enabled only allows traffic from Class 1 to Class 4 of QoS during a failover to the BACKUP LINK (most commonly set as 4GLTE but can also be set as WAN2).
   
3. Click on SAVE AND APPLY at the bottom of the page to save changes made.
   • Note: This might cause interruption as SDWAN Service will be restarted
     

1. In the LINK 3 Section, click on the STEERING tab.
2. Add the URL, IPs, NETS, etc the user wants to steer through the Overlay.
   • “Source-based steering” and “Trigger Port” steering can also be applied if desired.
     

1. Navigate to SDWAN > WIFI
   
2. Select the AP/GUEST network the user want to enable and configure
   
3. Check the ENABLE checkbox to enable the WIFI AP/GUEST
4. Fill out the details for SSID, PASSWORD and change other details as the user prefers.
   
5.  Click SAVE & APPLY to save the changes.
   

1. WiFi Networks can also be set as SDWAN Links (refer to TEAM LINKS Section to enable WiFi as a Link).
2. To enable 2G and 5G Clients, navigate to SDWAN > WIFI
3. Select the WIFI CLIENT the user wants to enable and configure
   
4. Check the ENABLE checkbox to turn  on the WIFI CLIENT
   
5. Click on the blue SCAN button to see available WiFi Networks to connect to.
   
6. Click the JOIN NETWORK button of the WIFI Network the user wants to connect to.
   
7. Fill out the KEY field.
   • Note: The KEY field in this case is the password of the WiFi Network the user wants to join into.
     
8. Click SAVE & APPLY
   

The RRT RAS can limit users’ access to the network resources by grouping assets (Asset Groups).

1. To addn navigate to SDWAN > ASSET GROUPS
   
   • Click on the DELETE button to remove default Asset Groups if desired.
2. To add a Group, type in the LABEL of the desired asset group in the bottom text field and click on the ADD button.
   
3. Under the Asset Group’s section, click on the IPs dropdown and select the LAN Devices assigned to the group (e.g., DVR IP for Cameras Group, etc.)
   
4. Hit SAVE&APPLY to save all the changes made.

1. Click on the RAS POLICY RULES Tab.
   
2. Click on the ADD button to add another Rule (existing rule can also be edited).
   
3. Type in the name desired for the RULE.
4. Under MATCH RAS GROUP, select the User Group user wants to give access too.
5. Under MATCH LAN GROUP, select the assets the user wants to be given access to.
   
6. Select the PROTO, PORTS, and LIMIT. Select SAVE&APPLY to save the changes.

1. Navigate to SDWAN > RAS.
   
2. Under RAS SERVER TAB, click on the EDIT button.
   
3. Add the PUBLIC STATIC IP or DMZ IP in the RAS ENDPOINT field.
   
4. Click on SAVE to setup the Server.

1. Click on the Add User/Client Tab
   
2. Setup the username and MAC Address of the user as identification.
3. The ALLOWED LAN(s) allows the user to access specific subnets.
4. The ASSIGN TO GROUP assigns the user to a USER GROUP created earlier.
5. Hit SAVE&APPLY to save the user.
   
6. A QR Code and a .conf file will be created which can be scanned with a WIREGUARD Mobile Client or can be downloaded and uploaded to a WIREGUARD Client.

SIPWatch is an RRT Feature that allows the user to view and monitor the SIP Phones connected under the RabbitRun.

1. To enable navigate to SDWAN > SIPWATCH
   
2. Under the CONFIG tab, click the ENABLE SIPWATCH checkbox.
   
   • Modify the PORT RANGE field matching the port phones utilized.
3. Hit SAVE & APPLY.
   

1. Under the WATCHLIST tab, click on CLEARALL to clear all registrations. (FW b28-RC1)
2. Alternatively, the user should also be able to see a GREEN CIRCLE button on each phone listed. Click on it to make the extension re-register. (FW b28-RC1)
   

1. After enabling SIPWATCH, the user should be able to see phones that are registered in the WATCHLIST tab.
   
   • Note: Users will be able to see information of all the phones connected like status, link being used (should show link3 if phone is in the overlay), etc.
2. Click on the plus (+) sign to add the phone to the watchlist.
   • Make sure to have an email setup for alerts in the Portal.
3. Click on SAVE&APPLY

• RabbitRun makes SIP Caller ID Feature built-in and eliminates the need for 3rd Party Caller ID Equipments and Costs!

• How do we enable the SIP Caller IP Feature?

Note: SIPCID cannot be enabled without the SIPCID addon License. To avail of the SIPCID, please send a support email to support@rabbit.run requesting for the SIPCID license (exisiting device) or include the SIPCID addon upon ordering of the device (new orders). SIPCID is available for 4, 6, 10 and 20 simultaneous CID.

• Setting up SIPWATCH for Phones on P1.

Note: It is necessary that the VoIP Phones are on a different LAN. With RabbitRun, we separate the Phones on LAN1 having its own subnet.

1. Once SIPCID License is applied to the device, navigate to SDWAN > SIPWATCH > CONFIG
   1. Click on the ENABLE SIPWATCH box.
   2. Change DELAY START UP to 120.
   3. In the INTERFACE section, select the Port towards the Phones (preferred Phones are plugged into P1 –  in this case select EHTERNET PORT P1)
   4. Select SIP Ports in PORT RANGE (default is 5060-5061).
   5. Hit on SAVE & APPLY at the bottom of the page to apply the changes done.

• SIP Caller ID Setup

1. Navigate to CALLERID CONFIG tab.
   1. Click on the ENABLE CALLER ID box.
   2. Under POS TYPE, select the POS APP/Company of the site.
   3. Select the port that goes to the POS LAN.
      1. IF NO FIREWALL BEFORE  POS DEVICES
         1. Select LAN2 for the BROADCAST PORT.
      2. IF A FIREWALL IS INSTALLED BEFORE THE POS DEVICES
         1. Select LAN3 as the BROADCAST PORT
         2. Disable DHCP Server of LAN3 under SDWAN > ETHERNET PORTS AND VLANS.
         3. Assign P3 an IP from the Subnet of the Firewall (Ex.192.168.100.253 if Firewall subnet us 192.168.100.XXX).
         4. Connect P3 to the Firewall LAN after setting up the Caller ID.
   4. Select the POS Terminal’s listening Protocol (default is UDP)
   5. Select the POS Terminal’s listening Port (default 3520)
   6. Hit SAVE & APPLY at the bottom of the page.
   7. Caller ID Integration should now be enabled.

PowerWatch is an RRT feature that enables the RRT to Monitor a connected UPS via Data Port and setup Alerts for Power Outage and Low Battery Power.

1. To enable, navigate to SDWAN > POWERWATCH
   
2. Under the CONFIGS Tab, click on the ENABLE UPS check box to turn on and the ENABLE ALERT checkbox to turn on the Email alerts notification.
   
   • Note: Please make sure that the UPS used has a DATA PORT and is connected to the RRT’s USB PORT at the back.
3. Click on SAVE & APPLY to save changes.

1. 1. Email alerts will be sent to the Porta-registered email addresses when:
      • Power is cut-off and Battery is in use.
      • Battery power depletes.

1. MTR Utility is found in DIAGNOSTICS Page and under the Network Utilities Section.
2. Select the Link you want to do an MTR from.
3. Type in the destination IP/URL and click on MTR.
   

1. Speedtest Utility is found in DIAGNOSTICS Page and under the Network Utilities Section.
2. Select the Link you wan to speedtest from the dropdown.
3. Select the type of connection type that the interface is using.
4. Select the BOTH for Download adn Upload testing, D for Download only and U for Upload only test.
5. Speedtest results should show as soon as the test is done.

IFSTATS is a utility that shows the user a real-time kbps traffic of all active interfaces (WAN,WAN2,4GLTE,WG1 and LANs).

1. Click on the IFSTATS button.
2. A real-time traffic for the SDWAN Links and LANs will be shown.

LINKFLAPS is a RabbitRun feature that shows the history of the status (Down/Up) of each link in chronological order.

1. Click on the Linkflaps button
2. A table that contains the Chronological sequence of the status of the Links will be shown.
3. The following are the different STATUS of the links
   • DOWN (D)
   • UP (U)
   • Failover (F) – this indicates that the PRIMARY link went down and failed over to the BACKUP Link.
   • Failback (F) – this indicates that the PRIMARY Link came back UP and the BACKUP Link transfers back the traffic.
   • Faildown (F) – this indicates that the Overlay went down and passed traffic over to the underlays.
   • Backup in use (B) – this indicates that the PRIMARY Link failed and that the device is currently using the BACKUP Link

LINKSTATS is a utility that shows the user a real-time statistics of the Active Links (Latency, Jitter, Loss, etc.)

1. Click on the LinkStats button.
2. A table containing the Links’ Statistics that updates every few seconds will be shown.

DIAGNOSTICS contains tools to help the user with the network troubleshooting such as:

• Speedtest
• MTR
• Linkstats – provides real-time  statistics of the active Links
• Linkflaps – shows the ‘flap’ data of all active links.
• Ifstat – displays kbps in/out traffic for all interfaces (WAN,4GLTE, Overlay as well as LANs)

1. To acces the Diagnostics Page, navigate to SDWAN > DIAGNOSTICS.
   
2. Default page shown contains information of the SDWAN and Network Interface.

1. Replace or Keep Existing Firewall / Router
   • All Voice and Data Apps flow through the RabbitRun’s Device – NAT Existing Firewall/LAN
   • 3 x Ethernet Ports for LAN(s), Port Based LANs, VLAN Trunk Support
2. Existing Firewall / Router + New Overly Ips
   • All Voice and Data Apps flow through the RabbitRun’s Device
   • Get Real Overlay Static IP on Existing Firewall from RabbitRun’s Cloud
3. Keep Existing Firewall / Router (Parallel)
   • All Voice and Data Apps flow through the RabbitRun’s Device
   • Existing Firewall can Control Steering (route/policy to RabbitRun device)

1. How will the RRT Device be intalled within the Network?
   • • Replace or Keep Existing Firewall/Router
     • Existing Firewall/Router + New Overlay IPs
     • Keep Existing Firewall/Router (Parallel)
2. Is link1 broadband dhcp or static (Blue WAN port)? If static, please provide the following:
   • • Useable IP
     • Gateway IP
     • Subnet Mask
3. Do you require vlan or port based lan setup?
4. Do you have required LAN Subnet  (RRT uses 192.168.40.1/24 by default for LAN)
5. Which city will the device is to be installed for selecting the appropriate Overlay vHUB?
6. Any other applications require Overlay protection (eg. Phones, POS, etc)?
   • • IPs, Urls, Networks that these apps connect or terminate to.
7. Any other details/requests.