Cisco Unified MeetingPlace

This document contains frequently asked questions pertaining to Cisco MeetingTime.

A. The Uncaptured Conferencing Use Capacity Management report tracks each port multiplied by the number of minutes that were attempted to be scheduled, but failed due to insufficient ports. For example, if a five-port, 60-minute meeting failed to be scheduled due to insufficient ports, this report would record that as: 5 ports x 60 minutes = 300 minutes. It only records those scheduling failures that were attempted and refused due to insufficient ports.

A. These are examples of what is represented by the numbers in the Device column:

• For Cisco MeetingPlace Server version 4.3 and earlier:

  PartId 	ConfNum 	gmStartDate 	gmStartTime 	gmEndDate 	gmEndTime 	Device
  0	24519		6/12/02		6:18:18		6/12/02		6:18:59		130
  0	24519		6/12/02		6:18:53		6/12/02		6:18:59		128

  This participant joined the unique meeting 24519 at 16:18:18 via the WebShare application (Web version 4.2.5 and earlier) as indicated by the device ID of 130 and through Cisco MeetingTime and the conference room at 6:18:53 as indicated by the device ID of 128.
• For Cisco MeetingPlace Server version 5.0 and later:

  PartId 	ConfNum 	gmStartDate 	gmStartTime 	gmEndDate 	gmEndTime 	Device    
  0      	14795    	06/12/02       	15:47:18        06/12/02	15:48:06	4082
  0 	14795 		06/12/02 	15:47:11 	06/12/02 	15:48:00 	4081
  0 	14795 		06/12/02 	15:47:23 	06/12/02 	15:47:59 	31

A. All billing reports round up to the next highest minute ( for instance, if a meeting lasts 61 seconds, the billing reports record that as two minutes). The Capacity Management graphs are intended for seeing trends in data, not exact numbers. The Raw Meeting Details report gives you the exact number of minutes in the column "ActLenOfConf".

A. The current design of the display window has a limitation of 32768 pixels. To view the entire list, go to File > Print Preview. From the Print Preview menu, you can zoom in or out and view multiple pages by clicking the Next Page button.

A. If your "Days until meeting stats purged" setting is 30 days or below, you receive no data. The suggested setting is 90 days if you wish to see monthly trending data. To check your setting, launch Cisco MeetingTime, and go to Configure Tab > Scheduling Parameters. It is in the first section of Scheduling Parameters, labeled "Scheduling Params".

A. Counting begins when the call is placed.

A. The Capacity Management Scheduling Failures report graph represents the percentage of all scheduling attempts that failed due to insufficient ports.

A. The Capacity Management Scheduling Failure graph adds a scheduling failure for each failure, regardless of whether or not it is a reschedule attempt of the same meeting.

The answer for the example is two failures are logged. The attempt for ten ports and the attempt for nine ports are reported as failures.

A. The value for nPartsRequested is the number of people invited to a meeting, while nPartRegistered is the number of people registered in the meeting by being invited, by showing up, or both. If the meeting is rescheduled, both of these values change to reflect the rescheduled data.

A. The OrigNumberOfPorts field reflects the number of ports when the meeting was last rescheduled.

A. The billing reports round up each individual port time, then takes the sum of all the ports. The answer in this example is two minutes.

A. The report must be run on the scheduled start date of the meeting. For example, if a meeting was in session from November 10 at 11:30 p.m. to November 11 at 12:30 a.m., you need to run the reports for November 10 to get the data for that meeting. The meeting must be over when you run the reports.

A. This field represents the number of ports required for a meeting. It is a dynamic number. This means that if a meeting is extended, it represents the number of ports in session at the time the meeting is extended, rather than the original number of scheduled ports. To find the original number of scheduled ports, refer to the OrigNumberOfPorts field.

A. The data conferencing (DC) minutes start being tracked the moment a user clicks on the Join Data Conference button, regardless if anything is being shared.

A. The data conferencing (DC) minutes stop being tracked as soon as a user exits from the data conference, regardless of the meeting end time.

