The Connectors view

Totalview uses connectors to receive and send user presence and other information to external systems. Examples of such connectors are phone connectors and calendar connectors or any other connector that can provide information or is interested in receiving Totalview information.

The created connectors and their parameters are used to verify external connectors and to provide connector parameters to external connectors when the external connectors are connecting to Totalview server. When connecting to Totalview the external connector supplies a connector name and. The name and type must be found in the Totalview3Server or the connection will be refused. If found and the license is validated, the connector parameters are returned to the external connector.

 

When creating a new connector and installing the service, the connector parameters must be defined and saved to the Totalview server before the service is installed.

Managing the services

All the connectors are running as services, and if the connectors are running on the same machine as the Totalview server, the user is able to Start and Stop the various services as well as installing or uninstalling the services.

If the connector is not running on the same machine as the Totalview3Server, the user is still able to create the connectors, but the installation of the connector service must then be done manually

 

Overview functions

Refresh
Requery the state of the listed connectors
Install/Update
Install or Update the files for the selected connector(s). The connector service must not be running when updating the connector.
Open Folder
This functionality only works if you are on the server and starts the Totalview Admin in the local folder. That means that the shortcut must point to e.g. C:\Program Files\Formula\Totalview3\Admin\Totalview3Admin.exe
Start (service)
Start the selected connector(s). The connector service must be registered befores starting the service
Stop (service)
Stop the selected connector(s)
Register (service)
Register the selected connector(s). The connector files must be installed before registering the service
Unregister (service)
Unregister the selected connector(s). If the connector is running, the service is not removed until the service is stopped
It is only possible to manage connector services that are running on the same machine as the Totalview  Server. Connector services installed elsewhere must be updated and managed manually (See section 5. Controlling services manually)

Overview listing

Name
The name of the defined connector
Type
The type of the defined connector
Machine
If known, this is the name of the machine where the connector is installed
Version
If known, this is the current version of the installed connector
New version
The newest version of the connector that is available. The new connector files are located in the InstallFiles folder. Update the connector by using the Install/Update button.
Connected
If the connector is connected to the server, this show the time of the connection
Service
Show the state of the connector service
Request result
Shows the result of the requested commands executed on the connector, i.e. Install/Update and service control.

Connector

Name
The name is used throughout the system where this connector must be identified. The name must be unique within the defined connectors

When creating a service based on the connector, the name will be used as part of the service name, e.g. a telephony connector service of the subtype HiPath will be named Totalview3HiPath<name>

The name is also used to verify external connectors. External connectors will only be allowed to connect to the Totalview server if the external connectors name matches one of the defined names in the connector list

Caption
A user friendly name for the connector to be used in user interfaces
Description
Description of the connector
Active
A connector will as default, be created as active. The user can deactivate the connector by unchecking this box
Category, Subtype
The types of connectors that can be created are grouped into categories. For each of the categories there might be one or more subcategories.
 – Telephony
Types of telephony connectors that supply the Totalview Server with user phone status. Subtypes are currently: HiPath, OpenScapeVoice, 3CX and Broadworks.
 – Calendar
Types of calendar connectors that supply the Totalview Server with user appointments. Subtypes are currently: Exchange, LotusNotes,  ExchangeEWS and Exchange Online
– SMS
Types of SMS connectors that gives Totalview Server the possibility to communicate with user by use of SMS messages. Subtypes are currently: SMS
– Mobile status
Types of Mobile connectors used to receive phone status from mobile devices
– Terminal
Types of Terminal connectors, e.g. doorway clients. Subtypes are currently: None
– Web services
Types of web service connectors offering communication with the Totalview server. Subtypes are currently: MobileWeb
– System Extensions
Types of connectors that extend the Totalview System. Subtypes are currently AD connector and OpenScape Office Presence.
Machine
As an extra verification of the connecting external connectors, it is possible to define that the connector is only accepted if it is from a specified machine. The value can be a machine name or an IP address. Mostly, this parameter is left blank.

Category, Subtype parameter settings

The various types of connectors have defined various parameters that are necessary for the connector to run and for interpreting the data from the connectors correctly. When a connector’s connection is validated the parameters are sent to the connector.

The parameter settings for the various parameters are defined in the following sections:

Telephony, HiPath parameters

HiPath connectors connect to Siemens HiPaths and monitors listed devices as well as sending call control commands to the HiPaths.

Supported PBX’s using HiPath connector

The HiPath connector can be used connecting to HiPath 3000 series, OpenScape Office single node and OpenScape Business single/multi node.

OpenScape Office/Business connection

When connecting to OSO/OSB the port is 8800 as default. When using OSB the password must match the password set in OSB administration.

When using OSB multi node there is only need for a single CSTA connection to the master node. The master node then handles the communication with the slave nodes.

Before you start

Additional to the HiPath parameters below, the external trunks and IP trunks for each connected HiPath are to be listed under Devices.

IP address, Port
Address and port of the HiPath PBX
PBX Trunk Code
The digit to dial when creating an external call from the PBX. Usually this is 0
Incoming Trunk Code
Depending on the PBX setup, external incoming A-numbers may or may not have a preceding digit (usually 0). If this is the case, this digit should be defined here so that the incoming numbers can be interpreted correctly
Username and Password
CSTA user name and password. If empty the default is AMHOST and 77777.
International prefix
Usually 00. For example 0045xxxx Denmark and 00298xxxx Faroe Islands.
International code
Country code. For example 45 for Denmark and 298 for Faroe Islands
Area trunk code
In countries that are using open calling number and where an arenas trunk code is used (usually 0), the digit should be defined here so that incoming number can be interpreted correctly

Examples of such countries are Sweden and England

