Blog

For years, I have been asked about the death of voicemail. It started at the end of 2014 with Coca-Cola’s announcement that it was disconnecting voicemail, which was followed by similar announcements from companies like JPMorgan Chase. What ended up happening in most cases? The companies didn’t actually completely get rid of voicemail, but they did experiment with eliminating it for certain users or groups of users.

Last week, I introduced SIP and wrote about the use cases around adjunct connectivity and routing. This week, I'll share use cases around SIP trunks and endpoints. Let's get to it!

I don’t think anyone questions the fact that most of enterprise communications is going SIP. We hear it everywhere. But I still get people asking about why it is such a big deal. Isn’t it just another signaling protocol? Is there really a strategic advantage to go SIP? The answer is an overwhelming YES! SIP’s flexibility and interoperability makes it an obvious choice. But I do think it’s important to dive into the details to know exactly why SIP is such a big deal. I think of SIP having three major strategic use cases. Generally in order of adoption, they are:

As a gamer, I'm always amazed by how realistic the modern gaming experience is. I'm currently playing the latest God of War on the PS4, in stunning 4k resolution. I can't help thinking about how far we've come since the video games of my childhood. I vividly remember playing Adventure on my Atari 2600, where your character was represented by a small square able to move from room to room, picking up things that kind of looked like a key or a sword. Pretty amazing transformation since then.