I’ve talked about potential pros of VoIP as it pertains to direct cost savings to the enterprise. There are some hidden benefits of VoIP as well, these don’t get the same attention or get measured like the other well known features.

Since VoIP works over the same infrastructure as your data traffic, this makes it very easy for VoIP systems to be integrated with your data systems. This is becoming more apparent as software like Microsoft’s Exchange 2007 gets released with direct unified communication hooks.

What this means to you is, you can easily integrate your voice and data to have one point of contact for your users. All email, faxes and voicemails come into the same universal inbox, this inbox gets backed up and is accessible via proprietary client (Outlook), web (OWA) or handheld.

Imagine the cost savings, your field and office personnel all use the same method of getting access to all forms of communication. Learning curves get flattened quickly, user productivity rises and users are happier while their frustration levels drop.

Most VoIP systems will offer such integration out of the box with little configuration. A big player, as I mentioned in an earlier article, is Microsoft. Microsoft’s strategy is to leave your phone system as it is and still enable VoIP and Unified Communications via software; Moto – VOIP as you are. Microsoft has already signed up vendor partners like Nortel, D-Link and a few others

Session Initiation Protocol (SIP) is a signaling protocol that is used by technology products for creating session-oriented connections between two or more endpoints on an IP network. These endpoints could be IP telephones, instant messaging clients, or collaborative multimedia conference applications.

Many businesses are sipping it up…(No pun intended) What I mean is, they are taking their time adopting to the technology and for good reason. Although SIP technology is cheaper (In some cases free), the cost of upgrading infrastrucure to support Quality of Service (QOS) can sometimes outweigh the savings.

While the protocol is now “final” enough to build sophisticated telecom systems using SIP, the Internet Engineering Task Force (IETF) working groups continue to forge new ways on how to apply SIP. One way that has been making it’s way to the top is SIP Connect.

What is SIPconnect?

SIPconnect is a standards-based method of interconnection between IP PBXs and VoIP service provider networks. It specifies the architecture, required protocols and features, and implementation rules necessary for seamless peering between IP PBXs and VoIP service providers.

Let’s take a look at the various applications: 

For end users in the small business or large enterprise, SIPconnect eliminates, or greatly reduces, the need for a costly gateway at the end user’s site.  In addition, new features from the service provider or the IP PBX vendor will be delivered more quickly.

For VARs and Interconnects, the SIPconnect compliant service provider will handle the complexites associated with connecting the SIP Trunk to the legacy TDM world.  This eliminates the need for a lot of integration and troubleshooting work and allows the partners to focus on other, revenue generating activities.

For Equipment and Software Vendors (Application Servers, IP PBX Vendors, SIP Proxies), SIPconnect greatly reduces the time and resources required to verify interoperability in the network.  This single item, interoperability, currently drains many man hours from the services and equipment providers that could be better used creating new and more exciting features.  This in turns reduces the amount of revenue that could be realized from those new features.

The SIP Trunking Service Provider that uses SIPconnect SIP trunks realizes higher revenue streams much more quickly.  Network services are rolled out more rapidly, greatly reducing the time to revenue for new services and features.  In addition, the service provider can greatly reduce the time and staff required to complete interoperability testing.

In the meanwhile…While service providers like Cbeyond continue the slow and steady rollout of SIP connect sit back, relax, and take a SIP!

VoIP requires robust infrastructure that has to be operational 24×7. If your email goes down for 10 minutes it’s not as critical, but if your voice services go down for 10 minutes, it’s a huge deal!

Keeping in mind how critical voice communications is, it is essential to plan the network accordingly. Don’t go cheap on the essential infrastructure components like network switches, routers and even cabling. Most companies tend to use the cheapest contractor for cabling when it can be one of the most critical components of the network that can haunt you for years to come. Make sure who-ever installs your cabling tests and certifies it for the amount of data that will be pushed through it.

Use intelligent switches that support multiple VLANs and QoS. This will come in handy to segregate different types of traffic, like data and voice traffic and prioritize voice traffic. VLANs allow you to have one physical network but logically have it split into multiple, so your voice can travel on VLAN1 while your data travels on VLAN2. You can have other services like video travel on VLAN3.

This not only provides your users a better experience for different voice, data and video services but also will assist in quicker troubleshooting of network issues as they arise and allow for testing of new services before deployment.

Remember, your entire infrastructure has to perform together. You can’t have one switch supporting VLANs while others don’t and you can’t have switches supporting VLANs while your routers don’t. Make the investment in the beginning and enjoy a successful roll-out instead of having to patch things on a routine basis later on.

If you don’t have in-house expertise for some of these technologies, it makes sense to go to a third party. If your planning is right from the beginning, it will be easier to scale your network and provide the quality of service your users expect.

Remember, you’ll have to provide POE (Power over Ethernet) for your VoIP nodes (handsets). You should have power backup on the POE circuit so your phones will stay operational even if there’s a power failure, users will expect this.