Local start/end
Fill in the first and last local number of all the connected HiPaths. All numbers that are not in the interval are treated as external numbers
Max externally called deviceid
The following two parameters are added to solve a problem with the presentation of the called deviceid. In some situations when external incoming calls travel between nodes, the calledDeviceid is changed from the internal representation to the external representation. When this occurs Totalview is not able to map the calledDeviceid with the correct user. N.B. This check is only needed in special cases and when multiple nodes are connected. Do only use if problem appears.
Enable max local digits
Enable the test of the max length of the calledDeviceid as explained above.
Max length
Set the max length of externally called calledDeviceid’s. E.g. if an external incoming call is calling deviceid 4095, but a travel through nodes changes this to 344095, then a max length of 4 assures us that Totalview interprets this as 4095.
Max national digits
In some cases the CSTA callingDevice and calledDevice do not contain the international prefix (typically 00). Totalview uses the 00 to differentiate between international and national calls.

Setting the max national digits helps solve this problem when it occurs. E.g. national digits are 22334455 (8 digits) and international call is 4622334455 (10). Using this parameter Totalview can differentiate between the calls. N.B. This check is only needed in special cases and when multiple nodes are connected. Do only use if problem appears.

Wait for delivered
When blind transferring calls to external devices, the HiPath connector by default does not wait for a delivered event before transferring the call.

In some situations this might cause problems for third party monitoring software.

When “Wait for Delivered” is enabled, the HiPaths wait for the delivered event before transferring the call.

N.B. Waiting for the delivered event before transferring the call might slow down transfers to external devices – especially if the external device is a mobile device.

Always add trunk code
When “Always add trunk code” is enabled the Totalview server will add the outgoing trunk code to external numbers. E.g. if the user enters 05000, then the HiPath will dial 005000
Generate call statistics
Enable to generate call statistics data from the HiPath connector. The “Call statistics enabled” settings under “Server settings” must also be enabled to generate call statistics data. Default value is true.
Use ClearConnection
When enabled, ClearConnection is used in Consult/Transfer calls instead of the default TransferCall. Using TransferCall sometimes result in undesired behavior on HiPath installations. If experiencing problems with BlindTransfer or Consult/Transfer then enabled “Use ClearConnection”.

N.B. TransferCall is required when using OpenScape Business.

Master OSB node When using OpenScape Business in nodes and using one TotalviewHiPath connector per node, the DeviceIDs will first be initialized on non-master nodes.
If a DeviceID is not found on non-master nodes then is initialized against the master node.
This solves the problem with DeviceIDs being initialized both on slave and master.
Only one TotalviewHiPath connector should be set as master.

Internal representation of external numbers

The Totalview server uses the values defined in Incoming Trunk Code, International prefix, International code and Area trunk code to convert external numbers to fully qualified numbers.

Fully qualified numbers means that numbers are defined with the international code, e.g. +4532003200 or +4670320032.

For closed number plans, like Denmark, the A-number 32003200 is changed to +4532003200.

For open number plans, like Sweden, the A-number 016320032 is changed to +4616320032.

When Totalview is looking in the phonebook for owners of incoming A-numbers the fully qualified number is used. Registered numbers in the phonebook must therefore also be fully qualified.

 

Monitoring external numbers

External numbers can be monitored when the HiPaths external trunks. The external numbers must be registered as fully qualified in Users for the monitoring to function properly.

Examples for fully qualified numbers are:

Country
Number
Denmark
+4512345678
Norway
+4712345678
Sweden
+4612345678
Finland
+35812345678
Faroe Islands
+298123456


Normally used settings
:

Country
International prefix International code Area code trunk
Denmark
00 45
Norway
00 47
Sweden
00 46 0
Finland
00 358 0
Faroe Islands
00 298

MULAP monitoring

In CSTA V8 changes are made to the HiPath software that enables monitor on MULAP groups. Totalview implements MULAP monitoring.

When using MULAP monitoring the CallControl and Events changes. MULAP monitoring is enabled using the HiPath using Manager E. The setting is found under System parameters.Plus product flags. MULAP monitoring is always enabled when using OpenScape Business

MULAP group numbers must be registered as the users default local device and not as a MULAP number.
Registering MULAP member devices is optional.

When using MULAP monitoring the following applies:

  • SetDoNotDisturb is not implemented for MULAP number. Totalview contains a work around for this problem.
  • If changing MULAP monitoring in HiPath Plus Product Flags, the connector must be restarted for the changes to be reflected in Totalview.
  • If deactivating MULAP monitoring in HiPath Plus Product Flags, the HiPath must be restarted for the changes to take effect.

In OSB the “MULAP monitoring” behavior have changed compared to HiPath v9.

The MULAP device is seen as the users single contact point and it is not possible to monitor member devices. This results in the following:

  • No events are generated for calls directly to the member devices. Events are only generated for calls to the MULAP device.

It is there for not possible for Totalview to show direct calls to MULAP member devices.

  • No events are generated for DND on MULAP device or members.

Totalview is not notified if DND is set on the MULAP or MULAP member devices.

This might result in Totalview showing the wrong DND state if DND is set using service codes and not the Totalview client.

IP monitoring

The following applies if using HiPath. This is not required if using OpenScape Business.

If using the Plus product function “Networked-CTI domain”, available in CSTA v8 MR5, the following Totalview setup must be true.

  • The Behaviour Configuration “Wait for Delivered” must be enabled in Admin.Connectors.Hipath connector. If not, transfers to another node over IP will fail.
  • Only external trunks must be listed in Admin.Devices.Trunk Devices. If IP trunks are listed, retrieving calls transferred to antother node over IP will fail.

Telephony, BroadWorks parameters

BroadWorks connectors connect to Broadsoft BroadWorks systems and monitors devices as well as sending call control commands to the system.

The Totalview3BroadWorks connector connects to BroadWorks using CTI commands that are sent using http REST requests.
At the same time BroadWorks reports events to the Totalview3BroadWorks connector using http request sent to a dedicated address and port.
For the systems to be able to communicate eventual firewalls must be configured to allow and, if necessary, route messages between the Totalview server and BroadWorks server.
Server address
URI of the BroadWorks server in the format http://address. Totalview uses this address then sending CTI commands to the BroadWorks server.
Local address
Address in the format http://address:port where BroadWorks will send events as result of a subscription method. The Totalview3BroadWorks connector will listen and act upon these events. If necessary the events must be routed to the machine where the connector is located.
Listener port
Port on the local machine where the Totalview3BroadWorks connector will listen for http event messages send from BroadWorks.
User/Password
Username and password to use when connecting to BroadWorks. The User must be a user with group admin privileges.
Enterprise ID/Group ID
When subscribing for events the Totalview3BroadWorks connector will subscribe for all devices belonging to a specific group. The group is identified by the Enterprise ID and Group ID. If monitoring more than one group in the enterprise, the groups are separated by semicolon.
Version
Current version running on the BroadWorks system. Currently tested versions are 17.sp4.
Log messages
Enable to log the messages sent from the Totalview3BroadWorks connector to the Totalview server.

