Troubleshooting SIP Endpoints

Understand how uConnected handles SIP response codes when a SIP endpoint rings, connects, declines, cancels or reports another status.

featuresbusinessbusy-endpoint busy endpoint busy endpoint call-connection call connection call connection call-response call response response sip-address sip address sip address sip-endpoint sip endpoint sip-response-code sip response code code sip-troubleshooting sip troubleshooting troubleshooting

SIP response codes tell uConnected whether an endpoint is connecting, has answered, has declined or is unavailable. Your endpoint must return the expected response so uConnected can handle the call correctly.

Responses while connecting

The SIP endpoint should return one of these responses while the call is connecting:

  • 100 — trying
  • 180 — ringing
  • 183 — session progress

When the call connects, the endpoint should return 200.

Responses that stop all ringing

If the SIP endpoint returns 603 (decline) or 487 (cancelled), uConnected stops ringing both the SIP endpoint and the user’s app endpoint, if one is configured.

All other responses

Any other SIP status code is treated as though that endpoint is busy. The other configured endpoints continue to ring as normal.

If calls are not behaving as expected, check the SIP logs for the response returned by the endpoint. Confirm that the endpoint returns 100, 180 or 183 while connecting and 200 once connected, and that it only returns 603 or 487 when all ringing should stop. Your SIP provider or system administrator can help review and adjust these responses.

For setup and management instructions, see SIP Endpoints.