ISPadmin

Your Invoices Can Now Fly Out on Their Own. What ISPadmin’s API Has Learned

Šárka — Wed, 12 Aug 2026 03:57:01 +0000

Version 5.43 extends the ISPadmin REST API with three new capabilities: download an issued invoice as a PDF, send an invoice to a client, and upload a file directly into the Client card. Together they mean that invoicing and client documentation no longer require anyone to click through the system by hand — your own application, portal, or script can handle it. And because version 5.42 already lets you control, through Token Management, who may create an API key at all, you gain options without losing control.

How many times a day does someone in your team log into ISPadmin just to download a single PDF invoice and forward it to a client? How many signed contracts sit in a shared folder instead of on the client’s record, because nobody got around to uploading them? And how much time does the monthly invoice run take when it could be triggered by a single call? If any of these sound familiar, version 5.43 has something for you.

Why it matters

The REST API is now a common gateway into ISPadmin. It is used to connect custom client portals, higher-level company applications, e-signature tools, accounting systems, and simple scripts that someone on the team wrote because they were tired of doing the same thing manually.

Invoicing, though, has long been the point where integrations hit a wall. Data could be read through the API, but when it came to the document itself — generating the PDF, sending it to the client, storing a signed contract alongside it — a person always had to step in and click it through in the system. The more clients you have, the more tedious it gets, and the more room there is for something to be forgotten.

Version 5.43 closes that gap.

What the new API capabilities bring

Downloading an issued invoice as a PDF. An invoice can now be retrieved through the API as a finished document, not just as a set of values. Your client portal can therefore offer the invoice for download directly, without sending the client to look for it elsewhere. It works equally well for archiving or for handing data over to an accounting system.

Sending an invoice to a client. Distributing documents can be triggered from your side, at the moment that fits your process — after a check in a higher-level system, for example, or tied to another event. Nobody needs to enter ISPadmin to do it.

Uploading a file into the Client card. Documents created outside ISPadmin reach the right client automatically. Typically a signed contract from an e-signature tool, a handover protocol from the field, or a document from another workflow. Instead of “someone will upload it later,” the file is where it belongs straight away.

Three roles, three reasons to appreciate it

The billing administrator stops being the bottleneck of the monthly close. What used to mean dozens of clicks is taken over by the system — and their time goes to the cases that genuinely need a human eye.

The developer or integrator finally gets the whole process into a single integration. No more half-solutions where some steps go through the API and others are done by hand, and no more sending users into two different systems.

The ISP owner sees the result in two numbers: faster delivery of invoices means earlier payments, and fewer manual steps mean fewer errors to track down and correct later.

How it fits into the rest of the system

This extension builds on what we wrote about in July — Token Management in version 5.42. There we covered who may generate an API key at all and added separate permissions for it. Now comes what such a key can actually do.

The two are closely connected. The more the API can do, the more it pays to keep control over who receives a key. If you have not reviewed your tokens since upgrading to 5.42, this is a good moment.

Three tips for rolling it out well

Tip 1 — Start with one process, not all of them. Pick whatever slows you down the most, usually the invoice run, and automate just that first. You will test the whole chain on something with an immediately visible benefit.
Tip 2 — One token per integration. Do not share a single key across tools. When you later need to disconnect one integration, or trace where a call came from, you will be glad you did.
Tip 3 — Test on a small sample. Before you turn automatic sending loose on your whole database, run it for a handful of clients and check what actually reached them.

What the ISP gains

Less manual work around invoicing — downloading PDFs and distributing documents are handled by the system itself.
Documents in the right place — signed contracts and protocols reach the client record automatically, not whenever someone remembers.
A better client portal — your own portal can offer the invoice for download directly, without pointing clients elsewhere.
Faster payments — the sooner an invoice reaches the client, the sooner it can be paid.

How to get started

The new API capabilities are part of version 5.43. If you have not deployed it yet, please contact us about upgrading. Then we recommend three steps:

Step 1 — Review in Token Management which API keys exist in your system, and issue a new token for the integration you are planning.
Step 2 — Choose the one process that costs you the most time today, and start there.
Step 3 — Verify the result on a few clients before you run it for real.

If you are interested, we are happy to advise on the integration design and on setting up the permissions.

The post Your Invoices Can Now Fly Out on Their Own. What ISPadmin’s API Has Learned first appeared on ISPadmin.

Before the storm hits: How to keep an eye on your network and handle outages from one place with ISPadmin

Šárka — Wed, 05 Aug 2026 04:21:18 +0000

Summer is a trial by fire for ISPs — and by water. Storms, power surges and fallen trees can take down half your network in minutes. Here’s how ISPadmin helps you spot an outage before your customers do, keep your dispatch team from drowning in alerts, and have spare parts and technicians ready to roll.

Storm season is here — and your network will feel it

Hail, wind, surges on the power line, a flooded cabinet. Every network operator knows the scenario: a storm rolls in and within minutes the phones start ringing. The question is never whether an outage will happen, but how fast you’ll find out about it and how prepared you’ll be when it does.

The good news is that most of the tools you need to get through storm season are already sitting together in ISPadmin — from network monitoring through a backup RADIUS and outage records all the way to warehouse stock and a mobile app for field technicians. Let’s walk through them in the order you’ll actually need them during a crisis.

1. NetMonitor: know about an outage before your customer does

The basics are simple — you want to hear about a problem from the system, not from an angry client. That’s what network monitoring and NetMonitor are for.

