[Index]
| Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
| Directory | Enter the server from which the phone obtains directory information. Leave this field blank to accept the default setting. Note If you set a Secured Directory URL enterprise parameter in the Enterprise Parameters Configuration window, that value overwrites the value of this field. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Device Protocol * | Protocol option is read-only,except when creating a device. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Secure Information URL | Enter the secure URL for the server location where the Cisco Unified IP Phone can find help text information. This information displays when the user presses the information (i) button or the question mark (?) button. Note If you do not provide a Secure Information URL, the device uses the nonsecure URL. If you provide both a secure URL and a nonsecure URL, the device chooses the appropriate URL, based on its capabilities. To accept the default setting, leave this field blank. Maximum length: 255 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Authentication Mode | This field allows you to choose the authentication method that the phone uses during the CAPF certificate operation. From the drop-down list box, choose one of the following options: By Authentication String—Installs/upgrades, deletes, or troubleshoots a locally significant certificate only when the user enters the CAPF authentication string on the phone. By Null String— Installs/upgrades, deletes, or troubleshoots a locally significant certificate without user intervention. This option provides no security; Cisco strongly recommends that you choose this option only for closed, secure environments. By Existing Certificate (Precedence to LSC)—Installs/upgrades, deletes, or troubleshoots a locally significant certificate if a manufacture-installed certificate (MIC) or locally significant certificate (LSC) exists in the phone. If a LSC exists in the phone, authentication occurs via the LSC, regardless whether a MIC exists in the phone. If a MIC and LSC exist in the phone, authentication occurs via the LSC. If a LSC does not exist in the phone, but a MIC does exist, authentication occurs via the MIC. Before you choose this option, verify that a certificate exists in the phone. If you choose this option and no certificate exists in the phone, the operation fails. At any time, the phone uses only one certificate to authenticate to CAPF even though a MIC and LSC can exist in the phone at the same time. If the primary certificate, which takes precedence, becomes compromised for any reason, or, if you want to authenticate via the other certificate, you must update the authentication mode. By Existing Certificate (Precedence to MIC)—Installs, upgrades, deletes, or troubleshoots a locally significant certificate if a LSC or MIC exists in the phone. If a MIC exists in the phone, authentication occurs via the MIC, regardless whether a LSC exists in the phone. If a LSC exists in the phone, but a MIC does not exist, authentication occurs via the LSC. Before you choose this option, verify that a certificate exists in the phone. If you choose this option and no certificate exists in the phone, the operation fails. Note The CAPF settings that are configured in the Phone Security Profile window interact with the CAPF parameters that are configured in the Phone Configuration window. Default: By Null String |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Require DTMF Reception | For phones that are running SIP and SCCP, check this check box to require DTMF reception for this phone. Note In configuring Cisco Unified Mobility features, when using intercluster DNs as remote destinations for an IP phone via SIP trunk (either intercluster trunk [ICT] or gateway), check this check box so that DTMF digits can be received out of band, which is crucial for Enterprise Feature Access midcall features. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| BAT Phone 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Mra Service Domain |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Calling Party Transformation CSS | From the drop-down list box, choose the calling search space (CSS) that contains the calling party transformation pattern that you want to apply on the calling number when this phone initiates a call. Cisco Unified CM transforms the calling party using the digit transformations configured on the matching calling party transformation pattern when this phone initiates a call. This setting allows you to transform the calling party number before Cisco Unified CM routes the call. For example, a transformation pattern can change a phone extension to an E.164 number. This setting is generally configured when a user dials using a URI instead of digits. Cisco Unified CM allows calling party transformations on various patterns when dialing using digits, this setting provides similar transformation provision even when dialing using a URI. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Use Trusted Relay Point * | From the drop-down list box, enable or disable whether Cisco Unified CM inserts a trusted relay point (TRP) device with this media endpoint. Choose one of the following values: Default—If you choose this value, the device uses the Use Trusted Relay Point setting from the common device configuration with which this device associates. Off—Choose this value to disable the use of a TRP with this device. This setting overrides the Use Trusted Relay Point setting in the common device configuration with which this device associates. On—Choose this value to enable the use of a TRP with this device. This setting overrides the Use Trusted Relay Point setting in the common device configuration with which this device associates. A Trusted Relay Point (TRP) device designates an MTP or transcoder device that is labeled as Trusted Relay Point. Cisco Unified CM places the TRP closest to the associated endpoint device if more than one resource is needed for the endpoint (for example, a transcoder or RSVPAgent). If both TRP and MTP are required for the endpoint, TRP gets used as the required MTP. If both TRP and RSVPAgent are needed for the endpoint, Cisco Unified CM first tries to find an RSVPAgent that can also be used as a TRP. If both TRP and transcoder are needed for the endpoint, Cisco Unified CM first tries to find a transcoder that is also designated as a TRP. Default: Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| BLF Audible Alert Setting (Phone Busy) | This setting determines the BLF audible alert setting when at least one active call exists on the BLF DN, but no call pickup alerts exist: On—An audible alert sounds. Off—No audible alert sounds. Default—The configuration in the Service Parameters Configuration window determines the alert option. Default: Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Msisdn | Mobile Subscriber ISDN |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| 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 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Elin Group |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Outbound Call Rollover | Use this setting for the Cisco Unified IP Phone 7931. No Rollover—Conference and transfer will not work in this mode. If a user attempts to use either of these features, the phone status displays as "Error Pass Limit." Choose this setting only if you need to support CTI applications. Rollover Within Same DN—Conferences and call transfers complete by using the same directory number (on different lines). For example, consider a phone that has directory number 1506 that is assigned to both Line 6 and 7. The user has an active call on Line 6 and decides to transfer the call. When the user presses the Transfer button, the call on Line 6 gets placed on hold, and a new call initiates on Line 7 to complete the transfer. Rollover to any line—Conferences and call transfers complete by using a different directory number and line than the original call. For example, consider a phone that has directory number 1507 assigned to Line 8 and directory number 1508 assigned to Line 9. The user has an active call on Line 8 and decides to transfer the call. When the user presses the Transfer button, the call on Line 8 gets placed on hold, and a new call initiates on Line 9 to complete the transfer. Default: No Rollover |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| IP Address | IP address of the phone |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| 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). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Retry Video Call as Audio | This check box applies only to video endpoints that receive a call. If this phone receives a call that does not connect as video, the call tries to connect as an audio call. By default, the system checks this check box to specify that this device should immediately retry a video call as an audio call (if it cannot connect as a video call) prior to sending the call to call control for rerouting. If you uncheck this check box, a video call that fails to connect as video does not try to establish as an audio call. The call then fails to call control, and call control routes the call via automatic alternate routing (AAR) and/or route/hunt list. Default: True |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Privacy | For each phone that wants Privacy, choose On in the Privacy drop-down list box. Default: Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Geo Location Filter Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Services Provisioning | From the drop-down list box, choose how the phone will support the services: Internal—The phone uses the phone configuration file to support the service. Choose this option or Both for Cisco-provided default services where the Service URL has not been updated; that is, the service URL indicates Application:Cisco/<name of service>; for example, Application:Cisco/CorporateDirectory. Choose Internal or Both for Cisco-signed Java MIDlets because Cisco-signed Java MIDlets are provisioned in the configuration file. External URL—Choosing External URL indicates that the phone ignores the services in the phone configuration file and retrieves the services from a Service URL. If you configured a custom Service URL for a service, including a Cisco-provided default service, you must choose either External URL or Both; if you choose Internal in this case, the services that are associated with the custom URLs do not work on the phone. Both—Choosing Both indicates that the phone support both the services that are defined in the configuration file and external applications that are retrieved from service URLs. Default: Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Key Order | keyOrder can be updated only if certificateOperation field is Install/Upgrade,Delete or Troubleshoot. Default: RSA Only |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Secure Directory URL | Enter the secure URL for the server from which the phone obtains directory information. This parameter specifies the URL that secured Cisco Unified IP Phones use when you press the Directory button. Note If you do not provide a Secure Directory URL, the device uses the nonsecure URL. If you provide both a secure URL and a nonsecure URL, the device chooses the appropriate URL, based on its capabilities. Leave this field blank to accept the default setting. Maximum length: 255 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Always Use Prime Line for Voice Message | From the drop-down list box, choose one of the following options: On—If the phone is idle, the primary line on the phone becomes the active line for retrieving voice messages when the phone user presses the Messages button on the phone. Off—If the phone is idle, pressing the Messages button on the phone automatically dials the voice-messaging system from the line that has a voice message. Cisco Unified CM always selects the first line that has a voice message. If no line has a voice message, the primary line gets used when the phone user presses the Messages button. Default—Cisco Unified CM uses the configuration from the Always Use Prime Line for Voice Message service parameter, which supports the Cisco CallManager service. Default: Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Mtp Required | This field is applicable only to SIP phones. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Secure Messages URL | Enter the secure URL for the messages server. The Cisco Unified IP Phone contacts this URL when the user presses the Messages button. Note If you do not provide a Secure Messages URL, the device uses the nonsecure URL. If you provide both a secure URL and a nonsecure URL, the device chooses the appropriate URL, based on its capabilities. To accept the default setting, leave this field blank. Maximum length: 255 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Key Size (Bits) | For this setting that is used for CAPF, choose the key size for the certificate from the drop-down list box. The default setting equals 1024. Other options include 512 and 2048. If you choose a higher key size than the default setting, the phones take longer to generate the entropy that is required to generate the keys. Key generation, which is set at low priority, allows the phone to function while the action occurs. Depending on the phone model, you may notice that key generation takes up to 30 or more minutes to complete. Note The CAPF settings that are configured in the Phone Security Profile window interact with the CAPF parameters that are configured in the Phone Configuration window. Default: 2048 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Proxy Server | Enter the host and port (for example, proxy.cisco.com:80) that are used to proxy HTTP requests for access to non-local host addresses from the phone HTTP client. The rule contains two parts for when to use the proxy server parameter: The hostname contains a "." The hostname specifies an IP address in any form. If you do not configure this URL, the phone attempts to connect directly to the URL. To accept the default setting, leave this field blank. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Add On Modules | Additional modules attached to the Phone.There can be 0,1, 2 or 3. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Add On Module |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Module 3 Load Name * | Enter the custom software for the appropriate expansion module, if applicable. The value that you enter overrides the default value for the current model. Ensure the firmware load matches the module load. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Model * | Model ID string. Default: 7914 14-Button Line Expansion Module |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Module 3 | Choose the appropriate expansion module or none. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Authentication String | If you chose the By Authentication String option in the Authentication Mode drop-down list box, this field applies. Manually enter a string or generate a string by clicking the Generate String button. Ensure that the string contains 4 to 10 digits. To install, upgrade, delete, or troubleshoot a locally significant certificate, the phone user or administrator must enter the authentication string on the phone. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Require off-premise location | Check this check box if the device inserted requires off-premise location update upon registration. Off-premise location update is required when the device location cannot be detected automatically by Cisco Emergency Responder. Check this check box only for remote or mobile devices that change locations frequently. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Phone Activation Code | The provisioning code which must be entered on the phone |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Protected Device | Check this check box to designate a phone as protected, which enables the phone to play a 2-second tone to notify the user when a call is encrypted and both phones are configured as protected devices. The tone plays for both parties when the call is answered. The tone does not play unless both phones are protected and the call occurs over encrypted media. Checking this check box represents only one of several configuration requirements for the secure indication tone to play. For a detailed description of the secure indication tone feature and the configuration requirements, see the Cisco Unified Communications Manager Security Guide . If you check this check box and the system determines that the call is not encrypted, the phone plays nonsecure indication tone to alert the user that the call is not protected. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Allow Control of Device from CTI | 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| RFC2833 Disabled | For phones that are running SCCP, check this check box to disable RFC2833 support. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Hlog Status |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Operation Completes By | The completion deadline for the operation (CCYY:MM:DD:HH:MM) |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Is Active | The Device Is Active message in the Phone Configuration window in Cisco Unified Communications Manager Administration displays when a phone consumes device license units and when a phone can register with Cisco Unified CM. For a phone that uses a real MAC address, not the dummy MAC address that is created via BAT, the Device Is Active message displays, which indicates that the phone uses device license units and can register with Cisco Unified Communications Manager. For a phone that uses the dummy MAC address that is created via BAT, the Device Is Active message does not display. If you manually convert the dummy MAC address to a real MAC address in the Phone Configuration window, the Device Is Active message displays after you save the configuration; this ensures that the phone can register with Cisco Unified Communications Manager and that licensing consumes device license units for the phone. Default: True |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Allow iX Applicable Media | This field is applicable only for Third-party AS-SIP Endpoint. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Hot line Device | This tag is applicable for PLAR-supporting SIP/SCCP phones only |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Protocol Side * | Side information is read-only except when creating a device Default: User |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| MLPP Domain ID | Choose an MLPP domain from the drop-down list box for the MLPP domain that is associated with this device. If you leave the None value, this device inherits its MLPP domain from the value that was set in the common device configuration. If the common device configuration does not have an MLPP domain setting, this device inherits its MLPP domain from the value that was set for the MLPP Domain Identifier enterprise parameter. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| AAR Group | Choose the automated alternate routing (AAR) group for this device. The AAR group provides the prefix digits that are used to route calls that are otherwise blocked due to insufficient bandwidth. If no AAR group is specified, Cisco Unified CM uses the AAR group that is associated with Device Pool or Line. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Media Resource Group List | Choose the appropriate Media Resource Group List. A Media Resource Group List comprises a prioritized grouping of media resource groups. An application chooses the required media resource, such as a Music On Hold server, from the available media resources according to the priority order that is defined in a Media Resource Group List. If you choose <None>, Cisco Unified CM uses the Media Resource Group List that is defined in the device pool. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Device Pool * | 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Is Dual Mode | Read-only tag. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Vendor Config |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Value |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Key |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Authentication Server | Enter the URL that the phone uses to validate requests that are made to the phone web server. If you do not provide an authentication URL, the advanced features on the Cisco Unified IP Phone that require authentication will not function. By default, this URL accesses a Cisco Unified Communications Self Care Portal window that was configured during installation. Leave this field blank to accept the default setting. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Certificate Operation * | From the drop-down list box, choose one of the following options: No Pending Operation—Displays when no certificate operation is occurring (default setting). Install/Upgrade—Installs a new or upgrades an existing locally significant certificate in the phone. Delete—Deletes the locally significant certificate that exists in the phone. Troubleshoot—Retrieves the locally significant certificate (LSC) or the manufacture installed certificate (MIC), so you can view the certificate credentials in the CAPF trace file. If both certificate types exist in the phone, Cisco Unified CM creates two trace files, one for each certificate type. By choosing the Troubleshooting option, you can verify that an LSC or MIC exists in the phone. For more information on CAPF operations, see the Cisco Unified Communications Manager Security Guide . Default: No Pending Operation |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| User Hold MOH Audio Source | To specify the audio source that plays when a user initiates a hold action, click the drop-down arrow and choose an audio source from the list that displays. If you do not choose an audio source, Cisco Unified CM uses the audio source that is defined in the device pool or the system default if the device pool does not specify an audio source ID. Note You define audio sources in the Music On Hold Audio Source Configuration window. For access, choose Media Resources > Music On Hold Audio Source. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| EM Profile | The name of the default profile for this device.Not Nullable. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Enable Call Routing To Rd When None Is Active | Determines whether calls should be routed to all remote destinations when the active remote destination is not set. Check this check box to receive calls during network connection outage or to use a third-party voicemail system. Note This field appears only on a CTI remote device type. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| MLPP Preemption | Be aware that this setting is not available on all devices. If available, this setting specifies whether a device that can preempt calls in progress will use the capability when it places an MLPP precedence call. From the drop-down list box, choose a setting to assign to this device from the following options: Default—This device inherits its MLPP preemption setting from the common device configuration. Disabled—This device does not allow preemption of lower precedence calls to take place when necessary for completion of higher precedence calls. Forceful—This device allows preemption of lower precedence calls to take place when necessary for completion of higher precedence calls. Note Do not configure a device with the following combination of settings: MLPP Indication is set to Off or Default (when default is Off) while MLPP Preemption is set to Forceful. Default: Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Single Button Barge | From the drop-down list box, enable or disable the Single Button Barge/cBarge feature for this device or choose Default to use the service parameter setting. Off—This setting disables the Single Button Barge/cBarge feature; however, the regular Barge or cBarge features will still work. Barge—This setting enables the Single Button Barge feature. CBarge—This setting enables the Single Button cBarge feature. Default—Uses the Single Button Barge/cBarge setting that is in the service parameter. Default: Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Messages | Leave this field blank (not used by Cisco Unified Communications Manager). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Enable Extension Mobility | Check this check box if this phone supports extension mobility. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Common Device Configuration | Choose the common device configuration to which you want this phone assigned. The common device configuration includes the attributes (services or features) that are associated with a particular user. Configure the common device in the Common Device Configuration window. To see the common device configuration settings, click the View Details link. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Early Offer support for voice and video calls (insert MTP if needed) | This field is applicable only for Third-party AS-SIP Endpoint. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Information | This field displays the name of the active firmware load if the Cisco Unified IP Phone has registered with Cisco Unified Communications Manager. In some cases, the Active Load ID field displays "Unknown." For example, Cisco Unified Communications Manager Administration might display "Unknown" in the Active Load ID field for any of the following circumstances: For SCCP phones, when the phone is a Cisco Unified IP Phone 7940 (SCCP), 7960 (SCCP), or 7985 (SCCP), because these phone models do not support the necessary version of SCCP. For SCCP and SIP phones, when the phone is any third-party phone. When Cisco Unified Communications Manager cannot determine the status of the phone. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Secure Authentication URL | Enter the secure URL that the phone uses to validate requests that are made to the phone web server. Note If you do not provide a Secure Authentication URL, the device uses the nonsecure URL. If you provide both a secure URL and a nonsecure URL, the device chooses the appropriate URL, based on its capabilities. By default, this URL accesses a Cisco Unified Communications Self Care Portal window that was configured during installation. Leave this field blank to accept the default setting. Maximum length: 255 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Block Incoming Calls while Roaming |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Secure Idle URL | Enter the secure URL for the information that displays on the Cisco Unified IP Phone display when the phone is idle, as specified in Idle Timer field. For example, you can display a logo on the LCD when the phone has not been used for 5 minutes. Note If you do not provide a Secure Idle URL, the device uses the nonsecure URL. If you provide both a secure URL and a nonsecure URL, the device chooses the appropriate URL, based on its capabilities. To accept the default setting, leave this field blank. Maximum length: 255 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Use Device Pool Calling Party Transformation CSS (Device Mobility Related Information) | Default: True |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Home Network ID | This tag is only valid when value of blockIncomingCallsWhenRoaming is true |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Trace Flag |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Phone Personalization | The Phone Personalization setting allows you to enable a Cisco Unified IP Phone, so it works with Phone Designer, a Cisco Unified Communications widget that allows a phone user to customize the wallpaper and ring tones on the phone. From the Phone Personalization drop-down list box, choose one of the following options: Disabled-The user cannot customize the Cisco Unified IP Phone by using Phone Designer. Enabled-The user can use Phone Designer to customize the phone. Default-The phone uses the configuration from the Phone Personalization enterprise parameter if you choose Default in both the Phone Configuration and Common Phone Profile Configuration windows. If you choose Default in the Common Phone Profile Configuration window but not in the Phone Configuration window, the phone uses the configuration that you specify in the Phone Configuration window. You must install and configure Phone Designer, so the phone user can customize the phone. Before you install and configure Phone Designer, identify which Cisco Unified IP Phone models work with Phone Designer, as described in the Phone Designer documentation. For more information on Phone Designer, see the Phone Designer documentation. Default: Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Geolocation | From the drop-down list box, choose a geolocation. You can choose the Unspecified geolocation, which designates that this device does not associate with a geolocation. You can also choose a geolocation that has been configured with the System > Geolocation Configuration menu option. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Digest User | This field is applicable only to SIP phones. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Join Across Lines | From the drop-down list box, enable or disable the Join Across Lines feature for this device or choose Default to use the service parameter setting. Off—This setting disables the Join Across Lines feature. On—This setting enables the Join Across Lines feature. Default—This setting uses the Join Across Lines setting that is in the service parameter. Default: Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Speeddials |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Speeddial |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Index |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Dirn * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Label |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Do Not Disturb | Check this check box to enable Do Not Disturb on the phone. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Wireless Lan Profile Group | Select a wireless LAN profile group from the drop-down list box. You may also click View Details to display the settings for this wireless LAN profile group. Note You can specify the Wireless LAN Profile Group at the Device Pool level or the individual phone level. Note This field does not apply to all phone models. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Network Hold MOH Audio Source | To specify the audio source that is played when the network initiates a hold action, click the drop-down arrow and choose an audio source from the list that displays. If you do not choose an audio source, Cisco Unified CM uses the audio source that is defined in the device pool or the system default if the device pool does not specify an audio source ID. Note You define audio sources in the Music On Hold Audio Source Configuration window. For access, choose Media Resources > Music On Hold Audio Source. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Network Location | The new Device Destination for Trunk to Trunk Transfer and Drop Conference Feature is required for most gateways ,except FXS gateways and phones.Not Nullable. Default: Use System Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Unattended Port | Check this check box to indicate an unattended port on this device. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Calling Party Transformation CSS | From the drop-down list box, choose the calling search space (CSS) that contains the calling party transformation pattern that you want to apply on the calling number when this phone initiates a call. Cisco Unified CM transforms the calling party using the digit transformations configured on the matching calling party transformation pattern when this phone initiates a call. This setting allows you to transform the calling party number before Cisco Unified CM routes the call. For example, a transformation pattern can change a phone extension to an E.164 number. This setting is generally configured when a user dials using a URI instead of digits. Cisco Unified CM allows calling party transformations on various patterns when dialing using digits, this setting provides similar transformation provision even when dialing using a URI. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Ec Key Size | ecKeySize can be updated only if certificateOperation field is Install/Upgrade,Delete or Troubleshoot. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Version Stamp | UUID changed each time device is updated |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Device Trust Mode | Select whether the device is trusted or not trusted. You can configure this setting for analog phones using SCCP, and for some third-party endpoints. Default: Not Trusted |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| 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 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Link To Line | Link to the line resource |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| 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 |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Third-party Registration Required |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Always Use Prime Line | From the drop-down list box, choose one of the following options: Off—When the phone is idle and receives a call on any line, the phone user answers the call from the line on which the call is received. On—When the phone is idle (off hook) and receives a call on any line, the primary line gets chosen for the call. Calls on other lines continue to ring, and the phone user must select those other lines to answer these calls. Default— Cisco Unified Communications Manager uses the configuration from the Always Use Prime Line service parameter, which supports the Cisco CallManager service. Default: Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| MTP Preferred Originating Codec | From the drop-down list box, choose the codec to use if a media termination point is required for SIP calls. Default: 711ulaw |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Blf Directed Call Parks |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Blf Directed Call Park |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Index |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Directed Call Park Dn And Partition |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Route Partition Name |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Dn Pattern * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Directed Call Park Id | Only the uuid attribute is read |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Label |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Secure Shell Password | This tag is applicable only to thosedevices that support ssh feature. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| BLF Audible Alert Setting (Phone Idle) | This setting determines the busy lamp field (BLF) audible alert setting when no current call exists on the BLF DN: On—An audible alert sounds. Off—No audible alert sounds. Default—The configuration in the Service Parameters Configuration window determines the alert option. Default: Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Built In Bridge * | Enable or disable the built-in conference bridge for the barge feature by using the Built In Bridge drop-down list box (choose On, Off, or Default). Note Cisco Unified IP Phones 7940 and 7960 cannot support two media stream encryptions or SRTP streams simultaneously. To prevent instability due to this condition, the system automatically disables the built-in bridge for 7940 and 7960 phones when the device security mode is set to encrypted. Default: Default |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Packet Capture Duration | This setting exists for troubleshooting encryption only; packet capturing may cause high CPU usage or call-processing interruptions. This field specifies the maximum number of minutes that is allotted for one session of packet capturing. The default setting equals 0, although the range exists from 0 to 300 minutes. To initiate packet capturing, enter a value other than 0 in the field. After packet capturing completes, the value, 0, displays. For more information on packet capturing, see the Cisco Unified Communications Manager Troubleshooting Guide . |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Wifi Hotspot Profile |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Use Device Pool Calling Party Transformation CSS (Caller ID For Calls From This Phone) | Default: True |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Allow Presentation Sharing using BFCP | This field is applicable only for Third-party AS-SIP Endpoint. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Services | From the drop-down list box, choose how the phone will support the services: Internal—The phone uses the phone configuration file to support the service. Choose this option or Both for Cisco-provided default services where the Service URL has not been updated; that is, the service URL indicates Application:Cisco/<name of service>; for example, Application:Cisco/CorporateDirectory. Choose Internal or Both for Cisco-signed Java MIDlets because Cisco-signed Java MIDlets are provisioned in the configuration file. External URL—Choosing External URL indicates that the phone ignores the services in the phone configuration file and retrieves the services from a Service URL. If you configured a custom Service URL for a service, including a Cisco-provided default service, you must choose either External URL or Both; if you choose Internal in this case, the services that are associated with the custom URLs do not work on the phone. Both—Choosing Both indicates that the phone support both the services that are defined in the configuration file and external applications that are retrieved from service URLs. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Feature Control Policy | From the drop-down list box, you can choose a feature control policy that has already been configured in the Feature Control Policy configuration window (Device > Device Settings > Feature Control Policy). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| MLPP Indication | If available, this setting specifies whether a device that can play precedence tones will use the capability when it places an MLPP precedence call. From the drop-down list box, choose a setting to assign to this device from the following options: Default—This device inherits its MLPP indication setting from the common device configuration. Off—This device does not handle nor process indication of an MLPP precedence call. On—This device does handle and process indication of an MLPP precedence call. Note Do not configure a device with the following combination of settings: MLPP Indication is set to Off or Default (when default is Off) while MLPP Preemption is set to Forceful. Turning on MLPP Indication (at the enterprise parameter or device level) disables normal Ring Setting behavior for the lines on a device, unless MLPP Indication is turned off (overridden) for the device. Default: Off |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Busy Lamp Fields |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Busy Lamp Field |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Index |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Call Pickup |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Label |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Route Partition |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Enable Activation ID | This boolean setting, when set to true, indicates that the phone should use activation code based registration |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Packet Capture Mode * | This setting exists for troubleshooting encryption only; packet capturing may cause high CPU usage or call-processing interruptions. Choose one of the following options from the drop-down list box: None—This option, which serves as the default setting, indicates that no packet capturing is occurring. After you complete packet capturing, configure this setting. Batch Processing Mode—Cisco Unified CM writes the decrypted or nonencrypted messages to a file, and the system encrypts each file. On a daily basis, the system creates a new file with a new encryption key. Cisco Unified CM, which stores the file for seven days, also stores the keys that encrypt the file in a secure location. Cisco Unified CM stores the file in the PktCap virtual directory. A single file contains the time stamp, source IP address, source IP port, destination IP address, packet protocol, message length, and the message. The TAC debugging tool uses HTTPS, administrator username and password, and the specified day to request a single encrypted file that contains the captured packets. Likewise, the tool requests the key information to decrypt the encrypted file. For more information on packet capturing, see the Troubleshooting Guide for Cisco Unified Communications Manager . Default: None |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Registration Status | Registration status of the phone |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Phone Load Name | Enter the custom software for the Cisco Unified IP Phone. The value that you enter overrides the default value for the current model. For more information about Cisco Unified IP Phone software and configuration, see the Cisco Unified IP Phone Administration Guide for Cisco Unified Communications Manager, which is specific to the phone model and Unified CM release. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| 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 (<>). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Allow Mra Mode |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Send Geo Location |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Ignore Presentation Indicators (internal calls only) | Check this check box to configure call display restrictions on a call-by-call basis. When this check box is checked, Cisco Unified CM ignores any presentation restriction that is received for internal calls. Use this configuration in combination with the calling line ID presentation and connected line ID presentation configuration at the translation pattern level. Together, these settings allow you to configure call display restrictions to selectively present or block calling and/or connected line display information for each call. See the translation configuration settings for more information about the calling line ID presentation and the connected line ID presentation parameters. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Phone Activation Code Expiry | The provisioning code expiry datetime |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Secure Services URL | Enter the secure URL for Cisco Unified IP Phone services. The is the location that the secure Cisco Unified IP Phone contacts when the user presses the Services button. Note If you do not provide a Secure Services URL, the device uses the nonsecure URL. If you provide both a secure URL and a nonsecure URL, the device chooses the appropriate URL, based on its capabilities. To accept the default setting, leave this field blank. Maximum length: 255 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Services |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Service |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Name * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Url |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Service Name Ascii |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Url Button Index |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Telecaster Service Name * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Url Label |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Secure Shell User | Enter a user ID for the secure shell user. You can enter any alphanumeric or special characters up to 50 characters. Invalid characters include”, %, &, <, >, and \. This field displays when the phone device that you are configuring supports SSH access. Cisco Technical Assistance Center (TAC) uses secure shell for troubleshooting and debugging. Contact TAC for further assistance. See the Cisco Unified Communications Manager Security Guide for this release for information about how to configure encrypted phone configuration files to ensure that Cisco Unified CM does not send SSH credentials to the phone in the clear. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Class * | Class ID string. Class information is read-only except when creating a device. Default: Phone |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| 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 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| BLF Presence Group |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Common Phone Profile * | From the drop-down list box, choose a common phone profile from the list of available common phone profiles. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Idle Timer (seconds) | Enter the time (in seconds) that you want to elapse before the URL that is specified in the Idle field displays. To accept the value of the Idle URL Timer enterprise parameter, leave this field blank. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Idle | This setting determines the busy lamp field (BLF) audible alert setting when no current call exists on the BLF DN: On—An audible alert sounds. Off—No audible alert sounds. Default—The configuration in the Service Parameters Configuration window determines the alert option. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| 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. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Remote Device | If you are experiencing delayed connect times over SCCP pipes to remote sites, check the Remote Device check box in the Phone Configuration window. Checking this check box tells Cisco Unified CM to allocate a buffer for the phone device when it registers and to bundle SCCP messages to the phone. Tip Because this feature consumes resources, be sure to check this check box only when you are experiencing signaling delays for phones that are running SCCP. Most users do not require this option. Cisco Unified CM sends the bundled messages to the phone when the station buffer is full, as soon as it receives a media-related message, or when the Bundle Outbound SCCP Messages timer expires. To specify a setting other than the default setting (100 msec) for the Bundle Outbound SCCP Messages timer, configure a new value in the Service Parameters Configuration window for the Cisco CallManager service. Although 100 msec specifies the recommended setting, you may enter 15 msec to 500 msec. The phone must support SCCP version 9 to use this option. The following phones do not support SCCP message optimization: Cisco Unified IP Phone 7935/7936. This feature may require a phone reset after update. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| AAR Calling Search Space | Choose the appropriate calling search space for the device to use when it performs automated alternate routing (AAR). The AAR calling search space specifies the collection of route partitions that are searched to determine how to route a collected (originating) number that is otherwise blocked due to insufficient bandwidth. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| SIP Dial Rules | If required, choose the appropriate SIP dial rule. SIP dial rules provide local dial plans for Cisco Unified IP Phones 7905, 7912, 7940, and 7960, so users do not have to press a key or wait for a timer before the call gets processed. Leave the SIP Dial Rules field set to <None> if you do not want dial rules to apply to the IP phone that is running SIP. This means that the user must use the Dial softkey or wait for the timer to expire before the call gets processed. |
|
|||||||||||||||||||||||||||||||||||||||||||||||