MeetingPlace Moderator at 21:23, 30 June 2010

2010-06-30T21:23:48Z

New page

'''Up one level:''' [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace|Administration Center Page References for Cisco Unified MeetingPlace]]

In the Cisco Unified MeetingPlace Administration Center, the title of each page appears in the blue bar beneath the "Cisco Unified MeetingPlace System Administration Center" banner.

This section describes the fields and options on each page, presented in alphabetical order by page titles '''M - P'''.

== Maintenance Page ==

Use this page to perform these tasks:
* [[Cisco Unified MeetingPlace Release 8.0 -- Importing Data into Cisco Unified MeetingPlace#Importing Data into Cisco Unified MeetingPlace|Importing Data into Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Running Reports and Exporting Data from Cisco Unified MeetingPlace#Running Reports and Exporting Data from Cisco Unified MeetingPlace|Running Reports and Exporting Data from Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SNMP on the Cisco Unified MeetingPlace Application Server#Configuring SNMP on the Cisco Unified MeetingPlace Application Server|Configuring SNMP on the Cisco Unified MeetingPlace Application Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server#Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server|Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Sending Email Blasts from Cisco Unified MeetingPlace#Sending Email Blasts from Cisco Unified MeetingPlace|Sending Email Blasts from Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Customizing Music and Voice Prompts for Cisco Unified MeetingPlace#Customizing Music and Voice Prompts for Cisco Unified MeetingPlace|Customizing Music and Voice Prompts for Cisco Unified MeetingPlace]] module

== Media Parameters Page ==

Use this page to modify audio and video settings. To find this page, select '''System Configuration > Call Configuration > Media Parameters'''.

===== Table: Field Reference: Media Parameters Page =====

{| border = 1
|-
!Field
!Description
|-
|colspan="2" rowspan="1"|''' Media Parameters'''
|-
|

Audio RTP starting port
|

The Media Server assigns RTP(*1)/UDP(*2) ports starting from the specified value up to that value plus 1024. Modify this field only if required to conform with local firewall rules.

This field applies only to audio ports. Video ports always start at 20000 and are not configurable.

Default 16384
|-
|

TTL
|

Time-to-live value in the IP header of transmitted voice packets. Determines how many hops an IP packet can travel through the network before it is discarded.

Recommendation: Set the value at least high enough to match the number of router hops between Cisco Unified MeetingPlace and the furthest user endpoint. Using a relatively low number can help reduce the quantity of stray packets on the network.

Default: 64
|-
|colspan="2" rowspan="1"|''' QoS (*3)'''
|-
|

Audio media IPv4

Video media IPv4

Signaling IPv4
|

Differentiated Services (DiffServ) code point (DSCP) settings that determine the QoS for the audio and video media signaling, as defined in RFC 2475.

Recommendation: Keep the default value. The other values are available for the rare instances when the network requires a different DSCP setting.

For more information, see the "Network Infrastructure" chapter of the ''Cisco Unified Communications Solution Reference Network Design (SRND)'' that applies to your version of Cisco Unified Communications Manager at http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guides_list.html.

Defaults:
* Audio media: EF DSCP (101110)
* Video media: AF41 DSCP (100010)
* Signaling: CS3 (precedence 3) DSCP (011000)
|-
|colspan="2" rowspan="1"|''' Echo Canceller (*4) (this section is available only when the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Field Reference: Media Resource Configuration Page|Type of media server]] is set to Hardware Media Server)'''
|-
|

Window size (milliseconds)
|

Range of echo return delay that the LEC will attempt to cancel.

Default: 128
|-
|

Enable non-linear processing (NLP)
|

NLP removes the small amount of residual uncanceled echo that inevitably passes through the echo canceller and might be useful for removing residual echo from acoustic or low-bandwidth voice codec (for example, ITU-T G.729) endpoints.

Set this field to No:
* If you do not want to suppress the residual echo.
* If you notice subtle voice quality issues, such as variations in background noise levels while NLP is enabled.

Default: Yes
|-
|

Enable comfort noise in NLP
|

To help make the overall background noise level continuous, the NLP generates comfort noise.

Set this field to No if you prefer silence instead of comfort noise whenever NLP is actively removing residual echo. Note, however, that disabling comfort noise might result in undesirable variations of background noise levels between silence and noise.

Default: Yes
|-
|

Enable LEC w. G.729?
|

Whether to enable LEC when G.729 is in use.

Restriction: You must disable Enable LEC w. G.729? (set this field to No) if you want the High Capacity [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Field Reference: Media Resource Configuration Page|Global audio mode]] field on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Field Reference: Media Resource Configuration Page|Media Resource Configuration Page]] to also use G.729.

Default: Yes
|-
|

Minimum echo return loss (ERL) (dB)
|

A lower ERL setting might help the LEC cancel loud echoes, but it increases the risk of distortion caused by clipping or squelching of the signal.

Default: 6
|-
|

Bulk delay (milliseconds)
|

This value is added to the Window size (milliseconds), so that the cancelled echo return delays will range from Bulk delay (milliseconds) to Bulk delay (milliseconds) + Window size (milliseconds). This allows the LEC to work on echoes that are outside the normal range in exchange for not canceling short-return-delay echoes.

Default: 0
|-
|colspan="2" rowspan="1"|''' Gain Control (*5) (this section is available when the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Field Reference: Media Resource Configuration Page|Type of media server]] is set to Hardware Media Server)'''
|-
|

Enable automatic gain control (AGC)
|

AGC causes Cisco Unified MeetingPlace to dynamically adjust the input gain so the average energy matches a specific level. This is useful when various phones, or people in a conference room, produce different volume levels. Nevertheless, AGC can be problematic in cases where noise might be mistaken for voice.

When AGC is disabled, the specified Fixed gain (dB) is applied to all inputs.

Default: No
|-
|

AGC target level (dBm)
|

The target energy level for the AGC algorithm is applied to all inputs. Make this number less negative to increase the average volume level. The default value of -18 is a typical level for telephony circuits.

Restriction: This field applies only when the Enable automatic gain control (AGC) field is set to Yes.

Default: -18
|-
|

Fixed gain (dB)
|

The fixed input gain is applied to all inputs. Use positive numbers to increase the volume, and use negative numbers to decrease the volume. The default value of 0 leaves the input level alone.

Restriction: This field applies only when the Enable automatic gain control (AGC) field is set to No.

Default: 0
|-
|colspan="2" rowspan="1"|''' Digits (*6)'''
|-
|

Enable RFC 2833 detection
|

There are three DTMF methods:

1. RFC-2833, which is negotiated and can be disabled

2. KPML, which is negotiated and cannot be disabled

3. In-band DTMF tones, which is not negotiated but can be disabled (see "Enable in-band DTMF detection" setting)

RFC 2833 is a standard mechanism for transmitting keypad digits in-band in VoIP media packets. It is commonly used as an adjunct to SIP signaling. Most calls will negotiate either RFC 2833 (in band) or KPML(*7) (out of band) depending on the capabilities of the user endpoint.

If both RFC-2833 and KPML are negotiated (implying that RFC-2833 was enabled), Cisco Unified MeetingPlace will listen for RFC-2833 and not KPML. You can force the use of KPML by disabling RFC-2833 if you are trying to validate KPML. Otherwise, disabling RFC-2833 is typically not necessary as most calls will not notice a difference. If you do notice a difference it may be due to Cisco Unified Communications Manager inserting a MTP to translate RFC-2833 to KPML. This happens if a trunk or endpoint does not support out-of-band signaling. Depending on the setup, MTP insertion may result in loss of video or, if you run out of MTP resources, call failure.

Restriction: this field is available only when the Type of media server is set to Hardware Media Server.

Default: Yes
|-
|

RFC 2833 payload type
|

Payload type for RFC2833 digits, tones, and signals.

Recommendation: Contact your network administrator for the payload type used in your network.

Default: 101
|-
|

Enable in-band DTMF detection
|

Whether to turn on the signal processing which looks for in-band acoustic DTMF (*8) tones in the input audio media stream. Note that DTMF works well only with the G.711 codec.

Recommendation: Enter Yes to support terminals that lack another signaling mechanism, including RFC 2833, KPML, or H.245. Enter No if you find that Cisco Unified MeetingPlace responds to voices as if they were keypad inputs (talk off).

Default: Yes

This option is not available when the Type of media server is set to Express Media Server.
|-
|colspan="2" rowspan="1"|''' Jitter Buffer (this section is not available when the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Type of media server|Type of media server]] is set to Express Media Server)'''
|-
|

Maximum size (milliseconds)

Minimum size (milliseconds)
|

Maximum and minimum lengths of time, in milliseconds, that the jitter buffer holds voice packets. A large jitter buffer helps the system accurately reassemble the media stream, but it adds to perceived latency.

Jitter refers to the variation in the delay of received packets. When voice data is sent across the network, the packets are sent in a continuous stream with the packets spaced evenly apart. Due to network congestion, improper queuing, or configuration errors, the delay between each received packet can vary instead of remaining constant. Some packets can even arrive out of order or not arrive at all.

A higher Maximum size (milliseconds) helps the system adapt to poor conditions. A lower value might be better for interactive conversations, where an occasional dropped packet might be preferable to long latency.

The Minimum size (milliseconds) is the starting jitter buffer size. The closer this value is to the typical jitter on the network, the quicker the system adapts, but this adds directly to latency.

Maximum size (milliseconds) default: 250

Minimum size (milliseconds) default: 30
|-
|colspan="2" rowspan="1"|''' Miscellaneous'''
|-
|

Maximum conference speakers
|

Maximum number of input lines that will be simultaneously mixed together in a meeting. A small value (2) reduces the background noise and echo. A large value (4) is best for more interactive meetings.

Default: 4
|}

===== Footnotes =====

*1: RTP = Real-Time Transport Protocol

*2: UDP = User Datagram Protocol

*3: QoS = Quality of Service

*4: The echo canceller parameters control the Line Echo Canceller (LEC), which reduces audible echo in meetings.

*5: The gain control parameters apply a fixed or adaptive gain to all audio inputs.

*6: The digits parameters control how keypad inputs are received.

*7: KPML = Key Press Markup Language

*8: DTMF = Dual Tone Multi-Frequency

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Parameters that Affect Sound and Video Quality|Configuring Parameters that Affect Sound and Video Quality]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Meetings for Cisco Unified MeetingPlace|Configuring Meetings for Cisco Unified MeetingPlace]] module

== Media Resource Configuration Page ==

Use this page to configure media resources. This page can be used for systems that are configured for a Hardware Media Server or for an Express Media Server.

To find this page, select '''System Configuration > Media Resource Configuration'''.

'''Note: ''' Depending on the type of media server you select, the order of the fields on this page varies.

===== Table: Field Reference: Media Resource Configuration Page =====

{| border = 1
|-
!Field
!Description
|-
|

Type of media server
|

This is set during installation, but you can change it.
|-
|

Total system resource units (SRUs)
|

''Display only.'' Available only when the Type of media server is set to Express Media Server.

Total number of SRUs available in the system. This shows the system capacity, based on hardware (such as the Cisco MCS type and the number and speed of the CPUs). For details, see the ''Planning Guide for Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_implementation_design_guides_list.html.
|-
|

Remaining SRUs for high-end audio and video
|

''Display only.'' Available only when the Type of media server is set to Express Media Server.

Number of SRUs that are available for enhanced audio and video features.

After you load audio and video licenses, the system deducts one SRU per audio or per video license from the remaining SRU pool. For example, if you install one audio and one video license, the system deducts two SRUs from the pool. If you install more licenses than the system can support, the remaining SRU pool shows 0, and the system allocates resources first to audio and second to video (if there are remaining resources).

Some SRUs are consumed immediately for normal system operation and are deducted from the Total system resource units (SRUs).

When you configure ad-hoc meeting features, SRUs are immediately deducted from the remaining SRU pool.

When you configure scheduled meeting features, the system allocates the resources at runtime if available. If there are not enough SRUs remaining in the pool, the system will not offer the feature to the user.
|-
|

Audio licensed ports
|

''Display only''. Number of voice licenses installed on the system, determined by the installed voiceconf and maxvoice licenses. To view installed and enabled licenses, see [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Displaying Licenses|Displaying Licenses]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
|-
|

Audio available ports
|

''Display only''. Number of voice ports for scheduled, reservationless and ad-hoc meetings on the system, determined by either the Audio licensed ports field or the Audio capacity override (ports) field.

Voice ports are also used by meeting recordings. See [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Audio and Video Recordings for Cisco Unified MeetingPlace#Audio and Video Recording Resources and Port Usage|Audio and Video Recording Resources and Port Usage]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Audio and Video Recordings for Cisco Unified MeetingPlace#Configuring Audio and Video Recordings for Cisco Unified MeetingPlace|Configuring Audio and Video Recordings for Cisco Unified MeetingPlace]] module.

The displayed value determines the maximum possible number of simultaneous voice meeting connections to Cisco Unified MeetingPlace.

Hardware media: Audio available ports = Audio licensed ports subject to the availability of hardware resources.

Express Media Server: [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Audio available ports|Audio available ports]] = [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Scheduled audio ports|Scheduled audio ports]].
|-
|

Video licensed ports
|

''Display only''. Number of video licenses on the system, determined by the installed videoconf and maxvideo licenses. To view installed and enabled licenses, see [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Displaying Licenses|Displaying Licenses]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Installing and Managing Licenses for Cisco Unified MeetingPlace#Installing and Managing Licenses for Cisco Unified MeetingPlace|Installing and Managing Licenses for Cisco Unified MeetingPlace]] module.
|-
|

Video available ports
|

''Display only''. Number of video ports for scheduled, reservationless, and ad-hoc meetings on the system, determined by either the Video licensed ports field or the Video capacity override (ports) field.

This number is also affected by the settings on the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)#Add Video Type Page|Add Video Type Page]] based on which video type you select. When the system runs out of resources from the remaining SRU pool, video is no longer offered to the user.