ISPadmin continuously tracks device status across platforms — MikroTik, Ubiquiti, Linux, airFiber, Cambium and others — and keeps an eye on switches too. When something stops responding, you get an alert. You tailor the setup through SNMP templates and NetMonitor notifications, so your dispatch team sees what actually matters and the alerts land where they should.

A practical tip before the season: check that all your key POPs and backbone links are covered, and verify that notifications are going to the right people and channels. An alert nobody reads is as good as no alert at all.

2. Safe mode: when half the network goes down, your dispatch team won’t drown

A storm rarely takes down just one device. When power fails across an entire site, monitoring can generate hundreds of alerts at once — and at exactly the moment you need a clear head, the dispatch team gets buried in notifications.

That’s precisely what NetMonitor’s safe mode is for. Through the fail_safe_mode_trigger_threshold setting you define a limit on the number of unavailable devices. Once it’s exceeded, monitoring switches to a limited mode and the dispatch team receives only the key information, not a massive wave of false alarms. The team sees the essence of the problem — an entire site is down — instead of three hundred individual notifications.

It’s also one of the elements that help meet NIS2 requirements for keeping monitoring operational even during large-scale outages.

3. Backup RADIUS: clients stay online even if the main server goes down

A storm doesn’t have to take down just a rooftop antenna — it can knock out the server room itself. And when RADIUS “dies,” clients can no longer authenticate and nobody gets connected, even if the rest of the network is running. The Backup RADIUS server submodule is built for exactly this scenario.

The principle is simple: alongside the primary ISPadmin installation, a second, backup solution runs on separate hardware. When the main server fails or crashes, the end client authenticates against the backup RADIUS and stays online. Authentication data is synchronized automatically and continuously from the primary server, so the backup is always up to date — and when the main system is updated, the backup is updated too, over SSH.

The key is the configuration on the MikroTik side: the device receives the parameters of both the primary and the backup RADIUS server, so if the main one fails, it automatically tries the other (the timeout is tuned via the radius_service_timeout key). The switchover happens without anyone lifting a finger.

For the backup to make sense, it’s recommended to place it geographically elsewhere, on separate connectivity and a separate power source from the primary server — so the same storm doesn’t take both down. The submodule is available from version 5.37 beta2, requires the NMM and RADIUS modules to be active, and activation is arranged through sales (sales@ispadmin.eu), with the installation and configuration handled by an ISPadmin technician.

If you run PPPoE or HotSpot and client connectivity lives and dies with authentication, this is one of the best safeguards you can put in place before storm season.

4. Outage records and POPs: an overview instead of chaos

Once an outage does happen, you need to record it somewhere, tie it to a location and track it until it’s resolved. The Hardware module gives you POP definitions and outage records — so you know what’s down, since when, and everything it affects. After the season, you also get data out of it: where things fail repeatedly, and where to invest in surge protection or backup power.

5. Central warehouse: spare parts ready to roll

The fastest monitoring in the world is useless if the technician has nothing to swap the broken device for. The central warehouse gives you an overview of where each antenna, switch or set-top box is, and thanks to barcode reader support, stocking and issuing items is a matter of seconds.

Before storm season it pays to check your stock of critical parts — the units that surges destroy most often — and have them ready for quick issuing. Equipment is assigned directly to technicians or clients and linked to contracts, so even in the rush of call-outs you keep track of what ended up where.

6. Task Manager: technicians in the field with the information in their pocket

When someone heads out to make a repair, decisions are made in the field. The Task Manager mobile app (Android and iOS) gives the technician an overview of assigned tasks, routers and clients, tasks on a map with navigation, and — crucially — the online/offline status of devices right on their phone. A photo from the site goes straight onto the client’s record.

That way the dispatcher assigns tasks online and the technician doesn’t have to call the office to find out whether the link came back in the meantime. In storm-driven operations, where every minute counts, that means more repairs per day.

7. Helpdesk: customer communication under control

Even with perfect monitoring, customers will still call. The Helpdesk keeps all tickets, emails and phone calls in one place, sorted by department, status, priority and labels. Through a dashboard with reports and charts you can see how many tickets the storm brought in and how quickly you’re resolving them — and thanks to the link with the Planning module, a ticket turns straight into a task for a technician.

A short pre-season checklist

Before the first big storm rolls in, run through these:

Are all your key POPs and backbone links covered in NetMonitor?
Are alerts and NetMonitor notifications going to the right people and channels?
Is fail_safe_mode_trigger_threshold set so a large outage doesn’t overwhelm you?
Do you have a backup RADIUS on separate hardware (different location, connectivity and power), and do your MikroTiks have both servers configured?
Do you have critical spare parts in stock, and are they entered with the barcode reader for quick issuing?
Do technicians have Task Manager on their phones with current access?
Does the dispatch team know how to work with the Helpdesk and Planning during a wave of reports?

Bottom line: you can’t stop the storm, but you can stop its impact

Outages can’t be avoided entirely — but the difference between “we hear about it from a customer an hour later” and “the system alerted us and a technician is already on the way with a spare part” comes down to well-configured monitoring, a stocked warehouse and a mobile team. And you have all of it in ISPadmin, in one place.

Want to go through your NetMonitor or safe mode setup on your network? Get in touch — we’ll be glad to walk through it with you before the season, not in the middle of it.

The post Before the storm hits: How to keep an eye on your network and handle outages from one place with ISPadmin first appeared on ISPadmin.

