Many of the policies require something the match other than the specific term.  Lets take the policies that match social security numbers, such as Graham Leach Bliley.  This requires not only the social security number, but also some identifying information, such as name and address.   The rational behind this is that a social security number without context is usually not very useful, if you think about it a social security number can easily  derived by just putting 9 numbers together with a “-“ between the third and fourth number and the sixth and seventh.

So, what if you want to use the vast array of dictionaries available to the DLP policy manager, but want to match and take action no matter what?

The easiest thing to do is create a custom policy.  With this you can grab any of the dictionaries in the DLP engine, such as various nationalities social security numbers, or states drivers license numbers.  Put a policy together using just those things and have it hit.  But leaving the policy like that is not good enough, you must also adjust the sliders at the bottom of the DLP policy page.  Normally the ignore is set for 0-9, meaning that a single social security number may not actually trigger an action even though it did match.  My suggestion is to move those sliders so that low starts at 1 and set your actions accordingly.

Ironport DLP is a post from: Geeknick

Related posts:

1. Dropping Traffic in IOS Everyone is familiar with access-lists as a way to drop...

Related posts brought to you by Yet Another Related Posts Plugin.

For more videos, check out my youtube channel by clicking the link bellow:

Networking Technologies Explained

Digital Signal Processors (DSPs) Explained is a post from: Geeknick

Related posts:

1. Voice Codecs Explained A high level explanation of Voice Codecs 1 of 2...
2. Multi Protocol Label Switching (MPLS) Explained A high level explanation of MPLS For more videos, check...
3. Quality of Service (QoS) Explained High level explanation of QoS For more videos, check out...

Related posts brought to you by Yet Another Related Posts Plugin.

Ethernet is the dominant transport technology in networking and by design allows for data loss.  When Ethernet was originally created it was based upon a bus technology using coax cable with taps to provide connectivity to individual devices.  Ethernet was designed with CSMA/CD which is Carrier Sense Multiple Access with Collision Detection.  This mechanism allowed Ethernet to recover from collisions due to two or more nodes attempting to communicate at the same time.  This mechanism allows for data to be lost and retransmitted on an Ethernet network.

Data Center Bridging is an effort by the standards bodies including the IEEE to enhance traditional Ethernet for use within the data center to provide a unified technology for all data center communications including network, storage and management.   The minimum enhancements to Ethernet to support Data Center Bridging are Priority Based Flow Control, Enhanced Transmission Selection, and Data Center Bridging Exchange Protocol.

Priority Based Flow Control creates eight separate virtual links on each physical link.  Each virtual link can be paused independently from the others.  This allows the creation of a loss free virtual link across the physical link.  In addition, quality of service can be configured for each virtual link.

Enhanced Transmission Selection allows differentiation between traffic of the same priority class.  This leads to the concept of priority groups.  Traditional QoS mechanisms allow for different traffic classes. ETS creates priority groups within the classes for further control over network traffic.

Data Center Bridging Exchange Protocol is used by devices to discover one another and exchange information about each device’s capabilities.  By creating a protocol for capabilities exchange, devices can better understand the capabilities and limitations of their peers with a Data Center Bridged environment.

Data Center Bridging allows customers the ability to create a converged network within the data center that incorporates networking, management and storage onto a single transmission medium.  It simplifies the cabling within the data center and allows organizations to adapt rapidly to changing business needs.  For more information on Data Center Ethernet see the links below.

http://www.ieee802.org/1/pages/dcbridges.html

http://www.cisco.com/en/US/partner/netsol/ns783/index.html

Data Center Bridging is a post from: Geeknick

Related posts:

1. Save Money with Data Center Virtualization and Vmware Vsphere 4.1 VMware vSphere is the most widely used and robust...
2. Should I use Supernets and Secondary Address in my network ? Many network administrators are using secondary addressing and supernets as...
3. What is Session Initiation Protocol (SIP) Trunking? SIP has been the buzz in the Telecom industry for...

Related posts brought to you by Yet Another Related Posts Plugin.

