[Index]
Before You Begin
To ensure that the Add Phones work flows execute successfully, create and configure the following items first on Cisco Unified Communications Manager (Unified CM). Then import them into VOSS-4-UC:
During the end-to-end creation of providers, customers, and sites, default values are created (for example, Site ID). If the dial plan for the site specifies Device Pool, CSS, and Partition names, these are available for selection. To identify these site-related values, refer to the naming conventions used in Modify Site Defaults.
The Site Defaults Menu item populates certain default values for phones. To view and edit the menu (depending on your sign-in level), choose Site Management > Defaults and click the site name in the list view. For phone parameter information, use the fields on the General Defaults and Device Defaults tabs. Refer to Modify Site Defaults for additional information regarding the values to fill in for phone parameters such as partitions and CSSs.
Note
If the Enable CSS filtering check box is selected at the customer dial plan, then the list of available calling search spaces includes only those that are marked as a Class of Service under Dial Plan Management > Site > Class of Service at the particular site. You can add a custom CSS in a CSS field if you know the exact syntax.
If the Enable CSS filtering check box is clear, then the list of available calling search spaces includes all CSSs that are configured on Unified CM.
Use this procedure as a high-level workflow to configure one or more phones and associated settings. If the Number Inventory feature is enabled, phone lines are not added. Instead, phones are selected from a drop-down list of available numbers.
The Phones screen is an integrated display to add, modify, or delete the following on the Unified CM device:
When adding a device for a subscriber, ensure that the following properties of the selected device are related correctly:
Note
The Registration Status and IP Address columns in the Phones list view (filterable) or the field values on the instance form of a phone refer to the registration status and address of the phone on Unified CM, for example "None", "UnRegistered with CUCM-11-5-IP2", "Registered with CUCM-11-5-IP2".
These phone properties are automatically updated when an instance form of a phone is opened, and also by a service that runs periodically at a configured interval. Refer to the Metrics Configuration topic in the Advanced Configuration Guide for details on RIS API data collector interval.
Procedure
Tab | Description |
---|---|
Phone | Default values for Device Protocol, BAT Phone Template, Device Security Profile, and other fields are updated automatically based on the selected Product type. The Vendor Config area displays the configurable vendor features available for the selected phone type. Configure each field as required. The fields displayed vary depending on the selected Product (device type) and the Device Protocol (such as SIP or SCCP). The availability of the Vendor Config settings depends on the Field Display Policy. The supported features available for each phone type are retrieved from the related Unified CM. You can override the default Phone Button Template value by entering a custom value in the Phone Button Template field. The entered value will be applied on Unified CM if the Unified CM allows it for that phone type. Tip: If you don't see a template that you are looking for in the drop-down list (for example, for Phone Button Template, Device Security Profile or SIP Profile), edit the template on Unified CM, and then sync the template into VOSS-4-UC to have it appear in the drop-down list. Tip: If the Product type list does not contain the phone or endpoint you want, take the following steps. In Unified CM, install a COP file for the endpoint you want. Install the COP file only once for the Unified CM instance where the endpoint is added. Then in VOSS-4-UC, import the phone button template from Unified CM. Note: Follow these steps while creating a CTI Remote Device to enable Extend and Connect in VOSS-4-UC:
|
Lines | This tab serves two purposes.
The Lines sections reflect the Lines object in Unified CM. You can add lines to this group and associate lines with the device. You can add custom lines by entering a line in the drop-down list (depending on the status of the Number Inventory feature). |
Speed Dials | Allows you to configure speed dials for the device. Available speed dials depend on the device's Phone Button Template. The order in which Speed Dial entries are added matches the slots that are available in Unified CM. |
Services | Used to set IP Phone services. |
Busy Lamp Fields | Allows you to configure busy lamps for the device. Available busy lamp fields depend on the device's Phone Button Template. |
Blf Directed Call Parks | Allows you to configure Busy Lamp Field directed call parks for the device. Available BLF-directed call parks depend on the device's Phone Button Template. Create BLF-directed call parks in Call Routing > Directed Call Parks on Unified CM before configuring them from this tab. The available BLF-directed call parks match those created for each specific Route Partition Name. |
Tab | Description |
---|---|
Dual Mode Settings | Only applies to a Dual Mode Phone, Spark Remote Device, or CTI Remote Device, and allows you to enter the relevant Mobile Identity and Remote Destination (or CTI Remote Destination) parameters for the device. These parameters include Name, Destination Number, Owner User ID, Dual Mode Device Name (or CTI Remote Device), and Answer Too Soon and Too Late Timers. |
After you make changes to any phone model specific data in Unified CM, for example by loading a new BAT file, editing phone button templates, security profiles, and so on, then in order to utilize that data in VOSS-4-UC, you need to do a sync of the Unified CM.
Include the following models in the data sync - depending on what you changed:
If you do a full sync or full import this will make the changes available in VOSS-4-UC. However, between full syncs, it is best practice to create a sync setup with a model type list that includes the above model types. This allows you to run an ad-hoc sync with a very limited scope as needed - if changes are made in the Unified CM that require a sync.
If adding new phone types to the system, you may also need to edit your device groups and entitlement profiles (if used) to have them show as options to the correct users.
If the Enhanced INI Filtering feature is enabled, administrators have access to the Inventory Filter dropdown list menu for lines on the following forms:
The filter would typically be used to show a filtered, shorter dropdown list of directory numbers.
Note
If the Internal Number Inventory (INI) feature is not enabled, Enhanced INI Filtering will not be applied and all the list of numbers are obtained from the device.
The following options are available in the Inventory Filter list:
Default
This filter - enabled by default - corresponds with the standard filter of Directory Numbers:
Show Unused Numbers with Associated E164's (Site Only)
Show Unused Numbers with Associated E164's
Show Used Numbers (Site Only)
Show Used Numbers
Show Numbers belonging to this Subscriber
Phone based relation.
Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
Phone | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Registration Status | Registration status of the phone |
|
|||||||||||||||||||||||||||||||||||||||||||||||
IP Address | IP address of the phone |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Device Name * | Enter a name to identify software-based telephones, H.323 clients, and CTI ports. For device names that are not based on a MAC address, as a general rule, you can enter 1 to 15 characters comprised of alphanumeric characters (a-z, A-D, 0-9). In most cases you can use dot (.), dash (-), and underscore (_) as well. Tip Because the rules for the device name field depend on the device type, Cisco recommends that you see the product documentation to determine which character set is valid for your device, as well as the number of characters allowed. For example, when you configure the device name for the Cisco Unified Personal Communicator, make sure that the name starts with UPC. Note Ensure that the device name of a Cisco Unified Mobile Communicator does not exceed 15 characters. If the device name of a Cisco Unified Mobile Communicator exceeds 15 characters, migration of this device will fail upon upgrade to a different release of Cisco Unified Communications Manager. If an existing Cisco Unified Mobile Communicator device name specifies a longer name, shorten the device name to 15 or fewer characters. Cisco Unified Mobile Communicator supports dual mode phones. The preceding limit of 15 characters also applies to Cisco Unified Mobile Communicator dual mode. When the MI for a dual mode phone is longer than 15 characters, the cellular network rejects the phone registration. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Product * | Product ID string. read-only except when creating a device. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Description | Identify the purpose of the device. You can enter the user name (such as John Smith) or the phone location (such as Lobby) in this field. For Cisco VG248 gateways, begin the description with VGC<mac address>. The description can include up to 128 characters in any language, but it cannot include double-quotes ("), percentage sign (%), ampersand (&), back-slash (\), or angle brackets (<>). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Device Protocol * | Protocol option is read-only,except when creating a device. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Phone Button Template * | Choose the appropriate phone button template. The phone button template determines the configuration of buttons on a phone and identifies which feature (line, speed dial, and so on) is used for each button. Cisco Unified CM does not make this field available for H.323 clients or CTI ports. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Device Security Profile | Choose the security profile to apply to the device. You must apply a security profile to all phones that are configured in Cisco Unified Communications Manager Administration. Installing Cisco Unified Communications Manager provides a set of predefined, nonsecure security profiles for auto-registration. To enable security features for a phone, you must configure a new security profile for the device type and protocol and apply it to the phone. If the phone does not support security, choose a nonsecure profile. To identify the settings that the profile contains, choose System > Security Profile > Phone Security Profile. Note The CAPF settings that are configured in the profile relate to the Certificate Authority Proxy Function settings that display in the Phone Configuration window. You must configure CAPF settings for certificate operations that involve manufacturer-installed certificates (MICs) or locally significant certificates (LSC). See the Cisco Unified Communications Manager Security Guide for more information about how CAPF settings that you update in the phone configuration window affect security profile CAPF settings. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Softkey Template | Choose the appropriate softkey template. The softkey template determines the configuration of the softkeys on Cisco Unified IP Phones. Leave this field blank if the common device configuration contains the assigned softkey template. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Common Phone Profile * | From the drop-down list box, choose a common phone profile from the list of available common phone profiles. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Calling Search Space | From the drop-down list box, choose the appropriate calling search space (CSS). A calling search space comprises a collection of partitions that are searched to determine how a dialed number should be routed. The calling search space for the device and the calling search space for the directory number get used together. The directory number CSS takes precedence over the device CSS. Note When set to <none>, Unified CM uses the device mobility calling search space, which is configured on the device pool. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Device Pool Name * | Choose the device pool to which you want this phone assigned. The device pool defines sets of common characteristics for devices, such as region, date/time group, and softkey template. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Location * | Use locations to implement call admission control (CAC) in a centralized call-processing system. CAC enables you to regulate audio quality and video availability by limiting the amount of bandwidth that is available for audio and video calls over links between locations. The location specifies the total bandwidth that is available for calls to and from this location. From the drop-down list box, choose the appropriate location for this Cisco Unified IP Phone. A location setting of Hub_None means that the locations feature does not keep track of the bandwidth that this Cisco Unified IP Phone consumes. A location setting of Phantom specifies a location that enables successful CAC across intercluster trunks that use H.323 protocol or SIP. To configure a new location, use the System > Location menu option. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
BLF Presence Group |
|
||||||||||||||||||||||||||||||||||||||||||||||||
SIP Profile | Choose the default SIP profile or a specific profile that was previously created. SIP profiles provide specific SIP information for the phone such as registration and keepalive timers, media ports, and do not disturb control. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Digest User | This field is applicable only to SIP phones. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Device Mobility Mode * | From the drop-down list box, turn the device mobility feature on or off for this device or choose Default to use the default device mobility mode. Default setting uses the value for the Device Mobility Mode service parameter for the device. Click View Current Device Mobility Settings to display the current values of these device mobility parameters: Cisco Unified Communications Manager Group Roaming Device Pool Location Region Network Locale AAR Group AAR Calling Search Space Device Calling Search Space Media Resource Group List SRST Default: Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Rerouting Calling Search Space | From the drop-down list box, choose a calling search space to use for rerouting. The rerouting calling search space of the referrer gets used to find the route to the refer-to target. When the Refer fails due to the rerouting calling search space, the Refer Primitive rejects the request with the "405 Method Not Allowed" message. The redirection (3xx) primitive and transfer feature also uses the rerouting calling search space to find the redirect-to or transfer-to target. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
SUBSCRIBE Calling Search Space | Supported with the Presence feature, the SUBSCRIBE calling search space determines how Cisco Unified CM routes presence requests that come from the phone. This setting allows you to apply a calling search space separate from the call-processing search space for presence (SUBSCRIBE) requests for the phone. From the drop-down list box, choose the SUBSCRIBE calling search space to use for presence requests for the phone. All calling search spaces that you configure in Cisco Unified Communications Manager Administration display in the SUBSCRIBE Calling Search Space drop-down list box. If you do not select a different calling search space for the end user from the drop-down list, the SUBSCRIBE calling search space defaults to None. To configure a SUBSCRIBE calling search space specifically for this purpose, you configure a calling search space as you do all calling search spaces. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
DND Option | When you enable DND on the phone, this parameter allows you to specify how the DND features handle incoming calls: Call Reject—This option specifies that no incoming call information gets presented to the user. Depending on how you configure the DND Incoming Call Alert parameter, the phone may play a beep or display a flash notification of the call. Ringer Off—This option turns off the ringer, but incoming call information gets presented to the device, so the user can accept the call. Use Common Phone Profile Setting—This option specifies that the DND Option setting from the Common Phone Profile window will get used for this device. Note For 7940/7960 phones that are running SCCP, you can only choose the Ringer Off option. For mobile devices and dual-mode phones, you can only choose the Call Reject option. When you activate DND Call Reject on a mobile device or dual-mode phone, no call information gets presented to the device. Default: Ringer Off |
|
|||||||||||||||||||||||||||||||||||||||||||||||
DND Incoming Call Alert | When you enable the DND Ringer Off or Call Reject option, this parameter specifies how a call displays on a phone. From the drop-down list, choose one of the following options: None—This option specifies that the DND Incoming Call Alert setting from the Common Phone Profile window gets used for this device. Disable—This option disables both beep and flash notification of a call, but, for the DND Ringer Off option, incoming call information still gets displayed. For the DND Call Reject option, no call alerts display, and no information gets sent to the device. Beep Only—For an incoming call, this option causes the phone to play a beep tone only. Flash Only—For an incoming call, this option causes the phone to display a flash alert. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Do Not Disturb | Check this check box to enable Do Not Disturb on the phone. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Enable Extension Mobility | Check this check box if this phone supports extension mobility. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Is Dual Mode | Read-only tag. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Allow CTI Control Flag | Check this check box to allow CTI to control and monitor this device. If the associated directory number specifies a shared line, the check box should be enabled as long as at least one associated device specifies a combination of device type and protocol that CTI supports. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Hot line Device | This tag is applicable for PLAR-supporting SIP/SCCP phones only |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Mobility User ID | From the drop-down list box, choose the user ID of the person to whom this dual-mode phone is assigned. Note The Mobility User ID configuration gets used for the Cisco Unified Mobility and Mobile Voice Access features for dual-mode phones. The Owner User ID and Mobility User ID can differ. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Primary Phone * | Choose the physical phone that will be associated with the application, such as IP communicator or Cisco Unified Personal Communicator. When you choose a primary phone, the application consumes fewer device license units and is considered an "adjunct" license (to the primary phone). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User Locale | From the drop-down list box, choose the locale that is associated with the phone user interface. The user locale identifies a set of detailed information to support users, including language and font. Cisco Unified CM makes this field available only for phone models that support localization. Note If no user locale is specified, Cisco Unified Communications Manager uses the user locale that is associated with the common device configurations. If the users require that information be displayed (on the phone) in any language other than English, verify that the locale installer is installed before configuring user locale. See the Cisco Unified Communications Manager Locale Installer documentation. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Network Locale | From the drop-down list box, choose the locale that is associated with the phone. The network locale contains a definition of the tones and cadences that the phone in a specific geographic area uses. Cisco Unified CM makes this field available only for phone models that support localization. Note If no network locale is specified, Cisco Unified CM uses the network locale that is associated with the device pool. If users require that country-specific tones be played (on the phone), verify that the locale is installed before configuring the network locale. See the Cisco Unified Communications Manager Locale Installer documentation. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Owner User ID | From the drop-down list box, choose the user ID of the assigned phone user. The user ID gets recorded in the call detail record (CDR) for all calls made from this device. Assigning a user ID to the device also moves the device from "Unassigned Devices" to "Users" in the License Usage Report. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Vendor Config |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Key |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Value |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Lines |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Line | An XLine is an entry in the DeviceNumPlanMap table. The actual directory number is referenced inside the XLine object by the "dirn" or "dirnId" element. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Link To Line | Link to the line resource |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Dirn | Only uuid attribute is returned in response |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Pattern * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Route Partition Name * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Position |
|
||||||||||||||||||||||||||||||||||||||||||||||||
E164Mask |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Label |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Display |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Display Ascii |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Associated Endusers |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enduser |
|
||||||||||||||||||||||||||||||||||||||||||||||||
User Id * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Speeddials |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Speeddial |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Dirn * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Position |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Label |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Services |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Service |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Service Name Ascii |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Url |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Url Button Index |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Url Label |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Busy Lamp Fields |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Busy Lamp Field |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Blf Dest | Either blfDest or the combination of blfDirn and routePartition is to be mentioned in the add/update request, if both are mentioned AXL will read only the blfDest tag and ignore blfDirn and routePartition. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Blf Dirn | Either blfDest or the combination of blfDirn and routePartition is to be mentioned in the add/update request, if both are mentioned AXL will read only the blfDest tag and ignore blfDirn and routePartition. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Position |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Label |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Route Partition |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Blf Directed Call Parks |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Blf Directed Call Park |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Label |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Position |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Directed Call Park Id | Only the uuid attribute is read |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Directed Call Park Dn And Partition |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Dn Pattern * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Route Partition Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Remote Destinations | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Remote Destination |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Name | Enter a name that identifies the remote destination or mobile identity. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Destination Number * | Enter the PSTN telephone number for the destination. Include the area code and any additional digits that are required to obtain an outside line. Maximum field length equals 24 characters; individual characters can take the values 0-9, *, #, and +. Cisco recommends that you configure the caller ID of the remote destination. If the administrator configures the Incoming Calling Party settings in the Cisco Unified Communications Manager gateway, trunk, or device pool to globalize the incoming calling party number, configure the Destination Number of the remote destination in the E.164 format. Example: For a remote destination with US area code 408 and destination number 5552222, configure the Destination Number as +14085552222. Additionally, if globalized destination numbers are in use, set the Matching Caller ID with Remote Destination service parameter to Complete Match. Note Add the necessary translation pattern or route patterns to route the destination number. You can also enter a directory URI in this field. Keep in mind that if you enter a directory URI in this field, you must also configure a domain-based SIP route pattern. Note When you place a call from a remote destination, the caller ID of the destination phone displays the directory number that is associated with the calling directory URI rather than the directory URI. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Dual Mode Device Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Answer Too Soon Timer * | Enter the minimum time in milliseconds that Cisco Unified Communications Manager requires the mobile phone to ring before answering the call. This setting accounts for situations where the mobile phone is switched off or is not reachable, in which case the network may immediately divert the call to the mobile phone voice mail. If the mobile phone is answered before this timer expires, Cisco Unified Communications Manager pulls the call back to the enterprise. Range: 0 - 10,000 milliseconds Default: 1,500 milliseconds Default: 1500 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Answer Too Late Timer * | Enter the maximum time in milliseconds that Cisco Unified Communications Manager allows for the mobile phone to answer. If this value is reached, Cisco Unified Communications Manager stops ringing the mobile phone and pulls the call back to the enterprise. Range: 0 and 10,000 - 300,000 milliseconds Default: 19,000 milliseconds If the value is set to zero, the timer is not started. Default: 19000 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Delay Before Ringing Timer * | Enter the time that elapses before the mobile phone rings when a call is extended to the remote destination. Range: 0 - 30,000 milliseconds Default: 4,000 milliseconds Tip When a hunt group is in use, the lines ring only for a short period of time. You may need to manipulate the Delay Before Ringing Timer setting and make it zero to allow a remote destination call to be established, ring, and answer, before the hunt list timer expires and pulls the call back. Default: 4000 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Time Zone | From the drop-down list box, choose a time zone to use for this remote destination or mobile identity. Note The time-of-day access feature uses the time zone that you choose for this remote destination or mobile identity to allow or to block calls to this remote destination or mobile identity. Default: Etc/GMT |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Mobile Smart Client Name | This tag is not applicable for dualmode phones |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Mobility Profile | From the drop-down list box, choose the mobility profile that you want to use for this remote destination. To configure a mobility profile, use the Call Routing > Mobility > Mobility Profile menu option. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Single Number Reach Voicemail Policy | Configures how mobile device users answer calls that terminate on a remote destination (RD). This feature provides users with a single enterprise voice mail box for their enterprise mobility if the RD call reaches an external voice mail system. Available options are as follows: Use System Default Timer Control User Control Note For User Control to work, you must set the Enable Enterprise Feature Access service parameter to TRUE. Default: Use System Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Dial Via Office Reverse Voicemail | Configures how dual mode device users answer Dial-via-Office Reverse (DVO-R) calls that terminate on the Mobile Identity (MI). This feature provides users with a single enterprise voicemail box for their enterprise mobility if the RD call reaches an external voice mail system. Available options are as follows: Use System Default Timer Control User Control Default: Use System Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Enable Mobile Connect | Check the check box to allow an incoming call to ring your desk phone and remote destination at the same time. For detailed task information about Cisco Unified Mobility and Extend and Connect, see the Feature Configuration Guide for Cisco Unified Communications Manager. Default: True |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Mobile Phone | Check the check box if you want calls that the desk phone answers to be sent to your mobile phone as the remote destination. Checking this check box ensures that, if Send Call to Mobile Phone is specified (by using the Mobility softkey for remote destination pickup), the call gets extended to this remote destination. Note This check box does not apply to dual-mode phones that are running SIP nor to dual-mode phones that are running SCCP, such as the Nokia S60. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Line Associations | The line association for this remote destination. The line to be associated must already be added to the remote destination profile. All directory numbers specified must already exist in the database. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Line Association |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Pattern | The directory number to be associated. This directory number must be already associated to remote destination profile. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Route Partition Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Extend And Connect | While UPDATE set it to false if you want to delete Enable Extend and Connect.Use only while update |
|
|||||||||||||||||||||||||||||||||||||||||||||||
CTI Remote Device | ctiRemoteDeviceName tag will be used to associate either CTI Remote Device or a Cisco Spark Remote Device with a Remote Destination |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Owner User Id | From 10.5, to get proper value of this tag in get handler's response it is required to have value of todaccess, in case if user does not give any value in todaccesss tag, axl will insert a random row so that get handler response can return proper value of Owner User id |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Enable Unified Mobility | While UPDATE set it to false if you want to delete enable Unified Mobility feature.Use only while update |
|