Fact-checked by Grok 2 weeks ago

CU-SeeMe

CU-SeeMe is a pioneering videoconferencing software that enabled real-time video communication over the using standard personal computers and low-cost cameras, marking the first PC-based application of its kind without requiring expensive dedicated hardware. Development of CU-SeeMe began in July 1992 at , led by student Tim Dorcey as part of an initiative to leverage the emerging Multicast Backbone (MBONE) for multimedia applications. The initial version, released for Macintosh in late 1992, supported grayscale video at resolutions of 160x120 or 320x240 pixels but lacked audio capabilities for the first few years. A Windows version followed in 1994, expanding its accessibility. Key features included one-to-one and one-to-many multiparty conferencing, facilitated by software reflectors for efficient distribution, along with basic . Audio support was added in 1995 by developer Charlie Kline, transforming it into a more complete system, while color video and additional enhancements like slide sharing were introduced in subsequent updates. The software was supported by grants from the (NSF) and collaborations such as NYSERNet and the Global Schoolhouse , which promoted its educational use. CU-SeeMe rapidly gained popularity, becoming the world's most widely used videoconferencing platform in the mid-1990s, with millions of users across over 40 countries. Its success spurred commercialization, including a partnership with White Pine Software in that led to enhanced versions and broader adoption. By democratizing video communication during the early era, CU-SeeMe influenced the development of webcams, digital telephony, and modern platforms, laying foundational groundwork for today's video conferencing technologies.

Development

Origins at

CU-SeeMe's development began in July 1992 at 's Computing and division, spearheaded by Tim Dorcey in collaboration with Dick Cogger, as a low-cost alternative to the expensive hardware-based videoconferencing systems prevalent at the time. These early systems, such as those demonstrated at meetings, relied on specialized, high-end equipment that limited accessibility for most users, prompting the Cornell team to explore software solutions leveraging existing personal computers. The project emerged from a desire to democratize , inspired by prior experimental demonstrations like Paul Milazzo's 1991 IETF showcase of low-bandwidth video transmission. The initial goal was to enable real-time video conferencing over the using commodity , specifically targeting Macintosh computers equipped with affordable digitizers and cameras, to serve educational and communities at Cornell and beyond. In the early , the faced significant constraints, including low-bandwidth dial-up connections like 28.8 kbps modems, the absence of standardized video protocols, and dependence on rudimentary experimental tools for transmission. Dorcey's team aimed to overcome these by developing efficient techniques and connectivity, allowing users to transmit video at resolutions such as 160x120 pixels without requiring dedicated infrastructure. This approach prioritized practicality on low-end , such as the SuperMac VideoSpigot board paired with basic cameras, to make videoconferencing viable for academic collaboration. The first prototype was released in late as a video-only, application that utilized for packet transmission, enabling direct connections between Macintosh users over IP networks. This early version employed simple frame-differencing algorithms for compression, focusing on minimal resource use to function within the era's limitations, and marked CU-SeeMe's debut as one of the first Internet-native videoconferencing tools. Subsequent iterations would incorporate audio support, but the 1992 prototype laid the foundation for adoption in educational settings.

Early Versions and Key Innovations

A beta release of CU-SeeMe occurred in late 1993 as software exclusively for Macintosh computers. This initial version focused on video transmission using an format, delivering 4-bit images at resolutions of 160x120 or 320x240 pixels at frame rates of 5-15 to accommodate low-bandwidth connections typical of the era. The software operated on a basis, enabling basic point-to-point video calls without requiring dedicated hardware beyond affordable cameras and digitizers. Subsequent updates in early 1994 improved the while remaining video-only. Audio capabilities were introduced in early 1994 with version 0.70b1, integrating Charlie Kline's tool for voice transmission over separate streams and enabling rudimentary audio-video . This integration allowed users to combine video from CU-SeeMe with audio, marking a significant step toward fuller conferencing on modest connections. Later in 1994, the introduction of reflector servers addressed limitations by enabling multiparty conferences, with custom Unix-based software relaying streams to support up to 20-30 participants. Cornell supplemented these developments with user support through mailing lists and training sessions organized via NYSERNet, which accelerated adoption in academic environments across multiple countries.