FlowPRO NG — Keep Your Network Traffic Under Control and Stay Compliant

Šárka — Tue, 28 Jul 2026 09:00:14 +0000

Retaining traffic and location data is one of the core obligations of internet service providers across Europe. Whether it stems from national legislation or the European cybersecurity framework (NIS2), a provider has to be able to reliably collect the data, store it securely, and hand it over to the competent authorities on request. That is exactly what FlowPRO NG is built for.

What the law expects from providers

The requirements differ in detail from country to country, but the principle is the same: a provider needs a solution in place that can reliably record traffic and location data on end-client communication, store it for the required period in an unaltered and verifiable form, search through it quickly and accurately, and hand the data over to the competent authorities in the required format on request.

Without the right tool, meeting these requirements is demanding and error-prone. FlowPRO NG simplifies and automates the entire process.

FlowPRO NG: a modern platform for monitoring and data retention

FlowPRO NG is a network monitoring and traffic data retention platform designed to meet the requirements of European legislation. It runs on Debian Linux with guaranteed security updates and is independent of the underlying infrastructure — it works on a physical server, in a virtual environment, and in the cloud.

The solution combines a border probe with a collector and puts the emphasis on fast, accurate, and clearly presented search results. It provides data in the format required by law and is ready for audits as well as for handing data over to the competent authorities.

Why choose FlowPRO NG

Ready for NIS2 and other regulations — 100% monitoring of private-to-public IP address translation (NAT), including ports, timestamps, and connection duration.
Fast and accurate searching — retrieve data in moments, with clear statistics and export to the required format.
Infrastructure independence — server, virtual environment, or cloud; the solution grows with your network.
Security as standard — secure communication, management over encrypted protocols, and a guarantee of future security updates.

We’ll help you deploy it

FlowPRO NG gives you full visibility into your network traffic while helping you meet the legal obligations tied to data retention. At NET service solution, we’ll be glad to help you with it.

Want to learn more? Get in touch with us by e-mail at info@flowpro.eu.

The post FlowPRO NG — Keep Your Network Traffic Under Control and Stay Compliant first appeared on ISPadmin.

Token Management: Who can generate an API key in your system? From now on, only those you allow

Šárka — Wed, 22 Jul 2026 05:34:11 +0000

Version 5.42 adds a new Token Management page to ISPadmin (Settings / System settings) and, more importantly, user permissions for it. Generating API keys — through which data can be both read from and written into the system — is now controlled: the administrator decides, not just anyone who logs in. For an ISP this means lower security risk, control over access to your data, and another step toward NIS2 compliance.

Do you know who can create an API key in your ISPadmin today? How many keys are currently active in the system, and which integration each of them actually belongs to? And is there a token still “living” somewhere after an expired trial license or a disconnected tool that no one remembers? If the answer is “no idea,” version 5.42 has good news for you: access to generating API keys is now fully in your hands.

Why it matters

The REST API is now a common gateway into ISPadmin. API keys are used to connect integrations for maps, SMS gateways, banking interfaces, invoicing links, as well as custom scripts and third-party tools — and increasingly also projects such as voice self-service or AI assistants that pull client and service data from ISPadmin. Every such connection needs its own token, and that token is essentially a key to the system.

The problem was that the API key generation page was not included in the navigation and had no permissions of its own. In practice this meant that any logged-in user could generate their own API key and use it to pull information out of ISPadmin, or to write data into it. For a system that manages sensitive data about clients, services, and the network, this is a real security risk — and this is exactly what one of the providers pointed out.

What Token Management brings

The Token Management page is now included in the menu under Settings / System settings, so generating and managing API keys is in one clearly defined place. The key change, however, is in the permissions: four separate permissions have been added for this page in the user settings — read, add, edit, and delete.

The permissions are enforced strictly. Without the read permission, the page will not be shown to the user at all and cannot even be found in the menu. Without the add, edit, or delete permissions, the relevant buttons disappear — and, importantly, the given action will not go through even via a direct URL. The permissions therefore cannot be bypassed through a “back door.”

The decision about who may see and create API keys is thus entirely up to the administrator. You can entrust it to a narrow group of people who actually manage the integrations, and not give the rest of the team access to generating keys at all.

Three roles, three reasons to appreciate it

The system administrator finally decides who can see the API. Instead of an “everyone can” state, access is granted deliberately and as needed — and just as easily revoked when staffing changes.

The person responsible for security gets the principle of least privilege in practice: access to the system’s keys is held only by those who truly need it. This is useful not only for peace of mind, but also for demonstrating that access to data is controlled — a topic that more and more providers are addressing with NIS2.

The ISP owner has a simpler assurance: data is not pulled out of their system through a key that no one knows about and that anyone could generate. The risk of a data leak via a “forgotten” token drops significantly.

How it fits into the rest of the system

Token Management is not a standalone feature — it builds on the user permissions on which the security of the entire ISPadmin rests. Just as with other pages, visibility and available actions for API key generation are now controlled through the permissions of a specific user. It also fits into the broader security line of recent versions (passwords, access control, NIS2-related measures), where the point is always the same: keeping control over who can access what in the system.

Three tips for setting it up well

Tip 1 — Grant permissions narrowly right after the update. After upgrading to 5.42, no one has the Token Management permissions at first. Use this and give access only to people who actually manage API keys — not to the whole team “just in case.”

Tip 2 — Review and clean up existing keys. Look at which tokens are in the system and remove those belonging to discontinued integrations or expired trial licenses. An inactive key is an unnecessary open window.