So many times the security of the network devices, or the access into the network is laid out in such a way that should one of those devices fail, the network is down.  In this case, no one even attacked you and you are in a spot where you must route around the failed security device, and with concern for uptime, you may do it in a manner that is far less secure than if you had never had the device in the first place.  Why?  Usually because you are trying to patch the hole quickly, and inadvertently leave a security hole, which, if you had never owned the device, you would have thought through and secured this method of connection.  These holes commonly show up as missing lines in the ACLs due to IP schema changes, or a routing issue that is now bypassing more of your security than you intended.

The solutions are numerous, but when developing a solution there are always the four “P”s that must work together.

Performance – How well will the solution work should there be a failure and how fast can it be implemented and how much will the reduced  performance cost in terms of business.

Probability – How likely is it that there will be a failure of this device given its own internal redundancy

Price – Do I need to explain this one?

So the obvious answer, is that if price weren’t a factor, buy two of everything have two circuits from two providers, bring in power from two power grids, have two cores switches, each with two fibers to redundant distribution layer, to redundant access layer to servers with redundant NICs and vmware to move all of the servers to another diversley geo-located site should this site get destroyed.

More likely you should look at ways to, within a budget, mitigate the consequences of a failure.  Let’s say you have an Inline web filter that is going up to a pair of Cisco ASAs.  Well, your inline web filter is a single point of failure sitting in front of a redundant solution.  So what do you do if you can’t afford another webfilter and need to know that should it fail you can still maintain business.

First – make sure you keep your warranty up on the web filter and have fast replacement.  This doesn’t cost nearly what a second webfilter would, and reduces your performance risk from an outage time perspective.

Second – Design with this in mind.  See if you can use your webfilter a different way.  Maybe as WCCP where should it go down, you can fail open. If you must stay inline, assume it will fail closed (even if it advertises itself differently).  Then plan disaster recovery around that.  In this case you may have two VLANs involved.  One for the inside of the web filter and one for the outside.  The inside VLAN is a routed VLAN on your layer 3 switch.  You are routing to your ASAs directly.  To do this you connect the inside of your web filter to the inside VLAN, and the outside interface to a non routeable VLAN on the layer 3 switch.  You will then connect your ASAs’ inside interfaces to that same outside VLAN.  This forces the traffic through the webfilter and is a very common setup for this scenario.  Should the webfilter go down, you change the VLAN on the ASAs to the inside vlan, and you have internet access again.  You have lost the web filter obviously, but hopefully your performance impact isn’t that great until the replacement unit can arrive.

By doing this you can also ensure that the inside vlan, is secured in a manner that your company policy is congruent with should a failure occur.

Security – More than just ACLs is a post from: Geeknick

Related posts:

1. Should I use Supernets and Secondary Address in my network ? Many network administrators are using secondary addressing and supernets as...

Related posts brought to you by Yet Another Related Posts Plugin.

VMware vSphere is the most widely used and robust data center virtualization platform in the industry. It gives the highest levels of responsiveness and availability, which are required by the most demanding data centers throughout the world.

VMware vSphere will help you to cut capital and operating costs and provide you additional control over your computing system . You will be able to lighten the load of your IT personnel and can use just about any server hardware, operating system, and applications you like.

What is new in vSphere 4.1:

vCompute

• Memory Compression -Minimizes memory contention and provides application response.

• DRS Host Affinity – Set policies when using Dynamic Resource Scheduling to ideally keep an application residing on a specific server.

vStorage

• Storage I/O Control-Set storage quality of service priorities for each virtual machine to prioritize availability of storage pools.

• Array Integration-use new storage protocols between vSphere and storage boxes for quicker Storage vMotion events and virtual machine set up.

vNetwork

• Network I/O Control-Set network quality of service priorities per flow type for preferential access to network resources.

Scalability

• More virtual machines per cluster: 3,000.

• More physical hosts per vCenter Server instance: 1,000.

• More virtual servers per vCenter Server instance: 10,000 powered on:15,000 registered.

Availability

• VMware vMotion – Improvements to vMotion allow quicker response and availability allowing up to eight vMotion migration events in parallel.

Security

