sinch-elastic-sip-trunkinglisted

# Sinch Elastic SIP Trunking API ## Overview The Sinch Elastic SIP Trunking (EST) API lets you programmatically provision SIP trunks and route voice traffic between customer infrastructure and the PSTN. The core workflow is: create a trunk, authorize it (ACL or credentials), attach endpoints, assign phone numbers. ## Agent Instructions Before generating code, ask the user these clarifying questions: 1. **Direction** — Do you need **inbound** (receive calls from PSTN), **outbound** (send calls to PSTN), or **both**? 2. **Auth method for the trunk** (if outbound or both) — **ACL-based** (static IPs) or **Credential-based** (digest auth / dynamic IPs)? 3. **Endpoint type** (if inbound or both) — **Static endpoint** (fixed IP/port) or **Registered endpoint** (SIP UA registers dynamically)? 4. **Language** — curl, Node.js SDK, Python, Java, .NET? Only ask questions 2-3 when relevant to the user's direction. Wait for answers, then follow the matching workflow below. ## Decision Tree ``` User wants EST → ├─ Outbound only │ ├─ Static IPs → Workflow A (Trunk + ACL) │ └─ Dynamic IPs → Workflow E (Trunk + Credential List / Digest Auth) ├─ Inbound only │ ├─ Static IP → Workflow B (Trunk + Static Endpoint + Phone Number) │ └─ Dynamic IP → Workflow D (Trunk + Credential List + Registered Endpoint + Phone Number) └─ Both → Workflow C (Trunk + ACL/Creds + Endpoint + Phone Number) ``` ## Critical Rules 1. **Dependency order matters.** Creating resources out of