Tip 3 — Separate reading from editing. For most people who need to look at the page, the read permission is enough. Leave add, edit, and delete only to those who actually issue the keys.

What the ISP gains

Lower security risk — an API key can no longer be created by just any logged-in user, so one of the quiet paths to your data disappears.

Control over access — the administrator decides who may see, create, and delete tokens, and can change it at any time.

A step toward NIS2 compliance — controlled access to the system’s keys and the principle of least privilege are exactly what today’s security requirements expect.

Order among your integrations — generating and managing keys is in one place, not scattered “with everyone who logs in.”

How to get started

You will find the Token Management page in ISPadmin 5.42 under Settings / System settings. If you have not deployed the version yet, please request an update. Then we recommend three steps:

Step 1 — Grant the Token Management permissions only to responsible users in their settings; for logged-in users, the change takes effect at their next login.

Step 2 — Review the current API keys and remove those that are no longer needed.

Step 3 — Agree within the team on a simple rule — who issues tokens and how they are revoked after an integration ends — so your overview stays clean going forward.

If you are interested, we are happy to help you set up the permissions.

The post Token Management: Who can generate an API key in your system? From now on, only those you allow first appeared on ISPadmin.

WiFi clients to be transferred: How ISPadmin Finds Misassigned MAC Addresses on Its Own

Šárka — Tue, 30 Jun 2026 09:01:23 +0000

ISPadmin 5.42 adds a new Dashboard widget — WiFi clients to be transferred (MAC address found on another router). The system recognizes on its own that a client’s device is physically connecting through a different access point than the one recorded for its internet service, and lets you fix it with a single click. For an ISP this means cleaner data, more accurate statistics, and fewer „mysterious“ issues that are not actually network faults but record-keeping faults.

Did your WiFi clients reconnect to a different access point after a storm and never return to where you have them recorded? Did a technician repoint a device to another AP on the same POP and forget to write it down? How many services do you have in ISPadmin assigned to an access point the client hasn’t really used in ages? If the answer is „no idea“, version 5.42 has good news: from now on ISPadmin watches it for you.

Why it matters

Every internet service in ISPadmin has a recorded access point — a specific AP / router through which the client connects. This link is just a record, but a lot depends on it: statistics and load graphs for access points, capacity planning, and quick diagnostics when a client calls with a problem.

But in wireless networks reality changes faster than the paperwork keeps up. A client’s CPE reconnects to a different AP for a better signal, a technician repoints a device to another access point on the same POP during service, after an outage some clients move elsewhere. The device’s MAC address stays the same — but it is physically read on a different access point than the system assumes in its records.

The result? A conflict arises between what is set on the service and what is actually read from the device. Graphs and statistics are drawn according to the records, so the load is attributed to an access point where the client no longer is. And when you plan investments or tackle congestion on such data, you are basing decisions on a wrong picture of the network.

What the new widget does

ISPadmin continuously reads which access points each MAC address appears on. The new Dashboard widget compares this data with the records and lists every case where a client’s MAC address was found on a different router than the one recorded for the service.

In other words: the widget is a list of mismatches between what you have in the system and what is actually happening in the network — services where the system knows the client should be elsewhere (in fact, an exclamation mark already flags such cases in the router overview today).

And here is the main thing — you don’t have to rewrite anything manually. Directly from the widget (and likewise from the WiFi clients overview on access points in Hardware → Routers) you can click through to the form to move the service to the correct access point and resolve it in one go. And if the target device where the MAC is actually read doesn’t have an access point yet, the system lets you create one first and only then move the service onto it. No searching the client card, no manual digging.

Three roles, three reasons to appreciate it

The technician gets a concrete „this doesn’t add up“ list instead of a vague feeling that the data is a mess. After every intervention, outage, or seasonal repointing they open the widget, run through the mismatches and reconcile them — even from the mobile app while still in the field.

The network planner finally works with data they can trust. Access point load matches reality, so decisions about boosting capacity, adding an AP, or rerouting clients stand on solid ground, not on outdated records.

The ISP owner has a single data-quality indicator. An empty widget means the records match reality. A full widget is a signal that something is happening in the field that is not being reflected in the system — and that it is time to address it before it becomes chronic disorder.

How it fits into the rest of the system

The widget isn’t a standalone feature. It builds on the work with access points and WiFi clients that ISPadmin does in the Hardware → Routers module. Version 5.42 also added the same logic to WiFi clients on access points: if the system detects a MAC address on a different router, it offers a click-through to the relocation form right there.

A clean „service ↔ access point“ link then carries further — into client statistics and router load graphs. A single reconciled record thus improves accuracy in several places at once.

Three tips to get the most out of the widget

Tip 1 — Add it to your morning routine. The Dashboard widget takes a few seconds. Going through it every morning (or after every larger network intervention) takes less time than later investigating why the statistics don’t add up.
Tip 2 — React right after outages and repointing. It is exactly the situations where WiFi clients mass-migrate to backup points that produce the most mismatches. If you reconcile them right away, the records never get a chance to drift.
Tip 3 — Treat a full widget as a warning, not extra work. When it regularly shows many records, it is not a system fault — it is a sign that some field process doesn’t end with an entry into ISPadmin. Fix the cause, not just the symptom.

What’s in it for the ISP