Features and Technology

Video and Audio Capabilities

CU-SeeMe's video capture relied on affordable grayscale cameras, such as the Connectix QuickCam, which provided input at resolutions like 160x120 pixels in 4-bit grayscale (16 shades). The software processed these frames using frame differencing, where only changed pixels within 8x8 blocks were transmitted if they exceeded a threshold, minimizing data sent over low-bandwidth connections. The proprietary compression algorithm employed differential updates relative to previous frames, combined with run-length encoding on pixel differences within each 8x8 block after subtracting the block's average value. This lossless intra-frame method achieved compression rates around 60% on average, enabling low-motion video streams at effective rates as low as 1-2 kbps for resolutions up to (352x288), though typical usage hovered higher depending on scene complexity and settings. Periodic full-frame refreshes prevented error accumulation from . Audio was handled separately through integration with the Visual Audio Tool (VAT) protocol, utilizing the GSM 06.10 at 13 kbps for compression. Early versions lacked automatic lip synchronization between audio and video streams, requiring manual adjustments by users to align playback. Rendering occurred in a straightforward windowed , displaying local and remote video panes side-by-side, with user controls for adjusting , quality, and enabling freeze-frame mode to conserve during static scenes. Key limitations included the absence of color support in initial releases and susceptibility to network , which often resulted in dropped frames and choppy playback over unreliable connections.

Network Architecture and Protocols

CU-SeeMe employed a networking model for direct point-to-point videoconferences, utilizing (UDP) connections on dynamic ports, with 7648 serving as the default UDP port for video and audio data streams. Participants exchanged IP addresses manually or through in-application to establish these connections, enabling one-to-one video transmission without intermediaries. This approach prioritized low-latency communication over the early Internet's unreliable links but was inherently limited to two users per session due to the absence of built-in multiparty relaying. To support multiparty conferences, CU-SeeMe introduced reflector servers in , functioning as custom UDP-based relays that duplicated incoming streams from one participant to multiple recipients, simulating functionality on networks. These reflectors operated without central , allowing open public access and enabling configurations such as one-to-many or several-to-several sessions, with users adhering to informal for bandwidth sharing. Written in C for Unix systems, reflectors reduced connection overhead from O(n²) in pure to O(2n) by centralizing stream multiplexing, though they lacked load balancing and were prone to overload in high-participation scenarios. The protocol stack relied on as the core for both video and audio, emphasizing unreliable, to minimize in interactions. Video streams were transmitted directly over , while audio could integrate with the VAT (Voice Audio Tool) protocol for interoperability, also using packets. Basic error correction was provided through an auxiliary transport mechanism, though the primary streams offered no , (QoS) guarantees, or advanced . Bandwidth management in CU-SeeMe featured adaptive throttling, where transmission rates adjusted dynamically based on round-trip time (RTT) measurements and feedback, ensuring usability on low-speed connections like 28.8 kbps modems. This mechanism varied frame rates to match available , with reflectors further optimizing by unnecessary streams. However, firewall traversal posed challenges, as the reliance on dynamic ports and the era's lack of widespread (NAT) support often required manual or configurations. Scalability was constrained in the mode to strictly two participants, while reflectors could handle up to 64 users in optimized setups, though practical limits hovered around 10-20 before performance degradation from overload or contention. Without native or load distribution, large conferences risked reflector instability, particularly on the heterogeneous early infrastructure.

Commercialization

Partnership with White Pine Software

