<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US><div class=WordSection1><p class=MsoNormal>I tend to see a 503 as a symptom of a critical situation (per cpu/cps/license threshold breach). And I would consider 503 spikes a decent canary for a sip trunk coal mine. Others view 503s as business as usual, specifically in LCR arrangements, and don't alarm/study them</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>What's the general idea behind industry best practice? E.g. 503 simply signifies another route should be taken, or 503 is cause for a remedy?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sent from my Windows 10 phone</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>