[VoiceOps] 503 usage

Glenn Geller (VDOPh) ggeller at vdo-ph.com
Tue Dec 13 21:04:43 EST 2016


We frequently encounter carriers that use the 503 for anything they cannot
classify otherwise.

So, generally, unless it is OUR system, we treat 503 as a "Progress to
another route".

In our system, we use our best efforts to classify in a more detailed way,
using other codes where they can be used.

Hope this helps,

*Glenn @ VDO*

On Tue, Dec 13, 2016 at 5:21 PM, <slocoach at gmail.com> wrote:

> 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
> 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?
> Sent from my Windows 10 phone
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20161213/4bbd22c8/attachment.html>

More information about the VoiceOps mailing list