412 4xx Client error RFC 3903
SIP 412 Conditional Request Failed
A conditional PUBLISH failed because the entity tag (SIP-If-Match) did not match.
Advertisement
Common causes
- Presence state published with a stale entity tag.
How to fix it
- Let the client publish fresh state without the condition.
Seeing 412 on calls through a router or firewall? Check that SIP ALG is disabled. It causes a surprising number of SIP errors. Read why.
About 4xx responses
The request has a problem or cannot be completed at this server, usually because of something on the requesting side or the target user.