Trustworthy statistics — access point load matches reality, so capacity planning rests on the right numbers.
Faster diagnostics — when a client calls with a problem, you see the router they are actually communicating through, not last year’s record.
Less data cleanup — mismatches are resolved with a click the moment they arise, not in a bulk review once a year.
Measurable record quality — the widget’s state is a simple indicator of how well your data matches reality in the network.

How to get started

You will find the WiFi clients to be transferred widget in ISPadmin 5.42 on the Dashboard — just add it to your displayed widgets. If you don’t have the version deployed yet, request an update. Then we recommend three steps:

Step 1 — Add the widget to your dashboard and see how many mismatches the system currently reports; it is usually the first aha moment.
Step 2 — Reconcile the existing records by clicking through to the service relocation form.
Step 3 — Agree within the team on who checks the widget and how often, so your records stay clean going forward.

If you would like to test the feature, we are at your disposal.

The post WiFi clients to be transferred: How ISPadmin Finds Misassigned MAC Addresses on Its Own first appeared on ISPadmin.

GPON Is No Longer Just Huawei — ISPadmin Now Supports TP-Link OLTs

Šárka — Tue, 16 Jun 2026 07:34:50 +0000

Back in April we wrote about how the GPON module in ISPadmin runs your entire FTTH network from one place – from ONT activation through billing all the way to IPTV. At the end of that article we made one promise: that we were working on extending support to more OLTs. Version 5.42 delivers on it. For GPON you can now choose whether you run on a Huawei or a TP-Link OLT – and, on top of that, set a specific ONT type per service.

Why multi-vendor support matters

Fiber is built in waves, both in the Czech Republic and across Europe, and each wave often means different hardware. You build one PoP on Huawei, extend another two years later, and in the meantime prices, availability and your preferred vendor have all shifted. The result is a reality many providers know well: a network made up of OLTs from more than one vendor.

As long as your monitoring and billing system speaks only one brand, you pay for it twice. Either you run a second, parallel tool just for the other OLTs, or you manage part of the network by hand through the vendor’s web interface – which drags you right back to the paperwork the GPON module was supposed to eliminate. Multi-vendor support in a single system removes that problem: whatever mix of OLTs you have underneath, you manage it from the same client card and the same overviews.

What’s new in version 5.42

Choice of OLT type: Huawei or TP-Link. In the OLT settings (Hardware / GPON / OLT) you now select the device type. Alongside the existing Huawei support, TP-Link has been added in two variants – you pick the right one based on the device you actually run. The rest of the workflow – reading ONT status, activating and deactivating the service, billing on the client card – stays the same regardless of the platform you use.

ONT type per service. For an Internet service of the GPON (Huawei) type you can now also set the ONT type. In practice this means more accurate records of end-user units right on the client’s service – you know not only that an ONT is there, but which one. Handy for servicing, swaps and reporting.

More reliable OLT data. Version 5.42 also includes a fix to how data is read from the OLT, so connection-status overviews are more accurate.

These changes build on version 5.41 – the option to select an access point for a GPON service, a column showing the status of individual LAN ports in the connections overview, and improved display of related links on maps. Together they paint a picture of a GPON module growing toward being genuinely vendor-neutral.

What providers gain

Less vendor lock-in. You can choose your OLT based on price, availability and parameters – not on what your software happens to support.

One system instead of two. A mixed Huawei + TP-Link network is managed from a single interface. No parallel tool, no manual handling of some PoPs through the vendor’s web UI.

More accurate records and reporting. ONT type per service and more reliable reads across all OLTs mean data you can rely on – for your own servicing as well as for mandatory reporting and subsidy projects.

Easier network takeovers. When you take over customers or an entire location from another operator, you simply set the inherited OLT in ISPadmin as another type.

Who it makes sense for

The extension is most valuable for providers who are building or extending FTTH on hardware from multiple vendors, ISPs with a mixed (hybrid) network who don’t want to run a separate tool just for fiber, and small and mid-sized operators for whom a standalone GPON OSS wouldn’t pay off financially, yet who still want a professional level of automation without being tied to a single brand.

Compatibility and technical details

The GPON module is a standalone module that is not part of the base installation and is licensed separately. Currently:

Supported OLTs: Huawei (development and testing on the MA5608T model, MA5600 series) and now TP-Link in two variants.
Supported ONTs: any vendor; for Huawei you can now also record the ONT type per service.
Communication protocol: SNMP, with no proprietary interface or CLI access required.

We recommend verifying the specific supported models and TP-Link variants in the documentation or with our sales team – the device list keeps expanding.

How to get started

Browse the documentation in the wiki, where you’ll find the current list of supported platforms and licensing requirements. If you’re interested in the module, get in touch with our sales team: sales@ispadmin.eu

The post GPON Is No Longer Just Huawei — ISPadmin Now Supports TP-Link OLTs first appeared on ISPadmin.

Billing in ISPadmin: When invoices issue, reconcile and chase payments by themselves

Šárka — Tue, 02 Jun 2026 11:10:55 +0000

Billing is the heart of every ISP — and at the same time, the place where money and time most often slip away. ISPadmin can take the whole cycle off your hands: from issuing invoices through matching bank payments to reminders and blocking non-payers. How many hours a month do manual invoicing and payment follow-ups consume today?

How many invoices do you issue by hand? How many payments do you reconcile each month “by eye” using a variable symbol in Excel? And when did you last send a reminder three weeks later than you should have, simply because there was no time? If those numbers don’t sit well with you, here’s the good news: ISPadmin can do all of this for you — and once it’s set up, you rarely have to come back to it.

Why tackle billing first, and why now

