Joining a Meeting Using Entry URL
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
Live Meeting provides user interfaces through which users can attend a meeting or view a recording. The user interface requires each user to fill in a form. The entry URL eliminates the need for users to fill in forms. By default, the Windows-based Meeting Console is used. The entry URL syntax for the default Windows-based console is as follows, where <conference_center> is the name of the conference center, and the <role> and <query-part> choices are specified in the following two tables.
https://www.livemeeting.com/cc/\<conference_center>/<role>?<query-part>
If a meeting or recording has the access control list enabled for a meeting or recording, you cannot use an entry URL to bypass the Logon screen and go directly to a meeting or recording. Instead, the user must log on with the user ID and password at the conference center Logon screen.
Roles in an Entry URL
Role |
Description |
|---|---|
attend |
Attend the meeting as an audience member. |
present |
Attend the meeting as a presenter. |
view |
Access the recording of a meeting. |
join |
Attend the meeting using a Windows-based console. This role value requires the use of the role query field to specify actual meeting role. |
webjoin |
Attend the meeting using a Web-based console. This role value requires the use of the role query field to specify actual meeting role. |
Query Fields in an Entry URL
Field |
Description |
|---|---|
cn |
The display name of the user. This name appears in chats and as the userName attribute of the Visitor or RecordingVisitor4 element. |
id |
The meeting or recording name. |
pw |
The meeting or recording password. The recording password is initialized to the same value as the meeting's audience password. |
If the registration option for the meeting or recording is True, the email field must be present to send the user to the meeting or recording. If this field is absent, the user must fill in a form. Only 64 characters are retained for this field. |
|
company |
Specifies the company name of the user. Its value range is 0-255 characters. If the registration option for the meeting or recording is True, the company field must be present to send the user to the meeting or recording. If this field is absent, the user must fill in a form. Only 64 characters are retained for this field. |
extra1 |
The conference center does not interpret this field. If present, this field appears unchanged in the Visitor or RecordingVisitor4 element. The extra1 field is limited to 128 characters. As an example, this field might be used to record the information needed by a custom application. |
extra2 |
The conference center does not interpret this field. If present, this field appears unchanged in the Visitor or RecordingVisitor4 element. The extra2 field is limited to 128 characters. As an example, this field might be used to record the information needed by a custom application. |
extra3 |
The conference center does not interpret this optional field. If present, this field appears unchanged in the Visitor or RecordingVisitor4 element. It is limited to 255 characters. |
fmt |
You use this optional field only with the View role. You can select the recording format in this field. The value no selects the non-streamed audio (.au) format; lmm selects the Microsoft Windows Media Replay format for all recordings created in Office Live Meeting 2007 client and Live Meeting 2005; wmm selects the Windows Media Replay format for all recordings created in Live Meeting 2003 even if they are migrated to Live Meeting 2005; and dll selects the Windows Media format as a downloadable .wmv file. The value HFF selects High Fidelity Format recordings. |
lc |
The locale requested for this user in the meeting. Only one of the locales supported by the conference center can be specified. The list of locales supported by a conference center can be obtained using the GetConferencingServiceData message. Specifying an unsupported locale results in an error being returned. |
placewareLicenseCookie |
This optional field is used, along with the recording_agreement field, to bypass the Live Meeting Join page in cases where the browser does not support cookies. In this case, the entry URL should specify both placewareLicenseCookie=true and recording_agreement=accepted parameters. |
recording_agreement |
This optional field is used, along with the placewareLicenseCookie field, to bypass the Live Meeting Join page in cases where the browser does not support cookies. When this field is not specified for an entry URL for a meeting, the entry URL takes users to a Web page that contains a notification that meetings might be recorded by presenters. When recording_agreement=accepted is specified along with the cn, id, and pw fields, the notification Web page is not shown and the Office Live Meeting 2007 client is directly launched for the meeting. The recording_agreement field applies to meeting entry only and does not need to be specified for an entry URL for a recording. .gif "Note") Note
If this field is used, it is the developers responsibility to inform users that meetings might be recorded.
.gif "Caution note") Caution
Certain jurisdictions have passed wiretapping laws that require anyone recording a conversation or meeting in any way to notify all the participants that the conversation or meeting might be recorded. By writing to the Entry URL API, you acknowledge that you are bypassing the Microsoft Office Live Meeting Join Meeting page that contains this recording notification and that you take full responsibility for notifying meeting participants that their conversation or meeting might be recorded. If you want, you can use the following recording notification text: "By using the Microsoft Office Live Meeting service, you agree that at any time during this meeting any presenter may initiate the recording function, which will result in your conversation and communications being recorded and logged by Microsoft. If you do not agree to being recorded, please exit Microsoft Office Live Meeting."
|
role |
The query field specifies the role of the meeting participant. The value can be attend or present. Note
This query field is intended to specify a meeting role only in the case where the <role>? field is being used to specify the type of meeting console (webjoin? and join?). In all other cases, this query field is optional.
Note
View is not a valid value because recordings are viewed in their own player and not a Web page.
|
src |
The conference center does not interpret this optional field. It is limited to 255 characters. If present, this field appears unchanged in the Visitor or RecordingVisitor4 element. |
The cn, id, pw, and recording_agreement fields must be present for the user to bypass the entry form.
Example: Tailspin Toys 2007 Kickoff Meeting Using a Windows-based Meeting Console
Bert has an invitation to the Tailspin Toys 2007 Kickoff meeting. A Web site can be set up to send Bert directly into the meeting through the URL.
http://www.livemeeting.com/cc/\<conference_center>/attend?cn=bert&id=kick&pw=351939&recording_agreement=accepted
In this example, <conference_center> is the name of the customer's conference center. This URL takes Bert directly to an audience console; there is no logon form to fill in because the user name, meeting name, audience password, and recording_agreement are all in the query part of the URL.
For a browser that does not support cookies, the **placewareLicenseCookie=**true parameter can be specified for the entry URL.
http://www.livemeetng.com/cc/\<conference_center>/attend?cn=bert&id=kick&pw=351939&recording_agreement=accepted&placewareLicenseCookie=true
A Web site can send Bert to the View Recording Info page for a particular recording (where he can select a format) through the URL.
http://www.livemeeting.com/cc/\<conference_center>/view?cn=bert&id=kick&pw=351939
A Web site can send Bert directly to the Windows Media Replay format recording through the URL.
http://www.livemeeting.com/cc/\<conference_center>/view?cn=bert&id=kick&pw=351939&fmt=lmm
Example: Weekly Staff Meeting Using a Web-based Meeting Console
The user is overriding the default Windows-based Meeting Console in favor of a Web-based console in the following example. There are several differences between the following example and previous examples, which call the Windows-based Meeting Console:
The role? parameter is replaced by a webjoin? parameter.
A query field called role is added with the value of attend.
A new dialog box is displayed. The meeting participant is prompted to run the software "cc-sv.cab". The participant should select Run.
https://www.livemeeting.com/cc/\<conference_center>/webjoin?id=WeeklyStaff&pw=pass1&cn=chris%20ashton&=attend&placewareLicenseCookie=True&recording_agreement=accepted