TSS & TPO Configuration

Create a PBX cluster

This part of the configuration is using the same method as if a CUCM/Avaya/Alcatel was used. Go in Device Management > PBX Clusters

Each Asterisk server node (1 or 2) should be entered in the PBX Cluster as a node with port 5060 and “Link to SIP Request” (the first node will be the primary Asterisk)

Settings in TPO cluster

Go to Device Management > TPO Cluster > edit TPO Cluster > Boot Settings

•Set the SIP local domain with the IP Address of the Primary Asterisk

Location: Terminal Boot Settings, TPO Shared Settings, TPO Private Settings, TPO Boot Settings
SIP	SIP local domain Key: application.sip.localdomain Description: The SIP Local domain is PBX dependent. This value should fit the PBX SIP domain otherwise some feature may have an unexpected behavior. If no SIP domain is defined the value should be the IP address of the main Call Manager. Notice that this key is also populated by the bootstrap. Related settings: SIP local domain (application.boot.sip.localdomain) Presence server (application.sip.presence.server) Ignore the domain in SIP URI received by Turret PC App (application.tsp.ignoredomain)

•Transport mode and SIP Connection mode can be either UDP or TCP but TCP is recommended for voice communications.

Location: Terminal Boot Settings, TPO Shared Settings, TPO Private Settings, TPO Boot Settings
SIP	SIP Connection mode UDPTCP Key: application.sip.connection.mode Description: Defines whether sip messages will contain UDP contact or TCP contact. The recommended value is TCP. Related settings: SIP connection mode (application.boot.sip.connectionmode) SIP Proxy Transport Type (application.sip.proxy.transporttype) Connection persistence (TCP only) (application.sip.connection.persistency) TPO Connection persistence (TCP only) (application.sip.connection.tpo.persistency)

Location: Terminal Boot Settings, TPO Shared Settings, TPO Private Settings, TPO Boot Settings
SIP	SIP Proxy Transport Type UDPTCP Key: application.sip.proxy.transporttype Description: Defines whether the proxy will be reached using UDP or TCP. This value should be the same as [application.sip.connection.mode] Related settings: SIP Connection mode (application.sip.connection.mode) Connection persistence (TCP only) (application.sip.connection.persistency) TPO Connection persistence (TCP only) (application.sip.connection.tpo.persistency)

•SIP Proxy fall back must be set to "true".

Location: TPO Shared Settings, TPO Private Settings, TPO Boot Settings
SIP	Enable SIP Proxy fall back truefalse Key: application.sip.fallback.enable Description: Defines if TPO SIP proxy fall back is enable When several proxies are configured, TPO initially register lines on the primary one. If the primary proxy break down, TPO fails over the secondary one. When the primary is back "up and running" TPO may fall back on it or remain registered on the secondary. true: TPO falls back on primary proxy when it detects it is back "up and running" false (default): TPO remains on secondary Constraint: true|false Related settings: Fall back from SRST even there are still active calls (application.sip.fallback.from.srst.with.call) Fall back by line (application.sip.fallback.by.line.enable)

The below key is also required for successful SIP Proxy fall back on Asterisk Nodes.

This key must be manually provisioned (in TPO Boot Settings)

TPO Redundancy Mode

The TPO Redundancy Mode needs to be set to "Session Persistency"

Create a line on the TPO cluster

Go to Device Management > TPO Cluster > edit TPO Cluster > TPO Lines > Add New

Create a place for this line

Go to Device Management > TPO Cluster > edit TPO Cluster > TPO Places > Add New

Then start the place in TPO places

Settings in Users or Turrets

It is required to set the following key to false on all users or turrets to avoid an error on the turret during a blind transfer:

profile.setting.transfer.displayerror = false

Location: Terminal Profile Settings, Terminal Boot Settings
User Settings	Display error on transfer truefalse Key: profile.setting.transfer.displayerror Description: The transfer feature generates an error on some PBX system even if the operation is succeed. This parameter allows to display errors from the PBX when using transfer feature Related settings: Ignore the defined PBX error on transfer feature (profile.setting.transfer.ignorederror)