Video ports can also be used by meeting recordings. See [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Audio and Video Recordings for Cisco Unified MeetingPlace#Audio and Video Recording Resources and Port Usage|Audio and Video Recording Resources and Port Usage]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Audio and Video Recordings for Cisco Unified MeetingPlace#Configuring Audio and Video Recordings for Cisco Unified MeetingPlace|Configuring Audio and Video Recordings for Cisco Unified MeetingPlace]] module.

The displayed value determines the maximum possible number of simultaneous video connections to Cisco Unified MeetingPlace.

Hardware media: Video available ports = Video licensed ports subject to the availability of hardware resources.

Express Media Server: Video available ports = Scheduled video ports.
|-
|

Audio floater ports
|

For a description, see the Scheduled Audio and Video Settings section.
|-
|

Audio overbook ports
|

For a description, see the Scheduled Audio and Video Settings section.
|-
|colspan="2" rowspan="1"|''' Scheduled Audio and Video Settings (available only when the Type of media server is set to Express Media Server)'''
|-
|

Scheduled audio ports
|

''Display only''. Number of scheduled voice ports. The system checks this number against the number of installed audio licenses.

Scheduled audio ports = Audio licensed ports - Ad-hoc audio ports
|-
|

Enable scheduled G.729 or G.722
|

Enables G.729 or G.722 high-quality voice ports for scheduled meetings. The system does not reserve these ports in advance but takes them from the remaining SRU pool only if there are enough resources remaining on the system.

Cost per port: 5 SRUs.
|-
|

Scheduled video ports
|

Number of scheduled video ports. The system does not reserve these ports in advance but takes them from the remaining SRU pool only if there are enough resources remaining on the system.

Scheduled video ports = Video licensed ports - Ad-hoc video ports
|-
|

Audio floater ports
|

''Applies to scheduled meeting resource allocation only''. Number of voice ports that are reserved as floater ports. You use floater ports for any scheduled meeting to accommodate unanticipated additional participants. Configuring voice floater ports reduces the number of ports that are available for scheduling meetings.

Voice floater ports are also used by meeting recordings. See [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Audio and Video Recordings for Cisco Unified MeetingPlace#Audio and Video Recording Resources and Port Usage|Audio and Video Recording Resources and Port Usage]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Audio and Video Recordings for Cisco Unified MeetingPlace#Configuring Audio and Video Recordings for Cisco Unified MeetingPlace|Configuring Audio and Video Recordings for Cisco Unified MeetingPlace]] module.

Restrictions:
* This number cannot exceed the value of the Audio licensed ports field.
* Changing the licenses might affect the upper and lower limits for this parameter.

For recommendations for determining the number of floater ports, see the ''Planning Guide for Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/ products/sw/ps5664/ps5669/products_implementation_design_guides_list.html.

Default: 2
|-
|

Audio overbook ports
|

''Applies to scheduled meeting resource allocation only''. Number of voice ports to allow for scheduled meetings that exceed the number of available voice ports on the system. Configuring voice overbook ports increases the risk of users being unable to attend scheduled meetings.

If you use this feature, you assume that users who are scheduled to attend meetings do not always attend, leaving their reserved voice ports unused. Once all voice ports are in use, other users who try to attend a voice meeting will not be able to get through.

Restrictions:
* This number cannot exceed twice the value of the Audio licensed ports field.
* Changing the licenses might affect the upper and lower limits for this parameter.

For recommendations for determining the number of overbook ports, see the ''Planning Guide for Cisco Unified MeetingPlace'' at http://www.cisco.com/en/US/ products/sw/ps5664/ps5669/products_implementation_design_guides_list.html.

Default: 0
|-
|colspan="2" rowspan="1"|''' Ad-Hoc Audio and Video Settings (available only when the Type of media server is set to Express Media Server)'''
|-
|

Ad-hoc audio ports
|

Number of ad-hoc voice ports registered to Cisco Unified Communications Manager. The Cisco Unified MeetingPlace system checks this number against the number of installed audio licenses. Changing this value affects the number of resources in the remaining SRU pool.

Default: Ad-hoc audio ports = Audio licensed ports - Scheduled audio ports

Select '''change''' to change the number of ad-hoc audio ports.
|-
|

Enable ad-hoc G.729 or G.722
|

Enable or disable G.729 or G.722 ad-hoc ports.

You can enable this feature only if there are enough SRUs available on the system to support these features. If there are enough resources, the system immediately deducts them from the remaining SRU pool.

Cost per port: 5 SRUs.

Default: No
|-
|

Enable ad-hoc video
|

Enable or disable ad-hoc video. When enabled, the system reserves the same number of ad-hoc video ports as ad-hoc audio ports from the SRU pool. Based on the selected Ad-hoc video mode type, these video ports are configured at the Ad-hoc video minimum bit rate (kbps) and the Ad-hoc video maximum bit rate (kbps).

The system guarantees video ports at the basic rate of 320 kbps. The system provides additional bit rates to the port only if there are remaining SRUs.

Default: No
|-
|

Ad-hoc video ports
|

''Display only''. Number of ad-hoc video ports available. This number cannot be larger than the number of Ad-hoc audio ports.

If Enable ad-hoc video is disabled, the ports that were allocated for ad-hoc video are now available for Scheduled video ports.

Default: Ad-hoc video ports = Ad-hoc audio ports
|-
|

Ad-hoc video mode
|

This system-level setting applies to all ad-hoc conferences. Options:
* H.263
* H.264 AVC (Level 1.1)-Low resolutions available with mobile endpoints. Example: QCIF 30 FPS.
* H.264 AVC (Level 1.3)-Most common resolutions available with desktop endpoints. Example: CIF 30 FPS.
* H.264 AVC (Level 3.0)-High quality resolutions for more advanced endpoints. Example: VGA at 30 FPS.
* H.264 AVC (Level 3.1)-High definition resolutions for HD endpoints. Example: 720p HD at 30 FPS.

Note that the resolution examples are not guaranteed. Per the H.264/AVC video coding standard, the endpoint must be able to support different resolutions for a given negotiated level. The actual resolution will vary and can change at any time during the conference. Cisco Unified MeetingPlace signals the specified H.264 level but does not mandate any resolution scheme.

Restriction: You can configure the ad-hoc video mode only if you set the "Enable ad-hoc video" field to Yes. Otherwise, the "Ad-hoc video mode" field is dimmed.

Default: H.263
|-
|

Ad-hoc video minimum bit rate (kbps)
|

Minimum bit rate for the video experience. The minimum bit rate is the minimum rate that the endpoint must receive from the conference.

The conference bridge offers the minimum and maximum bit rates to the endpoint during negotiation. The minimum bit rate specifies the minimum video experience and if the system does not have resources to support this rate, video is not offered to the user.
|-
|

Ad-hoc video maximum bit rate (kbps)
|

Maximum bit rate for ad-hoc video.

The maximum bit rate is the maximum rate that the endpoint can send video to the conference.
|-
|colspan="2" rowspan="1"|''' Override System Capacity'''
|-
|

Override system audio and video capacity
|

Select '''Yes''' to override the system audio and video capacity. This makes the Audio capacity override (ports) and Video capacity override (ports) become active.

When the Type of media server is set to Hardware Media Server, you can install more licenses than the hardware can support, and you can override the system capacity with this setting.

When the Type of media server is set to Express Media Server, you can install more licenses than the hardware can support. The system allocates all the SRUs to support basic audio unless you use the Override system audio and video capacity. You can free up SRUs by using the override capacity settings.

Use the Resource Management Spreadsheet to help you analyze the audio and video requirements of your user base. If you know how many users on the network use video and at what speed, and what type of audio quality, you can determine how many licenses to buy and whether to buy additional licenses to override the system capacity to provide extra features.

For information on using the Resource Management Spreadsheet, see the ''Planning Guide for Cisco Unified MeetingPlace'' at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment.

Default: No
|-
|

Audio capacity override (ports)
|

Number of voice ports for scheduled, reservationless, and ad-hoc meetings on the system. This field can be modified only when the Override system audio and video capacity field is set to Yes. Select '''Change''' to enter the number of override ports.
|-
|

Video capacity override (ports)
|

Number of video ports for scheduled, reservationless, and ad-hoc meetings on the system. This field can be modified only when the Override system audio and video capacity field is set to Yes. Select '''Change''' to enter the number of override ports.

Recommendation: When the Type of media server is set to Hardware Media Server, enter the number of video ports that is supported by your Hardware Media Server. See the limitations for Cisco Unified MeetingPlace licenses in the ''Planning Guide for Cisco Unified MeetingPlace'' at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment.
|-
|colspan="2" rowspan="1"|''' Global Settings (available only when the Type of media server is set to Hardware Media Server)'''
|-
|

Global audio mode
|

Choose between the higher-capacity and higher-quality options.

See the recommendations for determining the global audio mode in the ''Planning Guide for Cisco Unified MeetingPlace'' at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment.
|-
|colspan="2" rowspan="1"|''' Ports Per Meeting'''
|-
|

Maximum ports per reservationless meeting

Maximum ports per scheduled meeting

Maximum reserved ports per scheduled meeting
|

Maximum number of voice, web, or video ports that can be used in a meeting.

The first two fields (Maximum ports per reservationless meeting and Maximum ports per scheduled meeting) restrict the maximum size that a meeting can grow to even when ports are still available.
* When the Type of media server is set to Express Media Server, the upper limit for these two fields is Scheduled audio ports.
* When the Type of media server is set to Hardware Media Server, the upper limit for these two fields is Audio licensed ports.
* The lower limit for both of these fields is 2.

The third field (Maximum reserved ports per scheduled meeting) restricts the maximum number of ports that can be ''reserved'' when a meeting is scheduled.
* The upper limit for this field is Maximum ports per scheduled meeting.
* The lower limit for this field is 2.
|-
|

Default number of ports per audio meeting
|

Default number of voice ports to reserve for meetings. This value is used in the Number of Participants field when scheduling meetings. This field also applies to reservationless meetings.

Restriction: This number cannot exceed the [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Audio available ports|Audio available ports]] field value.

Default: 4
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Ad-Hoc Conferencing for Cisco Unified MeetingPlace#Configuring Ad-Hoc Conferencing for Cisco Unified MeetingPlace|Configuring Ad-Hoc Conferencing for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Meetings for Cisco Unified MeetingPlace|Configuring Meetings for Cisco Unified MeetingPlace]] module

== Media Statistics Report Page ==

Use this page to run reports that are useful for troubleshooting the software-based audio and video mixers in Cisco Unified MeetingPlace.

To find this page, select '''Reports > Media Statistics Report'''.
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Output Reference: Media Statistics Report Page > Conference Statistics Report|Output Reference: Media Statistics Report Page > Conference Statistics Report]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Output Reference: Media Statistics Report Page > Channel Statistics Report|Output Reference: Media Statistics Report Page > Channel Statistics Report]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages)#Table: Output Reference: Media Statistics Report Page > Channel Status Report|Output Reference: Media Statistics Report Page > Channel Status Report]]

