SIP 199 Early Dialog Terminated vs 483 Too Many Hops
SIP 199 (Early Dialog Terminated) is a 1xx Provisional response, while 483 (Too Many Hops) is a 4xx Client Failure 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, 483 means that the Max-Forwards header has reached zero, indicating the request has passed through too many proxies.
Описание
A UAS can send this to indicate that an early dialog has been terminated. Used when forking results in multiple early dialogs.
Когда вы это видите
In forked call scenarios when one of the forked branches is cancelled because another branch was answered.
Как исправить
No action needed. This is normal behavior in forked call setups. Ensure your UA handles early dialog termination gracefully.
Описание
The Max-Forwards header has reached zero, indicating the request has passed through too many proxies.
Когда вы это видите
When a request traverses more proxies than the Max-Forwards counter allows (default 70). Often indicates a routing loop.
Как исправить
Check for routing loops. If the path is legitimately long, increase Max-Forwards. Usually indicates misconfigured routing.
Ключевые различия
199 is a 1xx Provisional response, while 483 is a 4xx Client Failure 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 483: The Max-Forwards header has reached zero, indicating the request has passed through too many proxies.
You encounter 199 when in forked call scenarios when one of the forked branches is cancelled because another branch was answered.
You encounter 483 when when a request traverses more proxies than the Max-Forwards counter allows (default 70). Often indicates a routing loop.
Когда что использовать
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 483 (Too Many Hops): Check for routing loops. If the path is legitimately long, increase Max-Forwards. Usually indicates misconfigured routing.