Next Big Thing is Here – SIP trunks for Voice!

Having been in the Telecom field for well over twenty years, we were always saddled with certain decisions when it came to trunks to PSTN (Public Switch Telephone Network).  If you could live with marginal voice quality or didn’t have the budget to pop for a T-1 voice circuit, you had few options.  Your choices were between using POTS lines, CO (Central Office) trunks, or tie trunks if multi-location. These were typically analog with a snap, crackle, pop reminiscent of Rice Krispies1

The other choice was a voice T-1 or PRI flavor, both of which we were more expensive, but as it was digital, it was crystal clear and the bonus was it only used four wires for 24 phone lines or 23 for PRI (ISDN Primary Rate Interface). Heck, even I paid for PRI though I did not have a need for all the lines as I could not accept sacrificing call quality.

Fast-forward to today and Session Initiation Protocol, aka SIP. There are a lot of cool things about it, but it’s important to understand its current form of implementation.  It can also be implemented in a couple different manners. It can be delivered by your carrier over Ethernet, but don’t think that it will conflict and turn into a VoIP chattering, as it comes in on its own circuit. Alternately, as it is a protocol, it can also be delivered over existing MPLS circuits for multi-location businesses as long as QoS is enabled.  Important to note is that the SIP connection provided by your carrier is from your phone system/PBX to the carrier. The calls to the outside world are still carried through PSTN so the quality will remain acceptable.Print

What is so cool about SIP? First off, it handles both voice and video. But here is the really neat thing, much like a SuperTrunk of days gone by or the PRI of today, if you need less that 20-some lines, but want the robust DID (Direct Inward Dial) functionality, SIP trunks are for you.  Here’s a real scenario. I pay $250 per month for a PRI, but I can get 5 each SIP trunks (at $12 each for 3-year commitment) for $60 a month!  This will save me $190 per month and that’s a good thing – a real good thing!

SIP trunks may not be for everyone and may not even be available in your area, but if considering a new phone system or a new carrier, you should at least consider SIP trunks. If you’re simply changing telecom carrier and want to entertain SIP trunks, you will need to check to see if your phone system is SIP-trunk ready and capable.  Those pesky details!

If you want to know more or if you area or phone system is SIP-trunk ready, feel free to give us a call. We’re here to help!



Roundbrix – Moving to Take your IT Dollar Further!

What’s important to you? We think it should be the best use and longest life of each dollar spent on IT. It means really evaluating a few facets of each purchase.

Total Cost over Useful Life must Equal Business Value. Yeah, it’s a mouthful, but let’s think about that for a moment. The annual cost must be of business value, in other words, the benefit should be equal to, or preferably greater, than the cost. Here’s how we figure it out.

This must include all costs. Cost of item, tax, shipping and handling. But also important are items like annual maintenance and foreseeable costs outside what is covered. The name of the game has to be to cap your costs, but in doing so, you may overpay. Hardware support is a gamble in two ways. First, you’re betting that the cost of the support is less than a few service calls. Secondly, what is the most important thing to understand about support contracts is that you will always receive more timely response support over those that have no contract. So at this point, you need to figure out what an hour, or a day – or two – of downtime means to your operation. This is really what the hardware maintenance contract hedges against.

Software support must be factored in as well, but before signing up to 15-25% per year of retail cost (not what you paid for it), ask yourself a simple question. Am I going to benefit here? The answer lies in evaluating the situation. If you’re deploying a new ERP system, by ALL means, get the support for the first year to get through it. But once it’s stable and assuming you’re not in need of constant updates tied to a software agreement, that money might be better used for other business purposes. You can always re-up later

Very important here is to be realistic as to useful life. When considering the purchase, ensure you are not under buying to save a thousand dollars, but then your solutions only lasts for three years and you were thinking six years. This short-term savings just cost you a ton of money, and you not only have to repurchase, but pay the cost and endure the pain of redeployment.

If something (like a server or a phone system) is scalable, meaning you can buy what you need today and add to it later without performing a forklift upgrade, that may be another way to pull out a win.

Probably the most important point here about useful life is how a few dollars can hedge an earlier-than-expected retirement of your systems. Thinking down the road a few years and being just short of a clairvoyant will serve you well.

As we have been at this for many years, we know how long stuff lasts – period. We thought we would share our experience here to help you make better and more informed decisions .

