SIP 180 Ringing vs 513 Message Too Large
SIP 180 (Ringing) is a 1xx Provisional response, while 513 (Message Too Large) is a 5xx Server Failure response. 180 indicates that the UA receiving the INVITE is trying to alert the user. This response is used to initiate local ringback tone at the caller's end. In contrast, 513 means that the server was unable to process the request since the entire SIP message (not just the body) exceeded the size limit.
描述
The UA receiving the INVITE is trying to alert the user. This response is used to initiate local ringback tone at the caller's end.
何时出现
During call setup when the callee's phone is ringing. You should hear a ringback tone after receiving this response.
如何修复
No fix needed — the callee's device is ringing. If the call never connects after ringing, check the callee's device or call forwarding settings.
描述
The server was unable to process the request since the entire SIP message (not just the body) exceeded the size limit.
何时出现
When the total SIP message (headers + body) is too large. Different from 413 which refers only to the body.
如何修复
Reduce the message size by removing unnecessary headers or reducing the SDP size. Consider using UDP-compatible message sizes (< 1300 bytes).
主要区别
180 is a 1xx Provisional response, while 513 is a 5xx Server Failure response.
SIP 180: The UA receiving the INVITE is trying to alert the user. This response is used to initiate local ringback tone at the caller's end.
SIP 513: The server was unable to process the request since the entire SIP message (not just the body) exceeded the size limit.
You encounter 180 when during call setup when the callee's phone is ringing. You should hear a ringback tone after receiving this response.
You encounter 513 when when the total SIP message (headers + body) is too large. Different from 413 which refers only to the body.
何时使用哪个
For 180 (Ringing): No fix needed — the callee's device is ringing. If the call never connects after ringing, check the callee's device or call forwarding settings. For 513 (Message Too Large): Reduce the message size by removing unnecessary headers or reducing the SDP size. Consider using UDP-compatible message sizes (< 1300 bytes).