SIP

SIP 100 Trying vs 422 Session Interval Too Small

SIP 100 (Trying) is a 1xx Provisional response, while 422 (Session Interval Too Small) is a 4xx Client 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, 422 means that the request's Session-Expires value is too small. The Min-SE header in the response indicates the minimum acceptable session interval.

Deskripsi

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.

Ketika Anda Melihatnya

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.

Cara Memperbaiki

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

Deskripsi

The request's Session-Expires value is too small. The Min-SE header in the response indicates the minimum acceptable session interval.

Ketika Anda Melihatnya

When using SIP session timers (RFC 4028) and the proposed session refresh interval is below the server's minimum.

Cara Memperbaiki

Increase the Session-Expires value to at least the value indicated in the Min-SE header of the 422 response.

Perbedaan Utama

1.

100 is a 1xx Provisional response, while 422 is a 4xx Client 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 422: The request's Session-Expires value is too small. The Min-SE header in the response indicates the minimum acceptable session interval.

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 422 when when using SIP session timers (RFC 4028) and the proposed session refresh interval is below the server's minimum.

Kapan Menggunakan Yang Mana

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 422 (Session Interval Too Small): Increase the Session-Expires value to at least the value indicated in the Min-SE header of the 422 response.

Pelajari Lebih Lanjut