| Previous | Next |
| RTC_E_PINT_STATUS_REJECTED_SW_FAILED | RTC_E_PINT_STATUS_REJECTED_BADNUMBER |
RTC_E_PINT_STATUS_REJECTED_CANCELLED
What RTC_E_PINT_STATUS_REJECTED_CANCELLED means in RTC
Diagnosis begins inside a PINT gateway reporting the PSTN-side result of a requested telephone service, where the relevant condition for this HRESULT is the PINT telephone-service request was cancelled before completion.
The numeric form of this result is 0x80F0000A in the RTC PINT-status facility; an exception translator handling it should preserve this value before converting it into application-facing call or presence states.
Evidence should show that you correlate the cancellation source and time with gateway and leg state; the diagnostic distinction is that cancellation is an intentional terminal state, not evidence that a number, switch, or network was defective.
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 | the PINT telephone-service request was cancelled before completion |
| Safe corrective direction | stop all pending legs, acknowledge final state once, and prevent late callbacks from reviving the request |
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.
How to prove the condition
- Use protocol and object evidence to correlate the cancellation source and time with gateway and leg state.
- Confirm the distinction that cancellation is an intentional terminal state, not evidence that a number, switch, or network was defective.
- Start a fresh operation after you stop all pending legs, acknowledge final state once, and prevent late callbacks from reviving the request, and compare its final state with the failing run.
The result diagnosis is strongest when object state and protocol trace share timestamps and transaction identifiers; when diagnosing this result, avoid treating packet capture and HRESULT logging as substitutes for one another.
Nearby failure modes
Comparison point: No Answer is produced by timeout without a cancellation decision.
RTC_E_PINT_STATUS_REJECTED_BADNUMBER | the supplied telephone destination could not be accepted as a routable number for the PINT service |
|---|---|
RTC_E_PINT_STATUS_REJECTED_ALL_BUSY | every eligible PSTN destination or attempted leg was busy |
RTC_E_PINT_STATUS_REJECTED_NO_ANSWER | the PSTN call attempt rang or progressed but was not answered within the service window |
Minimum incident record
- Code-specific proof: correlate the cancellation source and time with gateway and leg state.
- Owning object: service and telephone number hashes.
- Wire evidence: primary/secondary leg outcome.
- Lifecycle state: gateway and switch timestamps.
Correct application response
To correct this, stop all pending legs, acknowledge final state once, and prevent late callbacks from reviving the request.
Example: The user cancels a pending callback while the gateway is still dialing the first leg.
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.