Docstoc

Telesnap UMS

Document Sample
Telesnap UMS Powered By Docstoc
					 Telesnap UMS

Technical Guide




           August 31, 2009
         www.telesnap.com
   PARTNERS, CUSTOMERS
                                                                                                    Telesnap UMS – Technical Guide




Contents
1     Introduction .................................................................................................................................... 8
    1.1     About this manual .................................................................................................................. 8
      1.1.1    Technical terms.................................................................................................................. 9
    1.2     Telesnap UMS Basic Functions ........................................................................................... 11
    1.3     System Domains .................................................................................................................. 12
        1.3.1.1     System domain PBX/PSTN .................................................................................... 12
          1.3.1.2           System domain kernel modules.............................................................................. 12
          1.3.1.3           System domain mail-gateway ................................................................................. 12
    1.4     Telesnap UMS Modules....................................................................................................... 13
      1.4.1    Kernel modules ................................................................................................................ 13
        1.4.1.1     CAPI driver.............................................................................................................. 13
          1.4.1.2           XCAPI-Treiber......................................................................................................... 13
          1.4.1.3           Telesnap UMS channels ......................................................................................... 13
          1.4.1.4           Telesnap UMS Line Manager ................................................................................. 14
          1.4.1.5           Telesnap UMS Queue Manager ............................................................................. 14
          1.4.1.6           Telesnap UMS Autotext .......................................................................................... 14
          1.4.1.7           Telesnap UMS Sync ............................................................................................... 14
          1.4.1.8           Telesnap UMS Gateway ......................................................................................... 14
          1.4.1.9           Attachment Converter ............................................................................................. 14
      1.4.2    Administration modules ................................................................................................... 15
        1.4.2.1    Telesnap UMS Setup (Telesnap UMS configuration)............................................. 15
          1.4.2.2           Telesnap UMS Administrator (Telesnap UMS administration) ............................... 15
          1.4.2.3           Telesnap UMS Log Converter and Log Setup........................................................ 15
      1.4.3         User administration.......................................................................................................... 15
2     Planning ........................................................................................................................................ 16
    2.1     System requirements ........................................................................................................... 16
      2.1.1    Fax Rendering ................................................................................................................. 16
      2.1.2    Text-To-Speech (TTS)..................................................................................................... 16
    2.2     Module distribution ............................................................................................................... 17
      2.2.1    All modules on one system.............................................................................................. 17
      2.2.2    Distributed modules ......................................................................................................... 17
        2.2.2.1       Telesnap UMS Line Server..................................................................................... 17
          2.2.2.2           Telesnap UMS Control Server ................................................................................ 17
          2.2.2.3           Telesnap UMS Gateway Server ............................................................................. 17
      2.2.3    Distributed Telesnap UMS systems for high demands ................................................... 18
        2.2.3.1      Scalability ................................................................................................................ 18
          2.2.3.2           Optimal redundancy ................................................................................................ 19
3     Installation/Configuration............................................................................................................ 20
    3.1      Settings for Windows Server 2003....................................................................................... 20
    3.2      New installation .................................................................................................................... 21
      3.2.1     XCAPI installation (VoIP)................................................................................................. 21
      3.2.2     ISDN hardware and drivers ............................................................................................. 21
        3.2.2.1      Eicon DIVA Server Driver........................................................................................ 22

                                                                                                                                                2(170)
                                                                                                 Telesnap UMS – Technical Guide



  3.2.3    Telesnap UMS software installation ................................................................................ 22
    3.2.3.1     Requirements.......................................................................................................... 23
      3.2.3.2           Starting the installation............................................................................................ 23
3.3     Configuration with Telesnap UMS Setup ............................................................................. 28
  3.3.1    License............................................................................................................................. 28
    3.3.1.1     Features & user numbers........................................................................................ 29
      3.3.1.2           Line Server Capacity............................................................................................... 29
      3.3.1.3           Options .................................................................................................................... 29
      3.3.1.4           Code........................................................................................................................ 30
      3.3.1.5           Demo-Version ......................................................................................................... 30
  3.3.2    Hardware ......................................................................................................................... 32
    3.3.2.1    Eicon hardware (CAPI) ........................................................................................... 32
  3.3.3    Phone............................................................................................................................... 33
    3.3.3.1    Connection type ...................................................................................................... 34
      3.3.3.2           Dialing options......................................................................................................... 34
      3.3.3.3           Phone advanced ..................................................................................................... 35
  3.3.4    DID................................................................................................................................... 36
    3.3.4.1     DID Configuration.................................................................................................... 36
      3.3.4.2           Special mode DIDs ................................................................................................. 37
      3.3.4.3           Default Service........................................................................................................ 38
      3.3.4.4           DID Checking .......................................................................................................... 38
  3.3.5    Voice ................................................................................................................................ 40
    3.3.5.1     VoiceMail settings ................................................................................................... 40
      3.3.5.2           Voice mail defaults .................................................................................................. 43
      3.3.5.3           Voice Advanced ...................................................................................................... 43
  3.3.6    Gateway........................................................................................................................... 44
    3.3.6.1    The ODBC user database....................................................................................... 45
      3.3.6.2           TimeOut (accessible over Advanced…) ................................................................. 50
      3.3.6.3           Mail System............................................................................................................. 50
  3.3.7    Fax ................................................................................................................................... 52
    3.3.7.1      Advanced ................................................................................................................ 54
      3.3.7.2           Printing and Archive ................................................................................................ 54
  3.3.8    Logging ............................................................................................................................ 56
    3.3.8.1     Logging level ........................................................................................................... 56
      3.3.8.2           Statistics.................................................................................................................. 57
      3.3.8.3           Logging mode ......................................................................................................... 57
3.4     Advanced Configuration with Telesnap UMS Setup ............................................................ 58
  3.4.1    Notification ....................................................................................................................... 58
    3.4.1.1      SMS-Hardware........................................................................................................ 59
      3.4.1.2           SMS-Providers ........................................................................................................ 59
      3.4.1.3           Cut long messages ................................................................................................. 60
      3.4.1.4           Notification type....................................................................................................... 60
      3.4.1.5           Replace SMS .......................................................................................................... 61
                                                                                                                                        3(170)
                                                                                                     Telesnap UMS – Technical Guide



          3.4.1.6          Outcall Times .......................................................................................................... 61
      3.4.2    SMS- Reception and inbound routing.............................................................................. 62
      3.4.3    Printing............................................................................................................................. 63
        3.4.3.1      Archive .................................................................................................................... 64
      3.4.4    Attachments ..................................................................................................................... 65
        3.4.4.1     Conversion .............................................................................................................. 65
          3.4.4.2          Margins ................................................................................................................... 66
          3.4.4.3          Font ......................................................................................................................... 66
      3.4.5   SNMP............................................................................................................................... 66
    3.5     User administration using WebAdmin.................................................................................. 67
      3.5.1   User specific informations................................................................................................ 67
      3.5.2   Telesnap UMS profile ...................................................................................................... 68
4     System Check............................................................................................................................... 69
    4.1     First System Check .............................................................................................................. 69
        4.1.1.1     Start of the Basic Services...................................................................................... 69
          4.1.1.2          Telesnap UMS Queue Manager ............................................................................. 69
          4.1.1.3          Telesnap UMS Autotext .......................................................................................... 69
          4.1.1.4          Telesnap UMS Line Manager ................................................................................. 70
          4.1.1.5          Internal Sending ...................................................................................................... 70
      4.1.2    Sending externally ........................................................................................................... 71
      4.1.3    Receiving ......................................................................................................................... 71
      4.1.4    Tests without Telesnap UMS software ............................................................................ 72
    4.2     Start of Telesnap UMS Sync................................................................................................ 72
    4.3     Distributed Telesnap UMS servers ...................................................................................... 73
5     Using Telesnap UMS.................................................................................................................... 75
    5.1     Receiving messages ............................................................................................................ 75
      5.1.1    Reception......................................................................................................................... 75
    5.2     Sending Messages............................................................................................................... 77
      5.2.1    Sending Faxes ................................................................................................................. 77
        5.2.1.1     Methods of adressing.............................................................................................. 77
          5.2.1.2          Additional information within the addressing .......................................................... 78
          5.2.1.3          Sending-time and priority ........................................................................................ 79
          5.2.1.4          Ignoring messages with identical MessageID......................................................... 79
          5.2.1.5          Sending Voicemail / Talkmail.................................................................................. 80
      5.2.2    Sending SMS ................................................................................................................... 80
    5.3     Telesnap UMS VoiceAccess................................................................................................ 81
      5.3.1    VoiceAccess functions..................................................................................................... 81
        5.3.1.1     VoiceMails............................................................................................................... 82
          5.3.1.2          FaxMails.................................................................................................................. 82
          5.3.1.3          Emails...................................................................................................................... 82
          5.3.1.4          Dates ....................................................................................................................... 82
          5.3.1.5          Connecting .............................................................................................................. 82
          5.3.1.6          User settings ........................................................................................................... 83
      5.3.2        VoiceAccess Menus ........................................................................................................ 83
      5.3.3        Dialing into Telesnap UMS VoiceAccess ........................................................................ 83
      5.3.4        Greeting ........................................................................................................................... 83

                                                                                                                                                  4(170)
                                                                                                    Telesnap UMS – Technical Guide



      5.3.5         Main menu ....................................................................................................................... 84
      5.3.6         Voicemail menu ............................................................................................................... 85
      5.3.7         Email menu ...................................................................................................................... 86
      5.3.8         Fax menu ......................................................................................................................... 88
      5.3.9         Date menu ....................................................................................................................... 89
      5.3.10        Search-for-date-menu...................................................................................................... 91
      5.3.11        Address book menu......................................................................................................... 92
      5.3.12        Connecting-Menu ............................................................................................................ 95
      5.3.13        User settings menu.......................................................................................................... 95
6     Administration, diagnosis, service............................................................................................. 97
    6.1     Telesnap UMS Administrator ............................................................................................... 97
      6.1.1    Toolbar............................................................................................................................. 98
      6.1.2    Server-Display ................................................................................................................. 98
      6.1.3    Channel status display..................................................................................................... 99
      6.1.4    Queue ............................................................................................................................ 100
      6.1.5    Service check and events.............................................................................................. 100
        6.1.5.1     Service check in distributed Telesnap UMS systems ........................................... 101
      6.1.6    Log files and statistics.................................................................................................... 102
    6.2     Logging............................................................................................................................... 103
        6.2.1.1      The Protocols ........................................................................................................ 103
          6.2.1.2           The applications .................................................................................................... 103
          6.2.1.3           The goal: Database............................................................................................... 104
      6.2.2    LogSetup........................................................................................................................ 104
        6.2.2.1    Concept................................................................................................................. 105
          6.2.2.2           LogSetup – Dialogues........................................................................................... 105
          6.2.2.3           Dialogue-page Global ........................................................................................... 105
          6.2.2.4           Dialogue page Files .............................................................................................. 107
          6.2.2.5           Dialogue Page Database ...................................................................................... 109
      6.2.3    The ThorLog.DLL........................................................................................................... 111
        6.2.3.1     Behaviour .............................................................................................................. 111
      6.2.4    Telesnap UMS Log Test ................................................................................................ 111
        6.2.4.1     Examples: ............................................................................................................. 112
    6.3     Telesnap UMS Info ............................................................................................................ 112
      6.3.1    Functions ....................................................................................................................... 113
        6.3.1.1     Reset ..................................................................................................................... 114
          6.3.1.2           Cancel ................................................................................................................... 114
          6.3.1.3           Create Info ............................................................................................................ 114
Appendix A: FAQ – Frequently asked questions........................................................................... 116
  General 116
  System domain mail-gateway ......................................................................................................... 118
  Client software................................................................................................................................. 118
  VoiceAccess, Text To Speech ........................................................................................................ 118
  Messages ........................................................................................................................................ 119
Appendix B: Tips & Tricks................................................................................................................ 120
Appendix C: Lotus Notes.................................................................................................................. 124
  Telesnap UMS – Anpassungen für Lotus Notes ............................................................................. 124
  Telesnap UMS – Konfiguration für Lotus Notes.............................................................................. 125
Appendix D: Dictionaries.................................................................................................................. 128
  Scansoft-TTS................................................................................................................................... 128
                                                                                                                                                5(170)
                                                                                                      Telesnap UMS – Technical Guide



      Provided dictionaries .................................................................................................................... 128
        HEADER-Section...................................................................................................................... 128
         Data-Section ............................................................................................................................. 129
   Eloquent-TTS .................................................................................................................................. 129
     Delivered Dictionaries .................................................................................................................. 129
       Root-dictionary (xxxROOT.DIC) ............................................................................................... 129
         Exceptions-dictionary (xxxMAIN.DIC) ...................................................................................... 130
         Abbreviation-Dictionary (xxx.ABBR.DIC).................................................................................. 130
Appendix E: Attachment Converter................................................................................................. 131
  Operating mode............................................................................................................................... 131
    Light version ................................................................................................................................. 131
    Business - and Graphics - version ............................................................................................... 132
  Configuration ................................................................................................................................... 132
  Supported file formats ..................................................................................................................... 132
  Tips and tricks Attachment Converter ............................................................................................. 139
    MS Office...................................................................................................................................... 139
      Office password protection and macros ................................................................................... 139
         Macros in normal.dot ................................................................................................................ 139
         Macro viruses ........................................................................................................................... 139
         Fonts......................................................................................................................................... 140
      Test............................................................................................................................................... 140
      Adobe PDF................................................................................................................................... 140
      Rich Text (RTF)............................................................................................................................ 141
Appendix F: Front page editor ......................................................................................................... 142
  Outline 142
  Front page description file ............................................................................................................... 142
      General attributes ..................................................................................................................... 142
         Text attributes ........................................................................................................................... 143
         The following pages.................................................................................................................. 143
   Front page selection........................................................................................................................ 144
       Global front page ...................................................................................................................... 144
         Individual front pages per user ................................................................................................. 144
   Variables for Telesnap UMS Gateway ............................................................................................ 145
       Sender data .............................................................................................................................. 145
         Recipient data........................................................................................................................... 145
         Additional data .......................................................................................................................... 145
   Variables for Exchange Connector.................................................................................................. 146
       Sender data .............................................................................................................................. 146
         Recipient data........................................................................................................................... 146
         Additional data .......................................................................................................................... 146
   Front page editor ............................................................................................................................. 147
       Company logo........................................................................................................................... 149
Appendix G: Recall system DOCbase............................................................................................. 150
  Outline 150
  Requirements .................................................................................................................................. 150
  Configuration ................................................................................................................................... 150
  Test    151
                                                                                                                                                   6(170)
                                                                                                     Telesnap UMS – Technical Guide



     Fax................................................................................................................................................ 151
   Preparing documents ...................................................................................................................... 151
     File formats................................................................................................................................... 151
Appendix H: Event-Logging ............................................................................................................. 152
  Telesnap UMS Linemanager........................................................................................................... 152
   Hint ............................................................................................................................................... 152
   Warning ........................................................................................................................................ 152
   Error.............................................................................................................................................. 152
  Telesnap UMS Queuemanager....................................................................................................... 154
   Hint ............................................................................................................................................... 154
   Warning: ....................................................................................................................................... 154
   Error:............................................................................................................................................. 154
  Telesnap UMS AutoText ................................................................................................................. 156
   Hint ............................................................................................................................................... 156
   Warning ........................................................................................................................................ 156
   Error.............................................................................................................................................. 156
  ThorLog.DLL.................................................................................................................................... 157
   Hint ............................................................................................................................................... 157
   Warning ........................................................................................................................................ 157
   Error.............................................................................................................................................. 158
  Telesnap UMS Gateway ................................................................................................................. 160
   Hint ............................................................................................................................................... 160
   Warning ........................................................................................................................................ 160
   Error.............................................................................................................................................. 161
  Telesnap UMS Monitor.................................................................................................................... 162
   Hint ............................................................................................................................................... 162
   Error.............................................................................................................................................. 162
  Telesnap UMS Wdog.dll.................................................................................................................. 164
   Error.............................................................................................................................................. 164
  Telesnap UMS Printing ................................................................................................................... 164
   Hint ............................................................................................................................................... 164
   Error.............................................................................................................................................. 164
  Telesnap UMS Sync........................................................................................................................ 165
   Hint ............................................................................................................................................... 165
   Error.............................................................................................................................................. 165
  UMS-Connector............................................................................................................................... 166
   Hint ............................................................................................................................................... 166
   Warning ........................................................................................................................................ 166
   Error.............................................................................................................................................. 166
Appendix I: Database schema ......................................................................................................... 168




Disclaimer
Duplication and circulation of this document, extracts thereof or any information contained in this document require the prior
authorization of Telesnap GmbH. All technical data, information and product features described or mentioned in this document
reflect the status quo on the date of document release. Telesnap GmbH reserves the right to apply modifications and
improvements to products or any of their documentation due to technical changes and improvements at any time without notice.




                                                                                                                                                  7(170)
                                                                      Telesnap UMS – Technical Guide




1 Introduction
This chapter contains information on:
                the documentation
                the topic of Telesnap UMS
                the system domains
                Telesnap UMS modules and their functions.




1.1 About this manual

This documentation will provide basic information on the topics of:


            •   Introduction
            •   Planning
            •   Installation
            •   Configuration
            •   Operation
            •   Service


The primary goal during the development of Telesnap UMS was to realize a seamless integration of
provided services (Fax, Voicemail, SMS and Inbox Access) into an existing mail system as easy as
possible. To reach this level of comfort at the best, many parameters can be adjusted.3




       Please read this manual to get acquainted with Telesnap UMS and to optimise benefits for the
individual user.


This manual focuses on one mail system (IMAP/SMTP connection) in the domain Mail gateway; it
contains references to other mail systems in the appendix. If you search for further details on other
mail systems, please refer to the appendix.




                                                                                                  8(170)
                                                                     Telesnap UMS – Technical Guide




1.1.1 Technical terms

In this section recurring technical terms and product designations are described:


UM (Unified Messaging)
UM Services link modern forms of communication (E-Mail, SMS) with classical communication
services (phone, fax, answering machine)


ODBC
The Open Database Connectivity (ODBC) is an universal interface to relational Databases. It contains
the essential functions for the connections to databases, the SQL-Queries and the processing of the
results.


ADSI
The Active Directory Service Interface (ADSI) is a Microsoft COM-component, which provides a
standardised programming interface (using the LDAP protocol). The implementation on a concrete
directory service is realized by an ADSI-provider.


Directory Service
A directory service provides the administration of network resources like workstations and printers.
The resources are addressed by names and arranged hierarchically. Besides, the service may contain
information about the network users. Therefore in high-end directory services digital certificates are
stored as attributes of the user objects.


LDAP
Lightweight Directory Access Protocol
LDAP is a protocol-standard for directory services. It describes a standard for Internet- and Intranet-
clients, -applications and –server for the retrieval of directory service access. If the achievement of
LDAP is enforced in future, the user gets a standard for a uniform, interoperable access to directory
services in heterogeneous system environments. In this way LDAP may help to simplify
communication. Intranets can be expanded easier to the internet. In the meantime all main IT-
manufacturers provide LDAP-directory services.


TTS-Engine
TTS-Engine (Text To Speech Engine): An application for the conversion of text to speech (e.g. in
order to readout emails).


Prompts
While handling Telesnap UMS on the phone you are able to choose between different speakers in
different languages. The used sound files are called prompts.




                                                                                                   9(170)
                                                                     Telesnap UMS – Technical Guide



Gateway
Architecture to connect two network systems which work with different protocols.
A Gateway is a protocol-converter. Gateways are applied to enable communication between the
higher layers of the ISO-7-layer model, although they use different protocols. Therefore the protocols
have to be translated. In addition, a gateway adopts the Network Cards’ physical coupling. A gateway
may be called a front-end-computer.


Eicon DIVA
ISDN-Hardware (PCI-Cards) to connect ISDN-devices with the PC-Server


Realspeak
Realspeak is a speech-synthesis-software to convert text-information to spoken (synthetic) language.


POP
POP3 means Post Office Protocol Version 3 and provides a protocol for the reception of emails over
the Internet. The disadvantage of the used SMTP-protocol for internet-dispatch is that it emails can be
delivered only in case the receiver is online. This deficiency is repaired by POP3: emails are stored in
some kind of mailboxes (secured by password and user name) until the user cleans up his box by
downloading the emails. (->IMAP)


IMAP
IMAP is a relatively new product (TCP-Port 143). Unlike the POP-protocol, which provides the
directory-hierarchy directly on the computer in front of you (email-client), IMAP is a server-based
protocol. With IMAP you are able to create directory-structures on the server itself. The advantage is
visible: Wherever you log on to the Internet, you have full access to your emails and the included
directory structure. If your email-client-application supports IMAP, this protocol should be used instead
of POP.




                                                                                                 10(170)
                                                                    Telesnap UMS – Technical Guide




1.2 Telesnap UMS Basic Functions

Telesnap UMS is a Unified Messaging Server, which integrates the services
            •   Fax sending/receiving
            •   Fax on demand
            •   Voice mail sending/receiving
            •   VoiceAccess (Access to UMS contents by phone)
            •   SMS (Short Message Service)


into an existing mail system. The services are available to every user automatically in their own Mail-
Client. The services can be used individually as well as in combinations for a modular based service.




                              Server              Services


                                                   Fax

                                                  Voice                                User
       PSTN

                                                  SMS

                                                  VoiceAccess                          User




                                                                                       User
                             mailserver             email




Telesnap UMS’s architecture allows you to use all services mentioned above directly after installation
at each mail-client without additional software-requirements. The programs are merely installed on
one or several central servers.
This solution saves elaborate installation procedures as well as service- and training work at the user’s
desktop.




                                                                                                 11(170)
                                                                    Telesnap UMS – Technical Guide




1.3 System Domains
As a possibility of structuring a whole Telesnap UMS-System, system domains have been defined to
illustrate functions, installations, updates, etc. in a more transparent way.




                          System domain
                          Kernel module



    System domain                                     System domain
    PBX/PSTN                                          Mailgateway




         PSTN
                                                 Mailserver



                          User       User




1.3.1.1 System domain PBX/PSTN
Here you find the CAPI channels provided by the system (also virtual CAPI channels via XCAPI or
others), the connection to the PBX (PBX, e.g. Cisco CallManager) or to the PSTN.



1.3.1.2 System domain kernel modules
The following services belong to the kernel domain:
The primary Telesnap UMS services Telesnap UMS Line Manager, Telesnap UMS Queue Manager,
Telesnap UMS Autotext; the optional Telesnap UMS services Telesnap UMS Sync, Telesnap UMS
Printing and Archive, and in wider senses the administration tools Telesnap UMS Setup and Telesnap
UMS Administrator.



1.3.1.3 System domain mail-gateway
The third and last domain is reserved for the mail-gateway. The mail-gateway is either the UMS
Connector for Exchange or the Telesnap UMS Gateway service for all other mail systems.
The related modules Attachment Converter, UDBedit, Outlook forms, etc. also belong to this domain.




                                                                                             12(170)
                                                                        Telesnap UMS – Technical Guide




1.4 Telesnap UMS Modules



                 Telesnap UMS            (Telesnap UMS Printing and




                                                                               Telesnap UMS Kernel
                 Gateway                          Archive)

                 Telesnap UMS
                 Autotext




                                                                                     Services
                                      Attachment Converter, MS Office



                 Telesnap UMS Queue
                 Manager

                 Telesnap UMS Line                           (Telesnap UMS
                 Manager                                          Sync)

                                                  Channels


                                                 CAPI
              WINDOWS Operating System
                                                                                               PSTN
                                                 Devicedriver


             CPU, RAM, HD                        ISDN-HW / XCAPI




1.4.1 Kernel modules
The Telesnap UMS-server-services are the core components of the system. These services control
the installed communication hardware and the ports to the connected modules and gateways.

1.4.1.1 CAPI driver
Program type: Windows service and DLLs
This service is available for all CAPI-based Telesnap UMSs. Using Eicon-ISDN-cards CAPI provides
the interface between the channel processes and the ISDN-cards.

1.4.1.2 XCAPI-Treiber
Program type: Wondows service and DLLs
XCAPI builds the Software API between the channel processes and the PBXs (Cisco CallManager).

1.4.1.3 Telesnap UMS channels
Program type: Background process, executable file: chnl.exe
The Telesnap UMS Line Manager starts a channel-process for each communication channel. The
channel process communicates with the communication hardware like ISDN cards and modems. It
sends and receives fax-, voicemail-, talkmail- and sms-messages.


                                                                                                      13(170)
                                                                     Telesnap UMS – Technical Guide



1.4.1.4 Telesnap UMS Line Manager
Program type: Windows service, executable file: thorxmit.exe
The Telesnap UMS Line Manager controls the communication to all connected communication
channels over one channel process for each channel. The channel process also controls the
VoiceAccess operation to the applied user- and mail databases.

1.4.1.5 Telesnap UMS Queue Manager
Program type: Windows service, executable file: thorq.exe
The Telesnap UMS Queue Manager is responsible for the distribution of sending-jobs, i.e., fax,
voicemail, talkmail, message-waiting and sms-mailing are administrated by a central queue and
distributed to the connected Telesnap UMS server(s). Transmission notifications are delivered to the
sender processes by status reports.

1.4.1.6 Telesnap UMS Autotext
Program type: Windows service, executable file: thoratx.exe
Telesnap UMS Autotext is a file-based sending-interface for the dispatch of Telesnap UMS messages.
This interface is currently used by all Telesnap UMS-gateways and can also be accessed in many
ways by foreign applications. The special Autotext documentation is contained in the technical
manual.

1.4.1.7 Telesnap UMS Sync
Program type: Windows service, executable file: thorsync.exe
This optional service can be installed - if desired – to make Telesnap UMS reacting differently to
incoming calls: Telesnap UMS can - depending on the phone extension received - answer as a fax
machine, fax point or as a usual answering machine. It is also possible to refuse a call from an
unknown number.

1.4.1.8 Telesnap UMS Gateway
Program type: Windows service, executable file: thorgate.exe
For Lotus Notes and Internet Mail. The UMS-Connector is provided for the Exchange connection.
This service is the direct interface between Telesnap UMS and the used mail system. It transports
messages to and from the mail server. Incoming messages will be forwarded to the appropriate users
and outgoing messages will be exported from the server and transmitted to the Telesnap UMS module
for dispatch. Depending on the used mail-server. Telesnap UMS Gateway communicates with
standard protocols such as POP3/IMAP4/SMTP, MAPI or Notes-API.

1.4.1.9 Attachment Converter
Program type: background process, executable file: attconv.exe
Apart from sending pure text mails, the Attachment Converter allows to send files as an attachment of
an email. The attachment is converted into a fax document by the Telesnap UMS server and sent
afterwards. The light version of the Attachment Converter is installed during the standard installation of
Telesnap UMS. It allows the dispatch of TIFF graphics and of MS Office-files (Word, Excel and
PowerPoint) if MS Office has been installed on the Windows system. Additional formats can be sent
by filter modules, which can be installed optionally. Equipped with these additional filters, Telesnap
UMS is able to process more than 240 different document types. You find a list of all supported
formats in the appendix Attachment Converter.




                                                                                                  14(170)
                                                                   Telesnap UMS – Technical Guide




1.4.2 Administration modules
The main part of the administration during maintenance of the system is the user administration done
via the web administration of the snapware system. There are the Telesnap UMS relevant user data
configured, Telesnap UMS itself doesn’t have an own user data storage, Telesnap UMS acts as a
Gateway.

1.4.2.1 Telesnap UMS Setup (Telesnap UMS configuration)
Program type: Application, executable file: thorsetup.exe
With the help of this program, central basic settings concerning communication hardware, PBX
connection, gateway port and fax/voice settings are performed during the setup process. The program
Telesnap UMS Setup is automatically called up during the installation and can also be used for
subsequent, global changes of the Telesnap UMS system.

1.4.2.2 Telesnap UMS Administrator (Telesnap UMS administration)
Program type: Application, executable file: thoradmin.exe
The program Telesnap UMS Administrator is used to monitor the Telesnap UMS services, the
communication channels, the queue and the journal files. Lines and services can be activated and
deactivated here and jobs can be deleted from queues. Simultaneously, the activities of all lines and
services can be monitored online.

1.4.2.3 Telesnap UMS Log Converter and Log Setup
Program type: Application and service, executable file: logsetup.exe and thorlogc.exe
With the program log setup you can create user-defined log-data. These data can be alternatively
exported in formats of data or database. The graphical user-interface alleviates the selection of the
desired parameters and allows the creation of user-defined log-formats for a detailed evaluation. The
corresponding service THORLOGC then executes the appropriate conversations automatically.



1.4.3 User administration

By default the administration of Telesnap UMS user data is done via the WebAdmin of the
corresponding Snapware system and the connection to the data via ODBC.
Details for the user administration using the WebAdmin can be found in the appendix.




                                                                                               15(170)
                                                                    Telesnap UMS – Technical Guide




2 Planning
The Telesnap UMS system consists of several modules and services. As the system is
scalable arbitrarily a detailed plan of the installation of each module is necessary. The way
in which the installation is executed should depend on the number of lines, the desired services and
the possible system efficiency.


2.1 System requirements
While the Telesnap UMS-server-services do not excite a high computer load when sending and
receiving messages (because of the active ISDN-hardware), there are two Telesnap UMS functions
which cause a significant charge of the CPU: Fax Rendering and Text-To-Speech (TTS).

2.1.1 Fax Rendering
The conversion of email texts and attachments into the fax format is called rendering, i.e. a conversion
of text and binary data into fax-graphic-data. This conversion is rather extensive especially for Office
documents. The more fax documents are sent with attachments, the higher are the requirements to
the CPU performance. If other processes already charge the CPU heavily, the conversion will take
more time and the fax sending efficiency decreases.