N.B. There might be many messages to log depending on the traffic on the BroadWorks server. This might slow down the Totalview server.

International prefix
Usually 00. For example 0045xxxx Denmark and 00298xxxx Faroe Islands.
International code
Country code. For example 45 for Denmark and 298 for Faroe Islands
Local start/end
Fill in the first and last local number in the connected BroadWorks system. All numbers that are not in the interval are treated as external numbers
Generate call statistics
Enable to generate call statistics data from this BroadWorks connector. The “Call statistics enabled” settings under “Server settings” must also be enabled to generate call statistics data. Default value is true.
Called hierarchy
Defines a hierarchy list of device id’s that controls what number is set as called device. This setting is especially useful if the initial called device is an IVR or distribution group and the reports should show the load on the group members.

E.g. a main number 100 is an IVR that, based on user selection, distributes the calls to 200, 300 or 400. Default behavior is to set 100 as the called device, but if the reports instead should show the calls arriving to 200, 300 or 400, a Called hierarchy could be defined. In the above example the hierarchy would be 100(200,300,400).

Transfer barge groups
Defines a group of devices allowed to transfer calls to devices that have their forwarding (All) set back to a device in the group.

The main purpose is to allow the receptionist to barge through a forwarding that is set to the receptionist itself. E.g. a group of receptionists (4000, 4001, 4002) that handles incoming calls and where staff devices are forwarded to the main number 4000 in case the staff are unavailable.

The rule is that if there is a group G with members (A, B) and a group member is transferring to a device that is forwarded back to a member of the group G, then transferring is allowed to barge through the forwarding.

The list of devices are separated by comma (,). Multiple groups can be separated by semicolon (;).

BroadWorks Remote Office

Remote Office is a service on BroadWorks that creates a logical connection between a local device and an external number.

When enabled, all calls to the local device are forwarded to the external device. If a physical phone is attached the local device, then call do not appear on the local device, but call control and device control can still be executed on the local device.

 

When using Remote Office, calls forwarded to an external device can be Transferred, Consulted, Held, Cleared etc. using Totalview. When initiating a call using Totalview BroadWorks calls the external device and then transfers the call and performs a remote call on behalf of the local device and thus the external device will behave much like a DECT device.

 

It is recommended that mobile users with no local device enable the Remote Office service. There is no need to enable Remote Calling in Totalview when using Remote Office.

 

Calendar connectors

The calendar connectors monitors listed users and notifies Totalview when changes happen in a user’s appointments list. The connector also sends create, update and delete commands from Totalview to the calendar server.

Calendar synchronization rules

Not all users or appointments created in Totalview are synchronized with the calendar server. The following rules state what users and appointments are synchronized with the calendar server.

  • Only active users with a valid Calendar ID and with Synchronize Calendar enabled are synchronized. These settings are available in Admin/User
  • Only appointments with state class of type Busy or OutOfOffice are synchronized. State class settings are available in Admin/State
  • Totalview is not allowed to update or created recurring appointments
  • When appointments created in Totalview are synchronized with the CC, the CC returns a calendar key that is used in subsequent requests on the same appointment
  • When appointments updated in Totalview are synchronized with the CC, the CC updates the appointment in the calendar system based on the calendar key
  • When appointments deleted in Totalview are synchronized with the CC, the CC deletes the appointment in the calendar system based on the calendar key

Not all users and appointments created in the calendar server are synchronized with Totalview. The following rules state what users and appointments are synchronized with Totalview.

  • Only users requested by the Totalview server will be synchronized
  • Only appointments with type of Busy or OutOfOffice are synchronized. (Lotus Notes and Google Calendar only has the Busy option).
  • Appointments with subject starting with * are not synchronized (* is the default setting but can be changed in the calendar connector setup)
  • Private appointments are synchronized with the subject set to the text “private”
  • Recurring appointments are synchronized for a defined number of days ahead. This is necessary to reduce the number of appointments returned from the calendar connector. The number of days is specified in the Admin/Connectors
  • When synchronizing an appointment that is not created or modified in Totalview, i.e. is created in the calendar server, the appointments start and end state is based on the Busy profile shortname and the OOF profile shortname specified in the Admin/Connectors. Notes connector can also use categories to map states to appointments.

Below are the extra rules applied if Synchronize current is enabled. N.B. This feature is both available for the Exchange connector, Lotus Notes Connector and Google Calendar.

  • Current states with state class of type Busy and OutOfOffice and where End type is set to Actual or Expected are synchronized.
  • If a new current state is set prior to Actual or Expected end of the synchronized state, no additional synchronization occurs. I.e. if current state is synchronized from 13.00 to 14.00 and the user changes to another state at 13.30, the calendar appointment will still show 13.00 to 14.00.
  • If the current state goes beyond the Expected end, no additional synchronization occurs. I.e. if current state is synchronized from 13.00 to 14.00 and no new state occurs at 14.00 then the Exchange appointment will still show 13.00 to 14.00.
When creating a new connector and installing the service, we recommend that the connector parameters are defined and saved to the Totalview server before the service is installed.

Exchange parameters

The Exchange connector monitors listed users and notifies Totalview when changes happen in a user’s appointments list. The connector also sends create, update and delete commands from Totalview to the Exchange server.

Do notice that if running the Exchange connector with the service credentials, it is necessary to use the service manager to enable the service to run under the Totalview service user. A description of creating the Totalview service user is specified in the Exchange security guide.

 

Before you start

The Exchange connector uses WebDAV or EWS to query information from the user’s calendar folder. To be able to query the user, a user must be created with rights to query user’s calendars. See the Exchange security settings guide.

