SIP 199 Early Dialog Terminated vs 436 Bad Identity-Info
SIP 199 (Early Dialog Terminated) is a 1xx Provisional response, while 436 (Bad Identity-Info) 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, 436 means that the Identity-Info header contains a URI that the server cannot dereference to obtain the signing certificate.
Description
A UAS can send this to indicate that an early dialog has been terminated. Used when forking results in multiple early dialogs.
When You See It
In forked call scenarios when one of the forked branches is cancelled because another branch was answered.
How to Fix
No action needed. This is normal behavior in forked call setups. Ensure your UA handles early dialog termination gracefully.
Description
The Identity-Info header contains a URI that the server cannot dereference to obtain the signing certificate.
When You See It
When the Identity-Info URI in the request points to an unreachable or invalid certificate location.
How to Fix
Ensure the Identity-Info URI is reachable and points to a valid certificate. Check DNS resolution and TLS configuration.
Key Differences
199 is a 1xx Provisional response, while 436 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 436: The Identity-Info header contains a URI that the server cannot dereference to obtain the signing certificate.
You encounter 199 when in forked call scenarios when one of the forked branches is cancelled because another branch was answered.
You encounter 436 when when the Identity-Info URI in the request points to an unreachable or invalid certificate location.
When to Use Which
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 436 (Bad Identity-Info): Ensure the Identity-Info URI is reachable and points to a valid certificate. Check DNS resolution and TLS configuration.