[Index]
Overview
Single number reach (SNR) is the remote destination number configured for a subscriber.
Note
While you can add one or more Remote Destination Profiles (RDP) to a subscriber, only one RDP may be added to a subscriber's SNR service.
View and Manage Single Number Reach
This procedure displays, moves, exports, and updates existing single number reach (SNR) remote destination profiles (RDPs), and adds new RDPs for SNR. For example, you can configure ring schedules, choose a mobility profile and a single number reach voicemail policy, or set up answer too soon / answer too late timers.
Pre-requisites:
To view, add, or update a subscriber's SNR:
In the VOSS Automate Admin Portal, go to (default menu) Subscriber Management > Single Number Reach to open the Single Number Reach list view.
Note
You can also view a multi vendor subscriber's SNR details (line and mobile number) via (default menus) User Management > User Services > Multi Vendor Subscribers, then click the Edit icon (wrench) to update their SNR settings, or click the Delete icon to remove their SNR. See Multi Vendor Subscribers.
View existing single number reach (SNR) profiles.
Choose an option:
Delete - to delete one or more single number reach (SNR) instances, select the relevant SNR instances, then click Delete.
Move - to move one or more single number reach (SNR) instances, select the relevant SNR instances, then click Move. Choose the target hierarchy.
Export - to export one or more single number reach (SNR) instances, select the relevant SNR instances, then click Export.
Edit - to edit a single number reach (SNR) instance, click on the relevant instance to open its configuration page. Update the instance, then click Save.
Add - to add a single number reach (SNR) instance, click the Plus icon (+) to add a new record, then fill out configuration details, and click Save.
Mandatory. Choose a user ID where you want to assign the SNR profile.
Note
The subscriber must have Enable Mobility enabled. You can verify via, default menus, Subscriber Management > Subscribers, click on the subscriber, and select the User tab.
Mandatory. At Profile Name, fill out a remote destination profile (RDP) name, which must be their user name, followed by "-RDP". For example: jsmith-RDP.
Note
You can use a maximum of 50 characters in the RDP name. Valid characters include letters, numbers, dashes, dots (periods), spaces, and underscores.
Optional. Fill out a description for the RDP name.
Optional. Choose the relevant device pool.
Note
The device pool defines sets of common characteristics for devices, such as region, date/time group, softkey template, and MLPP information.
Optional, if relevant to your scenario. At Calling Search Space, choose the Calling Search Space (CSS) to be used for routing mobile voice access or enterprise feature access calls.
Note
Calling Search Space (CSS) is relevant here only when you're routing calls from the remote destination, which specifies the outbound call leg to the dialed number for Mobile Voice Access and Enterprise Feature Access calls.
Optional, if relevant to your scenario. At Rerouting Calling Search Space, choose a calling search space to be used to route Cisco Unified Mobility calls.
Note
Ensure that the gateway configured for routing mobile calls is assigned to the partition that belongs to the Rerouting Calling Search Space.
Cisco Unified Communications Manager (CUCM) determines how to route calls based on the remote destination number and the Rerouting Calling Search Space.
The Rerouting Calling Search Space setting applies only when you are routing calls to the remote destination or mobility identity, which specifies the outbound call leg toward the remote destination or mobility identity when a call comes in to the user enterprise number. Cisco Unified Mobility calls do not get routed to the dual-mode mobility identity number that corresponds to the dual-mode mobile phone number if the device associates with the enterprise WLAN and registers with CUCM.
Cisco Unified Mobility calls get routed to the dual-mode mobility identity number only when the device is outside the enterprise.
Mandatory. At Privacy, select the relevant privacy option for the RDP. Options are Off, On, Default.
Note
When selecting Default (the default value), the setting matches the value of the Privacy Setting service parameter. If you change and save the value for Privacy, you must return to the Remote Destination Profile Configuration window for a remote destination profile that specifies Default and save your changes.
You can't transfer a call from a cell phone to a desk phone if the value for Privacy is On, and "Enforce Privacy Setting on Held Calls" is True.
Select Dnd Status to enable Do not disturb on the phone, else, leave this checkbox clear.
At User Locale, choose the locale associated with the phone user interface.
Note
User locale defines phone details that supports users, such as language and font, on phone models that support localization. When selecting a locale other than English, ensure the locale installer is installed. Refer to the Cisco Unified Communications Manager documentation for locale installation.
At Network Locale, choose the location of the network.
At Lines, click the Plus icon (+) to add lines (one or more).
Note
Lines you add are listed by their unique ID.
The table describes the line configuration settings:
Inventory filter | Options are:
|
Pattern | Mandatory. |
Route partition name | Mandatory. |
Position | Integer. |
E164 Mask | String. |
Label | String. |
Display | String. |
Display Ascii | String. |
Recording media source | Options are:
|
Enduser | Add associated end users, one or more, and select their user ID. |
At Remote Destinations, click the Plus icon (+) to add remote destinations (one or more) associated with the profile.
The table describes the remote destination settings:
Setting | Description |
---|---|
Name | Fill out a name to identify the remote destination or mobile identity. |
Destination Number | Mandatory. The PSTN telephone number for the destination, including the area code. |
Mobile Smart Client Name | Not relevant for dualmode phones. |
Delay Before Ringing Timer | Mandatory. Default is 4,000 milliseconds. Enter the time that elapses before the mobile phone rings when a call is extended to the remote destination. Range: 0 - 30,000 milliseconds. Note that when using a hunt group, 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. |
Answer Too Soon Timer | Mandatory. Default is 1,500 milliseconds. Enter the minimum time, in milliseconds, that CUCM 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. Range: 0 - 10,000 milliseconds Default: Default: 1500 |
Answer Too Late Timer | Mandatory. Default is 19,000 milliseconds Enter the maximum time, in milliseconds, that Cisco Unified Communications Manager allows for the mobile phone to answer. Range: 0 and 10,000 - 300,000 milliseconds If the value is set to zero, the timer is not started. |
Mobility Profile | The mobility profile you want to use for this remote destination. |
Enable Unified Mobility |
Enable Mobile Connect | Defines whether to allow an incoming call to ring your desk phone and remote destination at the same time. Default is Tru |
Mobile Phone | Defines whether to have calls that the desk phone answers to be sent to a mobile phone as the remote destination. Set to True to ensure that, if Send Call to Mobile Phone is specified (by using the Mobility softkey for remote destination pickup), the call is extended to this remote destination. Not relevant for dual-mode phones that are running SIP nor to dual-mode phones that are running SCCP, such as the Nokia S |
Line Association | 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 databa For each line you add, choose the Pattern (a directory number, which is already associated to RDP), Route Partition Name. |
Single Number Reach Voicemail Policy | Choose a policy to define how mobile device users answer calls that terminate on a remote destination (RD). Users have a voice mail box for their mobility if the RD call reaches an external voice mail system. Options are:
User Control works only when Enable Enterprise Feature Access is set to True. |
Enable Extend and Connect | Disable if you wish to delete Extend and Connect |
Dial Via Office Reverse Voicemail | Define how dual mode device users answer Dial-via-Office Reverse (DVO-R) calls that terminate on the Mobile Identity (MI). Allows users with a single voicemail box for their mobility, if the RD call reaches an external voice mail system. Options are:
|
Client Services Framework or CTI Remote Device | ctiRemoteDeviceName tag will be used to associate either CTI Remote Device or a Cisco Spark Remote Device with a Remote Destination. |
Ring Schedule | Manage ring schedules (maximum of 7 members in the schedule) for single number reach, to define working days and hours, for one or more days of the wee These fields display only when the CUCM server version is v11.5 and up Only ring schedules added via the Admin Portal can be managed in the Admin Portal. Ring schedules added via Self-service can only be managed in Self-service. |
CUCM Single Number Reach (RDP / RD) based relation.
Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Protocol * | Protocol option is read-only,except when creating a device. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Network Hold MOH Audio Source | Choose the audio source from the IOS gateway that provides multicasting audio source for Cisco Unified Mobility and Mobile Voice Access calls. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User ID * | Choose the user to whom this profile is assigned. The selection must match the ID of a user in the End User Configuration window where Enable Mobility is checked. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User Hold Audio Source | Choose the audio option for users on hold for Cisco Unified Mobility and Mobile Voice Access calls. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Calling Search Space | Choose the calling search space to be used for routing Mobile Voice Access or Enterprise Feature Access calls. Note This calling search space setting applies only when you are routing calls from the remote destination, which specifies the outbound call leg to the dialed number for Mobile Voice Access and Enterprise Feature Access calls. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Mobile Smart Client Profile Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Network Locale |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Use Device Pool Calling Party Transformation CSS | To use the Calling Party Transformation CSS that is configured in the device pool that is assigned to this device, check this check box. If you do not check this check box, the device uses the Calling Party Transformation CSS that you configured in the Remote Destination Profile Configuration window. Default: True |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Product * | Product ID string. read-only except when creating a device. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Description | Enter a text description of the remote destination profile. This field can comprise up to 128 characters. You can use all characters except quotes (“), close angle bracket (>), open angle bracket (<), backslash (\), ampersand (&), and percent sign (%). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Ignore Presentation Indicators (internal calls only) | Check the check box if you want to ignore the connected line ID presentation. Use this configuration for internal calls. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
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, including language and font, to support users. Cisco Unified Communications Manager makes this field available only for phone models that support localization. Note If the users require information to display (on the phone) in any language other than English, verify that the locale installer is installed before you configure user locale. See the Cisco Unified Communications Manager Locale Installer documentation. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Class * | Class ID string. Class information is read-only except when creating a device. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Primary Phone Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Dnd Option | This Call Reject option specifies that no incoming call information gets presented to the user. Note For mobile devices, dual-mode phones, and phones that are running SCCP, 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 Status | Check this check box to enable Do Not Disturb on the phone. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Name * | Enter a text name for the remote destination profile. This name can comprise up to 50 characters. Valid characters include letters, numbers, dashes, dots (periods), spaces, and underscores. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Privacy * | Choose a privacy option for the remote destination profile. If you choose the Default value for this field, the setting matches the value of the Privacy Setting service parameter. Note If you change and save the value of the Privacy Setting service parameter, you must return to the Remote Destination Profile Configuration window for a remote destination profile that specifies Default and click Save for the service parameter change to take effect. Note You cannot transfer a call from a cell phone to a desk phone if the Remote Destination Profile Privacy specifies On, and the "Enforce Privacy Setting on Held Calls" service parameter specifies True. Default: Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Rerouting Calling Search Space | Choose a calling search space to be used to route Cisco Unified Mobility calls. Note Ensure that the gateway that is configured for routing mobile calls is assigned to the partition that belongs to the Rerouting Calling Search Space. Cisco Unified Communications Manager determines how to route calls based on the remote destination number and the Rerouting Calling Search Space. Note The Rerouting Calling Search Space setting applies only when you are routing calls to the remote destination or mobility identity, which specifies the outbound call leg toward the remote destination or mobility identity when a call comes in to the user enterprise number. Note Cisco Unified Mobility calls do not get routed to the dual-mode mobility identity number that corresponds to the dual-mode mobile phone number if the device associates with the enterprise WLAN and registers with Cisco Unified Communications Manager. Cisco Unified Mobility calls get routed to the dual-mode mobility identity number only when the device is outside the enterprise. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Protocol Side * | Side information is read-only except when creating a device Default: User |
|
|||||||||||||||||||||||||||||||||||||||||||||||
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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Display Ascii |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Associated Endusers |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enduser |
|
||||||||||||||||||||||||||||||||||||||||||||||||
User Id * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Ring Setting | Default: Ring |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Consecutive Ring Setting | Consecutive Rings Setting. Replaces the consective ring setting on IPPhone. Default: Use System Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Recording Profile Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Index |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Ring Setting Active Pickup Alert | Applicable only for IP Phones Default: Use System Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Label |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Recording Media Source | Default: Gateway Preferred |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Max Num Calls | Default: 2 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Partition Usage | This tag cannot be modified. It can only be specified in the add request. Default: General |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Recording Flag | Default: Call Recording Disabled |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Speed Dial |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Monitoring Css Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
E164Mask |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Missed Call Logging | Default: True |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Call Info Display |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Dialed Number | Default: True |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Redirected Number |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Caller Number |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Caller Name | Default: True |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Dirn | Only uuid attribute is returned in response |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Inventory Filter | Default: default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Pattern * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Route Partition Name * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Mwl Policy | Default: Use System Policy |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Ring Setting Idle Pickup Alert | Applicable only for IP Phones Default: Use System Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Busy Trigger | Default: 1 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Audible Mwi | Not applicable for gatewayEndpointAnalogAccess and CiscoCatalyst600024PortFXSGateway Default: Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Display |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Calling Party Transformation CSS | Choose the calling search space for transformations. This setting allows you to localize the calling party number on the device. Make sure that the Calling Party Transformation CSS that you choose contains the calling party transformation pattern that you want to assign to this device. Note The partitions in the calling search space should contain only calling party transformations. Note Ensure the calling search space is not null because no transformations can apply to null partitions. Note The device takes on the attributes of the Calling Party Transformation Pattern because you assign the pattern to a partition where the Calling Party Transformation CSS exists. For example, when you configure the Calling Party Transformation CSS under Call Routing > Class of Control > Calling Search Space, you assign the CSS to a partition; when you configure the Calling Party Transformation CSS under Call Routing > Transformation Pattern > Calling Party Transformation Pattern, you choose the partition where the Calling Party Transformation CSS is assigned. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Calling Search Space AAR | Choose a calling search space to be used to route Cisco Unified Mobility calls. Note Ensure that the gateway that is configured for routing mobile calls is assigned to the partition that belongs to the Rerouting Calling Search Space. Cisco Unified Communications Manager determines how to route calls based on the remote destination number and the Rerouting Calling Search Space. Note The Rerouting Calling Search Space setting applies only when you are routing calls to the remote destination or mobility identity, which specifies the outbound call leg toward the remote destination or mobility identity when a call comes in to the user enterprise number. Note Cisco Unified Mobility calls do not get routed to the dual-mode mobility identity number that corresponds to the dual-mode mobile phone number if the device associates with the enterprise WLAN and registers with Cisco Unified Communications Manager. Cisco Unified Mobility calls get routed to the dual-mode mobility identity number only when the device is outside the enterprise. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Device Pool * | Choose the device pool that applies to this profile. The device pool defines sets of common characteristics for devices, such as region, date/time group, softkey template, and MLPP information. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Destination |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Enable Extend And Connect | While UPDATE set it to false if you want to delete Enable Extend and Connect.Use only while update |
|
|||||||||||||||||||||||||||||||||||||||||||||||
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 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Mobile Smart Client Name | This tag is not applicable for dualmode phones |
|
|||||||||||||||||||||||||||||||||||||||||||||||
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 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
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 |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Tod Access Name | From 11.0 this tag will not get the precedence if ringSchedule tag is present because ring schedule of the RD will be set based on ringSchedule tag |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Dual Mode Device Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
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 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Client Services Framework or CTI Remote Device | ctiRemoteDeviceName tag will be used to associate either CTI Remote Device or a Cisco Spark Remote Device with a Remote Destination |
|
|||||||||||||||||||||||||||||||||||||||||||||||
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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Enable Unified Mobility | While UPDATE set it to false if you want to delete enable Unified Mobility feature.Use only while update |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Remote Destination Profile | From the drop-down list box, choose the remote destination profile that you want to use for this remote destination. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
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 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
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 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
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 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Ring Schedule | This tag must be used for configuring RingSchedule of RD, this tag will get precendence over todaccess and accesslist tag. Passing a blank ringSchedule tag in updateRemoteDestination request will result in setting the time schedule to All the time. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Member |
|
||||||||||||||||||||||||||||||||||||||||||||||||
End Day | Default: None |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Start Day | StartDay and EndDay value should be same Default: None |
|
|||||||||||||||||||||||||||||||||||||||||||||||
End Time | Default: No Office Hours |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Start Time | Default: No Office Hours |
|
|||||||||||||||||||||||||||||||||||||||||||||||
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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Blocked Access List | Click this radio button to prevent incoming calls from ringing this remote destination if the caller belongs to the access list that is specified in the drop-down list box and according to the Ring Schedule that you specify in the Ring Schedule pane. This setting applies only if the Enable Cisco Unified Mobility check box is checked for this remote destination. From the drop-down list box, choose an access list that applies to this setting. If you want to view the details of an access list, click the View Details link. (To modify an access list, you must use the Call Routing > Class of Control > Access List menu option.) Choosing an access list that contains no members equates to choosing the Always ring this destination radio button. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
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 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Name | Enter a name that identifies the remote destination or mobile identity. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
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 |
|