URI (using WebDAV)
http:// <server name>/exchange. This is the URL/URI to the Exchange server where the WebDAV request will be sent
URI (using EWS)
http:// <server name>/. This is the URL/URI to the Exchange server where the Exchange web service request will be sent
URI (using Exchange Online)
When using Exchange Online no server URI is provided. The server is found based on the username, e.g. name@domain.onmicrosoft.com
Username
Query user with access to all the attached users’ calendars.

N.B. When using service credentials, username should be left blank. The use of service credentials is listed in the Totalview Exchange security guide. Service credentials cannot be used when connecting to Exchange Online

Password
Password for user with access to all calendars.

N.B When connecting to Exchange Online the password must not contain any of the reserved XML characters. The five reserved characters are < (less than), & (ampersand), > (greater than), ” (quotation) and ‘ (apostrophe).

N.B. When using service credentials, password should be left blank

Scrambled
The password can be saved scrambled in the Totalview server. Set the checkmark if the password is scrambled. Use the program “Totalview Password Scrambler” located in the InstallFiles folder to scramble the passwords.
Domain
The query user domain. Used when authentication the query user on the Exchange. The domain should be the NetBIOS name or the fully qualified domain name (FQDN). Domain is not set when using Exchange Online
Use FBA
Set the checkmark if Form Based Authentication is used when connecting to the Exchange server. Use FBA is not set when using Exchange Online
Recurring days ahead How many days forward, should recurring appointments from Exchange be shown in Totalview. This is necessary to be able to limit the number of recurring appointments retrieved from Exchange
Busy template
Select the template to use for Busy Exchange appointments. Appointments with state Busy in Exchange are mapped to this template when retrieved and shown in Totalview. If the Busy template is changed, the Exchange connector must be restarted to apply the new template
Out of office template

Select the template to use for Out of Office Exchange appointment. Appointments with state Out of Office in Exchange are mapped to this template when retrieved and shown in Totalview. If the Out of Office template is changed, the Exchange connector must be restarted to apply the new Template

Syncronize current
If enabled then Change state (current state/F5 in the client) settings are synchronized with the Exchange calendar. See the synchronization rules in: The Totalview server synchronization rules in the Totalview Calendar Technical guide.
Tentative Select the template to use for Tentative Exchange appointment. Appointments with state Tentative in Exchange are mapped to this template when retrieved and shown in Totalview. If the template is changed, the Exchange connector must be restarted to apply the new template. If no template is selected the Tentative appointments are not show in Totalview.
Working elsewhere Select the template to use for Working Elsewhere Exchange appointment. Appointments with state Working Elsewhere in Exchange are mapped to this template when retrieved and shown in Totalview. If the template is changed, the Exchange connector must be restarted to apply the new template. If no template is selected the Tentative appointments are not show in Totalview.
Working Elsewhere is supported in Exchange 2013 and newer.
Synchronize current If enabled then Change state (current state/F5 in the client) settings are synchronized with the Exchange calendar. See the synchronization rules in section: The Totalview server synchronization rules in the Totalview Calendar Technical guide.
Valid until end


Is used with Fallback appointments (See: Promoting appointments with fallback for more information)
Exchange version


Specify exchange version (Not defined, Exchange 2007, Exchange 2007 SP1, Exchange 2010, Exchange 2010 SP1, Exchange 2013, Exchange 2013 SP1). This only applies to ExchangeEWS
Ignore char When synchronizing, appointments with subject starting with the ignore char are ignored and not shown in Totalview. The default value is *.
If the char is changed, the Exchange connector must be restarted to apply the new rule.
If forwarding rules have influence on the phone settings of synchronized appointments, and the forwarding rules changes, then the Exchange connector must be restarted to apply the new phone settings.

Lotus Notes parameters

The Lotus Notes connector monitors listed users and notifies Totalview when changes happen in a user’s appointments list. The connector also sends create, update and delete commands from Totalview to the Lotus Notes Domino server.

Specific Lotus Notes issues

Using service credentials. It is not possible to use service credentials when using the Lotus Notes connector. Username and password must be passed from the Totalview server.

Recurring appointments. When handling recurring appointments, Lotus Notes only creates one appointment and lets the rules for the recurring appointments be stored in this one appointment. Currently the CC only looks for appointments created within the last 12 months. That means that if a recurring appointment is created more that 12 months ago, it will not be synchronized with Totalview.

Query user rights. Lotus Notes calendar users must grant the query user access to their calendar folder. There is no global setting allowing the query user access to other users’ calendar folders.

Before you start

The Lotus Notes connector uses the Lotus Notes client API to query information from the user’s calendar folder. To be able to query the user, the Lotus Notes client must be installed on the same machine as the Lotus Notes connector and a user must be created with rights to query user’s calendars.

Lotus Notes IP address
This is the IP address of the IBM Lotus Domino server.
Username
Query user with access to the attached users’ calendars
Password
Password for user with access to all calendars. The password can be saved scrambled or unscrambled. If scrambled then the Scrambled property must be set to true. Use the “Totalview Password Scrambler” to scramble the password (located in the InstallFiles folder)
Scrambled
The password can be saved scrambled in the TV3 server. Set the checkmark if the password is scrambled. Use the program “Totalview Password Scrambler” located in the InstallFiles folder to scramble the passwords.
Recurring days ahead
How many days forward, should recurring appointments from Lotus Notes be shown in Totalview. This is necessary to be able to limit the number of recurring appointments retrieved from Lotus Notes
Ignore char When synchronizing, appointments with subject starting with the ignore char are ignored and not shown in Totalview. The default value is *.
If the ignore char is changed, the connector must be restarted to apply the new rule.
Busy template
Select the template to use for Busy Lotus Notes appointments. Appointments with state Busy in Lotus Notes are mapped to this template when retrieved and shown in Totalview. If the Busy template is changed, the Lotus Notes connector must be restarted to apply the new template
Categories Mappings
Specify mappings between states and categories. For more information See: Notes categories synchronization
If forwarding rules have influence on the phone settings of synchronized appointments, and the forwarding rules changes, then the Exchange/Lotus Notes connector must be restarted to apply the new phone settings.

