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.

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

Field

Description

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

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.

Echo Canceller (*4) (this section is available only when the 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.

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

Gain Control (*5) (this section is available when the 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.

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.

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.

Jitter Buffer (this section is not available when the 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

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.

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.

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 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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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 (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.

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.

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.

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."

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.

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 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 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

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.

Meeting Information Report Page

This report provides information about meetings that occur in the specified date range. The output is grouped by User ID of the meeting owner. To find this page, select Reports > Meeting Information Report.

Restriction: The 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.

Related Topics

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.