<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Justin Downes</title>
    <description>The latest articles on DEV Community by Justin Downes (@justindownes).</description>
    <link>https://dev.to/justindownes</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4250616%2F1cb0cbbe-6475-42cd-a5d2-f70666fb4ce8.png</url>
      <title>DEV Community: Justin Downes</title>
      <link>https://dev.to/justindownes</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/justindownes"/>
    <language>en</language>
    <item>
      <title>SIP response codes: what they mean and what to check</title>
      <dc:creator>Justin Downes</dc:creator>
      <pubDate>Tue, 17 Nov 2026 22:02:05 +0000</pubDate>
      <link>https://dev.to/justindownes/sip-response-codes-what-they-mean-and-what-to-check-d5a</link>
      <guid>https://dev.to/justindownes/sip-response-codes-what-they-mean-and-what-to-check-d5a</guid>
      <description>&lt;p&gt;SIP response codes are the three-digit numbers a phone system, provider or softphone sends back to say what happened to a request: whether a call is ringing, was answered, was refused, or failed somewhere along the way.&lt;/p&gt;

&lt;p&gt;I built a free &lt;a href="https://www.softpagecms.com/sip-response-codes/" rel="noopener noreferrer"&gt;SIP response code lookup&lt;/a&gt; that covers all 75 codes in the IANA registry, with the RFC that defines each one and what to check on a PBX or softphone. You can paste a status line such as &lt;code&gt;SIP/2.0 403 Forbidden&lt;/code&gt; straight from a trace. This post covers the parts you need most often.&lt;/p&gt;

&lt;h2&gt;
  
  
  The six classes
&lt;/h2&gt;

&lt;p&gt;The first digit tells you most of what you need before you look up the exact code.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;1xx Provisional:&lt;/strong&gt; the server is handling the request, for example &lt;code&gt;100 Trying&lt;/code&gt; or &lt;code&gt;180 Ringing&lt;/code&gt;. Not a final answer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;2xx Success:&lt;/strong&gt; the request worked. For a call, &lt;code&gt;200 OK&lt;/code&gt; means it was answered.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;3xx Redirection:&lt;/strong&gt; the user is at another address, given in the Contact header.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;4xx Client error:&lt;/strong&gt; the request failed at this server, for example wrong credentials, an unknown number or no codec in common.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;5xx Server error:&lt;/strong&gt; a server failed to handle a request that was itself valid.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;6xx Global failure:&lt;/strong&gt; the request will fail everywhere, for example the user declined the call.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Normal codes that look like errors
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;401 Unauthorized&lt;/code&gt; and &lt;code&gt;407 Proxy Authentication Required&lt;/code&gt; are usually not problems. They are the server asking for credentials; the phone resends the request with them. Only repeated 401s or 407s point to a wrong username, password or realm. Likewise, &lt;code&gt;487 Request Terminated&lt;/code&gt; simply means the caller hung up before the call was answered.&lt;/p&gt;

&lt;h2&gt;
  
  
  The codes worth investigating
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;403 Forbidden:&lt;/strong&gt; the account may not make this call (dialling rules, international barring), or the provider does not accept requests from your IP address.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;404 Not Found&lt;/strong&gt; and &lt;strong&gt;484 Address Incomplete:&lt;/strong&gt; a number or dial plan problem.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;408 Request Timeout&lt;/strong&gt; and &lt;strong&gt;480 Temporarily Unavailable:&lt;/strong&gt; the far end could not be reached, often an unregistered phone or an expired NAT binding.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;488 Not Acceptable Here:&lt;/strong&gt; no codec or encryption method in common. This is common between WebRTC clients and PBXs, because the browser offers DTLS-SRTP over &lt;code&gt;UDP/TLS/RTP/SAVPF&lt;/code&gt; and the PBX endpoint must accept it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;503 Service Unavailable:&lt;/strong&gt; a trunk or route is down, or the server is overloaded.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Two cases from real deployments
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;488 on Asterisk with PJSIP.&lt;/strong&gt; In a &lt;a href="https://github.com/InnovateAsterisk/Browser-Phone/issues/301" rel="noopener noreferrer"&gt;Browser Phone issue&lt;/a&gt;, the Asterisk log showed &lt;code&gt;Couldn't negotiate stream&lt;/code&gt; just before the 488, after authentication had already succeeded. That line confirms a media mismatch rather than a password problem, so the place to look is the endpoint's WebRTC media settings, not the credentials.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A 503 the PBX never sent.&lt;/strong&gt; In a browser phone, SIP.js generates a 503 itself when its WebSocket connection fails, so the PBX never saw the request. In &lt;a href="https://github.com/InnovateAsterisk/Browser-Phone/issues/557" rel="noopener noreferrer"&gt;another Browser Phone case&lt;/a&gt; the WebSocket closed during the TLS handshake (close code 1015); putting a reverse proxy in front of Asterisk fixed it. If a browser phone reports 503, check the WebSocket and its TLS certificate before the PBX.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finding the code in your own calls
&lt;/h2&gt;

&lt;p&gt;The quickest way to see the codes for a failing call is a SIP trace. On Linux, &lt;a href="https://www.softpagecms.com/2025/05/06/sngrep-sip-debugging-tool/" rel="noopener noreferrer"&gt;sngrep&lt;/a&gt; shows each call as a ladder diagram. On Asterisk, &lt;code&gt;pjsip set logger on&lt;/code&gt; prints every SIP message to the console. If headers look mangled, a router feature called SIP ALG is a frequent cause.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;p&gt;The code list and names follow the &lt;a href="https://www.iana.org/assignments/sip-parameters/sip-parameters.xhtml#sip-parameters-7" rel="noopener noreferrer"&gt;IANA SIP response codes registry&lt;/a&gt;. &lt;a href="https://www.rfc-editor.org/rfc/rfc3261" rel="noopener noreferrer"&gt;RFC 3261&lt;/a&gt; defines most of the codes; the &lt;a href="https://www.softpagecms.com/sip-response-codes/" rel="noopener noreferrer"&gt;lookup&lt;/a&gt; links each code to the RFC that defines it.&lt;/p&gt;

</description>
      <category>voip</category>
      <category>webrtc</category>
      <category>asterisk</category>
      <category>networking</category>
    </item>
  </channel>
</rss>
