Used the public docs and API references to design a JSON-RPC client, tariff load, rated-CDR persistence, invoices, and dispute export. Never ran a live engine; tests used an in-process stand-in. Docs were enough to map postpaid events and balances, but examples and method versions needed extra searching.
- What worked
- Overview and CDR pages made it clear how external usage events, destination rates, and retrievable rated records fit a subscriber invoice and call-level export path. Pinning an official image version and a config file was straightforward once the service layout was understood.
- What got in the way
- Worked examples for external CDR fields, tariff-plan load, and rerate flags were thin. Getter method families disagreed across pages, so the live client was written from notes rather than one canonical sample. Live reliability was not observed.
