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.

GPON from A to Z: How to Run Your Entire FTTH Network from One Place in ISPadmin – from ONT Activation to IPTV Service

Šárka — Tue, 21 Apr 2026 08:23:03 +0000

The FTTH boom across Europe has handed providers a new problem: how to efficiently manage hundreds to thousands of ONT units when every OLT vendor has its own interface, your billing sits in a different system, and the field technician still scribbles serial numbers onto a paper form. The GPON module in ISPadmin unifies the entire process into a single pane of glass – from service activation to billing and IPTV. Here is what that looks like in practice.

Why managing GPON without an integrated system is slow and expensive

Most ISPs that are building or expanding an FTTH network end up running the same scenario over and over. A customer orders a service, the technician drives to the socket, mounts the ONT, and comes back to the office with a slip of paper carrying a serial number. The back office then has to:

Log into the OLT vendor’s web interface.
Assign the ONT to a specific port.
Switch to the billing system and create the service for the customer by hand.
Double-check that the parameters match.
If IPTV is bundled in, repeat the process in yet another system.

The result? On average 15–30 minutes of administration per activation, a high risk of a typo in the serial number, and no automatic reconciliation of data between OLT, billing, and the customer record. For an ISP with dozens of activations a month, that’s a full-time headcount doing work that could be automated – and spending the time elsewhere would create far more value.

What the GPON module in ISPadmin does differently

The GPON module in ISPadmin is designed to collapse that whole workflow into a single interface. Neither the technician nor the back office has to flip between three systems – everything happens on the customer card.

OLT data retrieval over SNMP. ISPadmin connects to your OLT via the SNMP protocol and automatically pulls the status of every ONT: online/offline, optical signal level, device type, firmware. You don’t have to log anywhere else – the data is right inside the system.

Service activation and deactivation with a single click. When you create a GPON service on the customer card, ISPadmin takes care of the OLT configuration for you. The same goes for termination – no more manually unplugging ports.

Multiport ONT support. If you deploy ONTs with multiple Ethernet ports for different services (typically Internet + IPTV, or Internet for an apartment and an office), the module can split individual ports across different services or customers.

Moving ONTs between customers. Is your customer moving house, or are you taking over a subscriber from another provider? The ONT can be reassigned in a few clicks, and the full history stays attached.

Editing core parameters. Line rate, VLAN, profile – everything is changed from one place, no CLI required.

Internet + IPTV bundled into one GPON service

For hybrid FTTH/IPTV offers, billing is one of the biggest pain points. When a customer has internet on one system and IPTV on another, you end up issuing two invoices, sending two dunning emails, and support has two separate conversation histories.

ISPadmin solves this by running Internet and IPTV as a single GPON service on the customer card. The customer receives:

one invoice,
one card inside the client portal,
one ticket when they call support,
one notification when parameters change.

Internally the services stay separated for reporting and subsidy projects, but toward the customer you present yourself as a single provider with a single message.

Typical technician workflow in the field

What does this look like in practice at an ISP that runs the module end-to-end? Let’s walk through a new customer activation.

1. Order. The customer orders an FTTH service online. Back office creates the customer card in ISPadmin and schedules the installation job for a technician through the Planning module. The technician receives the task – including the address and service type – on their mobile interface.

2. On-site installation. The technician mounts the ONT, scans the serial number (QR code or manual entry) straight into ISPadmin, picks the customer from the list of scheduled installations, and submits.

3. Automatic activation. In the background, ISPadmin pairs the ONT with the OLT port, pushes the configuration (line rate, VLAN, IPTV profile) and activates the service. The technician sees a confirmation within seconds.

4. Customer notification. Through the integrated SMS gateway, the customer gets a confirmation that the service is live, along with portal login credentials.

5. First invoice. In the next billing cycle the system issues the invoice automatically – no extra action required.

Administration that used to consume 20+ minutes spread across three people collapses into a few clicks in a single system.

What this means for ISP operations

A unified GPON workflow has measurable impact:

Fewer billing errors. Because the ONT serial number, service parameters, and billing record are created in one moment from one dataset, typos caused by manual rekeying between systems disappear.

