Cisco TelePresence SX80 Reference Manual page 67

Application programmer interface (api)
Hide thumbs Also See for TelePresence SX80:
Table of Contents

Advertisement

Cisco TelePresence SX80
Contents
Introduction
xConfiguration SIP Profile [1..1] DisplayName
When configured the incoming call will report the DisplayName instead of the SIP URI.
Requires user role: ADMIN
Value space: <S: 0, 255>
Format: String with a maximum of 255 characters.
Example: xConfiguration SIP Profile 1 DisplayName: ""
xConfiguration SIP Profile [1..1] Authentication [1..1] LoginName
This is the user name part of the credentials used to authenticate towards the SIP proxy.
Requires user role: ADMIN
Value space: <S: 0, 128>
Format: String with a maximum of 128 characters.
Example: xConfiguration SIP Profile 1 Authentication 1 LoginName: ""
xConfiguration SIP Profile [1..1] Authentication [1..1] Password
This is the password part of the credentials used to authenticate towards the SIP proxy.
Requires user role: ADMIN
Value space: <S: 0, 128>
Format: String with a maximum of 128 characters.
Example: xConfiguration SIP Profile 1 Authentication 1 Password: ""
xConfiguration SIP Profile [1..1] DefaultTransport
Select the transport protocol to be used over the LAN.
Requires user role: ADMIN
Value space: <TCP/UDP/Tls/Auto>
TCP: The system will always use TCP as the default transport method.
UDP: The system will always use UDP as the default transport method.
Tls: The system will always use TLS as the default transport method. For TLS connections a SIP
CA-list can be uploaded to the video system. If no such CA-list is available on the system then
anonymous Diffie Hellman will be used.
Auto: The system will try to connect using transport protocols in the following order: TLS, TCP,
UDP.
Example: xConfiguration SIP Profile 1 DefaultTransport: Auto
Codec SX80 API Reference Guide TC7.3, OCTOBER 2015.
D15107.05
About the API
xConfiguration
xConfiguration
xConfiguration SIP Profile [1..1] TlsVerify
xConfiguration SIP Profile [1..1] Outbound
xConfiguration SIP Profile [1..1] Proxy [1..4] Address
67
xCommand
For TLS connections a SIP CA-list can be uploaded to the video system. This can be done from the
web interface.
Requires user role: ADMIN
Value space: <Off/On>
Off: Set to Off to allow TLS connections without verifying them. The TLS connections are allowed
to be set up without verifying the x.509 certificate received from the server against the local
CA-list. This should typically be selected if no SIP CA-list has been uploaded.
On: Set to On to verify TLS connections. Only TLS connections to servers, whose x.509 certificate
is validated against the CA-list, will be allowed.
Example: xConfiguration SIP Profile 1 TlsVerify: Off
Turn on or off the client initiated connections mechanism for firewall traversal, connection reuse and
redundancy. The current version supports RFC 5626.
Requires user role: ADMIN
Value space: <Off/On>
Off: Connect to the single proxy configured first in Proxy Address list.
On: Set up multiple outbound connections to servers in the Proxy Address list. A random proxy is
selected from the list for each SIP outbound request.
Example: xConfiguration SIP Profile 1 Outbound: Off
The Proxy Address is the manually configured address for the outbound proxy. The default port is
5060 for TCP and UDP but another one can be provided.
If SIP Profile Outbound is enabled, multiple proxies can be addressed.
Requires user role: ADMIN
Value space: <S: 0, 255>
Format: If SIP Profile Outbound is enabled, use a fully qualified domain name. If SIP Profile
Outbound is disabled, you can also use a valid IPv4 address or IPv6 address.
Example: xConfiguration SIP Profile 1 Proxy 1 Address: ""
API Reference Guide
xStatus
Appendices
Copyright © 2015 Cisco Systems, Inc. All rights reserved.

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents