The Single Most Important Thing to Know About Computer Phones - VoIP5 December 2004
The single most important thing to know about computer phones, aka VoIP, is Security. Security involves privacy of phone calls and vulnerability to viruses, worms, Trojan horses, and unscrupulous computer hackers. Over 90% of voice over ip telephony (VoIP) computer phones use a standard, publicly available codex and protocol to transport voice conversations. Industry standard codex such as G.711, and industry standard packet protocols such as RTP, are open and interpretable. Like many peer-to-peer solutions, private information about “buddy” lists or call patterns, etc., are not confidential. In addition, users are vulnerable to decoding after a packet interception when traveling over the internet.
Here’s how VoIP services should protect your security, even on dial-up, wireless, satellite, and cable connections.
Call Security: The VoIP should be compressed using a proprietary codex that is transported over the internet using proprietary packets. Only that particular VoIP's service software should be able to interpret the headers and data contained in that particular VoIP service's packets.
Computer Phone Identity: When a VoIP computer phone is first installed, a phone number and password should be required to protect against unauthorized installation. Each VoIP computer phone’s setup process should combine the phone name and hardware data from the PC on which it is installed, thus creating a unique ID string known only to that VoIP service's server. This unique ID should be associated with the PC that “owns” the VoIP computer phone, and also prevent one person from reconfiguring their VoIP computer phone to spoof another. In addition, it should also prevent someone from copying that particular VoIP's software to another PC and then using it without having gone through the password-protected installation process.
Client Server Model: A VoIP service provider should follow a client-server model. The VoIP softphone “client” should share information only with that particular VoIP's server. This means, that unlike some peer-to-peer solutions, private information about “buddy” lists or call patterns, etc., are entirely confidential. The VoIP provider's server should be behind a highly secure firewall in a professionally hosted facility.
Softphone Setup: Firewalls vary widely and each network configuration may be quite different. When a VoIP softphone initializes, it should discover its ability to reach that particular VoIP's server and use a variety of ports and protocols for placing calls, depending on the results of its discovery. In a stricter environment, the VoIP softphone should use the same path the firewall already permits for web browsing, typically TCP ports 80 and 443. This allows users to make calls from anywhere without compromising or reconfiguring their firewall.
The VoIP softphone should be able to initiate conversation with that particular VoIP's server and keep the server updated as to its status. No public IP address should be setup for the PC running the computer phone, thus enabling the user the flexibility to move from network to network without concern. The particular VoIP computer phone should be compatible with Network Address Translation (NAT) and Port Address Translation (PAT), and the kind of dynamic addressing that is found in wireless “hotspots”, hotel internet access, and dial-up.
Monitoring Capability: A strong security model should include an auditing mechanism to monitor usage and activity. As such, each VoIP computer phone should include its own usage log, enabling users to look through their history of inbound, outbound, and missed calls. In addition, the VoIP service's website should provides users the ability to view all individual phone call charges.
Source: PR Web
All trademarks and copyrighted information contained herein are the property of their respective owners.
Related Voip Articles
|