You can have your network beautifully built, coverage planned down to the last entrance, and your technicians finely tuned — but until your payments are reconciled automatically and non-payers are tracked automatically, it eats into your margin and, above all, your time. At a small ISP, it still “somehow works” manually. Once you pass a few hundred clients, manual billing stops being sustainable, and every mistake (a wrong variable symbol, a forgotten tariff change, an unsent reminder) costs real money.

That’s why ISPadmin builds billing as an automated cycle, not as document filing. The contract, the service, the price, and the payment stay tied together — and each month, the system produces what needs to go to the client and into your accounting on its own.

What the Billing module can do

The Billing module covers the entire financial loop of a provider:

Automatic invoice generation from a client’s active services — regularly, in your chosen billing cycle (monthly, quarterly, annually), in bulk for all clients at once.
Consolidated billing of multiple services on a single document — internet, IPTV, VoIP, and one-off items on one invoice, clear for the client and for accounting.
Payment reconciliation from bank statements — the system matches incoming payments by variable symbol and amount, so you only handle the exceptions, not the whole statement.
QR payments and payment details right on the invoice — the client pays in a couple of clicks, and you get a higher share of on-time payments.
Reminders and non-payer tracking — automatic emails and SMS messages for overdue amounts, with follow-up service throttling or blocking based on the rules you set.
Credit notes, advance payments, and corrective documents — the full agenda you need to keep your accounting in order.
Exports to accounting systems — you hand the data to your accountant without retyping.

The important part is that all of this runs on a single source of data. The invoice knows which services the client actually has because it reads from the same record used by sales and field technicians.

Three roles, three views of the same billing

The accountant / billing clerk runs bulk billing for the whole month in one step, payments are reconciled from the statement automatically, and they only deal with discrepancies. The monthly close that used to take days becomes a matter of checking exceptions.
The salesperson sees the client’s real payment status and balance — before calling about an upsell, they know whether the client pays on time. Special pricing terms are set once, and billing keeps applying them automatically.
The ISP owner has cash flow under control: who owes money, who is getting a reminder, and how much has been invoiced this year. Instead of “it’ll be somewhere,” they have the numbers in real time.

How billing fits into the rest of the system

Billing is not an island. It reads from the same data as Clients (services, contracts, tariffs) and connects to the Helpdesk (communication with the client about a payment has its history on the ticket). When the question “why was I charged this amount?” comes in, you find the answer on a single record, not across three systems.

Three tips for rolling out billing smartly

First, get your billing cycles and tariffs straight. Before you run bulk billing, check that services have the right prices and periods. A few minutes here saves hours of complaints.
Turn on payment reconciliation right away. Automatic matching from the bank statement saves the most time — set it up first.
Set up reminders and blocks as a rule, not as a decision. When the system sends reminders automatically based on clear rules, you no longer agonize over “who to write to next,” and client relationships stay matter-of-fact.

What’s in it for the ISP owner

Less manual work — bulk billing and automatic payment reconciliation free up days each month for the billing clerk.
Faster, more stable cash flow — QR payments and automatic reminders shorten the time until money arrives.
Fewer errors and disputes — the invoice draws on the client’s real services, not on colleagues’ memory.
Auditable data — a single source of truth about what was invoiced and paid. For peace of mind in accounting and for NIS2.

How to get started

You’ll find billing in ISPadmin under the Billing tab, with detailed guides at wiki5.ispadmin.eu. We recommend three steps:

Review the tariffs and billing cycles on your services so billing generates the correct amounts.
Set up payment reconciliation from the bank statement and rules for reminders.
Verify the exports to accounting so the data lines up without retyping.

If you’re interested, we’re happy to help you set billing up or show it on a demo.

The post Billing in ISPadmin: When invoices issue, reconcile and chase payments by themselves first appeared on ISPadmin.

Sales Opportunities and Helpdesk in ISPadmin: Tickets, Emails, and Calls Linked to Every Opportunity

Šárka — Mon, 18 May 2026 11:05:20 +0000

In ISPadmin 5.42 beta 1, we connected the Sales Opportunities and Helpdesk modules. All client communication — emails, SMS messages, phone calls, and in-person meetings — is now available directly within the detail of a specific sales opportunity. You can also create a new ticket with a single click.

How much time do you spend every day switching between modules just to find out who spoke with a client, when, and about what? If your sales team keeps communication history “somewhere in Helpdesk” while the sales opportunity itself is “somewhere else,” it’s time to bring everything together. In ISPadmin 5.42, we completed one of the most requested integrations — the Sales Opportunities module now works directly with the Helpdesk module.

What’s New

A new Tickets tab has been added to every sales opportunity detail. It provides a complete overview of linked tickets and scheduled Helpdesk messages, including status, priority, department, owner, and labels. All communication with the client — emails, SMS messages, phone calls, and personal meetings — is now accessible exactly where it makes sense: directly within the related sales opportunity.

Two new buttons are available:

Link to Ticket opens a dialog with a ticket list and full-text search by ticket ID, client name, contact, or subject. Checking a ticket creates the link, while unchecking removes it. One ticket can be linked to multiple sales opportunities.
Create New Ticket opens the Helpdesk form with the sales opportunity already pre-linked. Tickets can be created through all four communication channels: Email, SMS, Phone, and Personal Visit. After saving, you are automatically returned to the sales opportunity detail, and the new ticket immediately appears in the list.

Practical Benefits for ISPs