In late 1994, Cornell University licensed CU-SeeMe to White Pine Software, a Nashua, New Hampshire-based company specializing in Internet collaboration tools, granting it a master licensee agreement for commercial development. This arrangement allowed White Pine to produce enhanced versions while Cornell retained focus on protocol research and continued distributing a free academic edition. The deal provided Cornell with upfront fees and ongoing royalties, enabling professional support and distribution without disrupting the open-access model that had already built a user base. In 1998, full commercial licensing rights were transferred to White Pine Software. White Pine integrated CU-SeeMe into its lineup of products, positioning it alongside tools for web-based conferencing to target growing demand for communication software. The company's early commercial release, Enhanced CU-SeeMe version 1.0 in late 1994, added Windows compatibility alongside the existing Macintosh support, full-color video, audio, window, and communications, along with minor refinements for broader accessibility. Priced at $69 for download or $99 with manual and , it appealed to business users seeking reliable videoconferencing and home enthusiasts exploring multimedia. White Pine adopted a centered on distribution, offering trial versions for download and full upgrades via the or , supplemented by volume site licenses for educational and corporate deployments. This approach facilitated widespread adoption, with the free Cornell version reaching over 500,000 downloads by late , while the commercial edition benefited from the momentum. Initial success was amplified by media exposure, including features in Wired magazine that highlighted its role in pioneering .

Major Releases and Platform Expansions

Following the initial licensing agreement with White Pine Software in 1994, the company began commercializing CU-SeeMe with enhanced versions that introduced key improvements for broader adoption. In 1996, White Pine released Enhanced CU-SeeMe 2.0, which included native support for , enabling better integration with the growing PC market, and was priced at $99 for individual licenses to reflect its commercial positioning. Additionally, it incorporated TCP fallback mechanisms to navigate restrictions common in corporate networks and introduced basic text chat functionality for non-video interactions. By 1997, White Pine launched CU-SeeMe 3.0, initially as a beta in April and final release in May, focusing on user interface enhancements and interoperability. The update featured a revamped interface with a phone book and directory services for locating online users and sharing vCards, along with integration of Microsoft ActiveMovie for resizable video windows that maintained frame rates while adjusting quality. Priced at $69 per client with volume packs available, it emphasized corporate use, though 80% of users at the time were in home or educational settings. Version 3.0 also improved reflector software to support multi-party conferences involving third-party clients, with added authentication features for secure access. Audio capabilities were enhanced using the G.723 codec for better compression and quality over low-bandwidth connections, and the software achieved H.323 compliance to enable interoperability with tools like Microsoft NetMeeting. Platform expansions began in 1997 with a community-driven port known as Q-SeeMe, an alpha version that allowed basic video reception on Linux systems, though it lacked full sending capabilities initially. This effort, developed by independent programmers, extended CU-SeeMe's reach beyond operating systems. By 1999, the software's user base had grown substantially, with client sales reaching $4.1 million, indicating widespread adoption amid rising . Subsequent pro editions introduced collaborative tools like whiteboard sharing for real-time annotations during sessions and file transfer capabilities for exchanging documents within conferences. Broadband support enabled higher resolutions up to 640x480 pixels, improving visual clarity for users with faster connections. Marketing efforts in the late 1990s positioned CU-SeeMe for practical applications, including bundling with webcams to simplify setup for new users. It was integrated into Microsoft's 1996 "Communications Tools for Schools" CD-ROM alongside the Reflector for up to 10 users, promoting its use in educational telecommuting pilots for remote collaboration. In 2000, White Pine Software rebranded to CUseeMe Networks to emphasize its focus on Internet-based video communications, aligning the corporate identity with the product's core brand.

Decline and Discontinuation

Competitive Challenges

