SIP 204 No Notification vs 380 Alternative Service
SIP 204 (No Notification) is a 2xx Success response, while 380 (Alternative Service) 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, 380 means that the call was not successful but alternative services are possible. The response body contains a description of alternative services.
Описание
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 call was not successful but alternative services are possible. The response body contains a description of alternative services.
Когда вы это видите
Rarely seen in practice. Indicates that the request cannot be fulfilled as-is but the user may be reached via an alternative method.
Как исправить
Check the response body for alternative service descriptions and attempt to reach the user through those channels.
Ключевые различия
204 is a 2xx Success response, while 380 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 380: The call was not successful but alternative services are possible. The response body contains a description of alternative services.
You encounter 204 when when subscribing to event packages that may not generate immediate notifications, such as dialog or presence packages.
You encounter 380 when rarely seen in practice. Indicates that the request cannot be fulfilled as-is but the user may be reached via an alternative method.
Когда что использовать
For 204 (No Notification): No fix needed. The subscription was accepted but there is no state change to notify about yet. For 380 (Alternative Service): Check the response body for alternative service descriptions and attempt to reach the user through those channels.