Cisco TelePresence SX20 Codec Reference Manual page 56

Application programming interface (api)
Hide thumbs Also See for TelePresence SX20 Codec:
Table of Contents

Advertisement

Cisco TelePresence SX20 Codec
Contents
Introduction
xConfiguration SIP Profile [1..1] TlsVerify
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
xConfiguration SIP Profile [1..1] Outbound
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.
Example: xConfiguration SIP Profile 1 Outbound: Off
xConfiguration SIP Profile [1..1] Proxy [1..4] Address
The Proxy Address is the manually configured address for the outbound proxy. It is possible to use a
fully qualified domain name, or an IP address. 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: A valid IPv4 address, IPv6 address or DNS name.
Example: xConfiguration SIP Profile 1 Proxy 1 Address: ""
SX20 Codec API Reference Guide TC6.2, JULY 2013.
D14949.04
About the API
xConfiguration
xConfiguration
xConfiguration SIP Profile [1..1] Proxy [1..4] Discovery
xConfiguration SIP Profile [1..1] Type
xConfiguration SIP Profile [1..1] Mailbox
56
xCommand
Select if the SIP Proxy address is to be obtained manually or by using Dynamic Host Configuration
Protocol (DHCP).
Requires user role: ADMIN
Value space: <Auto/Manual>
Auto: When Auto is selected, the SIP Proxy address is obtained using Dynamic Host Configuration
Protocol (DHCP).
Manual: When Manual is selected, the manually configured SIP Proxy address will be used.
Example: xConfiguration SIP Profile 1 Proxy 1 Discovery: Manual
Enables SIP extensions and special behaviour for a vendor or provider.
Requires user role: ADMIN
Value space: <Standard/Alcatel/Avaya/Cisco/Microsoft/Nortel>
Standard: To be used when registering to standard SIP Proxy (tested with Cisco TelePresence
VCS and Broadsoft)
Alcatel: To be used when registering to Alcatel-Lucent OmniPCX Enterprise. NOTE: This mode is
not fully supported.
Avaya: To be used when registering to Avaya Communication Manager. NOTE: This mode is not
fully supported.
Cisco: To be used when registering to Cisco Unified Communication Manager.
Microsoft: To be used when registering to Microsoft LCS or OCS. NOTE: This mode is not fully
supported.
Nortel: To be used when registering to Nortel MCS 5100 or MCS 5200 PBX. NOTE: This mode is
not fully supported.
Example: xConfiguration SIP Profile 1 Type: Standard
When registered to a Cisco Unified Communications Manager (CUCM) you may be offered the
option of having a private voice mailbox. Enter the number (address) of the mailbox in this setting, or
leave the string empty if you do not have a voice mailbox.
Requires user role: ADMIN
Value space: <S: 0, 255>>
Format: String with a maximum of 255 characters.
Example: xConfiguration SIP Profile 1 Mailbox: "12345678"
API Reference Guide
xStatus
Appendices
Copyright © 2013 Cisco Systems, Inc. All rights reserved.

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents