SIP 204 No Notification vs 302 Moved Temporarily
SIP 204 (No Notification) is a 2xx Success response, while 302 (Moved Temporarily) is a 3xx Redirection response. 204 indicates that the request was successful but the server has decided not to send a NOTIFY for this SUBSCRIBE request. In contrast, 302 means that the callee has temporarily moved to a different address. The client should retry the request at the Contact address but continue using the original URI for future requests.
説明
The request was successful but the server has decided not to send a NOTIFY for this SUBSCRIBE request.
このコードが表示される場合
When subscribing to event packages that may not generate immediate notifications, such as dialog or presence packages.
解決方法
No fix needed. The subscription was accepted but there is no state change to notify about yet.
説明
The callee has temporarily moved to a different address. The client should retry the request at the Contact address but continue using the original URI for future requests.
このコードが表示される場合
When a user is temporarily reachable at a different location, such as when traveling or using a different device.
解決方法
Redirect the current call to the Contact URI provided, but keep the original URI for future requests.
主な違い
204 is a 2xx Success response, while 302 is a 3xx Redirection response.
SIP 204: The request was successful but the server has decided not to send a NOTIFY for this SUBSCRIBE request.
SIP 302: The callee has temporarily moved to a different address. The client should retry the request at the Contact address but continue using the original URI for future requests.
You encounter 204 when when subscribing to event packages that may not generate immediate notifications, such as dialog or presence packages.
You encounter 302 when when a user is temporarily reachable at a different location, such as when traveling or using a different device.
どちらをいつ使うか
For 204 (No Notification): No fix needed. The subscription was accepted but there is no state change to notify about yet. For 302 (Moved Temporarily): Redirect the current call to the Contact URI provided, but keep the original URI for future requests.