Configure

To enable TPO Static Links, a Distributed Place has to be defined in the TSS.

Defining a Distributed Place is performed the following way.

Create a Master place

First, a Master place needs to be defined, and this place must be a RingdownDynamic DDI place that only has DDI slots with attached properties. Refer to the DDI Lines & Private Wires configuration for additional information.

The Master place looks like this:

Create a Slave place pointing to the Master place

Next, a slave place needs to be defined.

Start the TPO place creation process and check the Connected to another place check box. This switches to the Slave place mode of the TPO place creation form which allows selecting a Master place to connect to.

Enter the name of the Master place and press the Search button.

Select the Master place in the list, fill in the other parameters, such as volume amplification, recording properties, and press Save and Go Back.

At this point, the distributed place is ready to be started.  Repeat the Slave Place creation process if the place needs to be accessed from other TPOs.

Start the distributed place

Edit the Master place.

The place edition forms now presents a dedicated area that allows:

•Switching between all the places being part of the distributed place, each place being identified by its TPO Name (the Master place is displayed on the left side of the area while the Slave places are displayed on the right side)

•Requesting a debug information dump on the whole distributed place

Start the place by clicking the Start arrow.

After a few seconds, press the Refresh button. The Master place should be properly started.

Click the Slave place link on the right of the area, and start the Slave place by clicking the Start arrow.

Once the Master and all the Slave places are properly started, the distributed place is operational.

Settings when using DNS redundancy mode

When the DNS redundancy mode is used, the setting "application.sip.tpocluster.use.main.dns=true" is necessary on the TPO that runs a slave place.

A DNS delegation needs to be configured on the DNS server, see the "Main DNS Server" section for more details.

Location: Terminal Boot Settings, Terminal Profile Settings, TPO Shared Settings, TPO Private Settings, TPO Boot Settings
TPO	Always use main DNS to connect TPO cluster Key: application.sip.tpocluster.use.main.dns Description: Defines if system uses main DNS server of TPO cluster node IPs for DNS Name resolution. When terminal needs to access only one TPO DNS Cluster, it pushes IP addresses of cluster nodes as SIP Stack DNS server configuration. It makes name resolution more efficient for accessing the TPO cluster but it affects all DNS Name resolution that rely on the SIP Stack. If user has PBX lines and PBX proxies are provided as domain names, SIP stack is not able to resolve PBX proxies names any more. In order to avoid system being enable to resolve PBX proxies name, system administrator can turn this setting value to "true". In that case system doesn't use cluster node IPs as SIP Stack DNS Servers. On the turret, if SIP over Websocket is enabled (application.protocol.tpo.websocket), the default value of this key becomes true. Constraint: true|false Related settings: DNS List (application.sip.connection.dnsaddress) Enable WebSocket Protocol For TPO connections (application.protocol.tpo.websocket)

The setting application.sip.connection.dnsaddress can also be used to specify the DNS server address if needed.

Location: Terminal Boot Settings, TPO Shared Settings, TPO Private Settings, TPO Boot Settings
SIP	DNS List Key: application.sip.connection.dnsaddress Description: List of DNS ip addresses, comma separated. The turret cannot start if no DNS are defined in the network. This field is automatically filled by the bootstrap if DHCP is present. Related settings: DNS Suffix (application.sip.connection.dnssuffix) DNS Server checking (application.sip.dns.servercheck.enable) DNS Server checking timer (application.sip.dns.servercheck.timer) Always use main DNS to connect TPO cluster (application.sip.tpocluster.use.main.dns)

Settings to use Static Link over WebSocket

It's possible to create a Static Link over WebSocket. The TPO hosting the master place must be configured to handle WebSocket protocol, see this section.

If a TPO is configured with the following keys, all slave places hosted on this TPO will use the WebSocket protocol to connect to master places.

Location: TPO Shared Settings, TPO Private Settings, TPO Boot Settings
SIP	Enable Websocket Protocol for R-Link WSWSSDisable Key: application.protocol.rlink.websocket.transport Description: This parameter enables WebSocket (WS) or Websocket secure (WSS) protocol for R-Link connections. Related settings: R-Link WebSocket SIP remote TPO port (application.protocol.rlink.websocket.remote.port) R-Link WebSocket Secure SIP remote TPO port (application.protocol.rlink.websocketsecure.remote.port) R-Link WebSocket RTP remote TPO port (application.protocol.rlink.rtp.websocket.remote.port) R-Link WebSocket Secure RTP remote TPO port (application.protocol.rlink.rtp.websocketsecure.remote.port)

