Conferencing

This topic describes conferencing in general.

Conferencing is used if there are more than two participants:

  • Multipoint meeting is a conference
  • Most often just video terminals (endpoints)
  • Also used in other use cases, for example, call recording
  • Different visual experiences such as Cisco ActivePresence, advanced continuous presence, voice-switched
  • Different conference types such as ad hoc, scheduled, and rendezvous

Conferencing occurs when more than two participants join a meeting with a voice or video device. The challenge is to have a consistent user experience in voice or video conferences and to select the correct conference resource, depending on the device, especially when mixing standard-definition and high-definition video devices.

The Cisco focus for the future is Cisco ActivePresence using Cisco TelePresence Server instead of multipoint control units with many different layouts.

Ad hoc conferences are impromptu meetings. They are not scheduled and do not require an administrator to initiate them. Ad hoc conferences are suitable for smaller, on-the-fly meetings. A point-to-point call that is escalated to a multipoint call is considered an ad hoc conference.

Rendezvous conferences are also called Meet-Me, permanent, or static conferences. These conferences require that endpoints dial into a predetermined number and are often used for recurring group meetings that involve different endpoints each time.

Scheduled conferences provide a guarantee that endpoints and multipoint resources will be available at a certain time. Endpoints join manually or are automatically connected by the multipoint resource.

Continuous Presence Layouts

  • More than 50 layouts, depending on the MCU

Cisco ActivePresence

  • Up to 9 ActivePresence windows per screen

The Cisco TelePresence MCU 5300 Series, for example, offers more than 50 layouts for continuous presence. All ports on this multipoint control unit also support advanced continuous presence.

The future trend is active presence supported by Cisco TelePresence Server. Cisco ActivePresence capability supports a full-screen immersive view of the primary speaker with an overlay of others who are participating in the call. ActivePresence is designed to maximize the large-scale immersive experience and is available on all ports of the Cisco TelePresence Server. The server interworks with Polycom RPX and TPX telepresence systems while preserving the full Cisco ActivePresence view. Four layout families are provided for single-screen endpoints, including panel-switched Cisco ActivePresence capability.

Up to 9 ActivePresence windows are supported on a single screen at one time. In a triple-screen system, a total of 27 ActivePresence windows are supported.

Cisco Jabber Account Options

This topic describes the phone account options that Cisco Jabber presents if the service profile is configured.

Configure the Cisco Jabber options:

  • The phone accounts appear only if the user has certain Cisco Unified Communications Services configured—for example, a voicemail UC Service in the configured service profile.
  • Voicemail and conferencing profiles can share the user credentials.
  • Calendar integration can also be configured.

A Cisco Jabber option Account—for example, for voice messaging—appears only if the corresponding UC Service is configured. The Cisco Jabber menus are dynamic and show only account options for which a UC service is configured.

End users must provide the credentials in Cisco Jabber for the account that they are configuring—for example, voicemail or conferencing. In the example in the figure, a voicemail service was configured. The user must enter the Cisco Unity Connection local password if the voicemail service is imported from Cisco Unified Communications Manager and the LDAP credentials if the voicemail service is imported from the LDAP server.

For voicemail and conferencing, you can set the Credentials Source parameter so that the voicemail service can share user credentials with other services. If you want to share the voicemail service user credentials with another service, select the appropriate service from the Credentials Source list. The user credentials are automatically synchronized with the services that you select. The credentials can be entered for voicemail, conferencing, and LDAP. Other profiles are transparent to end users. In addition, the user can configure calendar integration.

Cisco Jabber in Phone-Only and Softphone Modes

This topic describes how to set up Cisco Jabber for phone-only mode without a Cisco Unified Communications IM and Presence Service node.

  • Configure Cisco Jabber in phone-only mode:
    1. Cisco Unified Communications IM and Presence Service node is not required.
    2. Presence and IM features are not available.
  • Checklist for phone-only mode configuration:
    1. Add a new end user, and do not enable presence.
    2. Add a new Cisco Unified CSF device; set the mandatory parameters and the owner ID.
    3. Add the DN, the route partition, and other mandatory settings.
  • Install Cisco Jabber:
    1. Set the account type to Automatic.
    2. Log in with the UserPrincipalName to discover the service domain.
  • The following are not available in phone-only mode:
    1. Desk phone control is not available.
    2. There is no LDAP server connection available for contact search.
    Note

    CSF = Client Services Framework

The figure lists the steps that are required to set up Cisco Jabber in phone-only mode. Cisco Jabber registers with Cisco Unified Communications Manager using SIP. In phone-only mode, features like IM, presence, and directory access are not available.

Follow the configuration checklist to set up Cisco Jabber in phone-only mode.

Note

Do not enable presence for users or devices in phone-only mode.

Configure Cisco Jabber in Softphone Mode

This topic describes how to configure Cisco Jabber to run in softphone mode.

Cisco Jabber in softphone mode must be configured on Cisco Unified Communications Manager:

  • Configure the end user.
    1. Create and associate the new Cisco Unified CSF device.
    2. Set the primary extension.
    3. Enable User for Unified CM IM and Presence.
  • Add a new device.
    1. Add a Cisco Unified CSF device.
    2. Name has no restrictions, so you do not have to use CSFNAME.
    3. Add the user as owner of the device, and set the primary phone.
    4. Add the DN, and associate a user with the line.
    5. Device will register with Cisco Unified Communications Manager using SIP.
  • Add Legacy Client Configuration (TFTP and CCMCIP profile).
  • Configure UC Profiles and Service Profile for presence functionality.

In Cisco Unified Communications Manager Administration, create a Cisco Unified Client Services Framework (CSF) device. This device is used by Cisco Jabber in softphone and deskphone mode. For deskphone mode, additional CTI configuration is required. The main difference is the registration. In softphone mode, Cisco Jabber registers with Cisco Unified Communications Manager using SIP. In deskphone mode, Cisco Jabber registers with Cisco Unified Communications IM and Presence using XMPP and controls the desk phone via CTIQBE.

Follow the checklist that is presented in the figure to set up a Cisco Unified CSF device for Cisco Jabber in softphone mode.

When the Cisco Unified CSF device is created, add the DN of the phone or device profile of the user to the new device. The DN is a shared line, and the devices that are sharing this number are listed under associated devices. After saving, associate the end user with the line by clicking the Associate End Users button. This action is important, because the presence status is shown per line, not per device status.

Next, associate the Cisco Unified CSF device with the end user. When the Cisco Unified CSF device is successfully created, associate the device to the end user configuration. Choose User Management > End User, and select the user. Click Device Association, search for the previously created Cisco Unified CSF device, and click Add Selected. The device is now displayed in the Controlled Devices list. After the association is done, the primary line can be selected.