SIP Profile settings, Standby settings | TANDBERG D14128.02 manual

Codec C90

Contents

Introduction

Getting Started

Interfaces

About the API

System Integrator Guide

xConﬁgurationxConfiguration

xCommand

xStatus

Cameras

Appendices

The SIP Profile settings

xConfiguration SIP Profile [1..1] URI [1..1]: <S: 0, 255>

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.

Example: “sip:name@example.com”, “1234”, “1234@example.com”

Format: Compact string with a maximum of 255 characters.

Example: xConfiguration SIP Profile 1 URI 1: “sip:name@example.com”

xConfiguration SIP Profile [1..1] DefaultTransport: <UDP/TCP/TLS/Auto>

Select the transport protocol to be used over the LAN.

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: xConfiguration SIP Profile 1 DefaultTransport: Auto

xConfiguration SIP Profile [1..1] TlsVerify: <On/Off>

For TLS connections a CA-list can be uploaded from the web interface.

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: xConfiguration SIP Profile 1 TlsVerify: Off

xConfiguration SIP Profile [1..1] Type: <Auto/Nortel/Microsoft/Cisco/Alcatel/

Experimental/Avaya/Siemens>

Enables SIP extensions and special behaviour for a vendor or provider Auto: Should be used when registering to standard SIP proxy like OpenSer. Nortel: Must be used when registering to a Nortel MCS 5100 or MCS 5200 PBX. Microsoft: Must be used when registering to a Microsoft LCS or OCS server. Cisco: Must be used when registering to a Cisco CallManager version 5 or later.

Alcatel: Must be used when registering to a Alcatel-Lucent OmniPCX Enterprise R7 or later.

Siemens: Must be used when registering to a Siemens HiPath 8000.

Telio: Must be used in combination with a Telio subscription (www.telio.no).

Experimental: Can be used if auto is not working Note! This mode is for testing purposes only.

Example: xConfiguration SIP Profile 1 Type: Auto

xConfiguration SIP Profile [1..1] Proxy [1..1] Discovery: <Auto/Manual>

Manual: When Manual is selected, the manually configured SIP Proxy address will be used

Auto: When Auto is selected, the SIP Proxy address is obtained using Dynamic Host Configuration Protocol (DHCP).

Example: xConfiguration SIP Profile 1 Proxy 1 Discovery: Manual

xConfiguration SIP Profile [1..1] Proxy [1..1] Address: <S: 0, 255>

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.

Format: Compact string with a maximum of 255 characters.

Example: xConfiguration SIP Profile 1 Proxy 1 Address: “”

xConfiguration SIP Profile [1..1] Authentication [1..1] LoginName: <S: 0, 50>