Peeling Back the SIP Resiliency Layers

Like most people, I like it when my machines work. If I get into my car and turn the key, I expect the engine to start and the tires to roll. Of course, I play an important role in keeping my Prius on the road. I follow the manufacturer’s recommended maintenance schedule. I keep the tires inflated and regularly check the tread for excessive wear. In the case of an unforeseen breakdown, I travel with a few essential tools and know who to call if a problem surpasses my ability to fix it.

Just like my car, SIP resiliency needs to be a layered approach.   While it’s impossible to build a system that is completely unbreakable, it’s not that difficult to eliminate all single points of failure and design something that can handle a myriad of software, hardware, and signaling failures.

In my latest article for No Jitter, I look at the three major subsystems of a SIP infrastructure and discuss how each one can be made robust and resilient.

Peeling Back the SIP Resiliency Layers

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: