Cisco Unified MeetingPlace, Release 7.0 -- About RSNA

From DocWiki

Revision as of 23:22, 1 February 2010 by Jmcmulle (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Main page: Cisco Unified MeetingPlace, Release 7.0

Up one level: Configuration



Contents

RSNA

The Reservationless Single Number Access (RSNA) feature allows multiple Cisco Unified MeetingPlace systems to appear as one system to the user community. Any user who hosts (as a profiled user) or attends (as a profiled user or as a guest) a reservationless meeting can join the meeting by dialing the access phone number of the Cisco Unified MeetingPlace system that is local to that user, regardless of which system is hosting the meeting. Users are then redirected to the system that is hosting the meeting.


RSNA Reserved Meeting Server

The RSNA Reserved Meeting Server feature allows a single Application Server to host reserved meetings within an RSNA-based network. Typically, all meeting reservations are on the one designated Reserved Meeting Server. When users attend meetings by accessing their local server, if their local server does not recognize the meeting ID, it transfers the user to the Reserved Meeting Server.


Note: The server times must be synchronized between the local Application Server and the Reserved Meeting Server.


The local server attempts to transfer calls to the Reserved Meeting Server if all of the following conditions are true:

  • The Reserved Meeting Server feature has been configured on the local server:
    The local server must be configured with a remote server record in which the Reserved Meeting Server check box is checked.
    If you want any user profiles to identify the remote Reserved Meeting Server as the Schedule home server, then create a duplicate remote server record in which you do the following:
    • Do NOT check the Reserved Meeting Server check box.
    • Enter a Home Server number in the range 0 to 999.
    • Make sure that all other fields are identical between the duplicate records for the Reserved Meeting Server.
  • The meeting ID that the user entered does not match the meeting ID of any meetings scheduled around that time on the local server.
  • The meeting ID that the user entered does not match any user profile, active or not.
  • The user confirms the meeting ID.


In addition, consider the following behavior of the RSNA Reserved Meeting Server feature:

  • This feature does not prevent meetings from being scheduled locally and will not warn or transfer a user who attempts to schedule a meeting locally.
  • If a meeting is scheduled on a server other than the Reserved Meeting Server, this feature will not facilitate attendance of that meeting.
  • A locally scheduled meeting always takes precedence over a remote one. This rule applies even if a local meeting recently ended and the user hears that meeting is over.
  • If the meeting does not exist on the remote system, the system prompts the user for a meeting ID after the transfer.
  • Users choose which server to schedule the meeting on from the Server drop-down box on the Scheduling page. To restrict users from choosing a server other than the Reserved Meeting Server, you may need to disable the Server drop-down box from the scheduling page. This restriction does not apply if the user dials into a local server and uses the TUI to schedule the meeting. In that case the meeting will be scheduled on a local server


Restriction

Meeting recordings are stored only on the Web Server that is associated with the Schedule home server for the meeting owner. To access meeting recordings, the users must know the URL of the Web Server that you assigned to the meeting owner.


Related Topics

Rating: 0.0/5 (0 votes cast)

Personal tools