Live Meeting add-in not working - artsocial.info
Getting to grips with presenting using Microsoft Office Live Meeting a presentation with a difference it was conducted via Microsoft Office Live Meeting There are also two types of meeting: scheduled; or meet now. Start an Unscheduled Meeting Now. To start an unscheduled Meet Now meeting. 1. Click Start. 2. Click All Programs, point to Microsoft Office Live Meeting. issues with Office Communicator R2 and Live Meeting when I tried to start a meeting using Live Meeting (via the Meet Now.
There are three main client applications used for on-premise conferencing hosted by Office Communications Server: It provides support for a full range of modalities that enable participants to have an effective collaborative meeting. Those modalities include the following: Data collaboration, such as with PowerPoint presentations, whiteboarding, polling, shared notes, and so on. Microsoft Live Meeting Console is the only client offering that supports application sharing.
Microsoft Live Meeting Console supports real time multiparty audio and video, complete with active speaker detection and display. Audio Conferencing Provider integration. Microsoft Live Meeting Console is the only client offering that supports integration between an Office Communications Server conference and a phone-based audio conference hosted by an outside Audio Conferencing Provider. The console provides user interfaces for users to control the audio conference, such as mute self, mute all, and so on.
Microsoft Live Meeting Console supports peer-to-peer text chat between two conference participants. Microsoft Office Live Meeting Console is also a scheduling client. It provides a Meet Now functionality that allows users to create an instant conference and invite other participants from within the conference. The following is a screen shot of the client: Microsoft Office Communicator Microsoft Office Communicator is the primary client application for instant communications and ad hoc collaboration.
It provides the following capabilities: The add-in allows users to use the familiar Microsoft Office Outlook interface for scheduling an Office Communications Server conference. In addition to the usual conference information that Outlook handles—such as meeting start and end time and recurrence—the add-in allows users to apply meeting settings that are specific to an Office Communications Server conference, such as meeting access type, presenter list, and audio information.
It also generates a preformatted meeting invitation that contains all the necessary information for joining the conference. The meeting invitation is sent to all the invited participants via e-mail.
Users can schedule two types of conferences: All modalities will be provisioned for the conference. Schedule a Conference Call This option schedules a conference that will happen in the Microsoft Office Communicator client. Only computer-based audio modality is provisioned at the start of the conference. Conference participants can add other modalities later. Those databases are hosted in the SQL back-end server. The RTC database stores persistent user data, including the contact list, access control information, and static conferencing information.
Static conference properties are stored in this database from the time the conference is created until the time the conference is deleted from the server. Following is a list of included conference properties: This setting indicates when it is safe for the server to delete the conference automatically.
Conference access type—for example, open authenticated. Conference access key for anonymous users. Supported media types A list of meeting participants and their roles. The RTCDyn database stores transient conference state information, such as the up-to-date participant list and the roles of participants, subscription information, conference lock, and so on.
That information is specific to each instance of a conference and is removed when a conference ends. It is, however, important to persist that information in a database during the conference. Doing this ensures high availability for the conference. If one server component fails or stops responding, another server with the same role can easily take over and continue to serve the same conference using information from the database.
Direct from the Source: Supporting a meeting start time and end time, recurrence schedule, and exceptions to recurrence are all important for a prescheduled conference. However, that information is maintained outside of the conferencing database and Office Communications Server.
How to start a Live Meeting
Instead, conference calendar information is maintained by scheduling clients as appropriate. For example, the Microsoft Conferencing Add-in for Microsoft Outlook client saves the time information as part of a Microsoft Exchange Server calendar item.
The Focus runs in the User Services module of all front-end servers. A separate instance of the Focus exists for each active conference. The Focus is responsible for the following tasks: The same sequence is repeated for all clients who want to add this media. When a new media type is added to the conference, the sequence is repeated with the new conferencing server for that media type. By centralizing security enforcement and roster management, the Focus relieves each of the conferencing servers of this duty.
How to setup “Meet Now” for LiveMeeting | Maverick Limited
Understanding the Focus Factory The Focus Factory is an entity that creates, deletes, and modifies meetings in the conferencing database. The Focus Factory creates a new instance of the meeting in the conference database and returns information, including the conference URI, about the newly created conference to the client. Note The Focus Factory runs in the same process as the Focus. Each type of conferencing server is responsible for managing one or more media types.
Office Communications Server includes four conferencing servers: All messages among the participants are routed through the IM Conferencing Server. Supports both dial-out and dial-in, as well as standard third-party call control features such as mute and eject. A conferencing server consists of two logical pieces: The MC on a conferencing server is responsible for managing the control commands between the Focus and a conferencing server.
Live Meeting 2007 Client Download
In the Office Communications Server architecture, all conference control commands are sent by clients to the Focus, which then relays these commands to the appropriate conferencing server or servers after verifying that the client that sent the request has the privileges to perform that operation.
Media is exchanged directly between clients and the conferencing server or servers. The media processor is responsible for media management, such as mixing, relaying, and transcoding direct digital-to-digital translation from one signal encoding format to another. In a Web Conferencing Server, the media processor is a software component that is responsible for managing data collaboration.
In a conference, when a media type needs to be added, the Focus requests a conferencing server for that media type through the Conferencing Server Factory. The Conferencing Server Factory is a lightweight logical component responsible for provisioning a conference for a particular media type on a conferencing server.
The MCU Factory takes into account the current load on the conferencing servers before assigning a conferencing server to a conference. There is one MCU Factory instance on each front-end server that handles all media types. Office Communications Server Conferencing Scale Early in the planning phase of Office Communications Serverwe knew a critical decision point would be the size of meetings we supported on the server.
After reviewing competitive products, speaking with customers, and mining the experience from our own Live Meeting service, it became clear that the vast majority of meetings were actually small 4 to 6 participants. Digging deeper, we discovered that 80 percent of meetings had less than 20 participants and We then polled customers to see if a figure of around to participants would meet their needs.
We found out that it would—with the caveat that there were occasionally larger meetings, such as all-hands meetings, that would exceed this limit. We considered supporting much larger meetings but made the decision to instead focus on the typical information worker meeting 4 to 6 users and allow room for growth up to to participants.
Meetings larger than that would need to take advantage of the Live Meeting hosted service, which can scale beyond participants in a meeting. Apart from the raw server scaling characteristics of such meetings, it was clear from our own operational experience that it takes dedicated staff and processes to make such large meetings effective.
In essence, it is a different solution altogether if done properly. How We Have Tested That Goal Our user model for performance testing of conferencing takes into account a number of factors: How many users are on the pool The effective concurrency rate for meetings The media types mixes that are available for each meeting Where users come from: That gives us the number of users we expect to be in a meeting at any given time in this example, users.
We can then divide this by the number of conferencing servers in the deployment for example, 2and that gives us a figure for the number of participants per conferencing server in this case, We test a variety of meeting sizes to ensure the server scales appropriately.
This calculation represents an average load that we test. One specific test we do is to ensure that we can indeed support a meeting with up to participants.
This includes audio, video, and data. In that test, we run one such large meeting on a given conference server a multipoint control unit, or MCU. We do not attempt to run multiple such meetings on a single conference server. No Magic Numbers When you see numbers like the largest meeting sizethe number of users on a single conferencing serverand so on, it can be easy to think that these are hard-coded values. But there really are no such magic numbers in our software.
Rather, these numbers represent the capacity we have tested for given a particular user model and a particular set of hardware.
Let me repeat that: We do have a notion of the maximum number of participants in a meeting that is controlled by the administrator through meeting policy. More details can be found in the deployment documentation which can be found at http: If you take a look at these policies in MMC, you will note that the default is actually much lower than This is not by accident. It is assumed that users who are allowed to create such large meetings are privileged users and therefore have a nondefault policy.
Meeting policies apply to the organizer of the meeting. Initiating an ad hoc conference call Among UniCom users If all the people you want to include in your conversation are UniCom users, you can: Select multiple names from your Contact list. Ctrl-click individual names, or Shift-click at the end of a range you want to select. Then right-click one of the highlighted contacts, and select Start a Conference Call.
Invite additional people into an ongoing conversation. In the Conversation window, click Invite. You'll see a new window with your contacts; select one or more, or type a name in the search bar.
When you click OK, Office Communicator will send either a phone call or an IM invitation to the contact sdepending on the type of conversation you were in when you invited them. In UniCom, what is a federated contact, and what organizations is IU federated with? Federated contacts cannot initiate a conference call on the IU UniCom system, but you can make a federated contact the leader of a call once that person has joined the call.
Including anyone You can include non-UniCom users, including people outside IU, in your conference by sending email invitations to any email address.
You can include one non-UniCom user who does not have a phone number local to IUB or IUPUI by placing a long distance call to his or her number first and entering the long distance code as usual. Once you've established the long distance call, invite other participants as described below. To include more than one non-UniCom long distance user, you'll have to schedule a conference call.
All UniCom users can invite anyone to join an instant messaging conference. If the leader of the conference is using UniCom Basic, those who join via a web browser may see the option to join the conference call, as described below, but the call to the phone numbers they enter will not complete. If you're in an existing conversation, skip to step 2. If not, in the top left corner of the main Office Communicator window, click the downward arrow next to the blue square, and select Meet Now.
A Conversation window will appear, with you as the only participant. Click the phone icon in the upper left of the Conversation window to switch from instant messaging to a conference call. Click the arrow next to the Invite button. To send an invitation to any email address, select Invite by E-mail You can invite UniCom users directly by selecting Invite a Contact If you use Outlook, an email message window will appear; enter the email addresses of the people you want to invite, and send the message.
If you use another email system, you'll see text that you can copy and paste into an email message, containing the links that allow the participants to join the conference. The Outlook conferencing plug-in, which you installed if you downloaded Office Communicator from IUwarehas a Meet Now button which generates a Live Meeting invitation, unlike using Meet Now in Office Communicator, as described above.
Joining a conference call Dialing in You can dial into a scheduled conference call from any phone number. All long distance charges are the responsibility of the calling party.