Google Calendar parameters

The GoogleCalendar connector monitors listed users and notifies Totalview when changes happen in a user’s appointments list. The connector also sends create, update and delete commands from Totalview to Google Calendar.

 

Before you start

The GoogleCalendar connector uses the GoogleCalendar API and service credentials to access the users’ calendar folder. Details on setting up the service credentials can be found in “Google Calendar settings“.

Account name The name of the create GoogleCalendar service application.
Certificate filename
The name of the GoogleCalendar service certificate. If the path to the file is not included, the certificate must be located in the same folder as the TotalviewGoogleCalendar executable.
Password
Password for the GoogleCalendar service certificate.
Initial user
An initial user used to the the access to Google Calendar.
Recurring days ahead
How many days forward, should recurring appointments from Google Calendar be shown in Totalview. This is necessary to be able to limit the number of recurring appointments retrieved from Google Calendar
Busy template
Select the template to use for Google Calendar appointments. Appointments in Google Calendar are mapped to this template when retrieved and shown in Totalview. If the template is changed, the Google Calendar connector must be restarted to apply the new template
 Ignore char When synchronizing, appointments with subject starting with the ignore char are ignored and not shown in Totalview. The default value is *.
If the ignore char is changed, the connector must be restarted to apply the new rule.
If forwarding rules have influence on the phone settings of synchronized appointments, and the forwarding rules changes, then the GoogleCalendar connector must be restarted to apply the new phone settings.

SMS Services

The SMS connector receives SMS messages from Totalview and sends SMS messages on request.

Currently there are two services that handle the sending of SMS messages from Totalview, the SMS Box and LinkMobility.

SMS Box parameters

The SMS is of the SMS Service Type, this service enables Totalview to send SMS messages. SMS messages sent to Totalview can be used to change current state setting or request users contact information.

COM Port
Fill in the value of the serial port the GSM station is connected to
Baud rate
Fill in the Baud rate (300, 600, 1200, 2400 etc. – 115200)
Pin
The Pin code of the SIM card (4 digits)
Service centre
The number of the SMS gateway of the GSM provider
Preferred Storage
Select how the messages should be saved on the GSM station. The options are: SIM Card which saves on the SIM card, GSM Memory which saves on the memory on the GSM station and Both which does both
Start up Script
The name of the script file with possible instructions to the GSM station, while configuring the SMS connector first time. This parameter is optional.
Prefix
The country code that is set in front of numbers without country code, e.g. 45 (Denmark) and (46 Sweden).
Drop nat. digits
Digits to remove in front of international telephone numbers which do not have the standard + or 00 country code prefix.
Input Only
Set the checkmark if the GSM station should be allowed to send messages.
State Change Receipts
Set the checkmark if the GSM station should send receipt to the Users when Receiving  Change State messages.
SMS syntax 2.0

Set the checkmark if the syntax 2.0 is used. The syntax 2.0 allows the user to select a state or a template when changing state using SMS messages

Message to known users

If a user with a registered mobile number in Totalview sends an unknown command to Totalview via SMS, the system can reply a specific message to the user.

Message to unknown users

If a user, not existing in Totalview, sends an unknown command to Totalview via SMS, the system can reply a specific message to the user.

LinkMobility

The LinkMobility is of the SMS Service Type, this service enables Totalview to send SMS messages.

LinkMobility Support will provide you with the following information:

  • Username, Password, Platform Parrent ID, Platform ID, Gate ID.

Request URI should be set to “https://wsx.sp247.net/sms/send”

Sender information is the string that is shown as “From” on sms messages, it can be any text within 2-11 Character range.

Using this feature to impersonate other parties will lead to a termination of your LinkMobility account

 

Mobile Connectors

Connectors of the mobile status type enables Totalview to display the status (idle/busy) of mobile phones in the Totalview client. To enable mobile status, a service agreement must be done with a corresponding telecom operator.  The service operator sends messages about the mobile status to the connector through an external URI:Port.

Sonofon Connector parameters

The Sonofon connector is of the mobile status type. Sonofon includes to their service a SIM application which makes it possible to change user status or appointments from a mobile phone.

Sonofon sends mobile status to a specific port on the machine where the connector is installed

Sonofon web service port
Port the Sonofon web service uses for mobile and user state changes sent from Sonofon
Lunch state
Select the state corresponding to “Lunch” state in Totalview
Meeting state
Select the state corresponding to “Meeting” state in Totalview
Home state
Select the state corresponding to “Home” state in Totalview
Sick state
Select the state corresponding to “Sick” state in Totalview
New state on deactivate
Select the state to change into when deactivating current appointment

 

TDC/Telia Connector parameters

The TDC/Telia connector is of the mobile status type. It enables visual displaying of mobile phone status (idle/busy/off) in the Totalview client.

TDC has to register in their system the address http://IP:Port

TELIA has to register in their system the address http://IP:Port/telia.asmx

URI in the Admin must be registered as http://IP:Port/ (must end with a slash) The IP address is the IP of the machine where the connector runs.

 

Listening port
Port where Totalview is listening for messages from TDC/Telia.

TDC/Telia are sending SOAP requests to this uri to inform Totalview about changes in the mobiles states. TDC/Telia must be informed where to send the requests.

International prefix
International prefix to be used to fully qualify the mobile numbers. I.e. if international prefix is 00 then mobile numbers like 0045xx are changed to +45xx.
International code
International code to be used to fully qualify the mobile numbers. I.e. if international code is 45 then mobile numbers like 34400000 are changed to +4534400000.
Device timeout
If no messages arrive from TDC/Telia in the specified timeout period, then it is assumed that some error has occurred and all mobile states are cleared.

Unitel Connector parameters

The Unitel connector is of the mobile status type. It enables visual displaying of mobile phone status (idle/busy) in the Totalview client.

Unitel has to register in their system the address and port where to send the mobile state messages. The Unitel connector will listen on the port defined.

Port
Port on the machine where the Unitel connector is listening for messages from Unitel.
International prefix
International prefix to be used to fully qualify the mobile numbers. I.e. if international prefix is 00 then mobile numbers like 0045xx are changed to +45xx.
International code
International code to be used to fully qualify the mobile numbers. I.e. if international code is 45 then mobile numbers like 34400000 are changed to +4534400000.
Device timeout
If no messages arrive from Unitel in the specified timeout period, then it is assumed that some error has occurred and all mobile states are cleared.

Telenor Connector parameters

The Telenor connector is of the mobile status type. It enables visual displaying of mobile phone status (idle/busy) in the Totalview client.

The Telenor connector connects to the Telenor service using a provided username and password. If access is granted the connector receives mobile state events from Telenor.

Username/Password
Username and password granted by Telenor
PNI
Customer ID identifying the use at the Telenor service. Supplied by Telenor
Application ID
ID identifying the application at the Telenor service. Default is Totalview and should not be changed unless requested.
Request URL
Address of the Telenor service. Default is https://mpgw.telenor.dk and should not be changed unless requested.

Web service connectors

Connectors of the web service status type enables Totalview to communicate with external systems using web services.

Totalview Mobile Web Application parameters

The web client connector enables web client to communicate with the Totalview server using standard SOAP requests.

The web client can request information from the Totalview server and display it on the client. The web client can also send commands such as change current state to the Totalview server.

WCF endpoint address
Enter the endpoint address for the WCF connector.
Use mobile password
If selected there will be two user passwords. One when logging in to the smart clients and one using the pc client.

Generally the mobile password should be more secure than needed for the pc client.

Min. password length
Define the minimum length of the passwords used when logging in from the smart clients.
Prefix intervals
The prefix interval setting is used to map local number to their external fully qualified numbers.

Local numbers are stored without area and trunk codes, but when listing the local number on the mobile devices, they should be listed as fully qualified; otherwise the mobile devices can not dial the numbers.

E.g. local number 4000 should be listed as +45xxxx4000 so that the mobile device can dial the numbers.

The order of the rules is essential. The first rule that matches the local number will be used.

Star/End local
Defines what devices will use the specified prefix. All devices within the interval will have the prefix applied to their local number when listed on the mobile device.
Max length
In case the local numberplan is x4000 and the external numberplan is xxxx4000, then only the last 4 digits should be used. Set the max length if only a part of the local number should be used – otherwise leave max length blank.
Prefix
Define the prefix to put in front of the local number to be able to list it as fully qualified. In the example above the prefix would be set to +45xxxx.
Enable win login
Enable use of the UserWinLogin web service method. Enables login using the users win login. Can e.g. be used when logging in using a Sharepoint client. Admin username and password must be set to use this service.
Admin user
Username when calling the UserWinLogin web service or when logging in using the PublishClient or ExternalClient.
Admin password
Password when calling the UserWinLogin web service or when logging in using the PublishClient or ExternalClient.

Prefix interval examples

Below are two examples for what prefix interval settings to use when local number are mapped to external numbers.

Local numbers 100 to 199 are externally known as +4533449100 to +4533449199.

  • Start/End local : 100-199
  • Max length : <empty>
  • Prefix : +4533449

Local numbers 100 to 199 are externally known as +4533449500 to +4533449599.

  • Start/End local : 100-199
  • Max length : 2
  • Prefix : +45334495

System Extensions

Extends the Totalview system with additional connectors, e.g. the AD Connector.

Lync presence connector

The Lync presence connector enables presence integration between the Lync server and the Totalview server.

The Lync presence connector uses UCMA 3.0 to communicate with the Lync server. The UCMA establishes a trusted application connection with the Lync server to be able to monitor Lync users and retrieve and set their presence and phone state.

A trusted application must be created on the Lync server for the Lync connector to be able to communicate with the Lync server. The trusted application must be validated by a user with AD administrator credentials.

UCMA requires 64 bit machines and the UCMA runtime or the Lync client must be installed on the machine where the Lync connector is running.

The server and Lync connection can be tested using the Totalview3LyncTester program.

Lync connector parameters

GRUU
GRUU address for the trusted application created on the Lync server. Use the Lync Powershell command Get-csTrustedApplication to see a list of trusted applications. Example:sip:totalview.formula.fo@formula.fo;gruu;opaque=srvr:TotalviewLync:W1w6QAeAA
Port
Trusted application port. Use the Lync Powershell command Get-csTrustedApplication to see a list of trusted applications.
Certificate Friendly name of the certificate authenticating the server to the Lync server. Certificate can be created using the Lync Powershell command Request-CsCertificate.
Application endpoint
SIP address of a trusted application endpoint created on the Lync server. Use the Lync Powershell command Get-csTrustedApplicationEndpoint to see a list of trusted application endpoints.
Registrar port
Lync server registrar port. Default is 5061
Registrar FQDN
Lync server registrar FQDN.


Trusted application setup

Use the Lync Powershell with sufficient user rights to create the trusted application.

More information can be found at MSDN http://msdn.microsoft.com/en-us/library/lync/hh347258(v=office.14).aspx

  1. Create a trusted application pool where the trusted application will reside.Lync PS: New-CsTrustedApplicationPool -Identity <tvapps.domain.com> -Registrar <lync server name> -Site <Site id> -ComputerFqdn <local computer name> Use Get-CsSite to list the Site IDs on the Lync server.Example:New-CsTrustedApplicationPool -Identity tvapps.formula.fo -Registrar srv-lync.formula.fo -Site 1 -ComputerFqdn totalview.formula.fo
  2. Create a trusted application for the Lync connector to connect toLync PS: New-CsTrustedApplication -ApplicationId <AppID> -TrustedApplicationPoolFqdn <Application Pool ID> -Port <port>Example:New-CsTrustedApplication -ApplicationId TotalviewLync -TrustedApplicationPoolFqdn tvapps.formula.fo -Port 6000The specified port must be open for TCP communication in firewalls.
  3. Create a trusted application endpointLync PS:New-CsTrustedApplicationEndpoint -SipAddress <sip address> -DisplayName “Totalview Lync” -TrustedApplicationPoolFqdn tvapps.formula.fo -ApplicationId TotalviewLyncExample:New-CsTrustedApplicationEndpoint -SipAddress sip:totalview@formula.fo -DisplayName “Totalview Lync” -TrustedApplicationPoolFqdn tvapps.formula.fo -ApplicationId TotalviewLync
  4. Request a server certificateA web server certificate is used to enable the Lync server to authenticate the server connecting to the trusted application.Lync PS: Request-CsCertificate -New -Type default -FriendlyName <name> -ca <certificate authority> -ComputerFQDN <local machine name>Example:Request-CsCertificate -New -Type default -FriendlyName “tvapps.formula.fo Pool” -ca “ca.formula.fo\Formula Root CA” -ComputerFQDN totalview.formula.fo
  5. Enable the topologyAn AD administrator must verify the trusted application and enable its topology using the Lync PS:Enable-csTopology command.

