Administration
Integrations
Connect DCM and other systems to pull customers, routers and online status automatically.
What this page is for #
Connects the app to DCM, the billing system. Once connected, the app pulls from DCM, by itself:
- customers (Data, MAC and Corporate) with package, expiry, manager, POP, balance and account status;
- their online status and the router MAC of their session;
- the routers (NAS) known to DCM.
Customers are then linked to their ONUs automatically, so Customers and the ONU lists show names instead of only serial numbers. In the other direction, DCM reads ONU status and power from this app to show them to support staff.
- 1 API URL, key and signing secret of the DCM server.
- 2 Sync automatically every so many minutes.
- 3 Test connection checks the address and the credentials.
- 4 Sync now pulls everything once, in the background.
Connect DCM #
- Get three values from the person who runs the DCM server: the API URL, the API key and the signing secret. (The box “How it works” on the page tells them how to create these.)
- Enter them and press Save.
- Press Test connection. A green message means the two systems can talk.
- Press Sync now for the first pull. The card shows “queued”, then “running” with progress.
- Tick Sync automatically and set the minutes (for example 60) so it repeats.
Connect another system #
Besides DCM, the app can pull customers and routers from any other system (for example a RADIUS log or another billing program), as long as that system offers the same kind of connection. Its developers build it from the developer guide.
Hand the developer guide to the other team
- Open Integrations.
- Press Developer guide at the top to read it, or PDF to download it.
- Send the PDF to the developers of the other system. When they are done they give you an API URL, an API key and a signing secret.
Add the other system
- In the card Add a data source, type its name (for example “Mazeda user data”) and press Add.
- A new card appears. Enter the API URL, key and secret and press Save.
- Press Test connection. The green message also says what the system offers (customers, routers, online status).
- Press Sync now, then tick Sync automatically.
Reading the status #
| Status | Meaning |
|---|---|
| Queued / Running | A pull is waiting or in progress. A very large customer base is pulled in parts; it continues by itself until done. |
| Success | Everything arrived; the numbers of customers added, updated and linked are shown. |
| Partial | One list could not be fetched (the error is shown). The rest was imported, and nobody is removed when a list is incomplete. |
| Failed | DCM could not be reached or refused the credentials. Use Test connection. |
What the pull does to your data #
- DCM (and every other connected system) sends only active customers. A customer that a complete pull no longer brings is removed here, even if it was edited here.
- Customers you added by hand (not from DCM) are never changed or removed.
- A link between a customer and an ONU that you set by hand is never changed.
- A router MAC seen behind two different ONUs is not linked automatically (it would be a guess).
- Routers that DCM marks inactive are not created; one that was synced earlier is only set to Inactive.
Related topics
Finished this topic?
Tick it off; the topic list shows what you have read.