SIP 199 Early Dialog Terminated vs 380 Alternative Service
SIP 199 (Early Dialog Terminated) is a 1xx Provisional response, while 380 (Alternative Service) is a 3xx Redirection response. 199 indicates that a UAS can send this to indicate that an early dialog has been terminated. Used when forking results in multiple early dialogs. In contrast, 380 means that the call was not successful but alternative services are possible. The response body contains a description of alternative services.
Mô tả
A UAS can send this to indicate that an early dialog has been terminated. Used when forking results in multiple early dialogs.
Khi bạn thấy mã này
In forked call scenarios when one of the forked branches is cancelled because another branch was answered.
Cách khắc phục
No action needed. This is normal behavior in forked call setups. Ensure your UA handles early dialog termination gracefully.
Mô tả
The call was not successful but alternative services are possible. The response body contains a description of alternative services.
Khi bạn thấy mã này
Rarely seen in practice. Indicates that the request cannot be fulfilled as-is but the user may be reached via an alternative method.
Cách khắc phục
Check the response body for alternative service descriptions and attempt to reach the user through those channels.
Sự khác biệt chính
199 is a 1xx Provisional response, while 380 is a 3xx Redirection response.
SIP 199: A UAS can send this to indicate that an early dialog has been terminated. Used when forking results in multiple early dialogs.
SIP 380: The call was not successful but alternative services are possible. The response body contains a description of alternative services.
You encounter 199 when in forked call scenarios when one of the forked branches is cancelled because another branch was answered.
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.
Khi nào dùng cái nào
For 199 (Early Dialog Terminated): No action needed. This is normal behavior in forked call setups. Ensure your UA handles early dialog termination gracefully. For 380 (Alternative Service): Check the response body for alternative service descriptions and attempt to reach the user through those channels.