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.
|
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.
If “use default mobile as sender” is checked the users default mobile number is used as “From”.
If the users mobile number is unavailable the “Default sender information” is used.
International Prefix: Default prefix to add to receiver number where international code is missing. LinkMobility requires that receiver numbers are fully qualified, i.e. +<int-code>number.
Using this feature to impersonate other parties will lead to a termination of your LinkMobility account
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.
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.
The Exchange Connectors monitors subscribed 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.
Exchange365 Connector Connection Parameters
An App registration must be made in Azure for the customer’s tenant. See the Exchange security settings guide for more information.
Tenant id
|
The Azure App Registration tenant id |
Client id
|
The Azure App Registration client id |
| Secret |
The Azure App Registration secret |
The App registration must have assigned the following permissions on Graph API:
- Calendar.Read
- Calendar.Write
- User.Read
- Mail.Send
Email Settings
Sender from-address
|
The e-mail account used to emails by Exchange365 connector |
Exchange Online Connector Connection Parameters using OAuth2 authentication (Deprecated)
Using OAuth2 authentication with Exchange Online, reqires an App Registration being created in Azure, with permission to use the EWS Legacy API (full permission).
See the Exchange security settings guide for more information.
Tenant id
|
The App Registration tenant id |
Client id
|
The App Registration client id |
| Secret |
The App Registration Secret |
| Test user |
An user existing in Exchange Online. The user is used to test that the connection with Exchange Online is successful. Format of test user is name@domain.com.
The test user will also be used as the send user when sending mail using the Exchange Online connector |
On-premise Exchange or Exchange Online Connector using basic authentication (Deprecated)
The Exchange connector uses 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 for more information.
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.
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 |
Synchronization settings
| 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
|
| 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 (Deprecated)
|
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.
Totalview 2016 SP2 can be extended by implementing connectors that handle the specific communications with external systems.
This document gives you an in depth description of the calendar connectors and how Totalview 3 interacts with external calendar systems.