News / Voice
VoIP developments in a July 2006 roundup
This July 2006 roundup grouped several small announcements from a market still testing where internet voice would fit: inside global companies, on websites, in public access venues and on city wireless networks.
Enterprise and developer tools
Rolls-Royce was reported to have selected Nortel for managed global voice services. PeerMe introduced a developer interface for adding click-to-call elements to websites, while TerraSip described a system intended to let internet cafés offer VoIP from shared workstations.
Public-network experiments
Taipei was preparing a wireless voice service on its WiFly WLAN network, and Skype promoted free weekend calling in the United States and Canada. These were separate announcements rather than evidence that any one approach had become the market standard.
One label, several operating models
The roundup is more useful when its announcements are separated rather than treated as one VoIP story. A managed multinational voice deployment, a web-site calling control, an internet-café service, a city wireless experiment, and a short promotional calling offer each depend on different owners, devices, and revenue logic. Their shared protocol language did not make their risks interchangeable. A business buying managed service had to consider administration and continuity, while a public access venue had to make a shared workstation simple enough for a visitor.
The missing link was the journey between contexts
Several items promised that calling could move outside the conventional desk phone, but the hard question was continuity. A person might encounter a browser button, a café terminal, home Wi-Fi, and an employer system in one day. A service only becomes coherent when identity, contacts, dialing behaviour, and support remain intelligible across those settings. It explains why feature lists alone could not establish a lasting communications experience.
Announcements should be read at their stated scale
The enterprise contract, local wireless plan, and weekend offer were evidence of experiments and commercial intent in July 2006, not interchangeable measures of adoption. A useful evaluation would ask who could actually use each service, what access conditions applied, and which part of the calling path the sponsor controlled. That approach avoids turning a collection of small launches into a market verdict. It also preserves what is distinctive here: early IP voice was being tried simultaneously in corporate, developer, public-access, and consumer settings.
How the pieces fit
The items in the roundup describe distinct routes into internet voice. Nortel’s managed service concerned a large company’s communications estate; PeerMe put a calling action into a website; TerraSip focused on shared workstations in internet cafés; Taipei tested voice over a city WLAN. Each route changes who owns the network, identity, device, and support problem. Reading them together shows why “VoIP” was not one market segment. It was a common transport idea applied to enterprise operations, web interaction, public access, and municipal connectivity.