CU-SeeMe, initially optimized for low-bandwidth dial-up connections typical of the mid-, faced significant challenges as technologies like DSL emerged in the late . While it could operate on connections as low as 28.8 kbps, the software struggled with video quality degradation and high in multiparty calls over faster but inconsistent emerging networks, limiting its appeal for users seeking smoother experiences. Security vulnerabilities further eroded user confidence during this period, as CU-SeeMe lacked built-in for video and audio streams, making it susceptible to on open reflector servers that facilitated multipoint conferences. The proliferation of firewalls in corporate and home networks around 1998-2000 exacerbated these issues, with the software's reliance on ports hindering connectivity without native support, often requiring manual configuration that deterred non-technical users. The rise of competitors intensified these pressures, particularly Microsoft's NetMeeting released in 1996, which offered free integration with Windows operating systems and improved audio-video synchronization, capturing a larger share of the desktop videoconferencing market without additional costs. Later entrants like Apple's in 2002 and Messenger's video features emphasized user-friendly interfaces and seamless integration, further marginalizing CU-SeeMe's more technical setup. Market dynamics during the dot-com boom favored web-based and ad-supported tools that promised scalability and ease of adoption, contrasting with CU-SeeMe's model under White Pine Software, which struggled to adapt after acquiring commercial rights in 1998. White Pine's pivot toward professional hardware-assisted markets alienated its core hobbyist base, contributing to a decline in adoption as users migrated to more accessible alternatives. User reports from the era highlighted stability issues, including frequent crashes on Windows platforms and poor for conferences beyond small groups of 10 participants, which compounded perceptions of unreliability amid rising expectations for robust performance.

Acquisitions and End of Product Life

In May 2000, White Pine Software Inc. rebranded itself as CUseeMe Networks Inc. to emphasize its core focus on videoconferencing technology, while divesting non-video assets to streamline operations amid shifting market priorities. The company pursued growth through a merger announced in March 2001 with First Virtual Communications Inc., a specialist in rich media streaming; the stock-for-stock transaction, valued at an undisclosed amount but aimed at integrating video expertise with media delivery platforms, closed in June 2001, with the combined entity retaining the First Virtual name and headquarters in . Facing financial pressures in the post-dot-com era, First Virtual Communications filed for Chapter 11 bankruptcy on January 20, 2005. Later that year, on March 15, Radvision Ltd. acquired substantially all of First Virtual's operating assets, , and customer contracts—including CU-SeeMe-related technologies—for approximately $7.2 million, integrating them into Radvision's IP-based video conferencing portfolio without further standalone development of the original client. The last major release of the commercial CU-SeeMe client, version 5.0, occurred in 2003, introducing enhanced video chat features such as improved audio integration and multipoint support. Official support ended shortly after the 2005 acquisition, with downloads removed from vendor sites and no subsequent updates issued as Radvision shifted emphasis to enterprise solutions like its SCOPIA platform. Community-driven efforts continued briefly among users but lacked commercial backing. In June 2012, Avaya Inc. acquired Radvision for $230 million to bolster its offerings, absorbing the CU-SeeMe intellectual property into broader enterprise video systems; however, the original product saw no revival, marking the effective end of its lifecycle. Patent-related activity post-acquisition was limited, with CU-SeeMe primarily cited as in unrelated video technology disputes rather than sparking new litigation over its core innovations. By 2008, associated public servers and reflectors had ceased operation, concluding the era of widespread CU-SeeMe use.

Legacy

Influence on Internet Videoconferencing

