Skip to main content

​
Before you start

Neo calls your VigorACS through its RESTful Web Service, at /RestfulWebService/rest/ on the address you open VigorACS at. Neo reaches it over the internet, so it must answer on HTTPS with a certificate from a public certificate authority, at a public address. A VigorACS a DrayTek distributor hosts for you already does. If you host VigorACS yourself, you can allow only Neo’s addresses to reach it.

​
1. Turn on the REST API and create a user for Neo

1

Turn on the web service

In VigorACS, open System > System Parameter and set parameter 38, EnableWebServices, to true. A hosted VigorACS may have it on already; ask your distributor if you cannot see System Parameter.
2

Create the user

In User Management, add a user for Neo with a strong password, and turn on Enable API Service. Pick its role:Reading a router’s own values and rebooting it need a System Administrator.

​
2. Add the user in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations → DrayTek VigorACS, under Networking.
2

Save the address and user

Enter the address you open VigorACS at, with its port when it is not 443 (for example https://acs.example.com:8443), the user name and the password, then click Save settings. Neo signs in and counts your devices before saving, so a wrong address or port, a certificate that is not from a public authority, or a refused user is rejected straight away.
3

Check the Organization Mapping tab

Neo maps your VigorACS networks to your PSA companies. Confirm or correct the matches on the Organization Mapping tab.

​
3. Turn VigorACS on per agent

Open the agent, go to its Tools & Settings tab, click Networking, and expand the DrayTek VigorACS block.

​
Pick a preset

Read Only

Read devices, which are offline, their TR-069 values, networks, user groups and users. Nothing is changed.

Helpdesk

Reads on its own. A reboot, a setting change or any other device change waits on a technician. Every other area is read only.

IT Admin

Devices, TR-069 settings, reboots, networks and user groups change without approval. Provisioning profiles and users wait on a technician.

Full Automation

Every change runs without approval, except the changes that always ask a technician.

​
Or set each area by hand

​
Changes that always ask a technician

These wait on a technician under every profile, whatever the area’s own approval setting:
  • A factory reset.
  • Deleting a network or a user group.
  • Creating, changing or deleting a VigorACS user, adding or removing a user in a group, and the wholesale wizard, which creates a user.
  • Any change that sends a password or a Wi-Fi key: a network’s device sign-in, or a TR-069 value whose name says it is a password or a key.

​
What Neo never sends

  • The wholesale wizard’s delete, which removes every network, device and user of a user group in one call.
  • Deleting the user group RootGroup, or deleting a user group by its id: Neo deletes a user group by its name, so it can tell RootGroup apart.
  • A device delete by name or IP address, which can match several devices: Neo deletes one device by its serial number.

​
Troubleshooting