SIP 100 Trying vs 502 Bad Gateway
SIP 100 (Trying) is a 1xx Provisional response, while 502 (Bad Gateway) is a 5xx Server Failure response. 100 indicates that the request has been received by the next-hop server and an unspecified action is being taken to process it. The UAC should expect additional responses. In contrast, 502 means that the server, acting as a gateway or proxy, received an invalid response from a downstream server it accessed in attempting to fulfill the request.
Beschreibung
The request has been received by the next-hop server and an unspecified action is being taken to process it. The UAC should expect additional responses.
Wann Sie es sehen
Immediately after sending an INVITE. The proxy has received the call and is searching for the callee. This is the SIP equivalent of a dial tone.
Wie man es behebt
No fix needed — this is normal call setup behavior. If stuck on 100 Trying for too long, check network connectivity and proxy configuration.
Beschreibung
The server, acting as a gateway or proxy, received an invalid response from a downstream server it accessed in attempting to fulfill the request.
Wann Sie es sehen
When a SIP proxy receives a malformed or invalid response from the next-hop server. Common in interop scenarios between different vendors.
Wie man es behebt
Check the downstream server's health and configuration. Verify SIP message formatting between the two servers. Review network connectivity.
Wesentliche Unterschiede
100 is a 1xx Provisional response, while 502 is a 5xx Server Failure response.
SIP 100: The request has been received by the next-hop server and an unspecified action is being taken to process it. The UAC should expect additional responses.
SIP 502: The server, acting as a gateway or proxy, received an invalid response from a downstream server it accessed in attempting to fulfill the request.
You encounter 100 when immediately after sending an INVITE. The proxy has received the call and is searching for the callee. This is the SIP equivalent of a dial tone.
You encounter 502 when when a SIP proxy receives a malformed or invalid response from the next-hop server. Common in interop scenarios between different vendors.
Wann welchen verwenden
For 100 (Trying): No fix needed — this is normal call setup behavior. If stuck on 100 Trying for too long, check network connectivity and proxy configuration. For 502 (Bad Gateway): Check the downstream server's health and configuration. Verify SIP message formatting between the two servers. Review network connectivity.