- Configure Clusterwide Call Park
- Configure a Partition for Call Park
- Configure a Call Park Number
- Call Park Configuration Fields
- Configure Call Pickup Group
- Assign Directory Number
- Configure Other Call Pickup
- Configure Directed Call Pickup
- Auto Call Pickup
- Configure Auto Call Pickup
- Set Up Cisco Unified Communications Manager to Support Dial via Office
- Set Up Enterprise Feature Access Number
- Set Up Mobility Profile
- Verify Device COP File Version
- Add Mobility Identity
- Enable Dial via Office on Each Device
- Line Group
- Configure Line Group
- Configure Hunt List
- Add Line Group to Hunt List
- Configure Hunt Pilot
- Jabber to Jabber Hybrid Mode
- Jabber to Jabber Bandwidth
- Configure a Device with No Voicemail
- Enable Handoff from VoIP to Mobile Network
- Set Up Handoff DN
- Match Caller ID with Mobility Identity
- Set Up User and Device Settings for Handoff
- Configure Multiline
- Enable Multiline MRA Access
- Enable Push Notification Service on Cisco Unified Communications Manager
- Enable Single Number Reach
- Limitations
- Associate URIs to Directory Numbers
- Automatically Populate Directory Numbers with URIs
- Configure Directory Numbers with URIs
- Set Up Timer-Controlled Voicemail Avoidance
- Set Up User-Controlled Voicemail Avoidance
- Set Up Cisco Unified Communications Manager to Support Voicemail Avoidance
- Enable Voicemail Avoidance on Mobility Identity
- Enable Voicemail Avoidance on Remote Destination
Voice and Video
Meeting Controls for CMS Meetings
Applies to: All clients
Jabber provides meeting control functions through the Cisco Meeting Server (CMS) ActiveControl feature. The meeting control functions include participant lists, muting participants, dropping participants, and changing the video layout.
To use ActiveControl requires the following in your deployment:
- The call path between the endpoint and Meeting Server supports iX media end to end.
- Appropriate permissions enabled in Meeting Server.
As of Release 12.5, Jabber can access Cisco Meeting Server conferences as a SIP device through ActiveControl. You can enter an ActiveControl conference by either:
- Dialing into a room that is configured on CMS
- Merging two calls when a CMS room is configured as the conference bridge
Before you begin
To set up ActiveControl, you need:
- Cisco Meeting Server Release 2.3 or later
- Cisco Unified Communications Manager 12.5.1.11900 or later
- Cisco Expressway for Mobile and Remote Access X12.5.1 or later (Optional if Jabber is in your corporate network, not using MRA)
These are the releases with full support for ActiveControl. Earlier releases of Unified CM and Expressway did not support the control functions over Expressway.
Procedure
Configure a SIP trunk in Cisco Unified Communications Manager with CMS to enable communication using SIP signals. For more information, see System Configuration Guide for Cisco Unified Communications Manager.
Configure a route pattern in Cisco Unified Communications Manager to route inbound and outbound SIP calls. For more information, see the Configure Call Routing chapter in System Configuration Guide for Cisco Unified Communications Manager.
Set up rules in CMS for outbound SIP call routing to the Cisco Unified Communications Manager server. For more information, see the Cisco Meeting Server with Cisco Unified Communications Manager Deployment Guide.
Configure your CMS space to manage your conference resources. For more information, see Cisco Meeting Server Release API Reference Guide.
Bridge Escalations
Applies to: All clients
Bridge escalations allow users to quickly escalate a group chat to a conference call. Participants are automatically added without the need to merge them into the conference call.
Procedure
Enable bridge escalations in Cisco Jabber clients by setting the EnableBridgeConferencing parameter to true in the jabber-config.xml file.
(Optional) Specify a mask for the room URI in the UserBridgeUriAdmin parameter in the jabber-config.xml file. If you don't specify a mask the user can enter a DN or a SIP URI in the client.
Enable URI dialing to allow your users enter a SIP URI for the conference call number. For more information on URI dialing, see the URI Dialing topic.
Call Park
Applies to: Cisco Jabber for Android, Cisco Jabber for iPhone and iPad
You can use call park to place a call on hold and pick it up from another phone in a Cisco Unified Communications Manager system. Call park must be enabled and extension numbers must be defined on each Cisco Unified Communications Manager node in the cluster. You can define either a single directory number or a range of directory numbers for use as call park extension numbers.
Complete the following tasks to enable call park. For detailed instructions, see the Feature Configuration Guide for Cisco Unified Communications Manager .
Procedure
Configure cluster wide call park
Configure a partition
Create a partition to add a call park number.
Configure a call park number
Configure a call park number to use call park across nodes in a cluster.
You can define either a single directory number or a range of directory numbers for use as call park extension numbers. You can park only one call at each call park extension number.
Configure Clusterwide Call Park
Procedure
Choose System > Service Parameters .
Select the desired node as Server and the service as Cisco CallManager (active).
Click the Advanced .
The advanced service parameters are displayed in the window.
In Clusterwide Parameter(Feature- General) section set the Enable cluster-wide Call Park Number/Ranges to True .
The default value is False. This parameter determines whether the Call Park feature is implemented clusterwide or restricted to a specific Unified CM node.
Set the Call Park Display Timer for each server in a cluster that has the Cisco CallManager service and Call Park configured.
The default is 10 seconds. This parameter determines how long a Call Park number displays on the phone that parked the call.
Set the Call Park Reversion Timer for each server in a cluster that has the service and Call Park configured.
The default is 60 seconds. This parameter determines the time that a call remains parked. When this timer expires, the parked call returns to the device that parked the call. If a hunt group member parks a call that comes through a hunt pilot, the call goes back to the hunt pilot when the Call Park Reversion Timer expires.
If you enter a Call Park Reversion Timer value that is less than the Call Park Display Timer, Call Park numbers may not display on the phone.
Restart all and CTI Manager services.
Configure a Partition for Call Park
Configure partitions to create a logical grouping of directory numbers (DNs) and route patterns with similar reachability characteristics. Partitions facilitate call routing by dividing the route plan into logical subsets that are based on organization, location, and call type. You can configure multiple partitions.
Procedure
From Cisco Unified CM Administration, choose Call Routing > Class of Control > Partition .
Click Add New to create a new partition.
In the Partition Name, Description field, enter a name for the partition that is unique to the route plan.
Enter a comma (,) after the partition name and enter a description of the partition on the same line.
To create multiple partitions, use one line for each partition entry.
From the Time Schedule drop-down list, choose a time schedule to associate with this partition.
Select one of the following radio buttons to configure the Time Zone :
- Originating Device —When you select this radio button, the system compares the time zone of the calling device to the Time Schedule to determine whether the partition is available is available to receive an incoming call.
- Specific Time Zone —After you select this radio button, choose a time zone from the drop-down list. The system compares the chosen time zone to the Time Schedule to determine whether the partition is available is available to receive an incoming call.
Configure a Call Park Number
If you want to use Call Park across servers in a cluster, you must configure Call Park extension numbers on each server.
Ensure that each Call Park directory number, partition, and range is unique within the . Each to which devices are registered requires its own unique Call Park directory number and range. does not validate the Call Park numbers or range that you use to configure Call Park. To help identify invalid numbers or ranges and potential range overlaps, use the Dialed Number Analyzer tool.
Procedure
Choose Call Routing > Call Park .
Perform one of the following tasks:
- To add a new Call Park number, click Add New .
- To copy a Call Park number, find the Call Park number or range of numbers and then click the Copy icon.
- To update a Call Park number, find the Call Park number or range of numbers.
Configure the fields in the Call Park configuration fields. See Call Park Configuration Fields for more information about the fields and their configuration options.
To save the new or changed Call Park numbers in the database, click Save.
Call Park Configuration Fields
Call Park Number/Range
Enter the Call Park extension number. You can enter digits or the wildcard character X (the system allows one or two Xs). For example, enter 5555 to define a single Call Park extension number of 5555 or enter 55XX to define a range of Call Park extension numbers from 5500 to 5599.
You can create a maximum of 100 Call Park numbers with one call park range definition. Make sure that the call park numbers are unique.
You cannot overlap call park numbers between servers. Ensure that each server has its own number range.
The call park range is selected from the list of servers where the call originates. For example, if phone A (registered to node A) calls phone B (registered to node B) and the phone B user presses Park, phone B requires a call park range in the CSS that resides on node A. In a multinode environment where phones and gateways communicate with various nodes and where calls that originate from any server may need to be parked, the phones require a CSS that contains call park ranges from all servers.
Provide a brief description of this call park number. The description can include up to 50 characters in any language, but it cannot include double-quotes (“), percentage sign (%), ampersand (&), or angle brackets (<>).
If you want to use a partition to restrict access to the call park numbers, choose the desired partition from the drop-down list. If you do not want to restrict access to the call park numbers, choose for the partition.
Make sure that the combination of call park extension number and partition is unique within the .
Using the drop-down list, choose the Cisco Unified Communications Manager to which these call park numbers apply.
Call Pickup
Applies to: Cisco Jabber for Windows, Cisco Jabber for Mac, Cisco Jabber Softphone for VDI
The Call Pickup feature allows users to answer calls that come in on a directory number other than their own. Call pickup groups have assigned directory numbers. Cisco Unified Communications Manager (Unified CM) automatically dials the appropriate call pickup group number. Users select Pickup to answer the call.
Group call pickup This setting allows users to pick up incoming calls in another group. Users enter the group pickup number, select Pickup , and Unified CM automatically dials the appropriate call pickup group number. The user can then pick up an available call in that group. Other group pickup This setting allows users to pick up incoming calls in a group that is associated with their group. When the user selects Other Pickup , Unified CM automatically searches for the incoming call in the associated groups and connects the call. Directed call pickup This setting allows users to pick up an incoming call on a directory number. Users enter the directory number, select Pickup and Unified CM connects the incoming call.
To enable call pickup, you use these parameters in the jabber-config.xml file, depending on the types of call pickup that you support:
true true true true For more information about configuring call pickup, see the Feature Configuration Guide for Cisco Unified Communications Manager .
Call Pickup Notifications
For multiple incoming calls, a notification, Call(s) available for pickup , appears. When the user answers a call, the user gets connected to the longest ringing call.
Desk Phone Mode
In desk phone mode, the following limitations apply:
- The Unified CM notification settings aren’t supported for the pickup group. The call pickup notification that displays is CallerA -> CallerB .
- The Unified CM settings for audio and visual settings aren’t supported. The visual alerts always appear.
Shared Line Behavior
For users that have a desk phone and also audio on computer with a shared line, the following limitations apply:
- For an attempt to pick up a call using the client when no call is available, No call available for PickUp displays on the desk phone.
- For an attempt to pick up a call using the desk phone when no call is available, No call available for PickUp displays on the client.
User Not a Member of an Associated Group
For an incoming call to another pickup group where the user isn’t a member of an associated group:
- You can use directed call pickup to pick up the incoming call.
- Group pickup doesn’t work.
Expected Behavior Using Group Call Pickup and Directed Call Pickup
The following are expected behaviors when using group call pickup and directed call pickup:
- If you enter an invalid number:
- Audio on computer mode—The conversation window appears and the user hears the annunciator immediately.
- Desk phone mode—The conversation window, fast busy tone, or the annunciator occurs followed by the fast busy tone, Pickup failed error message.
- Audio on computer mode—Tone in the headset, no conversation window appears, and No call available for pickup error message.
- Desk phone mode—No conversation window and No call available for pickup error message
- Audio on computer mode—Tone in the headset, no conversation window appears, and No call available for pickup error message.
- Desk phone mode—No conversation window and No call available for pickup error message
- Audio on computer mode—The conversation window appears and fast busy tone.
- Desk phone mode—The conversation window appears, fast busy tone, and Pickup failed error message.
- Audio on computer mode—Tone in the headset, conversation window appears, and, after 15 seconds, the annunciator followed by the fast busy tone.
- Desk phone mode—The conversation window appears, after 15 seconds, the annunciator, fast busy tone, and Pickup failed error message.
Call Pickup Using a Desk Phone That Isn’t in a Call Pickup Group
If a user attempts a call pickup from a desk phone that isn’t in a call pickup group, the conversation window appears for a moment. Don’t configure users to use the call pickup feature if they aren’t members of a call pickup group.
Original Recipient Information Not Available
When the Unified CM Auto Call Pickup Enabled setting is true, the recipient information isn’t available in the client when the call is picked up in audio-on-computer mode. If the setting is false, the recipient information is available.
Configure Call Pickup Group
Call pickup groups allow users to pick up incoming calls in their own group.
Procedure
Open the Cisco Unified Communication Manager interface.
Select Call Routing > Call Pickup Group
The Find and List Call Pickup Groups window opens.
The Call Pickup Group Configuration window opens.
Enter call pickup group information:
- Specify a unique name for the call pickup group.
- Specify a unique directory number for the call pickup group number.
- Enter a description.
- Select a partition.
(Optional) Configure the audio or visual notification in the Call Pickup Group Notification Settings section.
- Select the notification policy.
- Specify the notification timer.
For further information on call pickup group notification settings see the call pickup topics in the relevant Cisco Unified Communications Manager documentation.
What to do next
Assign a call pickup group to directory numbers.
Assign Directory Number
Assign a call pickup group to a directory number. Only directory numbers that are assigned to a call pickup group can use call pickup, group call pickup, other group pickup, and directed call pickup.
Before you begin
Before you assign a call pickup group to a directory number, you must create the call pickup group.
Procedure
Open the Cisco Unified Communications Manager Administration interface.
Assign a call pickup group to a directory number using one of the following methods:
- Select Call Routing > Directory Number , find and select your directory number and in the Call Forward and Call Pickup Settings area select the call pickup group from the call pickup group drop down list.
- Select Device > Phone , find and select your phone and in the Association Information list choose the directory number to which the call pickup group will be assigned.
To save the changes in the database, select Save .
Configure Other Call Pickup
Other Group Pickup allows users to pick up incoming calls in an associated group. Cisco Unified Communications Manager automatically searches for the incoming call in the associated groups to make the call connection when the user selects Other Pickup .
Before you begin
Before you begin, configure call pickup groups.
Procedure
Open the Cisco Unified Communication Manager Administration interface.
Select Call Routing > Call Pickup Group
The Find and List Call Pickup Groups window opens.
Select your call pickup group.
The Call Pickup Group Configuration window opens.
In the Associated Call Pickup Group Information section, you can do the following:
- Find call pickup groups and add to current associated call pickup groups.
- Reorder associated call pickup groups or remove call pickup groups.
Configure Directed Call Pickup
Directed call pickup allows you to pick up a incoming call directly. The user enters the directory number in the client and selects Pickup . Cisco Unified Communications Manager uses the associated group mechanism to control if the user can pick up an incoming call using Directed Call Pickup.
To enable directed call pickup, the associated groups of the user must contain the pickup group to which the directory number belongs.
When the user invokes the feature and enters a directory number to pick up an incoming call, the user connects to the call that is incoming to the specified phone whether or not the call is the longest incoming call in the call pickup group to which the directory number belongs.
Procedure
Configure call pickup groups and add associated groups. The associated groups list can include up to 10 groups.
For more information, see topics related to defining a pickup group for Other Group Pickup.
Enable the Auto Call Pickup Enabled service parameter to automatically answer calls for directed call pickups.
For more information, see topics related to configuring Auto Call Pickup.
Auto Call Pickup
You can automate call pickup, group pickup, other group pickup, and directed call pickup by enabling the Auto Call Pickup Enabled service parameter. When this parameter is enabled, Cisco Unified Communications Manager automatically connects users to the incoming call in their own pickup group, in another pickup group, or a pickup group that is associated with their own group after users select the appropriate pickup on the phone. This action requires only one keystroke.
Auto call pickup connects the user to an incoming call in the group of the user. When the user selects Pickup on the client, Cisco Unified Communications Manager locates the incoming call in the group and completes the call connection. If automation is not enabled, the user must select Pickup and answer the call, to make the call connection.
Auto group call pickup connects the user to an incoming call in another pickup group. The user enters the group number of another pickup group and selects Pickup on the client. Upon receiving the pickup group number, Cisco Unified Communications Manager completes the call connection. If auto group call pickup is not enabled, dial the group number of another pickup group, select Pickup on the client, and answer the call to make the connection.
Auto other group pickup connects the user to an incoming call in a group that is associated with the group of the user. The user selects Other Pickup on the client. Cisco Unified Communications Manager automatically searches for the incoming call in the associated groups in the sequence that the administrator enters in the Call Pickup Group Configuration window and completes the call connection after the call is found. If automation is not enabled, the user must select Other Pickup , and answer the call to make the call connection.
Auto directed call pickup connects the user to an incoming call in a group that is associated with the group of the user. The user enters the directory number of the ringing phone and selects Pickup on the client. Upon receiving the directory number, Cisco Unified Communications Manager completes the call connection. If auto directed call pickup is not enabled, the user must dial the directory number of the ringing phone, select Pickup , and answer the call that will now ring on the user phone to make the connection.
For more information about Call Pickup , see the Feature Configuration Guide for Cisco Unified Communications Manager .
Configure Auto Call Pickup
Procedure
Open the Cisco Unified CM Administration interface.
Select System > Service Parameters
Select your server from the Server drop down list and then select the Cisco Call Manager service from the Service drop down list.
In the Clusterwide Parameters (Feature - Call Pickup) section, select one of the following for Auto Call Pickup Enabled :
- true—The auto call pickup feature is enabled.
- false—The auto call pickup feature is not enabled. This is the default value.
Meeting Control for CMR Meetings
Applies to: All clients
Cisco Collaboration Meeting Rooms (CMR) Cloud provides easy access for users to join or start a Cisco Webex meeting. Cisco Jabber provides users with the ability to access the meeting either using Cisco Webex interface or join using video.
There is a limitation on CMR Cloud join experience for attendees of scheduled CMR Cloud meetings. This limitation impacts Mac users and Windows users who have not enabled Outlook calendar integration. Due to a server limitation, attendees for these deployment scenarios will only receive the option to join the meeting using Cisco Webex. Hosts will enjoy the full experience, as will anyone invited to join ad hoc CMR Cloud meetings.
Users who are in CTI control mode will only be able to join using Webex.
Before you begin
Cisco Collaboration Meeting Rooms Cloud is available on Cisco Webex Meetings.
Procedure
Configure the Collaboration Meeting Room options.
- Site Administration—https://help.webex.com/en-us/6maub2/Configure-Webex-Meetings-in-Cisco-Webex-Site-Administration
- Control Hub—https://help.webex.com/en-us/n8pgczj/Configure-Teleconferencing-Options-for-a-Webex-Site-in-Cisco-Webex-Control-Hub
Ensure Collaboration Meeting Rooms are enabled for your users on Cisco Webex Meetings.
Collaboration Meeting Room features uses SIP URI, you must enable URI dialing for your users on Cisco Unified Communications Manager. For more information on URI dialing, see the URI Dialing topic.
Dial via Office
Applies to: Cisco Jabber for Android, Cisco Jabber for iPhone and iPad
The following features are not supported if the Dial via Office-Reverse (DvO-R) feature is enabled:
- URI dialing
- Secure Phone
User-controlled voicemail avoidance, which can be used in conjunction with the DvO feature, is available only on Cisco Unified Communications Manager release 9.0 and later. Timer-controlled voicemail avoidance is available on Cisco Unified Communications Manager release 6.0 and later.
You can make DvO-R calls over Expressway for Mobile and Remote Access when you are outside corporate network. DvO-R is supported on Cisco Expressway X8.7 and Cisco Unified Communications Manager 11.0(1a)SU1.
The DvO feature is not supported when users connect to the corporate network using Expressway for Mobile and Remote Access.
The DvO feature allows users to initiate Cisco Jabber outgoing calls with their work number using the mobile voice network for the device.
Cisco Jabber supports DvO-R (DvO-Reverse) calls, which works as follows:
- User initiates a DvO-R call.
- The client notifies Cisco Unified Communications Manager to call the mobile phone number.
- Cisco Unified Communications Manager calls and connects to the mobile phone number.
- Cisco Unified Communications Manager calls and connects to the number that the user dialed.
- Cisco Unified Communications Manager connects the two segments.
- The user and the called party continue as with an ordinary call.
Incoming calls use either Mobile Connect or the Voice over IP, depending on which Calling Options the user sets on the client. Dial via Office does not require Mobile Connect to work. However, we recommend that you enable Mobile Connect to allow the native mobile number to ring when someone calls the work number. From the Cisco Unified Communications Manager user pages, users can enable and disable Mobile Connect, and adjust Mobile Connect behavior using settings (for example, the time of day routing and Delay Before Ringing Timer settings). For information about setting up Mobile Connect, see the Set Up Mobile Connect topic.
The users do not receive incoming calls on Cisco Jabber in the following situations:
- If users select the Mobile Voice Network calling option on any network and the Single Number Reach (SNR) is not configured for their device, they will not receive incoming calls on Cisco Jabber.
- If users select the Mobile Voice Network calling option on any network and the Single Number Reach (SNR) is configured with the Ring Schedule , they will not receive incoming calls on Cisco Jabber beyond the time set in the Ring Schedule .
The following table describes the calling methods used for incoming and outgoing calls. The calling method (VoIP, Mobile Connect, DvO-R, or native cellular call) varies depending on the selected Calling Options and the network connection.
- Automatically Populate Directory Numbers with URIs