| Previous | Next |
| RTC_E_STATUS_CLIENT_NOT_FOUND | RTC_E_STATUS_CLIENT_NOT_ACCEPTABLE |
RTC_E_STATUS_CLIENT_METHOD_NOT_ALLOWED
What the RTC value marks: RTC_E_STATUS_CLIENT_METHOD_NOT_ALLOWED
When RTC returns this result, the relevant contract is a peer, proxy, registrar, or gateway returning a specific SIP response to the RTC transaction, and it says that the target resource recognizes SIP but does not allow the requested method.
This result carries 0x80EF0195 in the RTC SIP-status facility carrying status 405; store the result value at the first RTC callback or method boundary, before retry logic replaces it with a broader timeout or connection message.
Start the result investigation by having the trace capture the Allow header, target URI, method, and resource state; do not skip the distinction that Method Not Allowed concerns this resource; 501 means the server does not implement the method at all.
Protocol and object state
| RTC area | SIP final response |
|---|---|
| Objects to correlate | SIP request method, client transaction, response status, dialog identifiers and method-specific headers |
| Condition to prove | the target resource recognizes SIP but does not allow the requested method |
| Safe corrective direction | select an allowed method or feature path and do not retry the prohibited method unchanged |
Evidence that separates the cause
- Code-specific proof: capture the Allow header, target URI, method, and resource state.
- Identity and target: request method and Request-URI.
- State at production: responding Via hop.
- Timing and ordering: Call-ID/CSeq/tags.
Related RTC results
Comparison point: 501 Indicates implementation-wide lack of support rather than resource-specific policy.
RTC_E_STATUS_CLIENT_CONFLICT | the legacy RTC peer reported a conflict with current resource or transaction state |
|---|---|
RTC_E_STATUS_CLIENT_TEMPORARILY_NOT_AVAILABLE | the addressed user or endpoint is temporarily unavailable at all currently known contacts |
RTC_E_STATUS_CLIENT_BAD_EXTENSION | the server requires removal of a SIP extension it does not understand |
A safe diagnostic sequence
- Collect enough evidence to capture the Allow header, target URI, method, and resource state.
- Test the competing explanation explicitly, because Method Not Allowed concerns this resource; 501 means the server does not implement the method at all.
- Apply the targeted fix — select an allowed method or feature path and do not retry the prohibited method unchanged — and validate both protocol completion and object cleanup.
How to handle the result
To correct this, select an allowed method or feature path and do not retry the prohibited method unchanged.
Example: A presence resource allows SUBSCRIBE but rejects an attempted MESSAGE method and lists supported methods.
Actions that do not address this condition
- Do not retry every 4xx or 5xx response with the identical request.
- Do not show a reason phrase as trusted server identity or authorization evidence.
Technical references
Looking for a different code? Search another status or error code.