2.1.2 Text-To-Speech (TTS)
The second „CPU consuming“ function is the synthesis of language while reading emails (text-to-
speech) in the Telesnap UMS VoiceAccess operating mode. The synthesis from text to speech is
arithmetically very extensive and cannot be executed in the same way as e.g. the fax communication
directly on the active ISDN hardware. The CPU calculates the speech-synthesis directly. If several
Telesnap UMS channels are operating simultaneously for TTS and the CPU, the performance
decreases. This can lead to a delay during the speech playback, worse quality or complete failure.
Due to these high performance requirements several recommendations concerning the distribution of
Telesnap UMS modules to one or more computer systems can be found below.




                                                                                                16(170)
                                                                    Telesnap UMS – Technical Guide




2.2 Module distribution
2.2.1 All modules on one system
Generally it’s possible to run all modules of the Telesnap UMS system on one PC. In this case, the
Telesnap UMS kernel modules as well as the gateway process and the Attachment Converter
(possibly with Office) are active simultaneously. This kind of configuration should be chosen only if
there are up to 8 channels available (4 S0). If there are more than 8 lines, the modules should be
distributed.


This does not apply for all Telesnap UMSs using a large number of lines. Systems with few or no
rendering and TTS are imaginable here. Examples for systems with 30 channels without module
swapping-out are:
1. exclusively fax-on- demand server
2. Telesnap UMS using mainly the receiving function (fax/voice).




2.2.2 Distributed modules
In this kind of configuration the Telesnap UMS server services are distributed to several servers. All
Telesnap UMS functions (including extensive rendering and TTS) with 30 or more lines parallel can be
implemented in this configuration. If you consider the resulting importance, the following server types
can be differentiated:
            •   Telesnap UMS Line Server
            •   Telesnap UMS Control Server
            •   Telesnap UMS Gateway Server

2.2.2.1 Telesnap UMS Line Server
A Telesnap UMS system, which has installed just the Telesnap UMS Line Manager service and the
ISDN hardware, is called a Telesnap UMS Line Server. A Telesnap UMS Line Server can contain up
to 30 channels. If more channels are required, several Telesnap UMS Line Servers can operate
parallel. According to this, a single Telesnap UMS Line Server is used for the calculation of the
computationally intensive function TTS.

2.2.2.2 Telesnap UMS Control Server
A parent server, the Telesnap UMS Control Server is responsible for the Telesnap UMS Queue
Manager, Telesnap UMS Autotext and Telesnap UMS Gateway services. Even the optional services
Telesnap UMS Sync and Telesnap UMS Printing and Archive can run here.

2.2.2.3 Telesnap UMS Gateway Server
The Telesnap UMS Gateway service has already been introduced in the control server description
above. A reason for the installation of an additional gateway server could be a second Telesnap UMS
Gateway service for the connection of an additional mail system.




                                                                                                 17(170)
                                                                   Telesnap UMS – Technical Guide



2.2.3 Distributed Telesnap UMS systems for high demands

2.2.3.1 Scalability


                                                           Line Server 1
                Control Server
                                                           Telesnap UMS Line Manager

                Telesnap UMS Queue Manager
                Telesnap UMS Autotext
                Telesnap UMS Sync                          Line Server 2
                Telesnap UMS Printing+Archive
                                                           Telesnap UMS Line Manager


                                                                      …


                                                           Line Server n

                                                           Telesnap UMS Line Manager




Telesnap UMS’s architecture allows the execution of each Telesnap UMS service on one or multiple
distributed systems. To implement a failsafe system in large environments, which can additionally be
enhanced for more capacity easily, the installation should be planned as follows:
All central data are filed on a server from which all Telesnap UMS servers „serve“ themselves. This
main server takes the role of the Telesnap UMS Control Servers (see above). The other computers,
which contain the communication hardware, are called Telesnap UMS Line Servers. Generally, in
distributed systems the existence of one Telesnap UMS Control Server (optionally secured as a
cluster) and several Telesnap UMS Line Servers should be provided.
The scalability can easily be achieved by adding more Telesnap UMS Line Servers.
If in this configuration a Telesnap UMS Line Server fails, the system keeps on operating automatically
with the remaining resources. Sending jobs will be passed on to the remaining Telesnap UMS Line
Servers and is processed automatically.
All global data, like personal announcements, cache databases and protocol-data, are stored centrally
on the hard disk of the Telesnap UMS Control Server and do not have to be replicated.




                                                                                               18(170)
                                                                     Telesnap UMS – Technical Guide




2.2.3.2 Optimal redundancy

Concerning distributed systems, you have to pay attention to the following features:


    •   All Telesnap UMS ISDN terminals should be reachable by the same number, i.e. belong to a
        shared line group.
    •   In the sending and receiving mode, half of the channels of all Telesnap UMS servers should
        be synchronized to reception and the other half on dispatch and reception. This setting can
        even be chosen in a similar way (i.e. always some channels to reception only so that the
        system is always accessible and external users can always access Telesnap UMS even if the
        send mode is highly utilized).
    •   The Telesnap UMS Control Server should be kept as redundant as possible (mirrored hard
        disk, backup, cluster etc.). After the installation all central data, like cache databases of valid
        calling numbers, the personal announcements and possibly the DOCbase data, will be located
        on this computer.
    •   The Telesnap UMS Control Server will be introduced to the Telesnap UMS Line Servers so
        that they can work with the central data kept there. Only the Telesnap UMS Line Manager
        service runs on these computers. All other services can be started on the control server.
    •   If a Telesnap UMS Line Server fails, the others overtake all incoming calls. All sending jobs
        from the failed server will automatically be transferred from the Telesnap UMS Control Server
        to the active Telesnap UMS Line Servers.
    •   To increase the capacity, it is only necessary to add another Telesnap UMS Line Server to the
        system. Thereby, it is important that the network as well as the server is „fast“ enough to serve
        all network calls of the Telesnap UMS Line Servers. Therefore, a separate network segment
        for distributed systems is recommended for the Telesnap UMS system.




                                                                                                  19(170)
                                                                      Telesnap UMS – Technical Guide




3 Installation/Configuration
After these extensive preparations the practical part can begin now. The division into the three
system domains ISDN, kernel modules and mailgateway will be maintained within these parts.




3.1 Settings for Windows Server 2003
Using OS Windows Server 2003 you have to accomplish the following instructions to avoid problems
concerning the printer driver’s installation.
To allow the installation of the FaxMail printer driver you have to enable the option “kernel printer
installation” which is configured in the group policy object editor.


        Please select WINDOWS Start          Execute and enter ‘gpedit.msc’.
        Now you enter the Group Policy Object Editor.




The path ‘Computer Configuration / Administrative Templates / Printers‘ allows you to access the
printer’s rules. As the picture shows you have to deactivate the rule „Disallow installation of printers
using kernel-mode drivers“ to ensure that the FaxMail printer driver can be installed (please ensure
that the policy was applied to the system correctly, for example when running in a windows domain).

On some systems also the following rule has to be applied:




                                                                                                   20(170)
                                                                     Telesnap UMS – Technical Guide




As the picture shows you have to deactivate the rule „Devices: Prevent users from installing printer
drivers“ to ensure that the FaxMail printer driver can be installed correctly.


You can start the printer driver’s installation manually from the directory “%WINDIR%\digi” using the
file prtinst.exe after the installation was completed.




3.2 New installation
3.2.1 XCAPI installation (VoIP)
A condition for the operation of Telesnap UMS at a Cisco call manager is the availability of virtual
CAPI channels, how they are offered e.g. from the software XCAPI by TE-Systems.
These channels make the connection between the PABX and Telesnap UMS. Alternatively XCAPI
over T.38 or over the soft fax version of XCAPI (dependent on the licencing) can communicate and
thus via a H.323 gateway of the call manager.
You please take Details for installation and configuration of these virtual CAPI channels from the
appropriate manuals.

3.2.2 ISDN hardware and drivers
On legacy PBX systems TELESNAP uses exclusively Eicon’s PCI-models.
Consequently, nothing needs to be set while installing these cards (jumper). Even the software
installation is particularly simple.


                                                                                                 21(170)
                                                                      Telesnap UMS – Technical Guide



3.2.2.1 Eicon DIVA Server Driver
The current driver that fit to all three Eicon-DIVA-cards are located on the Telesnap UMS CD under:
\driver\eicon\. They can be treated as an update for the Diva standard driver, which is installed -
if Diva hardware is detected - by Windows. Further instructions can be found under
\driver\eicon\V300_win2000\Readme.txt.
We refer to the Eicon documentation provided when inserting and installing the driver software:
Telesnap UMS CD\doc\eicon\DivaW2K.pdf. All necessary steps for the setup of the hardware are
described there. Only information on installation specific to Telesnap UMS is given below, to which
you should pay attention.
        •   Telesnap UMS requires CAPI drivers only. Other software parts such as modem ports,
            RAS drivers are not necessary and should not be installed, so that no data access from
            external sources over Telesnap UMS channels is possible. A separate modem channel is
            usually installed for remote control. In this way, it is easier to overview when a foreign
            access is free or blocked. (modem cable is separated).
        •   Please ensure that the correct ISDN protocol is adjusted after installation of the card
            drivers and CAPI software. In Germany, this is generally the EDSS1 (Euro ISDN protocol).
            The German national 1TR6 is sometimes used for PBX exchange simulations.
        •   Please note that Telesnap UMS generally operates as a system link, since only in this
            way sufficient by-elections are available. The type of link is adjusted with ISDN interface
            type. Select POINT to POINT for system link.
        After all adjustments have been finished, please carry out the line test (under the Eicon ISDN
        Tools in start-menu):




        This error appears if you do not follow the request for restart after configuration modification.




        The configuration is now complete. The installation of the Telesnap UMS software can be
        continued.


3.2.3 Telesnap UMS software installation
The Telesnap UMS server software establishes the actual Telesnap UMS installation of the kernel
modules. The setup application is created with Install Shield for Windows and requires Windows
Installer service. If Windows Installer is not located on the computer or the version is outdated, then
the installation of Windows Installer automatically takes place in the first instance. Afterwards, the
computer must usually be rebooted.


First, a decision must be made as to what Telesnap UMS server type is required according to the
distribution of Telesnap UMS functions:
              •    Telesnap UMS line server
              •    Telesnap UMS control server
              •    Telesnap UMS gateway server


                                                                                                   22(170)
                                                                        Telesnap UMS – Technical Guide



Explanations concerning the individual server types are given in the section installation. Combinations
are possible. If there is only a small number of channels used (up to 8) all modules can be installed on
one computer.



3.2.3.1 Requirements
Information given in the chapter planning must be well-known - especially in the case of a so-called
distributed installation.
Operating system
Windows 2000 server, Advanced Server or Enterprise Server (with current Service Pack)
Windows 2003 server (with current Service Pack)
Memory (RAM)
Data for this you take please from the current product specification.
Hard disk storage
Data for this you take please from the current product specification.




3.2.3.2 Starting the installation

With the installation of the Telesnap UMS server software in distributed environments please pay
attention to the fact that every machine gets – per installation - the modules which are necessary for
the respective function. This improves transparency.



        ATTENTION: You must have local administrator rights in order to be able to carry out the
installation correctly.


                 Insert Telesnap UMS CD if this has not already been done (example drive E:).

                 Enter: \install\setup.exe

                 A greeting appears      Next
                                                                                                23(170)
                                                 Telesnap UMS – Technical Guide




License agreement, read and, if necessary, accept     Next

 Select a target path for installation. Please use a base folder such as, e.g.
D:\PMUMS, since other various sub-folders are created on several levels below this
folder. A "deeper" base folder leads to problems during operation mode since the
resulting file names used by Telesnap UMS become too long. Default is C:\PMUMS,
but we recommend using another (data) partition if available     Next

Select installation type: Custom is usually selected. This gives you a better
overview of the components to be installed.




                                                                            24(170)
                                                   Telesnap UMS – Technical Guide



Select the server type(s) which is/are planned for this machine:


Exampe: Telesnap UMS Universal Server




This frequently used server-type installs all provided modules. The attachment
converter is installed in the light-version.
If you choose complete at the beginning of Telesnap UMS’s installation process, this
server-type is used.



Example: Telesnap UMS Line Server




The point Telesnap UMS line server is selected for the pure line server. This may be
sufficient.
However, if users should be able to listen to email attachments on the phone with
VoiceAccess, the attachment converter Business or Graphics must be activated –
provided that you have purchased a license for this. The light converter cannot
manage this function.


Example: Telesnap UMS Gateway Server




The Gateway Server creates the connection between Telesnap UMS and an email
system like MS Exchange, Lotus Notes or Internet-Mail.




                                                                                 25(170)
                                                   Telesnap UMS – Technical Guide



Example: Telesnap UMS Control Server




This example shows a pure control server. One of three attachment converters is
always part of a control server.
ATTENTION: Please choose only one of the three versions from the attachment
converter!
If Light and Business are selected, a mixture of both is installed which does not work
(in this case, the functions would be reduced to the Light converter).




The copying process operates for several minutes.



The installation program then automatically starts Telesnap UMS configuration.
Firstly, Telesnap UMS Setup asks for the system account for Telesnap UMS services.
The details can be modified at any time later in the service manager.

It is possible that your current account does not appear as a suggestion, but as a local
one, which would generally only be suitable for services without external access.

Enter the account in an unambiguous form DomainName\UserName!




                                                                                26(170)
                                                         Telesnap UMS – Technical Guide




       ATTENTION: The account used must own the right "registering as a service ".
Otherwise Telesnap UMS services can start in console-mode only. The right to the account
can be given in the windows user manager. However, the following method is quicker: Set the
installation to one of the services mentioned in the dialogue above, to the automatic start
mode. This will give the relevant account access rights if necessary.




                                                                                    27(170)
                                                                  Telesnap UMS – Technical Guide




3.3 Configuration with Telesnap UMS Setup

All configurations you choose during the first start of Telesnap UMS Setup can be changed later.


3.3.1 License
You are not able to activate Telesnap UMS without a valid license code. The license code is
dependent on the name of your Telesnap UMS-Control-Server-Machine (or universal server) and your
desired functionalities.
Different from former versions of Telesnap UMS, now just one license code for the whole Telesnap
UMS-System is necessary.
Please ask your Telesnap UMS-dealer for your license code.




                                                                                              28(170)
                                                                     Telesnap UMS – Technical Guide



3.3.1.1 Features & user numbers

Telesnap UMS is offered in four variants of configuration: Fax, Voicemail, Unified Messaging and
Mobile Office. Please select the services you purchased.


                1 Fax               Fax-sending, Fax-receiving, Fax-Polling und Fax-on
                                    demand-database
                2 Voicemail         Voicemail-receiving and access by phone.
                3 Unified           Fax and Voicemail-service plus Voice Access to
                  Messaging         email-messages
                4 Mobile Office     Unified Messaging plus Voice Access to calendar and
                                    address book (not available with IMAP/SMTP mode)




Further on you can choose for each variant the number of possible users. Please enter in each field
the number of the purchased service-licenses.
Normally you receive a license code for a certain number of users who will be allowed to use the same
service. This number marks the limit of users who are registered in the database and authorized to
use Telesnap UMS.
In big companies, the license can be extended to a corporate license. In this case no limit exists for
the number of users. For this option you have to choose the number “unlimited”.



      If you change the number of users later a new license code will be necessary.



3.3.1.2 Line Server Capacity

You have to specify the number of lines and their characteristics used in the whole Telesnap UMS
system (all line-servers). If you have two line-servers installed with 60 channels each and 30 channels
are used for the service Unified Messaging, you enter 90 in the first field and 30 in the second.



3.3.1.3         Options

Voice Controlled Sessions
Telesnap UMS is available in a speech-controlled version. Therefore a separate CD is required, which
is distributed by your Telesnap UMS-dealer. It’s possible to install and configure the additional
components of the speech-control later. Please notice that for the operation of the speech-controlled
version of Telesnap UMS Eicon DIVA-Server-Cards up from version 2.0 are required.
GSM Modem Support
Telesnap UMS supports the GSM-Modems Siemens M20 and TC35 for SMS sending, SMS-
Reception and for optimized SMS-transmission. If you installed one of these modems and you want to
activate the GSM support, you have to activate this option. Therefore a license is required, too.

                                                                                                 29(170)
                                                                     Telesnap UMS – Technical Guide



Attachment Converter Version
There are three alternatives of the attachment converter: Light, Business and Graphics.
Apart from the Light-version a license is required.



3.3.1.4 Code

Please enter the license-code that depends on the name of the control server. If you change the
configuration belatedly by adding or deleting services, a new license code will be required.
The files “expires” shows the date of expiration of your license code. If the checkbox is activated, the
expiration date integrated in the code field is shown in the field to the left of the checkbox.
If „never“ is shown, the license has an unlimited validity.



3.3.1.5 Demo-Version

For the purpose of demonstrations and tests, Telesnap UMS can be used without a license code.
Therefore you have to select the option “demo” beside the field of code at the bottom of the license
page. The Demo use of Telesnap UMS is subject to the following restrictions:


            •    The maximum capacity in the user-database for the UMS system is 5, otherwise the
                 UMS system cannot be started
            •    Mobile office functions are available for each of the 5 users; furthermore individual
                 settings can be chosen for every user; e.g. you can choose less functionalities like
                 “voicemail”, “fax” or “unified messaging” exclusively.
            •    The line-server is permitted to possess –independent from the functionality- TWO
                 channels maximum, it’s not possible to add more channels, even if you use Telesnap
                 UMS in a big environment
            •    For demo use, no SMS- and ASR-functionality is provided. GSM-support is
                 deactivated.
            •    The attachment-converter is available in the light version only.


Enter DEMO in the field of the license code and confirm by activating the small demo-box.


If you choose the settings according to the illustration you can use Telesnap UMS for the purpose of
demonstrations and tests without a license code.




                                                                                                  30(170)
                                                               Telesnap UMS – Technical Guide




If you enter different values, a license code will be necessary.




                                                                                      31(170)
                                                                  Telesnap UMS – Technical Guide



3.3.2 Hardware




3.3.2.1          Eicon hardware (CAPI)

This dialog is for configuration of a line server only.
When using virtual CAPI channels, e.g. XCAPI, for the service fax you select please as type of
channel CAPI. Add the number of channels which corresponds to the software, per virtual CAPI
channel a Telesnap UMS channel.
If using Eicon hardware please select CAPI as the channel type. Add the number of channels
according to the hardware. These are:
                 •   DIVA Server BRI: 2 Channels per card
                 •   DIVA Server 4 BRI: 8 Channels per Card
                 •   DIVA Server PRI: 30 Channels per card

A line server can be equipped with up to 4 DIVA-server-cards with maximal 60 channels. PRI and BRI-
cards cannot be mixed inside the same line-server.


                                                                                             32(170)
                                                                     Telesnap UMS – Technical Guide



Enter hardware configuration to determine the link port S0 or S2M.




Choose
    •    “basic rate (S0)” for card-types DIVA Server BRI and 4BRI or up to 2 virtual XCAPI channels
    •    “primary rate (S2M) / XCAPI more” for card type DIVA Server PRI or more than 2 virtual
         XCAPI channels

Please select maximum as many CAPI channels as actually can be supported by the hardware.
Please note that CAPI channels must be licensed. The service Telesnap UMS Line Manager will end if
more than the licensed number of CAPI channels is configured.



3.3.3 Phone




                                                                                              33(170)
                                                                      Telesnap UMS – Technical Guide



3.3.3.1 Connection type

Telesnap UMS can be operated from both a telephone system (PBX) as well as from an exchange
port (PSTN). The ISDN link, to which Telesnap UMS is connected with the telephone network, must
be entered here.

3.3.3.2 Dialing options

Outside line dial
If Telesnap UMS is connected to a telephone system (PBX), a line must be obtainable. This is
generally registered with a “0”.

        If the field is gray – due to a PSTN connection – then it must be empty. If necessary, switch
briefly to PBX connection and delete the field.

If at least x digits
Number of dialing digits, that must be dialed by a sender so that Telesnap UMS can automatically
obtain an outside line. A digit should be set which is greater than the internal length of the extension.
Example: internal extensions are 3 digits enter 4. This results in Telesnap UMS not obtaining an
outside line if 3 digits are dialed.

Long distance dials / international dial
A chosen digit must be entered here for selecting a national or international connection. Telesnap
UMS requires this data in order to check the permission of a user to dial a destination. Generally 0 is
entered. It’s not necessary to enter two 0 because Telesnap UMS uses the 0 of the Outside line dial
and the 0 of the Long distance dial.

Country code
The country code is entered here. For Germany this is generally set to 49. Telesnap UMS needs this
specification to check the individual permission of Telesnap UMS-users for sending transactions.

Area code
Enter the area code (omitting initial 0) for local area calls. Telesnap UMS needs this specification to
check the individual permission of Telesnap UMS-users for sending transactions.




                                                                                                   34(170)
                                                                   Telesnap UMS – Technical Guide



3.3.3.3 Phone advanced




Message Waiting

        ON dial code            Dial sequence for activating message waiting on an extension
        OFF dial code           Dial sequence for deactivating message waiting on an extension

        Dial type               MWAIT dialing mode, generally code followed by extension
        Hold time               Amount of time in seconds where the line is held.



Generation of calling party number

When Telesnap UMS is connected to a telephone system it is sometimes useful to place the so-called
calling party number or sender’s address dynamically during the build-up of an intended connection in
the d-channel. This function is particularly useful to assist with billing charges in a PBX.
If this function is activated, Telesnap UMS simulates a connection with the private user-DID during the
build-up by placing his/her DID in the d-channel as calling party Number. The telephone system
records this in exactly the same way as if it were coming from an extension with this DID. There are
four possible variations in this operating mode:


              None                     switched off, no placing of calling party number
              Main calling number      always the same fixed calling party number
              only
              User DID only            only the sender’s personal DID
              Main number + user       Main calling number with attached personal
              DID
                                       DID of the sender




                                                                                               35(170)
                                                                      Telesnap UMS – Technical Guide



3.3.4 DID




3.3.4.1 DID Configuration

DID = Direct Inward Dialing       Sometimes also known as
DDI = Direct Dialing Inward


This refers to the way in which the main number plus direct-inward dialing can be used for point-to-
point system links. The entire administrative process for the connecting procedure takes place in the
d-channel. Nowadays, almost every system link where a telephone system is connected with the
PSTN works along these lines.

Maximum Number of DID digits
Virtual direct inward dialing controls all functions for incoming calls. The max. number of direct-inward
dialing digits, which can be expected by Telesnap UMS, are set here. Once these digits are there
Telesnap UMS immediately accepts the call. After a call has been accepted, Telesnap UMS does not
note any further digits (as follow-on dial).

Allow variable DIDs
If it is necessary that direct-inward dialing digits with different lengths must be implemented within the
Telesnap UMS system this field can be activated. In this case, Telesnap UMS also accepts a call if

                                                                                                   36(170)
                                                                      Telesnap UMS – Technical Guide



fewer direct-inward dialling digits have been dialed. Telesnap UMS waits (Timeout) for further digits
and then accepts the call in any case. This option must sometimes be selected if the fax-recall service
(DOCbase) is to be activated and the number of direct-inward dialing digits needed for the recall
differs from the number of the user direct-inward dialing.

Ignore DID digits
This allows a fixed number of digits for the received selection to be ignored. They are cut off left/in
front, i.e. they are not noted the further processing.
With the connection to a PBX it is also possible that a code digit is provided which is possibly
unwanted. This can also be cut off using this option.


        Example: Your ISDN exchange has the number (prefix code) 234-0. The code digit 9 has
        been set for the Telesnap UMS line in PBX. The user direct inward dialing should be 4-digits
        (also for user administration). The user with the direct-inward dialing 4711 is to receive a
        message. Telesnap UMS directly receives 94711 for selection (if the code digit is sent – this
        can mainly be dialed freely in the PBX).


        -> maximum NUMBER OF DID-digits = 5, Ignore DID digit = 1 and user box digit = 4
        -> Telesnap UMS cuts off the 9 and merely processes 4711



User box digits
This field normally contains the difference between maximum number and Ignore.



3.3.4.2 Special mode DIDs

Telesnap UMS can activate additional services by means of direct-inward-dialing. Telesnap UMS
automatically switches to the appropriate operating mode depending on the start of the resulting
direct-inward dialing.
Please consider the call number household when connected to a telephone system as well as with the
exchange link.
If Telesnap UMS receives a DID where the initial numbers are not entered Telesnap UMS treats this
call as receiving a "normal" fax /voice.

Central VoiceAccess

There are two ways of achieving VoiceAccess.
    •   By dialing the personal Telesnap UMS DID, then entering the VoiceAccess-PIN during the
        greeting.
    •   By central voice access. For calls on this number Telesnap UMS firstly asks the caller for
        his/her personal DID followed by the PIN. Then he is in the VoiceAccess menu.


The first method can be used without entering anything in the field Central VoiceAccess.




                                                                                                   37(170)
                                                                    Telesnap UMS – Technical Guide



Document Access (DOCbase)

This service provides the supply of different message types like:
    •   fax documents (fax on demand)
    •   voice messages (voice on demand)
    •   texts (text on demand).


The messages can be recalled by means of DID. Up to 10.000 messages can be administered.
The documents to be recalled must be stored as files with certain names in the folder
PMUMS\docbase. The name must correspond to the following convention:


                       Message type     file name
                       Fax              DOC_nnnn.TIF
                       Voice            DOC_nnnn.WAV
                       Text             DOC_nnnn.TXT


The number of available call boxes systems from the number of supplied DID-digits for this service. If,
e.g. the DID scope 0000 - 9999 is available for Telesnap UMS and the code digit 9 has been set for
DOCbase, then max. 1000 documents from 9000 to 9999 can be recalled and the files must be named
as DOC_0900 to DOC_0999 (the DOCbase identifier 9 is not used).
A description of DOCbase can be found in the appendix.



3.3.4.3 Default Service

Here you define which service is the standard service for all users in case you already didn’t allocate a
personal or individual service in the user-administration. In case of an incoming call Telesnap UMS
proves each time if a user possesses a personal service-setting. If not, the “default-service” is
activated automatically.
It is recommended to choose that service for which the majority of licenses have been purchased. For
the users who should receive a more-advanced service, the appropriate additional services have to be
entered in their user-configurations manually.



3.3.4.4 DID Checking

On some occasions it is useful for Telesnap UMS to only accept DID calls, which are registered in the
user- database. This requires DID Checking to be activated.
A second reason for this can be that Telesnap UMS is to reply to DIDs in different ways: For DIDs,
which e.g. only has the fax function, Telesnap UMS is to reply as fax i.e. no greeting.
Telesnap UMS Sync can determine the creation of a local cache database for user-data by specifying
the synchronization interval and/or synchronization time.
The service Telesnap UMS Sync must also be started.


                                                                                                 38(170)
                                                                       Telesnap UMS – Technical Guide



Telesnap UMS Sync                         procures information from the user database
Telesnap UMS LINE manager                 uses this if the tick is entered.




Please do not start the service yet. As a rule, do not use DID Checking when operating for the first
time. Activate it later once the basic functions operate.




Accept Unknown Extension
If the received DID is unknown (not listed in the user database), a connection is nevertheless made
and the message is recorded. Afterwards, the defined default receiver has to forward this message
manually.
This setting is useful if importance is attached to the different reaction between accepting a call and
accepting wrong DIDs at the same time.



Skip password
This setting enables the users, who call up their own Telesnap UMS DID, to access directly the
VoiceAccess menu - without having to enter their PIN.
The caller ID of the called extension is used as identification. The number must be known by the user-
database.



Restricted access
This option determines that the user can access his messages exclusively from the accompanying
terminals provided that these terminals transmit their caller ID so that Telesnap UMS can identify
them.
Once this is activated no dial-in from other telephones is possible! As a result, this option is rarely
chosen and only used in high security environments.




                                                                                                   39(170)
                                                                  Telesnap UMS – Technical Guide



3.3.5 Voice

The default values for the Telesnap UMS VoiceAccess are configured here. Furthermore, all settings
can be adjusted individually for each user by using the Telesnap UMS user configuration. The
following values represent default values, which are used if a user does not have personal settings.




3.3.5.1         VoiceMail settings

Menu type
In the current version of Telesnap UMS only one menu-version is provided which contains all
Telesnap UMS-functions dynamically and activates, depending on the purchased license and/ or user-
depending service-settings, the Telesnap UMS-functions.

Pin code length
Each user who uses the Telesnap UMS VoiceAccess requires a secret code for auTelesnap UMSized
access. The number of digits for the secret code is determined here. The length of the secret code is
the same for all users. The individual user PINs are determined by the Telesnap UMS user-
administration.




                                                                                              40(170)
                                                                    Telesnap UMS – Technical Guide



# of greeting messages
This setting determines the number of a user’s personal voice-announcements. If this field is
deactivated (0), the standard announcement is used. As personal announcements require memory on
the Telesnap UMS-server, it is recommended to deactivate this option in case of great user numbers
or low local disk space.

Voice Messages max
A voice message can generally recorded for up to 30 seconds. The max. length of a recording can be
altered here. Please note that voice messages produce a large quantity of data, which, after receipt, is
then forwarded as email to the connected mail system. As a general rule for uncompressed voice: 30
seconds correspond to 250 KB, 1 minute approx. 500 KB, two minutes even 1 MB. However, if you
select a better codec with compressing (see below), this amount of data can be reduced significantly.

