What does HRESULT 0x80F00005 (RTC_E_PINT_STATUS_REJECTED_BUSY) mean?

RTC_E_PINT_STATUS_REJECTED_BUSY

Operational meaning: RTC_E_PINT_STATUS_REJECTED_BUSY

The operational meaning of this result is tied to a PINT gateway reporting the PSTN-side result of a requested telephone service: the selected PSTN destination returned a busy indication.

The machine-readable identity of this result is 0x80F00005 in the RTC PINT-status facility; the result identity matters because RTC uses separate facilities for API conditions, SIP final responses, and PINT service statuses.

The first useful check is to identify which telephone leg was busy and whether another destination was permitted. The result must be separated from nearby conditions because one busy destination is not the same as all candidate destinations being busy.

Verification workflow

1. Test the competing explanation explicitly, because one busy destination is not the same as all candidate destinations being busy.
2. Apply the targeted fix — apply the service’s alternate-number or delayed-retry policy without treating the IP signaling path as failed — and validate both protocol completion and object cleanup.

Protocol and object state

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.

Signals worth preserving

• Code-specific proof: identify which telephone leg was busy and whether another destination was permitted.
• Correlation key: primary/secondary leg outcome.
• Protocol or object snapshot: gateway and switch timestamps.
• Last completed transition: cancellation or final indication.
• Expected output: PINT request/correlation ID.

Recovery and control flow

The appropriate response to it is not a blanket reconnect. Instead, apply the service’s alternate-number or delayed-retry policy without treating the IP signaling path as failed, while preserving ownership of cleanup and any bounded retry.

Example: A click-to-call request reaches the gateway, but the called telephone line is engaged.

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.

Do not confuse it with

Comparison point: RTC_E_PINT_STATUS_REJECTED_ALL_BUSY aggregates busy results for all usable destinations.

Technical references

• Microsoft RTC return constants.
• PINT service protocol.