Kolmisoft MOR: users, credit, and VoIP devices
Configure MOR APIs, manage users, balances and SIP devices, and open contextual remote access.
Last updated: 2026-08-19
Purpose and prerequisites
The integration manages users and devices on a Kolmisoft MOR server from ISP Billing. It supports search, detail, selected updates, credit operations, SIP-device management, and contextual access to MOR.
Before activation, provide a reachable server with APIs enabled, an actual Admin/Master or Reseller account, and the keys required by that MOR installation. All writes remain remote, so reread provider state after every action.
Connection settings
Select the account’s real role and enter the base URL including /billing/, username, password, and API Secret Key. Calls use /billing/api/... and provider-defined request hashes.
Admin/Master sees the scope granted to that account; Reseller remains limited to its users. Do not select Admin to bypass visibility. Protect credentials and diagnose TLS, URL, authentication, role, hash, and empty scope separately.
Reseller UniqueHash
For the Reseller role, enter UniqueHash, used as the registration id and included in the signature. MOR commonly exposes it under API settings, the global Registration URL, or the reseller access path.
Copy it without spaces and do not confuse it with API Secret Key. When read and registration have different outcomes, inspect role, user ownership, UniqueHash, and hash rules.
MOR users
Filter users by ID, username, name, surname, type, and blocked state. Detail includes identity, contacts, owner, tariff, LCR, currency, timezone, and administrative options exposed by the server.
Refresh detail before editing and change only necessary fields. Tariff, LCR, owner, postpaid, and unlimited credit affect routing and financial exposure and must match the customer agreement.
Credit and recharges
A recharge writes an amount and customer-facing comment to MOR. Verify currency, sign, opening balance, supporting payment or document, and returned balance. Never use it blindly to correct an unexplained accounting mismatch.
Available credit, postpaid, and unlimited credit are different concepts. Refresh the user after the operation and reconcile the movement with ISP Billing payments and Cashbook.
SIP devices
User detail lists and creates linked SIP devices. Fields include name, device type, username, host, port, Caller ID, account code, password or secret, and active state; changes must match both MOR and endpoint capabilities.
Generate unique secrets, keep them out of screenshots, and transfer them securely. After create or update, test SIP registration, outbound and inbound calls, Caller ID presentation, and charging.
MOR panel access
The contextual action builds panel access for the selected user and can open MOR in a frame or separate page. Treat it as an administrative session and verify user, role, and server domain first.
Never share temporary URLs or tokens. Direct MOR changes may appear in ISP Billing only after the next refresh.
Diagnosis and checklist
Connection failures can come from a base URL missing /billing/, TLS, credentials, Secret Key, request hash, or role. An empty list can be valid for a reseller with no owned users. Separate authentication, authorization, and absence of data.
- Enable MOR APIs
- Use the correct base URL and real role
- Protect password and Secret Key
- Set UniqueHash only for Reseller
- Verify owner, tariff, and LCR
- Separate balance, postpaid, and unlimited credit
- Reconcile every recharge
- Use unique SIP secrets
- Test registration and calls
- Protect contextual panel access
- Reread remote state after each action