Voice comments max
The users can answer and forward messages by telephone. A spoken comment can be attached to
the message. This value determines how many seconds this kind of comment can be before Telesnap
UMS ends the recording. Please note that the memory consumptions mentioned above also occur
here.

VoiceMail format
This determines how the wave format of incoming voice mail data is forwarded to the user. Telesnap
UMS generally uses CCITT A-law format, which has become the standard format for voice mail
applications. Other formats can be used to save storage space or to support certain audio players.
Please find below a list of the codecs supported by Telesnap UMS:


               Name                Data rate    Remark
               CCITT A-Law         7kB/s        High data rate, Standard format
               PCM                 7kB/s        same data rate as A-law, however
                                                more widely used
               GSM 6.10            1kB/s        low data rate, optimized for cellular
                                                phone networks, player usually
                                                available only under Windows
               True speech™        1kB/s        low data rate, player usually
                                                available only under Windows
               MP3                 2kB/s        Low data rate, possibly codec has to
                                                be purchased separately




                                                                                                41(170)
                                                                      Telesnap UMS – Technical Guide



Default Call Authorization
This determines which phone numbers are valid for outbound dialing for a standard user using
VoiceAccess. This setting is valid in the features “call connect”, “call back” and establishes calls within
the user’s address book. Furthermore it’s possible to define restrictions. Therefore the following
options are available:


            •   Deactivated (all outbound calling with VoiceAccess is completely disabled)
            •   Internal (company-internal numbers only can be dialed)
            •   Regional (region with area code available only)
            •   National (national connections)
            •   International (international connections, any call target is allowed)


If you change these settings, all of the three functionalities mentioned above are affected. For example
with the setting “national” (figure) you are able to be connected to numbers inside your country
respectively you are able to call these numbers back and you can select/call any national contact
using the address-book-menu.
Restrictions for single users can be adjusted individually in the user configuration.



      If you choose “deactivated”, the option ”9” – the connection to any phone number in the
VoiceAccess main menu - will not be available. Consequently, with this setting the function can be
deactivated. Also the corresponding commands concerning call-back and connecting in the address-
book will not be available at all.


The values provided here should not be equated with the entry "Sendrights" in the rider "fax". There
the possible calling targets are specified for documents that can be sent. In this setting, the possible
dialing numbers are set while using Voiceaccess.



Empty Call Capture
The ECC (Empty Call Capture) – Function activates a calls indication in the Telesnap UMS-mailbox,
even if the caller didn’t leave a message. If the ECC is activated, the connector resp. the gateway
creates an email for each incoming call in the inbox of the Telesnap UMS-user with the subject “Call
from …”. Even the VoiceAccess informs the user about each call. In the VoiceAccess a call is
classified as an “empty” Voicemail.
In this way a user will be informed of any missed call and he can also initiate a call-back directly from
the VoiceAccess.
In Telesnap UMSSETUP there are three different settings provided for the ECC:
            •   OFF – Standard Set, no ECC activated. Empty calls will not be recorded
            •   If calling number available – only in case of a visible caller number, these calls will
                be indicated in the inbox. This is the recommended setting.
            •   ALL - All calls are signaled, even unknown calls without a calling-party number. In this
                case an entry with “call from unknown” is created. That means, that only the existence
                of a call is signaled but not the information about the caller’s number.



                                                                                                   42(170)
                                                                   Telesnap UMS – Technical Guide



3.3.5.2 Voice mail defaults

Menu language
The standard menu speaker is determined here. The menu speaker is the voice, which guides the
user through the menus in Telesnap UMS VoiceAccess.

Primary email language
The primary mail speaker is determined here. This speaker is used for reading out emails.

Secondary email language
The secondary mail speaker is determined here. This speaker is used if the user changes language
while reading out emails.

Automatically Play first Message
This setting determines whether the auto-play function is generally activated or deactivated. The Auto
play function means that Telesnap UMS automatically plays the first voice message when a user
enters VoiceAcces. In this case, the user does not have to select the appropriate menu manually.

Tell time and date
This setting determines whether the receipt date and time of a message is generally read out in
VoiceAccess.



3.3.5.3 Voice Advanced
In the Voice Advanced dialogue you can configure all language-settings and their engines.
Telesnap UMS supports the following Text-To-Speech-Engines
            •   Scansoft Realspeak (provided standard TTS-Engine)




     Please notice that the appropriate TTS-Engine provides a license of the respective
manufacturer.




                                                                                               43(170)
                                                                    Telesnap UMS – Technical Guide



3.3.6 Gateway
Here you activate the desired mail system.




The Telesnap UMS-mail-gateway for Internet-mail is suitable for all POP3- and IMAP-compatible mail-
server. The Telesnap UMS-server has to be able to access the mail-server per TCP/ IP.




       NOTE: In case of the connection per POP3 / IMAP only the mail objects are accessible which
have already not been retrieved, e.g. these which are still located on the mail-server. If a POP3-client
retrieves his messages, the messages are deleted server-sided and stored on the client’s workstation
only. These messages cannot be accessed by VoiceAccess.




                                                                                                44(170)
                                                                Telesnap UMS – Technical Guide



Databases
As Mail system typically you select IMAP/SMTP. For the user data binding you select ODBC. Over this
interface the user data with the data from the Snapware user system and the associated SQL server
are adjusted.
If you are using MS Exchange or Lotus Notes for accessing mail databases or user databases please
refer to the corresponding chapters in the appendix.



3.3.6.1 The ODBC user database
For the access to the selected user database, Telesnap UMS requires an ODBC connection. This
connection has to be created manually in MS Windows first.
When installing on an existing Snapware Server system the required ODBC connection “TsConfig”
should be available without manual creation.




ODBC Connection
       Name of the installed ODBC-connection. This connection has to be installed and tested as
       system-DSN before.

ODBC table
       Name of the used database.

User name
(Optional) Database-Login-Name

Password
(Optional) Database-Login-Passwort




                                                                                           45(170)
                                                                   Telesnap UMS – Technical Guide



Creation of an ODBC-Database
Please select Control-Panel->Data-sources (ODBC). You’ll find different ODBC-drivers here.




In case of an empty list, you have to install the necessary ODBC-drivers. You’ll find the ODBC drivers
(Microsoft Data Access Components) in the folder \tools\mdac on the Telesnap UMS-CD. Drivers for
different databases are provided for free by other manufacturers. After the installation process has
been finished, Telesnap UMS shows the dialogue mentioned above.
As Telesnap UMS-modules run as services, you have to create a System-DSN. A user-DSN is
suitable only if Telesnap UMS-services run as console. Services do not have any access to User-
DSNs opposite to users, who user do have access to system-DSNs. The generation of an ODBC-link
depends on the used database-system and cannot be described in general. Important is, that the
DSN’s name, the table’s name and the login-information is kept in mind by the database system. This
data is required by Telesnap UMS.
If the used ODBC-Database is case sensitive the key fields (DID, FAXADDR and MAILADDR) have to
be entered either in capital or lower case letters.


Testing Database-Connection
The tool UDBcheck.exe which is located in the folder \Telesnap UMS\bin can be used for testing the
chosen Telesnap UMS-ODBC-Connection. The application shows possible options and returns - by
request - all data-records. In this way you can prove if all configurations are correct.




                                                                                               46(170)
                                                                    Telesnap UMS – Technical Guide



Supported Database-fields
Connected to an Internet-mail-server, Telesnap UMS uses the LDAP- or ODBC-Database-Interface to
access the user-database.
Telesnap UMS expects certain database-fields. Default values are field identifiers, which may be
adapted. The standard field identifiers are resumed below.




Required Data-fields for VoiceAccess
Basically, Telesnap UMS Voice Access requires the following data fields. These have to be present in
the used ODBC-Database – either with the given standard-name or with a different name. (q. v.
adaption of field assignment) If fields with signification are still not present, the database has to be
expanded.


                DID                     (Index) User’s Telesnap UMS-Extension
                MailBox                 User’s mail account at the POP3/IMAP-Mailserver
                MailPassword            Password of the mail account at the POP3/IMAP-Server
                PIN                     PIN for the Voice Access. The PIN hat to set to a standard
                                        value first in order to permit a user to log on to the Voice
                                        Access. Now the user can set a new PIN per phone.
                                        Elementary, Telesnap UMS requires access to be able to
                                        write to this field.
                PinErrorCounter         Number of the incorrect inputs of PINs. The number is
                                        increased by Telesnap UMS while a incorrect entry is
                                        happening.
                                        Telesnap UMS requires access to write to this filed. After a
                                        valid PIN has been entered, the value is reset to zero. If an
                                        incorrect PIN is entered more than five times, the account will
                                        be locked. i.e. no more tries to enter the valid PIN are
                                        possible. To unlock the VoiceAccess the administrator must
                                        set this filed to 0 manually.
                Fullname                The user’s display-name. It is announced not only while the
                                        greeting but also entered in the cover sheet while sending
                                        faxes.



Optional Data-fields for VoiceAccess
                MailHost                (Option) If the user’s mail objects are not located on the
                                        standard-mail server set in Telesnap UMS setup but on
                                        another host, the name of this new host is entered here. In
                                        this case Telesnap UMS searches new messages on the set
                                        server instead of the standard server.




                                                                                                 47(170)
                                                                      Telesnap UMS – Technical Guide



Required Data-fields for Fax/Voice

These fields are required for the usage of FAX and VoiceMail-services.


                MailAddr                 (Index) The user’s complete SMTP-address. It’s used to
                                         switch the received Fax- and Voice-Massages and to prove
                                         auTelesnap UMSization while sending.

                SendRights               Sending rights – this fields must contain a value to permit the
                                         dispatch per Telesnap UMS Gateway:


                                         3 = international, i.e. no sending-restriction
                                         2 = distant zone
                                         1 = local zone
                                         0 = no auTelesnap UMSisation to send


The fileds DID and MailAddr have to be marked as Index, because Telesnap UMS selects data
records concerning these fileds.
The field DID is ought to be realized for the data-type string and not for int(eger), because of the
existing danger loosing main zeros in extensions.




Optional Data fields for Fax/Voice

The following fields can be additionally used working with the services Fax and VoiceMail.


                Services                 (Optional) Requires DID Checking. Activated Telesnap UMS-
                                         services for the user (bitmask)


                                         0 = no service– no call acceptance
                                         Bit 0 = 1 = Fax
                                         Bit 1 = 2 = Voice
                                         Bit 2 = 4 = eMail-Reading andVoiceAccess


                                         To enable all services for a user, set the value to 7.


                Costs                    The sender’s cost center. It’s printed to the Telesnap UMS
                                         Gateway’s journal.


                DialPrefix               Personal prefix for a special method of data billing using
                                         some PBX.

                                                                                                  48(170)
                                                                 Telesnap UMS – Technical Guide




               Cover                  User specified Fax-Datasheet. This Datasheet has to be
                                      already available.


               Company                Company name (Cover sheet)
               Department             Department (Cover sheet)
               City                   City (Cover sheet)
               Street                 Street (Cover sheet)
               Faxnum                 Fax number (Cover sheet)
               Phone                  Telephone number (Cover sheet)




Adaptation of the field allocation
If the fields in the ODBC-database differ from the Telesnap UMS-standard-names, the table of
allocation can be adapted here. You access the table by the following path
PMUMS Setup Gateway Configure. Make sure that the same type is maintained.




On the left you have the Telesnap UMS-standard-names and on the right the appropriate ODBC-
database’s field names.




                                                                                               49(170)
                                                                   Telesnap UMS – Technical Guide



3.3.6.2 TimeOut (accessible over Advanced…)
Surveillance of jobs in consideration of sending-time:




Up to this version of Telesnap UMS, the effective sending time has not been considered for
monitoring. This feature has been improved and now you can be sure that the timeout is kept.



3.3.6.3 Mail System




Incoming Host DNS
DNS-Name or IP-Address of the POP3/IMAP-Mailserver, where all incoming messages are stored.
Telesnap UMS accesses this host per VoiceAccess and uses the user’s login stored in the database
(see below). All documents which have to be sent are polled by Telesnap UMS here.

SMTP Host DNS
The SMTP-server’s DNS or IP-address has to be specified here without DNS-Lookup. The address
may be identical to the one of the IMAP-server as far as the host supports the SMTP-protocol. If you
enter a valid host, the function Answer to emails is activated automatically. Answering to and
forwarding emails will not be possible without this entry.

SMTP Mode
Incoming and forwarded messages as well as answers to messages are sent over the SMTP-Protocol.
A fixed Relay-host or a dynamic NDS-lookup can be set as SMTP-server at MX-Name-Resolution.


                                                                                               50(170)
                                                                    Telesnap UMS – Technical Guide



DNS Host
In case of an activated MX-Name-Resolution you have to enter the name or the IP-Address of a DNS
(Domain Name Server). By this DNS, Telesnap UMS acquires the appropriate SMTP-server for each
dispatch.

Gateway Address
(Optional) Here you enter the mailbox’ address, which Telesnap UMS Gateway uses for the dispatch
of messages. If you enter a valid SMTP-address, the function Forward is activated within the
VoiceAccess-Interface. If no entry is present, forwarding will not be possible.

Default Receiver
If incoming-switching cannot identify an adequate user, the message will be sent to this alternative
receiver. He can forward the messages manually.




Testing the POP3/IMAP-Connection
The specified mail-server has to be accessible anytime by the Telesnap UMS system. This condition
is necessary to make the user’s access per VoiceMail possible. Before Telesnap UMS is started, you
should prove this connection e.g. per Telnet. Therefore use port 110 for POP3 and 143 for IMAP4.




The mail-host shows his operating state in a short message.




                                                                                                51(170)
                                                                   Telesnap UMS – Technical Guide



3.3.7 Fax




Fax ID
The fax identifier of Telesnap UMS that is transmitted to the receiving station during sending and
receiving faxes must be entered here. Please enter the main identifier only without DID digits. While
sending and receiving faxes, the DID digits of the individual users are added automatically to the main
identifier by Telesnap UMS both during sending and receiving.

Company Stamp
The fax-send stamp can be configured here. The text applies globally for all outbound faxes. It can be
up to 20 characters in length. Longer texts are cut off. Generally, the company’s name is entered here.

Stamp mode
The stamp line contains the fax identifier, the stamp text as well as date and time. The settings under
Advanced... contain further possibilities. The stamp mode determines whether and how this stamp line
is to be used with fax sending. Please note that the advanced settings are only valid when using
brooktrout fax boards. There are four possibilities:




                                                                                               52(170)
                                                                         Telesnap UMS – Technical Guide



        Disabled:
        No stamp line is sent (standard).

        Inserted:
        The stamp line is inserted prior to the actual contents of the fax document. In this operating
        mode the length of the fax document is increased for the length of the stamp line, i.e. the fax
        document is approx. 8-10 mm longer than a standard A4 sheet.

        Replaced:
        The stamp line replaces the area on the fax document. For this operating mode the original
        size of the fax document is maintained although the original information is overwritten.

        Overlapped:
        The stamp line is transparently overlapped with the fax document. The original size of the fax
        document is also maintained in this case. However, if there is information on the part of the fax
        document where the stamp line is placed, the stamp line is illegible.



Stamp Placement
There are four different possibilities for placing the stamp line:

              Header on all pages              At the top of all pages
                                               (standard)
              Footer on all pages              At the bottom of all pages
              Header on first page             At the top, only on first page
              Footer on first page             At the bottom, only on first
                                               page




Default send right
The standard sending auTelesnap UMSization for all users is set here. If no user-specific setting is
available all users have this auTelesnap UMSization. Possible settings include local area, national
area and the international domain. Please note that the dialing digits for this function must be correctly
set in the register Phone.

Delivery report
If required, Telesnap UMS can attach the sent fax document to the receipt delivered to the sender via
email. This means that the user has both the confirmation and the sent document in one email. Please
note, however, that this function increases the size of the transported email data by the size of a fax
transmission per receipt.




                                                                                                  53(170)
                                                                   Telesnap UMS – Technical Guide



3.3.7.1 Advanced




Maximum Pages Allowed
Max. number of fax pages which a user may send in one transmission. The maximum value is 350.
However, due to reasons of costs and utility 50 should be the maximum value of sent pages. The
value -1 means that no boundaries have been set.

Retry on Busy
The number of repetitions and intermediate breaks can be set here in case the target terminal is busy.
Default values are: 3 times every 2 minutes. If this number is exceeded the status error will be
achieved. Afterwards, the retry on error (see below) happens for this dispatch.

Retry on error
The number of repetitions and the intermediate breaks can be set here if an error occurred during
transmission. Default values are: 3 times every 2 minutes.



3.3.7.2         Printing and Archive




                                                                                              54(170)
                                                                        Telesnap UMS – Technical Guide



Printing
For incoming and outgoing fax documents, central printout can be globally activated here.
The numbers corresponds to those which are allocated to the installed printers in the register Printing
(see below).



              ATTENTION: In this case all received or sent fax documents of all users are printed!
        This is rarely intended.


If a user-specific print is required this can be set in the user configuration.



Archive

All sent and received files can be archived in a separate folder by activating the Archive function. The
appropriate folders are set in the register Printing (see below).
Please note that a global archiving of all documents requires a substantial amount of storage space on
the archiving medium.




                                                                                                 55(170)
                                                                     Telesnap UMS – Technical Guide




3.3.8 Logging

Telesnap UMS can log all activities centrally. This setting determines in which way a Telesnap UMS
module controls whichever log file. All log files are located in the folder \Telesnap UMS\log and have
the file extension .log. There are always so-called CSV files, i.e. text files whose values are separated
by commas. The field designators are located in the first line. The files are not conceived for reading
with a word processor but for importing in its own databases or spreadsheet calculations. The
Telesnap UMS administrator also provides a prepared view of the journals.




3.3.8.1         Logging level

As the default setting logs all-important events, we recommend to apply the provided settings without
executing any changes.


Telesnap UMS merely produces logs. Deleting files now and again is the task of the administrator or
the associated archiving systems. Please note that detailed logs require a lot of disk storage.
Debugchnl, in particular, should not run on the highest level for months.

                                                                                                 56(170)
                                                                     Telesnap UMS – Technical Guide



3.3.8.2         Statistics
In addition to the loggings central statistics is produced regularly for the system capacity. Generally,
statistics are produced every day. However, this time period can be altered at will. The statistics can
also be found in the folder \Telesnap UMS\log and has the name statall.log.



3.3.8.3         Logging mode

The journals send.log, receive.log, vaccess.log and Telesnap UMSprn.log can either be
created in sequence or divided into certain time periods. When using the sequential mode these files
are continually extended by new entries, which can result soon in unmanageable, large journals.


Alternatively, a new file can be started automatically after a chosen time period. The files are
designated depending upon interval:


Day:
A new version of the file is produced following the first log entry after 00:00. The version from the
previous day then has the file name filename_date.log. e.g. send_19990813.LOG refers to the send-
log from August 13th, 1999.


Week:
A new version of the file is produced every Monday following the first log entry. The version of the
previous week then has the file name filename_weekcalenderweek_year.log.
E.g.send_week33_1999.log.


Month:
A new version of the file is produced each month following the first log entry. The version of the
previous month then has the file name filename_monthmonthlynumber_year.log, e.g.
send_month10_1999.log.




                                                                                                   57(170)
                                                                      Telesnap UMS – Technical Guide




3.4 Advanced Configuration with Telesnap UMS Setup

The application Telesnap UMS Setup is started during the installation in the "Wizard" mode. In this
control mode the most important settings, which are necessary for the operation of the system are
called one after another automatically.
However, the application Telesnap UMSSETUP can be also called later manually. This function is
used to change existing settings or to do additional settings. In the following paragraph, further setting
options are described.
In distributed Telesnap UMS environments, Telesnap UMS Setup must be called several times (for
each server). On the one hand for the hardware configuration of the individual Telesnap UMS Line
servers and on the other hand for the configuration of the Telesnap UMS control server. Please install
the individual Telesnap UMS Line Server first.
Telesnap UMS Setup offers different registers and option, depending on the locally installed Telesnap
UMS services. Then, more or less possibilities for settings are activated. Only if a single Telesnap
UMS server is used, one central setup is possible.



3.4.1 Notification

Telesnap UMS offers different types of notification. When voice or fax messages have been received,
Telesnap UMS can automatically inform the user either by SMS or with a phone call (user outcall).
Settings concerning the SMS provider and outcall times can be made within this register.




                                                                                                  58(170)
                                                                  Telesnap UMS – Technical Guide



3.4.1.1         SMS-Hardware

In order to be able to use the SMS functions, at least one SMS channel must have been installed on
the Telesnap UMS system.
In the current version of Telesnap UMS, the support of sending SMS messages over CAPI channels
(Eicon hardware) and over GSM modems of the types Siemens M20 and Siemens TC35 are
supported.
First, an SMS-compatible channel must be configured correctly in the register "hardware" (see above).
If you have already configured CAPI channels, these channels will be also configured automatically for
the SMS-service by the program Telesnap UMS SETUP.
In order to be able use a M20 or a TC35-GSM-Modem, you have to install the modem on a Telesnap
UMS Line Server correctly. For the installation of a GSM modem please read modem’s installation
manual. For the installation of a GSM channel for a M20 or a TC35-Modem, please switch to the
register “hardware” and add manually a channel of the type M20/TC35 (see above).




      ATTENTION: If using of a GSM-Modem for SMS-Notification, please pay attention to the
following important hints:


            a. ALL SMS to ALL providers are sent over the same GSM-modem. There is currently
               no possibility to use operator based SMS sending on multiple GSM modems with
               different SIM cards for different network providers.
            b. For all other existing channels the service SMS has to be deleted. If you don’t perform
               this action, all SMS-messages will be sent uncontrolled over different channels. The
               current version doesn’t provide any routing of the SMS-messages to individual
               channels.



3.4.1.2         SMS-Providers

As a rule, Telesnap UMS is delivered with the known SMS settings for sending over CAPI channels for
German GSM providers. If an additional provider should be added, click Add. The following data must
be entered in the mask below:




                                                                                              59(170)
                                                                     Telesnap UMS – Technical Guide



                •    Name of provider: This must be an unambiguous name, which has not yet been
                     used for identification
                •    Protocol TAP or UCP or GSM (only for GSM-modem)
                •    Pattern number: This serves for the identification of the provider according to the
                     target number of the SMS-dispatch job. The patterns must be separated from
                     each by using a colon ":"!
                •    SMSC number: Number of the service center, the dialing is actually placed there
                     and a data connection is built up to the entered number.




      ATTENTION: For the use of a GSM-Modem for SMS please pay attention to the following
settings:


    1. The protocol “GSM” must be activated for ALL SMS-providers.

    2. Settings under “SMSC number” are not relevant, as these settings have to be configured
       directly on the SIM-card of the GSM-modem.




3.4.1.3         Cut long messages

If a SMS message is longer than 160 characters (which is possible), Telesnap UMS divides the
message into several parts of SMS automatically. If this option is not activated, a SMS is terminated
automatically after 160 characters. Per sending order, only one SMS can be sent.


3.4.1.4         Notification type

In the current version, Telesnap UMS supports two different kinds of notification. The "old" variant, in
which one SMS is created per new fax- and Voicemail- message. This SMS contains only the
information of the new message.



Old Variant:




                                                                                                  60(170)
                                                                   Telesnap UMS – Technical Guide



In the "new" variant, an "Overview" SMS is created, which contains the present "status" of the user’s
inbox in addition to the information of the new message. Additionally, the number of all new and old
fax -, voice and email-messages is indicated. You may find the different layouts of the SMS messages
in the chapter "What's new".



Overview-SMS:




3.4.1.5         Replace SMS

If Telesnap UMS is equipped with a GSM modem (see above), the option "Replace SMS" can
additionally be selected. Thereby, the previous SMS message in the memory of the mobile phone is
removed automatically and replaced with the the new message. This option useful since with a
frequent notification by Telesnap UMS the SMS-memory of a mobile phone will not be exceeded, but
occupies just one memory slot.



3.4.1.6         Outcall Times

Profiles can be determined by the outcall settings, which determine the time periods when Telesnap
UMS should perform the notification outcalls. These calls are not suitable at any time of day. (Only a
few users are happy to receive a call at 3 o'clock in the morning in which Telesnap UMS explains that
a fax has arrived.)




                                                                                               61(170)
                                                                     Telesnap UMS – Technical Guide




In this window, profiles are configured which contain the information on what day and time the outcalls
are permitted. Afterwards, one of the profiles can be assigned to each user. In the example above
outcalls are carried out from Monday to Friday between 9:00 pm and 5 am, no outcall is done on
Saturdays and Sundays.



3.4.2 SMS- Reception and inbound routing

After the installation and configuration of a GSM-modem (see above) the reception of SMS-messages
is possible.


If an SMS is sent to the system, i.e. a GSM-modem receives an SMS, it will be treated like a usually
received message. Since a GSM modem does not support any DID numbers, and consequently SMS-
messages arrive naturally to the system without direct addressees, this message will be delivered as a
text-email to the administrator’s inbox configured in the gateway settings(see above).


With additional information inside the SMS, it is possible to forward the SMS directly to a user’s inbox
or a group of users.




     ATTENTION: If the received SMS contains a user’s DID number (a group or a public folder) at
the beginning the text, the gateway will analyze this information and forward the SMS to the
corresponding inbox.


With this method, it is possible to deliver SMS-messages with just one GSM-modem with a single SIM
card to any number of users.




                                                                                                 62(170)
                                                                      Telesnap UMS – Technical Guide



3.4.3 Printing

The service Telesnap UMS Printing and Archive can either operate on a Telesnap UMS server or
another windows 2000 station. As desired, it takes over the printout and/or archiving of received and
sent fax documents.


This option must firstly be activated for every user within the user configuration. to also print out fax
documents of individual users on printers. Please refer to the section Gateway in Use for activating the
printer function.


All printers, which are known on the used windows 2000 server can be used for Telesnap UMS
Printing and Archive. Local printers and installed network printers can both be used. The printers
where Telesnap UMS Printing and Archive should be used are given a so-called queue number for
simplified administration with Telesnap UMS.
First, install all addressed printers by using the operating system’s administration tools. Instructions for
this can be found in e.g. Windows online help.




The installed printers must then be assigned to the Telesnap UMS printer channels (queues). This
takes place in Telesnap UMS Setup as shown in the dialog above.


                                                                                                    63(170)
                                                                       Telesnap UMS – Technical Guide



All available printers are listed at the top. The internal queue number given by Telesnap UMS or a -
are shown in the column Queue.
By double-clicking on an entry, a dialog appears for the entry of a queue number.


These queue numbers can then be used as printout within the Gateway configuration for central and
user-specific printouts.


The column On/Off shows whether the printer is still installed on the computer and if it is available. If
printers are deleted after the allocation of queue numbers, fax documents, which should be printed out
on this printer, are copied into the error file
(default: \Telesnap UMS\mailgate\print\error) with an appropriate entry in the event list.


The printing service is activated like all other Telesnap UMS-services in the windows service-control-
window. The service can be started for the purpose of testing and monitoring in the console-mode
“Telesnap UMSPRN-C”, too.




The console-window shows the status of each printer-job.


3.4.3.1          Archive

Telesnap UMS printing and Archive can archive all faxes centrally; additionally or alternatively to
printing.
The selection (in the register Fax) whether received and/or sent faxes should be handled is possible.
The fax files are then copied into the in or out folders. A description of the file interface can be found in
Telesnap UMS Technical Information.



    Attention: Do not forget to transfer the archive to other media or to delete it after a while
depending upon the size of the disk memory!



                                                                                                     64(170)
                                                                      Telesnap UMS – Technical Guide




3.4.4 Attachments

The appendix attachment converter provides further information and additional configuration settings.
The list of file types that can directly process the different converter versions can be found here.




3.4.4.1          Conversion

This is the central place for controlling the way of conversion. Firstly, file types, which are normally
permitted or forbidden can be specified. Afterwards, you can adjust how certain file types should be
processed.


The file types may be entered with or without a dot.



Only convert...

All file types, separated by commas, which are to be converted by the attachment converter can be
entered here. Only the file types entered here are converted, all the other file types will not be
processed.

                                                                                                   65(170)
                                                                    Telesnap UMS – Technical Guide




Do not convert...

All file types that are not converted by the attachment converter can be entered here, separated by
commas. All executable binary files and file types, which do not normally have any optical content
should be listed here. Full-motion pictures are also not possible.
Examples: com, exe, dll, zip, wav, mp3, avi, RAM



Use shell conversion...

File types, which are to be converted by use of shell-commands (i.e. with the help of the original
application) can be are entered here, separated by commas.


Examples: doc, xls, tif




      ATTENTION: When using shell conversion on the Windows 2000 station, the original
application must already be installed and configured!




3.4.4.2         Margins
The margins of a non-formatted text (e.g. ASCII) for fax conversion are set here.
If a document to be converted already contains settings concerning the page layout (e.g. Office
documents), these remain effective. The settings in this dialogue are only relevant for non-formatted
texts.


3.4.4.3         Font
The font for fax conversion of non-formatted texts (e.g. ASCII) is entered here. Pressing the button
Change a dialogue appears in which you can enter the font type and font size. The button set defaults
sets the standard value: Arial Standard 10.




3.4.5 SNMP
In the SNMP dialogue the Telesnap UMS SNMP agent is configured for the monitoring of the
Telesnap UMS services. Further information about the types of installations you can find in the chapter
“SNMP-functions”.
Of course you can handle Telesnap UMS without the installation and configuration of the SNMP-
service. This service, however, provides an optimized functionality of monitoring which permits to
control all components of the system continuously.




                                                                                                 66(170)
                                                                  Telesnap UMS – Technical Guide



3.5 User administration using WebAdmin

