SIP

SIP 100 Trying vs 606 Not Acceptable

SIP 100 (Trying) is a 1xx Provisional response, while 606 (Not Acceptable) is a 6xx Global Failure response. 100 indicates that the request has been received by the next-hop server and an unspecified action is being taken to process it. The UAC should expect additional responses. In contrast, 606 means that the user's agent was contacted successfully but some aspects of the session description (SDP) are not acceptable. Unlike 488, this is a global failure — no other server can satisfy this request.

Description

The request has been received by the next-hop server and an unspecified action is being taken to process it. The UAC should expect additional responses.

When You See It

Immediately after sending an INVITE. The proxy has received the call and is searching for the callee. This is the SIP equivalent of a dial tone.

How to Fix

No fix needed — this is normal call setup behavior. If stuck on 100 Trying for too long, check network connectivity and proxy configuration.

Description

The user's agent was contacted successfully but some aspects of the session description (SDP) are not acceptable. Unlike 488, this is a global failure — no other server can satisfy this request.

When You See It

When the callee definitively cannot accept any of the offered media types or codecs. Different from 488 which is location-specific.

How to Fix

Check the Warning header or response body for which session parameters are unacceptable. Modify the SDP offer to use compatible codecs and media types.

Key Differences

1.

100 is a 1xx Provisional response, while 606 is a 6xx Global Failure response.

2.

SIP 100: The request has been received by the next-hop server and an unspecified action is being taken to process it. The UAC should expect additional responses.

3.

SIP 606: The user's agent was contacted successfully but some aspects of the session description (SDP) are not acceptable. Unlike 488, this is a global failure — no other server can satisfy this request.

4.

You encounter 100 when immediately after sending an INVITE. The proxy has received the call and is searching for the callee. This is the SIP equivalent of a dial tone.

5.

You encounter 606 when when the callee definitively cannot accept any of the offered media types or codecs. Different from 488 which is location-specific.

When to Use Which

For 100 (Trying): No fix needed — this is normal call setup behavior. If stuck on 100 Trying for too long, check network connectivity and proxy configuration. For 606 (Not Acceptable): Check the Warning header or response body for which session parameters are unacceptable. Modify the SDP offer to use compatible codecs and media types.

Learn More