Treat pre-connect SIP rejections as provider-confirmed zero cost

An outbound transfer leg that the carrier rejects before ringing, such as SIP 403 with no provider call ID, never connects, so it never gets a billing record. If the finish gate only accepts not-submitted, provider-zero-confirmed or billing-matched legs, that leg stays "submitted, reconciliation pending" for good. Recovery raises, the lease expires, another worker reclaims it, and the cycle repeats. Logs reuse the original request IDs, so it looks like fresh traffic hours later, and restarts do not help. Add a narrow rule that maps exactly that pre-connect rejection to provider-confirmed zero, and run a guarded one-time reconciliation of stuck rows. Keep outcome-unknown legs, legs with no failure reason and legs with connected time failing closed. Also, a 403 is not a person declining and is not a no-answer result.

Applies when: durable telephony usage accounting must finalize outbound legs the carrier rejected. Keywords: Telnyx LiveKit SIP 403 rejection outbound transfer leg billing reconciliation zero cost lease reclaim USER_REJECTED