By default the Telesnap UMS system retrieves its user data via ODBC from the Snapware user
database ‘TsConfig’, which is configured by the WebAdmin. The following chapters describe the
configuration of user specific informations and the configuration of the Telesnap UMS Profiles.


3.5.1 User specific informations
User general




User products:




Voicemail settings:




                                                                                              67(170)
                             Telesnap UMS – Technical Guide



3.5.2 Telesnap UMS profile




                                                    68(170)
                                                                     Telesnap UMS – Technical Guide




4       System Check


4.1 First System Check

After processing the previous steps accurately, we can continue with the first start of the Telesnap
UMS-Kernel-modules.
The Telesnap UMS-services should be run as a console-application in order to receive more distinct
feedback messages.
After the initiation all desired services can get the start-mode automatic and then start working in the
background.
The order of the start of the services is arbitrary later. For the first start however the Telesnap UMS
Queue Manager has to be started before the run of the Telesnap UMS Autotext, so that a couple of
new folders can be provided.


4.1.1.1         Start of the Basic Services
Please start the links of the Basic Services as a console in the start-menu or on the desktop:
            1. Telesnap UMS Queue Manager
            2. Telesnap UMS Autotext
            3. Telesnap UMS Line Manager


Now three consoles plus the number of all channel-consoles are visible. The windows for the Channel-
Processes are minimized and not relevant – except of their presence.


4.1.1.2         Telesnap UMS Queue Manager
If the queues manager has been executed as console, (similarly as Telesnap UMS administrator),
queue processes can be supervised and even be cancelled.
A description of the possible actions and opinions you receive by pressing the key < F1 >. All other
keys are indicated in the window.


     NOTE: During the installation the system account has been registered a service account. If the
Telesnap UMS system consists of several servers, it must get an account with network access.


4.1.1.3         Telesnap UMS Autotext
The window does not provide many functions. The possible keys are displayed on the screen window.
You can switch the autotext-mode to an inactive state (paused).
The second possibility is to stop sending, i.e. auto text does not accept any new auto text jobs from
the send-folder. However, it continues to monitor the active jobs in order to generate the status of
transmission.


                                                                                                  69(170)
                                                                   Telesnap UMS – Technical Guide



4.1.1.4         Telesnap UMS Line Manager
The Telesnap UMS Line Manager is -concerning the starting-conditions- the most sensitive Telesnap
UMS-process. If, e.g. the license code doesn’t fit, the Telesnap UMS Line Manager will terminate
himself immediately. If channels were configured which doesn’t correspond to the hardware (missing
hardware), error messages regarding the particular channels appear after a while.


All configured channels should be listed in the window and display the working status. There is no
possibility for interaction.



4.1.1.5         Internal Sending
Operating normally, a Gateway will produce so-called auto text jobs, which are then processed by
Telesnap UMS auto text followed by a queue entry and finally Telesnap UMS LINE manager sends
the document.

As the Gateway is not yet in operation a minimum auto text job must be produced manually: There is
an example on the Telesnap UMS CD \tools\Testfax\sample.txt:


@phone:insert faxnumber here
@user:Tom Tester
@file:testfax.tif


Now take a normal telephone extension number - e.g. 1234. A check is merely to be undertaken to
see if a connection is made and the phone rings.


Copy all files from \tools\Testfax into \Telesnap UMS\mailgate\senden and alter sample.txt with a word
processor (Delete write protection attribute beforehand):

@phone:1234
@user:Tom Tester
@file:testfax.tif




Now start \Telesnap UMS\mailgate\senden\go.bat. The batch copies the file sample.txt into sample.
par. Telesnap UMS auto text continually waits for files *.par in\Telesnap UMS\mailgate\senden and
processes them immediately, i.e. they disappear.

After some seconds the job is in the queue and is carried out by a suitable, free channel. The
telephone at the extension 1234 should ring. The fax GCN tone can be heard which is only a pleasant
noise for that moment. Much has been accomplished since the connection to PBX or PSTN is
basically in order.

The fax job could not be successfully sent. By pressing <F3> (queue list) in the window of the
Telesnap UMS queue manager repetitions are stopped and the job can be aborted by pressing < Del
>.


A second test could be undertaken using the same procedure for a fax machine, but this does not
achieve anything further.
                                                                                               70(170)
                                                                      Telesnap UMS – Technical Guide




4.1.2 Sending externally
If Telesnap UMS is connected to a PBX a test can be done to see if external calls are permitted
(complete exchange auTelesnap UMSization). If this is not possible, the PBX service must setup.


Start the Telesnap UMS administrator. The number actually dialed can be directly checked at the top.


Alter the sample.txt e.g. change in a way so that it results calling up your mobile telephone:


@phone:017........
@user:Tom Tester
@file:testfax.tif


Now start \Telesnap UMS\mailgate\senden\go.bat .

After a few seconds the job is in the queue and is carried out by a suitable, free channel. Watch if the
correct outside line is chosen in Telesnap UMS administrator. The Handy should ring.


This means that the complete external line auTelesnap UMSization is available for Telesnap UMS. If
certain users have fewer rights at a later stage, it is possible to program this in the user administration.



4.1.3 Receiving
If a UMS Telesnap UMS is installed the simplest way to test the receipt is a normal telephone call.

If only the fax service is licensed, the best way to test is to send a test fax from a fax machine to
Telesnap UMS.




     Example: Your ISDN connection has the number (prefix) 234-0. The code digit 9 is
programmed in PBX for using the Telesnap UMS lines. The user DIDs should be 4-digit (also in the
user administration). This has also been set in the DID configuration.


This test is not to reach the user with the extension 4711. We only want to check that messages are
received by Telesnap UMS and the DID registered by Telesnap UMS.


Dial (internally) 9-4711 or (externally) prefix -234-9-4711.


If dialing by telephone (UMS Telesnap UMS) the Telesnap UMS standard announcement is heard: "
hello, here is the Telesnap UMS communication network. The connection to number 4-7-1-1 is
currently not attainable – please leave a message after the beep."



                                                                                                    71(170)
                                                                     Telesnap UMS – Technical Guide



Telesnap UMS reads out the exact number, which is received. This makes any investigation
necessary for the fax Telesnap UMS (which cannot speak) superfluous:


New incoming messages (faxes and voice) are firstly stored in \Telesnap UMS\mailgate. The
important administration file vermit.dat is also located here, which contains the classifications between
messages and received DIDs. If a mailgateway were active vermit.dat would only have a very short
“life span” as Mailgateway would immediately begin the input-switching.


Open vermit.dat with a word processor and take a look at the beginning of the first line.
                U4711, K041234, f03b0531.wav, 1, A000C8E89FA30005


It is possible to see if the DID 4711 has reached Telesnap UMS as intended.


This section (system area kernel modules) is then successfully completed and the third and last
system area mailgateway can be started.



4.1.4 Tests without Telesnap UMS software
The reason for these tests is to check the three Telesnap UMS basic services (see above) with the
ISDN connection.


If the ISDN connection is to be concentrated on in more detail, there are tools for the Brooktrout
Telesnap UMS which work without the Telesnap UMS kernel modules. This also makes it possible to
send and receive test faxes. A so-called CAPI trace is also possible.




4.2 Start of Telesnap UMS Sync
This service is optional. It is used for the creation of a cache database with user information, which
can be taken into consideration by the Telesnap UMS Line Manager when accepting a call.
.
Start with the links in the start menu or from the desktop Telesnap UMS Sync. Firstly, all parameters
are displayed. The time of the next synchronisation is seen. By pressing the key < R> the immediate
synchronization is activated. With the initial start-up the synchronization automatically begins.


At this stage probably few/no users have been recorded. Therefore, the first cache databank does not
contain any entries. If the DID Checking is already active, no more incoming calls are accepted. To
check Telesnap UMS Sync please firstly deactivates the DID Checking (in Telesnap UMS Set up,
register DID).


This is how Telesnap UMS Sync can be carried out „isolated“ and the synchronizations can be
undertaken.


Depending on the size of the used user database, the synchronization can take from a few seconds or
up to an hour. Both the start and finish of the synchronization are stored in the NT-event journal.
                                                                                                 72(170)
                                                                      Telesnap UMS – Technical Guide



Changes in the user database, i.e. new and changed entries are only effected following the next set
synchronization interval.




4.3 Distributed Telesnap UMS servers

The following information is only relevant if several Telesnap UMS servers have been installed, split
into Telesnap UMS Line server and Telesnap UMS control server. If only an individual Telesnap UMS
server is installed please disregard this section.


In the current version of Telesnap UMS the configuration must be accomplished separately for each
system i.e. both Telesnap UMS control server and Telesnap UMS Line server must be configured
individually. For future versions of Telesnap UMS the configuration and administration of Telesnap
UMS will be possible from a central place.


Only two entries must be undertaken in the local Telesnap UMS.ini of the Line server to connect the
Line server with the control server. This cannot be achieved with Telesnap UMS Setup. A text-editor is
required.


Please open the file Telesnap UMS.ini in the folder \Telesnap UMS\bin of each Line Server. An (still
out-commented) entry control station is in the paragraph [MAIN]. The computer name of the control
server must then be entered. Furthermore, each Line server must receive its own unique number.
This value is located in the same section and is called ServerNumber.


[Main]
...
; ServerNumber - Telesnap UMS server number for connection to Telesnap UMS
Queue Manager service, default=1
ServerNumber=1
; ControlStation - name of the machine where Telesnap UMS Queue Manager
service is running.
; Default is the local machine name. Setting is recommended if running on
external machine.
ControlStation=MyControlServer


This result in the service Telesnap UMS Line manager operating on the Line servers does not search
for a local Telesnap UMS queue manager but for the one located on the Telesnap UMS control server.
This entry must be for all available Line servers.


Afterwards, the Telesnap UMS queue manager can be started on the control server and then all
Telesnap UMS Line manager can be started on the Line servers.


In order to check that all Line servers register with the control server start the program Telesnap UMS
administrator on the control server. All available lines on the Line server will appear after a short time.
The S refers to the server number on the Line server; the C refers to the channel (Channel) of this
server. The channels on each server are numbered beginning with 1.



                                                                                                   73(170)
Telesnap UMS – Technical Guide




                       74(170)
                                                                      Telesnap UMS – Technical Guide




5         Using Telesnap UMS


5.1 Receiving messages

5.1.1 Reception
Received Fax- and Voice-Messages are deposited in a switching-list (\Telesnap
UMS\mailgate\vermit.dat) by the Telesnap UMS-server and subsequently processed by
Telesnap UMS gateway. Before the document is forwarded as an email, Telesnap UMS gateway
looks up in the database for the received extension. The found user (or default-receiver) receives the
message as an email with a .wav or .tiff-attachment.
Since internet-based emails cannot be typed differently, the received documents are typed on the
basis of the subject-field. Consecutively the contents of subject-fields for Voice- and Fax-mails in
German and English are listed:



Language                 Type             Attachment        Subject
German                   Fax              TIF,GIF,JPG       "<p> page(s) Fax from <k>"
German                   Voice            WAV               "VoiceMessage <d> from <k>"


    <p> = Number Fax-pages
    <k> = Identifier sender
    <d> = Duration of the Voice Message in the form hh:mm (only in Telesnap UMS Mail)




If the receiver couldn’t be resolved and the following content is sent to the postmaster:


                “Please forward to <r>”
                <r> = Extension of the original receiver.




German          Report OK        if so TIF        >OK< und Original-Betreff
German          Report Error     if so TIF       >Hinweis< bzw. >Fehler< und Original-Betreff


English         Fax              TIF, GIF, JPG "<p> page(s) fax from <k>"
English         Voice            WAV              "Voicemessage <d> from <k>"




                                                                                                 75(170)
                                                                     Telesnap UMS – Technical Guide



    <p> = number Fax-pages
    <k> = Identifier sender
    <d> = Duration of the Voice Message in the form hh:mm (only in Telesnap UMSMail)


If the receiver couldn’t be resolved and the following content is sent to the postmaster:


                “Please forward to <r>”
                <r> = Extension of the original receiver.


English         Report OK        if so TIF        >OK< und Original Subject
English         Report Error     if so TIF        >Hint<or>Error< und Original Subject




For testing the incoming switching function, please add a new editor with a valid mail address and an
arbitrary extension stored in the Telesnap UMS-user-database (ODBC or LDAP). Subsequently you
call up this number or send a fax to the extension.


If the document’s switching was finalized successfully, it has to be present in the inbox of the mail-
client. If an error occurred while the switching process, the document appears either in the
postmaster’s inbox which was entered under “Default Fax Receiver” or – if the SMTP-connection is
malfunctioning – in the MAILGATEERROR-subdirectory. In this case a problem exists with the SMTP-
connection. Please conduct a test proving the connection with a TELNET-tool or an email-client.




                                                                                               76(170)
                                                                    Telesnap UMS – Technical Guide




5.2 Sending Messages

5.2.1 Sending Faxes

5.2.1.1         Methods of adressing

For sending an email as fax from an Mail-Client, you have to follow a certain notation concerning the
adressing. It’s possible to list all neccessary data of a fax-sending in a mail.
Generally, the following specifications are supported:


                Fax-number
                Receiver’s name
                Receiver’s company
                Sending-time
                Priority


For sending faxes, you just have to enter the receiver’s fax-number. Therefore the fax-number can be
entered in three different ways:



Fax-number within the email-address
e.g. 04103939022@faxgate.speech-design.de, whereby the existing mail-server must support
an appropriate routing-function, i.e. all fax-documents which have been sent to faxgate.speech-
design.de must be deposited in the inbox of the fax-gateway-mailbox.



Fax-number within the email-name or mail-alias
Within the production of a new Internet-mail-address, which can be stored in the mail-client’s address
book, you have the possibility to enter the fax-number and further receiving-data in the mail-address’
fields “name” or “alias”. The advantage of this procedure is the possibility to organize mail-addresses
in an easy way. Further on, no modifications have to take place at the mail-server, since the address
indicates directly the gateway’s mailbox.


The data could be:
        Mail-Name:         FAX:0410388672
        Mail-Address:      faxgate@firma.com


Important is that the keyword FAX: is used here.




                                                                                                77(170)
                                                                     Telesnap UMS – Technical Guide



Fax-number within the subject-field of the emails
Here the same format-settings apply as mentioning the fax-number within the email-name or the mail-
alias. Even here, the keyword FAX: is compellingly necessary.




5.2.1.2         Additional information within the addressing

Fax-number
The Gateway searches for a valid fax-address in an outgoing mail in the following order:


                In the mail-address (are there numbers available before the @?)
                In the mail-name (is FAX: available?)
                In the subject-field (is FAX: available?)


After a valid address has been found, the system does not carry on searching in the following fields.




Receiver’s name
The specification of receiver-information like name or company can/ must take place within the
addressing. Afterwards, these data are transferred to the fax-datasheet. Since within an Internet-mail-
address blanks are permitted, the following notation is expected:
        Fax-number/receiver-name/receiver-company@…


Special characters are converted as follows:


                "_"      becomes SPACE
                "/"      becomes a LINE BREAKl


Example:
The addressing to Mr. Hans Meier, company Mueller could look like that:


a) Mentioning within the mail-address:
                041039142200/Hans_Meier/Firma_Mueller@faxgate.company.com
b) Mentioning within the mail-name or the mail’s subject-field:
                FAX:041039142200/Hans_Meier/Companya_Mueller


The resulting expenditure on a Fax-datasheet could look like that:




                                                                                                78(170)
                                                                     Telesnap UMS – Technical Guide




                FAX-Message
                From: Klaus Heinze
                ABC Inc
                23, Main Street
                12345 CITY

                To:     Hans Meier
                Company Mueller

                Fax:    041039142200

                …




5.2.1.3         Sending-time and priority
Sending-time as well as priority are specified by control words. The control words have to be sperated
by blanks.


TIME:                      sending-time in SS:MM
%PRIOx                     mentions priority x:


                1 = high, Fax is inserted at the beginning of the queue and the dispatch starts as soon
                as it’s the entry’s turn
                2 = normal, the Fax-request is inserted into the queue and the dispatch starts as soon
                as it is the entry’s turn
                3 = low, the fax is sent at a cost-efficient sending-time, as far as it has been specified
                in the configuration-file autotext.ini


The appropriate section in autotext.ini is:
[zeiten]
zeit1=02:00,05:00
standard value=2 (normal)


5.2.1.4         Ignoring messages with identical MessageID
While sending messages to address-lists some MailClients (e.g. Internet-Mailer) possibly create n
identical mails to a list containing these n-receivers. Since the gateway creates an own fax-request for
all receivers, n*n fax-request would be created, i.e. each receiver would receive the message n-times.
This problem can be solved as follows:
As these n-mails have the same message-ID, you can ensure by an appropriate registry-entry in the
gateway that only the first of these mails will be processed.
Registry-Entry: IgnoreByMSGID=1 (dword) beyond thor\mailgate




                                                                                                   79(170)
                                                                   Telesnap UMS – Technical Guide




5.2.1.5         Sending Voicemail / Talkmail
Beside the dispatch of fax-messages, the dispatch of received voice-messages and the dispatch of so
called Talkmails is possible. In this case Telesnap UMS dials the desired number and plays the
contained Voicemail or reads the contained text to the receiver using the primary email-speaker.


As this services are able to use all options of conventional emails like sending-time or server-based
rules, you could, for example, use them as wake-up service or information service. Even with this rule-
based events, important messages could be sent to determined users immediately and then be read
out “live”. The user may decide himself if and what this services are suitable for.
To send an email as Talkmail, you merely have to enter the control word VOICE in the subject-field
followed by the number of the receiver’s mobile. Example:


Subject:                VOICE:<Telefon-Nummer>


The content of such an email can be a wave-file or text only.



5.2.2 Sending SMS
Besides of sending faxes, the dispatch of SMS-messages to mobile phones is possible. Therefore you
need an SMS-capable Telesnap UMS-channel.
SMS-messages may have a maximum length of 160 signs. While dispatching, the gateway adds
several signs describing sender and subject so that the number of written signs should not exceed 100
signs. Generally, it’s possible to send even longer SMS-messages, which then will be split by
Telesnap UMS and will be sent as multiple messages.
To send an email as an SMS-message the control word SMS: followed by the number of the receiver’s
mobile. Example:
Subject:                SMS: 01721234567


Please note, that it’s not possible to add documents to an SMS-email.




                                                                                               80(170)
                                                                 Telesnap UMS – Technical Guide



5.3 Telesnap UMS VoiceAccess

If Telesnap UMS could not/cannot be used for VoiceAccess, this section can be skipped.


The Telesnap UMS VoiceAccess enables all users of a mail system - in which VoiceAccess is
permitted - to access all the emails in their email box by telephone.



5.3.1 VoiceAccess functions

Using Telesnap UMS VoiceAccess, every user has access to his/her email box from anywhere. The
only prerequisite is a touch-tone telephone.


In VoiceAccess the messages are always provided in this order:


               1. Unread messages with high priority (important)
               2. Remaining unread messages
               3. Old (read) messages


Within these three groups the messages are sorted according to date and time - the most recent
appear first.


After a voice message or email has been completely played back or read out by Telesnap UMS, it is
marked automatically as read. With the option mark as unread, the user can mark this message again
as a new message.
The marking of a message as read/unread is generally not supported by the POP3-Protokoll. The
menu option is also not provided.




                                                                                           81(170)
                                                                    Telesnap UMS – Technical Guide




5.3.1.1         VoiceMails
All voice messages (VoiceMails) can be
                •   heard,
                •   deleted,
                •   forwarded to internal users (with spoken commentary when desired), or
                •   marked as unread (not with POP3)
by telephone.


5.3.1.2         FaxMails
All fax messages (fax mails) can be:
                •   directly recalled (from a fax machine),
                •   forwarded to any fax machines,
                •   forwarded to internal users (with spoken commentary when desired), or
                •   marked as unread (not with POP3)
by telephone.


5.3.1.3         Emails
All "normal" emails can be:

                •   read out (including attachments),
                •   answered (voice recording),
                •   forwarded to internal users (with spoken commentary if desired)
                •   forwarded to any fax devices,
                •   deleted
                •   marked as unread (not with POP3)


5.3.1.4         Dates
All current Outlook dates of the mail are announced automatically in the overview, additionally the user
is able to
                •   Get announced contents of dates, like place, time, reference and took part
                    persons
                •   Get announced dates from today, tomorrow or next
                •   To search for dates in a period and
                •   To delete dates.


5.3.1.5         Connecting
In the main menu the caller can be connected to any number.


                                                                                                82(170)
                                                                   Telesnap UMS – Technical Guide



5.3.1.6         User settings
                •   The personal announcement text can be modified.
                •   The personal secret number text can be modified.
                •   The autoplay function (automatic playing of new messages) can be switched on
                    and off.
                •   The date announcement can be switched on and off.



5.3.2 VoiceAccess Menus
The VoiceAccess menus of Telesnap UMS are constructed in a similar way and therefore easy to use.
        Keys can already be pressed during the menu announcement or the message playback. The
        required action is carried out immediately up to the function Delete.



5.3.3 Dialing into Telesnap UMS VoiceAccess
There are generally two possibilities for accessing VoiceAccess:
                •   the user selects the general accession number and enters his/her PIN after or
                    during the greeting. The general access number must have been created in the
                    Telesnap UMS Setup in the register DID before.

                •   the user selects his/her personal direct-inward dialing number and enters the PIN
                    during his announcement.


5.3.4 Greeting
If a user has not yet recorded a personal announcement, Telesnap UMS uses a standard
announcement. If the user records such an announcement, this is used instead. If the Telesnap UMS
system is selected under a virtual direct-inward dialing number of a user, Telesnap UMS makes the
following announcement:


" Hello, here is the Telesnap UMS communication network. "
„The link“ <Number> „ cannot be reached at the moment”
„ However, you may leave a message after the beep.“


The Telesnap UMS system provides automatic service recognition and during the announcement the
system can switch to three different operating modes:
If Telesnap UMS discovers a CNG fax tone during the announcement, the system switches
automatically to fax receipt and then forwards the document to the user by using the gateway.
If the caller inputs his secret number over the DTMF keyboard during the announcement, the system
branches out to the main menu.


If neither a CNG tone nor a DTMF tone is detected, the caller can leave a voice message after the
announcement that is forwarded to the user via gateway.
If the maximum recording time is reached, the following is announced:

                                                                                                83(170)
                                                                 Telesnap UMS – Technical Guide



„Thank you, good bye.”


5.3.5 Main menu
                                    1            2               3

                                   Hear        Read         Recall fax
                                   voice      Emails         message

                                    4            5               6

                                  Dates      Address-
                                                                —
                             /Calendar         book

                                    7            8               9

                            Overview of        User
                                  today’s                  Connecting
                                            Adjustments
                                  dates
                                    *            0               #


                                    —          Help             —




After the login has been successful, the caller reaches the main menu. From here the individual
message types can now be accessed. The user options can also be set. If the autoplay function is
activated, the first new voice message is played back without further key input.



 1 – Hear voice message
branch into the voice recall menu

 2 – Read emails
branch into the email reading menu

 3 – Recall fax documents
branch into the fax recall menu

 4 – Dates/ Calendar
branch into the dates/ calendar-Menu.

 5 – Address-book
branch into the Address-book-Menu

 7 – Overview of today’s dates
an overview of all new messages and upcoming dates

 9 – Connecting
branch into the Connecting-menu
                                                                                             84(170)
                                                                    Telesnap UMS – Technical Guide



 8 – To user adjustments menu
branch into the user adjustments menu

 0 – Help in the main menu
Brief assistance for the individual menu options is announced.



5.3.6 Voicemail menu


                                  1                2               3

                                Delete                            Pass
                                                  —
                               message                       message on

                                  4                5               6

                              Previous          Mark              Next

                              message         as unread          Message

                                  7                8               9


                                                  —              Forward
                               Rewind

                                  *                0               #

                               To main
                                                 Help              —
                                menu



Voice messages can be heard over the telephone in this menu. After calling up this menu, the first
new voice message is played automatically. After the complete playback of the message the message
is marked as read (not POP3) and the user then has the following input options:



 1 – Delete voice message
The message is deleted. With Exchange this message is shifted into the folder deleted objects. In all
other systems the message is deleted permanently.

 3 – Forward message
Using this function the voice message can be forwarded to any internal Telesnap UMS user. The user
can also record a comment concerning the message.

 4 – Play previous message
The previous message is shown. If the first message is reached, an appropriate announcement is
played back. The current message is marked as read after the message has been completely shown.




                                                                                               85(170)
                                                                    Telesnap UMS – Technical Guide



 5 – Mark the message as unread
It may be desired that the message be shown in a later call as a new message again. Then the next
message is played back.

 6 – Play next message
The next message is shown. The current message is not marked as read if the message has not yet
been completely shown. If the last message is reached, the first old message is shown if it is available.
If, in this case, the last message is reached, an appropriate announcement takes place.

 7 – Rewind within message
The playback is rewound approximately 5 seconds. In this way, contents that were not understood
when first heard can be repeated.

 9 – Forward within message
The playback moves forward approximately 5 seconds. In this way message sections, which do not
appear relevant for the user, can be ignored.

 0 – Help
Notes on using this menu are announced.

 * – Back to the main menu


5.3.7 Email menu
                                   1               2                3

                                Delete          Answer            Pass
                               message         message        message on

                                   4               5                6

                               Previous          Mark             Next

                               message         as unread        message

                                   7               8                9

                                                Change
                                Rewind                          Forward
                                               language

                                   *               0                #

                                  To
                                                 Help              —
                             main menu

In this menu emails can be heard over the telephone. After calling up this menu, the first new email is
read out automatically. Following the complete playback of the message it is marked as read (not
POP3) and the user then has the following input modes:




                                                                                                 86(170)
                                                                     Telesnap UMS – Technical Guide



 1 – Delete email
The message is deleted. With Exchange this message is shifted into the folder deleted objects. In all
other systems the message is deleted permanently.

 2 – Answer email
It is possible to record a voice message as a response, which is then sent to the sender of the email
as an attachment to the original mail

 3 – Forward email
With this function, the email can be forwarded to any internal Telesnap UMS user or an external fax
machine. If an internal Telesnap UMS direct-inward dialing number is indicated as recipient, the
recipient receives the email as a normal forwarded email. If an " external " fax number is indicated, the
email, including all contained file creations, is converted into a fax document and sent to the desired
fax machine. Therefore emails can also be recalled by fax.

 4 – Read out previous email
The previous message is shown. If the first message is reached, an appropriate announcement is
made.

 5 – Mark the email as unread
It may be desired that the email is shown again as a new message in a later call. Subsequently, the
next message is read.

 6 – Read next email
The next message is shown. If the last message is reached, the first old message is shown if
available. If the last message is also reached here, an appropriate announcement is made.

 7 – Rewind within email
The playback is rewound approximately 5 seconds and played again. In this way, contents, which
were not understood when first heard, can be repeated.

 8 – Change the language
Before reading, Telesnap UMS analyzes the language of the email. If a false language was detected,
the language can be changed manually. Following the change, firstly the secondary mail speaker is
heard, then all other installed languages.

 9 – Forward within email
The playback is forwarded approximately 5 seconds. In this way message sections, which do not
appear relevant for the user, can be ignored.

 0 – Help
Notes for using this menu are announced.

 * – Back to the main menu




                                                                                                 87(170)
                                                                    Telesnap UMS – Technical Guide



5.3.8 Fax menu


                                   1               2               3

                                              Recall fax          Pass
                                  —
                                                directly         fax on

                                   4               5               6

                               Previous                          Next
                                                   —
                               message                         message

                                   7               8               9


                                  —                —               —


                                   *               0               #

                                   To
                                                 Help              —
                             main menu



In this menu, fax messages can be recalled or forwarded to a fax machine. After calling up this menu
the data of the first fax document are announced automatically. The caller then has the following
possibilities:

 2 – Recall fax
This function is used for the immediate call of the current fax document. After a short announcement
Telesnap UMS transmits the document immediately, i.e. the caller must call either from a combination
fax machine or have the option of connecting the conversation to a fax machine. Following
transmission the telephone connection is terminated. The user must call again in order to recall further
documents.

 3 – Forwarding fax document
After selecting this function the user has the option of forwarding the fax document to a Telesnap UMS
user, to an internal or to an external fax number. The input of the destined number must be concluded
with the # - key and then acknowledged. If a Telesnap UMS user’s extension number is entered, the
fax document is sent to this user directly by email. For all other numbers the fax document is sent
again as a fax.

 4 – Previous fax message
Details of the previous fax document are announced. If the first message is reached, an appropriate
announcement is made.

 6 – Next fax message
The details of the next fax document are announced. If the last message is reached, the first old
message is shown if available. If the last message is also reached here, an appropriate
announcement is made.



                                                                                                88(170)
                                                                    Telesnap UMS – Technical Guide



 7 – Play message again
The data of the fax document are announced again.

 0 – Help
Notes on using this menu are announced.

 * – Back to the main menu




5.3.9 Date menu

Firstly, in the date menu all dates of the current day are announced and play back automatically,
similarly as email-messages in the Autoplay mode. Also the key allocation is here almost identical to
the well-known message menus.



     Attention: The date menu is only able to reach a user if either the "default service" in Telesnap
UMSSETUP was configured by Telesnap UMS to the setting "mobile Office" or if the service
"Calendar" was assigned to the user in the personal settings of the user administration.


The following data of a date are announced:
            •   Beginning
            •   End
            •   Location
            •   Subject
            •   Involved Persons
            •   Notice text of the date




      Attention: The current Version of Telesnap UMS doesn’t support the playback of series or
