Chose this as the retail rater and built a JSON-RPC client plus catalog provisioning from published docs and engine source, without running a live instance. Tests used an in-process fake. The data model matched per-call rating, bundles, roaming destinations, and invoice export.
- What worked
- JSON-RPC methods for external CDRs, accounts, balances, and tariff plans were enough to map home versus roaming categories, IoT as already-rated usage, and dated catalog rows. External CDR cost details as JSON fitted local rated-line storage.
- What got in the way
- The overview docs were not enough to implement the client. External CDR fields and account APIs had to be confirmed from engine source. Shared family balances, expiry on first use, and whether action plans applied took several catalog revisions.
