Cisco 6800 Series 유지 관리 매뉴얼 - 페이지 7

{카테고리_이름} Cisco 6800 Series에 대한 유지 관리 매뉴얼을 온라인으로 검색하거나 PDF를 다운로드하세요. Cisco 6800 Series 8 페이지. Ip phone, multiplatform phones
Cisco 6800 Series에 대해서도 마찬가지입니다: 빠른 시작 매뉴얼 (3 페이지), 사용자 설명서 (8 페이지), 사용자 설명서 (14 페이지), 문제 해결 매뉴얼 (12 페이지), 빠른 시작 매뉴얼 (4 페이지), 하드웨어 설치 (20 페이지), 사용자 설명서 (22 페이지), 빠른 시작 매뉴얼 (4 페이지), 설치 매뉴얼 (39 페이지), 빠른 시작 매뉴얼 (2 페이지), 빠른 시작 매뉴얼 (2 페이지), 빠른 시작 매뉴얼 (2 페이지)

페이지 인쇄
Cisco 6800 Series 유지 관리 매뉴얼
Maintenance
Reason
Upgrade
Provisioning
SIP Triggered
RC
User Triggered
IP Changed
You can view the reboot history as follows:
• From the phone web user interface
• From the IP phone screen
• From the phone Status Dump file (http://phoneIP/status.xml or http://phoneIP/admin/status.xml)
Reboot History on the Phone Web User Interface
On the Info > System Status page, the Reboot History section displays the device reboot history, the five
most recent reboot dates and times, and a reason for the reboot. Each field displays the reason for the reboot
and a time stamp that indicates when the reboot took place.
For example:
Reboot Reason 1: [08/13/14 06:12:38] User Triggered
Reboot Reason 2: [08/10/14 10:30:10] Provisioning
Reboot Reason 3: [08/10/14 10:28:20] Upgrade
The reboot history displays in reverse chronological order; the reason for the most recent reboot displays in
Reboot Reason 1.
Reboot History on the Cisco IP Phone Screen
Reboot History is located under Apps > Admin Settings > Status menu. In the Reboot History window, the
reboot entries displays in reverse chronological order, similar to the sequence that displays on the phone web
user interface.
Reboot History in the Status Dump File
The reboot history is stored in the Status Dump file (http://<phone_IP_address>/admin/status.xml).
Reboot History on the Phone Web User Interface
Description
The reboot was a result of an upgrade operation
(regardless whether the upgrade completed or failed).
The reboot was the result of changes made to
parameter values by using the IP phone screen or
phone web user interface, or as a result of
synchronization.
The reboot was triggered by a SIP request.
The reboot was triggered as a result of remote
customization.
The user manually triggered a cold reboot.
The reboot was triggered after the phone IP address
changed.
Maintenance
7