recurring dates. These dates are not used and announced by the system. This function will be
implemented in a later version of Telesnap UMS.
During the Playback of dates the following options are possible:




                                                                                                 89(170)
                                                                    Telesnap UMS – Technical Guide




                                     1             2               3


                             Delete date          —                —


                                     4             5               6

                               Previous                          Next
                                              Play again
                                 date                            date

                                     7             8               9

                                              Search for
                               rewind                          forward
                                                 date

                                     *             0               #

                                     To
                                                 Help              —
                             main menu


 1 – Delete Date
The date is deleted permanently.

 4 – Announce previous date
The previous date is played. If the first date is reached an appropriate announce takes place.

 5 – Play date again
The selected date is played again.

 6 – Announce next date
The next date is played. f the late date is reached an appropriate announce takes place.

 7 – Rewind within a date
The playback is rewind for ca. 5 seconds and played again. In this way contents, which could not be
understood hearing the first time could be repeated.

 8    Search for a date
Here you jump to the search-for-a-date-menu.

 9    Forward within a date
The playback is forwarded for ca. 5 seconds and played again. In this way contents which seem to be
not relevant can be skipped.

 0 – Help
Notes on using this menu are announced.

 * – Back to the main men


                                                                                                 90(170)
                                                                  Telesnap UMS – Technical Guide



5.3.10 Search-for-date-menu


                                     1             2             3


                                   today       tomorrow     Next 7 days


                                     4             5             6


                             This month        Next month   Enter period


                                     7             8             9


                                 Enter date        —             —


                                     *             0             #

                                     To
                                                   —             —
                                 date menu



 1 – Today
All dates of today are played.

 2 – Tomorrow
All dates of the next day are played.

 3 – Next 7 days
All dates of the next seven days are played.

 4 – This month
All dates of the current month are played.

 5 – Next month
All dates of the next month are played.

 6    Enter a period
Here you can enter a time period with a start and an end date (8 digits in the form DDMMYY).
Subsequently number and content of the dates of the entered period are played.

 7    Enter a date
Here you can enter a single date (8 digits in the form DDMMYY). Subsequently number and content of
this date are played.

 * – Back to the main menu

                                                                                               91(170)
                                                                       Telesnap UMS – Technical Guide



5.3.11 Address book menu

Firstly in the Address-book menu the number of all address-book entries is announced. Thereby all
outlook-contacts are counted. Additionally the user enters the search mask. The hits are presented in
alphabetical order.



      Attention: The access to the Address book-menu is only possible if in Telesnap UMSSETUP the
“Default-Service” of Telesnap UMS is configured to “Mobile Office” or if in the personal settings the
service “address book” has been allocated to the user.


To select a directory entry the user must use the telephone keyboard in the letter mode. Alternatively
the initial letter or the initial part of a surname is to be entered. With current telephones the associated
letters are visible on the keyboard as follows:



                                    1                2                3


                                                   ABC              DEF


                                    4                5                6


                                  GHI              JKL             MNO


                                    7                8                9


                                 PQRS              TUV              WXYZ




To select an entry or a letter the user must press one to four-times the according button. Here some
examples:


To search the first entry with “A”                 1 x button 2
To search the first entry with “B”                 2 x button 2
To search the first entry with “S”                 4 x button 7
To search the first entry with “SE”        4 x button 7, 2 x button 3
To search the first entry with “MEI”       1 x button 7, 2 x button 3, 3 x button 4



    Note: Telesnap UMS considers just address book entries which contain an entry i, field last
name.




                                                                                                    92(170)
                                                                      Telesnap UMS – Technical Guide



The system has a timeout between the exhibits of differing letters. If you do not want to use the first
letter of a button, the button has to be pressed several times in a time interval of two seconds.
Otherwise the first letter of this button is detected.
Whenever the system detects a letter a short tone acknowledges the entry.



              Note: Umlauts cannot be entered directly


After the input of the letters the system announces the first letter which relevant for the selection. The
following data will be announced:


                 •   Pre- and surname
                 •   Company
                 •   Phone number
                 •   Mobile phone number
                 •   Private number
                 •   Email


Beginning with this entry the user is able to navigate within the sorted list. He can be connected to a
subscriber or send a voice message per email. Further the entry can be deleted as well.



                                    1                2                3

                                                                send eMail
                                 delete


                                    4                5                6


                                Previous         Connect            Next


                                    7                8                9


                                  First           Search           Latest


                                    *                0                #


                              Main menu            help




 1 – Delete entry
Address book entry is deleted permanently.

                                                                                                   93(170)
                                                                    Telesnap UMS – Technical Guide



 3 – Send eMail
With this function you can send a spoken comment by email to the selected contact, similarly as
answering to an email with a voice massage. The addressee receives this email as a conventional
email with an audio appendix. The recording of the message and the additional processing options are
here identically to answering email in the email call menu.

 4 – Previous Entry
The previous entry is played. When the first entry is reached an appropriate announce takes place.

 5 – Connecting
If the selected entry possesses one or more telephone numbers, the user can be connected with this
participant on the phone. If several numbers are existent, the desired number must be selected
additionally. Then Telesnap UMS establishes a connection. During the conversation the user can
terminate the connection any time by pressing the # - key. If the connection is terminated, the user is
navigated to the directory menu again.


       ATTENTION: In order to be connected with a number, each user needs auTelesnap
UMSizations which are specified in various stages under "default call auTelesnap UMSization" in the
user administration. If a user does not have the auTelesnap UMSization to dial an appropriate number
this option will not be announced by the system and cannot be selected. in order to prevent
inadvertent telephone calls of unauTelesnap UMSized persons this function is always active.

 6 – Next entry
The next entry is played. When the last entry is reached an appropriate announce takes place.

 7 – First Entry
The first entry is played.

 8 – Search
Switch to search mode.

 9 – Last
The last entry is played.

 0 – Help
Notes for the use of this menu are announced.

 * – Back to main menu




                                                                                                 94(170)
                                                                   Telesnap UMS – Technical Guide




5.3.12 Connecting-Menu
In this menu, the user can be connected to an arbitrary telephone number. Telesnap UMS then
establishes the connection. The user is able anytime to close the connection by pressing the #-button.
Afterwards, the user arrives back at the system’s main menu.
In diesem Menü kann der Benutzer sich mit einer beliebigen Nummer verbinden lassen. Telesnap
UMS baut anschließend eine Verbindung auf. Durch Drücken der #-Taste hat der Benutzer jederzeit
die Möglichkeit , die Verbindung zu beenden. Anschließend landet der Benutzer wieder im Hauptmenü
des Systems.



       ATTENTION: To be able to be connected to a number, each user needs appropriate
auTelesnap UMSizations, which are set in different ranks in the „Default Call AuTelesnap
UMSizations“. If any user tries to dial a non-auTelesnap UMSizised number, the system caused an
interrupt and an appropriate announcement takes place.



5.3.13 User settings menu


                                 1                2                3

                              Modify           Modify           Modify

                             Greeting           Name             secret
                                                                    b
                                 4                5                6

                             Autoplay            Date
                                            announcement           —
                              On/off            on/off
                                 7                8                9


                                 —                —                —


                                 *                0                #

                                To
                                                Help               —
                            main menu


 1 – Recording personal announcement / switching on standard
announcement
Up to 9 personal greeting texts can be recorded and listened to. Further on the standard
announcement can be activated and the selected greeting text can be activated as announcing box.
The way of recording an announcement is identical to the recording of an answer or a spoken
message. Additionally, after the recording each present take can be used for the announcing mode by
pressing button 5. If the announcing mode is activated a caller cannot leave a message. This function
is helpful during longer absence or vacation if you do not want to receive voice messages.


                                                                                              95(170)
                                                                 Telesnap UMS – Technical Guide



 2 –Record / modify names
Here the name of the user to be announced in the greeting can be recorded.

 3 – Modify secret number
The personal secret number for VoiceAccess can be entered and stored here.

 4 – Autoplay function on/off
The automatic playback of the first new message following logging on of VoiceAccess can be switched
on and off here.

 5 – Date announcement on/off
The additional announcement of the receipt time during the playback of each message can be
switched on and off here.

 0 – Help
Notes on using this menu are announced.

 * – Back to the main menu




                                                                                           96(170)
                                                                  Telesnap UMS – Technical Guide




6      Administration, diagnosis, service


6.1 Telesnap UMS Administrator
       The Telesnap UMS administrator is used for the monitoring of the entire Telesnap UMS
       system. It offers the following information:

           •   Status and event displays of the Telesnap UMS- services
           •   Status of each channel (sender, destination) – also several line servers at one go
           •   Sending queue (level and detail of each job)
           •   Access to Telesnap UMS journals
The application can be called up on a Telesnap UMS server or on another NT machine. A network
connection for the Telesnap UMS server is all that is required.


      NOTE: The Telesnap UMS queue manager is the collecting area for all status messages of the
Telesnap UMS line manager. This means if the Telesnap UMS queue manager does not operate, the
information could not be displayed on any Telesnap UMS line manager.




                                                                                              97(170)
                                                                   Telesnap UMS – Technical Guide




6.1.1 Toolbar

The toolbar contains several of the frequently used functions.




                                                       The functions in detail:

                                                                 1.      Local connection to the Telesnap
                                                                         UMS-Server of this machine

                                                                 2.      Connection to a distributed
                                                                         Telesnap UMS-Server

                                                                 3.      Close Connection from Telesnap
                                                                         UMSADMIN to Control Server

                                                                 4.      Delete job from queue


                                                                 5.      Lock Service communication. If
                                                                         Telesnap UMSATX is locked,
                                                                         further jobs will not be sent to
                                                                         Telesnap UMSQ anymore. If
                                                                         Telesnap UMSQ is locked,
                                                                         further jobs will not be sent to the
                                                                         Telesnap UMS Line-Manager.

                                                                 6.      Unlock    service-communication
                                                                         (see above)

                                                                 7.      Print the statistics


                                                                 8.      Info about Telesnap UMSADMIN




6.1.2 Server-Display
                                                      To establish a connection to a Telesnap UMS-
                                                      Server please choose“ File->New Connection”.
                                                      In the following dialogue the name of the
                                                      Telesnap UMS-Control-Server must be entered.




                                                                                                98(170)
                                                                    Telesnap UMS – Technical Guide




6.1.3 Channel status display
                                                     In the normal state the Channel status display
                                                     shows a summary over all channels of a server.
                                                     Using several LINE servers for each a single
                                                     summary appears. Thus provides a better
                                                     overview in case of large installations.
                                                     .




If you click on one of these summaries or choose a server in the left server-window, the channel-
status display changes to the detailed view.




In this window the online status of all channels can be monitored. In the menu View, a selection of
different representations can be made. In the view Detailed, the called and calling identifiers of a
connection are displayed for a current internal message. Depending on whether the call is incoming or
outgoing, the details are different.


           Type of call            Local Number                     Remote Number
           Incoming / Receipt      Selected direct-inward dialing   Sender call number/
                                                                    TSI
           Outgoing/               Virtual branch                   Selection digit
           Transmitting


With a fax transmission, the identifier changes after establishing a digital connection to the fax
identifier of the sender or receiving machine. Furthermore, during the transmission of a fax document
the page is displayed which has just been sent.




                                                                                               99(170)
                                                                      Telesnap UMS – Technical Guide



                                  Additionally in the menu view you can choose the look and the level of
                                  detailing.




6.1.4 Queue

The queue contains all jobs waiting for being sent. The icon on the left indicates the type of job. There
are the following job types:


                         Fax
                         Talk mail
                         SMS
                         set Message-Waiting
                         delete Message-Waiting


        If necessary, the administrator can abort waiting jobs by Menu Modify Break or with the
        box    . The sender of the message then receives a negative receipt with the error cause:
        manual abort.



6.1.5 Service check and events

The displayed Telesnap UMS services can be started and stopped in the Telesnap UMS
administrator.

        In distributed Telesnap UMS systems, all the Telesnap UMS Line managers of the attached
        Line servers are displayed. In this case, the name of the computer is also displayed after the
        service name on which the service is active. Icons display event announcements of these
        services as far as they are available:


                       OK                 No messages

                       Information        Non-critical messages such as start and stop of a service

                       Warning            Critical irregularity

                       Error              A critical error occurred



                                                                                                100(170)
                                                         Telesnap UMS – Technical Guide



                                           A list of past events is displayed by double
                                           clicking on the service. A time filter can be set
                                           using the context menu on this event
                                           monitoring and display.
                                           Additionally, the selected service can be started
                                           and stopped by pressing the right mouse button
                                           and selecting the menu point start/stop.



 Image 6-1: Service status context menu

                                           If a filter is set, only events occurring after this
                                           date are noted and displayed. The adjusted
                                           time filter always applies to all Telesnap UMS
                                           services.




6.1.5.1        Service check in distributed Telesnap UMS systems

                                          If a distributed Telesnap UMS system is used,
                                          the names of the involved Telesnap UMS
                                          servers must be indicated to Telesnap UMS
                                          administrator (usually several Line servers).
                                          The option line-servers appear in the context
                                          menu of the entry for the Telesnap UMS Line
                                          manager.



                                          In the following dialog the names of all available
                                          line-servers must be entered. After the next
                                          start of the Telesnap UMS administrator these
                                          details are automatically noted.




                                                                                      101(170)
                                                                       Telesnap UMS – Technical Guide




6.1.6 Log files and statistics

The central Telesnap UMS logs can be displayed in the left lower window with one double click.
Setting of a time filter is also possible here. Furthermore, a statistic can be called up in the context
menu of the log files.




                                                          Depending on the selected log file the statistics
                                                          contain analyses about transmitted, received or
                                                          recalled messages. Statistics can be both
                                                          exported and printed out by clicking on the box.




In distributed Telesnap UMS systems, all logs, such as SEND.LOG, RECEIVE.LOG and
VACCESS.LOG are not stored on the line servers themselves but on the control server. Thus there is
always the possibility of central evaluation. DEBUG logs are merely stored locally on the individual line
servers.




                                                                                                   102(170)
                                                                  Telesnap UMS – Technical Guide




6.2 Logging

From the beginning protocol-files are and were created in the whole Telesnap UMS-System. These
files can be classified in two groups:


   •   Operation Protocols, in which statistics and connection data are saved.
   •   Debug Protocols in which single actions are logged.


This document and the described programs deal basically with the operation protocols.


6.2.1.1           The Protocols

The table shows the most important protocols Telesnap UMS uses.


Table 1, protocols and their applications
       Protokollname      Erzeugender Dienst     Description
       activity           Telesnap UMS Line      Special activity on the channels
                          Manager
       GateIn             Telesnap UMS           Data of the received documents
                          Gateway
                                                 (Processing by the Gateway)
       GateOut            Telesnap UMS           Data of the jobs sent (Fax, Voice, SMS, usw.)
                          Gateway
                                                 (Processing by the Gateway)
       print_in           Telesnap UMS           Data of incoming documents
                          Printing and Archive
       print_out          Telesnap UMS           Data of outgoing documents
                          Printing and Archive
       receive            Telesnap UMS Line      Data of received documents
                          Manager
       send               Telesnap UMS           Data of jobs sent (Fax, Voice, SMS, usw.)
                          Queue Manager
       statall            Telesnap UMS Line      Statistics of the channels’ activities
                          Manager
       vaccess            Telesnap UMS Line      Data concerning the Voice Access on the Telesnap
                          Manager                UMS System




6.2.1.2           The applications


                                                                                             103(170)
                                                                       Telesnap UMS – Technical Guide



The applications, which create protocols can be looked up in table 1. Protocols and their applications
are described in the chapter “The Protocols”. Each of the applications uses the Telesnap
UMSLog.DLL to write the appropriate data.




Table 2, applications
        Dateiname                   Description
        Telesnap                    To write the data to the protocol-files and to the database
        UMSLog.DLL
        LogSetup.exe                Dialogue-based Admin-Tool for the Telesnap UMSLog.DLL and the
                                    Telesnap UMS Log Converter
        Telesnap                    Command line-Tool to test the functionality of the Telesnap
        UMSLogTest.exe              UMSLog.DLL. is accessed by LogSetup too
        Telesnap                    The Telesnap UMS log converter allows a special adaptation to
        UMSLogC.exe                 existing environments, in which Telesnap UMS is used. It can read in
                                    the log files, convert the data and place in databases.



6.2.1.3            The goal: Database

With the development of the Telesnap UMS system importance has been always attached to the
logging process. In the course of time the files were extended or it new ones have been added. It
suggested itself that the desire for the direct writing to a database was put into action.
Simultaneously it was also important not to change or to leave out the old functionality.
The following actions are possible:


Writing into a database
                   Variable allocation of the fields to the data base columns
                   Leaving out some fields
Writing to files
                   Rotating Protocol data
                   Changing the separators
                   Changing the order of columns and the column activation
                   Defining the minimum column width
                   Defining the column-title
                   Defining a maximum height of these files


6.2.2 LogSetup

Log Setup is the administration-tool for the Telesnap UMSLog.DLL and the Telesnap UMS Log
Converter. All important settings can be handled with this tool.



                                                                                                  104(170)
                                                                       Telesnap UMS – Technical Guide



6.2.2.1          Concept

In LogSetup several settings can be set globally and others locally. (i.e. only for one table/protocol file)
The Telesnap UMSLog.DLL interprets these settings in this order locally and globally.


6.2.2.2          LogSetup – Dialogues

The application LogSetup consists of five dialogue-pages in the file format (Register). The first three
pages (Global, Files and Database) serve for the administration of the Telesnap UMSLog .DLL. The
fifth page administrates exclusively the Telesnap UMSLogConverter.
Page four (DB spec.) takes a special position in connections to databases. Thereby it’s irrelevant for
which data source (Telesnap UMSLog.DLL or Telesnap UMS Log Converter) the appropriate
database is set.


6.2.2.3          Dialogue-page Global

The logging-goal (pages file and database), the common File-properties Rotation, Separator/
Replacer, the goal-path for the files and the settings for the database are among the Telesnap
UMSLog.DLL’s characteristics




Rotation

                                                                                                  105(170)
                                                                       Telesnap UMS – Technical Guide



With the rotation of protocol-data we mean the cyclic renaming of the file. In the field rotation the
following characteristics can be specified:


<continuous>     no rotation
day              daily
week             weekly
month            monthly renaming the file
<manual>         This value cannot be set! It’s just a value which is available for testing in the registry.



Max. file size

Here you can choose the maximum file size which the system can create.




Such a setting is possible and makes sense in the rotation mode only <continuous >. The appropriate
file is then and filled up to this size (and/or a line more than the value is indicated) and then renamed
in *.old. Thereby possibly the existing file is deleted!




Separator/ Replacer

These both fields define the Separators in the protocol files.
The separator is replaced with the Replacer in all character strings, which are written into protocol
files. This is the reason why you should think twice which setting you choose.
Standard setting is the comma as separator and the space character as replacer.



Global database settings

                                                                                                    106(170)
                                                                      Telesnap UMS – Technical Guide



This area resumes the most important database settings. In the field ODBC data source (DSN) you
enter the name of the database. The name has to be established before in the Windows 2000
ODBC.Data-sources. With the button “…” you can choose the appropriate database. In the dialogue
you’ ll be ask about the username and password for the database. These data appear in the fields
ODBC user and ODBC password (pwd) on the page “Global Database Settings”.
With the push button Check you can check the connection to the selected database.



6.2.2.4          Dialogue page Files




On the dialogue page files special settings are adjusted for each log file. There are two ranges:


            •    the upper range for file settings
            •    and the lower range for column settings




File-settings

With the pull-down menu (left above) you select a file. Only for this file the settings are indicated on
the entire dialogue page.
                                                                                                  107(170)
                                                                       Telesnap UMS – Technical Guide




        With the page buttons
        Global
        File
        Database


You select the advanced LOGGING mode. With some files one can additionally select whether an
extended or a reduced (less) LOGGING should take place.
By pressing the push button test logging the start of a test for this file - in order to examine the settings
-.is activated.
Therefor the application Telesnap UMSLogTest is started.

Column-settings

The lower range consists of a list with 4 columns and a list with push buttons on the right side. This
range is responsible for the appearance of a file. You can de-/activate columns, specify column titles,
define the minimum column width and change the column order.


        (black)           column is deactivated

        (black)           column is activated

        (black)           column is activated anytime, the position is fix


You can change the settings for this column processing a double-click on the symbol (or clicking the
button set). The following dialogue appears:




Here you can de-/ activate the column, the title and the minimum column-width.
You can change the order of the columns by pressing the push buttons Up or Down. Pressing the
push button New starts a dialogue in which you can define a new column:




                                                                                                   108(170)
                                                                    Telesnap UMS – Technical Guide




        By pressing the push button cancel you can recover the previous state.


6.2.2.5         Dialogue Page Database

The Database Page deals with the allocation if the protocol files to a database. It’s important to know
that you can only adjust settings about a database if


            •   An existent database has been adjusted on the dialogue page Global
            •   A database setting has been chosen on the dialogue page files
            •   The database has been read successfully       push button Read DB




                                                                                               109(170)
                                                                       Telesnap UMS – Technical Guide



With the push button Check DB you can test the selected settings using the database (Existence of
tables and columns). You can select the table of the database by pressing Table alias.


The push button Set provides special settings for a single column:




In the big list field additional information about columns are indicated with the following symbols:




        (blue)           deactivated field (untested)

        (blue)           activated field (untested)

        (blue)           fix field (untested)

        (black)          deactivated field without errors

        (black)          activated field in the protocol without errors

        (black)          fix field im Protokoll ohne Fehler

        (red)            deactivated field in the protocol: not in the database

        (red)            activated field in the protocol with errors: not in the database

        (red)            fix field in the protocol with errors: not in the database

                         unknown field in the database




                                                                                                 110(170)
                                                                       Telesnap UMS – Technical Guide




6.2.3 The ThorLog.DLL

In this chapter describes the settings (Registry) and the behaviour of the ThorLog.DLL. The
administration assumes LogSetup. By using Telesnap UMS Log Test the functions and the settings
can be tested.


6.2.3.1          Behaviour

The ThorLog.DLL receives its information with three specifications:


Internal name of table (e.g. send)
internal name of column (e.g. time)
content


With this data the appropriate goal (file or database) is chosen, the selected column-allocation and the
content are marked down. With the write-command the entry takes place. It may happen that the
connection to a database breaks off. In this case the entries are written into the files directly so that no
data gets lost.
The Telesnap UMS Log Converter will contain - in a future version - an additional mode, which records
these data in the database.



6.2.4 Telesnap UMS Log Test

Telesnap UMS Log test is used to test the settings. It avails oneself of the Telesnap UMS Log DLL
and can be called with different parameters. The most helpful parameter is help:




                                                                                                  111(170)
                                                                     Telesnap UMS – Technical Guide



6.2.4.1          Examples:
Test the send(log)


Telesnap UMSlogtest send loop


Testing the entries into the send (.log or DB) with repetitions every 30 seconds.




The declaration “0 error” means that the error code 0 has been passed back. Everything should be
OK. The indicated digit is an error code, which permits the conclusion to detect details about the error.




6.3 Telesnap UMS Info

This tool is used to compile almost all the important information about a Telesnap UMS system. This
means all settings of the three system domains ISDN, kernel modules and mailgateway as well as
settings of the Windows operating system.



      Each support inquiry should consist of two parts:
1. The completed form " Telesnap UMS support Request "(.dot or .pdf) from the Telesnap UMS CD in
\doc
2. A current t h o r i n f o.txt (compressed).
This generally spares any other necessary further inquiries and the process is accelerated.




                                                                                                112(170)
                                                                      Telesnap UMS – Technical Guide




The following is collated:


            •   Registry entries
            •    Configuration files (e.g. \Telesnap UMS\bin\thor.ini)
            •    Directory tree with files
            •    Version numbers and creation dates of the important files


This information can be helpful with a set of questions.
            •   Monitoring installation
            •    Service and Update
            •    Preparation of the installation routines
            •    Assistance for difficult problems



6.3.1 Functions

The use of Telesnap UMS info is very simple:
By starting the program the main dialog is reached.


            1. The range of the information collection is selected,
            2. the report process is started, and the program is terminated.
            3. the output is \Telesnap UMS\log\thorinfo.txt




                                                                                            113(170)
                                                                     Telesnap UMS – Technical Guide




                                                         The Check box read registry switches on the
                                                         reading of the registry. The entries are written
                                                         in a format, which can be re-imported as a reg-
                                                         file in the registry.




                                                         Reading configuration files is activated with the
                                                         Check Box read ini files. In this mode in each
                                                         case the whole file is always read and written
                                                         into the output file Telesnap UMSinfo.txt. The
                                                         Check box take full file is deactivated but
                                                         switched on. Then a decision can be made
                                                         with the radio buttons whether only the
                                                         Telesnap UMS.ini (with only Telesnap UMS.ini)
                                                         or all known files (with all known ini files) will
                                                         be adopted.
                                                         To compile the version information, the Check
                                                         box read version info must be activated. A
                                                         decision can be taken whether a search is to
                                                         be made in the entire Telesnap UMS system
                                                         (complete\Telesnap UMS) or only in the \bin
                                                         directory (only \bin).


                                                         With the Check box generate file, a complete
                                                         list of all directories and files can be generated.
                                                         To define the final output file you enter its
                                                         name here.




6.3.1.1         Reset
This button reinserts all the settings, which were present at the start of the program run. No safety
request appears.


6.3.1.2         Cancel
With this button the program can be exited without producing any output.


6.3.1.3         Create Info
The creation of the Telesnap UMSinfo.txt file is started with this button in the bottom left hand corner.
Before actually creating the file, the question is asked whether this should really occur.




                                                                                                  114(170)
             Telesnap UMS – Technical Guide




Appendices




                                   115(170)
                                                                   Telesnap UMS – Technical Guide




Appendix A: FAQ – Frequently asked
questions


Please refer to your questions here before contacting your dealer for support.



General

        Can Telesnap UMS receive SMS messages?


                        With a GSM-modem the reception is possible.



        Is it possible to differ between email, Voicemail and Faxmail ?


                         Yes, Telesnap UMS has nothing to do with the “previous” emails, unless it
                allows the access per telephone.



        Which version is installed?


                        To get this information please use the application Telesnap UMS info.



        Is faxing possible with Telesnap UMS using my application XY?


                         No, Telesnap UMS creates an extension of a mail system. Anytime, the client
                must send a mail effectively. There are upstream printer drivers, which do not control
                a printer but produce emails. The details depend heavily from the client-PC (OS,
                Mailclient).




                                                                                             116(170)
                                                              Telesnap UMS – Technical Guide




I try to stop the service X (Telesnap UMSQueue, Telesnap UMSAutotext, Telesnap
UMSGateway, Telesnap UMSSync, Telesnap UMSPrintingAndArchive or Telesnap
UMSLogConverter) with the Telesnap UMSAdministrator. After many tries it doesn’t
seem to work. Instead the active node on the cluster changes. What does that mean?



                The named services on cluster-control-servers are normally cluster-
        resources. They may not be stopped or started with the Telesnap UMSAdministrator
        and even not with the service-control, because this step is monitored by the cluster
        service and assumes an malfunction. All modules which run as cluster-resource must
        be controlled by the cluster administrator.



Telesnap UMS Autotext doesn’t start
        After start of Telesnap UMS Autotext as service it terminates itself immediately. Even
        in case of starting as a console with the error code that the folder …\mailgate\senden
        could not be found.


                You have tried the first start ever on your system. Starting the service the first
                time you cannot choose the order of the services Telesnap UMS Autotext and
                Telesnap UMS Queue Manager arbitrarily. Start the Telesnap UMS Queue
                Manager before Telesnap UMS Autotext. Telesnap UMS Queue Manager
                executes several small adjustments. e.g. it produced the folder
                …\mailgate\senden.


Sending job does not go out
 The gateway runs on another machine. Telesnap UMS (with Queue, Autotext and Line
Manager) processes the gateway job immediately and without error but it can only be seen in
the queue and is not forwarded. What is it waiting for?


                Telesnap UMS always waits for the right time. I.e., if the gateway computer
                has given its job at 9:00 a.m., then this time will also be noted as sending time
                for the job. The Telesnap UMS server might have a wrong system time, for
                example 8:00 a.m. The job will wait in the queue until 10:00 a.m. (then it will
                be 9:00 a.m. on Telesnap UMS) and the sending will begin.
                If the Telesnap UMS system time were ahead, the sending would start
                immediately; i.e. the job would not be ignored because it is too old.


Always dialing 0
Although I use different dialings during receiving tests, Telesnap UMS always acts as if the 0
had been dialed.


                In the DID configuration of Telesnap UMS Setup, too many digits of the
                dialing have been ignored. If there is nothing left after the cut-off, the 0 is put
                in as default. The value for the digits to be ignored should be first set to 0 so
                the received dialing will be used uncut. Now it should be tested again



                                                                                           117(170)
                                                              Telesnap UMS – Technical Guide




System domain mail-gateway

        Generating front pages with Word?
        Can I generate Telesnap UMS front pages with Word or import them from Word files?


              This is not possible. To create/adjust the front page definitions the Telesnap
        UMS Front page editor is intended.


        A front page is not required
        I would like to use a Word-created document template for faxes but I do not want
        Telesnap UMS to make an additional front page.


                 Telesnap UMS will not necessarily do this. It depends on whether only the
        Word attachment or also additional mail text has been written in the faxmail. If there is
        no mail text, no Telesnap UMS front page will be created. Attention: (Automatic)
        signatures are also mail text.



