gossipper-buildlisted

# gossipper-build — SIP Scenario Authoring Author valid Gossipper XML scenarios. Pinned to **Gossipper 0.1.60-rtcpmuxpatch2** (sipcapture/gossipper on `main`, audited 2026-05-18). ## When to use this skill - Write a new XML scenario for a specific SIP call flow. - Modify an existing scenario. - Port a SIPp scenario to Gossipper. - Answer "is feature X supported / how do I express Y in Gossipper XML?" ## When NOT to use this skill | Task | Owner | |---|---| | Invoking gossipper, picking transport/rate, deployment | gossipper-run | | Interpreting summary JSON / trace CSVs / call records | gossipper-analyze | | Authoring the 3PCC peer file (CSV `name;host:port`) | gossipper-run (deployment artifact) | | Running `gossipper pcap2scenario` to convert a PCAP | gossipper-run | If the user hands you a PCAP and asks for an XML scenario, the right move is: have gossipper-run invoke `pcap2scenario` first, then this skill cleans up the produced XML. ## Authoring workflow 1. Clarify intent: UAC vs UAS (vs 3PCC). Sequence, expected response codes, auth requirements, media expectations, branching, retries. 2. **Check built-ins first.** If a `-sn <name>` covers the case, no XML is needed. See the built-ins table below. 3. Pick the closest file in `examples/` as a starting point. 4. Declare any needed `<Global>` and `<User>` variables up front. 5. Write SIP flows inside `<![CDATA[ ... ]]>`. Use keywords liberally. 6. Add `rtd="name"` / `start_rtd="name"` on the steps that matter