See it working
The screens below are the real monitor with demo data. The API panel answers with recorded responses.
New clients: enter a client, watch the ONU come up.
Add a client below. In the demo the ONU is “plugged in” a few seconds later and the router does the rest, step by step. Everything here is fictional and runs in your browser — nothing is sent anywhere.
Demo data: fictional names, serials and documentation addresses.
Make the page a suspended client sees.
Fill in the form: the phone shows the page as your subscriber gets it, with the “Sign in to network” notice that opens it. Everything here is fictional and runs in your browser — nothing is sent anywhere.
Demo: a fictional operator, numbers and links. The buttons go nowhere.
Home
The start page: all OK, or what needs a look, the worst first — with the clients online, the light, the traffic and the server in one row.
The client card
One client on one page: connection, ONU signal, plan, IPTV, installation and Wi-Fi — suspend, change the plan or reboot the ONU from there.
New clients
Enter a client before the visit; when the technician plugs the ONU in, the router installs it step by step and says so.
The OLT
Boards and PON ports as the OLT has them — a click opens a port with its clients and the fiber history of each.
The ONU card
A client of the port: its signal against the optical bands, its fiber level over time, its traffic and its events.
Traffic
What goes through the uplinks over 24 hours, 7 days, 30 days or a year, by kind — estimated by port, no packet inspected.
The bell
What is wrong now, the worst first, one click from where it can be seen.
Alarms by area
OLT, clients’ ONUs, network, server and services — each checked every minute, with a history of raises and clears.
The clients’ ONUs
Online and why the others are not, the light of every ONT in bands, the weakest ones first.
The 24/7 wall
For a TV in the support room: all OK in green…
…and what is wrong, in red
Critical alarms pulse, the oldest first, with how long they have been open.
The OLT console
Every command the router sends to an OLT, and the reply, live, as it happens.
The terminal
The router’s dtvsol commands in the browser, with your role’s rights — ? shows what may come next.
Interfaces
Ports and bonds as configured and as they are running — edited, reviewed and applied with a 120 s safety net.
VLANs
Operator VLANs, QinQ and the service VLANs, one per PON port.
Protection
Who may reach the router, port forwards, login protection, anti-spoofing and CGNAT.
Routing: BGP and OSPF
Your upstreams with BFD, the full table checked by RPKI, the prefixes you announce, a blackhole for DDoS, and OSPF inside your network.
The audit log
Every change, who made it, how — monitor, CLI, terminal, billing, API — and from where.
Backups
Every night the configuration is saved on the router (and, with the DTVSOL Backup agent, copied encrypted off-site) — each archive checked by a restore drill.
The API
Pick a call to see the request and a recorded answer. Your billing uses the same calls.
Request
Response (recorded)
Or call us:Call us — enable JavaScript to see the number, or use the contact form.