Size SIP concurrency from the smallest of profile, account and runner limits

Raising a Telnyx outbound voice profile's channel limit does not by itself raise call capacity. The profile limit covers only outbound legs, here one per simultaneous warm transfer. An account-wide outbound limit is shared by every profile, including staging; setting a profile above it fails with a 422, and raising it takes a support request. Inbound is limited separately by the connection's inbound channel limit, where null means unlimited. Real capacity is the minimum of these, the runner call slots (minus slots lost if one runner fails) and any LiveKit participant limits. Count worst-case load as inbound legs plus one outbound leg per concurrent transfer. Also check the profile's daily spend cap and destination whitelist: a destination outside the whitelist is rejected with SIP 403.

Applies when: planning or debugging how many concurrent calls and transfers a SIP setup can carry. Keywords: Telnyx outbound voice profile channel limit concurrency account limit inbound channel limit LiveKit SIP capacity whitelist 403