Authentication workflows
Support PPPoE, MAC-based, static IP and hotspot designs across different subscriber access environments.
Access policy with subscriber context
RADIUS server software for ISP AAA and bandwidth management.
Control who connects, which service they receive and how activity is accounted for—while keeping subscriber, billing and support teams aligned.
Why it matters
Turn network access into a managed subscriber lifecycle.
RADIUS brings authentication, authorization and accounting into a consistent exchange between subscriber records and access infrastructure. For an ISP, the operational value comes from connecting that exchange to packages, billing status, IP allocation and support context.
PHP Radius provides one operating layer for subscriber access and surrounding workflows. Teams can manage common authentication methods, monitor sessions and usage, apply service policy and investigate issues without treating the RADIUS server as an isolated system.
Core capabilities
Manage access decisions with the full account in view.
Bring authentication and accounting signals together with the customer and commercial information required to act on them.
Authorization and service policy
Relate the authenticated subscriber to the configured package, addressing and bandwidth policy used by the network.
Accounting and usage context
Keep session and traffic information available for operational review, customer support and subscriber visibility.
Bandwidth control
Apply plan and policy controls and inspect usage behavior at subscriber and network level.
IP pools and addressing
Coordinate subscriber addressing, IP pools, routes and DHCP-related workflows through the supported network integration.
Multi-zone operations
Organize access infrastructure and subscribers across service areas while retaining centralized visibility.
How the workflow connects
From access request to accountable service.
A connected workflow gives NOC and support teams a clearer explanation for what happened at each stage.
-
01
Identify the subscriber
Receive the access request and relate it to the correct subscriber account and authentication method.
-
02
Authorize the service
Return the configured service context, such as the applicable package, policy or addressing details.
-
03
Observe the session
Track active sessions and accounting information to understand connectivity and usage.
-
04
Support the customer
Use subscriber, billing and network context together when diagnosing access or performance questions.
Operational value
Designed for the teams that operate subscriber access.
The same access event has different meaning for the NOC, billing team and customer-care desk. Shared context keeps those interpretations aligned.
For the NOC
Monitor active subscriber sessions, network access state, traffic context and the infrastructure involved.
For customer support
Start with the subscriber record and investigate authentication, package, billing and session context in one place.
For management
Standardize access workflows across zones and infrastructure without losing the commercial view of each subscriber.
Common questions
What ISP teams usually ask.
These answers cover the core workflow. We can confirm compatibility and deployment details for your environment during a demonstration.
What does RADIUS AAA mean for an ISP?
AAA refers to authentication, authorization and accounting. Together, these functions identify the subscriber, determine the permitted service and record session activity used for operations and reporting.
Which subscriber authentication methods does PHP Radius support?
PHP Radius supports PPPoE, MAC-based, static IP and hotspot-based authentication workflows for different access-network designs.
Can PHP Radius work with multiple NAS or BNG devices?
Yes. PHP Radius is designed for multi-vendor NAS and BNG environments, with centralized subscriber and operational visibility. Compatibility and available actions depend on the specific deployment.
How does bandwidth management connect to billing?
The subscriber package and service policy can be managed alongside billing and renewal context. The configured network integration determines how policy is enforced on the access infrastructure.
Can PAI help investigate unstable subscriber sessions?
PAI uses subscriber and network context to support guided diagnostics and pattern detection, including PPPoE flapping detection for repeated connection instability.
Planning resources
Prepare the workflow before implementation.
Use practical guidance to document requirements, test cases and ownership before changing production operations.
See it in your environment
Bring your access policy and subscriber workflow together.
Tell us about your authentication methods, NAS or BNG environment, zones and bandwidth policies. We’ll map the relevant PHP Radius workflows to your network.