Cisco Unified MeetingPlace Release 8.0 -- Choosing an Audio Without Video Deployment for Cisco Unified MeetingPlace Release 8.0

From DocWiki

Revision as of 22:41, 15 March 2010 by MeetingPlace Moderator (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Main page: Cisco Unified MeetingPlace, Release 8.0

Up one level: Planning Your Deployment


This chapter discusses design considerations and recommendations for Cisco Unified MeetingPlace Release 8.0 deployments that do not include video. These deployments may or may not include a web component. If you want to use video in your deployment, see Choosing an Audio and Video Deployment for Cisco Unified MeetingPlace Release 8.0.


This chapter does not include a comprehensive list of all possible audio without video deployments but instead describes common scenarios.


Contents

About Audio Without Video Deployments

All Cisco Unified MeetingPlace Release 8.0 systems require Cisco Unified Communications Manager and all Cisco Unified MeetingPlace Release 8.0 systems automatically ship with Cisco Unified Communications Manager Release 8.0. For audio without video deployments, the minimum release of Cisco Unified Communications Manager that we support is Release 6.0.1.x.


Cisco Unified MeetingPlace Release 8.0 has two audio without video deployment options and both use Cisco Unified Communications Manager to support MGCP (Media Gateway Control Protocol), H.323, SCCP, and SIP gateways. Note that Cisco Unified MeetingPlace Release 8.0 interoperates with all third-party, standards-based IP PBXs; however, only deployments with Cisco Unified Communications Manager have been tested.


Related Topics


Determining which Audio Without Video Deployment to Use

Use the following table to determine which audio without video deployment to use for your system.

Feature Option 1: Using Cisco Unified Communications Manager Release 6.1.4.39 or Later Option 2: Using Cisco Unified Communications Manager Release 6.0.1.x or Release 6.0.2.x

Directory synchronization

X

 

Can use any endpoints

X

 

Seamless integration with Cisco Unified MeetingPlace

X

 

Already have Cisco Unified Communications Manager Release 6.0.1.x or Release 6.0.2.x and do not want to upgrade

 

X



Audio Without Video Deployment Option 1: Using Cisco Unified Communications Manager Release 6.1.4.39 or Later

Note: This deployment refers to the following releases of Cisco Unified Communications Manager:

  • 6.1.4.39 and later
  • 7.1.3.x
  • 8.0


Cisco Unified Communications Manager Release 8.0 is the preferred deployment choice in all cases for both audio-only and audio-video. It is required if you want directory synchronization. Using Cisco Unified Communications Manager Release 8.0 does not limit your endpoint choices in any way. Video terminals may connect to Cisco Unified MeetingPlace; however, the connection is audio only.


The following is the call path for this deployment option:

  1. SIP or SCCP (voice or video) endpoint
  2. Cisco Unified Communications Manager Release 6.1.4.39 or later
  3. SIP trunk
  4. Cisco Unified MeetingPlace


Example 1
  1. Phone
  2. PSTN
  3. IOS gateway
  4. Cisco Unified Communications Manager Release 7.x
  5. Cisco Unified MeetingPlace


Example 2
  1. Phone
  2. IOS gatekeeper
  3. Cisco Unified Communications Manager Release 8.x
  4. Cisco Unified MeetingPlace


Audio Without Video Deployment Option 2: Using Cisco Unified Communications Manager Release 6.0.1.x or Release 6.0.2.x

Choose this deployment option if you use Cisco Unified Communications Manager Release 6.0.1.x or Release 6.0.2.x and you do not want to upgrade to a newer release.


For systems that already use Cisco Unified Communications Manager Release 6.0.1.x or Release 6.0.2.x, we recommend putting a Cisco Unified Communications Manager Release 6.1.4.39 or later cluster in between the older release of Cisco Unified Communications Manager and Cisco Unified MeetingPlace.


The call path is shown below.

  1. SIP endpoint
  2. Cisco Unified Communications Manager Release 6.0.1.x or Release 6.0.2.x
  3. SIP gateway
  4. Cisco Unified MeetingPlace


Example 1
  1. SIP endpoint
  2. Cisco Unified Communications Manager Release 6.0.1.x or Release 6.0.2.x
  3. SIP trunk
  4. Cisco Unified Communications Manager Release 8.x
  5. SIP gateway
  6. Cisco Unified MeetingPlace


Example 2
  1. SIP endpoint
  2. Cisco Unified Communications Manager Release 6.0.1.x or Release 6.0.2.x
  3. H.323 trunk
  4. Cisco Unified Communications Manager Release 8.x
  5. SIP gateway
  6. Cisco Unified MeetingPlace


Example 3
  1. SIP endpoint
  2. Cisco Unified Communications Manager Release 6.0.1.x or Release 6.0.2.x
  3. SIP trunk
  4. Cisco Unified Communications Manager Release 7.x
  5. SIP trunk
  6. Cisco Unified MeetingPlace


Example 4
  1. SIP endpoint
  2. Cisco Unified Communications Manager Release 6.0.1.x or Release 6.0.2.x
  3. H.323 trunk
  4. Cisco Unified Communications Manager Release 7.x
  5. SIP trunk
  6. Cisco Unified MeetingPlace


Reservationless Single Number Access (RSNA) Deployment

In addition to the two audio without video deployments listed earlier in this chapter (Audio Without Video Deployment Option 1: Using Cisco Unified Communications Manager Release 6.1.4.39 or Later and Audio Without Video Deployment Option 2: Using Cisco Unified Communications Manager Release 6.0.1.x or Release 6.0.2.x), you can also configure your system for RSNA. You can deploy RSNA with either of the audio without video deployments.


About RSNA

The Reservationless Single Number Access (RSNA) feature allows two 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.


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


All reservationless meetings are owned by a user and the meeting ID matches the PIN of that user. You can identify the owner of a meeting by looking up the meeting ID in the user profile database table. A reservationless meeting owned by a particular user will always be hosted on the server listed as the scheduling home server in the user's profile. You can identify the server that hosts a meeting by looking up the meeting ID in the user profile database table.


Restrictions for RSNA

  • Only two RSNA systems (sites) are currently supported.
    • Both RSNA systems must have the same value for the System media mode parameter; for example, they must both be set either to software mode or to hardware mode.
    • Both RSNA systems must use the same type of connectivity; for example, with connectivity through Cisco Unified Communications Manager or through Cisco Unified Border Element (CUBE) connected node.
  • Ad-hoc conferencing is not supported with RSNA.
  • RSNA is not supported with web conferencing integrations (Cisco WebEx and IBM Lotus Sametime).
  • The server times must be synchronized between the local Application Server and the Reserved Meeting Server.


Prerequisities for RSNA

All systems that are part of an RSNA deployment must have copies of all user profiles, which is accomplished through automatic database replication. Therefore, database replication must be set up between the systems. In addition, communication between the systems must not be blocked by a firewall and you must have a minimum of bandwidth 250Kbps available.


The call transfer between systems uses the SIP REFER method. This method passes the call back to the connected communications server, such as Cisco Unified Communications Manager, which then redirects the call to the other system. The communications server must have SIP connectivity to the other system. The SIP REFER method cannot operate across H.323 trunks.


Related Topics

For information on configuring your system for RSNA, see the online help in the administrator interface or the Configuration Guide for Cisco Unified MeetingPlace Release 8.0 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.

Rating: 0.0/5 (0 votes cast)

Personal tools