| Previous | Next |
| RTC_E_PINT_STATUS_REJECTED_NO_ANSWER | RTC_E_PINT_STATUS_REJECTED_PL_FAILED |
RTC_E_PINT_STATUS_REJECTED_ALL_BUSY
What the RTC value marks: RTC_E_PINT_STATUS_REJECTED_ALL_BUSY
The legacy RTC Client API reports this result while working with a PINT gateway reporting the PSTN-side result of a requested telephone service; the precise meaning of it is every eligible PSTN destination or attempted leg was busy, not merely that a call or registration failed.
For correlation, retain 0x80F00007 in the RTC PINT-status facility together with this result; generic HRESULT text can otherwise hide the protocol family and the exact RTC branch.
The quickest way to localize this result is to preserve the candidate set and per-leg result that led to the aggregate outcome; the important boundary is that this is an aggregate terminal result, not a single busy branch.
Protocol and object state
| RTC area | PINT telephone-service outcome |
|---|---|
| Objects to correlate | PINT request, gateway, primary and secondary PSTN legs, switch outcome and cancellation state |
| Condition to prove | every eligible PSTN destination or attempted leg was busy |
| Safe corrective direction | stop branch attempts for the current request and schedule only policy-approved retry |
PINT extends SIP/SDP to request telephone-network services; these status values describe PSTN execution rather than ordinary SIP proxy routing. A signaling request can be accepted by the gateway yet later fail because one leg is busy, unanswered, invalid, or rejected by the switch.
Evidence that separates the cause
- Code-specific proof: preserve the candidate set and per-leg result that led to the aggregate outcome.
- Identity and target:
PINTrequest/correlation ID. - State at production: service and telephone number hashes.
- Timing and ordering: primary/secondary leg outcome.
Related RTC results
Comparison point: RTC_E_PINT_STATUS_REJECTED_BUSY can apply to one selected leg.
RTC_E_PINT_STATUS_REJECTED_CANCELLED | the PINT telephone-service request was cancelled before completion |
|---|---|
RTC_E_PINT_STATUS_REJECTED_NO_ANSWER | the PSTN call attempt rang or progressed but was not answered within the service window |
RTC_E_PINT_STATUS_REJECTED_BADNUMBER | the supplied telephone destination could not be accepted as a routable number for the PINT service |
A safe diagnostic sequence
- Confirm the distinction that this is an aggregate terminal result, not a single busy branch.
- Start a fresh operation after you stop branch attempts for the current request and schedule only policy-approved retry, and compare its final state with the failing run.
How to handle the result
The owning RTC component should stop branch attempts for the current request and schedule only policy-approved retry; it should also settle or cancel its previous operation before callers begin a replacement.
Example: A service tries several numbers for a user and receives a busy indication from each.
Actions that do not address this condition
- Do not expose complete telephone numbers in general application logs.
- Do not reinterpret a PSTN leg result as a SIP transport outage.
Technical references
Looking for a different code? Search another status or error code.