CU-SeeMe pioneered software-based videoconferencing by introducing the first widespread application for real-time video transmission over IP networks, enabling direct connections between users without requiring dedicated hardware or centralized servers. Developed at and released in 1992 for Macintosh, followed by Windows in 1994, it allowed individuals to conduct point-to-point video calls using standard personal computers and low-cost cameras, marking a significant departure from expensive, hardware-dependent systems prevalent at the time. This model inspired subsequent technologies, including Skype's early architecture, which adopted similar direct connectivity principles to facilitate scalable video communication. The software's early adoption demonstrated the viability of Internet-based video. Later commercial versions of CU-SeeMe integrated support, allowing seamless connections with other vendors' systems like , thus contributing to the standardization of communications over . Additionally, CU-SeeMe's reflector servers—simple UNIX-based tools that replicated video streams for multipoint conferences—prefigured the multipoint (MCU) designs in enterprise videoconferencing systems, such as those from Polycom, by enabling efficient bandwidth management in group sessions without advanced mixing hardware. By operating on consumer-grade with minimal requirements—a connection, grayscale monitor, and optional —CU-SeeMe achieved an milestone, amassing millions of users across over 40 countries and daily downloads of around 1,000 even into the late . This low-cost approach paved the way for the mass adoption of video tools in the , exemplified by platforms like and , which built on its proof-of-concept for affordable, software-driven communication. Technically, CU-SeeMe's use of for video packet transmission established a norm for prioritizing low-latency delivery over reliability in streaming applications, a practice echoed in contemporary systems. Its frame-differencing compression techniques, which transmitted only changed pixels between frames to reduce , influenced efficient encoding methods in later video codecs. On a cultural level, CU-SeeMe normalized video in everyday online interactions during the , fostering early cyberculture through widespread use and contributing to the proliferation of personal video sharing on the nascent . It shifted perceptions of remote communication from tool to accessible medium, setting the stage for video's integration into daily life long before ubiquity.

Applications in Education and Research

CU-SeeMe found significant adoption in educational settings through initiatives like the Global Schoolhouse project, launched in 1993 under NSF funding to connect K-12 classrooms worldwide for collaborative learning. The software enabled students to engage in real-time video interactions with experts, such as scientists from NASA's Jet Propulsion Laboratory, facilitating lessons on topics like space exploration and environmental research during the mid-1990s. These sessions often utilized reflector servers to support multi-party videoconferences, allowing multiple classrooms to participate simultaneously without high-bandwidth requirements. In research contexts, CU-SeeMe supported NSFNET-based experiments in distance learning, integrating with projects like Global Schoolhouse to broadcast educational content, such as NASA's missions and public addresses, to schools across the network. Additionally, CU-SeeMe was used for the world's first broadcast by WXYC in 1994, simulcasting its signal over the MBone. At , developers extended the software in 1995 with CU-SeeMe , embedding live video and audio into a to enable remote collaborations, including virtual labs where scientists could jointly explore shared digital spaces for informal discussions and data visualization. Early telemedicine applications emerged in the mid-1990s through university pilots, with Medical College creating plug-in extensions to CU-SeeMe for remote consultations, medical teaching, and diagnosis in the mid-1990s. These trials, demonstrated in settings like telepathology at Rome Laboratory in , leveraged the software's low-bandwidth compression (e.g., 4:1 ratios over T1 lines) to support rural access and sharing, such as high-resolution medical images. By the mid-1990s, CU-SeeMe facilitated community events in , including student-led sharing under Global SchoolNet initiatives, where reflectors hosted by universities like enabled campus-wide broadcasts and exchanges. Numerous universities operated public reflectors by 1996, expanding access for the software in educational environments and fostering pre-broadband international partnerships among millions of users, including grade schools.

