40 terms · 5 groups
ISP and WISP glossary
A shared vocabulary for operators, finance staff and support agents. Start with a term, understand why it matters, then follow a guide where one is available.
These are industry definitions, not a list of ISPAgents features.
Find a termAccess
- PPPoE
Point-to-Point Protocol over Ethernet creates a subscriber session over an Ethernet access network.
Why it matters. Separate discovery failures from authentication failures before changing a customer password.
- IPoE
IP over Ethernet carries subscriber IP traffic without a PPP session, often using DHCP for address assignment.
Why it matters. Plan how the access port, VLAN or DHCP information identifies the subscriber; an IP address alone can change.
- Hotspot
A location or access service that provides network connectivity, commonly over shared Wi-Fi.
Why it matters. Separate radio coverage problems from login, voucher and session-limit problems.
- Captive portal
A web page where users sign in, pay or accept terms before receiving broader network access.
Why it matters. A portal login does not prove that DNS, upstream connectivity or the purchased service works.
- VLAN
A virtual LAN separates an Ethernet network into distinct logical broadcast domains.
Why it matters. A wrong VLAN tag can isolate an otherwise healthy subscriber link.
- CGNAT
Carrier-grade NAT lets multiple subscribers share public IPv4 addresses through translation in the operator network.
Why it matters. Inbound connections and fault attribution need extra planning; a shared public IP does not identify one subscriber.
- MTU
Maximum Transmission Unit is the largest packet a link can carry without fragmentation at the relevant layer.
Why it matters. Encapsulation reduces available payload. A mismatch can leave small requests working while larger transfers stall.
- MSS
TCP Maximum Segment Size is the maximum TCP data payload a peer advertises it can receive in one segment.
Why it matters. MSS clamping can help TCP across a smaller path MTU, but does not fix UDP or every path discovery problem.
AAA: authentication, authorization and accounting
- AAA
Authentication checks identity, authorization decides permitted service, and accounting records session activity.
Why it matters. A successful login does not prove the right speed policy was applied or that usage records arrived.
- RADIUS
A protocol through which access equipment requests authentication and service authorization from a server; a companion protocol records session usage.
Why it matters. Keep login decisions, applied service policy and usage records distinct when diagnosing an outage.
- NAS
The Network Access Server admits subscriber connections and acts as a RADIUS client.
Why it matters. Identify the correct access router before investigating a reject or trying to change a live session.
- Access-Reject
A RADIUS response denying an access request.
Why it matters. It is a received refusal, not a timeout. Check the server decision and subscriber policy before assuming a transport failure.
- CoA
A Change of Authorization request asks the access equipment to change authorization for an existing session.
Why it matters. Supported attributes vary. Confirm the response and actual session behavior before treating a policy change as applied.
- Disconnect-Request
A RADIUS dynamic authorization message requesting termination of a matching session.
Why it matters. A customer may reconnect immediately if authentication still permits access; disconnecting is not a durable suspension policy.
- Accounting
RADIUS accounting reports session starts, stops and, where configured, interim usage updates.
Why it matters. Missing or delayed records can distort online status and usage totals; accounting is not an invoice ledger.
- Framed-IP (Framed-IP-Address)
A RADIUS attribute used to communicate the IPv4 address assigned to a subscriber session.
Why it matters. Distinguish the subscriber address from the NAS address and any public address after NAT.
- Mikrotik-Rate-Limit
A MikroTik vendor-specific RADIUS attribute describing rate limits and optional burst settings.
Why it matters. Read rx/tx from the router’s perspective: subscriber upload/download. Reversing them applies the wrong service speeds.
Devices
- CPE
Customer Premises Equipment is network equipment installed at the subscriber’s premises, such as a router, radio or optical terminal.
Why it matters. Record model, serial number and subscriber assignment so support investigates the correct device.
- ONT
An Optical Network Terminal terminates a passive optical access connection at the subscriber side.
Why it matters. Check optical and registration state before treating an ONT problem as a Wi-Fi fault.
- OLT
An Optical Line Terminal is the operator-side equipment serving optical subscriber terminals on a PON.
Why it matters. A shared OLT port or feeder fault can affect many subscribers at once.
- TR-069 / CWMP
The Broadband Forum specification and CPE WAN Management Protocol used for remote device configuration and management.
Why it matters. A TR-069 label alone does not prove that a particular firmware exposes the parameters or diagnostics you need.
- ACS
An Auto-Configuration Server manages CPE through CWMP sessions.
Why it matters. Correct server address, trust settings and device credentials are prerequisites for reliable management.
- Inform
The CWMP message a CPE sends to open a management session and report identity, events and selected parameters.
Why it matters. The last Inform is evidence of management contact, not proof that the subscriber can browse the internet.
- USP / TR-369
The User Services Platform defines communication between device agents and controllers for management and service control.
Why it matters. Qualify the exact model, firmware, transport and data model before planning a rollout.
- SNMP
Simple Network Management Protocol reads management objects and supports notifications and, when permitted, writes.
Why it matters. Interface counters help locate congestion; they do not automatically identify the subscriber or the cause of a fault.
- Syslog
A standard way for devices and applications to send event messages to a log receiver.
Why it matters. Consistent timestamps and device identity help connect a reboot or link change to a support incident.
- RouterOS REST
The HTTP-based JSON API for reading and changing supported RouterOS resources and running commands.
Why it matters. Restrict reachability and permissions, verify TLS, and validate writes before using the API on customer-serving routers.
Billing
- Prepaid
A billing model in which payment buys service time or usage before it is consumed.
Why it matters. Define activation and expiry clearly, especially when a payment arrives after service has expired.
- Postpaid
A billing model in which service or usage is charged after the relevant period.
Why it matters. Keep billing periods, due dates and collection follow-up clear to avoid disputes over unpaid balances.
- Grace period
A defined interval after a due date or expiry during which a stated service or payment concession applies.
Why it matters. Document when it ends and what access remains; staff should not need to improvise exceptions.
- Dunning
The organized follow-up of overdue amounts through reminders and collection steps.
Why it matters. Check payment evidence before sending another reminder to a customer who may already have paid.
- Proration
A proportional charge or credit for part of a billing period.
Why it matters. Agree the day-count and rounding rules before a mid-period installation or plan change.
- Paybill / till
Merchant collection identifiers used by mobile-money services. Paybill commonly includes a customer account reference; till payments commonly identify a merchant.
Why it matters. Confirm the provider’s reference fields so a received payment can be matched to the right subscriber.
- Mobile-money reconciliation
Matching provider transactions and settlements with internal payment, invoice and balance records.
Why it matters. Investigate duplicates, fees and unmatched references before treating a receipt as a fully allocated payment.
- Credit note
A document reducing or correcting an amount previously invoiced.
Why it matters. Keep it linked to the original invoice and distinguish an account credit from money actually refunded.
Operations
- FUP
A Fair Usage Policy states how usage thresholds or conditions affect a service.
Why it matters. Explain measurement periods and any speed changes before sale so support can apply the published terms consistently.
- Contention ratio
The ratio of aggregate subscriber access capacity sold to the shared capacity available at a specified bottleneck.
Why it matters. It is a planning ratio, not a speed guarantee. Check busy-hour demand and the actual limiting link.
- 95th percentile
A traffic measurement threshold with about 95% of samples at or below it; some transit contracts use it for billing.
Why it matters. Confirm sampling interval, traffic direction and contract rules. It measures a rate, not total transferred data.
- SLA
A Service Level Agreement defines measurable service commitments and the conditions attached to them.
Why it matters. State the measurement window, exclusions and remedy; an uptime percentage alone does not describe the agreement.
- Truck roll
A technician visit to a customer or network site to install, diagnose or repair equipment.
Why it matters. Collect remote evidence first and record the required parts so a visit has a clear purpose.
Discuss a guided pilot
Bring your access method, device models and billing workflow. Agree the scope and limits of an ISPAgents guided pilot before testing.
Ask about a guided pilot