Less clicking. Sales representatives no longer need to switch between modules to see who communicated with the client and when.
Complete sales context. The entire communication history becomes part of the sales opportunity — from the first inquiry to the final closure.
Cleaner Helpdesk organization. Tickets related to sales activities are clearly linked, making them easy to distinguish from operational support tickets.
Smooth handovers. When sales hands a client over to support, simply open the sales opportunity — everything is already there.

How Does It Work?

Open a sales opportunity, switch to the Tickets tab, and immediately see everything related to the client communication history. Need to find an existing ticket? Click Link to Ticket — full-text search will find it, and a single checkbox creates the connection. Need to send an email, schedule a meeting, or record a phone call? Click Create New Ticket — the form opens with the sales opportunity already linked. Simply choose the communication channel (Email, SMS, Phone, or Personal Visit), add the content, and save. The ticket instantly appears in the list while continuing through its standard Helpdesk workflow.

How to Enable It

The functionality is automatically available to all customers running ISPadmin 5.42 beta 1. The only requirement is that the user has both modules activated — Sales Opportunities and Helpdesk — along with the necessary permissions (read and write access) in both modules.

Try It Yourself

You can test the feature on our demo environment: www.ispadmin.eu/demo

If you need any assistance or would like to learn more about the Sales Opportunities module, contact us at sales@ispadmin.eu.

Thank you for using ISPadmin. We are already working on more improvements.

The post Sales Opportunities and Helpdesk in ISPadmin: Tickets, Emails, and Calls Linked to Every Opportunity first appeared on ISPadmin.

Central Warehouse in ISPadmin: Where Every Antenna, Set-Top Box and Switch Is — and Why It Matters After NIS2

Šárka — Tue, 05 May 2026 08:03:51 +0000

How many set-top boxes, antennas and switches do you have out in the field — and do you know exactly who has each of them right now? If the answer starts with “somewhere in a spreadsheet” or “Pavel knows,” this article is for you. The Central Warehouse module in ISPadmin moves your hardware records out of sticky notes and Excel files into one clear module — and after NIS2, it has become part of what regulators actually expect from you.

Why asset management is suddenly topic number one

In our previous article we covered how ISPadmin helps you handle NIS2 in the areas of password policy, Helpdesk and NetMonitor. The second major pillar of cybersecurity that any audit will check is asset management — a factual, up-to-date list of every piece of hardware your network runs on. Without it you cannot manage vulnerabilities, plan replacements, or prove that controls are in place.

For an ISP this is also a daily operational topic:

The antenna someone moved three years ago from a tower in Štíhlovice to the POP in Bystřice — is it written down anywhere?
The set-top box a customer returned when ending their contract — is it on the shelf, or did a technician take it home?
The switch in “Pavel’s storage” — does it even have an inventory number?

The Central Warehouse in ISPadmin closes these questions by tracking hardware as inventoried items from receiving through issuing to a technician, installation at a customer, and finally return or write-off.

What the Central Warehouse can do

The module is built to track all assets of an ISP:

active devices — switches, routers, APs, GPON ONTs, CMTS cards
passive devices — antennas, brackets, masts, connectors, cable
customer equipment — set-top boxes, ONTs at customers, modems
consumables — cables, adapters, fittings

For every item you can see where it is right now, who is currently responsible for it, what state it is in, and the full history of its movements.

Overview and history — the filter that pays off

The item overview is not a long list you have to scroll through manually. The filters at the top of the page take you straight to what you need:

Billing group — useful for ISPs with several branches or legal entities
User — who the item is currently assigned to (technician, customer, warehouse)
Year / month — the time window of movement
Previous state / new state — what happened to the item (received, issued, installed, written off…)

For each item you can open the Detail view to see the full history card. When an audit or warranty claim asks when and from whom you got a specific set-top box, the answer takes about thirty seconds.

A warehouse connected to real operations

The strength of the Central Warehouse in ISPadmin is that it is not an island. Items naturally connect to the other modules:

Receiving after purchase from a supplier.
Issuing to a technician as part of a task in Planning — the technician “takes” specific serial numbers for the field visit and installs them on site.
Installation at a customer — the item is linked to a specific service or contract, so you can see it from the customer card too.
Return / write-off — when a service ends or a device fails, the item goes back to the warehouse or is written off, and everything stays in the history.

This connection is exactly what separates a real warehouse from a spreadsheet: nobody has to remember to add a row after a field trip — the movement is recorded where the work actually happens.

Four practical tips that will save you hours

Enter serial numbers during receiving, not at the customer site. A field technician then only confirms what is already in the system, instead of typing codes from a box label into a phone.
Set up roles and permissions. The warehouse keeper issues, the technician receives, the manager sees the history. The Central Warehouse respects ISPadmin user permissions, so separated responsibilities stay separated.
Run inventory checks every quarter, not once a year. The “month” + “user” filter quickly reveals items that have been sitting with a technician for a suspiciously long time without being installed.
Use the warehouse for POPs too, not just customers. A switch in a rooftop cabinet is your asset. When the records show that a specific DGS-1210 has been at POP Bystřice since April 2024, outages and warranty cases are resolved in minutes.

By the way — your warehouse is with you in the field too

ISPadmin is a fully responsive web application. The warehouse opens in exactly the same way from a laptop in the office, a tablet in a service van, or a phone on a rooftop. There is no separate mobile app to install — a browser and a login are enough. A technician can receive goods or confirm an installation right on the spot.

What an ISP owner gets out of it

