A named room, not a generic video call
Cisco's own securities filings are the clearest dated record of how the company described this product in its first year. In a quarterly earnings statement filed with the Securities and Exchange Commission on 8 November 2006, the company called Cisco TelePresence a new, emerging technology solution that creates in-person experiences between people, places and events whether they are across town or across the world. The same filing records that AT&T had completed initial network-interoperability testing and that Verizon Business was expected to begin its own tests, placing the product's public debut in the autumn of 2006 without naming a specific day. Because no earlier SEC filing mentions the product, 2006 is treated here as a record year rather than a single dated launch.
Why the room, not the screen, was the sale
By a further earnings statement filed on 8 May 2007, Cisco reported that it had extended TelePresence to support meetings across multiple locations at once and to let companies meet outside the corporate firewall. The same filing records that the office-space provider Regus had agreed to install the system at fifty locations worldwide, describing it as the first public TelePresence booking service. That detail is instructive: Regus was not selling a video codec, it was selling a room. Systems in this category are conventionally engineered so that the camera, screen and table at each site are matched in position and scale, so a viewer's gaze toward the screen also appears, to the remote colleague, to land on the right pair of eyes. That describes the category's usual method, not a Cisco specification; the filings describe business terms, not camera geometry, screen count or room dimensions.
What the record does not establish
Nothing in the two filings consulted here states how many cameras a room used, how closely the paired sites' furniture needed to match, or what network guarantee a booked Regus room carried. A securities filing exists to disclose material business developments to investors, not to document engineering tolerances, so its silence on those points is not evidence that they did not matter, only that this record does not cover them. A retrospective account wanting the room's actual specification would need a manufacturer data sheet or an engineering account, neither of which forms part of this entry's sources.
Questions to bring to a demo
- Were both rooms built to matching camera height, screen size and table shape, and who verified that.
- What network guarantee, if any, backs the connection, and what happens to the eye-line effect if it is not met.
- Is the room rented as a bundled product, as Regus's arrangement was, or is it a codec added to an existing space.
The lasting point is not that Cisco overstated its 2006 product. It is that the surviving dated record of it comes from investor disclosures rather than product documentation, fixing what a retrospective account can respectably claim: a name, a rough date, a customer list, and a boundary around the room-based method that a full specification would still need to fill in.
Sources & provenance
Preserved from the existing project research collection. These records were not independently re-researched as part of the design update. Supplier, historical and technical claims remain subject to editorial review; no hands-on test is implied.
Source publication: 2006-11-08 · Retrieved 2026-09-16
Cisco's earliest dated description of TelePresence as a new, emerging technology, with AT&T and Verizon Business named as network testers.
Source publication: 2007-05-08 · Retrieved 2026-09-16
Records the multi-location, cross-firewall extension of TelePresence and the Regus public-booking deployment across fifty locations.
Record: 0009-bf-042 · Rewrite revision: 2026-09-16.1 · Actual site publication: pending. No exact event date asserted.