Call YOA using NetMeeting at 18.104.22.168(Rocks IP address)
Adding A NetMeeting "Callto" Statement
Using Microsoft Internet Explorer, people can call you using the link on your Web page even if they do not have NetMeeting running. Use one of the following HTML formats to create a link on your Web page:
For example, if Carl Smith wanted to embed a link in his Web page so that other people could call him, he would add the following HTML tag:
Call me using NetMeeting at <A HREF="callto:email@example.com"> firstname.lastname@example.org </A>
To find the IP address, run winipcfg on the host computer. From the taskbar, click Start, click Run, and then type winipcfg.
The T.120 architecture supports several topologies that define how users connect to a conference and transmit data during the conference. The following diagram illustrates three common topologies: star, daisy-chain, and cascaded. These topologies represent the types of connections typical of NetMeeting conferences.
One of the participants in the conference is assigned as the top provider (conference host). The top providers application is responsible for handling the global resources in the conference and also for sequencing data, if necessary. The top provider is determined within the initial connection between the first two participants. The location of the top provider and how the other participants are connected to the top provider differentiates the various topologies.
With NetMeeting, the person initiating the call is the top provider. The previous diagram illustrates the relationship of this top provider to other NetMeeting nodes in the various conference topologies; many other combinations of top provider and conference nodes are possible. NetMeeting actually initiates the call and determines whether a conference is already running. If no conference is running, NetMeeting creates one locally with the person initiating the call as the top provider. If a conference is running, NetMeeting notifies the person, who then has the option of joining the remote conference. Also, NetMeeting provides a Host Meeting feature (Call menu), which determines the top provider automatically based on the selected conference host rather than on the caller order.
Data flows according to the conference topology, which is determined by how each connection in the conference is established ("who calls who"). For example, in the diagram, the following order of calls establishes the conference topology:
nA (top provider) initiates calls to B and C.
nThen, B calls D and E (or D and E each call B).
nC calls F and G (or F and G each call C).
There is only one
top provider in a conference. After the top provider (A) is established, that computer
remains the top provider throughout the conference. Note that two conferences cannot be
joined together. Therefore, if C called F and G first, it would not be possible for them
to join the conference with A, B, D,
During data conferencing, if B shared an application with the other conference participants, data would flow simultaneously to the adjoining connections (A, D, and E). Then, data would continue to flow outward to the remaining connections. Also, any two connections within the conference can initiate audio and video conferencing. NetMeeting enables audio and video switching, so that participants can switch the pair sharing audio and video.
If B hangs up or is removed from the conference, D and E are also removed. D and E may remain conferenced together, though, if they were connected with audio and video in the original session. D and E would not have data conferencing, however, because this function is removed when B hangs up.
Copyright © 1998 Microsoft Corporation. All rights reserved.
ActiveX, DirectDraw, Microsoft, MS-DOS, PowerPoint, Windows, and Windows NT are registered trademarks and DirectX, FrontPage, NetMeeting, and Outlook are trademarks of Microsoft Corporation in the USA and other countries. All other product and company names referenced herein may be the trademarks of their respective owners.
This document is provided for informational purposes only and represents the current view of Microsoft Corp. on the issues discussed as of the date of publication. Because Microsoft must respond to changes in market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
INFORMATION PROVIDED IN THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND FREEDOM FROM INFRINGEMENT. The user assumes the entire risk as to the accuracy and the use of this document. This document may be copied and distributed subject to the following conditions: 1) All text must be copied without modification and all pages must be included; 2) All copies must contain Microsoft's copyright notice and any other notices provided therein; and 3) This document may be used for informational and non-commercial or personal use only and not be distributed for profit.