The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The phone web user interface allows you to customize settings such as the phone name, background picture, logo, and screen saver.
You can create a text or 128-by-48 pixel by 1-bit deep image logo to display when the Cisco IP Phone boots up. A logo displays during the boot sequence for a short period after the Cisco logo displays.
Step 1 | Click . |
Step 2 | In the Screen section, select any option from the Boot Display field.
|
Step 3 | Click Submit All Changes. The phone reboots, retrieves the .png file, and displays the picture when it next boots. |
Step 1 | On the phone web page, select . |
Step 2 | In the Screen section, select Logo from the Boot Display field. In the Logo URL field, enter a URL or path for the location where the logo image is saved.
You can also download a picture and add as a boot display: select Download Picture from the Boot Display field. In the Picture Download URL field, enter a URL or path for the location where the picture is saved. The logo must be a .jpg or a .png file. The phone has a fixed display area. So, if the original logo size doesn't fit into the display area scale to fit it. For the Cisco IP Phone 7832, the logo display area is at the mid-center of the phone screen. The display area size of the Cisco IP phone 7832 is 48x48. |
Step 3 | Click Submit All Changes. |
Phones that support multiple call appearances on a line can be configured to specify the number of calls to allow on the line.
To enable call forwarding, you can enable the feature in two places: on the Voice tab and the User tab of the phone web page.
If a user is not on an active or held call and misses a call, the user needs to know about the missed call. To alert the user, configure the Handset LED Alert field on the Configuration Utility page. If you set this field to Voicemail, Missed Call, the LED on the Handset will turn on when the user has recently missed a call.
You can allow users to turn the do not disturb feature on or off. The caller receives a message that the user is unavailable. Users can press the Ignore softkey on their phones to divert a ringing call to another destination.
If the feature is enabled for the phone, users turn the feature on or off with the DND softkey.
Step 1 | On the Configuration Utility page, select (where [n] is the extension number). |
Step 2 | In the Call Feature Settings section, set the Feature Key Sync field to Yes. |
Step 3 | Click Submit All Changes. |
You can configure star codes that a user dials to turn on or off the do not disturb (DND) feature on a phone.
A shared line is a directory number that appears on more than one phone. You can create a shared line by assigning the same directory number to different phones.
Incoming calls display on all phones that share a line, and anyone can answer the call. Only one call remains active at a time on a phone.
Call information displays on all phones that are sharing a line. If somebody turns on the privacy feature, you do not see the outbound calls made from the phone. However, you see inbound calls to the shared line.
All phones with a shared line ring when a call is made to the line. If you place the shared call on hold, anyone can resume the call by pressing the corresponding line key from a phone that shares the line. You can also press the Select button if the Resume icon is displayed.
Line Seizure
Public Hold
Private Hold
Silent Barge (only through enabled programmable softkey)
Transfer
Conference
Call Park / Call Retrieve
Call Pickup
Do Not Disturb
Call Forward
You can configure each phone independently. Account information is usually the same for all IP phones, but settings such as the dial plan or preferred codec information can vary.
You can create a shared line by assigning the same directory number to different phones on the phone web page.
You can configure the Message Waiting Indicator for separate extensions on the phone. The Message Waiting Indicator lights based on the presence of new voicemail messages in the mailbox.
You can enable the indicator at the top of your IP phone to light when voice mail is left, or display a seeing message waiting notification.
The user can modify volume settings by pressing the volume control button on the phone, then pressing the Save softkey.
The Cisco IP Phone respects only the “ua” user access attribute. For a specific parameter, the “ua” attribute defines access by the user account to the administration web server. If the “ua” attribute is not specified, the phone applies the factory default user access for the corresponding parameter. This attribute does not affect access by the admin account.
Note | The value of the element attribute encloses within double quotes. |
The web server allows administrators and users to log in to the phone by using a phone web user interface. Administrators and users have different privileges and see different options for the phone based on their role.
Use this procedure to enable the phone web user interface from the phone screen.
If the Enable Direct Action URL setting is set to "Yes ", these Direct action URLs are accessible only for the admin. If Admin user is password protected, the client provides a login prompt before these are accessed. The Direct Action URLs are accessible via the phone web page via the path /admin/<direct_action>. The syntax is:
http[s]://<ip_or_hostname>/admin/<direct_action>[?<url>]
For example, http://10.1.1.1/admin/resync?http://server_path/config.xml
The following table provides a list of the different direct avtion URLs that are supported.
direct_action |
Description |
Example |
---|---|---|
resync |
Initiates a one-time resync of the config file specified by URL. The URL to resync is provided by appending ? followed by the URL. The URL specified here will not be saved anywhere in the phone settings. |
http://10.1.1.1/admin/resync?http://my_provision_server.com/cfg/device.cfg |
upgrade |
Initiates an upgrade of a phone to the specified load. The load is specified via the upgrade rule. the rule is specified by appending ? followed by URL path to the load. The upgrade rule specified is one time only and will not be saved in any property setting. |
http://10.1.1.1/admin/upgrade?http://my_upgrade_server.com/loads/sip88xx.11.0.0MP2.123.loads |
updateca |
Initiates a one-time install of the Custom Certificate Authority (Custom CA) specified by the URL. The URL to download is provided by appending ? followed by the URL. The URL specified here will not be saved anywhere in the phone settings. |
http://10.1.1.1/admin/updateca?http://my_cert_server.com/certs/myCompanyCA.pem |
reboot |
Initiates a reboot of the phone. Does not take any parameter with ? |
http://10.1.1.1/admin/reboot |
cfg.xml |
Downloads a snapshot of the phone configuration in XML format. The passwords are hidden for security. Most of the information here corresponds to the properties on the phone web page under Voice tab. |
http://10.1.1.1/admin/cfg.xml |
status.xml |
Downloads a snapshot of the phone status in XML format. Most of the information here corresponds to the Status tab in the phone web page. |
http://10.1.1.1/admin/status.xml |
screendump.bmp |
Downloads a screenshot of the phone LCD UI at the time when this action is initiated. |
http://10.1.1.1/admin/screendump.bmp |
log.tar |
Downloads a set of archived logs stored on the phone. |
http://10.1.1.1/admin/log.tar |
The phones provide support for XML services, such as an XML Directory Service or other XML applications. For XML services, only HTTP and HTTPS support are available.
The following Cisco XML objects are supported:
CiscoIPPhoneMenu
CiscoIPPhoneText
CiscoIPPhoneInput
CiscoIPPhoneDirectory
CiscoIPPhoneIconMenu
CiscoIPPhoneStatus
CiscoIPPhoneExecute
CiscoIPPhoneImage
CiscoIPPhoneImageFile
CiscoIPPhoneGraphicMenu
CiscoIPPhoneFileMenu
CiscoIPPhoneStatusFile
CiscoIPPhoneResponse
CiscoIPPhoneError
CiscoIPPhoneGraphicFileMenu
Init:CallHistory
Key:Headset
EditDial:n
There are more URIs supported which are available in the Cisco Unified IP Phone Services Application Development Notes.
For more information, see the Cisco Unified IP Phone Services Application Development Notes located here: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/all_models/xsi/9-1-1/CUIP_BK_P82B3B16_00_phones-services-application-development-notes.html.
When an XML URL requires authentication, use the parameters XML UserName and XML Password.
The parameter XML UserName in XML URL is replaced by $XML UserName.
For example:
The parameter XML UserName is cisco. The XML Directory Service URL is http://www.sipurash.compath?username=$XML_User_Name.
This results in the request URL: http://www.sipurash.com/path?username=cisco.
When authentication is required for CGI/Execute URL via Post from an external application (for example, a web application) to the phones, the parameter CISCO XML EXE Auth Mode is used in 3 different scenarios:
Trusted—No authentication is performed (local user password is set or not). This is the default.
Local Credential—Authentication is based on digest authentication using the local user password, if the local user password is set. If not set, then no authentication is performed.
Remote Credential—Authentication is based on digest authentication using the remote username/password as set in the XML application on the web page (to access an XML application server).
You can use macro variables in XML URLs. The following macro variables are supported:
User ID—UID1, UID2 to UIDn
Display name—DISPLAYNAME1, DISPLAYNAME2 to DISPLAYNAMEn
Auth ID—AUTHID1, AUTHID2 to AUTHIDn
Proxy—PROXY1, PROXY2 to PROXYn
MAC Address using lower case hex digits—MA
Product Name—PN
Product Series Numbe—PSN
Serial Number—SERIAL_NUMBER
The following table shows the list of macros supported on the phones:
Macro Name |
Macro Expansion |
||
---|---|---|---|
$ |
The form $$ expands to a single $ character. |
||
A through P |
Replaced by general purpose parameters GPP_A through GPP_P. |
||
SA through SD |
Replaced by special purpose parameters GPP_SA through GPP_SD. These parameters hold keys or passwords used in provisioning.
|
||
MA |
MAC address using lower case hex digits (000e08aabbcc). |
||
MAU |
MAC address using upper case hex digits (000E08AABBCC). |
||
MAC |
MAC address using lower case hex digits with colon to separate hex digit pairs (00:0e:08:aa:bb:cc). |
||
PN |
Product Name; for example IP Phone 8861. |
||
PSN |
Product Series Number; for example 8861. |
||
SN |
Serial Number string; for example 88012BA01234. |
||
CCERT |
SSL Client Certificate status, installed or not installed. |
||
IP |
IP address of the phone within its local subnet; for example 192.168.1.100. |
||
EXTIP |
External IP of the phone, as seen on the internet; for example 66.43.16.52. |
||
SWVER |
Software version string; for example 2.0.6(b). |
||
HWVER |
Hardware version string; for example 1.88.1. |
||
PRVST |
Provisioning State (a numeric string): |
||
UPGST |
Upgrade State (a numeric string): |
||
UPGERR |
Result message (ERR) of previous upgrade attempt; for example http_get failed. |
||
PRVTMR |
Seconds since last resync attempt. |
||
UPGTMR |
Seconds since last upgrade attempt. |
||
REGTMR1 |
Seconds since Line 1 lost registration with SIP server. |
||
REGTMR2 |
Seconds since Line 2 lost registration with SIP server. |
||
UPGCOND |
Legacy macro name. |
||
SCHEME |
File access scheme (TFTP, HTTP, or HTTPS, obtained after parsing resync or upgrade URL). |
||
METH |
Deprecated alias for SCHEME, do not use. |
||
SERV |
Request target server host name. |
||
SERVIP |
Request target server IP address (following DNS lookup). |
||
PORT |
Request target UDP/TCP port. |
||
PATH |
Request target file path. |
||
ERR |
Result message of resync or upgrade attempt. |
||
UIDn |
The contents of the Line n UserID configuration parameter |
||
ISCUST |
If unit is customized, value=1, otherwise 0.
|
||
INCOMINGNAME |
Name associated with first connected, ringing, or inbound call. |
||
REMOTENUMBER |
Phone number of first connected, ringing, or inbound call. If there are multiple calls, the data associated with the first call found will be provided. |
||
DISPLAYNAMEn |
The contents of the Line N Display Name configuration parameter. |
||
AUTHIDn |
The contents of the Line N auth ID configuration parameter. |
Step 1 | In the Configuration Utility, select . |
Step 2 | Enter this information:
If you configure an unused line button to connect to an XML application, the button connects to the URL configured above. If this is not what you want, you need to enter a different URL when you configure the line button. |
Step 3 | Click Submit All Changes. |