===== Table: Field Reference: Media Statistics Report Page =====

{| border = 1
|-
!Field
!Description
|-
|

Conference Statistics Report
|
* Global statistics-Contains historical data that applies to all voice meetings and video conferences handled by the mixers since initialization.
* Conference statistics-Contains information about voice meetings and video conferences that are currently active.
|-
|

Channel Statistics Report
|

Displays mixer statistics for each voice call and video connection that is currently active.
|-
|

Channel Statistics Report
|

Displays mixer status information about each voice call and video connection that is currently active.
|}

'''Note: ''' The fields that display only video information do not appear in the report output if no video calls are received by Cisco Unified MeetingPlace.

===== Table: Output Reference: Media Statistics Report Page > Conference Statistics Report =====

{| border = 1
|-
!Field Name
!Description
|-
|colspan="2" rowspan="1"|''' Global Statistics'''
|-
|

Start Time
|

Date and time when the mixer was initialized (system boot time).
|-
|

Elapsed Time
|

Number of hours, minutes, and seconds that the mixer has been active.
|-
|

Active Audio/Video Conf
|

Number of currently active voice and video meetings.
|-
|

Max Active Conf
|

Maximum number of voice meetings, video meetings, and breakout sessions that were active simultaneously since initialization.
|-
|

Total Audio/Video Conf
|

Number of voice meetings, video meetings, and breakout sessions that were held since initialization.
|-
|

Active Audio/Video Chn
|

Number of channels (callers) currently connected to either the audio or video mixer.
|-
|

Join/Depart Conf
|

Number of times that callers joined or left voice meetings and video meetings as well as the number of times that the system called a user to join a meeting or ejected someone from a meeting since system initialization.
|-
|

Max Conf Duration
|

Elapsed time of longest running voice or video meeting.
|-
|

Total Audio/Video Rcv Pkt
|

Number of RTP (1) packets received by the audio and video mixers.
|-
|

Total Audio/Video Xmt Pkt
|

Number of RTP packets transmitted by the audio and video mixers.
|-
|

Total Audio Drop Pkt
|

Number of incoming voice packets that were detected as missing.
|-
|

Max Jitter
|

Maximum length of time, in milliseconds, that the RTP jitter buffer holds voice packets.
|-
|colspan="2" rowspan="1"|''' Conference Statistics'''
|-
|

System Active
|

Status of the server.
|-
|

Date and Time
|

Date and time that the report was last refreshed, which occurs automatically and frequently.
|-
|

Conf ID
|

Unique number used by the local audio mixer to identify the voice meeting. This value is different from the meeting ID displayed to users.
|-
|

Start Time
|

Date and time when the voice meeting began.
|-
|

Elapsed
|

Amount of time that the voice meeting has been active.
|-
|

Max Active Chn
|

Total number of active channels (callers) connected to the audio mixer since the voice meeting began.
|-
|

Active Chn
|

Number of channels (callers) currently connected to the audio mixer for this meeting.
|-
|

Join/Depart Conf
|

Number of user-initiated joinings and departures (the number of times that callers joined or left voice meetings) and system-initiated joinings and departures (the number of times that the system called a user to join a meeting or ejected someone from a meeting) since system initialization.
|-
|

Audio Pkts Recv/Xmit
|

Number of audio RTP packets received and transmitted by the audio mixer for this meeting.
|-
|

Video Pkts Recv/Xmit
|

Number of video RTP packets transmitted by the video mixer for this meeting.
|-
|

Audio Bytes Recv
|

Amount of audio RTP data, in bytes, received by the audio mixer for this meeting.
|-
|

Audio Bytes Xmit
|

Amount of audio RTP data, in bytes, sent by the audio mixer for this meeting.
|-
|

Intra-frames Requested/Detected/ Timeouts
|

Number of times the video mixer requested and detected intra-frames. Also the number of timed-out intra-frame requests.

Intra-frames (or I-frames) are frames that carry the complete picture of a video image from a participant. I-frames are sent periodically in a video stream and whenever a video speaker switch occurs.

When the active speaker changes, the system requests an I-frame and then waits to receive an I-frame from the new active speaker before switching the video stream. Until an I-frame is received or the active speaker changes again, the system sends FVU requests to the new active speaker every two seconds.
|-
|

Active/Previous Speaker
|

Channel IDs ([[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Chn ID|Chn ID]]) of the active and previous speakers in the conference.
|-
|

Active Video Chn
|

Number of active video channels in use during this conference.
|-
|

Max Jitter
|

Maximum jitter detected in incoming audio during this conference.
|-
|

Max Play Delay
|

Maximum delay during this meeting, in milliseconds, between the time a play request was received and the time the buffer started playing the data.
|-
|

Play Delay
|

Current delay, in milliseconds, between the time a play request is received and the time the buffer starts playing the data for this meeting.
|-
|

Max Record Delay
|

Maximum delay during this meeting, in milliseconds, between the time a file recording was requested and the time the recording began.
|-
|

Record Delay
|

Current delay, in milliseconds, between the time a file recording is requested and the time the recording begins.
|}

Footnote 1: RTP = Real-Time Transport Protocol

'''Note: ''' The fields that display only video information do not appear in report output if no video calls are received by Cisco Unified MeetingPlace.

===== Table: Output Reference: Media Statistics Report Page > Channel Statistics Report =====

{| border = 1
|-
!Field Name
!Description
|-
|

Total Active Channels
|

Number of channels that are currently active.
|-
|

Channel Record Last Updated
|

Date and time that the channel record was last refreshed, which occurs automatically and frequently.
|-
|

Chn ID
|

Channel identification assigned to the caller.
|-
|

Conf ID
|

Unique number used by the local audio mixer to identify the voice meeting. This value is different from the meeting ID displayed to users.
|-
|

Start Time
|

Date and time that the call was established.
|-
|

Elapsed
|

Amount of time that the call has been active.
|-
|

Audio Pkts Rcv/Sent/Lost
|

Number of audio RTP (*1) packets received from and sent to the endpoint and the number of lost packets.
|-
|

Video Pkts Rcv/Sent
|

Number of video RTP packets received from and sent to the endpoint.
|-
|

Audio KBytes Rcv/Sent
|

Amount of audio RTP data, in kilobytes, received from and sent to the endpoint.
|-
|

Video KBytes Rcv/Sent
|

Amount of video RTP data, in kilobytes, received from and sent to the endpoint.
|-
|

Out of Order Video Pkts
|

Number of video RTP packets that were received out of sequence from the endpoint.
|-
|

FVU / Flow Cntl Requests
|

Number of fast video update requests and flow-control requests received from the endpoint.
|-
|

I frame Req / Detected
|

Number of I-frames requested and detected. I-frames are frames that carry the complete picture of a video image of a participant. I-frames are sent periodically in a video stream and whenever a video speaker switch occurs.

When the active speaker changes, the system requests an I-frame and then waits to receive an I-frame from the new active speaker before switching the video stream. Until an I-frame is received or the active speaker changes again, the system sends FVU requests to the new active speaker every two seconds.

Under normal conditions, the requested and detected values should be the same. If these counts do not match, check the video endpoints for errors.

Also, endpoints that have difficulty decoding video can request additional I-frames. Therefore, endpoints that have a higher I-frame count than others in a conference should be examined for network issues.
|-
|

Flush Rate
|

Average number of flushed packets per second. A flushed packet is one that arrived too late for the audio mixer to play in the correct sequence order and is thus thrown away.

'''Note: ''' The value of this field and the Insert Rate field should be equal.
|-
|

Insert Rate
|

Average number of PLC (*2) packets per second that are locally generated by the audio mixer and inserted in place of packets that did not arrive in time to play in the correct sequence order. Without PLC packets, callers would hear clicks and pops because of missing packets.

'''Note: ''' The value of this field and the Flush Rate field should be equal.
|-
|

Silence Pkt Rate
|

Average number of RTP packets per second that are not received, not sent, or are SID(*3) packets.

Using VAD(*4) saves bandwidth by sending RTP packets over the network only when the audio reaches a certain level, such as when a caller talks. When the caller stops talking, a SID packet is sent to notify the audio mixer that a subsequent gap in RTP packets is caused by silence on the call, as opposed to serious network delay. If the last packet in a stream of RTP packets is a SID, the audio mixer knows not to count the subsequent gap as jitter and to locally generate and play comfort noise to fill the gap.
|-
|

Audio Pkt Size
|

Size of audio RTP packets, in bytes. 160-byte packets correspond to a 20 ms packetization period.
|-
|

Max Jitter
|

Maximum jitter detected in incoming audio packets from the endpoint.
|-
|

Avg Jitter
|

Average jitter value observed for packets arriving from the endpoint.
|-
|

Pkt Delay
|

Delay, in milliseconds, between the current packet being played and the last received packet. Also called buffer depth.
|-
|

Digits Rcvd
|

Number of digits received from the endpoint.
|-
|

Digits Sent
|

Number of digits sent to the endpoint.
|-
|

Max Play Delay
|

Maximum delay, in milliseconds, between the time a play request was received and the time the buffer started playing the data.
|-
|

Play Delay
|

Current delay, in milliseconds, between the time a play request is received and the time the buffer starts playing the data.
|-
|

Max Record Delay
|

Maximum delay, in milliseconds, between the time a file recording was requested and the time the recording began.
|-
|

Record Delay
|

Current delay, in milliseconds, between the time a file recording is requested and the time the recording begins.
|}