Faster Time-to-Service. New customer activation measured in days, not weeks. In subsidy-backed projects, where the speed of connecting the first subscriber is a tracked KPI, that’s a tangible metric.

Report-ready data for regulators and subsidy programs. Port counts, statuses, and traffic data are available in one system in real time. For providers participating in national broadband or EU-funded programs, that’s a significant saving of time when preparing mandatory reports.

Smoother transition from hybrid networks. If you operate a mixed wi-fi / copper / fiber network, ISPadmin with the GPON module can run all technologies under one roof – you don’t have to build a parallel tool just for fiber.

Who this makes sense for

The GPON module in ISPadmin delivers the most value for:

ISPs currently building or expanding FTTH – they get a tool that scales to thousands of subscribers without further investment in integration.
Providers enrolled in subsidy programs – report-ready data and consistent records save hours when preparing mandatory filings.
ISPs running hybrid networks who don’t want to operate three parallel systems for different technologies.
Small and mid-sized providers for whom a standalone GPON OSS wouldn’t pay off financially, but who still want a professional level of automation.

Compatibility and technical parameters

To avoid any confusion – the GPON module in ISPadmin is a standalone add-on that is not part of the base installation and is licensed separately. The current state of play:

Supported OLT: Huawei devices; development and testing is performed on the Huawei MA5608T and Huawei MA5801 (MA5600 series and above). If you run a different OLT, get in touch – integration is technically feasible and we’re actively expanding support.
Supported ONT: no vendor lock-in. Any ONT compatible with your OLT will do.
Communication protocol: SNMP, so no proprietary interface or CLI access is required.
Management: all specific actions are driven by OID templates, which means adding a new OLT model is a configuration exercise, not a code change.

We recommend verifying the current state of supported devices directly in the documentation or with our sales team, because the list is being extended continuously.

Getting started

If you are evaluating the GPON module or considering a migration from another system, start with the documentation in our wiki (GPON Introduction and the GPON Module Manual), which lists currently supported platforms, licensing requirements, and a first-configuration guide.

The post GPON from A to Z: How to Run Your Entire FTTH Network from One Place in ISPadmin – from ONT Activation to IPTV Service first appeared on ISPadmin.

Sales Opportunities in ISPadmin: Keep Track of Every Opportunity

Šárka — Mon, 13 Apr 2026 08:36:33 +0000

How many business opportunities slipped through your fingers in the past month simply because they weren’t recorded anywhere? If your sales team manages leads in spreadsheets, notes, or just in their heads, it’s time for a change. The new Sales Opportunities module in ISPadmin helps you capture every opportunity and guide it all the way to a successful close.

What the module offers

The Sales Opportunities module brings a complete tool for managing your sales process directly into ISPadmin. You can record leads — initial contacts and inquiries — and convert them into sales opportunities with assigned clients, products, and estimated value. Each opportunity moves through a defined pipeline with custom stages and win probability, giving you an instant overview of where each deal stands.

The module also includes activity management — you can log meetings, calls, and emails directly within the sales opportunity, plan next steps, and track the full communication history. Labels, filters, and sorting help you stay organized even with dozens of open opportunities.

Practical benefits for ISPs

Centralized records: All leads and sales opportunities in one place — no more spreadsheets or scattered notes.
Pipeline visualization: Instant overview of all opportunities thanks to a visual pipeline with win probabilities.
Integration with customer database: Each sales opportunity is directly linked to an existing client in ISPadmin — contact details, services, and communication history are always at hand.
Team collaboration: Multiple users can be assigned to each opportunity, enabling effective teamwork within the sales team.
Measurable results: Win and Loss statuses, including reasons for closing, allow you to analyze sales performance.

How does it work?

A salesperson creates a lead with contact details and a description of the inquiry. Once qualified, the lead is converted into a sales opportunity — assigning a client from the database, selecting products or services, setting priority, and estimating deal value.

The opportunity then progresses through pipeline stages (Qualification, Proposal, Negotiation, etc.), each with a defined probability of success. The salesperson continuously logs activities and plans next steps. At the end of the process, the opportunity is closed as either Won or Lost.

The entire process is clearly visualized in a pipeline view directly within the sales opportunity detail.

