Cisco C40 Manual

							D14636.12 Profile C60-C40 and Codec C60-C40 Administrator Guide TC6.3, OCTOBER 2013. www.cisco.com — Copyright © 2010-2013 Cisco Systems, Inc. All rights reser ved. 
41
Navigate to: Configuration > Startup ScriptsManaging startup scripts
You can create one or more startup scripts* that will run every 
time the video system starts up.
A startup script contains commands (xCommand) and 
configurations (xConfiguration) that will be executed as 
part of the start up procedure. A few commands and 
configurations cannot be placed in a startup script, e.g. 
xCom m and Boot. It is not possible to save a script containing 
illegal commands and configurations.
Syntax and semantics for xCommand and xConfiguration are 
explained in the API guide for the product.
If you have more than one startup script, they will run in the 
order from top to bottom of the list.
Running the script 
immediately
Running the script at every 
start up
Not running the script at start up
*  The script name and commands shown in the illustration ser ve as 
examples. You may make your own scripts.
Deleting a script
Select the script you want to 
delete and click Delet e.
1.
 C

lick Create new...
.
2.
 E

nter a name for your script in the 
title input filed.
3.
 E

nter the commands (xConfiguration 
or xCommand) you want to issue in 
the command input field. Start each  command on a new line.
4.
 
C

lick Save
.
Creating a startup script
Select the script you want to 
deactivate and click Off
. 
Select the script you want to 
activate and click On
.
Select the script you want 
to run and click Run
.
Startup scripts are listed here. A green dot 
appears next to an active script; a red ring  appears next to an inactive script. List of startup scripts
Cisco TelePresence System Codec C40/C60 and Profiles using C40/60 Administrator Guide  
						

							D14636.12 Profile C60-C40 and Codec C60-C40 Administrator Guide TC6.3, OCTOBER 2013. www.cisco.com — Copyright © 2010-2013 Cisco Systems, Inc. All rights reser ved. 
42
Application programming interface
The application programming interface (API) is a tool for 
integration professionals and developers working with this 
video system. The API is described in detail in the API guide 
for the system.
XML files
The XML files are part of the codec’s API. They structure 
information about the codec in a hierarchy.
•
 
Con
 figuration.xml  contains the current system settings 
(configuration). These settings are controlled from the 
web interface or from the API (Application Programmer 
Interface).
•
 
T
 he information in status.xml  is constantly updated by 
the system to reflect system and process changes. The 
status information is normally monitored from the API.
•
 
C
 ommand.xml  contains an overview of the commands 
available to instruct the system to perform an action. The 
commands are issued from the API.
•
 
V
 aluespace.xml  contains an overview of all the value 
spaces used in the system settings, status information, 
and commands.
API commands
Commands (xCommand) and configurations (xConfiguration) 
can be executed from this web page. Syntax and semantics 
are explained in the API guide for the product.
Opening an XML file
Click the file name to open the XML file.
Executing API commands
Enter a command, or a sequence of 
commands, in the text area and click  Execute  to issue the command(s).
Navigate to: Configuration > API
Cisco TelePresence System Codec C40/C60 and Profiles using C40/60 Administrator Guide  
						

							D14636.12 Profile C60-C40 and Codec C60-C40 Administrator Guide TC6.3, OCTOBER 2013. www.cisco.com — Copyright © 2010-2013 Cisco Systems, Inc. All rights reser ved. 
43
Managing the video system’s 
certificates
Certificate validation may be required when using TLS 
(Transport Layer Security). 
A server or client may require that your video system 
presents a valid certificate to them before communication can 
be set up.
The video system’s certificates are text files that verify the 
authenticity of the system. These certificates may be issued 
by a certificate authority (CA).
The certificates are listed as shown in the illustration to the 
right
*. They can be used for the following services: HT TPS, 
SIP and IEEE 802.1X.
You can store several certificates on the system, but only one 
certificate can be used for each service at a time. 
If authentication fails, the connection will not be established.
Enabling and disabling certificates
Use the buttons to switch a certificate on or off for 
the different services.
You can also view a certificate, and delete a 
certificate using the corresponding buttons.
Contact your system administrator to obtain the 
following file(s):
•
 
C

ertificate (file format: .PEM)
•
 
P

rivate key, may be included in the same file 
as the certificate (file format: .PEM format)
•
 P
assword (required only if the private key is 
encr ypted)
The certificate and the private key will be stored in 
the same file on the video system.Adding a certificate
1.
 C

lick B rowse... and find the Certificate and   Private key file(s) on your computer. 
2.
 F

ill in the Password if required.
3.
 C

lick Add certificate...  to store the certificate 
on your system.
Navigate to: Configuration > Security: Certificates tab
*  The certificates and certificate issuers shown in the illustration 
ser ve as examples. Your system may have other certificate(s).
Cisco TelePresence System Codec C40/C60 and Profiles using C40/60 Administrator Guide  
						

							D14636.12 Profile C60-C40 and Codec C60-C40 Administrator Guide TC6.3, OCTOBER 2013. www.cisco.com — Copyright © 2010-2013 Cisco Systems, Inc. All rights reser ved. 