Client software

        Client software / Faxes from applications
        I would like to send a fax from, e.g. my spreadsheet analysis application by printing on
        a fax device driver.


                 Telesnap UMS provides no client software. The essential feature of Telesnap
        UMS is the close integration into the mail system. The way to send a fax always starts
        at the Client with a mail sending. Also see question printer device driver.
        For host applications there is the Telesnap UMS Autotext port. This is a file interface,
        on which all types of messages can be processed.


        Printer device driver
        Is there really no possibility of creating a fax with a printer device driver?


                 Yes, there is a possibility. On the Telesnap UMS-CD there are TIFF printer
        device drivers for 16 and 32bit in the \tools folder. These device drivers produce
        a TIFF file from the document to be printed. In the second step, the user must create a
        faxmail. The previously generated TIFF will be used as attachment to the faxmail.




VoiceAccess, Text To Speech

        Menu and TTS languages
        With Telesnap UMS, German and English have been installed automatically.
        However, in the \Telesnap UMS\voice directory there are many more languages.
        How can I activate them?


                                                                                         118(170)
                                                         Telesnap UMS – Technical Guide




            The other languages have been prepared there on purpose.
      Unfortunately Telesnap UMS activates just German and English
      activated in standard mode. To add other languages or to switch
      from German to English, several configurations have to be
      adjusted. In a service pack there is a tool available that can
      automate this procedure. Until this is available, SPEECH DESIGN
      should be consulted to obtain support for the adjustment.
      Additional languages (three or more languages active at the same
      time) are available at extra cost and need a separate licensing
      key.
      wrong system time, for example 8:00 a.m. The job will wait in the queue until 10:00
      a.m. (then it will be 9:00 a.m. on Telesnap UMS) and the sending will begin.
      If the Telesnap UMS system time were ahead, the sending would start immediately;
      i.e. the job would not be ignored because it is too old.




Messages

      Too many SMS notifications
      I like the possibility of receiving SMS notifications of
      incoming fax and voice-mails. However, I do not want to receive
      a SMS notification for every regular email. How can I separate
      them?


             They have already been separated automatically. The SMS
      notification refers only to messages received by Telesnap UMS
      anyway, i.e. fax and voice-mails. Email traffic does not run on
      Telesnap UMS but normally between mail server and ISP.


      Not enough SMS notifications
      The possibility of SMS notifications is restricted to new fax
      and voice-mails. I would like to receive a SMS note for certain
      emails too. Is this possible?


             Yes, with the rules assistant (Outlook) or an agent
      (Notes) or corresponding tools from other mail clients.




                                                                                   119(170)
                                                                    Telesnap UMS – Technical Guide




Appendix B: Tips & Tricks


Description
Entfernen des        Folgende Dateien müssen bearbeitet werden:
Eintrages:
                     'sendmailbody.txt' und 'msg_01.ini' und 'msg_02.ini' (zu finden im '\bin'
-Powered by          Verzeichnis)
TELESNAP - im
                     Einträge der Sektionen [thorgate_received_fax] und [thorgate_received_voice]
Fax-Mail
                     anpassen.
Faxen ohne           Parameter MailGate/"CoverTextLen" entsprechend setzen oder über
Deckblatt            Steuerparameter "%COVER=0" testen
Aktivieren von       Registry -> HKLM/SOFTWARE/Digitronic/THOR/MDB/INET dort dann DWORD
Debug                debug=2/3/4/5
Informationen für
IMAP Anbindung
Aktivieren von       Registry -> HKLM/SOFTWARE/Digitronic/THOR/odbc dort dann DWORD
Debug                debug=2/3/4/5
Informationen für
ODBC Anbindung
Aktivieren von       Registry -> HKLM/SOFTWARE/Digitronic/Attachment Converter/2.0 dort dann
Debug                DWORD DebugMode=2/3/4/5
Informationen für
ATTCONV
Exchange             SMTP Connector einrichten, Smarthost [IP des Telesnap UMS MTA],
Connector für        Adressraum andere -> FAX mit * und Kosten 1, im MTA (z.B. Mercury) dann
[FAX:xyz]            entsprechende Domäne behandeln, z.B. DM=pmums mit "Telesnap.de"
Exchange          SMTP Connector einrichten, Smarthost [IP des Telesnap UMS MTA],
Connector für     Adressraum SMTP mit fax.Telesnap.de und Kosten 1, im MTA (z.B. Mercury)
xyz@fax.Telesnap. dann entsprechende Domäne behandeln, z.B. DM=pmums mit "fax.Telesnap.de"
de
SMTP                 HKLM/Software/Digitronic/THOR/MDB/INET und dort "SMTPSender"="xyz"
Sendeadresse         (zusätzlich evtl. noch HKLM/Software/Digitronic/THOR/MDB und dort
ändern von           "SMTPReportSender"="abc")
"UMSGate" zu
"xyz"
"Rundmail-           HKLM/Software/Digitronic/THOR/Mailgate und dort DWORD mit
Handling"            "IgnoreByMsgID"=1
(mehrere
Faxnummern in
Adresse)
Alternative          der Registry Schalter thor\mailgate\ReplaceExtensions (string) kann verwendet
Dateitypen bei der   werden, um für Thorgateway einzustellen, dass z.B. die TIF Dateien als .FAX
Zustellung (nur      Dateien in die Postfächer zugestellt werden. Eintrag als Komma separierte Liste
Endung wird          mit Wertepaaren durch = getrennt, z.B. TIF=FAX,WAV=VOC

                                                                                                 120(170)
                                                                    Telesnap UMS – Technical Guide



angepasst!)
Verschiedene          Im UMSUser_View muss zusätzlich DialPrefix Feld definiert werden (z.B. gefüllt
Kennziffern pro       mit Teil der eigenen Nebenstelle), Zuordnung ODBC im Gateway sollte bereits
Benutzer vor          vorhanden sein.
Faxnummer stellen
                      Nur für externe Nummern ->
(Routing-
                      HKLM/Software/Digitronic/Thor/Mailgate/DialPrefixDigits=xy(DWORD)
Auswertung auf
CCM)
Empfänger-Name        FAX:0123667788/Hans_Meier/Firma_Müller
und -Firma in
Deckblatt
übernehmen
Telesnap UMS an       MWI nur über CAPI/ISDN möglich, hier ist Option "CAPI MWI" notwendig
Alcatel
                      XCAPI: IP-Adresse des H.323 Gateways in XCAPI eintragen, nicht IP-Adresse
                      der Anlage, ansonsten keine ausgehenden Anrufe möglich
                      XCAPI: evtl. "Overlap sending" in XCAPI Konfiguration deaktivieren
                      XCAPI: ggf. "NationalCallingPrefix" und "CompanyPrefix" in chnl.ini anpassen
                      (wenn interne Anrufer als extern signalisiert werden)
Telesnap UMS mit      Anpassungen am Notes-Server siehe Thor-Notes-Doku (Dll kopieren, Eintrag in
Notes-MDB- und        notes.ini)
ODBC-UDB-
                      Mail-Adresse z.B. "OU=ptest/O=Telesnap"
Anbindung
                      Mail-Server z.B. "NotesServer1/Telesnap"
                      Mail-Box z.B. "mail\ptest"
                      Mail-Passwort wird auf Mail-Adresse gemapt (Radio-Box im Telesnap UMS Profil
                      richtig setzen!)
                      Gateway Account muß "Person/Manager"-Rechte mit Löschen auf alle VA Boxen
                      haben
GSM Modem             INI File im Verzeichnis \bin\m20 muss den Namen des der Kanalnummer haben
Installation          (z.B. chnl05.ini).
                      In dieses File die Portnummer (COMPort) des GSM Modems eintragen.
                      INI aus V24 Verzeichnis kopieren und ggf. anpassen.
                      In der thor.ini im Abschnitt [SMS Providers] die Einträge 'smssrvprotocol' auf den
                      Wert 3 setzen
                      oder alle Provider im Telesnap UMS Setup auf Protokoll "GSM" konfigurieren
Testen des GSM        Hyperterminal über Software/Windows Komponenten/Zubehör/Kommunikation
Modems                installieren
                      Hyperterminal starten - Verbindung zum GSM Modem aufbauen
                      Folgende Befehle eingeben:
                      at (enter)
                      at+cpin? (enter)
                      at+cpin="PIN der SIM-Karte" (enter)
                      at + cmgf=0 (enter)
Datei-Schnittstelle   Verzeichnis "C:\PMUMS\Mailgate\senden"
ATX
                      PAR-Datei mit folgendem Inhalt:

                                                                                               121(170)
                                                                  Telesnap UMS – Technical Guide



                    @PHONE:0711906684134
                    @FILE:attach.doc
                    @DEL
                    @TSI:34
                    @RESULT: nolog, smtp_doc=steffen.schmoll@Telesnap.de, no_smtp_on_ok
                    Anhang ins selbe Verzeichnis kopieren
Redundanz           Control Server auf beiden Knoten des Clusters installieren, LineServer laufen
                    separat
                    Dann Clustergruppe einrichten (Dienste, Registry synchronisieren, File-System
                    redundant, ...)
                    Microsoft Cluster oder Legato Cluster
TTS Wörterbuch      kann unsinnige Passagen in Mails ersetzen
                    z.B. <HTML>usw.
BRI und PRI         jeweils Server Karten notwendig
                    zusätzlich "voll DSP bestückt"
Converter           Business/Graphics für Attachment Reading notwendig
                    Business Converter ist erste Stufe, für den Graphics Converter ist zusätzlicher
                    Aufpreis erforderlich
                    Graphics Converter macht zusätzlich noch PDF, PostScript, ...
ATT CONV Fehler     Zugriffs-Pfade zur attconv.exe in der Registry auf Doppel-Backslash überprüfen
                    und ggf. bereinigen
IMAP/SMTP mit       speziell kompilierte DLL (mdbimap.dll) muss verwendet werden, entsprechend
SSL                 die Datei durch Umbenennen aktivieren, zusätzlich Registry-Schalter:
                    [HKEY_LOCAL_MACHINE\SOFTWARE\digitronic\THOR\MDB\INET]
                    "UseSSL" (dword) = 1
Mehrere Mailserver IMAP Zugriff: über User Attribut "MailHost"
                    SMTP: "MX" SMTP Mode aktivieren (-> entsprechender zuständiger SMTP-Host
                    wird per Namensauflösung ermittelt, bei SMTP Host muss dann entsprechend
                    ein DNS Server eingetragen werden)
POP3, IMAP und      SMTP: 25, IMAP: 143, POP3: 110
SMTP Ports
ADS                 Über UDBADSI.dll und extensionAttributes möglich
Benutzerdaten
                    Parameter: LDAP://voip6:389/cn=users,dc=voip6,dc=telesnap,dc=com
                    Username: VOIP60\Administrator mit entsprechendem Passwort
                    Zuordnung dann ggf. über "EXT:xyz"
                    ExtensionAttribute-Konfiguration:
                    HKLM\\SOFTWARE\\DIGITRONIC\\THOR\\ADSI\\"ExtensionAttribute"=extension
                    Attribute7
Service Flag        nur Fax: 1
                    nur Voice: 2
                    Fax und Voice: 3


                                                                                             122(170)
                                                                    Telesnap UMS – Technical Guide



                     Unified Messaging: 7
                     Mobile Office: 166
ATT CONV             Konvertierung dauert zu lange - timeout ist die Folge.
                     Registry Key setzen:
                     HKEY_LOCAL_MACHINE
                     Software\\Digitronic\\Thor\\ThorATX
                     WaitForATTConv (DWORD) - Angabe in Milisek.
ATT CONV TEST        Attachment-Konverter über Kommandozeile aufrufen und Testfile konvertieren.
                     Befehl: attconv -Ic:\TestFile.doc -Oc:\TestFile.301 -D


This Tips & Tricks section is a subset of additional helpful configuration and testing hints, but doesn’t
cover all existing modules. Please refer also to the corrsponding sections in this document.




                                                                                               123(170)
                                                                   Telesnap UMS – Technical Guide




Appendix C: Lotus Notes




Telesnap UMS – Anpassungen für Lotus Notes

Die Telesnap UMS Funktionen können auch nahtlos in eine Lotus-Notes-Umgebung integriert werden.
Hier werden die Anpassungen im Telesnap UMS System und in Notes/Domino beschrieben.
Die Notes-Clients hingegen benötigen keine zusätzliche Software oder Konfiguration.

Voraussetzungen für Notes/Domino
Installierter Notes/Domino-Server, Version 4.5x, 4.6x, 5.x oder 6.02

Neuer Notes-Benutzer
Richten Sie einen neuen Notes- Benutzer (z.B. PMUMS) ein. Der Benutzername erscheint bei allen
Eingangsobjekten, die Telesnap UMS vermittelt (Fax- und Voicemails) als Absender. Dieses Konto
wird von Telesnap UMS Gateway benötigt um Nachrichten in das und aus dem Notes-System zu
übertragen.

Zugriffsrechte des neuen Notes-Benutzers
Der Telesnap UMS Line Manager arbeitet in Notes als normaler Notes-Benutzer. Zum Senden und
Empfangen reicht der Zugriff auf die persönliche Mail-Datenbank.
Bei Beginn einer VoiceAccess-Session meldet sich der Telesnap UMS Line Manager unter
Verwendung der Notes-C++ API bei Notes an. Wenn der VoiceAccess-Benutzer seine Zugangsdaten
eingegeben hat, versucht der Telesnap UMS Line Manager auf die Mail-Datenbank des Benutzers
zuzugreifen, um ihm seine Nachrichten und, falls gewünscht, seine aktuellen Termine anzubieten.
Dazu benötigt er das Zugriffsrecht ("Person/Manager") auf alle Mail-Datenbanken der anderen
Telesnap UMS Benutzer – entweder aufgrund der Eigenschaft als Administrator oder durch explizite
Rechtevergabe durch den Notes-Administrator über die ACL (Access Control List).

Neue Fremde Domäne (Foreign Domain)
Um den Notes-Benutzern eine einfache Adressierung ihrer zu sendenden Telesnap UMS Nachrichten
zu ermöglichen, wird eine Fremde Domäne (Foreign Domain) erzeugt. Der Name der Domäne sollte
z.B. „PMUMS“ oder „UMS“ oder „FAX“ sein.
Mit Beispiel „PMUMS“ ist damit ein Faxversand durch die Adressierung an „04012345678@pmums“
möglich.
Als Mail-Datenbank der Fremden Domäne muss die persönliche Mail-Datenbank des neuen
Benutzers angegeben werden, der eben eingerichtet wurde.
Dadurch gelangen alle Mails, die an die Domäne „PMUMS“ adressiert wurden, in das persönliche
Postfach von Telesnap UMS Gateway. Ab dieser Stelle beginnt dann die Verarbeitung des
Sendeauftrags durch Telesnap UMS.

                                                                                         124(170)
                                                                   Telesnap UMS – Technical Guide



Installation eines Notes-Clients
Zwei Telesnap UMS Module können mit Notes kommunizieren:
           •   Telesnap UMS Gateway         Sendeaufträge erstellen, Eingangsvermittlung
           •   Telesnap UMS Line Manager        VoiceAccess
Auf allen Telesnap UMS Servern, auf denen diese Dienste laufen, muss ein Standard-Notes-Client
installiert werden. Die Notes-API setzt auf diesen Notes-Client auf.
Der Notes-Client kann mit (Lotus Notes Single Logon) oder ohne Verbindung mit einem NT-Konto
installiert werden. Es wird empfohlen, ohne Verknüpfung mit einer NT-Anmeldung zu installieren.



     Stellen Sie durch Tests unbedingt den fehlerfreien „normalen“ Mailversand und -empfang
mit dem Notes-Client sicher, bevor Telesnap UMS die Kommunikation mit dem Client
aufnimmt.

Installation von Telesnap UMS Gateway
Meist wird Telesnap UMS Gateway mit auf dem Telesnap UMS Server ablaufen. Dann ist die
Installation des Gateways bereits durch die Installation der Telesnap UMS Kernelmodule erledigt.
Wenn ein dedizierter Gateway-Server vorgesehen wird, muss er entsprechend den Hinweisen aus
dem Kapitel Installation/Konfiguration installiert werden.
Im Ordner \PMUMS\bin sind danach die folgenden Notes-spezifischen Dateien vorhanden:


               XDBnotes.dll           alle Datenbanktypen (mail, user, adress, kalender) sind mit
                                      dieser dll implementiert
               lcppn201.dll           Lotus C++ Notes API
               nextpwd.dll            Passworteingabe durch externe Programme
               fax.bmp                Fax-Icon für Faxmails
               phone.bmp              Telefon-Icon für Voicemails

Anpassungen
           1. Die Datei nextpwd.dll in den Notes-Ordner kopieren.
           2. Das Notes-User-Passwort muss durch externe Programme (hier Telesnap UMS Line
              Manager) gesetzt werden können. Dazu muss in der Datei notes.ini im Abschnitt
              [Notes] die Zeile extmgr_addins=extpwd
              eingefügt werden.
           3. Die Umgebungsvariable PATH um den Pfad zum Notes-Ordner erweitern (wurde bei
              älteren Notes-Versionen durch die Notes-Client-Installation gesetzt – zumindest bei
              der Version 5.0.x aber nicht mehr)

Konten der Telesnap UMS Module
Wenn Sie (wie empfohlen) den Notes-Client ohne Lotus Notes Single Logon, d.h. ohne Verbindung
mit einem NT-Konto installiert haben, dann braucht das aktuelle Konto der Dienste nicht geändert zu
werden. Die NT-Anmeldung hat dann keine Bedeutung für die Verbindung mit Notes.



Telesnap UMS – Konfiguration für Lotus Notes
Gateway Konfiguration mit Telesnap UMS Setup
Hier werden die Informationen zur Notes-Datenbank konkretisiert.
                                                                                            125(170)
                                                                Telesnap UMS – Technical Guide




Mail System
Hier ist Lotus Notes/Domino zu wählen.
User Database
Bei der Anbindung an Lotus Notes wird auch hier bevorzugt die ODBC-Datenbank-Verbindung zur
Snapware Benutzerdatenbank unterstützt. Näheres hierzu in den entsprechenden Kapiteln.
Notes Password
Hier wird das Kennwort für die Notes-Client-Anmeldung eingetragen.
Retype Password
Wiederholung zur Kontrolle. Die Übereinstimmung wird erst bei Klick auf Übernehmen geprüft und ggf.
gefordert.
Foreign Domain
Name der Fremden Domäne (Foreign Domain), die eingerichtet wurde.
Notes Server
Maschinenname des Notes-Servers, auf dem die Fremde Domäne eingerichtet ist.
Telesnap UMS Mailbox
Name des neuen Notes-Benutzers für Telesnap UMS Gateway. Er wird für das Weiterleiten an
Faxziele im VoiceAccess gebraucht.
                                                                                       126(170)
                                                                 Telesnap UMS – Technical Guide



Default Receiver
Name des Notes-Benutzers, der alle nicht automatisch vermittelbaren Thor-Nachrichten bekommt.
Diese muss er dann manuell verteilen.
Der Name muss in der Form CN=Vorname Nachname/O=Organisation eingegeben werden.

Benutzer Konfiguration im WebAdmin
Im jeweiligen Benutzer müssen folgende Werte konfiguriert werden :
   •   Mail-Adresse im Format "OU=ptest/O=Telesnap"
   •   Mail-Box im Format "mail\ptest"
   •   Mail-Passwort muss nicht eingetragen werden!
Im Telesnap UMS Profil sind folgende Einstellungen notwendig :
   •   „Mail access over“ auf Notes API einstellen
   •   Mail-Server im Format "NotesServer1/Telesnap"




                                                                                        127(170)
                                                                    Telesnap UMS – Technical Guide




Appendix D: Dictionaries


Dictionaries content all “exceptions” for TTS-engines that should be pronounced different from normal
manner-of-speaking. All dictionaries are text-files and must be located in the sub-directory Telesnap
UMS\VOICE\DIC\.




Scansoft-TTS
Scansoft-Speaker uses a dictionary whose name derives from the language and the ending DCT.
Consecutively a short description of the body of a Scansoft-dictionary:




Provided dictionaries

As a standard Telesnap UMS is delivered with two dictionaries (German and English). The appropriate
files are german.dct and ang.dct. Each dictionary consists of a HEADER-part and a DATA-section.




HEADER-Section
The Header-Part contains general information about the dictionary and has the following form:


[Header]
Dictionary Name=German Dictionary
Language=German
Data Type=ANSI
Algorithm=
Date=Thu May 10 20:17:08 2001
Description=German Dictionary
This part must not be changed.




                                                                                             128(170)
                                                                      Telesnap UMS – Technical Guide




Data-Section

The Data-section contains the real exceptions and has the following form:


<exception-word> <TAB>                     <New manner-of-speaking>
Msg                               Yours sincerely
Etc                               and so on
Email                             …


Here you can add further exceptions to enlarge the dictionary.



Eloquent-TTS

From Telesnap UMS Scansoft is the standard TTS-engine. For reasons of compatibility to previous
Telesnap UMS-versions and updates we still refer to the old TTS-engine at this point. Each eloquent-
speaker always uses three dictionaries belonging together, whose name is derived from the value of
dictionary. Subsequently you find a short description of the single dictionaries.


Delivered Dictionaries
Telesnap UMS is delivered with two sets of dictionaries (German and English). The appropriate files
are xxxabbr.dic , xxxmain.dic and xxxroot.dic, whereby xxx represents the language. Each dictionary
describes an exception per line in the form:


<exception word>          <TAB>            <New manner-of-speaking like e.g. >
Msg                                        Yours sincerely
Etc                                        and so on


Root-dictionary (xxxROOT.DIC)
Use a root-dictionary for substantives, verbs, adjectives and proper names. The root-dictionary
distinguishes oneself that you just have to enter the root-word of a word. All other forms of the word
are pronounced automatically. The root-dictionary doesn’t differentiate between upper and lower case.
If you enter a root-word using small letters it’s found anyway by the guidelines and pronounced if it
starts with a capital letter at the beginning of a sentence. Examples for the root-dictionary:


Search item     Realization       is applied
Two             tu                two, two hundred, two times, two sides
Style           [steil]           style, styles, style art, stylish


                                                                                             129(170)
                                                                        Telesnap UMS – Technical Guide




Exceptions-dictionary (xxxMAIN.DIC)

The most important performance feature of the exception dictionary is the fact that it my consist of an
arbitrary string. The exception-dictionary differs between upper and lower case. So if you entered the
search item “THE” to the conversion to “German Dictionary” the uncapitalized “the” will be pronounced
as expected.


Serach item      Realisation
Kbit/ s          kilobit per second
GB               Great Britain and Northern Ireland
A1               first-class




Abbreviation-Dictionary (xxx.ABBR.DIC)

The Abbreviation-dictionary is used for abbreviations (with as well as without points) which do not
need a control demand with the implementation. The Abbreviation-dictionary differs between upper
and lower case. If you enter the search item “sun” for transformation in “Sunday” the uncapitalised “so”
will be pronounced as you expect.
The following aspect needn’t to be specified (like e.g. “Dr.”). The dictionary’s search routine locates
the abbreviation according to the specifications and will pronounce it like that. It doesn’t matter if a full
stop is listed or not. If an abbreviation is to be pronounced as an abbreviation as well - if a full stop
follows – the full stop must be entered with the search item. Examples for the Abbreviation dictionary:


Search item               transformation
M.A.                      Magister Artium
Ref




                                                                                                    130(170)
                                                 Telesnap UMS – Technical Guide




Appendix E: Attachment Converter


The Attachment Converter is available in three versions: Light, Business
and Graphics. It is used to change the faxmail attachments into faxes.



Operating mode

Light version
During Telesnap UMS installation the Attachment Converter version could be
selected. The Light version is the default. This version does not need a
licensing code.
However, the Light version is not able to convert independently. It always
needs the desired original applications – most of the time this is MS
Office.
The Adobe PDF format can be cast if the Adobe Acrobat Reader has been
installed. This freeware is contained on the Telesnap UMS-CD in the
\tools\Acrobat file. The following formats can be processed with the Light
version of the Attachment Converter:


           MS Word
           MS Excel
           MS PowerPoint
           Adobe PDF
           MS WordPad
           MS Write
           TIFF
           ASCII-Text
The default configuration corresponds exactly to this list.


If it is desired that additional formats be sent as a fax, a version of the
Attachment Converter that requires a license, or a TIFF printer device
driver at every (!) workplace, must be installed. With the help of this
printer device driver, the user can generate a TIFF document from every
application by using the command print, which can then be sent as a fax
mail attachment.
With this, the conversion has been transferred from the server to the user
PC. The price for this is the high installation expense necessary for each
user-PC involved.
Printer device drivers for Windows 2000 and Windows 95/98 can be found on
the Telesnap UMS-CD in the \tools\TIFDrvnn file.

                                                                       131(170)
                                                                  Telesnap UMS – Technical Guide



However, it is recommended to install another version of the Attachment
Converter rather than the printer device driver in Telesnap UMS.




Business - and Graphics - version
These Attachment Converters offer essential advantages for the user as well
as the administrator:
                1. No installation of additional software on the Client.
                2. No maintenance work on the Client for software updates.
                3. Uniform operation mode when sending emails and faxes
                   documents. The instruction send is always used. The mail and
                   fax recipients can be mixed in one distribution list.
When using a printer device driver for fax sending, the user must consider
beforehand how he/she wants to send the document. In a mixed sending to a
mail and a fax recipient, two working operations would be required.
The Attachment Converter in the Business- and Graphics version enables the
sending of almost any word processing-, spreadsheet analysis- and graphics
documents. In this way, mail enclosures (attachments) are converted into
the fax format and sent directly on the Telesnap UMS server. For operating
these Attachment Converters, a licensing code is necessary which can be obtained at a dealer.




Configuration
Instructions on the basic settings of the Attachment Converter can be found in the
chapter Installation/configuration, section configuration with Telesnap UMS Setup.



Supported file formats
As already mentioned, the Light version only offers the possibility of a
shell-conversion through other applications.
The versions Business and Graphics offer several routines of their own
which can work independently. Here is an outline:



Filters (Alphabetical by Filter Name)

ACS           Microsoft Access 1.0, Microsoft Access 2.0

AMI           Ami Pro, Ami, Professional Write Plus

              Microsoft Office Binder 7.0, Microsoft Office Binder 97 (conversion of files contained
BDR
              in the Binder file is supported only on Windows)

              Windows Bitmap, Windows Bitmap 98/2000, OS/2 Bitmap, OS/2 Warp Bitmap,
BMP
              Windows Cursor, Windows Icon, Corel Draw 2.0 - 9.0

CGM           Computer Graphics Metafile

DBS           DBase III, DBase IV, DBase V


                                                                                            132(170)
                                                               Telesnap UMS – Technical Guide



DEZ         DataEase 4.x

DIF         Navy DIF

DRW         Micrografx Drawing Products

DX          DEC DX 3.0 and DEC DX 3.1

EMF         Enhanced Windows Metafile

EN4         Enable Word Processor 4.x

ENS         Enable Spreadsheet

ENW         Enable Word Processor 3.0

ESHR        Escher internal Microsoft Office graphics format

EXE2        DOS Executable, Windows Executable or DLL

FAX         CCITT Group 3 Fax

FCD         First Choice DB

FCS         First Choice SS

FFT         IBM DCA/FFT

            Freelance 1.0 & 2.0 for OS/2, Freelance 1.0 & 2.0 for Windows, Freelance 96 for
FLW         Windows 95, Freelance 97 for Windows 95, Freelance for SmartSuite Millennium
            Edition, Freelance for SmartSuite Millennium Edition 9.6

FWK         Framework III

GDSF        Interface for *.FLT filters

GIF         CompuServe GIF

GZIP        UNIX GZip

            Harvard Graphics DOS 3.0 Chart, Harvard Graphics DOS 2.0 Chart, Harvard Graphics
HGS
            DOS 3.0 Presentation

HTML        Internet HyperText Markup Language (up to 3.0 with some limitations)

HWP         Hangul 97

HWP2        Hangul 2002

IBFPX2.FLT Kodak Flash Pix

IBGP42.FLT CALS Raster

IBJPG2.FLT Progressive JPEG

IBPCD2.FLT Kodak Photo CD

IBXBM2.FLT X-Windows Bitmap

IBXPM2.FLT X-Windows Pixmap

IBXWD2.FLT X-Windows Dump

                                                                                         133(170)
                                                          Telesnap UMS – Technical Guide



ICH    Ichitaro versions 8.x through 13.x and 2004

ICH6   Ichitaro versions 4.x through 6.x

IMG    GEM Image (Bitmap)

IWP    Wang IWP

JBG2   JBIG2 graphic embeddings in PDF files

JW     JustWrite 1.0, JustWrite 2.0, Q&A Write 3

LEG    Legacy, Wordstar for Windows

       For Win32 platforms only, and only supporting text extraction/viewing. Lotus
LWP    WordPro 96, Lotus WordPro 97, Lotus WordPro for SmartSuite Millennium Edition,
       Lotus WordPro for SmartSuite Millennium Edition 9.6

       For non-Win32 platforms only, and only supporting text extraction/viewing. Lotus
LWP7   WordPro 97, Lotus WordPro for SmartSuite for the Millennium, Lotus WordPro for
       SmartSuite Millennium Edition 9.6

LZH    LZH Compress, LZA Self Extracting Compress

M11    Mass 11

MANU   Lotus Manuscript 1.0, Lotus Manuscript 2.0

MCW    MacWrite II

       FrameMaker MIF versions 3.0, 4.0, 5.0, 5.5 and 6.0 and Japanese 3.0, 4.0, 5.0 and
MIF
       6.0 (text only)

       MIME-encoded mail messages(See “MIME Support Notes” later in this appendix for
MIME
       detailed information about MIME support.)

MM     MultiMate 3.6, MultiMate Advantage 2

