Voice and Video
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.
Call Park
Applies to: Cisco Jabber for Android, Cisco Jabber for iOS
You can use call park to place a call on hold and pick it up from another phone in a Cisco Unified Communication Manager system. Call park must be enabled and extension numbers must be defined on each Cisco Unified Communication Manager node in a 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.
Configure Clusterwide Call Park
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.
| Step 1 | From Cisco Unified CM Administration, choose . |
| Step 2 | Click Add New to create a new partition. |
| Step 3 | In the Partition Name, Description field, enter a name for the partition that is unique to the route plan. Partition names can contain alphanumeric characters, as well as spaces, hyphens (-), and underscore characters (_). See the online help for guidelines about partition names. |
| Step 4 | Enter a comma (,) after the partition name and enter a description of the partition on the same line. The description can contain up to 50 characters in any language, but it cannot include double quotes ("), percentage sign (%), ampersand (&), backslash (\), angle brackets (<>), or square brackets ([ ]). If you do not enter a description, Cisco Unified Communications Manager automatically enters the partition name in this field. |
| Step 5 | To create multiple partitions, use one line for each partition entry. |
| Step 6 | From the Time Schedule drop-down list, choose a time schedule to associate with this partition. The time schedule specifies when the partition is available to receive incoming calls. If you choose None, the partition remains active at all times. |
| Step 7 | Select one
of the following radio buttons to configure the
Time
Zone:
|
| Step 8 | Click Save. |
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 Cisco Unified Communications Manager. Each Cisco Unified Communications Manager to which devices are registered requires its own unique Call Park directory number and range. Cisco Unified Communications Manager Administration 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 Cisco Unified Communications Manager Dialed Number Analyzer tool.
| Step 1 | Choose . |
| Step 2 | Perform one of the following tasks: The Call Park number configuration window displays. |
| Step 3 | Configure the fields in the Call Park configuration fields. See the Related Topics section for more information about the fields and their configuration options. |
| Step 4 | To save the new or changed Call Park numbers in the database, click Save. |
Call Park Configuration Fields
Field |
Description |
||||||
|---|---|---|---|---|---|---|---|
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.
|
||||||
Description |
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 (<>). |
||||||
Partition |
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 <None> for the partition.
|
||||||
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
The Call Pickup feature allows users to answer calls that come in on a directory number other than their own. Directory numbers are assigned to call pickup groups and Cisco Unified Communications Manager automatically dials the appropriate call pickup group number. Users select Pickup to answer the call.
Group call pickup allows users to pick up incoming calls in another group. Users enter the group pickup number, select Pickup and Cisco Unified Communications Manager automatically dials the appropriate call pickup group number.
Other group pickup allows users to pick up incoming calls in a group that is associated with their group. When the user selects Other Pickup Cisco Unified Communications Manager automatically searches for the incoming call in the associated groups.
Directed call pickup allows users to pick up an incoming call on a directory number. Users enter the directory number, select Pickup and Cisco Unified Communications Manager connects the incoming call.
For more information about configuring call pickup, see the Feature Configuration Guide for Cisco Unified Communications Manager.
Call pickup notifications
For multiple incoming calls, the notification displayed is Call(s) available for pickup. When the user answers a call, the user gets connected to the incoming call that has been ringing the longest.
Deskphone mode
The Cisco Unified Communications Manager notification settings are not supported for the pickup group. The call pickup notification displayed is CallerA->CallerB.
The Cisco Unified Communications Manager settings for audio and visual settings are not supported. The visual alerts are always displayed.
Shared line behavior
User not a member of an associated group
Expected behavior using group call pickup and directed call pickup
Enter an invalid number Enter a valid number and no current call available to pick up Enter directory number of a phone in an associated group and no current call available to pick up Enter a directory number of a phone on the same Cisco Unified Communications Manager node and not in an associated group Enter first digits of a valid group
Call pickup using a deskphone that is not in a call pickup group
If a user attempts a call pickup from a deskphone that is not in a call pickup group, the conversation window appears for a moment. The user should not be configured to use the call pickup feature if they are not members of a call pickup group.
Original recipient information not available
When the Cisco Unified Communications Manager Auto Call Pickup Enabled setting is true, the recipient information is not available in the client when the call is picked up in softphone mode. If the setting is false, the recipient information is available.
- Configure Call Pickup Group
- Assign Directory Number
- Configure Other Call Pickup
- Configure Directed Call Pickup
- Auto Call Pickup
Configure Call Pickup Group
Call pickup groups allow users to pick up incoming calls in their own group.
| Step 1 | Open the Cisco Unified Communication Manager interface. |
| Step 2 | Select
The Find and List Call Pickup Groups window opens. |
| Step 3 | Select
Add
New
The Call Pickup Group Configuration window opens. |
| Step 4 | Enter call pickup group information: |
| Step 5 | (Optional)
Configure the
audio or visual notification in the
Call
Pickup Group Notification Settings section.
For further information on call pickup group notification settings see the call pickup topics in the relevant Cisco Unified Communications Manager documentation. |
| Step 6 | Select Save. |
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 assign a call pickup group to a directory number, you must create the call pickup group.
| Step 1 | Open the Cisco Unified Communications Manager Administration interface. |
| Step 2 | Assign a call pickup group to a directory number using one of the
following methods:
|
| Step 3 | 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, configure call pickup groups.
| Step 1 | Open the Cisco Unified Communication Manager Administration interface. |
| Step 2 | Select
The Find and List Call Pickup Groups window opens. |
| Step 3 | Select your
call pickup group.
The Call Pickup Group Configuration window opens. |
| Step 4 | In the Associated Call Pickup Group Information section, you can do the following: |
| Step 5 | Select Save. |
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.
| Step 1 | 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. |
| Step 2 | 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
| Step 1 | Open the Cisco Unified CM Administration interface. |
| Step 2 | Select |
| Step 3 | Select your server from the Server drop down list and then select the Cisco Call Manager service from the Service drop down list. |
| Step 4 | In the Clusterwide Parameters (Feature - Call Pickup) section, select one of the following for Auto Call Pickup Enabled: |
| Step 5 | Select Save. |
Collaboration Meeting Rooms
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.
Cisco Collaboration Meeting Rooms Cloud is available on Cisco WebEx Meeting Center.
| Step 1 | Configure the Collaboration Meeting Room options using the configuration guides available here: https://www.cisco.com/c/en/us/support/conferencing/webex-meeting-center/products-installation-and-configuration-guides-list.html |
| Step 2 | Ensure Collaboration Meeting Rooms are enabled for your users on Cisco WebEx Meeting Center. |
| Step 3 | 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 iOS
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 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.
 Note |
|
|
Connection |
Calling Options |
|||||
|---|---|---|---|---|---|---|
|
Voice over IP |
Mobile Voice Network |
Autoselect |
||||
|
Corporate Wi-Fi |
Outgoing: VoIP |
Incoming: VoIP |
Outgoing: DvO-R |
Incoming: Mobile Connect |
Outgoing: VoIP |
Incoming: VoIP |
|
Noncorporate Wi-Fi |
||||||
|
Mobile Network (3G, 4G) |
Outgoing: DvO-R |
Incoming: Mobile Connect | ||||
|
Phone Services are not registered |
Outgoing Native Cellular Call | |||||
| Incoming Mobile Connect | ||||||
To set up Dial via Office-Reverse (DvO-R), you must do the following:
-
Set up the Cisco Unified Communications Manager to support DvO-R. See the Set Up Cisco Unified Communications Manager to Support DvO topic for more information.
-
Enable DvO on each Cisco Dual Mode for iPhone device. See the Set Up Dial via Office for Each Device topic for more information.
-
Enable DvO on each Cisco Dual Mode for Android device. See the Set Up Dial via Office for Each Device topic for more information.
- Set Up Cisco Unified Communications Manager to Support Dial via Office
- Set Up Dial via Office for Each Device
Set Up Cisco Unified Communications Manager to Support Dial via Office
To set up Cisco Unified Communications Manager to support Dial via Office-Reverse ( DvO-R), perform the following procedures:
-
Complete one or both of the following procedures.
-
Complete the Verify Device COP File Version procedure.
-
If necessary, create application dial rules to allow the system to route calls to the Mobile Identity phone number to the outbound gateway. Ensure that the format of the Mobile Identity phone number matches the application dial rules.
Set Up Enterprise Feature Access Number
Use this procedure to set up an Enterprise Feature Access Number for all Cisco Jabber calls that are made using Dial via Office-Reverse.
The Enterprise Feature Access Number is the number that Cisco Unified Communications Manager uses to call the mobile phone and the dialed number unless a different number is set up in Mobility Profile for this purpose.
Reserve a Direct Inward Dial (DID) number to use as the Enterprise Feature Access Number (EFAN). This procedure is optional if you already set up a mobility profile.
Determine the required format for this number. The exact value you choose depends on the phone number that the gateway passes (for example, 7 digits or 10 digits). The Enterprise Feature Access Number must be a routable number.
| Step 1 | Open the Cisco Unified CM Administration interface. |
| Step 2 | Select . |
| Step 3 | Select Add New. |
| Step 4 | In the Number field, enter the Enterprise Feature Access number. Enter a DID number that is unique in the system. To support dialing internationally, you can prepend this number with \+. |
| Step 5 | From the Route Partition drop-down list, choose the partition of the DID that
is required for enterprise feature access.
This partition is set under , in the Clusterwide Parameters (System - Mobility) section, in the Inbound Calling Search Space for Remote Destination setting. This setting points either to the Inbound Calling Search Space of the Gateway or Trunk, or to the Calling Search Space assigned on the Phone Configuration window for the device. If the user sets up the DvO Callback Number with an alternate number, ensure that you set up the trunk Calling Search Space (CSS) to route to destination of the alternate phone number. |
| Step 6 | In the Description field, enter a description of the Mobility Enterprise Feature Access number. |
| Step 7 | (Optional) Check the Default Enterprise Feature Access Number check box if you want to make this Enterprise Feature Access number the default for this system. |
| Step 8 | Select Save. |
Set Up Mobility Profile
Use this procedure to set up a mobility profile for Cisco Jabber devices. This procedure is optional if you already set up an Enterprise Feature Access Number.
Mobility profiles allow you to set up the Dial via Office-Reverse settings for a mobile client. After you set up a mobility profile, you can assign it to a user or to a group of users, such as the users in a region or location.
| Step 1 | Open the Cisco Unified CM Administration interface. |
| Step 2 | Select . |
| Step 3 | In the Mobility Profile Information section, in the Name field, enter a descriptive name for the mobility profile. |
| Step 4 | In the Dial via Office-Reverse Callback section, in the Callback Caller ID field, enter the caller ID for the callback call that the client receives from Cisco Unified Communications Manager. |
| Step 5 | Click Save. |
Verify Device COP File Version
Use the following procedure to verify that you are using the correct device COP file for this release of Cisco Jabber.
| Step 1 | Open the Cisco Unified CM Administration interface. |
| Step 2 | Select . |
| Step 3 | Click Add New. |
| Step 4 | From the Phone Type drop-down list, choose Cisco Dual Mode for iPhone. |
| Step 5 | From the Phone Type drop-down list, choose Cisco Dual Mode for Android. |
| Step 6 | Click Next. |
| Step 7 | Scroll down to
the Product Specific Configuration Layout section, and verify that you can see
the Video Capabilities drop-down list.
If you can see the Video Capabilities drop-down list, the COP file is already installed on your system. If you cannot see the Video Capabilities drop-down list, locate and download the correct COP file. |
Set Up Dial via Office for Each Device
Use the following procedures to set up Dial via Office - Reverse for each TCT device.
Use the following procedures to set up Dial via Office - Reverse for each BOT device.
Add Mobility Identity
Use this procedure to add a mobility identity to specify the mobile phone number of the mobile device as the destination number. This destination number is used by features such as Dial via Office or mobile connect.
You can specify only one number when you add a mobility identity. If you want to specify an alternate number such as a second mobile phone number for a mobile device, you can set up a remote destination. The mobility identity configuration characteristics are identical to those of the remote destination configuration.
| Step 1 | Open the Cisco Unified CM Administration interface. | ||||||||||||||||||
| Step 2 | Navigate to the device that you want to configure as follows: | ||||||||||||||||||
| Step 3 | In the Associated Mobility Identity section, select Add a New Mobility Identity. | ||||||||||||||||||
| Step 4 | Enter the
mobile phone number as the destination number.
You must be able to rout this number to an outbound gateway. Generally, the number is the full E.164 number.
| ||||||||||||||||||
| Step 5 | Enter the
initial values for call timers.
These values ensure that calls are not routed to the mobile service provider voicemail before they ring in the client on the mobile device. You can adjust these values to work with the end user's mobile network. For more information, see the online help in Cisco Unified Communications Manager.
| ||||||||||||||||||
| Step 6 | Do one of the following: | ||||||||||||||||||
| Step 7 | If you are
setting up the Dial via Office feature, in the Mobility Profile drop-down list,
select one of the following options.
| ||||||||||||||||||
| Step 8 | Set up the schedule for routing calls to the mobile number. | ||||||||||||||||||
| Step 9 | Select Save. |
Enable Dial via Office on Each Device
Use this procedure to enable Dial via Office on each device.
| Step 1 | Open the Cisco Unified CM Administration interface. | ||
| Step 2 | Navigate to the device that you want to configure as follows: | ||
| Step 3 | In the Device Information section, check the Enable Cisco Unified Mobile Communicator check box. | ||
| Step 4 | In the Protocol Specific Information section, in the Rerouting Calling Search Space drop-down list, select a Calling Search Space (CSS) that can route the call to the DvO callback number. | ||
| Step 5 | In the Product Specific Configuration Layout section, set the Dial via Office drop-down list to Enabled. | ||
| Step 6 | Select Save. | ||
| Step 7 | Select Apply Config. | ||
| Step 8 | Instruct the
user to sign out of the client and then to sign back in again to access the
feature.
|
What to Do Next
Test this feature.
Far End Camera Control (FECC)
Applies to: All clients
In calls that support far-end camera control (FECC), you can adjust the far-end camera to give you a better view during video calls. FECC is available to users if the endpoint that they are calling supports it.
You can configure whether users can access FECC-enabled endpoints. Disabling the configuration parameter means that users are not provided with the ability to control far-end camera endpoints, even if the endpoint is capable. From a user experience, with FECC disabled, it works the same as dialing in to an endpoint that is not FECC enabled.
To disable FECC, set the EnableFecc parameter to false. For more information about this parameter, see the Parameters Reference Guide.
Limitations
FECC is only supported in point-to-point calls, but not in group calls or conferences where multiple video connections are connecting to the same bridge.
FECC is only supported in Softphone mode.
Flexible DSCP Values
Applies to: Cisco Jabber for Mac, Cisco Jabber for Android, Cisco Jabber for iOS
Flexible Differentiated Services Code Point (DSCP) allows you to specify different DSCP values to separate the audio and video streams on the network.
The EnableDSCPPacketMarking parameter is used to enable or disable DSCP packet marking in the client.
You can configure the DSCP values for audio calls, video calls, audio portion for video calls, and audio portion for telepresence calls separately. For better bandwidth management and to protect audio stream degradation, separate the audio stream from the higher-bandwidth video stream. This can help when the network is congested or the call quality is impacted.
DSCP values are configured on Cisco Unified Communications Manager. For more information, see the Configure Flexible DSCP Marking and Video Promotion Policy section of the System Configuration Guide for Cisco Unified Communications Manager.
Hunt Group
Applies to: All clients
A Hunt Group is a group of lines that are organized hierarchically, so that if the first number in the hunt group list is busy, the system dials the second number. If the second number is busy, the system dials the next number, and so on. Every hunt group has a pilot number that is also called as hunt pilot. A hunt pilot contains a hunt pilot number and an associated hunt list. Hunt pilots provide flexibility in network design. They work with route filters and hunt lists to direct calls to specific devices and to include, exclude, or modify specific digit patterns.
A hunt pilot number is the number that a user dials. A hunt list contains a set of line groups in a specific order. A line group comprises a group of directory numbers in a specific order. The order controls the progress of the search for available directory numbers for incoming calls. A single-line group can appear in multiple hunt lists.
Cisco Unified Communications Manager identifies a call that is to be routed through a defined hunt list, Cisco Unified Communications Manager finds the first available device on the basis of the order of the line groups that a hunt list defines.
You can let a user log in to hunt groups by configuring EnableHuntGroup parameter. For more information, see the latest Parameters Reference Guide for Cisco Jabber.
Cisco Unified Communications Manager 9.x and later allows configuring of automatic log out of a hunt member when there is no answer. Once the user is logged out, the system displays a log out notification regardless of whether the user is auto logged out, manually logged out, or logged out by the Cisco Unified Communications Manager administrator.
Hunt group features supported by the Cisco Jabber clients:
|
Features |
Mobile Clients |
Desktop Clients |
|---|---|---|
|
Log in to hunt group and log out of hunt group |
Not supported |
Supported |
|
Call, answer, and decline |
Supported |
Supported |
Line Group
A line group allows you to designate the order in which directory numbers are chosen. Cisco Unified Communications Manager distributes a call to an idle or available member of a line group based on the call distribution algorithm and on the Ring No Answer (RNA) Reversion timeout setting.
Users cannot pick up calls to a DN that belongs to a line group by using the directed call pickup feature.
Configure Line Group
Configure directory numbers.
| Step 1 | Open the Cisco Unified CM Administration interface. |
| Step 2 | Select
.
The Find and List Line Groups window opens. |
| Step 3 | Select
Add
New.
The Line Group Configuration window opens. |
| Step 4 | Enter settings in the Line Group Information section as follows: |
| Step 5 | Enter settings in the Hunt Options section as follows: |
| Step 6 | In the Line Group Member Information section, you can do the following: |
| Step 7 | Select Save. |
What to Do Next
Configure a hunt list and add the line group to the hunt list.
Hunt List
A hunt list contains a set of line groups in a specific order. A hunt list associates with one or more hunt pilots and determines the order in which those line groups are accessed. The order controls the progress of the search for available directory numbers for incoming calls.
A hunt list comprises a collection of directory numbers as defined by line groups. After Cisco Unified Communications Manager determines a call that is to be routed through a defined hunt list, Cisco Unified Communications Manager finds the first available device on the basis of the order of the line group(s) that a hunt list defines.
A hunt list can contain only line groups. Each hunt list should have at least one line group. Each line group includes at least one directory number. A single line group can appear in multiple hunt lists.
Note | The group call pickup feature and directed call pickup feature do not work with hunt lists. |
Configure Hunt List
| Step 1 | Open the Cisco Unified CM Administration interface. |
| Step 2 | Select
.
The Find and Hunt List Groups window opens. |
| Step 3 | Select
Add New.
The Hunt List Configuration window opens. |
| Step 4 | Enter settings in the
Hunt List Information section as follows:
|
| Step 5 | Select Save to add the hunt list. |
What to Do Next
Add line groups to the hunt list.
Add Line Group to Hunt List
You must configure line groups and configure a hunt list.
| Step 1 | Open the Cisco Unified CM Administration interface. |
| Step 2 | Select
.
The Find and Hunt List Groups window opens. |
| Step 3 | Locate the hunt list to which you want to add a line group. |
| Step 4 | To add a line group, select
Add Line Group.
The Hunt List Detail Configuration window displays. |
| Step 5 | Select a line group from the Line Group drop-down list. |
| Step 6 | To add the line group, select Save. |
| Step 7 | To add additional line groups, repeat Step 4 to Step 6. |
| Step 8 | Select Save. |
| Step 9 | To reset the hunt list, select Reset. When the dialog box appears, select Reset. |
Hunt Pilot
A hunt pilot comprises a string of digits (an address) and a set of associated digit manipulations that route calls to a hunt list. Hunt pilots provide flexibility in network design. They work in conjunction with route filters and hunt lists to direct calls to specific devices and to include, exclude, or modify specific digit patterns. For more information about hunt pilots, see the System Configuration Guide for Cisco Unified Communications Manager.
For more detailed information on the configuration options for hunt pilots, see the relevant Cisco Unified Communications Manager documentation.
Configure Hunt Pilot
| Step 1 | Open the Cisco Unified CM Administration interface. |
| Step 2 | Select
.
The Find and List Hunt Pilots window opens. |
| Step 3 | Select
Add
New.
The Hunt Pilot Configuration window opens. |
| Step 4 | Enter the hunt pilot, including numbers and wildcards. |
| Step 5 | Select a hunt list from the Hunt List drop-down list. |
| Step 6 | Enter any additional configurations in the Hunt Pilot Configuration window. For more information on hunt pilot configuration settings, see the relevant Cisco Unified Communications Manager documentation. |
| Step 7 | Select Save. |
Jabber to Jabber Call
Applies to: All clients
Note |
|
Jabber to Jabber Call Experience
-
Cisco Jabber for mobile clients does not support HD video in portrait mode. To achieve HD video, you need to rotate the phone from portrait to landscape mode during the call.
-
If two users start a Jabber to Jabber call to each other at the same time, the call is automatically connected. In such case, users do not receive any incoming call notification.
-
When users are on a Jabber to Jabber call and start another call, the ongoing call ends immediately, even if the person they called does not answer.
-
When on a Jabber to Jabber call and they receive an incoming Jabber to Jabber call, the End Call And Answer option is displayed. When they select this button, the ongoing Jabber to Jabber call ends and the incoming call is answered.
-
For Jabber to Jabber calls on Cisco Jabber for mobile clients: -
Cisco Jabber for mobile clients does not support HD video in portrait mode. To achieve HD video, you need to rotate the phone from portrait to landscape mode during the call.
-
When users are on a Jabber to Jabber call and they make a phone call, the ongoing Jabber to Jabber call ends immediately, even if the remote party does not answer.
-
When users are on a mobile call, they cannot answer any Jabber to Jabber call. The incoming Jabber to Jabber call is listed as a missed call.
-
When users are on a Jabber to Jabber call and they receive an incoming mobile call:
-
Supported In-Call Features
Jabber to Jabber Call Cloud Deployment
-
Install the following root certificate to use the Jabber to Jabber call feature: GoDaddy Class 2 Certification Authority Root Certificate. To resolve any warnings about this certificate name, install the required GoDaddy certificate.
-
Include the following servers in the proxy server bypass list: For information on proxy server lists, see the Configure Proxy Settings in the Cisco Jabber Deployment Guides. -
Enable the range of media ports and protocols for RTP/SRTP over UDP: 33434-33598 and 8000-8100. For Jabber to Jabber call setup over HTTPS, enable port 443.
-
Before you enable the Jabber to Jabber calling feature, complete the following tasks: -
Contact the Cisco Customer Support team or your Cisco Customer Success Manager to request that your organization is added to the Cisco Common Identity server. This process to add users to the Common Identity server takes some time to complete and is necessary to access Jabber to Jabber calling capabilities.
-
For Single Sign On (SSO) users, you must set up SSO for Common Identity. For more information about configuring SSO, see the Cisco WebEx Messenger documentation at this link: https://www.cisco.com/c/en/us/support/unified-communications/webex-messenger/products-installation-guides-list.html.
-
-
Using the P2P settings in the Configuration Tab section. For more information, see the Cisco WebEx Messenger Administrator's Guide.
-
Using the Internal VoIP and External VoIP settings in the policy editor for Cisco WebEx Messenger Administration tool. You can control the video services for Jabber to Jabber calls using the Internal Video and External Video policy actions. For more information, see the Policy Editor section of the Cisco WebEx Messenger Administration Guide.Jabber to Jabber calling can be enabled for groups of users or all users.
Jabber to Jabber Hybrid Mode
Jabber to Jabber Call Experience in Hybrid Mode
In addition to the limitations for Jabber to Jabber, the following are the scenarios that occur when using Jabber to Jabber calls and Cisco Unified Communications Manager calls:
-
When users are on a Jabber to Jabber call and make a Cisco Unified Communications Manager call, the ongoing Jabber to Jabber call ends immediately, even if the remote party does not answer.
-
When users are on a Jabber to Jabber call and resume a Cisco Unified Communications Manager call from on hold, the Jabber to Jabber call ends immediately.
-
When users are on a Jabber to Jabber call and receive an incoming Cisco Unified Communications Manager call, a notification with an End Call And Answer button displays. If your user selects this button the ongoing Jabber to Jabber call ends and the incoming call is answered.
-
When users receive a Cisco Unified Communications Manager call, they can place the ongoing Cisco Unified Communications Manager call on hold to answer the new call.
-
When users are on a Cisco Unified Communications Manager call and they choose to make a Jabber to Jabber call, the Cisco Unified Communications Manager call is put on hold immediately, even if the participant in the Jabber to Jabber call does not answer the call.
-
When users are on a Cisco Unified Communications Manager call and they answer an incoming Jabber to Jabber call, the Cisco Unified Communications Manager call is put on hold immediately.
-
If your user’s line is configured on Cisco Unified Communications Manager to auto-answer calls and they receive an incoming Cisco Unified Communications Manager call when they are on a Jabber to Jabber call, the Jabber to Jabber call ends immediately without notification and the Cisco Unified Communications Manager call is answered.
Jabber to Jabber Bandwidth
Specifies the maximum bandwidth (in kilobits per second) to be used for Jabber to Jabber calls. The video quality (resolution) of the call is lowered so that it meets the bandwidth limit. This feature is configured using the J2JMaxBandwidthKbps parameter.
For more information on parameters, see the Parameter Reference Guide for your release.
Mobile Connect
Applies to: Cisco Jabber for Android, Cisco Jabber for iOS
Mobile connect, formerly known as Single Number Reach (SNR), allows the native mobile phone number to ring when someone calls the work number if:
Cisco Jabber is not available—After Cisco Jabber becomes available again and connects to the corporate network, Cisco Unified Communications Manager returns to placing VoIP calls rather than using mobile connect.
The user selects the Mobile Voice Network calling option.
The user selects the Autoselect calling option and the user is outside of the Wi-Fi network.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | Enable Mobile Connect | |
| Step 2 | Add Mobility Identity | To configure the mobile device phone number. |
| Step 3 | Add Remote Destination (Optional) | To configure an alternate phone number. |
| Step 4 | Test your settings. |
Enable Mobile Connect
Use the following procedure to enable mobile connect for an end user.
| Step 1 | Open the Cisco Unified CM Administration interface. |
| Step 2 | Search for and delete any existing remote destination or mobility Identity that is already set up with the mobile phone number as follows: |
| Step 3 | Configure the end user for mobile connect as follows: |
| Step 4 | Configure the
device settings for mobile connect as follows:
|
Add Remote Destination (Optional)
Use this procedure to add a remote destination to specify any alternate number as the destination number. The Mobility Identity configuration characteristics are identical to those of the remote destination configuration.
Alternate numbers can be any type of phone number, such as home phone numbers, conference room numbers, desk phone numbers, or multiple mobile phone numbers for additional mobile devices. You can add more than one remote destination.
| Step 1 | Open the Cisco Unified CM Administration interface. |
| Step 2 | Navigate to the device that you want to configure as follows: |
| Step 3 | In the Associated Remote Destinations section, select Add a New Remote Destination. |
| Step 4 | Enter the
desired phone number as the Destination Number.
You must be able to rout the number to an outbound gateway. Generally, the number is the full E.164 number. |
| Step 5 | Enter the
initial values for the following call timers: These values ensure that calls are not routed to the mobile service provider voicemail before they ring in the client on the mobile device. For more information, see the online help in Cisco Unified Communications Manager. |
| Step 6 | Do one of the following: |
| Step 7 | Set up the schedule for routing calls to the mobile number. |
| Step 8 | Select Save. |
Move to Mobile
Applies to: Cisco Jabber for Android, Cisco Jabber for iOS
Users can transfer an active VoIP call from Cisco Jabber to their mobile phone number on the mobile network. This feature is useful when a user on a call leaves the Wi-Fi network (for example, leaving the building to walk out to the car), or if there are voice quality issues over the Wi-Fi network.
Implementation Method |
Description |
Instructions |
|---|---|---|
Handoff DN |
The mobile device calls Cisco Unified Communications Manager using the mobile network. This method requires a Direct Inward Dial (DID) number. The service provider must deliver the DID digits exactly as configured. Alternately, for Cisco IOS gateways with H.323 or SIP communication to Cisco Unified Communications Manager, you can use Cisco IOS to manipulate the inbound called-party number at the gateway, presenting the digits to Cisco Unified Communications Manager exactly as configured on the handoff DN. This method does not work for iPod Touch devices. |
See the Enable Handoff from VoIP to Mobile Network topic. |
Mobility Softkey |
Cisco Unified Communications Manager calls the phone number of the PSTN mobile service provider for the mobile device. |
See the Enable Transfer from VoIP to Mobile Network topic. |
None of the above |
Disable this feature if you do not want to make it available to users. |
Select Disabled for the Transfer to Mobile Network option in the Product Specific Configuration Layout section of the TCT device page. Select Disabled for the Transfer to Mobile Network option in the Product Specific Configuration Layout section of the BOT device page. |
Enable Handoff from VoIP to Mobile Network
Set up a directory number that Cisco Unified Communications Manager can use to hand off active calls from VoIP to the mobile network. Match the user's caller ID with the Mobility Identity to ensure that Cisco Unified Communications Manager can recognize the user. Set up the TCT device and mobile device to support handoff from VoIP to the mobile network.
Set up a directory number that Cisco Unified Communications Manager can use to hand off active calls from VoIP to the mobile network. Match the user's caller ID with the Mobility Identity to ensure that Cisco Unified Communications Manager can recognize the user. Set up the BOT device and mobile device to support handoff from VoIP to the mobile network.
Set Up Handoff DN
Determine the required values. The values that you choose depend on the phone number that the gateway passes (for example, seven digits or ten digits).
| Step 1 | Open the Cisco Unified CM Administration interface. | ||
| Step 2 | Select . | ||
| Step 3 | Enter the
Handoff Number for the Direct Inward Dial
(DID) number that the device uses to hand off a VoIP call to the mobile
network.
The service provider must deliver the DID digits exactly as configured. Alternately, for Cisco IOS gateways with H.323 or SIP communication to Cisco Unified Communications Manager, you can use Cisco IOS to manipulate the inbound called-party number at the gateway, presenting the digits to Cisco Unified Communications Manager exactly as configured on the handoff number.
| ||
| Step 4 | Select the
Route Partition for the handoff DID.
This partition should be present in the Remote Destination inbound Calling Search Space (CSS), which points to either the Inbound CSS of the Gateway or Trunk, or the Remote Destination CSS. This feature does not use the remaining options on this page. | ||
| Step 5 | Select Save. |
Match Caller ID with Mobility Identity
To ensure that only authorized phones can initiate outbound calls, calls must originate from a phone that is set up in the system. To do this, the system attempts to match the caller ID of the requesting phone number with an existing Mobility Identity. By default, when a device initiates the Handoff feature, the caller ID that is passed from the gateway to Cisco Unified Communications Manager must exactly match the Mobility Identity number that you entered for that device.
However, your system may be set up such that these numbers do not match exactly. For example, Mobility Identity numbers may include a country code while caller ID does not. If so, you must set up the system to recognize a partial match.
Be sure to account for situations in which the same phone number may exist in different area codes or in different countries. Also, be aware that service providers can identify calls with a variable number of digits, which may affect partial matching. For example, local calls may be identified using seven digits (such as 555 0123) while out-of-area calls may be identified using ten digits (such as 408 555 0199).
Set up the Mobility Identity. See the Add Mobility Identity topic.
To determine whether you need to complete this procedure, perform the following steps. Dial in to the system from the mobile device and compare the caller ID value with the Destination Number in the Mobility Identity. If the numbers do not match, you must perform this procedure. Repeat this procedure for devices that are issued in all expected locales and area codes.
| Step 1 | Open the Cisco Unified CM Administration interface. |
| Step 2 | Select . |
| Step 3 | Select the active server. |
| Step 4 | Select the Cisco CallManager (Active) service. |
| Step 5 | Scroll down to the Clusterwide Parameters (System - Mobility) section. |
| Step 6 | Select Matching Caller ID with Remote Destination and read essential information about this value. |
| Step 7 | Select Partial Match for Matching Caller ID with Remote Destination. |
| Step 8 | Select Number of Digits for Caller ID Partial Match and read the essential requirements for this value. |
| Step 9 | Enter the required number of digits to ensure partial matches. |
| Step 10 | Select Save. |
Set Up User and Device Settings for Handoff
| Step 1 | In the
Cisco
Unified CM Administration interface, go to the TCT Device page, and
select
Use
Handoff DN Feature for the
Transfer to Mobile Network option.
Do not assign this method for iPod Touch devices. Use the Mobility Softkey method instead. |
| Step 2 | In the Cisco Unified CM Administration interface, go to the BOT Device page, and select Use Handoff DN Feature for the Transfer to Mobile Network option. |
| Step 3 | On the iOS device, tap to verify that Caller ID is on. |
| Step 4 | On some Android device and operating system combinations, you can verify that the Caller ID is on. On the Android device, open the Phone application and tap . |
| Step 5 | Test this feature. |
Enable Transfer from VoIP to Mobile Network
| Step 1 | Open the Cisco Unified CM Administration interface. |
| Step 2 | For
system-level settings, check that the Mobility softkey appears when the phone
is in the connected and on-hook call states.
|
| Step 3 | Navigate to the device that you want to configure as follows: |
| Step 4 | For the
per-user and per-device settings in
Cisco Unified Communications Manager, set the specific device to use the
Mobility softkey when the device transfers calls to the mobile voice network.
Ensure that you have set up both Mobility Identity and Mobile Connect for the
mobile device. After the transfer feature is working, users can enable and
disable Mobile Connect at their convenience without affecting the feature.
If the device is an iPod Touch, you can configure a Mobility Identity using an alternate phone number such as the mobile phone of the user. |
| Step 5 | In the User Locale field, choose English, United States. |
| Step 6 | Select Save. |
| Step 7 | Select Apply Config. |
| Step 8 | Instruct the user to sign out of the client and then to sign back in again to access the feature. |
What to Do Next
Test your settings by transferring an active call from VoIP to the mobile network.
Personal Rooms
Applies to: All clients
A personal room is a virtual conference room that is always available and can be used to meet with people. Cisco Jabber uses the personal room feature of Cisco WebEx Meeting Center to allow users to easily meet with their contacts using the Meet Now option in the client.
| Step 1 | Personal Rooms are enabled by default for users on Cisco WebEx Meeting Center. For more information see the Cisco WebEx Meeting Center documentation available here: https://www.cisco.com/c/en/us/support/conferencing/webex-meeting-center/products-installation-and-configuration-guides-list.html |
| Step 2 | Users can configure their personal rooms for all instant meetings by selecting Use Personal Room for all my instant meetings in Cisco WebEx Meeting Center. |
URI Dialing
This feature is supported for on-premises deployments. URI dialing is enabled in Cisco Unified Communications Manager, release 9.1(2) or later.
This feature is enabled in the jabber-config.xml file using the EnableSIPURIDialling parameter.
Example: <EnableSIPURIDialling>True</EnableSIPURIDialling>
For more information on the values of the parameter, see the Parameters Reference Guide.
Applies to: All clients
The mobile clients don't support URI dialing when the Dial via Office-Reverse feature is enabled.
URI dialing allows users to make calls and resolve contacts with Uniform Resource Identifiers (URI). For example, a user named Adam McKenzie has the following SIP URI associated with his directory number: amckenzi@example.com. URI dialing enables users to call Adam with his SIP URI rather than his directory number.
For detailed information on URI dialing requirements, such as valid URI formats, as well as advanced configuration including ILS setup, see the URI Dialing section of the System Configuration Guide for Cisco Unified Communications Manager .
Associate URIs to Directory Numbers
When users make URI calls, Cisco Unified Communications Manager routes the inbound calls to the directory numbers associated to the URIs. For this reason, you must associate URIs with directory numbers. You can either automatically populate directory numbers with URIs or configure directory numbers with URIs.
Automatically Populate Directory Numbers with URIs
When you add users to Cisco Unified Communications Manager, you populate the Directory URI field with a valid SIP URI. Cisco Unified Communications Manager saves that SIP URI in the end user configuration.
When you specify primary extensions for users, Cisco Unified Communications Manager populates the directory URI from the end user configuration to the directory number configuration. In this way, automatically populates the directory URI for the user's directory number. Cisco Unified Communications Manager also places the URI in the default partition, which is Directory URI.
The following task outlines, at a high level, the steps to configure Cisco Unified Communications Manager so that directory numbers inherit URIs:
What to Do Next
Verify that the directory URIs are associated with the directory numbers.
Configure Directory Numbers with URIs
You can specify URIs for directory numbers that are not associated with users. You should configure directory numbers with URIs for testing and evaluation purposes only.
To configure directory numbers with URIs, do the following:
| Step 1 | Open the Cisco Unified CM Administration interface. | ||
| Step 2 | Select
.
The Find and List Directory Numbers window opens. | ||
| Step 3 | Find and
select the appropriate directory number.
The Directory Number Configuration window opens. | ||
| Step 4 | Locate the Directory URIs section. | ||
| Step 5 | Specify a valid SIP URI in the URI column. | ||
| Step 6 | Select the
appropriate partition from the
Partition column.
| ||
| Step 7 | Add the partition to the appropriate calling search space so that users can place calls to the directory numbers. | ||
| Step 8 | Select Save. |
Associate the Directory URI Partition
You must associate the default partition into which Cisco Unified Communications Manager places URIs with a partition that contains directory numbers.
To enable URI dialing, you must associate the default directory URI partition with a partition that contains directory numbers.
If you do not already have a partition for directory numbers within a calling search space, you should create a partition and configure it as appropriate.
| Step 1 | Open the Cisco Unified CM Administration interface. |
| Step 2 | Select . The Enterprise Parameters Configuration window opens. |
| Step 3 | Locate the End User Parameters section. |
| Step 4 | In the Directory URI Alias Partition row, select the appropriate partition from the drop-down list. |
| Step 5 | Click Save. |
The default directory URI partition is associated with the partition that contains directory numbers. As a result, Cisco Unified Communications Manager can route incoming URI calls to the correct directory numbers.
You should ensure the partition is in the appropriate calling search space so that users can place calls to the directory numbers.
Enable FQDN in SIP Requests for Contact Resolution
To enable contact resolution with URIs, you must ensure that Cisco Unified Communications Manager uses the fully qualified domain name (FQDN) in SIP requests.
| Step 1 | Open the Cisco Unified CM Administration interface. |
| Step 2 | Select
.
The Find and List SIP Profiles window opens. |
| Step 3 | Find and
select the appropriate SIP profile.
You cannot edit the default SIP profile. If required, you should create a copy of the default SIP profile that you can modify. |
| Step 4 | Select Use Fully Qualified Domain Name in SIP Requests and then select Save. |
What to Do Next
Associate the SIP profile with all devices that have primary extensions to which you associate URIs.
Voicemail Avoidance
Applies to: All clients
Voicemail avoidance is a feature that prevents calls from being answered by the mobile service provider voice mail. This feature is useful if a user receives a Mobile Connect call from the enterprise on the mobile device. It is also useful when an incoming DvO-R call is placed to the mobile device.
You can set up voicemail avoidance in one of two ways:
Timer-controlled—(Default) With this method, you set timers on the Cisco Unified Communications Manager to determine if the call is answered by the mobile user or mobile service provider voicemail.
User-controlled—With this method, you set Cisco Unified Communications Manager to require that a user presses any key on the keypad of the device to generate a DTMF tone before the call can proceed.
If you deploy DvO-R, Cisco recommends that you also set user-controlled voicemail avoidance. If you set user-controlled Voicemail Avoidance, this feature applies to both DvO-R and Mobile Connect calls.
For more information about voicemail avoidance, see the Confirmed Answer and DvO VM detection section in the Cisco Unified Communications Manager Features and Services Guide for your release.
Set Up Timer-Controlled Voicemail Avoidance
Set up the timer control method by setting the Answer Too Soon Timer and Answer Too Late Timer on either the Mobility Identity or the Remote Destination. For more information, see the Add Mobility Identity or Add Remote Destination (Optional) topics.
Timer-controlled voicemail avoidance is supported on Cisco Unified Communications Manager, release 6.0 and later.
Set Up User-Controlled Voicemail Avoidance
User-controlled voicemail avoidance is available on Cisco Unified Communications Manager, release 9.0 and later.
Set up User-Controlled Voicemail Avoidance as follows:
-
Set up Cisco Unified Communications Manager using the Set Up Cisco Unified Communications Manager to Support Voicemail Avoidance topic.
-
Set up the device using one of the following topics:
Cisco does not support user-controlled voicemail avoidance when using DvO-R with alternate numbers that the end user sets up in the client. An alternate number is any phone number that the user enters in the DvO Callback Number field on the client that does not match the phone number that you set up on the user's Mobility Identity.
If you set up this feature with alternate numbers, the Cisco Unified Communications Manager connects the DvO-R calls even if the callback connects to a wrong number or a voicemail system.
Set Up Cisco Unified Communications Manager to Support Voicemail Avoidance
Use this procedure to set up the Cisco Unified Communications Manager to support user-controlled Voicemail Avoidance.
| Step 1 | Open the Cisco Unified CM Administration interface. | ||
| Step 2 | Select . | ||
| Step 3 | In the Server drop-down list, select the active Cisco Unified Communications Manager. | ||
| Step 4 | In the Service drop-down list, select the Cisco Call Manager (Active) service. | ||
| Step 5 | Configure the
settings in the
Clusterwide Parameters (System - Mobility Single Number Reach
Voicemail) section.
| ||
| Step 6 | Click Save. |
Enable Voicemail Avoidance on Mobility Identity
Use this procedure to enable user-controlled voicemail avoidance for the end user's mobility identity.
-
Set up the annunciator on the Cisco Unified Communications Manager. For more information, see the Annunciator setup section in the Cisco Unified Communications Manager Administrator Guide for your release.
-
If you set up a Media Resource Group on the Cisco Unified Communications Manager, set up the annunciator on the Media Resource Group. For more information, see the Media resource group setup section in the Cisco Unified Communications Manager Administrator Guide for your release.
| Step 1 | Open the Cisco Unified CM Administration interface. | ||
| Step 2 | Navigate to the device that you want to configure as follows: | ||
| Step 3 | In the
Associated Mobility Identity section, click the link
for the Mobility Identity.
| ||
| Step 4 | Set the
policies as follows:
| ||
| Step 5 | Click Save. |
Enable Voicemail Avoidance on Remote Destination
Use this procedure to enable user-controlled voicemail avoidance for the end user's remote destination.
-
Set up the annunciator on the Cisco Unified Communications Manager. For more information, see the Annunciator setup section in the Cisco Unified Communications Manager Administrator Guide for your release.
-
If you set up a Media Resource Group on the Cisco Unified Communications Manager, set up the annunciator on the Media Resource Group. For more information, see the Media resource group setup section in the Cisco Unified Communications Manager Administrator Guide for your release.
| Step 1 | Open the Cisco Unified CM Administration interface. |
| Step 2 | Navigate to the device that you want to configure as follows: |
| Step 3 | In the Associated Remote Destinations section, click the link for the associated remote destination. |
| Step 4 | Set the
policies as follows:
|
| Step 5 | Click Save. |
Feedback