AD connector

The AD connector enables read only import of user information from Microsoft Active Directory (AD).

The AD connector does not enable importing of users from Notes.

Using the AD connector, the user can import users and groups from AD using the Select  AD Users function. The AD integration can also be set up to import users automatically at specific times.

The AD connector requires a valid license to be able to connect to the Totalview 3 server.

The TotalviewADTester program can be used to test the settings to be used when reading user information from AD. The tester program is found in then <Totalview>\InstallFiles\AD folder.

 

AD connector parameters

LDAP address
The path in ActiveDirectory to use when importing users. Only users belonging to the path or groups in the path are imported. If blank, all users in AD are imported.

Examples of LDAP paths are listed below.

Username/Password
In case the user running the AD connector does not have access to ActiveDirectory, credential for a user with access can be added.

Add Username and Password for a user with access to ActiveDirectory. The Username should be in the format user@domain.com.

The LDAP address must specify ad domain, or the IP or name of the AD server. E.g. domain.com, srv-ad or IP address.

When username/password are used the authentication method use is Secure.

Users filter group
Optional LDAP path to group in ActiveDirectory with users to import into Totalview. Only users in the group are imported. If path is left blank all users in the LDAP address path are imported.

It’s required that the Users filter group path is within the LDAP address path.

Ignore paths
Optional LDAP path to filter out users with an ending path equal to specified path. E.g. filter out all users with ending path “ou=Users,dc=Contoso,dc=Com”.

Multiple paths to ignore can be separated by ;.

Device length
Part of the WORK number to be used as local device number in case of fully qualified WORK numbers. E.g. if WORK number is registered as (+45)34123400 then a Device length of 4 will result in a local device number of 3400. If Device length is 0 no changes are made to the WORK number.
Trim numbers
Remove blanks from phone numbers when importing.
Remove parentheses
Remove parentheses from phone numbers when importing.
Include security groups
Include AD security groups in the AD search result. Default is false.
Mapping parameters
If required the default mapping between Totalview fields and AD properties can be changed. Change the default mapping by adding a new mapping for the Totalview field. The default mappings are listed in appendix VII.

 

Examples of LDAP paths

Path
Description
<Empty>
The entire local AD is imported.
LDAP://contoso.com
The entire contoso.com AD is imported
LDAP://ADservername or IP
The entire AD is imported.
LDAP://OU=TVUsers,DC=contoso,DC=com
Users and groups under the TVUsers group are imported.
LDAP://IP/OU=TVUsers,DC=contoso,DC=com
Users and groups under the TVUsers group on the specified ad server are imported.

 

Active directory sync settings

Sync with AD
Activate automatic synchronization with AD. When activated the synchronization will be performed once a day at the hour specified in Sync every day at.

The synchronization will read from the current AD and update users in Totalview accordingly.

Sync every day at
Hour of day, in 24 hour format, when to run the automatic AD synchronization.

OpenScape Office connector

The OpenScape Office (OSO) connector enables synchronization of user presence from OSO to Totalview. When users change their presence in OSO, the presence will be synchronized and the users current state in Totalview will be set accordingly.

The mapping between OpenScape Office presence and Totalview states are set in the OSO connector.

Before you start

Use the Totalview3OsoTest application to test the connection to OpenScape Office. You need a web user account on OpenScape Office to be able to login.

The following rules apply when using the OSO connector

  • Only users with OSO user id defined in Users will by synchronized.
  • If no mapping exists between the OSO presence and the Totalview state, then the presence will not be synchronized.
  • The synchronization is one way. Presence changes made in OSO will be synchronized with Totalview, but state changes in Totalview made by e.g. the switchbard will not be synchronized with OSO.

 

OSO connector parameters

Server:port
The OSO web service address in the format http://IP:port. The port defaults to 8801
Username
Username of the query user with access to the OSO web service
Password
Password for the query user
Polling interval
Interval in milli seconds between each polling. The polling checks for changes in the OSO presence.
State settings
Mapping between OSO presence and Totalview templates.

Telephony, 3CX parameters

3CX connectors connect to 3CX system and monitors devices as well as sending call control commands to the 3CX system.

The Totalview3CX connector connects to 3CX using the 3CX API.
The 3CX system requires that access from the 3CX API is established from the same machine as where 3CX is running. This means that the Totalview3CX connector also must be installed on the same machines as where 3CX is running.

N.B. It’s not required that the Totalview3CX connector runs on the same machine as the Totalview3Server service.

Config port
Port of the 3CX config server. Default is 5485.

When running multiple hosted 3CX instances the config port differs between the instances.

PBX port
Port of the 3CX PBX server. Default is 5482. When running multiple hosted 3CX instances the PBX port differs between the instances.
Server User/Password
Username and password to use when connecting the 3CX API to the 3CX system. The information can be found in the 3CXPhoneSystem.ini file.
PBX User/Password
Username and password to use when connecting the 3CX API to the 3CX system. The information can be found in the 3CXPhoneSystem.ini file.
International prefix
Usually 00. For example 0045xxxx Denmark and 00298xxxx Faroe Islands.
International code
Country code. For example 45 for Denmark and 298 for Faroe Islands
Local start/end
Fill in the first and last local number in the connected 3CX system. All numbers that are not in the interval are treated as external numbers