1. The Scheduling Statistics data is derived from a separate data store than the Raw Meeting Details data. It is a global set of counters that are updated constantly and written to disk every few minutes. Because of how data is aggregated and written to disk, you can get slight differences in amounts if operations happened around midnight.
2. The Scheduling Statistics report counts rescheduling activity and recurring meetings differently than the Raw Meeting Details. For example, you do not get matching data if you took the Raw Meeting Details, sorted by scheduling client, or OrigSchedDate and compared that to the Scheduling Statistics report. For example, if a meeting is scheduled, and then rescheduled, it counts twice in Scheduling Statistics, but only once in Raw Meeting Details. If it is then cancelled before the meeting is held, it does not count in the Raw Meeting Details report, but it is still counted in Scheduling Statistics.
3. Scheduling Statistics are sorted by the time that the schedule operation was performed. Raw Meeting Details records are sorted by the time that the meeting is to be held.

A. If you want meeting-by-meeting accuracy for statistics such as what meetings are scheduled, held, or attended, view the Raw Meeting Details. If you want general trends such as which clients are used more frequently or how many login attempts are being made, view the Scheduling Statistics.

A. The time frame can be changed by completing these steps:

1. Run the Port Utilization report of your choice.
2. Click the View Menu.
3. Select Display Options.
4. Change the time frame to the desired setting.

A. The fBlast column reports whether the outdial was a blast outdial or a non-blast outdial. Both are explained here:

Blast outdial scenarios (the fBlast column in the Raw Outdial report is set to Yes):

• Have the system call or page you as an invitee to join the meeting.
• Outdial missing invitees during the meeting (number 33 from the Voice User Interface (VUI), or use the outdial dialog in Cisco MeetingTime).
• Team outdial (number 32 from VUI, or use the outdial dialog in Cisco MeetingTime).

Non-blast outdial scenarios (the fBlast column in the Raw Outdial report are set to No):

• Adhoc outdial (number 31 from VUI, or screened outdial to guest from the outdial dialog in Cisco MeetingTime).
• Attendant 0-out outdial.

A. No, the View Disk Usage Statistics report only reflects disk space that is currently used by the system.

A. An Excel Raw Data report is opened by following these steps:

1. Run the report and select Save to File.
2. Save the file to a location you will remember. For example, your desktop.
3. In the Save As box, decide on a file name and enter it in the File Name field.
4. At the end of the file name enter .csv to convert this file to a comma separate values file.
5. Click the Save button.
6. Open Excel.
7. Open the report from Excel. (File > Open. Select the report file and click Open). Make sure to have All Files selected under file type or the file does not show up.
8. In the Open dialog box, highlight the .csv file and click Open.

A. You have to end the meeting before the reports show accurate data. You can always restart the continuous meeting. This is true for all meeting types.

A. The Raw Meeting Details report pulls data directly from each conference server and gives the number of seconds the meeting lasted. The Billing Details report gives the number of minutes the meeting lasted, but this number is rounded up to the next minute. For example, a 63-second meeting would be reported as two minutes. You cannot divide the number of seconds from the Raw Meeting Detail report by 60 and expect that to equal the number of minutes in the Billing Detail report. The system is designed this way in order to provide customers with different options for billing.

A. If the system is configured with overbook ports and they are being used, the dotted line in the Port Utilization report shows more than one-hundred percent.

A. For all meetings that are scheduled and never attended, the start date is changed to 12/31/69 once the meeting appears in the Review Tab.

A. Yes, for attendants and below. However, system managers and technicians must use the current Cisco MeetingTime version. For example, if you are running Cisco MeetingPlace Server version 4.3.x, attendants and below can use any Cisco MeetingTime client they prefer. System managers and technicians must use a Cisco MeetingTime 4.3.x client.

A. The "Monthly by day of week" option is an added feature in Cisco MeetingTime version 4.1.x, but the default setting when installed is not to display this option. To enable the option, go to Configure Tab > Scheduling Parameters > Enable Resched Recurring Mtgs? Change the setting to Yes and click Save Changes.

A. Cisco MeetingTime versions 4.0 and later are compatible with Windows 2000. If you are running Cisco MeetingTime earlier than version 4.0, it is recommended that you upgrade.

