Cisco Codec C20 Reference Manual page 146

Telepresence system
Hide thumbs Also See for Codec C20:
Table of Contents

Advertisement

Cisco TelePresence System Codec C20
Contents
Introduction
xStatus SIP Proxy [1] Status
Shows the status of the communication between the endpoint and the SIP Proxy server.
Active: The communication between the endpoint and the SIP Proxy is active.
DNSFailed: The attempt to establish communication to the DNS server failed.
Off: There is no communication between the endpoint and the SIP Proxy.
Timeout: The attempt to establish communication to the SIP Proxy timed out.
UnableTCP: The system is unable to use TCP as the transport method.
UnableTLS: The system is unable to use TLS as the transport method.
Unknown: The status of the communication is not known.
Value space of the result returned:
<Active/DNSFailed/Off/Timeout/UnableTCP/UnableTLS/Unknown>
example:
xStatus SIP Proxy 1 Status
*s SIP Proxy 1 Status: Active
** end
xStatus SIP Proxy [1] Address
Shows the address of the SIP Proxy that the system communicates with.
Value space of the result returned:
<String>
example:
xStatus SIP Proxy 1 Address
*s SIP Proxy 1 Address: "192.0.2.50"
** end
xStatus SIP Proxy [1] Secure
Shows the encryption status of the signalling with the SIP Proxy server.
Value space of the result returned:
<True/False>
example:
xStatus SIP Proxy 1 Secure
*s SIP Proxy 1 Secure: True
** end
Codec C20 API Reference Guide TC6.0 February 2013.
D14869.05
About the API
xConfiguration
xStatus SIP Proxy [1] Verified
xStatus SIP Registration [1..n] Status
xStatus SIP Registration [1..n] Reason
146
xCommand
Shows whether or not the SSL certificate of the server that the video system / codec tries to register to
is included in the codec's trusted CA-list. The server is typically a Cisco VCS or CUCM.
True: The server's SIP certificate is checked against the trusted CA-list on the codec and found valid.
Additionally, the fully qualified domain name of the server matches the valid certificate.
False: A TLS connection is not set up because the SIP certificate verification failed or the domain name
didn't match. Note that the status also returns False when TLS is not used (xConfiguration SIP Profile
1 DefaultTransport not set to TLS) or certificate verification is switched off (xConfiguration SIP Profile
TlsVerify set to Off).
Value space of the result returned:
<True/False>
example:
xStatus SIP Proxy 1 Verified
*s SIP Proxy 1 Verified: False
** end
Shows the status of the registration to the SIP Proxy Server.
Deregister: The system is in the process of de-registering to the SIP Proxy.
Failed: The system failed to register to the SIP Proxy.
Inactive: The system is not registered to any SIP Proxy.
Registered: The system is registered to the SIP Proxy.
Registering: The system is in the process of registering to the SIP Proxy.
Value space of the result returned:
<Deregister/Failed/Inactive/Registered/Registering>
example:
xStatus SIP Registration 1 Status
*s SIP Registration 1 Status: Registered
** end
Shows a message to explain the reason why the SIP registration failed.
Value space of the result returned:
<String>
example:
xStatus SIP Registration 1 Reason
*s SIP Registration 1 Reason: "404 Not Found"
** end
API Reference Guide
xStatus
xStatus
Appendices
Copyright © 2010–2013 Cisco Systems, Inc. All rights reserved.

Advertisement

Table of Contents
loading

Table of Contents