AVAYA IP Office – 7 years minimum. Look, there are no moving parts and upgrades are a couple hundred dollars and a few hours, it’s a solid telephony solution.

Cisco VoIp – 5 years maximum. Our experience here in supporting these systems has been that a couple years in, it requires an expensive upgrade to remain compatible with the latest Windows systems on which the Agents reside. A workaround here is to run XP in Virtual Mode. The other reason that life is limited to 5 years is that the servers/hardware they place them on are typically only warrantied for 5 years max.

Exchange Server – 5 to 7 years. Most companies here skip every other version of exchange, so most folks going to Exchange 2010 today are on Exchange 2003. This helps defray deployment costs by ‘skipping’ a deployment cycle. And these days, Dell and soon others will warranty servers for 7 years, as it makes business sense.

Firewalls – 4-5 years. This is typically as long as the manufacturer is comfortable standing behind the product. Also pay attention to “trade-up” programs and try to pre-purchase at least two years of support as it’s cheaper that way.

Switches – 7 years+. The HP Procurve line carries a lifetime warranty, so unless you need more functionality, like PoE (Power over Ethernet) built-in, use it as long as you can.

In the end, it’s all about the best use of strategic IT dollar and how you stretch and leverage your expenditures.

We’ve moved! We now have a 50% larger data center with more rack space, all the bells and whistles, and are able to host more cost- effective solutions like cloud hosting, SBS hosting, web hosting and proactive system monitoring. Also, if you’re moving, we can be your stop-gap for mission-critical applications as we can host your systems as you transition.

Recently, we also have become both a Juniper Networks and Barracuda Networks partner to add to our list of strategic partnerships. The way we see it, if we can deploy the solutions for companies, we don’t need to make as much in the sale of the hardware and software solutions, controlling your total cost of deployment.


Roundbrix is Hosting an AVAYA IP Office Demonstration . . . and feeding you!

To me, there’s nothing like “seeing is believing”. I’ve been in telecom and computers, well, let’s put it this way. When I was a kid, I used to go to Thrifty’s drug store and test my vacuum tubes to see which one had failed so I could get my Zenith shortwave radio working again to listen to Chick Hearn in his early years – and I digress.


Flash forward, I have been in IT 30 years and we’re all over what is new. But newer is not always better, as so many of us have learned. The key in entertaining any new voice technology platform is asking a few simple questions:


Is what we have now at or near “end of life”, meaning we’re looking at a replacement anyways?

Is it better than what we have now, and if so how? Will it help us be more efficient in a tangible manner?

• What if we don’t do anything, what might be the downsides?

• If I get this, will it scale for my needs for many years downstream?

• Does it have a useful life of more than 5 years, thus lessening my annual total cost of ownership?


Then I put on my IT and voice hat and ask a few other questions:


• Can I get the best of both worlds – that is less expensive digital phones inside and VoIP for remote sites or remote users and the

functionality is basically the same for both?

• Can I leverage existing CAT3 cabling so I can use the CAT5e for data at 1Gbit (as although some IP phones have 1Gbit switch, they

come at a cost premium)?

• As handsets tend to be about half of the hardware cost, can I leverage any of my existing handsets so I can upgrade the ‘core’ now,

and handsets later to hedge costs?

• Can I use packet-tagging if using VoIP so I don’t have to create VLANs?

• Can it “follow me” so it stays current with my mobile world?

• Does it integrate into my Microsoft environment and have functionality such as Unified Messaging?

• Are the phones full duplex so they don’t cut out while on speakerphone?

• Does it have conference bridge ability and automatically adjust levels so everyone can be heard?

• Can it use remote IP phones in a widely distributed environment of both remote sites and individual users?


Lastly, I have an additional consideration for those contemplating or in process of moving. If you are moving, is your money to move your phone system better spent on a new one? Remember, to move the phone system you’ll have to pay cash, but when buying a new system even the labor can be bundled into the lease, so your out-of-pocket during the expense of the move can be reduced, at least on the voice end.


So being an authorized AVAYA IP Office Reseller, we figured the best way for you to know if this is something you might want or need, is to tell you about it, show it to you, and feed you to limit your out-of-pocket time!


To attend, please RSVP to Shani Griffis at 949 273 5220 or . We have limited space so please reply promptly to ensure a spot!

Look before you VoIP!

As technology would have it, the train keeps moving forward, but at times it feels like we’re losing passengers. A lot of new speak and talk, but what does it all mean? In this ever-changing world, technologies are leap-frogging one another. How decision-makers choose today makes more difference than ever. Not just for the initial purchase, but in coming years. Allow me to me explain.

For background purposes, I have been in technology for over twenty years and have seen a lot, but the VoIP thing has a lot of folks perplexed, and for good reason. Here, I will try to clarify the most common areas of confusion. We want to help you make a smarter decision here as you entertain your next phone system or a move where maybe your current phone system has seen better times.

Understanding the Cost Components. As with any technology, what’s important is to clearly understand the cost components to any system. In doing so, the cost/benefit equation needs to remain in balance. With a phone system, there is: 1) the infrastructure (main pieces), 2) the handsets, 3) the adjuncts (other pieces connected), and 4) the ongoing cost of maintenance which include moves, adds and changes. At the end of the day, we need to have an understanding of total cost over useful life and then employ the cost/benefit equation. The longer the useful life, clearly the less cost per year, so this component is truly key.

Understanding Reusable Items. Here’s where a lot of savings can occur. For many manufacturers, like AVAYA, the reuse of phone sets as much as 5-7 years back can allow you to either significantly reduce the cost, or perhaps buy the infrastructure pieces first, followed by new handsets over time. I cannot stress how much this can save, but over 30% savings is not uncommon. Upgrading from same brand to same brand is typically the only scenario in which this strategy works well.

Another important reuse item is premise cabling, specifically CAT3 cabling still in so many buildings. Only AVAYA can reuse all your existing cabling by using digital phone sets which have the same functionality as VoIP, without the chatter!

Digital versus IP Phones. Here’s where the rubber meets the road. Let’s start with costs. An IP Phone will run you $400 to $500 for Avaya and a bit more for Cisco. Digital sets are $100-$150 less and basically have the same functionality. You also need to know that if you plan on or need to run gigabit Ethernet at the desktop and use the same network drop, the IP phone needs to be gigabit as well. If not, you just slowed down the PC’s network speed tenfold. Ouch!

You may also need to replace your network switch with a PoE (Power over Ethernet) switch at a cost of $3,000 and up for a managed PoE switch offering, which you need to prioritize voice traffic to eliminate VoIP chatter. PoE essentially powers the IP phone, otherwise you’ll have to pay another $50-$80 per power supply. It’s really not structured to save you a whole lot.

So let’s say you are a single facility with 25-75 users. There is no real benefit for VoIP handsets. But say you have 50 people in one location, a smaller location with 10 folks and another 15 sales folks in regional home offices. Now you could benefit from VoIP. It would be nice if there was a best of both worlds scenario. Well, you’re in luck!

What you do in this situation is implement an Avaya IP Office 500, deploy the lesser expensive digital handsets in the office, and deploy VoIP softphones or handsets in the field. The routers we use in home offices are $80 each and properly tag voice packets to minimize or eliminate VoIP ‘chatter’.

VoIP Downsides. I love technology, probably more than most folks. I live it, breathe it, and at times, get frustrated with it. But at the end of the day, the name of the tech game is to not make it more complicated or have more pieces than necessary. This strategy tends to keep costs under control and makes troubleshooting simpler.

But there are a few significant challenges to VoIP. The first is the chatter component. Look, we can control voice packet priority on the one or two ends we control (main site and remote site), but we cannot control the Internet itself and latency and congestion issues within. This chatter can be quite prevalent, especially if you choose a ‘hosted’ VoIP solution.

The second downside is if you have all of the voice and data on the same switch (as is the VoIP model) and the switch fails, you not only lose all of your data traffic, but your ability to make and receive calls as well. Double ouch! A failed router can have a similar effect as well. So you moved up in technology, but added points of failure. Not sure about the win here.

A third issue is that data issues can now affect voice, and this includes troubleshooting, which now gets a bit more involved and costly. So a bad PC network card could bring your voice quality to its knees. Also, you could have a glitch on the data network which could effectively drop every voice call in the building. Not nice!

Summary. The items here are not meant to discourage the newer VoIP technology, but to help in selecting the proper technology best suited for the need and not overcomplicate your infrastructure. It’s important to keep it as simple as possible, which will keep the total cost of ownership (TCO) well in check.