===== Footnotes =====

*1: RTP = Real-Time Transport Protocol

*2: PLC = packet loss concealment

*3: SID = Silence Insertion Descriptor

*4: VAD = Voice Activity Detection

'''Note: ''' The fields that display only video information do not appear in report output if no video calls are received by Cisco Unified MeetingPlace.

===== Table: Output Reference: Media Statistics Report Page > Channel Status Report =====

{| border = 1
|-
!Field Name
!Description
|-
|

Conf ID
|

Unique number used by the local audio mixer to identify the voice meeting. This value is different from the meeting ID displayed to users.
|-
|

Chn ID
|

Channel identification assigned to the caller.
|-
|

Callers DN (`R"=Outdial)
|

Phone number of the video caller. An R at the end denotes that this is an outgoing call.
|-
|

State
|

Whether the caller is currently in a voice meeting.
|-
|

Mixed
|

Whether or not the voice stream of the caller is currently being heard by others in the voice meeting. The audio mixer mixes the three loudest callers at any given time, and all other meeting participants cannot be heard at all.
|-
|

Rmt Audio IP Addr

or

Rmt A/V IP Addr
|

Voice endpoint IP address of the caller.

or

Voice endpoint IP address and video endpoint IP address of the caller.
|-
|

Rmt Audio RTP Port

or

Rmt A/V RTP Port
|

Voice endpoint RTP (*1) port of the caller.

or

Voice endpoint RTP port and video endpoint RTP port of the caller.
|-
|

Rmt Audio RTCP Port

or

Rmt A/V RTCP Port
|

Voice endpoint RTCP (*2) port of the caller.

or

Voice endpoint RTCP port and video endpoint RTCP port of the caller.
|-
|

Lcl Audio IP Addr

or

Lcl A/V IP Addr
|

IP address of the audio port for your Cisco Unified MeetingPlace system.

or

IP addresses of the audio and video ports for your Cisco Unified MeetingPlace system.
|-
|

Lcl Audio RTP Port

or

Lcl A/V RTP Port
|

RTP port of the Cisco Unified MeetingPlace audio mixer, which receives the audio RTP stream from the caller.

or

RTP ports of the Cisco Unified MeetingPlace audio mixer and video mixer, which receive the audio and video RTP streams of the caller.
|-
|

Lcl Audio RTCP Port

or

Lcl A/V RTCP Port
|

RTCP port of the Cisco Unified MeetingPlace audio mixer, which receives the audio RTCP messages from the caller

or

RTCP ports of the Cisco Unified MeetingPlace audio mixer and video mixer, which receive the audio and video RTCP messages from the caller.
|-
|

Picture Format
|

Picture format information for Common Intermediate Format (CIF), Video Graphics Array (VGA), high definition (HD), and the video endpoint H.264 profile level.
|-
|

TOS
|

IP type of service setting for the output stream to this caller.
|-
|

TTL
|

Time-to-live, in hops, for transmitted packets.
|-
|

Audio Codec Type

or

A/V Codec Type
|

Audio payload type used in the RTP media streams.

or

Audio and video payload type used in the RTP media streams.

Valid payload types:
* 0-G.711uLaw.
* 8-G.711aLaw.
* 34-H.263 (1996) video.
* 96-127-DTMF (*3) or H.264 video. During call setup, an unused payload type is negotiated from the dynamic payload type range.
|-
|

Ann Active
|

Whether an announcement is currently being played.
|-
|

Ann File Name
|

Displays the full name of the file or prompt that is currently being played.
|-
|

Rec Active
|

Whether the call is being recorded.
|-
|

Rec File Name
|

Displays the full name of the file to which the call is being recorded.
|}

===== Footnotes =====

*1: RTP = Real-Time Transport Protocol

*2: RTCP = RTP Control Protocol

*3: DTMF = dual tone multifrequency

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Running Reports and Exporting Data from Cisco Unified MeetingPlace#Running a Report about Media Statistics|Running a Report about Media Statistics]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Running Reports and Exporting Data from Cisco Unified MeetingPlace#Running Reports and Exporting Data from Cisco Unified MeetingPlace|Running Reports and Exporting Data from Cisco Unified MeetingPlace]] module

== Meeting Cancellation Report Page ==

This page provides information about each meeting that was cancelled during a specified range of dates. To find this page, select '''Reports > Meeting Cancellation Report'''.

===== Table: Field Reference: Meeting Cancellation Report Page =====

{| border = 1
|-
!Field
!Description
|-
|

Report type
|

Output format, either text or HTML.

Restriction: If you select txt, all fields are displayed in the report output. The check boxes for selecting fields become dimmed.
|-
|

Destination
|

Output destination. For restrictions and recommendations for each option, see [[Cisco Unified MeetingPlace Release 8.0 -- Running Reports and Exporting Data from Cisco Unified MeetingPlace#Reports and Exported Data|Reports and Exported Data]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Running Reports and Exporting Data from Cisco Unified MeetingPlace#Running Reports and Exporting Data from Cisco Unified MeetingPlace|Running Reports and Exporting Data from Cisco Unified MeetingPlace]] module.
|-
|

Sort by
|

Whether you want the report data sorted by scheduler ID, meeting ID, or date.

Default: Meeting ID
|-
|

Start date
|

Default: yesterday (mm/dd/yyyy)
|-
|

End date
|

Default: today (mm/dd/yyyy)
|-
|colspan="2" rowspan="1"|''' Check Boxes and Output Fields'''
|-
|

Show all fields
|

Displays all fields in the report output.

Unchecking this clears all check boxes, except Scheduler ID and Meeting ID.
|-
|

Scheduler ID
|

Name of the meeting owner.

Restriction: This check box cannot be cleared.
|-
|

Meeting Subject
|

Meeting subject.
|-
|

Number of required ports
|

Number of ports that were reserved for the meeting.
|-
|

Required length of conference
|

Length of time scheduled for the meeting.
|-
|

Meeting ID
|

Meeting ID.

Restriction: This check box cannot be cleared.
|-
|

Start date/time of conference
|

Scheduled start date and time of the meeting.
|-
|

Billing code
|

See Billing code.
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Running Reports and Exporting Data from Cisco Unified MeetingPlace#Running Reports and Exporting Data from Cisco Unified MeetingPlace|Running Reports and Exporting Data from Cisco Unified MeetingPlace]] module

== Meeting Categories Page ==

To find this page, select '''System Configuration > Meeting Categories'''.

===== Table: Navigation Reference: Meeting Categories Page =====

{| border = 1
|-
!To
!Do This
|-
|

Sort by owner, last modifier, or last modification time
|

Select the '''Owner''', '''Last Modified By''',''' '''or '''Last Modified Time '''column heading.
|-
|

Change the sort order to ascending or descending
|

Select the column heading to display an arrow. Select the heading again to toggle between a down arrow (ascending sort) and an up arrow (descending sort).
|-
|

Display a shorter or longer list in one view
|

At the bottom of the page, in the Rows per page field, select the number of entries to display.
|-
|

Display a different page of entries
|

At the bottom of the page, perform one of these actions:
* In the Go field, enter the page number to display, and select '''Go'''.
* Select the arrows to page through the list.
|-
|

Search by name
|

Enter at least the first character of the name, and select '''Search'''.
|-
|

Edit an existing entry
|

Select an entry.
|-
|

Create a new meeting category
|

Select '''Add New'''.
|-
|

Delete one or more meeting categories
|

Check the appropriate check boxes in the far left column, and select '''Delete Selected'''.

Restriction: You cannot delete the preconfigured Standard meeting category.
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Meeting Categories|Configuring Meeting Categories]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Meetings for Cisco Unified MeetingPlace|Configuring Meetings for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Add Meeting Categories Page|Add Meeting Categories Page]]

== Meeting Configuration Page ==

Use this page to configure system-wide meeting parameters. To find this page, select '''System Configuration > Meeting Configuration'''.

===== Table: Field Reference: Meeting Configuration Page =====

{| border = 1
|-
!Field
!Description
|-
|

Default meeting length (minutes)
|

Default length of meetings, in minutes. This value is used in the Duration field when scheduling meetings. This field also applies to reservationless meetings.

Restrictions:
* This number cannot exceed the value entered in the Maximum meeting length (minutes) field.
* This field does not apply to meetings that are scheduled from Microsoft Outlook.

Default: 30
|-
|

Maximum meeting length (minutes)
|

User cannot schedule meetings longer than this number of minutes. Also, reservationless meetings end after this number of minutes.

Restriction: If this value differs from the following, the lowest value is used:
* Maximum meeting length (minutes) field in the user profile of the meeting owner.
* Maximum Call Duration Timer service parameter in Cisco Unified Communications Manager.
: See [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco Unified Communications Manager#Configuring the Maximum Call Duration in Cisco Unified Communications Manager|Configuring the Maximum Call Duration in Cisco Unified Communications Manager]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Integrating Cisco Unified MeetingPlace with Cisco Unified Communications Manager#Integrating Cisco Unified MeetingPlace with Cisco Unified Communications Manager|Integrating Cisco Unified MeetingPlace with Cisco Unified Communications Manager]] module.

Default: 240
|-
|

Meeting ID start guard time (minutes)
|

Number of minutes before the requested meeting start time that the meeting ID is reserved.

This field and the Meeting ID end guard time (minutes) field control when meeting IDs are available for reuse and when the system recognizes a meeting ID.

Before the meeting ID start guard time, users who try to attend the meeting hear or see on the screen: "This is not a recognized meeting ID number." During the meeting ID start guard time period, users hear: "The meeting has not started."

Meeting ID start guard times are not applied to reservationless meetings or meetings that begin immediately.

Recommendation: 30. To ensure that meeting IDs are available for reuse, decrease this value if the number of simultaneous meetings to be held on your system is about the same as the number of available meeting IDs.

Default: 30
|-
|

Meeting ID end guard time (minutes)
|

Number of minutes after a meeting that the meeting ID is reserved.

This field and the Meeting ID start guard time (minutes) field control when meeting IDs are available for reuse and when the system recognizes a meeting ID.

During the meeting ID end guard time, users who try to attend the meeting hear or see on the screen: "The meeting has ended." After the meeting ID end guard time period, users hear: "This is not a recognized meeting ID number."

Meeting ID end guard times are not applied to reservationless meetings or meetings that are user-terminated before the scheduled end time.

Recommendation: 15. To ensure that meeting IDs are available for reuse, decrease this value if the number of simultaneous meetings to be held on your system is about the same as the number of available meeting IDs.

Default: 30
|-
|

Extend meeting (minutes)
|

Whether to extend meetings if they run over the requested duration ''and'' if ports are available. Meetings might continue to be extended as long as ports are available, up to the Maximum meeting length (minutes) field value. Specifically for web meeting rooms:
* For meetings scheduled with zero locations, the web meeting is extended as long as there is at least one participant in the web meeting room.
* For meetings scheduled with at least one location, the web meeting is extended only if there are at least two voice meeting participants.

If you select Yes, also enter the number of minutes to extend meetings.

If you select No, or if ports are not available at the end of the meeting, callers receive a warning that the meeting will end. The warning time is determined by the Last warning time (minutes) field.

Default: Yes, 15
|-
|

Early meeting start (minutes)
|

Maximum time, in minutes, before the scheduled meeting start that participants can enter the meeting. This field does not apply to reservationless meetings.

Restriction: This number cannot exceed the value entered in the Meeting ID start guard time (minutes) field.

Recommendation: 10

Default: 10
|-
|

Last warning time (minutes)
|

Number of minutes before the end of a meeting when the system issues a warning.

Default: 2
|-
|

Minimum meeting password length
|

Minimum number of characters required in meeting passwords.

A value of 0 means that meeting passwords are never required, even for meetings that are scheduled by users whose user profile [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (A - C pages)# Table: Field Reference: Add User Profile Page and Edit User Profile Page|Meeting password required]] field is set to Yes.

Recommendation: Follow your company guidelines for similar telecommunications systems.

Default: 0
|-
|

Maximum advance days to schedule
|

How many days in advance users can schedule meetings.

Default: 300
|-
|

Days until meeting statistics deleted
|

Minimum number of days that meeting data is stored on the Application Server and Web Server. To determine the actual date when the meeting data will be deleted:
* If you enter a value less than 7, the system deletes the meeting data after the specified number ''plus'' 7 days. For example, if you enter 5, the meeting data is deleted after 5 + 7 = 12 days.
* If you enter a value equal to or greater than 7 days, the system deletes the meeting data after the specified number of days. For example, if you enter 7, the meeting data is deleted after 7 days.

Once meeting data is deleted, it is no longer available for reporting purposes.

Restriction: Changes to this field apply only to meetings that are scheduled ''after'' the field is changed. For each meeting, the system applies the field value that was configured at the time the meeting was scheduled.

Recommendation: If your system holds more than 2000 meetings per day, keep this value lower than 180 days (or 6 months). This will prevent database size issues that may impact system performance. For more information, see the [[Cisco Unified MeetingPlace Release 8.0 -- Maintaining the Cisco Unified MeetingPlace Database#Maintaining the Cisco Unified MeetingPlace Database|Maintaining the Cisco Unified MeetingPlace Database]] module.

Default: 120
|-
|

Allow vanity meeting IDs
|

Whether users can request a specific meeting ID when scheduling a meeting. If a user requests a meeting ID that is already reserved for another meeting, the system prompts the user to select another meeting ID.

If you select No, the system generates a unique, randomly generated ID for every scheduled meeting. Users cannot change the assigned meeting IDs.

Default: Yes
|-
|

Minimum scheduled meeting ID length
|

Minimum number of characters in meeting IDs.

Note that longer meeting IDs are more secure, because they are more difficult to guess.

Restriction: If this value is set to 3 ''and'' the scheduler does not enter a vanity meeting ID, the system assigns a four-digit meeting ID to all new meetings.

Default: 4
|-
|

Enable rescheduled recurring meetings
|

Whether to enable users to reschedule recurring meetings.

Default: Yes
|-
|

Disconnect empty port (minutes)
|

Number of minutes after the scheduled start time that ports are held after all participants leave, even when the scheduled meeting time is not over. This time accounts for longer meetings when people break and return to the meeting. This time also applies if no one comes to the meeting.

Restriction: This parameter does not apply to reservationless meetings.

Default: 30
|-
|

Early meeting port release (minutes)
|

Number of minutes before the scheduled end of a meeting that ports are released if no ports are in use for that meeting.

Default: 5
|-
|colspan="2" rowspan="1"|'''Auto-Answer Devices'''
|-
|

Meeting controls device
|

Determines whether the meeting owner or the meeting itself controls when auto-answer devices are disconnected from each meeting:
* No-When the meeting owner leaves the meeting, all auto-answer devices are disconnected from the meeting.
: If the meeting owner never joins the meeting, auto-answer devices are disconnected from the meeting when ports are disconnected or released due to the Disconnect empty port (minutes) and Early meeting port release (minutes) settings on the Meeting Configuration Page, whichever field is enforced first.
* Yes-The Connected until meeting ends field is enforced.

Restriction: You must select '''Yes''' if your Cisco Unified MeetingPlace system is integrated with Cisco WebEx and allows external meetings. Otherwise, Cisco WebEx Network-Based Recording (NBR) will not work.

Default: No
|-
|

Connected until meeting ends
|

Determines how meeting-controlled auto-answer devices are disconnected from meetings:
* No-All auto-answer devices are disconnected from the meeting when all ''non''-auto-answer participants leave the meeting.
* Yes-Auto-answer devices are disconnected from the meeting when ports are disconnected or released due to the Disconnect empty port (minutes) and Early meeting port release (minutes) settings on the Meeting Configuration Page, whichever field is enforced first.

Restriction: This field is ignored when the Meeting controls device field is set to No.

Default: No
|-
|

Disconnect when all continuous meeting parties leave
|

Whether to disconnect auto-answer devices from continuous meetings when all ''non''-auto-answer participants leave the meeting.

Recommendation: Set this field to Yes if both the Meeting controls device and Connected until meeting ends fields are also set to Yes. Otherwise, the system will never automatically disconnect auto-answer devices from continuous meetings.

Default: No
|-
|colspan="2" rowspan="1"|''' Recordings'''
|-
|

Maximum meeting message length (minutes)
|

Maximum length of each recorded meeting message.

Default: 60
|-
|

Maximum meeting name length (seconds)
|

Maximum length of recorded meeting names.

Default: 4
|-
|

Maximum participant name length (seconds)
|

Maximum length of recorded meeting participant names.

Default: 4
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Meetings for Cisco Unified MeetingPlace#Configuring Meetings for Cisco Unified MeetingPlace|Configuring Meetings for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Endpoints for Cisco Unified MeetingPlace#How to Configure Auto-Answer Devices|How to Configure Auto-Answer Devices]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Endpoints for Cisco Unified MeetingPlace#Configuring Endpoints for Cisco Unified MeetingPlace|Configuring Endpoints for Cisco Unified MeetingPlace]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Audio and Video Recordings for Cisco Unified MeetingPlace#Configuring Audio and Video Recordings for Cisco Unified MeetingPlace|Configuring Audio and Video Recordings for Cisco Unified MeetingPlace]] module

== Meeting Information Report Page ==

This report provides information about meetings that occur in the specified date range. The output is grouped by [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#User ID|User ID]] of the meeting owner. To find this page, select '''Reports > Meeting Information Report'''.

===== Table: Field Reference and Output Field Reference: Meeting Information Report Page =====

{| border = 1
|-
!Field
!Description
|-
|

Report type
|

Output format, either text or HTML.
|-
|

Destination
|

Output destination. For restrictions and recommendations for each option, see [[Cisco Unified MeetingPlace Release 8.0 -- Running Reports and Exporting Data from Cisco Unified MeetingPlace#Reports and Exported Data|Reports and Exported Data]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Running Reports and Exporting Data from Cisco Unified MeetingPlace#Running Reports and Exporting Data from Cisco Unified MeetingPlace|Running Reports and Exporting Data from Cisco Unified MeetingPlace]] module.
|-
|

Start date
|

Default: yesterday (mm/dd/yyyy)
|-
|

End date
|

Default: today (mm/dd/yyyy)
|-
|colspan="2" rowspan="1"|''' Check Boxes and Output Fields'''
|-
|

Show all fields
|

Displays all fields in the report output.

'''Note: ''' Unchecking this clears all check boxes that are not dimmed.
|-
|

Owner ID
|

User ID of the meeting owner.
|-
|

Date held
|

Date and time that this meeting took place.
|-
|

Billing code
|

Billing code for the meeting.
|-
|

Disk space clear date
|

Date and time when recordings for the meeting will be deleted from the Application Server. This clear date cannot be changed, and it is set to seven days after the meeting ends.
|-
|

Scheduled length
|

Length of time scheduled for the meeting.
|-
|

Actual length
|

Actual meeting length, from when the first meeting participant joined to when the last meeting participant left.
|-
|

Roll call
|

Number of minutes used to record the participant names or locations.
|-
|colspan="2" rowspan="1">|''' Additional Output Fields'''
|-
|

Total for <[[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#User ID|User ID]]>
|

Sums of the following items for the user:
* Scheduled length
* Actual length
* Roll call
|-
|

Number of Meetings
|

Number of meetings in this report that were owned by the user.
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Running Reports and Exporting Data from Cisco Unified MeetingPlace#Running Reports and Exporting Data from Cisco Unified MeetingPlace|Running Reports and Exporting Data from Cisco Unified MeetingPlace]] module

== Migration Import Tool ==

Use this file to migrate user groups, user profiles, and meetings from an existing Cisco Unified MeetingPlace system of a previous release.

To find this page, select '''Maintenance > Migration Import Tool'''.

'''Caution! ''' Once you execute a migration, do not make any changes in the Administration Center until the migration is complete.

===== Table: Field Reference: Migration Import Tool Page =====

{| border = 1
|-
!Field
!Description
|-
|

Data file to use
|

Selects the data migration file.
|-
|

Send log information to
|

Whether to display the migration log information on the screen or save the log information to a file.
|-
|

Error threshold
|

If the number of errors that occur while importing the migration file is greater than this error threshold, the system cancels the import.

Default: 50
|}

== Notification Configuration Page ==

To find this page, select '''System Configuration > Email Notifications > Notification Configuration'''.

===== Table: Field Reference: Notification Configuration Page =====

{| border = 1
|-
!Field
!Description
|-
|

If notification fails retry (times)
|

Default: 3
|-
|

Delay between retries (seconds)
|

Default: 10
|-
|

If still fails wait before trying again (hours)
|

Default: 4
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Email Notifications for Cisco Unified MeetingPlace#Configuring Email Notification Retries|Configuring Email Notification Retries]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring Email Notifications for Cisco Unified MeetingPlace#Configuring Email Notifications for Cisco Unified MeetingPlace|Configuring Email Notifications for Cisco Unified MeetingPlace]] module

== Notification Destinations Page ==

To find this page, select '''Maintenance > SNMP > Notification Destinations'''.

===== Table: Field Reference: Notification Destinations Page=====

{| border = 1
|-
!Field
!Description
|-
|

Destination IP address
|

Select to edit this notification destination.
|-
|

Port number
|

Port number of this notification destination.
|-
|

SNMP version
|

Either SNMP version 1 or version 2c.
|-
|

Community string name
|

Community string associated with this notification destination.
|-
|

Notification type
|

Either trap or inform.
|}

===== Related Topics =====

Topics in the [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SNMP on the Cisco Unified MeetingPlace Application Server#Configuring SNMP on the Cisco Unified MeetingPlace Application Server|Configuring SNMP on the Cisco Unified MeetingPlace Application Server]] module:
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SNMP on the Cisco Unified MeetingPlace Application Server#Adding or Editing SNMP Notification Destinations|Adding or Editing SNMP Notification Destinations]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SNMP on the Cisco Unified MeetingPlace Application Server#Displaying or Deleting SNMP Notification Destinations|Displaying or Deleting SNMP Notification Destinations]]

== Outlook Authentication Configuration Page ==

To find this page, select '''System Configuration > Outlook Authentication Configuration'''.

'''Note: ''' This page appears only when the msft_int license is installed.

Use this page to configure the default authentication method for users who schedule Cisco Unified MeetingPlace meetings from Microsoft Outlook.

If you select the [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook#Single Sign-On|Single Sign-On]] authentication method, these options become available:
* To add a domain, select '''Add New'''.
* To edit an existing entry, select the name of that entry.
* To delete an entry, check the item and select '''Delete Selected'''.

===== Table: Field Reference: Outlook Authentication Configuration Page, Add Outlook Single Sign-On Domain Page, and Edit Outlook Single Sign-On Domain Page =====

{| border = 1
|-
!Field
!Description
|-
|

Outlook Default Authentication method
|

Select between the [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook#Remember Me|Remember Me]] and [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook#Single Sign-On|Single Sign-On]] user authentication options.

Restriction: The [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook#Single Sign-On|Single Sign-On]] option is available only when SSL (1) is enabled on the Application Server.

Default: Remember me
|-
|

Outlook Single Sign-On Domain
|

Specify all domains that are used by your Cisco Unified MeetingPlace for Microsoft Outlook users. Specifically:
* Enter the domains that the client machines are in.
: Note that the client machine domains may differ from the user domains. For example, a user PC may be in domainA.example.com, while the user account is domainB\username. You would enter domainA as an Outlook Single Sign-On Domain.
* For client machines in a workgroup (as opposed to a domain), enter the domain portion of the user email addresses (that is, the part after @) in the Outlook Single Sign-On Domain field.

If you enter any uppercase letters, the system automatically converts them to lowercase letters.

Default: Application Server domain, which was set during installation.
|}

Footnote 1: SSL = Secure Sockets Layer

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook#Configuring the Default Authentication Method for Microsoft Outlook Users|Configuring the Default Authentication Method for Microsoft Outlook Users]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook#Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook|Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook]] module
* [[Cisco Unified MeetingPlace Release 8.0 -- Configuring SSL for the Cisco Unified MeetingPlace Application Server#Configuring SSL for the Cisco Unified MeetingPlace Application Server|Configuring SSL for the Cisco Unified MeetingPlace Application Server]] module

== Outlook Plug-In Configuration Page ==

Use this page to configure which Cisco Unified MeetingPlace servers become available in the client PC Microsoft Outlook options after the plug-in is installed.
* To add a server, select '''Add New'''.
* To edit an existing entry, select the name of that entry.
* To delete an entry, check the item and select '''Delete Selected'''.

To find this page, select '''System Configuration > Outlook Plug-In Configuration'''.

'''Note: ''' This page appears only when the msft_int license is installed.

===== Table: Field Reference: Outlook Plug-In Configuration Page, Add Cisco Unified MeetingPlace Server Page, and Edit Cisco Unified MeetingPlace Server Page =====

{| border = 1
|-
!Field
!Description
|-
|

Make Cisco Unified MeetingPlace form the default appointment form
|

Whether to use the Cisco Unified MeetingPlace scheduling form by default for all new Microsoft Outlook appointments and meetings.

The user can override this setting from Microsoft Outlook by selecting '''Tools''' > '''Options''' and selecting the '''MeetingPlace''' tab.

Default: Yes
|-
|

Name
|

Unique name to appear in the list of available Cisco Unified MeetingPlace systems in the Microsoft Outlook options on the user PC.

Restriction: This field cannot contain any spaces. You can, however, use an underscore character (_), for example, "my_mpx_server."
|-
|

URL
|

URL of the Cisco Unified MeetingPlace server to associate with the entered [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Name|Name]].

If SSL is enabled, be sure that the URL starts with "https" and not "http".

Required format: '''http://'''''hostname'''''/outlook/mpe'''
|}

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook#Adding Cisco Unified MeetingPlace Systems to the Plug-In for Microsoft Outlook|Adding Cisco Unified MeetingPlace Systems to the Plug-In for Microsoft Outlook]] in the [[Cisco Unified MeetingPlace Release 8.0 -- Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook#Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook|Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook]] module

== Port Utilization Report Page ==

Use this page to compare the number of ports scheduled to the number of ports actually used during a specified period of time. This information can help you determine the peak and off-peak times for your system and compare resource usage with available capacity.

To find this page, select '''Reports > Port Utilization Report'''.
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Table: Field Reference: Port Utilization Report Page|Table: Field Reference: Port Utilization Report Page]]
* [[Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace#Output Reference: Port Utilization Report|Output Reference: Port Utilization Report]]

===== Table: Field Reference: Port Utilization Report Page =====

{| border = 1
|-
!Field
!Description
|-
|

Start date
|

The day you want the port utilization report data to begin.

Default: today (mm/dd/yyyy)
|-
|

End date
|

The day you want the port utilization report data to end.

Default: today (mm/dd/yyyy)
|-
|

Start time
|

The hour you want the port utilization report data to begin.

Default: 8:00 AM
|-
|

End time
|

The hour you want the port utilization report data to end.

Default: 5:00 PM
|-
|

Conference type
|

Whether you want report data about voice, web, or video meetings.

Default: Voice
|}

===== Output Reference: Port Utilization Report =====

The port utilization report output is a chart that shows this information:
* Date and times represented by the report.
* Number of licensed ports on the system for the selected conference type.
* (Red data) Percentage of licensed ports that were ''scheduled'' for meetings of the selected conference type.
* (Blue data) Percentage of licensed ports that were actually ''used'' to attend meetings of the selected conference type.

===== Related Topics =====
* [[Cisco Unified MeetingPlace Release 8.0 -- Running Reports and Exporting Data from Cisco Unified MeetingPlace#Running Reports and Exporting Data from Cisco Unified MeetingPlace|Running Reports and Exporting Data from Cisco Unified MeetingPlace]] module

[[Category: Reference Information for Cisco Unified MeetingPlace Release 8.0]]

Cisco Unified MeetingPlace Release 8.0 -- Administration Center Page References for Cisco Unified MeetingPlace (M - P pages) - Revision history

Annekim: /* Table: Field Reference: Meeting Configuration Page */ updated for CSCts50536

Cgriffen: /* Table: Field Reference and Output Field Reference: Meeting Information Report Page */

Bobbmart: /* Output Reference: Port Utilization Report */

MeetingPlace Moderator: 1 revision

MeetingPlace Moderator at 21:23, 30 June 2010

← Older revision		Revision as of 18:40, 15 September 2011
Line 1,814:		Line 1,814:


-	Meeting ID end guard times are not applied to reservationless meetings or meetings that are user-terminated before the scheduled end time.	+	'''Note:''' Meeting ID end guard times are not applied to reservationless meetings, meetings that are user-terminated before the scheduled end time, or meetings that end automatically due to non-attendance. In such instances, the meeting ID is available immediately for reuse.


Line 2,053:		Line 2,053:
	Default: 4		Default: 4
	\|}		\|}
-
-
-

	===== Related Topics =====		===== Related Topics =====

← Older revision		Revision as of 21:42, 18 July 2011
Line 2,156:		Line 2,156:
	\|		\|

-	Actual meeting length, from when the first meeting participant joined to when the last meeting participant left.	+	Actual meeting length, from when the first meeting participant joined to when the last meeting participant left. If the meeting is not attended, the length is 1+ the disconnect empty port (minutes).
	\|-		\|-
	\|		\|
Line 2,184:		Line 2,184:
	Number of meetings in this report that were owned by the user.		Number of meetings in this report that were owned by the user.
	\|}		\|}
-
-
-

	===== Related Topics =====		===== Related Topics =====

← Older revision		Revision as of 15:24, 8 October 2010
Line 2,559:		Line 2,559:
	* (Red data) Percentage of licensed ports that were ''scheduled'' for meetings of the selected conference type.		* (Red data) Percentage of licensed ports that were ''scheduled'' for meetings of the selected conference type.
	* (Blue data) Percentage of licensed ports that were actually ''used'' to attend meetings of the selected conference type.		* (Blue data) Percentage of licensed ports that were actually ''used'' to attend meetings of the selected conference type.
-		+	* Percent of conference is calculated each minute.

	===== Related Topics =====		===== Related Topics =====