44
Navigate to: Configuration > Security: CAs tabManaging the list of trusted 
certificate authorities
Certificate validation may be required when using TLS 
(Transport Layer Security). 
Your video system may be set up to require that a server 
or client presents its certificate to the system before 
communication can be set up. 
The certificates are text files that verify the authenticity of the 
server or client. The certificates must be signed by a trusted 
certificate authority (CA).
To be able to verify the signature of the certificates, a list of 
trusted CAs must reside on the video system. The certificates 
of the CAs are listed as shown in the illustration to the right
*. 
The list must include all CAs needed in order to verify 
certificates for HT TPS, SIP and IEEE 802.1X connections.
If the server cannot be authenticated, the connection will not 
be established.
*  The certificate and certificate issuers shown in the illustration ser ve 
as examples. Your system will have other certificate(s).
Contact your system administrator to obtain 
the CA certificate list (file format: .PEM).
Viewing and deleting certificates
You can view a certificate, and 
delete a certificate using the 
corresponding buttons.Uploading a list of certificate authorities
i.
 C

lick B rowse...  and find the file containing a 
list of CA certificates (file format: .PEM) on  your computer.
ii.
 C

lick the Add certificate authority...  to store 
the new CA certificate(s) on your system.
The entries in a new file with CA certificates 
will be appended to the existing list, that is, 
the previously stored certificates will not be 
deleted. 
Cisco TelePresence System Codec C40/C60 and Profiles using C40/60 Administrator Guide  
						

							D14636.12 Profile C60-C40 and Codec C60-C40 Administrator Guide TC6.3, OCTOBER 2013. www.cisco.com — Copyright © 2010-2013 Cisco Systems, Inc. All rights reser ved. 
45
Navigate to: Configuration > Security: CAs tab  /  Configuration > System Configuration
i
ii
iii
Adding audit certificates
Audit logging records all sign in activity and configuration 
changes on your video system.
Audit logging is disabled by default, but you can enable it 
using the Security > Audit > Logging > Mode setting on the 
on-screen menu or the web interface.
In ExternalSecure audit logging mode the video system 
sends encrypted audit logs to an external audit server 
(syslog server), which identity must be verified by a signed 
cer tificate.
To be able to verify the signature of the audit server 
certificates, a list of trusted audit certificate authorities (CAs) 
must reside on the video system. 
If the audit server cannot be authenticated, the logs will not 
be sent.
Always upload the audit certificate list before enabling 
secure audit logging.1. Upload a list of audit server certificatesThe entries in a new file with CA 
certificates will overwrite the existing 
list, that is, any previously stored audit 
certificates will be lost when you add a 
new file. 
i.
 C

lick B rowse...  and find the file containing the 
list of audit CA certificates (.PEM format) on 
your computer.
ii.
 C

lick Add audit certificate to store the 
certificate(s) on your system.
Contact your system administrator to 
obtain the Audit CA list (file format: .PEM).
2. Enable secure audit 
loggingi.
 G

o to the System 
Configuration page and  
choose the Security  
category.
ii.
 E

nter the Address  of 
the audit server. If 
you choose Manual  
PortAssignment,  you 
must also enter a Port  
number for the audit 
server. Click Save  for the 
changes to take effect.
iii.
 C

hoose ExternalSecure  
from the Logging Mode  
drop-down list. Click 
Save  for the change to 
take effect.
Cisco TelePresence System Codec C40/C60 and Profiles using C40/60 Administrator Guide  
						

							D14636.12 Profile C60-C40 and Codec C60-C40 Administrator Guide TC6.3, OCTOBER 2013. www.cisco.com — Copyright © 2010-2013 Cisco Systems, Inc. All rights reser ved. 
46
Navigate to: Configuration > Security: Strong Security Mode tabSetting strong security mode
Strong security mode should be used only when compliance 
with DoD JITC regulations is required. 
Read the provided information carefully before setting 
strong security mode.
Strong security mode sets very strict password requirements, 
and requires all users to change their password on the next 
sign in. 
Software upload from TMS, web snapshots and calling from 
the web interface are prohibited in strong security mode.
Setting strong security mode
Read carefully about the consequences of 
strong security mode before you continue.
1.
 I

f you want to use strong security mode,  click Enable strong security mode . 
Confirm your choice in the dialog box that  appears.
The system will restart automatically. 
2.
 C

hange the password when you are 
prompted. The new password must meet  the strict criteria as described. 
How to change the system password is  described in the ►
  Setting passwords  
section.
Return to normal mode
1.
 W

hen in strong security mode, the system  can be restored to normal mode by 
clicking Disable strong security mode... .
2.
 T

he system will restart automatically.
Cisco TelePresence System Codec C40/C60 and Profiles using C40/60 Administrator Guide  
						

							D14636.12 Profile C60-C40 and Codec C60-C40 Administrator Guide TC6.3, OCTOBER 2013. www.cisco.com — Copyright © 2010-2013 Cisco Systems, Inc. All rights reser ved. 