Fewer losses — set-top boxes and antennas no longer fall into the “grey zone” between the warehouse and the customer.
Smoother accounting — hardware has a clear history, depreciation and write-offs are traceable.
Audit readiness — whether NIS2, tax, or grant-related (for example the Czech Ministry of the Interior FlowPro programme), the asset register is one of the first documents an inspector will look at.
Fewer arguments in the team — who had which antenna is no longer a question of memory, but of two clicks.

How to get started

If you are not yet using the Central Warehouse to its full extent, we recommend three steps:

Open the overview in ISPadmin and look at what is already in there (often more than an ISP expects).
Add serial numbers to critical assets first — POPs, customer CPE, expensive antennas.
Introduce the rule “field trip from Planning → issue from the warehouse,” so new devices are recorded automatically.

Detailed step-by-step guides are available in the ISPadmin wiki — Central Warehouse (Czech). To try the module without commitment, book a demo.

The post Central Warehouse in ISPadmin: Where Every Antenna, Set-Top Box and Switch Is — and Why It Matters After NIS2 first appeared on ISPadmin.

ISP Security after NIS2: Password Policy, Helpdesk Under Control, and NetMonitor in Safe Mode

Šárka — Wed, 29 Apr 2026 07:04:27 +0000

In December, we wrote about how ISPadmin supports a more secure ISP operation — 2FA, roles and permissions, TLS with Let’s Encrypt, and bulk password changes on MikroTik. But NIS2 requires more than one-time measures; it demands demonstrably managed access, enforced policies, and operational continuity even on a bad day.

Version 5.40 introduces features that move exactly in this direction — password policy, a redesigned Helpdesk, fail-safe NetMonitor, and a widget for external service status.

1. Password policy — no more “Password123” in your team

Until recently, each system administrator could use whatever password they remembered. From both an audit and NIS2 perspective, that’s a problem — one weak account is enough to leave the door wide open.

In Settings → System settings → General, a new password_policy configuration is now available. It lets you define password requirements for system users (length, complexity, character rules). Once enabled, all newly created passwords must comply — weak passwords are simply rejected.

And an important audit trail feature: in Settings → Administrators → Administrators, there is a new Password policy column that directly shows whether each user’s password meets the requirements. You can instantly see who needs to update their password — no Excel sheets, no guesswork.

What it means for you: Weak passwords are no longer a matter of trust, but of configuration. You enable the policy once, and your team follows it automatically. For audits (NIS2, Cybersecurity Act), one screenshot and one timestamp are enough.

2. Permissions and signatures in Helpdesk — who can do what and under which name

In ISP operations, the Helpdesk quickly fills up with agendas from multiple departments — billing, technical, field technicians, support. When everyone sees everything, it becomes both an audit issue and a practical one (“why did a technician delete a billing ticket?”).

The Helpdesk → Settings → Departments section is now split into three sub-tabs:

Departments — original settings.
Permissions — an overview of all users and departments with the ability to edit permissions directly. Finally, one place where you can clearly see “who has access to what” — and change it.
Signatures — define different signatures for different users across departments. A technician no longer signs billing replies as an accountant, and vice versa.

What it means for you: Clear segregation of duties is one of the first things auditors and NIS2 look for. In ISPadmin, it’s a table — not a Word document on a shared drive.

3. NetMonitor in fail-safe mode — when the network collapses, your operations stay in control

A classic failure scenario: a backbone link goes down, NetMonitor starts reporting hundreds of unavailable devices, alerts flood the operations team, and somewhere in that flood, the one critical alert gets lost.

In Hardware → Settings → NetMonitor → General, there is now a fail_safe_mode_trigger_threshold setting. You define the threshold of unavailable devices, after which NetMonitor switches to a limited mode — showing only key information instead of a massive wave of noise.

What it means for you: Operational continuity under NIS2 isn’t just about systems running. It’s about people being able to work during a crisis. Fail-safe is the difference between “a quarter of the network went down, but the team handled it” and “a quarter of the network went down and the team spent an hour digging through 3,000 alerts.”

4. Dashboard widget External service status — one view, everything important

Secure and reliable ISP operations don’t depend on ISPadmin alone. You rely on backup RADIUS servers, external integrations, monitoring tools. When one of these “supporting pillars” fails, you should know before your customer tells you.

The Dashboard now includes a new External Services and Systems Status widget. In one panel, you can see the status of external services (e.g., backup RADIUS) and verify whether your “safety net” is actually working. Visibility respects user permissions (Settings → Administrators), so users only see what they are allowed to.

What it means for you: A backup system you don’t know is down overnight isn’t a backup system. This widget gives you that certainty every morning on your first screen.

Summary

Post-NIS2 ISP security stands on four pillars, all now natively covered by ISPadmin:

Identity and passwords — 2FA + new password policy with audit visibility.
Segregation of duties — Helpdesk permissions as a clear, manageable table.
Operational continuity — fail-safe NetMonitor that prevents alert overload.
Dependency visibility — dashboard widget for external services and backup systems.

Security in version 5.40 is no longer just an “audit checkbox.” It’s an everyday operational layer that saves time, reduces risk, and gives you something solid to show during an audit or incident.

Want to see how it works in your network? Try ISPadmin in a demo or get in touch with our team — we’ll guide you through setting up password policies and Helpdesk configuration in your environment.

The post ISP Security after NIS2: Password Policy, Helpdesk Under Control, and NetMonitor in Safe Mode first appeared on ISPadmin.