• Active Directory integration-Single sign-on capability for user authentication at the vSphere host for centralized user management. Easily assign privileges to users or groups and roll out permission rules across hosts.

VMware server virtualization solutions can help you to make the most of your IT assets. It can help to reduce the capital expenditure of the data center by as much as 60%! Reductions in real estate, cooling, and power requirements can help you to reduce energy costs by as much as 80%!

If you are not already deploying server virtualization with shared storage, you should know that it can significantly cut costs. A good way to start is to have a server consolidation analysis completed which will give you an estimate of what types of capital and operational cost savings you can get with a server virtualization upgrade.

Find out additional information about the benefits of server virtualization technology as well as full data center virtualization from your local information technology value added reseller, who can also help you with the upgrade.

Author: Rolf Versluis

Adcap Network Systems, Inc.

Save Money with Data Center Virtualization and Vmware Vsphere 4.1 is a post from: Geeknick

Related posts:

1. Virtualization – a new era for computer systems After working with PCs and Servers for many years we...
2. Hardware requirements for Virtual Machines When buying a new server, or any piece of computer...

Related posts brought to you by Yet Another Related Posts Plugin.

If users are unable to access the applications that they need over the network, or if customers are unable to access the Internet-based Web services or applications that they need, all business transactions come to an immediate screeching halt. Since application access is so important, it is worthwhile to look at how to make sure everything in the system works reliably.

There are four core network services that have to be up and running for users to be able to access their applications. These are:

1. DHCP stands for Dynamic Host Configuration Protocol. This service is what hands the user an IP address on the internal network when they connect. No network communication can take place without having an IP address, as well as the other information that the DHCP service provides, which is a default route and the IP addresses of the DNS servers. What most people don’t know, is that usually the DHCP service is provided by a non-redundant Windows server, or by a router that provides little visibility into the operation of the service. DHCP is essential for VoIP systems.
2. DNS stands for Domain Name Service. This service is what translates easy to remember names on the network, like a URL in a browser, to the IP addresses that the applications running on computers require. Without DNS, any network-based applications cannot be used. DNS is usually provided centrally by redundant windows servers, and externally by multiple small linux boxes running BIND. Unfortunately, sometimes the Windows DNS service has stability issues, and it is tedious and error prone to update the BIND applications on the Linux boxes.
3. NTP stands for Network Time Protocol. There are many applications that require proper time on the servers and workstations, especially SIP-based voice applications and network security applications. NTP is in many cases served from redundant windows servers.
4. IPAM stands for IP Address Management. It is important to have an overall IP address management method in order to ensure that DHCP and DNS are working properly. Entire new subnets are added in a VoIP deployment, so this is especially important then.

As you can see, high availability core network services are essential to the proper operation of everything on the network, and especially VoIP. In your next upgrade planning cycle, it is worthwhile to look at improving the availability of the core network services of DHCP, DNS, NTP, and IPAM.

Find out more about Core Network Services here. Rolf Versluis is a Cisco Certified Voice Professional and engineer with Adcap Network Systems, Inc., with offices in Atlanta and Miami.

Reduce VoIP Network Downtime with Improved Core Network Services is a post from: Geeknick

Related posts:

1. Should I use Supernets and Secondary Address in my network ? Many network administrators are using secondary addressing and supernets as...

Related posts brought to you by Yet Another Related Posts Plugin.

With Virtual Machines, the story is a little bit different.

Let’s say you have a very powerful server that is being used as a file server: probably its CPU and most of its memory is underused. Sometimes you have a server that has a lot of applications running at the same time eating all the CPU and memory to the point that its performing poorly.

With virtualization technologies you have much more control on the resources you are going to assign to your servers, the cap being how powerful and fast is your virtualization infrastructure.

One of the things we need to let go is the assumption that our virtual machines need the same amount of resources as if they were physical ones. Do you need 4-CPU Cores on a Server that has no software optimized for multiple CPUs? Are you sure you actually need 8 GB to run those web applications running on IIS?

Enterprise Virtualization environments offer statistics and overviews on how our vm are actually performing. I recently installed a SQL Server environment from physical to virtual and they were really happy on how the new server / vm was performing: it had more cores and double the RAM (8 in this case). They were surprised when I told them: yes, you have multple cpu cores and 8 GB of memory on that server, but I just gave it 1 core and 2 GB of RAM. They asked me why aren’t we giving it more resources so it can run much more faster. I then showed him the performance statistics on the vm and he was kind of suprised, the CPU was barely doing anything and the  memory usage was only about half.

Now the client has more resources to create new virtual machines to the box that before could only hold just one.

And it doesn’t stop there.

For example Vmware ESX is capable of optimizing the memory usage when you are running several virtual machines with the same OS (Windows Server 2008 R2 for instance) by sharing the same memory blocks. How? Different vms running the same OS share a lot of the same instructions in memory because they share the same code, so instead of running and loading the same code into memory several times, it does it just once.

Using this kind of performance monitors you can a better control on how your servers are going to perform, how much they really need and how much free resources you are going to have for future virtual machines.

Author: Daniel Ruiz
Adcap Network Systems – Atlanta and Miami
Great Local Engineers Creating Systems that Work!
Posted at Geeknick

Hardware requirements for Virtual Machines is a post from: Geeknick

Related posts:

1. Virtualization – a new era for computer systems After working with PCs and Servers for many years we...

Related posts brought to you by Yet Another Related Posts Plugin.

Ethernet was developed as a broadcast medium. At its core Ethernet uses Carrier Sense Multiple Access with Collision Detection (CSMA/CD). Ethernet at its inception used collisions as a way to handle congestion and give every user access to the communications medium. As networks grew, the need arose for improved bandwidth to the end user. Prior to the invention of the switch, bridges were used to reduce the collision domains in an Ethernet network. Switches are essentially multiport bridges that eliminate collisions and deliver dedicated bandwidth to the end device. It is important to note a this point that while switches control the unicast traffic to the end device, they forward all broadcasts and multicasts to all ports on that VLAN.

In a large switched environment broadcast storms soon became a major issue causing numerous network outages. At this point, the need to reduce broadcast domains became a major design issue. This introduced the concept of VLAN’s. By deploying VLAN’s in the enterprise, network managers were able to reduce the size of the broadcast domains in their networks. This is why many organizations migrated to RFC1918 address space to allow them to assign a subnet to a building, floor, department or other criteria without running out of public addresses.

So the question becomes do I stick with a single class C subnet that gives me 254 addresses per VLAN or do I use variable length subnet masks and supernetting or secondary addressing to create larger broadcast domains. The answer to this question is a definitive NO! It is important to remember that one of the enemies in a network is broadcasts. Supernetting or using secondary addressing increases the broadcast domain and can be detrimental to end user and network performance.

To better understand this issue, we need to review Ethernet as a transport mechanism again. This is where the OSI model comes into the picture. At the physical layer, the modern transport medium for Ethernet is unshielded twisted pair cabling. The next step, data link layer in this case is Ethernet. The third layer, Network is where IP comes into play.

Every station in an Ethernet broadcast domain receives all broadcast and multicast traffic in that domain and must process that packet to determine if it is destined for that machine. After it receives the broadcast Ethernet packet, it strips off the Ethernet header and passes that packet to the Network layer. At this point the end station determines if that broadcast packet needs further processing. Regardless of whether the packet was destined for that end station, it must still perform processing on the packet.

As you can see, supernetting or using secondary addresses can be detrimental to network performance because of the increased processing at the end workstation. In addition, it gives worms, viruses, malware etc access to a greater number of devices due to the increase in users in a common broadcast domain. The next time someone asks you to supernet or use secondary addresses in your network just say no !

Author: Mike Lundy

Posted at Geeknick

Should I use Supernets and Secondary Address in my network ? is a post from: Geeknick

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Application performance over the Internet is a tricky thing. It depends on a number of different aspects of the TCP/IP stack working correctly. TCP is a protocol that is optimized for reliable transmission of traffic over a medium in which packets are expected to be dropped. It does this through a combination of packet retransmission requests, packet sequence ordering, and TCP windowing. TCP automatically adjusts to the available bandwidth by using dynamic windowing, and it always starts with a small window and ramps up to the point where TCP packets dropped that have to be retransmitted, so there is always a slow start in any Internet connection. Because of the TCP windowing, if any packets are dropped during a TCP/IP session, the window size gets smaller and effective bandwidth for the application drops.

What happens when TCP/IP traffic is transmitted worldwide, especially over the Internet when it goes through a number of different service providers and their peering points, is that packets are dropped as a matter of course. Due to the inherent nature of the protocol and situation, this means bandwidth, performance, and latency are going to be poor for an application requiring interactivity. Large organizations have always done with this issue by building out a worldwide private Wide Area Network.

Our engineers have been working with customers for years upgrading and improving their wide-area networks in order to deliver the best application performance to the remote sites possible. We are very familiar with how this is done when using a leased circuit service such as MPLS, both with QoS at the routers, and Wide Area Application Acceleration. This has been much more difficult to do with applications delivered over the Internet to individual users, and in most cases we haven’t even tried.

What my friend needed, was a way to do application acceleration for individual users over the Internet, without installing any applications on their PCs, or putting any special hardware at their location at all. This is trickier than it sounds, since each of the reasons for TCP bandwidth limitation have to be addressed in order to have the application work properly. After the TCP protocol issues are addressed, then the information needs to be compressed at the head end and expanded at the remote site, which would effectively increase the available bandwidth for the application and then accelerate the application speed.

If he were to build out this, he would need a special acceleration server at his data center, and then another acceleration server at the Internet point of presence closest to each of its customers. The servers would have to be able to send packets to each other in a multiple redundant routes, perform compression using all the available current algorithms, have dynamic DNS to reroute the request to the server closest to the end-user, and the monitored all the time to make sure everything was working properly.

Obviously, this would have been a cost prohibitive exercise for my friend. Fortunately, he found a company that offers this type of acceleration as a service.

In fact, this company has tens of thousands of service deployed in most datacenters worldwide, which can be used for dynamic content delivered over the Internet. Examples of content that can be accelerated include:

• Improve VDI (virtual desktop infrastructure) performance.
• Speed up any end-user applications delivered by HTML or IP.
• Remote office and end-user VPN acceleration.
• Speed up large file transfers.
• WAN supplementation or replacement.

Most organizations typically do a test run with whatever application is causing the most issues and problems at the time. This can be a VDI deployment to remote users that is experiencing unacceptably slow performance, slow remote desktop protocol sessions, slow enterprise application performance, or other similar issues that users or customers are complaining about.

If you are experiencing slow application performance over the Internet, you should definitely look for a company that’s able to provide this service. A local reseller that is competent and experienced in improving network performance would be able to recommend a solution for you.

____________________________________
Author: Rolf Versluis
Adcap Network Systems – Atlanta and Miami
Great Local Engineers Creating Systems that Work!
Posted at Geeknick

Speeding up Slow Internet Application Performance is a post from: Geeknick

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

The first thing that you have to know is what the reasons are for the deployment. It is important to keep the reasons for the upgrade in mind when planning and selecting the new system, so as not to get sidetracked into less important reasons during the process. Here are the most common good reasons ones that we run into:

• The old PBX is failing or breaking down all the time.
• People are complaining about how old the phone system.
• There are potential monthly cost savings by converting to SIP trunking.
• You are hearing about improved productivity from other companies using voice over IP systems.
• There are a lot of new features available that you need.

There are, however, other benefits to upgrading the existing phone system that you may not have thought of and will come out during the process:

• Your old data network gets an upgrade as part of the cost of the new phone system.
• There will be an ability to improve business processes.
• There are many ways customer service and vendor interactions can be improved.
• Faster handset moves, adds, and changes.

This guide assumes that you are looking at getting an on premise voice over IP-based phone system. The other options of getting in on premise traditional PBX system or a hosted voice over IP system are not discussed because they are a minor part of the overall market at this point.

Planning the VoIP Upgrade

