Which manufacturer is best?
I often get asked “which manufacturer is best for IP Telephony and Unified Communications?”. I see this questions almost like being asked “which car is best?” … really it depends on what your requirements are, now and in the future, and on your budget. I’d be happy with a good value sports car now (because I cant afford a luxury sports car!) but that is not going to work when I get a family (my requirements will change in the future)… my retired self-made millionaire friend (if I had a friend like that!) will give you a different answer.
When considering an immediate requirement for a new corporate telephony solution it is important to also consider the Unified Communications requirements that may be needed, even if not needed immediately. A bit like my sport car annology you don’t want to out grow your purchase.
If your requirements are clear the next challenge will be determining which manufacturer and ultimately supply partner is best suited to meet them.
Manufacturer platforms change so rapidly that assessing the relative merits can be difficult. Companies such as Gartner release research on their view of the Corporate Telephony and Unified Communications landscapes. I propose that the relative positions of the manufacturers on the above charts are not too important, but understanding the differences between their solutions is key to determining which is right for your own requirements (and it may result in a combination of manufacturers - note that IBM and Microsoft do not appear in both charts for example).
If you have a good understanding of your requirements (now and in the future) and a good understanding of the available solutions then you will provide your own answer, or answers, to the question “which manufacturer is best?”.
-Richard Tucker
Entry Filed under: ip telephony, unified communications
Leave a Comment
Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
Trackback this post | Subscribe to the comments via RSS Feed