On a more practical level there are many issues around integrating IP telephony systems with legacy systems, especially where there are different and/or multiple vendors involved. Legacy systems -- whether PBX or KTS -- are closed, proprietary and inflexible, making it hard to bring VoIP along. IP telephony is by nature the opposite -- open, standards-based and flexible, and unless the business is making a wholesale changeover, the initial transition will be somewhat disruptive, which for some is not worth the bother.
Another key challenge is trust. VoIP is still evolving, and even the most tech-savvy business will have trust issues around this. At the most basic level is quality. To adopt VoIP there must be trust that the quality and reliability will be on par with TDM, which we all know is nearly flawless. Telephony is mission-critical, and businesses cannot afford best-efforts here, and nor will they accept voice having to compete with data applications on the same network, and becoming a secondary priority from time to time.
Trust extends to many other aspects of communications and networking, including security, scalability and flexibility. There is a great deal to explore here -- should you have any additional questions, send me an email and I will be happy to expound upon anything I have discussed.
Dig Deeper on IP Telephony Systems
Related Q&A from Jon Arnold
Where on-premises UC offers control, cloud-based UC offers agility. Learn why a hybrid UC deployment is a temporary move on the way to a full cloud ... Continue Reading
Adopting the UC tools within a cloud-based office suite may be the most beneficial option if users are already comfortable with the suite's features. Continue Reading
UC offerings that include contact center integration provide more seamless communications and engagement between office workers and contact center ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.