What does HRESULT 0x80F00008 (RTC_E_PINT_STATUS_REJECTED_PL_FAILED) mean?

RTC_E_PINT_STATUS_REJECTED_PL_FAILED

Operational meaning: RTC_E_PINT_STATUS_REJECTED_PL_FAILED

Read this result as an RTC state-machine result: at this point in a PINT gateway reporting the PSTN-side result of a requested telephone service, the primary telephone leg failed before the requested PINT service could be completed.

Log this result as 0x80F00008 in the RTC PINT-status facility, not only as a signed decimal; the facility distinguishes local RTC validation from a response status mapped by the stack.

The first useful check is to capture primary-leg setup stage, switch cause, number normalization result, and whether a secondary leg started. The result must be separated from nearby conditions because Primary Leg Failed identifies service sequencing; it is broader than busy or no-answer outcomes.

Signals worth preserving

• Code-specific proof: capture primary-leg setup stage, switch cause, number normalization result, and whether a secondary leg started.
• Correlation key: PINT request/correlation ID.
• Protocol or object snapshot: service and telephone number hashes.
• Last completed transition: primary/secondary leg outcome.
• Expected output: gateway and switch timestamps.

Recovery and control flow

Resolve this result at its producing layer: correct the primary-leg route or input and restart the whole service request only after confirming no surviving leg; after it, a separate UI or watchdog retry must wait until that layer reports a final state.

Example: A callback service cannot establish the initial call to the requesting user, so it never dials the destination.

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.

Verification workflow

1. Record it and 0x80F00008 at the first RTC method or event that returns it.
2. Apply one controlled change: correct the primary-leg route or input and restart the whole service request only after confirming no surviving leg; then verify the result return value and resulting RTC state.

Actions that do not address this condition

• Do not reinterpret a PSTN leg result as a SIP transport outage.
• Do not expose complete telephone numbers in general application logs.

Do not confuse it with

Comparison point: Switch Failed identifies the PSTN switching function rather than one defined service leg.

Technical references

• Microsoft RTC return constants.
• PINT service protocol.