Location: TPO Shared Settings, TPO Private Settings, TPO Boot Settings
SIP	R-Link WebSocket SIP remote TPO port Key: application.protocol.rlink.websocket.remote.port Description: Defines the port on which the TPO have to contact other TPOs for SIP R-Link when using websocket (WS) transport. The TPO will use this port to contact all "master" TPOs over WS for the signalisation (SIP). Only one port can be specified with this setting. Related settings: Enable Websocket Protocol for R-Link (application.protocol.rlink.websocket.transport) R-Link WebSocket Secure SIP remote TPO port (application.protocol.rlink.websocketsecure.remote.port) R-Link WebSocket RTP remote TPO port (application.protocol.rlink.rtp.websocket.remote.port) R-Link WebSocket Secure RTP remote TPO port (application.protocol.rlink.rtp.websocketsecure.remote.port)

Location: TPO Shared Settings, TPO Private Settings, TPO Boot Settings
SIP	R-Link WebSocket Secure SIP remote TPO port Key: application.protocol.rlink.websocketsecure.remote.port Description: Defines the port on which the TPO have to contact other TPOs for SIP R-Link when using websocket secure (WSS) transport. The TPO will use this port to contact all "master" TPOs over WSS for the signalisation (SIP). Only one port can be specified with this setting. Related settings: Enable Websocket Protocol for R-Link (application.protocol.rlink.websocket.transport) R-Link WebSocket SIP remote TPO port (application.protocol.rlink.websocket.remote.port) R-Link WebSocket RTP remote TPO port (application.protocol.rlink.rtp.websocket.remote.port) R-Link WebSocket Secure RTP remote TPO port (application.protocol.rlink.rtp.websocketsecure.remote.port)

Location: TPO Shared Settings, TPO Boot Settings
Media	R-Link WebSocket RTP remote TPO port Key: application.protocol.rlink.rtp.websocket.remote.port Description: Defines the port on which the TPO have to contact other TPOs for RTP R-Link when using websocket (WS) transport. The TPO will use this port to send RTP streams to "master" TPOs over WS. Only one port can be specified with this setting. Related settings: Enable Websocket Protocol for R-Link (application.protocol.rlink.websocket.transport) R-Link WebSocket SIP remote TPO port (application.protocol.rlink.websocket.remote.port) R-Link WebSocket Secure SIP remote TPO port (application.protocol.rlink.websocketsecure.remote.port) R-Link WebSocket Secure RTP remote TPO port (application.protocol.rlink.rtp.websocketsecure.remote.port)

Location: TPO Shared Settings, TPO Boot Settings
Media	R-Link WebSocket Secure RTP remote TPO port Key: application.protocol.rlink.rtp.websocketsecure.remote.port Description: Defines the port on which the TPO have to contact other TPOs for RTP R-Link when using websocket secure (WSS) transport. The TPO will use this port to send RTP streams to "master" TPOs over WSS. Only one port can be specified with this setting. Related settings: Enable Websocket Protocol for R-Link (application.protocol.rlink.websocket.transport) R-Link WebSocket SIP remote TPO port (application.protocol.rlink.websocket.remote.port) R-Link WebSocket Secure SIP remote TPO port (application.protocol.rlink.websocketsecure.remote.port) R-Link WebSocket RTP remote TPO port (application.protocol.rlink.rtp.websocket.remote.port)

Visual representation of TPO links (TPOs Floor Map)

It is possible to get a visual representation of TPO clusters links, on the TSS it is located in "Device Management" > "TPOs Floor Map". The map is the actual configuration of TPO clusters, TPO clusters are grouped per TSS and per zones.

Map representation

On the TPOs floor map, static links between TPOs are represented by a line. The dashed lines represent the intercom links between TPOs.

The bullet on the TPO cluster represent the owner of the relation (the original place).

Filtering

It is possible to filter the map, there is actually two filters available: Zones (in green) and links types (in blue).

•Zones: When you uncheck a zone in the list, all clusters of this zones and associated links are hidden.

•Links types: This filter allows to only choose which kind of links you want to see on the TPOs floor map (both, only one or none of them).