47
Navigate to: Configuration > Security: Non-persistent Mode tabChanging the persistency mode
By default, all persistency settings are set to Persistent . This 
means that configurations, call history, internal logs, local 
phonebook / favorites list and IP connectivity information 
are stored as normal. A system restart does not delete 
information.
As a general rule, we recommend NOT to change the 
default settings for persistency.  But in the case were a 
new user is not supposed to see or trace back to any kind 
of logged information from the previous session, Non-
persistent  mode must be used.
In order to clear/delete information that was stored 
before changing to Non-persistent mode, you should 
consider to factory reset the video system.
There is more information about performing a factory 
reset in the ►
  Factory resetting appendix.
When in Non-persistent mode, the following information will 
be lost/cleared each time the system restarts: •
 
S
 ystem Configuration changes that have been made 
since the last system restart.
•
 
I
 nformation about calls that are placed or received since 
the last system restart (call history).
•
 
I
 nternal log files that has been made since the last system 
restart.
•
 
C
 hanges that are made to the local phonebook / favorites 
list since the last system restart.
•
 
A
 ll IP related information (DHCP) from the last session.
Checking the persistency status
The radio buttons that are active when you open the Security  
page and go to the Non-persistent Mode  tab, shows the 
current persistency status of the video system.
You can also see the status by checking Security > 
Persistency on the Configuration > System Status  page.
Changing the persistency settings
1.
 S
 et the persistency settings for the five 
categories as desired.
2.
 C

lick Save and reboot... .
The system will restart. After the 
restart, behavior according to the new 
persistency settings will start.
Note that logs, configurations etc. that 
was stored before you switch to Non-
persistent mode, will not be cleared or 
deleted.
Cisco TelePresence System Codec C40/C60 and Profiles using C40/60 Administrator Guide  
						

							D14636.12 Profile C60-C40 and Codec C60-C40 Administrator Guide TC6.3, OCTOBER 2013. www.cisco.com — Copyright © 2010-2013 Cisco Systems, Inc. All rights reser ved. 
48
Navigate to: Configuration > Security: CUCM tabDeleting trust lists (CUCM only)
The information on this page is only relevant for 
video systems that are registered to a Cisco Unified 
Communications Manager (CUCM).
The web interface can be used to delete existing trust lists 
(CTL and ITL) that are stored on the video system. Normally, 
you will not delete the old CTL and ITL files, but there are a 
few cases when you will need to delete them.
For more information about CUCM and trust lists, read the 
Administering TC Endpoints on CUCM  guide available on the 
Cisco web site.
Cisco TelePresence System Codec C40/C60 and Profiles using C40/60 Administrator Guide  
						

							D14636.12 Profile C60-C40 and Codec C60-C40 Administrator Guide TC6.3, OCTOBER 2013. www.cisco.com — Copyright © 2010-2013 Cisco Systems, Inc. All rights reser ved. 
49
Navigate to: Diagnostics > TroubleshootingTroubleshooting
The troubleshooting page lists the status for some common  
sources of errors. The list may be different for different 
products and installations
*.
Note that critical issues and errors are clearly marked in red 
color; warnings are yellow.Run diagnostics
Click Re-run diagnostics  to make sure 
the information in the list is up-to-date.
* The messages shown in the illustration ser ve as examples. Your 
system may show other information.
Leave standby mode
This button is only visible when the 
system is in standby mode. If in 
standby mode, click Deactivate standby 
to wake up the system. 
Cisco TelePresence System Codec C40/C60 and Profiles using C40/60 Administrator Guide  
						

							D14636.12 Profile C60-C40 and Codec C60-C40 Administrator Guide TC6.3, OCTOBER 2013. www.cisco.com — Copyright © 2010-2013 Cisco Systems, Inc. All rights reser ved. 
50
Navigate to: Diagnostics > Log FilesDownloading log files
The log files* are Cisco specific debug files which may be 
requested by the Cisco support organization if you need 
technical support.
The current log files are time stamped event log files.
All current log files are archived in a time stamped historical 
log file each time the system restarts. If the maximum 
number of historical log files is reached, the oldest one will be 
overwritten.
About extended logging mode
Extended logging mode may be switched on to help diagnose 
network issues and problems during call setup. While in this 
mode more information is stored in the log files.
Note that extended logging use more of your video system’s 
resources, and may cause your video system to under-
perform. You should only use extended logging mode when 
troubleshooting an issue.Downloading all log files
Click Download logs archive and follow the instructions.
You can choose whether to include the call history in 
the archive or not; and you can choose whether to 
include the full call history or to make the caller/callee 
anonymous. Use the drop down list to include the 
preferred call history list. 
* The log files shown in the illustration ser ve as examples. Your 
system may have other files.
Open/save one log file
Click the file name to open the log file in the web browser;  right click to save the file on the computer.
Start extended logging
1.
 U
 se the drop down list to choose the duration of  
extended logging.
2.
 C

lick Start extended logging .
You can stop the extended logging before it times 
out by clicking the Stop extended logging  button 
that appears when extended logging is on.
Cisco TelePresence System Codec C40/C60 and Profiles using C40/60 Administrator Guide