60
Cisco TelePresence System Codec C60/C40 and Profiles using C60/C40 Administrator guide
D14636.06 Profile C60-C40 and Codec C60-C40 Administrator Guide TC4.2, July 2011.
Copyright © 2010-2011 Cisco Systems, Inc. All rights reserved.
www.cisco.com
The SIP settings
SIP Profile [1..1] URI
The SIP URI or number is used to address the system. This is the URI that is registered and used
by the SIP services to route inbound calls to the system. A Uniform Resource Identifier (URI) is a
compact string of characters used to identify or name a resource.
Requires user role: ADMIN
Value space: <S: 0, 255>
Format: Compact string with a maximum of 255 characters.
Example: SIP Profile 1 URI: "sip:firstname.lastname@company.com"
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: SIP Profile 1 DisplayName: ""
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: SIP Profile 1 Authentication 1 LoginName: ""
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: SIP Profile 1 Authentication 1 Password:
SIP Profile [1..1] DefaultTransport
Select the transport protocol to be used over the LAN.
Requires user role: ADMIN
Value space: <UDP/TCP/Tls/Auto>
UDP: The system will always use UDP as the default transport method.
TCP: The system will always use TCP 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 using the web interface. 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: SIP Profile 1 DefaultTransport: Auto
SIP Profile [1..1] TlsVerify
For TLS connections a SIP CA-list can be uploaded using the web interface.
Requires user role: ADMIN
Value space: <On/Off>
On: Set to On to verify TLS connections. Only TLS connections to servers, whom x.509
certificate is validated against the CA-list, will be allowed.
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.
Example: SIP Profile 1 TlsVerify: Off
SIP Profile [1..1] Outbound
The client initiated connections mechanism for firewall traversal, connection reuse and redundancy.
The current version supports http://tools.ietf.org/html/draft-ietf-sip-outbound-20.
Requires user role: ADMIN
Value space: <On/Off>
On: Set up multiple outbound connections to servers in the Proxy Address list.
Off: Connect to the single proxy configured first in Proxy Address list.
Example: SIP Profile 1 Outbound: Off
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 Outbound is enabled, multiple proxies can be addressed.
Requires user role: ADMIN
Value space: <S: 0, 255>
Format: Compact string with a maximum of 255 characters. An IP address that contains letters
(192.a.2.0) or unvalid IP addresses (192.0.1234.0) will be rejected.
Example: SIP Profile 1 Proxy 1 Address: ""
To Next Page
Loading...