• Check the user Profile > Restrictions > Max mtg length.
• Make sure that the maximum meeting length is set to 1440 (24 hours).
• Check Scheduling Parameters > Max meeting length (min).
• Make sure that the maximum meeting length (in minutes) is set to 1440.
• Schedule your meeting.

A. Yes. Here are the steps:

1. Make sure the import file contains at least the uid and prfnum fields. These fields are used to find the existing user record.
2. Edit the import file and add two new columns using field names newuid and newprfnum.
3. Specify the new (changed) user IDs and profiles in these new columns.
4. For users you do not wish to change, copy the values from the original uid and prfnum fields.
5. When you perform the import, set the "Overwrite duplicate info?" field to Yes.

Here is an example import file:

"uid"		"prfnum"	"newuid"		"newprfnum"
"btoombs5"	"23265"		"btoombs5_newID"	"23265999"
"btoombs6	"23266"		"btoombs6_Mgr"	        "23266"

Importing this file changes the user ID of btoombs5 to btoombs5_newID and their profile number to 23265999. It also changes the btoombs6 user ID to btoombs6_Mgr, but does not change that user's profile number.

Note: These steps also are documented in the Cisco MeetingPlace 4.3 System Manager's Guide.

A. The Disconnect Empty Port Timer (DEPT) starts ticking as soon as the meeting begins. This example describes the process:

1. A meeting is scheduled from 9 a.m. to 10 a.m., DEPT = 30 minutes, Meeting Start Guard Time = 10 minutes.
2. The meeting begins at 8:50 a.m. per the Meeting Start Guard Time setting. Therefore, the DEPT starts ticking at 8:50 a.m.. If there are no participants in the meeting at 9:20 a.m., the meeting ends.

Note: These specifics affect the process:

• If you do not want the Meeting Start Guard Time to affect the DEPT, set the Meeting Start Guard Time.
• No matter what these settings are, every meeting is guaranteed to last for the first ten minutes.

A. No, the meeting does not end. There only needs to be one meeting participant in the meeting to make the Disconnect Empty Port Timer (DEPT) obsolete.

A. No, the meeting is not extended. You get the two-minute warning and the meeting ends. After the two-minute warning has expired, you hear "The meeting has now ended" and the system disconnects you.

A. The number of participants who can join a meeting is controlled by the "Max ports per meeting" parameter under scheduling parameters in Cisco MeetingTime. This parameter also controls the maximum number of ports that can be scheduled out per meeting.

A. Meetings that have expired their "Days until mtg stats purged" date but have not passed their "MeetingNotes purge date" still appear in the review tab of Cisco MeetingTime and users are still able to access their meeting recordings over the phone. However, since the "Days until mtg stats purged" date has expired, the meeting information is not reflected in most reports.

A. Schedulable ports = Conference ports + Overbook ports - Floater ports - Contingency ports

A. This depends on how you configured your Cisco MeetingPlace Server. If you have the parameter Extend Meeting set to zero, then the meeting does not extend. However, if it is not set to zero, then the meeting is extended only if you have ports available. If there are no ports available, then the system does not extend the meeting.

A. This is most likely due to your Meeting Guard Time parameter. If your meeting guard time is not set to zero, then your meeting is actually scheduled for the interval that you indicated plus the guard time. In this case, the End Meeting Guard Time was set for ten minutes. Therefore, the meeting is actually scheduled for 3 p.m. to 3:40 p.m. (assuming that the Start Meeting Guard Time is set to zero). As a result, you hear the end-meeting prompt at 3:30 p.m. instead of 3:20 p.m. The Meeting Guard Time parameter is a system-wide parameter, which means only the system manager can set it.

A. If the Record Meeting option is checked, this reserves recording space on the Cisco MeetingPlace Server.

A. Performing this action unlocks all profiles. This is as designed.

A. It is by design since Cisco MeetingPlace Software Release 3.4 that the system always allows an additional system manager login after all the workstation licenses are used.

A. No.

A. No.

A. They are listed according to the meeting start time.