The Networkservices Configuration; Xconfiguration Networkservices H323 Mode; Xconfiguration Networkservices Http Mode; Xconfiguration Networkservices Https Mode - Cisco TelePresence System Codec C90 Reference Manual

Cisco TelePresence System Codec C90
Contents Introduction

The NetworkServices configuration

xConfiguration NetworkServices Multiway Address

The Multiway address must be equal to the Conference Factory Alias, as configured on the Video
Communication Server. The Multiway™ conferencing enables video endpoint users to introduce a 3rd
party into an existing call.
Multiway™ can be used in the following situations:
1) When you want to add someone else in to your existing call.
2) When you are called by a 3rd party while already in a call and you want to include that person in
the call.
Requirements: The Codec C20 must be running TC3.0 (or later), Codec C90/C60/C40 must
be running TC4.0 (or later), EX90/EX60/MX200/MX300 must be running TC4.2 (or later), Video
Communication Server (VCS) version X5 (or later) and Codian MCU version 3.1 (or later). Endpoints
invited to join the Multiway™ conference must support the H.323 routeToMC facility message if in an
H.323 call, or SIP REFER message if in a SIP call.
Requires user role: ADMIN
Value space: <S: 0, 255>
Format: String with a maximum of 255 characters.
Example: xConfiguration NetworkServices Multiway Address: "h323:multiway@
company.com"

xConfiguration NetworkServices Multiway Protocol

Determine the protocol to be used for Multiway calls. NOTE: Requires a restart of the codec.
Requires user role: ADMIN
Value space: <Auto/H323/Sip>
Auto: The system will select the protocol for Multiway calls.
H323: The H323 protocol will be used for Multiway calls.
Sip: The SIP protocol will be used for Multiway calls.
Example: xConfiguration NetworkServices Multiway Protocol: Auto

xConfiguration NetworkServices H323 Mode

Determine whether the system should be able to place and receive H.323 calls or not. NOTE:
Requires a restart of the codec.
ADMIN
Requires user role:
<On/Off>
Value space:
On: Enable the possibility to place and receive H.323 calls (default).
Off: Disable the possibility to place and receive H.323 calls.
xConfiguration NetworkServices H323 Mode: On
Example:
D14641.06 Codec C90 API Reference Guide TC5.0 November 2011.
© 2010-2011 Cisco Systems, Inc. All rights reserved.
About the API xConfiguration xConfiguration

xConfiguration NetworkServices HTTP Mode

xConfiguration NetworkServices HTTPS Mode

xConfiguration NetworkServices HTTPS VerifyServerCertificate

xConfiguration NetworkServices HTTPS VerifyClientCertificate

46
xCommand
Set the HTTP mode to enable/disable access to the system through a web browser. The web
interface is used for system management, call management such as call transfer, diagnostics and
software uploads.
Requires user role: ADMIN
Value space: <On/Off>
On: The HTTP protocol is enabled.
Off: The HTTP protocol is disabled.
Example: xConfiguration NetworkServices HTTP Mode: On
HTTPS is a web protocol that encrypts and decrypts user page requests as well as the pages that are
returned by the web server.
ADMIN
Requires user role:
Value space: <On/Off>
On: The HTTPS protocol is enabled.
Off: The HTTPS protocol is disabled.
Example: xConfiguration NetworkServices HTTPS Mode: On
When the system connects to an external HTTPS server (like a phonebook server or an external
manager), this server will present a certificate to the system to identify itself.
ADMIN
Requires user role:
<On/Off>
Value space:
On: Requires the system to verify that the server certificate is signed by a trusted Certificate
Authority (CA). This requires that a list of trusted CAs are uploaded to the system in advance.
Off: Do not verify server certificates.
xConfiguration NetworkServices HTTPS VerifyServerCertificate: Off
Example:
When the system connects to a HTTPS client (like a web browser), the client can be asked to present
a certificate to the system to identify itself.
Requires user role: ADMIN
Value space: <On/Off>
On: Requires the client to present a certificate that is signed by a trusted Certificate Authority
(CA). This requires that a list of trusted CAs are uploaded to the system in advance.
Off: Do not verify client certificates.
Example: xConfiguration NetworkServices HTTPS VerifyClientCertificate: Off
API Reference Guide
xStatus Appendices
www.cisco.com