MM4    MultiMate 4.0

MMFN   MultiMate Note

MP     Multiplan 4

MPP    Microsoft Project versions 98 - 2003 (text only)

       Microsoft Outlook Message and Microsoft Outlook Form Template versions 97, 98,
MSG
       2000, 2002 and 2003

MSW    Microsoft Word 4.x, Microsoft Word 5.x, Microsoft Word 6.x, Windows Write

MWKD   Mac Works 2.0 Database

MWKS   Mac Works 2.0 Spreadsheet

MWP2   Mac WordPerfect 2.0, Mac WordPerfect 3.0

MWPF   Mac WordPerfect 1.x

MWRK   Mac Works 2.0 WP

OW     OfficeWriter

                                                                                    134(170)
                                                            Telesnap UMS – Technical Guide



PBM    PBM (Portable Bitmap), PGM (Portable Graymap), PPM (Portable Pixmap)

PCL    PC File 5.0 Doc

PCX    Paintbrush, DCX (multi-page PCX)

PDX    Paradox 2 & 3, Paradox 3.5, Paradox 4, Paradox for Windows

       PFS: Write A, PFS: Write B, Professional Write 1, Professional Write 2, IBM Writing
PFS
       Assistant, First Choice word processor, First Choice 3 word processor

PGL    HP Graphics Language

PIC    Lotus PIC

PICT   Macintosh PICT, Macintosh PICT2

PNG    Portable Network Graphics

PNTG   MacPaint

       Microsoft PowerPoint 3.0 for Windows, PowerPoint 4.0 for Windows, PowerPoint 4.0
PP2
       for the Mac

PP7    Microsoft PowerPoint 7.0 for Windows 95

       Includes Presentation (PPT) and Slideshow (PPS) support. Microsoft PowerPoint 97,
       Microsoft PowerPoint Dual 95/97, PowerPoint 98 for the Mac, PowerPoint 2000,
PP97
       PowerPoint 2001 for the Mac, PowerPoint 2002 (XP), PowerPoint 2003, PowerPoint
       2004 for the Mac, and PowerPoint v.X for the Mac

PPL    PFS: Plan

PSP6   For Windows platforms only. Paint Shop Pro 5.0-6.0

       Microsoft Outlook Folder and Microsoft Outlook Offline Folder files versions 97, 98,
PST
       2000, 2002 and 2003

QA     Q&A Write

QAD    Q&A Database

QP6    Quattro Pro 5.0 - 8.0

QP9    QuattroPro 9.0 - 12.0 (text only)

RAS    Sun Raster

RBS    R:Base System V, R:Base 5000

RFT    IBM DCA/RFT

RFX    Reflex

RTF    Rich Text Format

SAM    Samna

SC5    SuperCalc 5

SDW    Ami Draw


                                                                                       135(170)
                                                              Telesnap UMS – Technical Guide



SHW3   Novell Presentations 3.0, Novell Presentations 7.0, Corel Presentations 8.0 - 12.0

SMD    Smart DataBase

SMS    Smart Spreadsheet

SMT    SmartWare II

SNAP   Lotus Snapshot

       StarOffice 6.x through 8.x, and OpenOffice 1.1 and 2.0 (Writer is fully supported, Draw
SO6
       and Calc are text only)

SOC    StarOffice Calc 5.2 (text only)

SOI    StarOffice Impress 5.2 (text only)

SOI6   StarOffice Impress 6.x, 7.x and 8.x and Open Office 1.1 and 2.0

SOW    StarOffice Writer 5.2 (text only)

SPT    Sprint

SWF    Macromedia Flash 6.x, Macromedia Flash 7.x, and Macromedia Flash Lite (text only)

TAZ    UNIX compress, UNIX tar

       Text - DOS character set, Text - ANSI character set, Text - Macintosh character set,
       Text - Unicode character set, Text - UTF-8, Text - EBCDIC.
TEXT   This filter outputs otherwise unidentified files to a user-defined text character set. See
       SCCID_FALLBACKFORMAT for more information about what is available and how to
       change the character set.

TGA    Truevision TGA (TARGA)

       Tagged Image File Format, EPS (TIFF header only), CCITT Group 3 Fax, CCITT
TIF6
       Group 4 Fax, JPEG, JFIF (JPEG not in TIFF format)

TW     Total Word

TXT    IBM DisplayWrite 2 or 3, IBM DisplayWrite 4, IBM DisplayWrite 5

VCRD   vCard, vCalendar

VISO   Visio 4 - Page Preview mode only (WMF/EMF), Visio 5, 2000, 2002 and 2003

VW3    Volkswriter

       Microsoft Word 6.0 for Windows, Microsoft Word 7.0 for Windows 95, Microsoft
W6
       WordPad

       Microsoft Word 97, Word 98 for the Mac, Word 98-J, Word 2000, Word 2001 for the
W97
       Mac, Word 2002 (XP), Word 2003, Word 2004 for the Mac, and Word v.X for the Mac

WBMP   WBMP wireless graphics format

WG2    Lotus 123 for OS/2 release 2

WK4    Lotus 1-2-3 3.0, Lotus 1-2-3 4.0, Lotus 1-2-3 5.0

WK6    Lotus 1-2-3 for SmartSuite 97, Lotus 1-2-3 for SmartSuite Millennium Edition, Lotus 1-

                                                                                          136(170)
                                                             Telesnap UMS – Technical Guide



       2-3 for SmartSuite Millennium Edition 9.6

       Lotus 1-2-3 1.0, Lotus 1-2-3 2.0, Symphony, Microsoft Works SS, Microsoft Works DB,
WKS    VP-Planner, Mosaic Twin, Quattro (DOS), Quattro Pro (DOS), Generic WKS, Windows
       Works Spreadsheet, Windows Works Database

WM     WordMarc

WMF    Windows Metafile

WML    Wireless Markup Language

       Word for Windows 1.x, Word for Windows 2.0, Word for Macintosh 4.0, Word for
WORD
       Macintosh 5.0

       Microsoft Works DOS 1.0 WP, Microsoft Works DOS 2.0 WP, Microsoft Works Win 3.0
WORK
       WP, Microsoft Works Win 4.0 WP

WP5    WordPerfect 5.x

WP6    WordPerfect 6.0 - 12.0

WPF    WordPerfect 4.2

WPG    WordPerfect Graphic 1.0

WPG2   WordPerfect Graphic 2.0

WPL    Dec WPS Plus 4.1

       Novell PerfectWorks 2.0 word processor, Novell PerfectWorks 2.0 draw, Novell
WPW
       PerfectWorks 2.0 spreadsheet

WS     Wordstar 3.0, Wordstar 4.0, Wordstar 5.0, Wordstar 6.0, Wordstar 7.0

WS2    Wordstar 2000

       Microsoft Excel 2.x, Excel 3.0, Excel 4.0, Excel 5.0, Excel 7.0, Excel 97, Excel 98 for
       the Mac, Excel 2000, Excel 2001 for the Mac, Excel 2002 (XP), Excel 2003, Excel
XL5
       2004 for the Mac, v.X for the Mac, Excel 2.x Chart, Excel 3.0 Chart, Excel 4.0 Chart,
       Excel 5.0 Chart, Excel 7.0 Chart

XML    XML (text only)

XY     XyWrite / Nota Bene, Signature

YIM    Yahoo! Instant Messenger 6.x and 7.x

ZIP    PKZIP format, self-extracting .exe




                                                                                        137(170)
                                                            Telesnap UMS – Technical Guide



Premier Graphics Filters

ACAD            AutoCAD Drawing Versions 2.5 - 2.6, 9.0 - 14.0, 2000i and 2002
IBPSD2.FLT      All versions
IMCDR2.FLT
IMCD32.FLT
IMCD42.FLT
IMCD52.FLT      Corel Draw Versions 3, 4, 5, 6, 7, 8
IMCD62.FLT
IMCD72.FLT
IMCD82.FLT
IMCMX2.FLT
IMCM52.FLT      Corel Draw Clipart
IMCM72.FLT
IMDSF2.FLT      Micrografx Designer Version 6
IMFMV2.FLT      FrameMaker Vector and Raster Graphics (FMV)
IMGDF2.FLT      IBM Graphics Data Format (GDF)
IMGEM2.FLT      Gem File (Vector)
IMIGS2.FLT      IGES Drawing
IMMET2.FLT      OS/2 PM Metafile
IMPIF2.FLT      IBM Picture Interchange Format
IMPS_2.FLT
IMPSZ2.FLT      Postscript (Levels 1-2) and EPS files
IMPSI2.FLT
IMRND2.FLT      AutoShade Rendering
IPHGW2.FLT      Harvard Graphics for Windows
PDF             PDF versions 1.0 - 1.6 (including Japanese PDF) and Adobe Illustrator
PDFI            versions 7.0 and 9.0




                                                                                    138(170)
                                                                   Telesnap UMS – Technical Guide




Tips and tricks Attachment Converter

MS Office
The Attachment Converter (not Light) usually supports the conversion of Microsoft Office documents
(Word, Excel and Power Point). However, not all functions in the standard range of Word (for example
Word frames, Word autotext, macros, etc.) will be supported. If such functions are used, MS Office
must be installed on the NT machine where the converter is running. Office can be installed before or
after the installation of the Attachment Converter.


     ATTENTION: Office must be installed under the same login account used for
Telesnap UMS Autotext. After successful installation, all Office
applications should be restarted and the requested user settings should be
made.
        To activate the shell-conversion, i.e. the conversion with Office,
        the extensions of the Office files must be entered in Telesnap UMS
        Setup, register attachments.
After this, the Attachment Converter uses the associated applications and no longer its own
routines for this type of file.


Office password protection and macros
The Attachment Converter monitors the execution of subordinate processes, i.e. Word. If there is no
notification until a timeout (standard=3 minutes), the process will be ended by the Attachment
Converter.
This behavior typically occurs during the processing of keyword protected Office files. Word (for
example) requests the keyword but there is no one to enter it – the timeout takes effect. Connections
in documents that cannot be resolved can also lead to an abnormal termination. The application will
be terminated and the sender receives the negative receipt, “error during conversion of attachments”.
Therefore, please ensure that no Office documents with keyword protection or interactive macros are
sent.


Macros in normal.dot
When calling up the Attachment Converter the message „ambiguous ole.tmp“ appears.
Solution: The standard document template normal.dot contains functions or macros
that do not belong there, i.e. macro viruses.
After deleting the file, all functions can be used again.


Macro viruses
Telesnap UMS can spread no macro viruses. Telesnap UMS only receives documents
from Telesnap UMS users (and can therefore be infected itself). Only TIFF
and wave files are forwarded inward (to the users). Only analogue messages
(faxes, speech) are given outward. The digital exceptions are SMS messages
(not critical).
Altogether no danger potential can be recognized here.


                                                                                             139(170)
                                                                   Telesnap UMS – Technical Guide




Fonts
All types of fonts supposed to appear on the faxes must be installed locally on Telesnap UMS. If users
choose fonts that are unknown to Telesnap UMS, known fonts will replace them.


Test
To test the correct operation mode of the Attachment Converters, an Office file can be
copied into the folder \Telesnap UMS\attconv and the converter can be called up:
                attconv -iOffice-filename -oc:\test.301
Afterwards, the corresponding Office application must be started
automatically and the document converted into a fax. The produced fax pages
then can be checked as files c:\test.3xx. If no files have been produced,
the converter has not been installed correctly.
       It is advisable to check that Office is functioning faultlessly
       (double click on source file) and that the printer device driver
       digitronic FaxMail is working correctly and is the standard printer.
The debug mode can be activated with the parameter -d
                attconv -iOffice-filename -oc:\test.301 -d
The debug protocol can be found in \Telesnap UMS\attconv\mydebug.txt


Adobe PDF
The Attachment Converter can use the Acrobat Reader for the conversion of
Adobe PDF files. However, after the installation this reader has one
peculiarity that could cause problems when using the Attachment Converter.
After installing the Acrobat Reader, it is imperative that it is started
again to acknowledge the licensing conditions.
When the Attachment Converter calls up the Acrobat Reader as a sub-process,
the PDF document will be correctly converted but the process does not
terminate. Therefore, the Attachment Converter still has to wait for the
timeout and then terminate the process. The conversion will then be
recognized but this could possibly take a very long time. Therefore, it is
advisable to use the following trick. With this, the PDF conversions will
work smoothly.
Open registry: HKEY_CLASSES_ROOT\.pdf
Read the character string (standard): regularly AcroExch.Document
Delete or rename key HKEY_CLASSES_ROOT\AcroExch.Document\shell\print
Delete or rename key HKEY_CLASSES_ROOT\AcroExch.Document\shell\printto\ddeexec
Key HKEY_CLASSES_ROOT\AcroExch.Document\shell\printto\command:
process character string (standard):
before something like "C:\Programme\Adobe\Acrobat 4.0\Reader\AcroRd32.exe"
could be found. Add /t "%1“ "%2“ "%3“ "%4“:
after that it reads
"C:\Programme\Adobe\Acrobat 4.0\Reader\AcroRd32.exe" /t "%1" "%2" "%3" "%4"
Now the PDF reader should be started correctly and terminate itself after
the work has been done.




                                                                                             140(170)
                                                                  Telesnap UMS – Technical Guide




Rich Text (RTF)
If an optimal conversion of RTF documents with page layout support is desired, this conversion must
be done in Microsoft Word (as a shell-conversion). For this, a few changes in the registry are
necessary:
In HKEY_CLASSES_ROOT\.rtf there will be Word.RTF.8 as a standard. Here the same value as
for HKEY_CLASSES_ROOT\.doc must be entered, i.e. usually Word.Document.8
       In Word under extras options general, the button confirm conversion during opening
       must be activated.




                                                                                            141(170)
                                                                      Telesnap UMS – Technical Guide




Appendix F: Front page editor


Front pages are used when a user sends a simple text mail to a fax address with his Mail-Client. It is
not a question of a front page in front of the actual content but a form, which can be completed, with
the content of the text mail.
The content can exceed the space of a page, and then continuation pages will be produced.
There are always two description files for a „front page“. The first one for the first page which also
contains a head with sender and address information, and the second one for all following pages.



Outline
All Telesnap UMS gateways prompt Telesnap UMS Autotext to call up the front page generator to
generate dynamic and individual fax front pages.
The front page generator creates a fax document from a front page description file. Prerequisite for the
use of the front page generator is an Attachment Converter. The Light version, which is always
contained in Telesnap UMS, is sufficient.
The relevant description files and the front page editor can be found in the \Telesnap
UMS\mailgate\cover folder of the computer, which executes Telesnap UMS Autotext.
The standard front page, which is activated at the beginning, is called
default.cvr/default.cv1. This file is also the standard setting of the
gateway. This front page layout contains the most customary data fields. A
list of all supported front page fields of all gateways can be found below.
To create an individual front page, copies of default.cvr/default.cv1
should be used and processed.



Front page description file
The structure of these files is similar to that of a Windows configuration
file (INI file). The single paragraphs in the file describe the objects or
variables of the document. With the keys, values are put on the objects‘
attributes.
                [VAR1]
                attr1=valuea
                attr2=valueb
                [VAR2]
                attr1=valuec


General attributes
TYPE=Text or Bitmap
The given file will be interpreted as a bitmap or text file. Default=Text
FILE=filename of a bitmap or text file


                                                                                                 142(170)
                                                                        Telesnap UMS – Technical Guide



RECT=x_left, y_above, x_right, y_bottom
These values define a rectangle in which texts and images can be displayed.
The A4 sheet has the coordinates 0,0 in the above left and at the bottom
right 10000,10000. Default=0,0,0,0


Text attributes
FONT=font attributes, font size
Example: Arial bold italic, 20                      Default: Times New Roman, 10
STYLE=R or L or C
Alignment of the text flush right, flush left or centered. Default=L
TEXT=example text
Text that should be displayed
TEXTEX=example text
This text should be displayed in several lines (as a list). A special character string in each case will
mark the end of the line.
DELIMITER=example text
Text with which the end of a line (of a list) is marked. Default=Tabulator
MAXLIST=n
Maximum number of lines which are supposed to be displayed (with list). Default=2
LISTENDTEXT=example text
Text which appears in the last line of a list if the list is longer than
MAXLIST is. Default=...


INCLUDE
The keyword INCLUDE takes an exceptional position where another front page description file can be
included. The attribute FILE enters the file name.
Repetitions of definitions overwrite the previous entry, i.e. the last
definition always takes effect.


The following pages
If the text of a mail is longer than the space for the notefield, the reaction can be controlled by the
attribute TEXT:
If this attribute contains the value ONFAIL_FAIL an error will be sent
back. The value ONFAIL_NEXTPAGE effects that follow pages will be
generated. The total number of pages for a fax can be limited through the
parent process (Telesnap UMS Autotext).
For the second and all other pages a template with the ending cv1 is
needed. The meincover.cv1 belongs in the same folder as a meincover.cvr.
If the attribute TEXT contains a different value, then this is displayed as a text in front of the note text.




                                                                                                    143(170)
                                                                      Telesnap UMS – Technical Guide




Front page selection
All usable front page templates can be found in the \Telesnap UMS\mailgate\cover folder
of the computer that carries out Telesnap UMS Autotext.


     ATTENTION: Only an existing front page is entered at the mailgateway.
If an expected front page description file is missing, the fax will not be
created, and the sender receives a negative receipt: Error during front
page generation.


Global front page
default.cvr will be used as a global template per default. If another one is
desired, the selection can be made at the Exchange Connector or in Telesnap
UMS Setup (for Telesnap UMS Gateway). All available front pages are provided
there in a list.


Individual front pages per user
Usually the set global front page is always used. However, it is also possible to allocate a personal
front page to every Telesnap UMS user.
If it is desired to allocate a personal front page to a user, the name of the front page description file
(without ending .cvr) must be given in the user administration. Naturally, the
file (and the .cv1) must also exist.




                                                                                                 144(170)
                                                                    Telesnap UMS – Technical Guide




Variables for Telesnap UMS Gateway
The following outline shows the variables, which the gateway has in store for the generation of a front
page. All these fields can be encompassed into the front page template.


Sender data
The gateway gains the sender data from the applied database as long as the request has been
activated.


                Variable             Type        Meaning
                SFULLNAME            TEXT        name of sender
                SMAILADDR            TEXT        SMTP address
In addition, the global company data from the basic settings are used:
                SCOMPANY_NAME TEXT Company
                SCOMPANY_STREET TEXT             address1
                SCOMPANY_CITY        TEXT        address2
                SCOMPANY_PHONE TEXT              global company telephone number
                SCOMPANY_FAX         TEXT        global company fax number
The following field is additionally available when using the ODBC database:
                SDEPARTMENT          TEXT        department


Recipient data
                Variable             Type        Meaning
                RNAME                TEXT        name of the recipient
                RCOMPANY             TEXT        company
                RDEPARTMENT          TEXT        department
                RFAXNUMBER           TEXT        fax number


Additional data
                Variable             Type        Meaning
                SUBJECT              TEXT        subject
                PAGES                TEXT        number of attached pages
                ALLPAGES             TEXT        number of all pages incl. cover sheet pages
                DATE                 TEXT        date (dd.mm.yyyy)
                TIME                 TEXT        time (hh:mm)
                DATETIME             TEXT        date time


                                                                                               145(170)
                                                                      Telesnap UMS – Technical Guide




Variables for Exchange Connector

Sender data
The Exchange gateway gains the sender data from the individual data of the sender (Exchange-
Administrator / recipient). If no fields can be found, the global cover sheet data of the fax-connector
will be used (Exchange-Administrator, options page 1).
                Variable              Type        Meaning
                SNAME                 TEXT        name of the sender
                SCOMPANY TEXT Company
                SDEPARTMENT           TEXT        department
                SOFFICE               TEXT        office
                SASSISTANT            TEXT        assistant
                SSTREET               TEXTEX      address (multiple-lined, postbox, street etc.)
                SCITY                 TEXT        ZIP code and city
                SPHONE                TEXT        telephone
                SFAXNUMBER            TEXT        fax number
                SEMAIL                TEXT        SMTP address


Recipient data
                Variable              Type        Meaning
                RNAME                 TEXT        name
                RCOMPANY TEXT Company
                RDEPARTMENT           TEXT        department
                ROFFICE               TEXT        office
                RASSISTANT            TEXT        assistant
                RFAXNUMBER            TEXT        fax number
                TOCC                  TEXTEX      multiple-lined distribution list of all recipients


Additional data
                Variable              Type        Meaning
                SUBJECT               TEXT        subject
                PAGES                 TEXT        number of attached pages
                ALLPAGES              TEXT        number of all pages including cover sheet pages
                DATE                  TEXT        Datum (dd.mm.yyyy)
                TIME                  TEXT        time (hh:mm)
                DATETIME              TEXT        date time



                                                                                                       146(170)
                                                                     Telesnap UMS – Technical Guide




Front page editor
The provided Front Page Editor should support you in creating individual cover sheets. In the actual
version two different kinds of editors are provided. A “normal” version and an “Unicode”-


The front page editor is supplied to support the creation of individual front pages.
To work on a front page, xyz.cvr or xyz.cv1 should be double clicked. This will
start the front page editor in the source text view. The settings can be
made here. The standard front page default.* should not be changed but
copies with other names should be created and processed. In this way there
is always a functioning front page in reserve, and updates do not overwrite
their own definitions.
In this way, undesired fields can be deleted and others can be altered in
their positions, sizes and fonts. Furthermore additional new objects can be
inserted under new names. A list with possible objects can be found further
above.




In the current version the editor contains additionally a graphic edit
mode. It can be activated by calling the menu-command “ view   Graphic
view”. Each field of the cover sheet can be edited and displaced by moving
the mouse.




                                                                                              147(170)
                                                                     Telesnap UMS – Technical Guide




To increase the speed of the view in the graphic mode you can mask out the display of the bitmaps in
the cover sheet. Afterwards the picture’s build-up is faster and performing work easier.
By double-clicking on one of the data-fields all properties of this field can be edited and viewed
interactively.




                                                                                                 148(170)
                                                                  Telesnap UMS – Technical Guide




The preview-function allows you to view anytime the layout of the current
cover sheet. Therefore please click on the push button rightmost in the
symbol task bar. Thereupon a new window that contents the cover-sheet
definition opens.




If you want to change the cover sheet layout strongly is it recommended to create a drawing on scale
paper to deviate the coordinates.




Company logo
It is very easy to just add a company logo:
The standard front pages load a BMP file default.bmp at the very beginning.
It only contains the letters „FAX message“ and on the bottom right the logo
„powered by Telesnap UMS“.
On the right there is space to insert a company logo. The simple graphic
editor Paint is sufficient for this. However, the dimensions of the graphic
should not be altered, otherwise the result will be distorted.




                                                                                            149(170)
                                                                     Telesnap UMS – Technical Guide




Appendix G: Recall system DOCbase


Outline
Telesnap UMS contains a document recall database for existing fax, voice
and text documents. Each document can be addressed with a special direct
inward dialing number and can be recalled by external machines.
Up to 10.000 documents can be filed for recalling in the DOCbase. Depending
on the type of document, Telesnap UMS acts differently during the DOCbase
recalling:


               faxes (*.TIF)       The fax will be sent upon the call (fax on demand for
                                   Telesnap UMS, fax polling for the caller)
               voice messages      The wave file will be played upon the call.
               (*.WAV)             Afterwards, the connection is ended.
               texts (*.TXT)       The content of the text file will be read to the caller.
                                   Afterwards, the connection is ended.



Requirements
The Telesnap UMS ISDN terminal must be able to deliver the direct inward calls planned for
DOCbase.
ATTENTION: Please note that Telesnap UMS requests an additional code digit for the document
access (=DOCbase). This is installed in Telesnap UMS Setup (see below).
To implement DOCbase, no other module apart from the Telesnap UMS Line Manager (plus optionally
Telesnap UMS Sync) needs to be operating.



Configuration
Start Telesnap UMS Setup and open the register DID. A one or more digit identifier code must be
reserved in the field Document Access. This always results in the DOCbase mode. All direct inward
dialings, which start with this answer code, cannot be used for other users or Telesnap UMS functions.


The DOCbase answer code can also have several digits, but this will extend
the resulting compiled direct inward dialing number. The complete number
(prefix without 0 plus mains number plus direct inward dialing number)
should be no longer than 13 digits because only this number of digits is
guaranteed to be transmitted to every ISDN terminal.
Afterwards, the service Telesnap UMS Line Manager must be restarted.



                                                                                              150(170)
                                                                  Telesnap UMS – Technical Guide




Test
Three test documents for recalling are included in the Telesnap UMS.


Fax
To test fax polling, Telesnap UMS must be dialed from a fax, where no template has been loaded, with
the set DOCbase identifier code +0.
When the connection has been made, the polling function of the fax machine
must be started (usually by pushing the start-button).
The fax machine should now receive the test fax.




Preparing documents
All recalled documents are contained in the folder \Telesnap UMS\DOCbase. The documents must
correspond to a certain name convention:
               DOC_xxxx.TIF
               DOC_xxxx.WAV
               DOC_xxxx.TXT
xxxx contains the recall direct inward dialing number with initial nils. A
document number may only be used once, i.e. it is not acceptable to file
DOC_1234.TIF and DOC_1234.WAV. In such cases only one of the documents with
the same name can be recalled in the sequence TIF, WAV, TXT.


File formats
To provide documents for fax polling, they must merely be filed in the Multipage-TIFF-group3-format
and named corresponding to the name convention.
VoiceMails must be filed in the Telesnap UMS standard format CCITT A-Law 8 Bit, 8 kHz, Mono.
Other formats will be played back incorrectly or only as noise.
Text files must have the ASCII format.




                                                                                            151(170)
                                                                 Telesnap UMS – Technical Guide




Appendix H: Event-Logging


The following section shows the message entries in the event log, which can be entered by the
Telesnap UMS services and modules. Adjoining you will find a brief description to every message, and
sometimes possible reasons and methods for troubleshooting. The messages are sorted by modules
and categories.



Telesnap UMS Linemanager
These entries are entered in the application event log by the Telesnap UMS Linemanager.


Hint
Error Message                                               Description
Starting server version:%d.%d.%d.%d Build(%s)
Stopping server
Last stop was not complete (%d channels remained)



Warning

Error Message                                              Description
Stop: chnl:%u does not accept any command:%s               chnl process doesn’t accept commands
                                                           anymore
Stop: chnl:%u does not answer                              chnl process didn’t respond in the
                                                           timeout period
Stop: chnl:%u reset                                        chnl process receives reset-command



Error
Error Message                                               Description
Start server failed                                         Exception appeared with starting the
                                                            service
Stop server failed                                          Exception appeared with shutting down
                                                            the service
init logging failed                                         Telesnap UMSLog.DLL couldn’t be
                                                            loaded
Invalid license, service stopped                            License not valid

                                                                                           152(170)
                                                       Telesnap UMS – Technical Guide



interface to maildatabase:xxx failed              xxx mdbexch,mdbimap... dll couldn’t be
                                                  loaded
Interface to Menu xxx failed                      xxx menudat,menuvxml... dll couldn’t be
                                                  loaded in effect only 4.5
Exception in channel(Main)                        Exception in Telesnap UMSxmit with the
                                                  chnl handling
Exception in channel (incoming call)              Exception in Telesnap UMSxmit with
                                                  incoming call
Exception in channel (VoiceAccess)                Exception in Telesnap UMSxmit at the
                                                  VoiceAccess
Exception in channel (sending)                    Exception in Telesnap UMSxmit with the
                                                  dispatch
Exception in channel (restarting)                 Exception in Telesnap UMSxmit with the
                                                  attempt to restart the chnl Prozess


Null-Pointer received!!!!!                        chnl Prozess delivers result NULL




Failed to create channel process                  chnl Prozess couldn’t be generated
Failed to create channel process(check license)   chnl Prozess couldn’t be generated
                                                  CAPI chnls license restricted
chnl%u can not write vermitfile                   Switching-list couldn’t be written
No more tts channels available                    TTS license restricted
Exception in userdataclient                       Exception with the access to user-
                                                  database
Exception in mailclient                           Exception with the access to eMails
Exception(%X) at %X                               Description of the exceptions
chnl%u can not convert file:%s                    conversion to wav codec failed
Exception in channel %d (vaccess)                 (see above)
Exception in channel %d (sending)                 (see above)


Interface to CalendarDB:%s failed
Interface to AddressbookDB:%s failed
Interface to UserdataDB:%s failed




                                                                                   153(170)
                                                                   Telesnap UMS – Technical Guide




Telesnap UMS Queuemanager

Hint
Error-message                                                Description
"Conversion into newest format: OK Queue loaded!"            Queue could be loaded after a
                                                             conversion
"Service started (console + debug). (OK); with Telesnap      Start-Information of Telesnap UMSQ
UMSLog.DLL; version %s"
"Service started (console). (OK); with Telesnap
UMSLog.DLL; version %s"
"Service started. (OK); with Telesnap UMSLog.DLL; version
%s"
"Service started (console + debug). (OK); without Telesnap
UMSLog.DLL; version %s"
"Service started (console). (OK); without Telesnap
UMSLog.DLL; version %s"
"Service started. (ok); without Telesnap UMSLog.DLL;
version %s"
"Service stopped. "                                          Stop-Information of Telesnap UMSQ



Warning:
Error-message                                                Description
"Wrong queue format detected! Try to convert into newest     Queue couldn’t be read. Now the call-
format"                                                      doctor is called to convert the queue.
                                                             Additional information in the log-file
                                                             “Telesnap UMSQ.log”