Outbound Caller ID settings

The extensions Outbound Caller ID can be changed using the clients phone settings, and by changing state and activating appointments.
Valid Outbound Caller IDs are the users own work or mobile number, numbers defined in templates and forwarding rules, and optionally an empty string.

Allow blank Caller ID
Determines if the Outbound Caller ID can be set to an empty string.

State synchronizing settings

Using 3CX state synchronization changes in 3CX user profiles are synchronized with Totalview, and changes in Totalview state is synchronized with 3CX. This enables the Totalview user to see the actual 3CX state, and the 3CX user to see the actual Totalview state.

Synchronizing states between 3CX and Totalview requires basic user license.
3CX Profile mappings
Define what Totalview template should be used when 3CX Profile is changed.

When synchronizing 3CX states with Totalview, any forwarding rules defined in the mapped template is ignored.

N.B. At 3CX connector start-up, only users with current state not originating from an appointment are synchronized.

Totalview State mappings
Define what 3CX Profile should be used when Totalview state changes.

When synchronizing Totalview states with 3CX, any forwarding rules defined in the Totalview template are synchronized with the 3CX state OOF2 (All,External, Internal) and Available (None).

Yealink phone call control

Totalview is able to extend the call control offered by 3CX, by using the Action URI functionality offered by Yealink phones.

The following call control methods are available using Action URI and Yealink:

  • Hands free AnswerCall and MakeCall
  • ConsultationCall with Trasnfer or Reconnect
  • Hold/Resume on the Yealink phone.

To be able to user Action URI’s the security settings on the Yealink phones require that remote control access is allowed.

Add the callers IP address to list of trusted IP’s.
See “Yealink_SIP-T4X_IP_Phone_Family_Administrator_Guide_V72_2” for more information.
When the first call is sent to the phone, the user must accept the use of remote control.

Device ID
The Yealink phones device ID as known in Totalview
Address
IP address of the Yealink phone. Action URI requests are sent to this address.
Username/Password
Credentials to use when accessing the Yealink phone.
Yealink format
Select to use new Yealink action URI format introduced in firmware upgrade in fall 2016. Default is false.
Use 3CX Parking Select to use 3CX Parking instead of Yealink action URI Hold methods.

 

Recommended 3CX setup

Below is a description of suggested settings that are required for Totalview functionality to be as expected. The Totalview3CX connector will function without the settings, but the behavior will be undetermined.

Intercom settings

Hands free call control. To be able to use hands free MakeCall and AnswerCall, the device must support Intercom. The 3CXPhone supports Intercom using *9<phonenumber>, but Siemens OpenStage does not. The Intercom prefix can be changed using 3CXAdmin.Settings.Advanced.Paging.

3CXPhone setting

Prevent stealing of focus. When using the 3CXPhone and the Totalview client, the 3CXPhone should be set to not steel focus. Otherwise the focus will switch from the Totalview client to the 3CXPhone when incoming calls arrive at the phone.

To prevent the 3CXPhone to steel focus, set “Prevent answering pop-up from stealing focus on ringing” in 3CXPhone.Preferences and minimize the 3CXPhone to the icon tray.

Enable queue on device. To enable more than one call on the device at the same time, the Forwarding rule for “Phone is busy” must be changed in 3CXAdmin. Change the “Send call to” <same extension> to prevent the call leaving the device when “Phone is busy”.

Forward calls. To be able to use the Totalview External/Internal/All forwarding, the call events must be allowed to arrive at the forwarding device. The 3CX forwarding rules must be set so that call events are not prevented access to the forwarding device.

Totalview is using the forwarding rules All, Internal, External and None. 3CX uses other forwarding rules and the rules do not comply directly with the Totalview rules.

A mapping is created between Totalview forwarding and 3CX forwarding using the following rules:

* Totalview rule All, Internal and External is mapped to the 3CX rule Out of Office 2.

When setting forwarding using Totalview, the extension forwarding in 3CX is set to Out of Office 2.

If Totalview forwarding is All or Internal, the “Forward internal calls” of Out of Office 2 is set to forward the calls to the selected ForwardTo number, otherwise the calls are forward to the voice machine.

If Totalview forwarding is All or External, the “Forward external calls” of Out of Office 2 is set to forward the calls to the selected ForwardTo number, otherwise the calls are forwarded to the voice machine.

* Totalview rule None is mapped to the 3CX rule Available. No changes are made to the settings of Available.

The 3CX connector monitor the extension forwarding, and updates the forwarding shown in Totalview based on the current forwarding of the devices.

Connections at 3CX Queued at listed in the queue member queue in Totalview.

I.e. if device 100 is member of queue 800, then calls queued at 800 will be listed in the Active Queue of device 100 in the Totalview client.

It is not possible do perform any call control on the queued calls.

Monitoring external numbers

External numbers can be monitored when calls are travelling through the 3CX system. The external numbers must be registered as fully qualified in Users for the monitoring to function properly.

Examples for fully qualified numbers are:

Country Number
Denmark +4512345678
Norway +4712345678
Sweden +4612345678
Finland +35812345678
Faroe Islands +298123456

 

Normally used settings:

Country International prefix Inernational code Area trunk code
Denmark 00 45
Norway 00 47
Sweden 00 46 0
Finland 00 358 0
Faroe Islands 00 298

Attachment connector

The Attachment connector provides the attachment structure and data to the Totalview server to present to the user. The structure and data can be customized (see document Totalview  Attachments).

Create the connector using Totalview3.Admin.Connectors. Select Category: System extensions and Subtype: Attachments.

The User filtering defines what users are allowed to use the connector. Only users that apply to the filter setting are allowed to use the connector. If no filter is set, then no user will use the connector.

 

Install the connector using Overview.Install/Update. This will create a new folder and copy the connectors’ program files and XML settings files to the folder.

The XML settings files define the attachment structure and data for the connector. A demo definition and demo data xml file is created when first installing an attachment connector.

Modify these files to customize the attachment definition and data (see document Totalview Attachments).

 

Last edited on October 2nd, 2017