WimeRadius: setup, profiles, and accounts

What WimeRadius integrates

WimeRadius connects ISP Billing with WIME for access accounts, Radius profiles, IP addresses, and CRM customer synchronization. It is independent from ISP Radius 2.0, Radius Manager, Radius Lucy, and other Radius providers.

The commercial service remains in ISP Billing; WIME stores network credentials and remote technical parameters. Linking them keeps activation, suspension, and termination traceable.

Prerequisites

Enable the contracted module, grant only the required permissions, and identify the authoritative WIME environment. Prepare a reachable API host, dedicated credentials, understood remote profiles, customer installation addresses, and the ISP’s IP-assignment policy.

Do not provision the same access through another Radius connector without a migration plan. Decide which system owns customer data, account state, and IP allocation.

API settings

Enter the WIME host, API username, and password. Verify DNS, network path, TLS where provided, authentication, and authorization before creating production accounts.

Keep credentials server-side and out of screenshots and logs. A successful login does not prove that the account may create users, change state, allocate IPs, or read profiles; verify required operations separately.

Radius profiles

Synchronize the remote profile catalog manually after confirmation or enable the supported scheduled synchronization. Review profile name, technical meaning, rate, access policy, and intended commercial offer.

Catalog import does not assign profiles to customers automatically. After changes in WIME, inspect created, updated, removed, or renamed profiles and reconcile existing accounts before using new values.

CRM PUSH mapping

Map each safe ISP Billing source field to the exact remote property expected by WIME. Sources can include standard CRM fields, calculated values, and CRM custom fields. Address without street number and street number remain separate.

Obtain target property names from WIME documentation or support and never guess them. Exclude passwords, unrelated notes, and unnecessary personal data.

When customer PUSH runs

Saving a CRM customer triggers PUSH when the module, credentials, and mapping are active. A missing mapping table retains the historical payload for backward compatibility, which must be reviewed before relying on it.

Test one complete controlled record, verify the remote result, then test updates and empty values. Avoid bulk edits until field ownership, formatting, and error handling are understood.

Create a WimeRadius account

Select the correct customer and installation address, then enter unique username and password, optional static IP, remote profile, and lifecycle state. The installation address must already be maintained in CRM.

The free-IP lookup asks WIME for a candidate; verify it against the ISP addressing plan, routing, pool ownership, and existing assignments before saving.

State, connection, and actions

The account page and service management render local data immediately and retrieve live state and session details from WIME in the background. The remote request does not block pagination, products, or other page operations; an error leaves the interface usable and marks live state as unavailable.

Disconnect ends only the current session. Suspend changes authorization, while Activate restores it according to the provider workflow. Do not repeat an action after timeout until its actual result is known.

CPE SNMP diagnostics

Device type and SNMP community are stored on the individual account. Without an override, reads use the framedipaddress of a WIME session with an active acctsessionid. For a bridged CPE, enable Query a different IP, enter its static address, and press OK: the stored target remains usable while PPPoE is offline. Disable the flag and confirm to restore the live address.

With an operational Edge Agent or configured MikroTik bridge, the page automatically starts an unsaved live check: Generic runs ten pings and specific device types run ping and SNMP separately. Manual verification stores one valid sample and temporary monitoring retains up to 20.

Customer service link

A WimeRadius service instance can create or link the technical account and display username, profile, address, and state. Service activation, suspension, reactivation, and termination invoke the module adapter where configured.

Do not edit only the Radius account to conceal an inconsistent commercial service. Identify the authoritative workflow and reconcile both sides.

Customer Area, credentials, and unbilled services

Customer Area exposes only the permitted service summary and never API credentials or internal provider fields. Credential email uses the linked customer and configured template; verify identity, recipient, content, and secure delivery.

Unbilled services identifies active technical accounts without the correct commercial association. Confirm ownership, service, period, and billing before suspending, terminating, or deleting anything.

Checklist

• Choose WIME as the single authority for the intended access
• Enable module and least-privilege permissions
• Use dedicated API credentials
• Verify environment and operation-specific authorization
• Synchronize and understand remote profiles
• Map exact WIME properties
• Keep address and street number separate
• Test CRM PUSH and updates on controlled data
• Verify customer, address, profile, and IP assignment
• Distinguish disconnect from suspension
• Reread remote state after every action
• Reconcile account, service, and billing