"Unable to init Telesnap UMSLog.DLL. Error occurs if DB      Internal error with the initialisation of
connection failed!"                                          Telesnap UMSLog.DLL
"Telesnap UMSWdog.dll not found. SNMP disabled!"             The SNMP-DLL 'Telesnap
                                                             UMSWdog.dll' couldn’t be found. The
                                                             support of SNMP is deactivated.
"SNMP disabled! No DLL (%s) loaded!"                         SNMP-Initialisisation was not
                                                             processed.
"Unable to load %s - Initialize failed!"                     The SNMP-DLL 'Telesnap
                                                             UMSWdog.dll' couldn’t be loaded. The
"Unable to load %s"
                                                             support von SNMP is deactivated..



Error:
Error-message                                                Description
"Service stopped. (InitSettings %d)"                         Initialisation failed, please verify logfile!

                                                                                                 154(170)
                                                                  Telesnap UMS – Technical Guide



"Service stopped. (InitSNMP failed)"                         Initialisierung von SNMP fehlgeschlagen
"Service stopped. Main: Error (%d) in system\n"              Globaler Fehler
"Service stopped. Another Telesnap UMSQ is running or a      Error appears when a service and a
directory parameter in the registry is incorrect!"           console or two consoles run
                                                             simultaneously
"Service stopped! The Telesnap UMS Queue Doctor              The Telesnap UMS Queue Doctor is
(Telesnap UMSQDr.exe) is not installed!"                     absent on this system
"Service stopped! Unable to convert into newest format!      The Telesnap UMS Queue Doctor
Error %d! View Telesnap UMSQDr.log!"                         couldn’t process any conversation.
"Service stopped! Unable to convert into newest format!      The Telesnap UMS Queue Doctor
Error %d"                                                    couldn’t process any conversation.
"Service stopped! After conversion into newest format:       The Queue couldn’t be loaded even
unable to load Queue!"                                       after the conversation. .
"Service stopped! Queue loading failed! Please try repairing The Queue couldn’t be read. The
with Telesnap UMS Queue Doctor."                             Telesnap UMS Queue Doctor my not
                                                             convert automatically.
"Service stopped. Internal channel error! IO-Thread not      The IO-Thread couldn’t be started.
started! "
"Service stopped. X-Thread error"                            The X-Thread couldn’t be started.
"Service stopped. X-Thread timeout error (%d sec.)."
"Service stopped. FTCGate-Thread error"                      The FTC-Thread couldn’t be started.
"Service stopped. FTCGate-Thread timeout error (%d
sec.)."
"Service stopped. Unable to start SNMP-Thread"               The SNMP-Thread couldn’t be started.
"Service stopped. SNMP-Thread timeout error (%d sec.)."
"Global Q errors exceed maximum limit of %d errors! Try to   Too many errors appeared with the
repair the file failed (error code %d)!"                     access to the queue. It was not possible
                                                             to write it newly.
"Telesnap UMS Queue Manager is not able to rewrite           The queue couldn’t be written.
Global Q! (error code %d)"
"Error while loading global queue!"                          Error loading the Queue
"Not enough disk space (less than %I64u Byte)!"              Harddisk capacity underrun
"Service stopped. Unable to terminate FTCGateThread! "       The FTC-Thread couldn’t be terminated.
"Service stopped. Unable to terminate FTCGateThread
(WAIT_ABANDONED)! "
"Service stopped. Internal channel error! call of            Internal error of the channel-data-
FaxServerHighestChannel() failed (return -1)!”               administration.
"Service stopped. Internal channel error! call of
FaxServerHighestChannel() failed (return -3)! "




                                                                                              155(170)
                                                                   Telesnap UMS – Technical Guide




Telesnap UMS AutoText

Hint
Error-message                                                 Description
"Service started."                                            Startinformation of Telesnap UMSATX
"Service stopped. (last error: no RPC-connection to           Stopinformation of Telesnap UMSATX
Telesnap UMSQ)"
"Service stopped. (last error %d)"
"Service stopped. (ok)"




Warning
Error-message                                                 Description
"Unable to load robinson list (robinson.lst)."                The Robinson-List couldn’t be loaded.
"Unable to load %s (SNMP)"                                    Error with loading the DLL-file.
"Missing definition in Msg-file detected or unable to write   The definitions are incomplete at least in
Msg-Log-file! Please check file %s!"                          one of the msg-files.



Error
Error-message                                                 Description
"An error occurs on writing the error-file for %s!"           Error with writing an error-file in the
                                                              autotext-directory.
"Another Telesnap UMS Autotext is running in Autotext         You cannot start a service and a
mode on this computer! (OLD-File control)                     console or two consoles simultaneously.
Please stop the program or the running service!"
"Another %s is running on this computer!"




                                                                                                 156(170)
                                                                  Telesnap UMS – Technical Guide




ThorLog.DLL

These entries are executed by the ThorLog.DLL, in the name of the calling application (e.g.. Telesnap
UMSQ).


Hint
Error-message                                                Description
"Telesnap UMSLog (DEBUG-INFORMATION): Telesnap               General parameter- display from
UMSSimpleInitLogging(...); prepare call Telesnap             Telesnap UMSLogSimpleInitLogging().
UMSLogInitLogging() with parameter: DB=%s; USR= %s;          (debug)
PWD=%s; RotLog=%d; Local-Log-Dir=%s; Dest-Log-
Dir=%s; Log/Tab=%s; MaxFileSize=%d "
"Telesnap UMSLog (Function: Telesnap UMSLogOpen):            Call-up of Telesnap UMSLogOpen()
OK!"                                                         error-free
"Telesnap UMSLog (function Telesnap UMSLogClose()):          Aufruf von Telesnap
OK! "                                                        UMSLogClose()error-free



Warning
Error-message                                                Description
"Telesnap UMSLog (function Telesnap                          Both of the parameters Replacer and
UMSLogSimpleInitLogging(%s)): The parameter Replacer         Separator are identical. This may not be
and Separator are identical in Registry!"                    the case because the two files cannot
                                                             be imported to table-calculations
"Telesnap UMSLog (<unknown>): The parameter Replacer
                                                             separately.
and Separator are identical in Registry!"
"Telesnap UMSLog (function Telesnap                          Unknown Mode of Rotation.
UMSLogSimpleInitLogging(%s)): Rotation Logging Mode
illegal (%d). Set to %d!"
"Telesnap UMSLog (<unknown>): Rotation Logging Mode
illegal (%d). Set to %d!"
"Telesnap UMSLog (function Telesnap                          Unknown Mode of Rotation. Mode was
UMSLogSimpleInitLogging(%s)): Rotation Logging Mode          changed.
(%d) is now in Registry (%s %s)!"
"Telesnap UMSLog (function Telesnap
UMSLogSimpleInitLogging(<unknown>)): Rotation Logging
Mode (%d) is now in Registry (%s %s)!"
"Telesnap UMSLog (function Telesnap                          Too many tables (maximum is 10)
UMSLogSimpleInitLogging(%s)): Too many File/Table
connections (max.%d)!"
"Telesnap UMSLog (function Telesnap
UMSLogSimpleInitLogging(<unknown>)): Too many
File/Table connections (max.%d)!"
"Telesnap UMSLog (Function: Telesnap UMSLogOpen):            Error with opening a database
open error %d! DB is not open - try to buffer in files."

                                                                                             157(170)
                                                                            Telesnap UMS – Technical Guide



"Telesnap UMSLog (function Telesnap                                 Error within a table definition
UMSLogOpenTables(%s)): Illegal table definition in registry
\"%s\" (no comma in entry; error %d)!"
"Telesnap UMSLog (function Telesnap                                 Table was not initialized.
UMSLogPrepareWrite()): Illegal or no init for table name
\"%s\" (DATABASE); This error occurs, when the database
could not be opened! The DLL will try to buffer the
information in files."
"Telesnap UMSLog (function Telesnap                                 No AddNew() could be executed in the
UMSLogPrepareWrite()): (%s) Unable to call AddNew(...)              database.
(%d)!"
"Telesnap UMSLog (function Telesnap UMSLogWrite()):                 Error writing in a database. An export-
Unable to write into DB (%d). Writing Export file (%s) ok!"         file could be written.
"Telesnap UMSLog (function Telesnap UMSLogWrite()):                 Error writing to a log-file. The data
Unable to write into logfile \"%s\"! Dataset buffered (buffer       record was stored.
size: %d) and try next time."
"Telesnap UMSLog (function Telesnap UMSLogWrite()):                 ditto
Unable to write into logfile \"%s\"! Dataset and buffer (buffer
size: %d) written into tlp file. This file will be moved into the
original file!"
"Telesnap UMSLog (function Telesnap                                 Error with the initialisation of the buffer,
UMSLogInitSet(Telesnap                                              because the buffer-size has been
UMSLOG_INIT_MAX_BUFFER_COUNT)): call with Value                     declared as too big.
%d failed (%d / %d)"
"Telesnap UMSLog: function Telesnap UMSLogInitSet(%d)               Unknown parameter used.
unknown wSetMode"



Error
Error-message                                                       Description
"Telesnap UMSLog (function Telesnap                                 The mode, which has been entered to
UMSLogInitLogging(%s)): Rotation Logging Mode illegal               the registry is unknown.
(%d)!"
"Telesnap UMSLog (<unknown>): Rotation Logging Mode
illegal (%d)!"
"Telesnap UMSLog (function Telesnap                                 Both of the parameters Replacer and
UMSLogInitLogging(%s)): The parameter Replacer and                  Separator are identical. This may not be
Separator are identical in Registry!"                               the case because the two files cannot
                                                                    be imported to table-calculations
"Telesnap UMSLog (<unknown>): The parameter Replacer
                                                                    separately.
and Separator are identical in Registry!"
"Telesnap UMSLog (function Telesnap                                 The control-interval should not be
UMSLogInitLogging(%s)): The control interval is out of              changed.
range!"
"Telesnap UMSLog (<unknown>): The control interval is out
of range!"
"Telesnap UMSLog (Function: Telesnap UMSLogOpen):                   Unknown mode to open the target-data-
unknown Logging mode (%d)!"                                         drain. (db or file)


                                                                                                       158(170)
                                                                          Telesnap UMS – Technical Guide



"Telesnap UMSLog (Function: Telesnap UMSLogOpen):                 Error opening the target-data-drain (db
open error %d! Unable to open DLL for files..."                   or file)
"Telesnap UMSLog (function Telesnap                               No Init-function (simple-init) has been
UMSLogOpenTables(%s)): No init function called (error             recalled.
%d)!"
"Telesnap UMSLog (function Telesnap                               The entered table-definition (in the
UMSLogOpenTables(%s)): Illegal table definition in registry       registry) is wrong.
\"%s\" (LineDim(%d); error %d)!"
"Telesnap UMSLog (function Telesnap                               ditto
UMSLogOpenTables(%s)): Illegal table definition in registry
\"%s\" (error %d)!"
"Telesnap UMSLog (function Telesnap                               ditto
UMSLogOpenTables(%s)): Illegal table definition in registry
\"%s\" (no comma in entry; error %d)!"
"Telesnap UMSLog (function Telesnap                               An entry is to be written for a table,
UMSLogPrepareWrite()): Illegal or no init for table name          which has not been initiated before.
\"%s\" (DATABASE_ONLY); This error occurs, when the
database could not be opened! The calling program/service
will retry later."
"Telesnap UMSLog (function Telesnap                               Error accessing a database; Preparing a
UMSLogPrepareWrite()): (%s): Unable to call AddNew(...)           data record
(DATABASE_ONLY)!"
"Telesnap UMSLog (function Telesnap UMSLogWrite()):               Table was not initialised.
Illegal or no init for table name \"%s\""
"Telesnap UMSLog (function Telesnap UMSLogWrite()):               Error writing to a log-file.
Unable to write into logfile \"%s\" (Export DB mode)!"
"Telesnap UMSLog (function Telesnap UMSLogWrite()):               ditto
Illegal or no init for table name \"%s\" (%d) (Export DB
mode)!"
"Telesnap UMSLog (function Telesnap UMSLogWrite()):               Error writing to a database
Unable to write into DB (no file) \"%s\" (%d) (Export DB
mode)!"
"Telesnap UMSLog (function Telesnap UMSLogWrite()):               Error writing to a log-file.
Unable to write into logfile \"%s\"! Dataset was buffered
(buffer size: %d) but not written into tlp-file! Dataset May be
lost if access to log and tlp file are not recoverred!"
"Telesnap UMSLog (function Telesnap UMSLogWrite()):               Writing possible neither to the log-file
Unable to write into logfile \"%s\"! Unknown error (%d) in        nor to the buffer.
Buffer-module detected. (buffer size: %d)"
"Telesnap UMSLog (function Telesnap                               Error with the reconnect.
UMSLogReconnect()): error=%d (reconnect failed)"
"Telesnap UMSLog (function Telesnap                               ditto
UMSLogReconnect()): error=%d Telesnap UMSLog not
opened yet -> reconnect impossible; open: %s mode: %d
module: %s log: %s"




                                                                                                    159(170)
                                                                 Telesnap UMS – Technical Guide




Telesnap UMS Gateway

Hint
Error-message                                               Description
“(GetMail) OK connection to maildb %s, %s”                  The access to the gateway-mailbox per
                                                            mdbXXX.DLL is possible again. (after
                                                            an error occurred)
"(GetTelesnap UMS) OK connection to maildb %s, %s"          The access to the user-data per mail-
                                                            database-interface is now possible
                                                            again (after an error occurred)
"Spooler (%c%d) OK connection to maildb %s, %s"             The access to the mail-database-
                                                            interface for the dispatch of emails is
                                                            now possible again. (after an error
                                                            occurred)
"MailDLL (%s) successfully loaded."                         The DLL to access the selected mail-
                                                            database could now be loaded
                                                            successfully. (after an error occurred)
"License-Check: database now available"                     License-Check: The access to the
                                                            selected user-database is possible
                                                            again.
"Service started. (v%s) Build(%s)"                          The gateway-service (with the release-
                                                            number) could be started successfully.
"Service stopped."                                          Gateway Service terminated.
“"(GetMail) OK connection to notifydb"                      The access to the NOTIFY-Interface
                                                            (UCP, SMPP) is OK again. (after an
                                                            error occurred)
"Spooler (%c%d) OK connection to notifydb"                  Dispatch-interface to SMCS per
                                                            nfyXXX.DLL is OK again. (after an error
                                                            occurred)
"NotifyDLL (%s) successfully loaded."                       Interface-DLL to SMSC could be loaded
                                                            successfully now. (after an error
                                                            occurred)



Warning
Error-message                                               description
“(GetTelesnap UMS) Warning, no default-receiver             Advice that no overflow-user is adjusted
available."                                                 for the inbox-switching.
"%d Send-Message(s) cleared, no status after %d hour(s)."   After the adjusted TimeOut no status-
                                                            advice could be created for jobs, which
                                                            had been delivered to Telesnap UMS.
                                                            For the gateway the job is finished.
"Error loading Telesnap UMSWdog.dll, SNMP-Handling          Error while loading Telesnap UMS
disabled”                                                   Watchdog.DLL. The gateway doesn’t
                                                            send any SNMP-events.

                                                                                             160(170)
                                                                    Telesnap UMS – Technical Guide



"Sorry, another instance of %s is already running."            The Gateway couldn’t be started
                                                               because of the activation of another
                                                               gateway-instance.
"Version %s or greater of Telesnap UMSLog.DLL required.        Wrong Telesnap UMSLOG.DLL,
Using old logmode."                                            Gateway processes an internal logging.
"Error initializing Telesnap UMSLog.DLL"                       Error initialising the Telesnap
                                                               UMSLOG.DLL. Gateway processes
                                                               internal logging..
"Main() refreshing maildb"                                     After errors with the mail-connection the
                                                               mdbXXX was discharged and refreshed;
                                                               for NOTES-connection only.
"Billing: HandleLogFile() %s, no Billing order found"          SMS2Voice-Billing: A billing-receipt was
                                                               received by the SMSC, after the job has
                                                               been done by the gateway after a
                                                               timeout (without receipt).
"Error loading notify-dll (%s), version greater %s required"   The interface-DLL for the
                                                               communication with the SMSC couldn’t
                                                               be loaded because of a wrong version.
                                                               SMSC-Handling disabled.
"Error loading NotifyDLL (%s)."                                The interface-DLL to communicate with
                                                               the SMSC couldn’t be loaded. SMSC-
                                                               Handling disabled.




Error
Error-message                                                  Description
“Error in GwGetMail() for ref: %d from number of mails: %d" Error accessing a mail in the gateway-
                                                            mailbox
“(GetMail) Error connection to maildb %s, %s"                  Error connecting to the gateway-mailbox
"(GetTelesnap UMS) Error connection to maildb %s, %s"          Error connecting to the mail data base
                                                               to access the user data for the income-
                                                               switching
"Error: receiver not resolved (%s), default not available"     income-switching: User cannot be
                                                               allocated and no overflow available; job
                                                               cannot be arranged
"(SpoolMails) Error connection to maildb %s, %s"               Error connecting with the mail database
                                                               for the mails’ dispatch to the inboxes
"Error, missing attachment converter <%s>"                     Incoming Faxes should be converted
                                                               into files of type xyz (e.g. *.jpg); the
                                                               necessary converter is not installed
"Terminating, dead-locked thread found."                       Gateway terminates itself because of a
                                                               thread accessing the mail database
                                                               terminated in an undefined not
                                                               repairable state
"Error loading MailDLL (%s). %s"                               Gateway cannot load the DLL for the
                                                               adjusted mail database; it continues
                                                               trying

                                                                                                 161(170)
                                                                  Telesnap UMS – Technical Guide



"License-Check: error accessing database. Service will stop License-check: Error accessing the
if error still exists in %d minutes."                       user-database. If the error continues
                                                            existing after a time period, the Gateway
                                                            will stop.
"STOP LICENSE NOT VALID (Code %d)"                           Gateway stops because the license
                                                             code is not valid. Possible error codes:
                                                             1: missing license code
                                                             2: more user than licences
                                                             3: no user-database entered
                                                             4: error accessing the database
"Service not started. (v%s) Error: HomeDir <%s> not          No access to the adjusted Telesnap
accessable"                                                  UMS-homedirectory
"(GetMail) Error connection to notifydb"                     Error connecting to SMSC (per
                                                             nfyXXX.DLL)
"GetTelesnap UMSV() Error: ExchangeOrg not found for         MultiOrg-Installation: No ExchangeOrg-
receiver (%s)"                                               Entry found for the receiver in the user-
                                                             database
"GetTelesnap UMSV() Error: unable to save order (%s) in      MultiOrg-Installation: The incoming
queue (%s)"                                                  message couldn’t be sent to the
                                                             switching queue,which has been found
                                                             with the Exchange-Org-Entry in the
                                                             database. Switching will be retried after
                                                             a short time.
"(SpoolMails) Error connection to notifydb"                  Error in the Switching-Interface SMSC
                                                             over nfyXXX.DLL.
"Billing-Error detected, shutting down."                     SMS-Billing fatal error in the interface to
                                                             the Billing-SMSC. Gateway terminates
                                                             itself.



Telesnap UMS Monitor

Hint
Error-message                                                Description
Service started v.%s Build: %s. DSN:%s
Service stopped



Error
Error-message                                                Description
Unable to listen SNMP TRAP Service                           Is verified during the start.
Unable to open table: %s
Table Severitys: Type %d not found


                                                                                               162(170)
                                                    Telesnap UMS – Technical Guide



eMail notification. SMTP Connect to %s failed. %s
eMail notification. SendMessage(). LastError=%s




                                                                          163(170)
                                                                    Telesnap UMS – Technical Guide




Telesnap UMS Wdog.dll

Error
Error-message                                               Description
Dll loaded. Ver:.4.5.0.0,Build Jun 62002
DLL unloaded.



Telesnap UMS Printing

Hint
Error-message                                               Description
Service started
Service stopped



Error
Error-message                                               Description
Another instance of Telesnap UMSPrn is already running.     Is verified during the start.
Unable connect to spooler service.                          Is verified during the start.
Missing read-write permission to directory %s               Is verified during the start.
Spooler service status. %s
Attempt to start spooler service failed. %s"                Ditto
Rename file %s to %s failed.                                Job processing
Move file %s to %s failed 50 times. %s                      Job processing
Order:[%s] ,file name is empty.                             Job processing
File not found: %s                                          File, which is listed in the job could not
                                                            be found
Printer number not found: %d                                Printer number which is listed in the job
                                                            could not be found
%d min timeout. ShellExecute printing process terminated.   Job processing




                                                                                              164(170)
                                                                  Telesnap UMS – Technical Guide




Telesnap UMS Sync
These entries are processed by Telesnap UMS Sync in the application protocol.




Hint
Error-message                                                Description
"Service finished."                                          Service terminated normally.
"Service started. (V %s) Next synchronisation at %s.         Service started successfully, next
Build(%s)"                                                   synchronization-attempt at
"Sync done. Next synchronisation at %s"                      Synchronization successful. Next run at
"Done: %I64d records written"                                Synchronization successful. N-Data
                                                             records were taken over.




Error
Error-message                                                Description
"error starting service (%s), errorcode %d (missing          Missing settings in the registry.
parameters)"
"error starting service (%s), errorcode %d - (wrong          Database-source not supported.
database-mode)"
"Sync error. Next synchronisation at %s"                     Error during the synchronization. Next
                                                             attempt at
"synch-error, could not save new bin-database"               Error saving the new cache-database
                                                             (possibly used by another process)
"synch-error, bin-database not accessable"                   Error accessing the provided cache-
                                                             database
"synch-error, could not create new bin-database"             Error creating the provided cache-
                                                             database
"synch-error,   could not write new bin-database");          Error writing to the new cache-database
"synch-error, error accessing %s"                            Error accessing the indicated file/
                                                             database
"synch-error, error in database-synchronisation, errorcode   Synchronization error. The error with the
<%d>                                                         indicated code appeared.




                                                                                                 165(170)
                                                                    Telesnap UMS – Technical Guide




UMS-Connector

Hint
Error-message                                                 Description
Service started.
Service stopped.
The required faxpath %1 is now available.                     After an error message the appropriate
                                                              path is accessible again.




Warning
Error-message
                                                              Description
Service started. The connector is started, but the required   Service started. Access to several
faxpath %1 is not available. ErrorCode #%2                    necessary directories not possible.


No report for incoming faxes after %1 hours. %2 files         The connector forwarded incoming fax/
cleared from directory WORK.                                  speech-messages to the client’s
                                                              mailbox. Although the client received an
                                                              acknowledgement, the connector didn’t
                                                              receive any handshake. This happens in
                                                              case of forwarding over several sites.
Error handling receive fax (1) << %s >>.Files moved to <<     Incoming message couldn’t be
%s >>                                                         processed. It is forwarded to the
                                                              specified directory.
Error converting incoming order %s, error-code: %d            Incoming message couldn’t be
                                                              processed because of an error-code.




Error
Error-message                                                 Description
Service stopped. The connector was stopped by an internal     Connector stops because of an internal
program error: %1. [0x%2].                                    error, followed by an error code
Internal program error: %1. [0x%2].                           Internal Error, followed by an error code.
                                                              However, the connector continues
                                                              working.
Error while starting the connector. Internal Error #%1.       Connector couldn’t be started because
                                                              of an internal error (followed by an error
                                                              code)
Message not converted, the required faxpath %1 is not         Message couldn’t be processed
                                                                                                  166(170)
                                                                 Telesnap UMS – Technical Guide



available. ErrorCode #%2                                    because the path to the Telesnap UMS-
                                                            server is not accessible.
Error while processing %1 message of class %2, will be      Incoming/ Outgoing message of the type
moved to archive folder.                                    X couldn’t be processed.
Service stopped. The required ExchangeServer is not         At least one of the necessary Exchange-
running !!!                                                 services doesn’t work.
Service stopped. The number of fax-clients exceeds your     More user than licenses.
purchased licences. Please purchase additional licenses, or
delete the computed number of clients with fax-adresses.
Error converting incoming order %s, missing attachmentfile. Incoming message couldn’t be
Will be moved to archive folder."                           converted, no access to the attachment-
                                                            file possible.
ProcessMtsOut() NonDeliver, Exception in                    Outgoing messages couldn’t be
ExportMessage\n                                             processed; an exception appeared.




                                                                                          167(170)
                                                                    Telesnap UMS – Technical Guide




Appendix I: Database schema


Listing and description of all data records used in Telesnap UMS.
Fieldname                 Type    Values      Description                                     Mandatory


DID                       Char    0..999999 Personal DID number or Account-Code               Y
                          16
FullName                  Char    Any         Used for Greeting in Menu if no name recorded Y
                          32
PIN                       Char    2-16 digits PIN-Code for Mailbox access                     Y
                          16
PinErrorCounter           Int     1 to 5      Internal counter for invalid logins             Y
MailBox                   Char    Any         Personal Mailbox on Mailhost or VXML-file       Y
                          128
MailAddr                  Char    Any         Complete SMTP-Adress                            Y
                          128
MailPassword              Char    Any         Password to log on to server                    Y
                          16


MailHost                  Char    Any         Mail-Host containing users' mailbox             N
                          128
MailType                  Int     0,1         Type of Mail host, POP3 or IMAP4                N
                                              (reserved for future use)
Services                  Int     Bitmask     Bitmask: Fax (b1), Voice (b2), MessageAccess N
                                              (b3) , Voice-app (b6),AppointmentAccess(b7),
                                              AdressbookAccess(b8)
MenuAction                Int     Any         Kind of user (new, profi, standard etc.)        N
MenuStyle                 Int     Any         Type of application / menu-flow /ASR enabled    N
LastAccess                Char 8 date/time    Last Access to Mailbox                          N
BlockDate                 Char 8 date/time    Blockdate for Box                               N
BlockState
Notification              Int     BitMask     0=None, 1=SMS, 2=OutCall, 3=Mwait               N
                                              Bits 4 bis 17 werden bereits verwendet
OutCallProfile            Char    Any         Defines days/timeframes for outcall-notification N
                          128
Mobile                    Char    Any         Used for SMS notification if set                N
                          32
                                                                                             168(170)
                                                     Telesnap UMS – Technical Guide



Pager          Char   Any        Used for SMS notification if set                    N
               32
ExtraNumbers   Char   Any        Used for outcall notification and incoming calls    N
               128
HomePhone      Char   Any        Used for SMS notification if set                    N
               32
WakeNumber     Char   Any        For wakeupcalls                                     N
               32
MWait          Char   Any        Used for SMS notification if set                    N
               32
WakeTime
HomeFax        Char   Any        Used for forwarding of fax and eMails if set        N
               32

Speaker        Int    Any        Speaker number, used by CacheDLL                    N
MenuSpeaker    Char   any name   Default Menu speaker if not global                  N
               16
MailSpeaker1   Char   any name   Default eMail speaker if not global                 N
               16
MailSpeaker2   Char   any name   Secondary eMail speaker if not global               N
               16
AutoPlay       Int    0,1        Automatically plays first message in                N
DatePlay       Int    0,1        Tells time and         date   before    message N
                                 playback/reading
CountryCode    Int    1 to 8     Country-code for any type of text messages          N
CustomerCode   Int    Any        Determines Greeting Prompt and environment          N
Costs          Char   Any        Cost-Code
               10
DialPrefix     Char   Any        User’s dialprefix
               10
SendRights     Int    1,2,3      Rights to send Faxes/Voicemails to certain N
                                 area-codes (Local Area, National, International)
Polling        Int    Bitmask    Polling, SMS, Callback                              N
Company        Char   Any        For Faxpage only                                    N
               32
Department     Char   Any        For Faxpage only                                    N
               32
Assistant      Char   Any        For Faxpage only                                    N
               32
City           Char   Any        For Faxpage only                                    N
               32
PostalCode     Char 8 Any        For Faxpage only                                    N
Street         Char   Any        For Faxpage only                                    N
               32
Phone          Char   Any        For Faxpage only                                    N

                                                                                    169(170)
                                                            Telesnap UMS – Technical Guide



                    32
Faxnum              Char      Any      For Faxpage only                                 N
                    32


PrinterIn           Int       0..255   Print incoming faxes to queue n                  N
PrinterOut          Int       0..255   Print outgoing faxes to queue n                  N
ArchivIn            Int       0,1      Archive incoming faxes                           N
ArchivOut           Int       0,1      Archive outgoing faxes                           N
CoverTemplate       Char      Any      Name of cover template                           N
                    32
InternetAddr        Char      Any                                                       N
                    128


DFrom               Date/Ti            Reserved for Vario                               N
                    me
                                       Notification Time Daily
DTo                 Date/Ti            Reserved for Vario                               N
                    me
                                       Notification Time Daily
WEFrom              Date/Ti            Reserved for Vario                               N
                    me
                                       Notification Time Weekend
WETo                Date/Ti            Reserved for Vario                               N
                    me
                                       Notification Time Weekend
WDFrom              Date/Ti            Reserved for Vario                               N
                    me
                                       Notification Time Weekday
WDTo                Date/Ti            Reserved for Vario                               N
                    me
                                       Notification Time Weekday
BMS                 long               Reserved for Vario                               N
                                       Field to Control Execution for Special Update
                                       Trigger
PIN2                Char               Reserved for Vario                               N
                    16
                                       Contains Pin Retrived from External Source


ExchangeOrg         Char      Any      Used for MultiOrg-Version only                   N
                    128
UserAnnounceFlags   long               Which user announcefiles does exists             N
                                       Reserved for Vario
UserAnnounceDate    Date/Ti            Date where the Latest Change from one of the N
                    me                 announcefiles are done.
                                       Reserved for Vario




                                                                                       170(170)

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:66
posted:11/16/2011
language:German
pages:170