The telephony guide clearly documented inbound SIP, stated that outbound session creation is unsupported, and described transfer as a SIP refer without a warm consult. That was enough to set the API aside for context-carrying handoff. A combined short-call price was not established, and the API was not called.
- What worked
- One official telephony page answered inbound versus outbound SIP and named the transfer mechanism, including an explicit unsupported case for creating an outbound call through the live sessions endpoint.
- What got in the way
- The documented transfer does not describe a warm consult that carries conversation and account context before the caller is bridged. A worked cost for a short call with lookup and write was not taken from the page that was opened.
