Configure Direct Intercom

In a direct intercom configuration. Two kinds of users exist:

1.The trader who talks to the intercom (named below "the talker")

2.The trader who listens to the talker (named below "the listener" or target)

The talker must have a direct intercom shortcut present in its shortcut.

A user can be configured to be talker and listener. The basic scenario here supposes a non-PBX-registered extension.

The Direct intercom mode option must be defined with IPT value. This value is the default value if the option is not initialized.

Location: Terminal Boot Settings, Terminal Profile Settings
Intercom	Direct intercom mode IPTCISCO Key: profile.setting.direct.intercom.mode Description: Defines if the intercom mode is IPT (between turrets) or CISCO (between turrets and CISCO phones) Constraint: IPT | CISCO Related settings: Direct intercom auto-close (profile.setting.intercom.autoclose) Allow direct intercom close (profile.setting.intercom.direct.allowclose)

Workflow

To make a direct intercom call, the user must :

•be related to at least one TPO. Two possible ways for that:

1)to have a DDI Line configured in its profile

2)to set the following key with a TPO DNS Name active on the TSS:

Location: Terminal Boot Settings, Terminal Profile Settings
Intercom	Preferred lookup service TPO Name Key: profile.setting.intercom.direct.lookup.tpo.service.preferred Description: Defines TPO DNS Name used to resolve direct intercom address lookup. If that setting has empty value, user of device will use first active TPO DNS Name in alphabetical order. It is only taken in account if Direct Intercom Lookup through TPO is enabled. Constraint: string Related settings: Direct Intercom lookup through TPO (profile.setting.intercom.direct.lookup.tpo) Direct Intercom lookup data validity period (profile.setting.intercom.direct.lookup.validity.period)

•Configure a direct intercom shortcut.

•Other options are available to customize the direct intercom shortcuts.

Get IP from TPO

To acquire the IP address associated to an extension when doing intercom, the turret will make a request to its TPO. If the TPO knows the information, it provide immediately data, otherwise it asks to a central TPO named TPO CIA which contacts all active TPOs in order to retrieve data.

By default, the unique TPO CIA is automatically chosen by the TSS. However, it can be manually configured by editing the DNS Name associated to the TPO chosen as the new CIA. Simply check the check-box in the CIA column to define it as the new CIA. Please, also note that to configure  a TPO as CIA, it must imperatively be in a cluster whose redundancy mode is either "Virtual IP", "DNS", or "Session Persistency".

If the TPO CIA is deleted, a new CIA is automatically chosen by the TSS.

Get IP from TSS

By default the direct intercom address lookup is made via TPO. However it is still possible (but not recommended) to rely on TSS to retrieve the IP address associated to an extension when doing intercom:

1.Disable the Direct Intercom lookup through TPO (set the following setting to false):
 

Location: Terminal Boot Settings, Terminal Profile Settings
Intercom	Direct Intercom lookup through TPO truefalse Key: profile.setting.intercom.direct.lookup.tpo Description: Defines if the direct intercom address lookup is made via TPO. Constraint: true|false true: the direct intercom address lookup use only TPO. false: the direct intercom address lookup relies on ITMH or TSS. Related settings: Get target IP from TSS (profile.setting.intercom.usetss) Preferred lookup service TPO Name (profile.setting.intercom.direct.lookup.tpo.service.preferred)

2.Make sure the Direct Intercom lookup through TSS is enabled (remove the following setting or set it to true):
 

Location: Terminal Boot Settings, Terminal Profile Settings
Intercom	Get target IP from TSS truefalse Key: profile.setting.intercom.usetss Description: Defines if the turret tries to retrieve the IP address associated to an extension when doing direct intercom. The sequence is as follows: - look in broadcasting info - if not found, look in TSS info - if not found, request info to TSS If the intercom fails and the info was found in TSS info, the turret tries to re-request this info to get the latest (in case of IP change). Constraint: true|false Related settings: Direct Intercom lookup through TPO (profile.setting.intercom.direct.lookup.tpo)

3.Add the setting service.users.authorization with the value "authenticated" or "all" to authorize users to access the TSS service /users. See Authorization for TSS services.

Inter-TSS Direct Intercom

Direct intercom between two turrets not belonging to the same TSS is possible simply by fetching/synchronizing TPO clusters from other (remote) TSSs. Once the TPO clusters have been fetched, the local TPO CIA obtains information about TPO CIAs of the fetched TSSs. If the local TPO CIA is unable to find the IP address (associated to an extension) requested by a turret for a direct intercom, it simply forwards the request to all known remote CIA TPOs.
 
For a turret connected to a TSS "A" to be able to make a direct intercom to a turret connected to a TSS "B", TPO clusters of TSS "B" have to be fetched in the TSS "A". As for the Static Links between TPOs not belonging to the same TSS, fetching TPO clusters can be performed in TPO Clusters list page. It is as easy as providing the URI of the remote TSS API and clicking on the "Fetch" button (first row in the shrink Box titled “Configuration Fetch”).
 
A TPO clusters re-fetch is necessary as soon as the CIA TPO DNS name of a fetched TSS has changed to keep local information of remote TSSs up to date.