SIP 488 Not Acceptable Here
The proposed session parameters cannot be accepted at this destination. In voice deployments, media negotiation is a useful first area to investigate.
FoundationalFind your next answer
Search VoIP.info
One search across the technical library, device research, videos, providers and tools.
4 results for “SIP 488”
SIP 406 Not Acceptable
The responder could not generate a response body in any format allowed by the request's Accept header; bind it to the method and application before changing media policy.
RFC 3261, RFC 6665 and RFC 4475 reviewed September 28, 2026; no user agent, notifier, subscription, request, response body or retry was testedSIP 415 Unsupported Media Type
The server rejected a request because a required message body format, content encoding, language or body-handling context was unsupported.
RFC 3261 and RFC 5621 reviewed September 27, 2026; no user agent, proxy, PBX, request body or retry was testedSIP 606 Not Acceptable
The user's agent was reached, but the user cannot adequately support the described session and no other endpoint is expected to answer.
IETF RFC 3261 and current Asterisk hangup-cause, PJSIP codec-negotiation, hangup inspection and PJSIP diagnostic documentation reviewed September 28, 2026; no endpoint, PBX, proxy, provider, codec, SDP, media path, dialplan or live request tested