So, where do you start? Well, the first step is assessing your current phone system and data network. You have to find out what the current capabilities are that you have, what people like about the system and what they don’t like about the system, and especially how the people that are big users of the PBX on the customer and help desk interaction side make use of the current system and want to improve it.

From a calculation standpoint, what it means you have to figure out a bunch of things for every site:

• How many analog and digital phones you have. Which analog handsets can be replaced by low end IP phones (usually all of them will be).
• How many outside lines you have in the form of voice T-1′s and analog ports
• Number and type of data T1′s at every site. (A T1 can be used for voice, Internet, WAN, or a combination).
• Current wide area network per site bandwidth and utilization.
• Current local area network switches quantity and location; quantity of used ports per closet.
• Any special requirements for ACD, IVR, call recording, handset paging, and application integration.

If you want to get funding support for this you have to get a handle on what your current monthly costs are. Current monthly costs include charges at every site:

• Internet and wide area network circuit costs.
• PBX lease costs.
• PBX monthly service costs. Average cost of additional PBX service on a monthly basis.
• Cellphone costs, since some of these can be offset using single number reach.
• Monthly conferencing costs.
• Monthly maintenance and support on all network hardware and software that may be replaced.

Once you have calculated what your current monthly costs are you’re ready to figure out what the budget for your new project is. The best outcome to the new project would be that your new monthly costs are lower than your current monthly costs, after accounting for new equipment installation services and everything else to put the new phone system in place, when financed over a 3 to 5 year period with a one dollar buyout at the end so you own the new system. You may find out during the course of this planning that it will be necessary to get  new phone and wide area network connections in order to realize the desired return on investment, so make sure you keep your monthly circuit costs and your financing of equipment, maintenance, and installation separate.

Choosing VoIP vendors and resellers

There are two choices to make next. One of the choices is to determine the manufacturer of the new phone system that you want to purchase, the other choice is to pick a local vendor who’s going to do the design installation and support of the new system. To get the best price and the best service on the new system you should go about this in a very specific way. Customers have found in many cases that it’s best to get a phone system from a manufacturer who has good local resellers that will do a good installation of the system, a smooth cutover, enabling all the features that they want, and then support them well in an ongoing fashion afterwards. The size of the reseller that you probably want to work with depends on the size and needs of your organization. I recommend that you work with the reseller who is big enough to handle your business but won’t be overwhelmed by it and is small enough that your business is important to them and they’ll bend over backwards to take care of you.

So how do you find a reseller that’s the right size for you? This is where you go back to the phone system manufacturers to get some options. The major phone system vendors are the best source to find out the local resellers. The major vendors of voice over IP systems at this point in time are Cisco Systems, Avaya, Mitel, Shoretel, and Digium Switchvox. If you contact these vendors either online or through their local salespeople you can ask them for a recommendation of their top three resellers who would do a good job for you. After you get those reseller names from the vendors try to get their recommendation of whom that you should really work with, then call that reseller, as well as the other two. At this point you should have three equipment vendors, three resellers for these vendors, and will have nine good options of a local business that will do a great job for your voice over IP upgrade.

Be aware though as soon as you start this process of contacting vendors you are going to start getting phone calls because people know that you’re interested. Now, that may be a way that you can find out who’s the most eager to get your business, but it also might just give you just indication of who has the most aggressive salespeople. So be very clear to everyone what your expected timeframe is going to be, that you plan to take your time and select the best vendor, and if they bug you excessively that will put them on the bottom of your list. By the way, you should start this process at least six months before you want to have a new phone system up and running. It is going to you 2 to 3 months to select a vendor, another month to figure out pricing and financing, and from when you say go it will take about two months to get the equipment then another month to fully set up and cut over to the new phone system.

Vendor expectations

What you should expect from these vendors is that they are going to want to meet with you to determine what your needs are, do a walk-through of your existing systems, and find out any special requirements that you have. They will then try to sell you on some specific feature that their system has that nobody else has and try to get you to see a demo of their system. I recommend that you see the demo of their system, don’t buy into any of their must have exclusive special features, then ask them for a list of reference customers about your size and requirements that you can call and talk to to see how things went.