Interested in trying the Sales Opportunities module? Schedule a no-obligation demo or contact us at sales@ispadmin.eu.

The post Sales Opportunities in ISPadmin: Keep Track of Every Opportunity first appeared on ISPadmin.

Quick Notes in ISPadmin: No Idea Left Behind

Šárka — Wed, 01 Apr 2026 08:12:45 +0000

The new Quick Notes feature in the Planning module lets technicians and administrators capture ideas, reminders, or tasks in seconds — right from the system header, with the ability to link them to a specific client, router, or POP.

Anyone working at an ISP knows the feeling. You’re handling a ticket, a customer calls, you’re checking a device — and suddenly something important comes to mind. But opening a new task takes too long, and by the time you get to it, the thought is gone.

One Click from the Header

Quick Notes are accessible via the Quick Actions button (Plus icon) directly in the ISPadmin header. You don’t need to navigate anywhere or leave the page you’re working on. Click, type your note, and save — the whole thing takes just a few seconds.

Link Anything with @

The key feature is the ability to link a note to a specific element in the system. Simply type the @ symbol in your note and choose from three options: Router, Client, or POP. The system will then offer a search, allowing you to easily assign the note to the right object. When you come back to it later, you’ll immediately know what it’s about.

Overview and Management

All your notes are available on the Planning → Quick Notes page. Here you can browse, edit, or delete them. Notes are displayed in a clear list, so nothing gets lost.

Team Permissions

Access to the Quick Notes page requires setting the appropriate permissions in Settings → Administrators → Administrators, under the Quick Notes section. This way, you can precisely control which users have access to this feature.

Who Benefits Most?

Quick Notes are especially useful for field technicians (via the mobile app), dispatchers handling requests, network administrators during diagnostics, and team leaders during planning.

Conclusion: Quick Notes are available from ISPadmin version 5.41. A detailed guide can be found at wiki.ispadmin.eu in the Planning section. If you haven’t tried ISPadmin yet, test it with our free demo at ispadmin.eu/demo.

The post Quick Notes in ISPadmin: No Idea Left Behind first appeared on ISPadmin.

How to Keep Your Entire ISP Network Under Control from a Single System

Šárka — Tue, 17 Mar 2026 10:32:12 +0000

Running an internet service provider involves handling dozens of tasks every day: new installations, service interventions, customer requests, billing, network monitoring, and coordinating technicians in the field. When this information is scattered across multiple tools, confusion quickly follows. Technicians cannot see customer details, administration cannot track installation status, and management lacks a clear overview of network operations.

That is exactly why ISPadmin was created – a system that connects all key ISP processes into a single environment.

One System for Customers, Services, and the Network

ISPadmin allows you to manage:

customer database
internet services and tariffs
network infrastructure
installations and service interventions
customer communication
billing and operational finance

All of this information is interconnected. When solving an issue, a technician can immediately see not only the customer contact but also their services, communication history, and scheduled tasks.

More Efficient Work for Technicians

A large part of an ISP’s work takes place in the field. With the planning module, you can:

schedule installations
manage service interventions
assign tasks to technicians
track work progress

Each technician receives a clearly defined task, the necessary customer information, and can immediately record the result of their field visit.

Less Administration

Automation is key to efficient ISP operations today. ISPadmin helps with:

automated billing
service management and records
handling customer requests
tracking technician work
maintaining a clear overview of the network

As a result, a large portion of manual administrative work is eliminated.

Overview for Management

ISP owners and operations managers need a quick overview of what is happening in their company. ISPadmin provides insights such as:

number of active customers
status of installations
technician workload
overview of services and tariffs
operational network information

All in one place.

Software That Understands ISPs

ISPadmin was developed specifically for the needs of internet service providers. Because of this, it offers features that standard CRM or billing systems typically lack – such as linking customers, services, network infrastructure, and service tasks. The result is a platform that helps manage daily ISP operations more efficiently.

Want to see the system in action? We would be happy to show you how ISPadmin can support your company.

👉 Schedule a free system demo.

The post How to Keep Your Entire ISP Network Under Control from a Single System first appeared on ISPadmin.