References

  1. [1]
    The CU-SeeMe Project - Packetizer
    When development of CU-SeeMe began in July 1992, the only real-time videoconferencing software for the Internet required expensive hardware which severely ...How Did It Happen? · Project · For Windows 95/nt
  2. [2]
    The Evolution of Video Conferencing Platforms - AVer
    Sep 8, 2023 · In 1992, a Cornel Student named Tim Dorcey created the first PC-based video conferencing software called CU-SeeMe. It was released at first ...The Birth of the First PC-based... · Business-centric Video...
  3. [3]
    The History and Evolution of Video Conferencing - TechTarget
    Aug 17, 2021 · Also in early 1990s, a Cornell student wrote a program called CU-SeeMe. This became the first desktop video conferencing platform. It was ...Video Conferencing Has A... · The 1800s And Bell Labs · 2000s: Rise Of Smartphones...<|control11|><|separator|>
  4. [4]
    CU-SeeMe Desktop Videoconferencing Software - Packetizer
    Introduction CU-SeeMe is a desktop videoconferencing system designed for use on the Internet or other IP networks. It runs on Macintosh and Windows platforms ...Missing: prototype UDP
  5. [5]
    From Baud to Awed: The History of the Modem | Auvik
    May 24, 2022 · As the 90s progressed, the maximum modem speeds ramped quickly. 1993 saw 19.2k, followed by 28.8k in 1994, and 33.6k in 1996. By the end of the ...
  6. [6]
    A history of video conferencing (VC) technology - Packetizer
    1994 Feb: CU-SeeMe v0.70b1 for Macintosh (with ... Working with Richard Cogger in the summer of 1992, Tim Dorcey wrote the original version of CU-SeeMe.
  7. [7]
    CU SeeMe Early Video Conferencing Tech | Origins of Telecom
    Dec 22, 2018 · CU SeeMe v0.1 arrived in 1992 as a video conferencing application that had no audio for the first two years of its existence.
  8. [8]
    Using CU-See-Me for Internet Videoconferencing
    CU-SeeMe is a popular Internet videoconferencing tool developed by Cornell University. CU-SeeMe is shareware, and is available for both Macintosh and IBM PC ...
  9. [9]
    Video for Everyone - TidBITS
    Jan 16, 1995 · Cornell University's freeware CU-SeeMe videoconferencing application (designed specifically to use TCP/IP protocols as found on the Internet) ...
  10. [10]
    Cornell University's CU-SeeMe Welcome Page
    With CU-SeeMe, you can videoconference with another site located anywhere in the world, or by use of a reflector, multiple parties/locations are able to ...
  11. [11]
    CU-SeeMe VR - CS@Cornell
    CU-SeeMe VR combines elements of both computer graphics and video-conferencing. Both these subjects have a long and rich history. The MBONE suite of video ...Introduction · Vr Client Implementation · Limitations, Issues, And...
  12. [12]
    CU-SeeMe Video - Michael (Mickey) Sattler
    In the Mac version, the size of the transmitted image is set by an item under the "Compression" controls. In particular, you can choose "Standard Resolution ...Missing: 0.50 | Show results with:0.50
  13. [13]
    The GSM 06.10 lossy speech compression library and its applications
    The low-level speech compression algorithm of the GSM suite is called GSM 06.10 RPE-LTP (Regular-Pulse Excitation Long-Term Predictor).
  14. [14]
    Internet TV with CU-SeeMe: Chapter 9 - Other Videoconferencing ...
    It is commonly supplemented with vat (Visual Audio Tool) and wb (whiteboard) for full-featured video/audio conferencing and collaboration. LAN Protocols ...
  15. [15]
    Geek of the Week: Ron Frederick - Open Transcripts
    Malamud: There's another set of video tools on the net, known as CU-SeeMe that are made for Macintoshes. ... lip sync and all of the other things that you want it ...
  16. [16]
    UDP 7648 - Port Protocol Information and Warning! - Audit My PC
    Port Description: CU-SeeMe Server Ports. Server control port for CU-SeeMe. Client contact port is tcp 7649. Data stream is over udp ports 7648-7652, and 24032.
  17. [17]
    CU-SeeMe Reflector - Michael (Mickey) Sattler
    In the recently released version 0.70b1, there is a preferences item where you can set the maximum number of windows that you want displayed at any time.Missing: March 1994
  18. [18]
    Appendix E - CU-SeeMe Configuration File
    This is the CU-SeeMe configuration file for the CU-SeeMe reflector that ... port-num UDP port number to communcicate with nv via multicast NV-MC-PORT ...Missing: default | Show results with:default
  19. [19]
    [PDF] Traversing Firewalls with H.323 - GIAC Certifications
    Concept: CUseeMe approaches the firewalls traversal issue by placing servers on both sides of the firewall. The server on the outside the firewall handles.Missing: CU- SeeMe
  20. [20]
    None
    Nothing is retrieved...<|control11|><|separator|>
  21. [21]
    Professors, Students Profit on Wall Street From Internet Tools
    May 10, 1996 · White Pine Software, in Nashua, N.H., has exclusive rights to “CU-SeeMe,” software developed by Cornell University staff members that allows ...
  22. [22]
    [PDF] Low-Cost Videoconferencing for the Clinical Management of ...
    May 1, 2025 · Cu-SeeMe has four audio CODECs to choose from. These include Voxware (2.4 Kbps), DigiTalk (8.5kbps), Delta-Mod (16 Kbps), and Intel DVI. ( ...
  23. [23]
    WHITE PINE ACQUISITION OF ABOUT SOFTWARE WINS IT ...
    Dec 5, 1995 · White Pine master-licensed CU-SeeMe from Cornell University, from whom it had been distributed as a freeware to 500,000 users. Berke said ...
  24. [24]
    Net Surf - WIRED
    Dec 1, 1995 · Though the hype has faded since CU-SeeMe was first introduced as freeware by Cornell University ("See Me, Hear Me," Wired 2.09, page 145), the ...
  25. [25]
    CU-SeeMe Window The development of CU-SeeMe began in 1992 ...
    CU-SeeMe Window The development of CU-SeeMe began in 1992 in Cornell University's Information Technology Organization. It was originally written for Macintosh, ...Missing: history origins Tim Dan Frohlich
  26. [26]
    Vintage CU-SeeMe 1996 Version 2.0 Desktop Videoconferencing ...
    In stock $8 deliveryVintage CU-SeeMe 1996 Version 2.0 Desktop Videoconferencing Software Floppy Set - Picture 2 of ... White Pine. Category. Computers/Tablets & Networking > Vintage ...
  27. [27]
    [PDF] Reference Manual for the ProSafe VPN Firewall FVS114
    Apr 1, 2005 · In the example shown in Figure 4-4, CU-SEEME connections are allowed only from a specified range of external IP addresses. In this case, we ...
  28. [28]
    CU-SeeMe reaches version 3 - CNET
    Apr 21, 1997 · CU-SeeMe reaches version 3. Responding to Microsoft and Intel, White Pine Software prepares the next releases of its videoconferencing software.Missing: 1996 TCP chat<|control11|><|separator|>
  29. [29]
    [PDF] Signaling Protocols for Internet Telephony
    Some more H.323 software clients. Manufacturer. Voxware. NetSpeak. White Pine Software. Product. VoxPhone Pro. Webphone. CU-SeeMe. Version. 3.0. 4.0 (full). 3.1.
  30. [30]
    RE: Alpha version of CU-SeeMe for Linux
    Subject: RE: Alpha version of CU-SeeMe for Linux; From: "Michael J. Pelletier" <mjpell@earthlink.net>; Date: Tue, 13 May 1997 20:02:30 -0400 (EDT); Cc: Miguel ...Missing: port | Show results with:port
  31. [31]
    posam.txt - SEC.gov
    Our trademarks include ClassPoint, CU-SeeMe, CUseeMe Networks, CU-SeeMe Web and MeetingPoint. ... 0.50 0.50 Interest rate ...
  32. [32]
    CU-SeeMe V3 (PC, CD-ROM) White Pine Software - 1997 USA ...
    Video chat software. CU-SeeMe is award-winning Internet video chat software. Now you too can see, hear and chat with friends and family all over the world ...Missing: integration | Show results with:integration
  33. [33]
    Cornell University's CU-SeeMe Page
    His overview of the project, CU-SeeMe Desktop Videoconferencing Software was published in CONNEXIONS, March 1995. ... CU-SeeMe is intended to provide useful video ...Missing: history | Show results with:history
  34. [34]
    New Microsoft CD-ROM Gives K-12 Schools Free Communications ...
    ... White Pine's award-winning desktop video conferencing software, Enhanced CU-SeeMe, and CU-SeeMe Reflector for 10 users. Collaborate with colleagues via real ...<|separator|>
  35. [35]
    White Pine changes name to CUseeMe - CNET
    May 8, 2000 · (Nasdaq: WPNE) said Monday it changed its name to CUseeMe Networks and will trade under its new symbol (Nasdaq: CUSM) by May 15. Shares in ...Missing: CU- SeeMe agreement
  36. [36]
    Video Conferencing History: Still Frustratingly Imperfect - Tedium
    Mar 24, 2020 · 0310 cuseeme A screenshot of CU-SeeMe, a very early internet-based video conferencing system that dates all the way back to 1992. Examples ...
  37. [37]
    Early Internet Video
    CU-SeeMe is an internet video-conferencing client written by students at Cornell University. It was first developed for the Macintosh in 1992 and later for the ...Missing: history | Show results with:history
  38. [38]
    First Virtual and CUseeMe Merge - Streaming Media
    Mar 23, 2001 · The transaction is expected to be complete in the second quarter of 2001. The combined company will be headquartered in Santa Clara, Calif ...Missing: ePop | Show results with:ePop
  39. [39]
    425 - CUSEEME NETWORKS INC - CUSM / 1006591 - 2001-03-22
    Mar 22, 2001 · The transaction will be effected as a stock for stock merger and is subject to the approval of the stockholders of both companies and to ...Missing: ePop | Show results with:ePop
  40. [40]
    Radvision buys US co First Virtual Communications - Globes English
    Mar 2, 2005 · Radvision will buy substantially all the operating assets, intellectual property and customer contracts of FVC and its wholly-owned subsidiary ...
  41. [41]
    https://www.cs.columbia.edu/~hgs/rtp/cuseeme.html
  42. [42]
    CUseeMe 5.0 Videoconferencing : Amazon.co.uk: Software
    Product Details ; Is discontinued by manufacturer: No ; Package Dimensions: 24.13 x 20.32 x 3.81 cm; 226.8 g ; Release date: 1 Jan. 2003 ; Manufacturer: White Pine ...
  43. [43]
    Cu-SeeMe - Columbia CS
    Jan 9, 2008 · Description: "CUseeMe v5.0 is the next generation CUseeMe software with new features that make it the best solution for videochat available ...Missing: integration VAT GSM
  44. [44]
    It's True: Avaya Buying Radvision, For $230 Million - CRN
    Mar 15, 2012 · Avaya on Thursday confirmed it will acquire videoconferencing specialist Radvision, dramatically expanding Avaya's videoconferencing footprint.
  45. [45]
    Pixion, Inc. v. Citrix Systems, Inc., No. 3:2009cv03496 - Document ...
    ... claims are invalid due to 25 anticipation by an earlier conferencing system, known as “CU-SeeMe.” 26 27 28 LEGAL STANDARD Summary adjudication is proper ...
  46. [46]
    Virtual Field Trips and Global Collaborations in Education , Always ...
    Jun 1, 2015 · CU-SeeMe was introduced to the public on April 26, 1993 as part of an NSF funded education project called the Global Schoolhouse. GLOBAL ...Missing: applications | Show results with:applications
  47. [47]
    1995: Scientist on Tap: Video-Conferencing Over the Internet
    Cu-SeeMe software , was developed at Cornell University, and supports multi-party real-time videoconferencing on inexpensive desktop computers via the Internet.Missing: applications | Show results with:applications
  48. [48]
    [PDF] Building a High-Speed Networking Infrastructure. - DTIC
    Cornell University Medical College has developed extensions to CU-SeeMe which permit it to be used for remote medical teaching, research and diagnosis. (See CU-.<|separator|>