Definitely call these reference customers and see how the reseller did during the design phase, how competitive their pricing was, how they did during the installation, and what their support was like after the sale. During this part of the engagement is when you have the most leverage and you can get the most things for free. By all means take the time to get some good lunches and get to know the people that are going to potentially doing work for you for. Furthermore find out who is actually going to be doing the installation for you, if they’re going to be coming from out of state, or if they are local and are going to be available for support after the installation. Don’t be afraid to ask this question as it is perfectly valid and definitely will have a bearing on the outcome of the project and should be a decision factor for you.

At this point you should have proposals from every one of your vendors and you can start comparing them. Some phone system vendors will try to give you just a monthly cost with a summary description of the parts, then say hey that’s the way it’s done. Since most of the voice over IP vendors are coming from the data side of business they expect that you’re going to be wanting a line item pricing and a bottom-line cost. You can then use this to decide what you want finance or not. If you’re not getting this ask for line item pricing and the specific part and model numbers of equipment and a complete breakout of what the annual maintenance costs are going to be.

Annual maintenance is broken down into three areas. Annual product maintenance which provides for support and replacement of hardware and software, upgrade maintenance costs which allows you to upgrade the applications, and a local vendor support contract. All three areas of maintenance are valid. The first two are very important and should be bought in just about all cases, and a local support contract should be purchased if you are not going to have someone qualified to operate the equipment after it’s installed.

Since this is a voice over IP system you should expect that you’re going to be able to run the system over a new data network and not on a separate network that you put in parallel to the existing one. This means that the company that is putting in your voice over IP phone system should have excellent networking capability and be able to demonstrate that they understand Quality of Service, which is tuning the network equipment to differentiate between different types of data, then prioritize the voice traffic. This is easy to do on a local area network, somewhat challenging to do on a wide-area network, and difficult to do over a firewall connection to the Internet. If you are looking at doing SIP trunking make sure the vendor shows where they are going to apply quality of service on all the SIP voice paths.

Making a VoiP phone system decision

So at this point you should have your line item proposals with all the pricing, with all the installation and maintenance included, have seen the demos, and have gotten a chance to meet with the local vendors and contact their reference customers and asked some basic questions. Step back and asked real basic questions at this point. Ask the vendor if there’s anything that you’re missing. Ask the vendor if any parts are over engineered. Ask the vendor if this is the best price, then go one step further and ask the reseller if there’s any way to get better pricing out of the vendor. Sometimes there is an end of fiscal quarter or year coming up and it’s possible to get a few extra points discount or some other concessions thrown in.

During the process you’ve probably eliminated some vendors from consideration, because you’ve been trying to narrow your list of nine vendors down to about three. For those six vendors that you eliminate call and give them a good reason so that they definitely know why they’re out of the running and what they can do about it in the future with other customers. For the other three, let them know that they made the shortlist and give them the timeframe for when you’re going to perform the evaluation and the decision.

Go through whatever decision-making process your organization uses and settle on one vendor. As you go through the final contract negotiation with this vendor, the other two on the shortlist who haven’t made it are going to be calling you nonstop unless you let them know that you have placed the order with somebody else and that they’re out of the running. This is a small industry and there are not a lot of companies that do a good job in this space; I recommend next you let them know that they did not make the cut in a nice professional way and that you appreciate all the hard work that they did on your behalf. At some point in the future you may be calling them for assistance, and you want to make sure that you parted on good terms.

Finally, as you start the installation with your vendor of choice, make sure you work closely with their project management team and get them all the information that you’re looking for as quickly as possible. This is going to make your installation go much smoother, faster, and successful.

Hopefully this guide has been helpful to you in describing the process of how to go through and choose a voice over IP solution vendor, as well as give you some idea of what to expect. Please let me know if you have any questions or comments on any parts of this. If you have specific questions about your situation, please contact one of the fine account managers at Adcap Network Systems.

____________________________________
Author: Rolf Versluis
Adcap Network Systems – Atlanta and Miami
Great Local Engineers Creating Systems that Work!
Posted at Geeknick

VoIP Business Telephone System Upgrade Planning for Mid-Size Organizations is a post from: Geeknick

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.