ISP Billing ISP Billing Documentation
Italiano Back to website
Telecommunications

OpNet: SIMs, profiles, VAS, and coverage

Configure OpNet, inventory and assign SIMs, manage lifecycle, profiles and VAS, and check coverage.

Last updated: 2026-08-19

Module scope

OpNet connects ISP Billing with the contracted mobile platform for SIM inventory, remote state, first activation, suspension, reactivation, termination, navigation profiles, VAS services, geographic coverage, and public lead routing.

The remote platform remains authoritative for the SIM and network operation, while ISP Billing links the ICCID to the CRM customer, commercial service, billing, and local history. Do not use OpNet state changes as a substitute for the service lifecycle or vice versa; reconcile both after every operation.

API and VAS catalogue

Configure endpoint, App ID, bearer token, username and password from the same OpNet MVNO environment. Define each allowed VAS with its exact provider ID, operator-facing description and permitted parameter names/values. A friendly label never replaces the technical code.

Protect credentials and verify connectivity before loading inventory.

Insert a SIM

Add the complete physical ICCID only after verifying that it belongs to the ISP’s OpNet allocation. Keep leading digits and the full provider format; do not shorten it to a printed serial fragment.

ISP Billing queries OpNet before storing the resource, records the remote identifier, state, service type, and class, and rejects a duplicate already owned by another tenant. A successful insertion creates inventory only: it does not assign the SIM to a customer or activate mobile service.

List, inquiry, and detail

The inventory uses cursor pagination and combines ICCID, provider identifiers, remote state, service class, customer relationship, linked services, and locally recorded VAS. Use filters and detail to distinguish free stock from assigned or operational SIMs.

Inquiry uses the SIM ID and available Record ID to retrieve current provider data before sensitive actions. Compare ICCID, record, state, class, customer, service, profile, and VAS. A stale local row should be synchronized rather than manually edited to imitate the remote platform.

Customer and service assignment

Assign the SIM to the correct CRM customer first. A service may select only a SIM owned by that same customer; the same ICCID cannot be attached to another non-terminated OpNet service. Removing or changing ownership requires reviewing every dependent service.

Lifecycle and state

First activation requires Record ID, Area Code and service type. Available actions depend on remote state: activate, suspend, reactivate or terminate. These are separate provider operations with different commercial consequences. Re-read Inquiry after every request and reconcile the service instance and billing.

Navigation profile

The preliminary profile check sends SIM ID, Record ID, target Service Type and Area Code and returns ChangeProfile/ChangeSim guidance. Continue only when the provider permits it and the APN, capacity and restrictions match the contracted catalogue.

Do not confuse profile change, SIM replacement and reactivation. After execution, verify the returned profile; where operational confirmation is unavailable, stop after the preliminary check and follow the agreed provider procedure.

VAS services

Read active VAS, then add or remove only an ID present in the configured and provider-supported catalogue. Addition can include dynamic parameters and Area Code and stores the returned provider data; removal requires an existing SIM/VAS association. Check price, consent and compatibility first.

Coverage and public script

Internal coverage sends latitude and longitude to the OpNet GIS. The public script can style input and button placeholder/text, colors, borders, radius, padding and custom CSS. Configure a redirect for every OpNet Service Type and a separate nocoverage destination.

Test covered, uncovered and invalid coordinates on desktop and mobile. A GIS result is not an activation guarantee and redirect markup must never expose credentials.

Unbilled services

The reconciliation view finds customer-owned SIMs without a linked service field or whose matching service is still in progress. Review customer, ICCID, remote state, VAS, order and billing period before linking, charging, suspending or terminating anything.

Checklist

  • Protect OpNet credentials
  • Verify ICCID and tenant
  • Assign the correct customer
  • Prevent multi-service use
  • Validate activation fields
  • Re-read each remote state
  • Separate suspend/reactivate/terminate
  • Check VAS price and consent
  • Reconcile unbilled services