ISP Software in Uganda
Plan a guided pilot for your Uganda ISP or WISP: one router, a small subscriber sample, whole-shilling UGX evidence and customer language requirements, with explicit gates before live actions.
Agree the Uganda evaluation
Start with the operator's existing setup
This evaluation is for a small or mid-sized Uganda ISP or WISP running MikroTik routers, mixed customer equipment and PPPoE or hotspot access. It is a target operator profile, not a claim about every network in Uganda. Bring router models, firmware versions, renewal rules and a small synthetic subscriber sample. Keep existing billing and access systems authoritative.
Use the migration review to frame coexistence and the MikroTik integration scope to prepare router questions.
Prepaid PPPoE, hotspot sessions and interrupted backhaul
For a Uganda pilot, compare a recurring household PPPoE renewal with a prepaid hotspot session. Write down when validity starts, how unused time is treated and who reviews a disputed renewal. Model the amounts in whole UGX shillings; subscriber billing and service-policy foundations remain guided pilot scope, not a complete prepaid or hotspot billing service.
Rehearse a power cut at the customer CPE and another at the access site. Then simulate a backhaul interruption with the access router still powered. A delayed payment confirmation after connectivity returns must not count as a second payment. Ask the operator to compare the original reference, timestamp and balance before reviewing an access decision. Do not mistake a paid account for proof that the radio backhaul or upstream is working. These are lab evaluation steps, not a promise of outage resilience or offline collection.
Rollout focus
| Area | Guided pilot scope and roadmap requirements |
|---|---|
| Router evidence | MikroTik RouterOS REST backup export, neighbor discovery and enrollment are guided pilot scope. Guarded writes and RouterOS 6 fallback remain product work. |
| Payment evidence | Evaluate provider-neutral mobile-money webhook mapping, signature verification and settlement-import foundations in a guided pilot with synthetic records. |
| Access decisions | Service-policy previews, approvals and mock-safe result recording are guided pilot scope. Live router/RADIUS mutation needs separately proven adapters, permissions and rollback. |
| Field handoffs | Record the installation address, equipment and responsible technician in the sample. A complete technician app remains roadmap. |
Uganda payment integration targets — custom integration, not shipped
These provider names describe local requirements, not working ISPAgents adapters. Public provider information checked on 16 October 2026:
- MTN MoMo Uganda: custom integration; no shipped ISPAgents Uganda client.
- Airtel Money Uganda: custom integration; no shipped ISPAgents client.
Identify the provider account owner, transaction reference, subscriber matching rule and settlement evidence required. Rehearse duplicates, delayed confirmations and partial payments with synthetic records before agreeing any live integration. A provider's service in another country does not establish support here.
UGX amounts in the evaluation
UGX is the Uganda shilling, a zero-decimal currency: use whole shillings, for example UGX 50,000, without fractional shillings. Do not apply a generic cents conversion or silently multiply a sample amount by 100. Confirm each provider's amount encoding separately during custom integration review.
The ISO 4217 currency list records this precision. These are subscriber-record examples for pilot review, not ISPAgents subscription prices, local tax compliance or a promise of live collection. Confirm invoice fields and reconciliation rules with your finance team.
Customer language requirements
Prepare English wording for the review and identify where customers need Swahili or Luganda wording as a roadmap requirement. Ask local staff to review reminders, receipts and support handoffs; do not assume one translation fits every customer. Swahili and Luganda interfaces and localized automated messages are not shipped promises. WhatsApp and SMS customer delivery remain roadmap requirements.
Licensing context
The Uganda Communications Commission (UCC) publishes telecommunications licensing information. Confirm the requirements for your proposed service and network with the UCC and qualified local advisers. This is general planning context, not legal advice or a claim that ISPAgents provides licensing or regulatory compliance.
First workflow to evaluate
Choose 50–200 synthetic customer records and one lab router. Rehearse one renewal with a synthetic payment record and an operator-reviewed access decision. In a guided pilot, service-policy previews and mock-safe results let the team review intended actions. Automatic restoration after a Uganda payment is not shipped in this scope.
Agree who owns finance review, customer wording and rollback. Review the payment pilot scope and RADIUS evaluation guide before choosing an access path. See other country evaluations for market-specific requirements.
Discuss a Uganda pilot
Bring your customer count, router model, billing process, payment provider and language requirements to the scope review. Do not put passwords, API credentials or customer exports in the contact form. Agree a secure handoff during onboarding.
Frequently asked questions
Can we collect Uganda payments through ISPAgents today?
The named local providers require custom integration; live Uganda collection clients are not shipped. Evaluate the provider-neutral payment-evidence foundation in a guided pilot with synthetic records.
How should we prepare UGX sample amounts?
UGX is a zero-decimal currency. Use whole shillings, such as UGX 50,000, with no fractional shillings. Check provider encoding separately; this is not an ISPAgents subscription price.
Will a payment reconnect a PPPoE or hotspot customer?
Automatic restoration is not shipped in this country scope. Evaluate service-policy previews and mock-safe results in a guided pilot, with separate adapter, permission and rollback gates before live access changes.
Continue the operations map.
ISP and WISP software in Algeria
Scope a guided pilot around your payment references, equipment and support procedures in Algeria.
Open pageCountriesISP and WISP software in Bénin
Start with subscriber records and TR-069 device management in Bénin. Evaluate billing and reconciliation foundations in a guided pilot using fictitious XOF records.
Open pageSolutionsAutomatic Internet Suspension Software — Guided pilot
Guided pilot: Preview, queued jobs, approvals, result recording, and a mock-safe worker can be evaluated in a guided pilot. Live router/RADIUS mutation remains gated; automated suspension and restoration are not a shipped promise.
Open pageSolutionsCustomer Self-Service Foundations — Guided pilot
Guided pilot: Field-job lifecycle, serialized stock, basic tickets and subscriber portal flows have narrow synthetic-data proof and remain guided pilots. Physical installs and invite email delivery are unproven. The technician PWA, dispatch board, dedicated stock workspace and IPAM remain roadmap.
Open page