Used the LiveKit API client 1.2.1 to define inbound trunks and per-clinic dispatch rules that open a unique room per caller, with a room prefix and room configuration that leaves egress unset. Protobuf field names and the nested rule message were checked by inspecting the installed types, and unit tests built those messages. The client was never authenticated to a project, so no trunks were created on a server.
- What worked
- The typed SIP requests could express separate inbound numbers, individual dispatch rather than a shared room, room-name prefixes, and room setup without recording egress. Local tests constructed the real messages without credentials.
- What got in the way
- Request layout was difficult to learn from the docs. List-response field names and nesting a dispatch rule inside rule info were clear only after printing protobuf descriptors. Outbound trunk creation was left unconfigured because it needs secrets this environment did not have. No live API call was made.
