1. Manuals
  2. Brands
  3. Cycos Manuals
  4. Software
  5. Cycos ERGO mrs 5.0
  6. Manual

Cycos mrs 5.0 Manual

Message routing system
Hide thumbs Also See for Cycos mrs 5.0:
1
2
3
4
Table Of Contents
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
Table of Contents

Advertisement

Quick Links

Download this manual See also: Administration Manual, Administrator's Manual
System
Architecture

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Cycos mrs 5.0 and is the answer not in the manual?

Questions and answers

Related Manuals for Cycos Cycos mrs 5.0

Summary of Contents for Cycos Cycos mrs 5.0

  • Page 1 System Architecture...
  • Page 4 The range of functions described in this documentation were accurate at the time of this manuals printing. The manufac- turer reserves the right to make technical and functional changes as well as extensions and reductions without prior no- tification. No liability is assumed for any discrepancies contained within this manual. Protocols pertaining to devices connected to the system are based on norms or extensions as required by marketing de- mands.

  • Page 5: Table Of Contents

    System Architecture Table of Contents Table of Contents 1 Introduction ............13 2 MRS 5.0 Kernel .
  • Page 6 System Architecture Table of Contents 2.8 USER and SHORT Database fields of special significance ..... .64 2.9 Distributed MRS Server..........65 2.9.1 Firewalls between Nodes of a Distributed MRS .
  • Page 7 System Architecture Table of Contents 3 TeleReg API ............125 3.1 Registry Entries .
  • Page 8 6.3 Innovaphone IP 400 Connection ........
  • Page 9 System Architecture Table of Contents 9.10.1 Vanity Number Generation......... . 222 9.11 Registry Entries .
  • Page 10 System Architecture Table of Contents 15.1 Named Pipes ............267 15.2 SPX Protocol .
  • Page 11 System Architecture Table of Contents 18.3 Automatic Call Distributor (ACD.e) ........304 18.3.1 Resources .
  • Page 12 System Architecture Table of Contents 21 Remote Administration of a MRS Server ......373 21.1 The MRS Monitor .

  • Page 13: Introduction

    System Architecture Introduction 1 Introduction ... she called Ulysses: “Stranger,” said she, “rise and let us be going back to the town; I will introduce you at the house of my excellent father, where I can tell you that you will meet all the best people among the Phaecians.”...

  • Page 14: System Architecture

    System Architecture Introduction An incoming fax can for example be routed directly into an Exchange e-mail network or an Internet mail could be prepared for retrieval via fax. Users can retrieve informa- tion selectively through either the MRS client, Internet, over the telephone or fax, or through an extraneous mail system.

  • Page 15: Mrs 5.0 Kernel

    System Architecture MRS 5.0 Kernel 2 MRS 5.0 Kernel ... let us then send chosen messengers, who may go to the tent of Achilles son of Peels without delay. Let those go whom I shall name. Let Phoenix, dear to Jove, lead the way;...

  • Page 16: Mrs Kernel Components (Mrs)

    System Architecture MRS Server Structure These services can be divided into two groups: MRS Kernel components. The kernel contains databases, router, and administra- tive software. MRS APL’s (Access Protocol Layers). The APL’s provide the kernel with the required communication protocols. The APL’s implement e.g. ISDN protocols, Exchange gateways, and TCP/IP transports.

  • Page 17: Mrs Access Protocol Layers (Apl)

    System Architecture MRS Server Structure The XMRSVC is much more powerful than the NT Event Viewer. MRS Information Store (INFOSTOR) Four components are managed by the MRS Servers database: Address books. Address book and user information are stored in the Correlation database.
  • Page 18 System Architecture MRS Server Structure Dialogic APL (DLGAPL) Voice and fax protocols for Dialogic hardware. In addition, the CornetN protocol is supported for the Siemens Hicom PBX. Microsoft Exchange 2000 APL (E2KAPL) Gateway to Microsoft Exchange Version 2000. This APL is comprehensively described in an individual documentation.
  • Page 19 System Architecture MRS Server Structure Lotus Notes APL (LNAPL) Gateway to Lotus Notes. This APL is comprehensively described in an individual doc- umentation. Lotus Notes True Unified Messaging APL (LNUMAPL) Additional connector enabling True Unified Messaging with a Lotus Notes connec- tion.

  • Page 20: Mrs Server User Interface

    System Architecture MRS Server Structure SPX Transport APL (SPXAPL) This Network APL implement the client-server communication over the Windows NT network protocol SPX/IPX. TCP/IP Transport APL (TCPAPL) This Network APL implement the client-server communication over the Windows NT network protocol TCP/IP. V.24 APL (V24APL) The V.24 APL enables the use of fax with fax class 2 modems.
  • Page 21 System Architecture MRS Server Structure More information to the operation of the MRS Monitor is found in the MRS Server Administrations manual.

  • Page 22: Mrs Process Structure

    System Architecture MRS Process Structure 2.2 MRS Process Structure The following illustration provides an overview of the MRS process structure. M o n i t o r s I n f o S t o r I n f o S t o r I n f o S t o r I n f o S t o r M T A...

  • Page 23: The Mrs Addressing

    System Architecture The MRS Addressing 2.3 The MRS Addressing The MRS Server uses the following addressing form. This form of addressing is inde- pendent of protocol and structure of the target system. NVS:NODE.CLASS/USER NVS:NODE/USER The first address section (NVS:) is a constant and non-changeable, as it characterizes the syntax as well as the address type.

  • Page 24: Mrs 5.0 Server Rules

    System Architecture MRS 5.0 Server Rules NVS:FAXG3/491234567890 Fax address for telephone number +49 1234 567890. NVS:FAXG3.1/491234567890 The same address using the CLASS option. NVS:MS/MAYER MS-Mail user MAYER. NVS:SMTP/MAYER@mister.de TCP/IP e-mail with SMTP protocol to user MAYER at domain mister.de. NVS:FAXG4/491234567890 Fax G4 member 491234567890.

  • Page 25: Rule Application Within The Kernel

    System Architecture MRS 5.0 Server Rules . The Mail APL can be instructed to send a copy when a time A l a r m - C o p i e s dependent rule condition occurs. In this way faxes that have not been read within a prescribed period could be sent to an administrator.

  • Page 26: Examples For Rules

    System Architecture MRS 5.0 Server Rules Restriction definitions are permitted with the following Values listed under the Key HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\MTA RecursivReRout REG_DWORD 0 or 1 Through the use of RecursivReRout it is specified whether the rule list may be applied in more than one instance. A value of 0 (false) specifies that only one application of the rule list is allowed.

  • Page 27: Rule Structure

    System Architecture MRS 5.0 Server Rules This rule processes an incoming G3 fax addressed to 491234905678. The server first tries to locate the user with the address 491234905678. If an equivalent user address is found, the server then tries to locate the SMTP Internet address from the address tables in the user database.

  • Page 28: Rule Element Structure - Condition

    System Architecture MRS 5.0 Server Rules In the event that Address1 and the recipient correspond with another, then the rule is further evaluated. In this example the transaction to the recipient NVS:FAXG3/ 32155 would be further evaluated. 2.4.3.2 Rule Element Structure - Condition Through Condition further requirements are defined that must be satisfied before the rule can be applied.[Condition] can be comprised of one or more require- ments separated by a semicolon (logical AND):...
  • Page 29 System Architecture MRS 5.0 Server Rules Possible flags are: Flag Significance If a message carries this flag, the message body is deleted as ADMINDELETE soon as an OK or FAILURE report arrives. The body is replaced with the short information that the message has been deleted.
  • Page 30 System Architecture MRS 5.0 Server Rules Flag Significance Document message ID was externally created. NODELMID Preferred Routing Rule no longer applicable. NOPREFERRED Standard reports are surpressed when Report-Mails are used. NOREPORT Document has been printed. PRINTED Document has been read. READ Special flag for VU-S charge invoice.
  • Page 31 System Architecture MRS 5.0 Server Rules LEN=n, LEN>n, LEN<n, LEN!=n Rule only applies when the length of the document is equal to, greater than, less than or not equal to the n bytes. ORG=<address-wildcard> Rule only applies if the originator´s address corresponds with the address form <address-wildcard>.
  • Page 32 System Architecture MRS 5.0 Server Rules Value Significance Departmental printer information SMTP-Mail SMTP Transition telex-teletex TLXTTX TTU transition TTU acknowledgment TTUACN Voice VOICE PRIVOGROUP(ORG)=<Private Group of the originator> PRIVOGROUP(REC)=<Private Group of the originator> PRIVRGROUP(ORG)=<Private Group of the recipient> PRIVRGROUP(REC)=<PrivateGroup of the recipient> Same as GROUP, however, for private groups.
  • Page 33 System Architecture MRS 5.0 Server Rules n=5 or n=REPEAT Faulty termination. Redial will be performed. n=6 or n=DELAYED Processing successfully completed, recipient to receive information at next login. This status is applicable when a document is sent to an e-mail subscriber that is currently not logged in.

  • Page 34: Rule Element Structure - Address2

    System Architecture MRS 5.0 Server Rules 2. A fax to 491234567890. User Mayer has the following entry in the user data- base: USER MAYER FAXG3 491234567890 NETWORK/OFFICE/SCHULZ OPTION1 Since a user does exist for the example transaction with the fax G3 address 491234567890, the database is further queried to see if the OPTION1 database field contains the string XYZ.

  • Page 35: Rule Element Structure - Assignment

    System Architecture MRS 5.0 Server Rules Example (Explicit form): If the recipient corresponds to the transaction type Address1 and requirements in [Condition] are satisfied, then Address1 is replaced by Address2. NVS:FAXG3/49832*[PRIO=4]=NVS:TXSF/498888* If a fax with the priority 4 is sent to the address NVS:FAXG3/49832155, then it would be rerouted to NVS:TXSF/498888155.
  • Page 36 System Architecture MRS 5.0 Server Rules The transmission time is delayed by n seconds, set to the clock time hh:mm, set on the time hh:mm on the next week day from [MO,TU,WE,TH,FR,SA,SU], or set on the time hh:mm in n days, if the recipient address is from type Address1 and [Condition] is satisfied.

  • Page 37: Rerouting

    System Architecture MRS 5.0 Server Rules The Subject is set on <Text>. The variants OSUBJ and CSUBJ are intended for use with Carbon Copy Rules and set the flag by the Original resp. by the copy. The following variables may be contained in <Text>: Variable Significance Message originator as a complete MRS Address.
  • Page 38 System Architecture MRS 5.0 Server Rules NVS:FAXG3.*/*=NVS:$(NODE)/<DB> NVS:FAXG3.*/*[ORG=NVS:FAXG3.*/*]=NVS:$(NODE)/$(POSTMASTER) Fax G3 documents that are directed to an arbitrary number *, will be routed to the corresponding user on the MRS-System $(NODE), as long as an appropriate data- base definition is found. If the database contains no definitions pertaining to a fax G3 address *, then the document would be forwarded to the $(POSTMASTER).

  • Page 39: Transmission Copies, Carboncopy

    System Architecture MRS 5.0 Server Rules NVS:VOICE/*[ORG=NVS:VOICE/*]=NVS:LN/VOICE/* NVS:*.*/*=<PREFERRED> NVS:SMTP.*/*[ORG=NVS:SMTP.*/*;FLAG=LOCALUSER; ORG!=NVS:SMTP/MAIL-REPORTER]=NVS:$(NODE)/$(POSTMASTER) The switching strategy, Switching through Exchange address book, reroutes all incom- ing mails to the Exchange APL which then routes to the individual user in accordance to the entries in the individual address books. The Value ReRouting in this case con- tains the following Routing Rules: NVS:FAXG4/*[ORG=NVS:FAXG4/*]=NVS:EXCH/FAXG4/* NVS:FAXG3/*[ORG=NVS:FAXG3/*]=NVS:EXCH/FAXG3/*...
  • Page 40 System Architecture MRS 5.0 Server Rules Example: CarbonMode REPORT CarbonCopy NVS:TCPIP.*/*[ORG=NVS:FAXG3.*/*;SUCCESS=DELAYED; REC!=NVS:TCPIP/$(POSTMASTER)]=NVS:TCPIP/$(POSTMASTER) Reroutes all incoming fax G3 documents addressed to not currently logged-in Mail user, to the TCP/IP address $(POSTMASTER). In order to prevent recur- sion, the rule is only used if the addressee is not $(POSTMASTER). CarbonMode REPORT CarbonCopy...

  • Page 41: Awake Rules

    System Architecture MRS 5.0 Server Rules Default Settings Default settings are easily accessed through the configuration menus on the MRS Monitor. The following Carbon Copy Rules have been entered in the Value CarbonCopy. Copy incoming fax documents to default printer routs a copy to the default APL printer. NVS:*.*/*[ORG=NVS:FAXG3.*/*;FLAG!=CARBONCOPY;...
  • Page 42 System Architecture MRS 5.0 Server Rules then the polling rate must be set to 1 second. If AGE is in days, then a polling rate of 3600 seconds (1 hour) is sufficient. MaxAwake REG_DWORD Maximum number of Awake rules. Memory is reserved for the number of Awake rules entered here.

  • Page 43: Automatic Report Transmission Per Mail

    System Architecture MRS 5.0 Server Rules POSTMASTER. Awake Rule 2: Mail sent to TCP/IP user that was received (SUCCESS=OK), but has not been read or printed within a 10 day period would be sent to the POSTMASTER. Awake Rules 3 and 4: Incoming fax G3 and G4 documents that are not processed within a 4 day period are sent as a copy to the POSTMASTER.

  • Page 44: Report Form Structure

    System Architecture MRS 5.0 Server Rules Copy Rules. The Value Report must also be inserted in the CarbonMode Key in the Registry. The Mail-Report must now be activated through the appropriate Carbon Copy Rule. Example: NVS:*.*/*[TYPE=REPORT;ORG=NVS:LN/*]=NVS:LN/<ODB>[FORM=report.ok] Report Forms can be applied to the various status reports through use of the SUCCESS-Condition.
  • Page 45 System Architecture MRS 5.0 Server Rules Variable Significance Readable form of the originator address. If information {ORGNAME} over the fax originator is contained in the Alias database, this could appear as a name instead of a fax number. Incoming Service {ORGNODE} Readable form of the original originator for documents that {ORGORGNAME}...

  • Page 46: Normal Report Suppression

    System Architecture MRS 5.0 Server Rules Cost: {COST} Subject: {SUBJECT} Digest: {DIGEST,256} ======================================================================= 2.4.4.3 Normal Report Suppression If the normal default report for the recipient APL is to be suppressed, the NOREPORT flag must be set for the Carbon Copy Rule sending the report. This suppresses the default report so that only Report Mail created by the Carbon Copy Rules can be sent as a document.

  • Page 47: Routelets

    System Architecture MRS 5.0 Server Rules Additionally, the database field PREFERRED is used for entering services preferences from the alias list. If a message is addressed to a user through an alias function of the MRS Client, the Client forwards the message to the user through the appropriate ser- vice and corresponding address.

  • Page 48: Logical And Physical Lines

    System Architecture Logical and Physical Lines 2.5 Logical and Physical Lines The Access Protocol Layers (APLs) sets physical lines into logical lines. A physical line is defined and made available through an external network, and is represented through a connection (network hardware). A logical line is independent of the external network and is determined by the network type and protocol.

  • Page 49: Actions

    System Architecture Maintenance Script InformOnFailure = <User> InformOnSuccess = <User> Task <Task> <Task> <TaskGroup> is an arbitrary name for a group of <Tasks>, that are to be collectively started. <TimeSpec> in format n[s,m,h,D,W,M,Y]@hh:mm gives the time hh:mm and intermittence n, with which the <TaskGroup> is to be executed. The suffix @hh:mm give the time at which the <TaskGroup>...
  • Page 50 System Architecture Maintenance Script <Server> is the server name of a Windows NT server in UNC notation, on which a MRS database (InfoStor) runs. If the call is being executed locally, the parameter node= may be excluded. The following actions can be started through <TASK>: EXPORT record=<Record>...
  • Page 51 System Architecture Maintenance Script EXPORT record=RUND file=<Filename> class=<LName> The distribution list <LName> is exported in a usable form for extraneous appli- cations as a file <Filename>. Example: EXPORT record=RUND file=rund.txt class=TESTLISTE CLASSNAME CLASS KEYNAME RUND TESTLISTE GLIST GLIST TESTLISTE NVS:FAXG3/1234 GLIST TESTLISTE NVS:FAXG4/2343...
  • Page 52 System Architecture Maintenance Script Use DELDB only with records received by user MAYER. flags=<Flags> Deletes only data records which contain all of the set flags. <Flags> is a comma separated list of the flags READ, PRINTED, ARCHIVE, DELORG, DELREC, DELARC and DELPOP. The DEL* flags refer to messages that were deleted by either the originator (DELORG), recipient (DELREC), archiving (DELARC), or POP3 client (DELPOP.) Example: flags=READ...
  • Page 53 System Architecture Maintenance Script Correlation-records of the CLASS <Classname> are imported. If the option delete=1 is set, then all correlation-records with CLASS=<Classname> will be deleted. Example: A new privilege list is to be installed on the server. The new privileges are contained in a correlation-export file as privlist.txt. With CLASSIMPORT class=PRIVILEGES file=privlist.txt delete=1 the old PRIVILEGES definitions are first deleted, then the new definitions are imported.

  • Page 54: Variables

    System Architecture Maintenance Script this field will be use exclusively for the given user. This field was designed for use with InfoTool. OldUserCleanup This task removes all non-active user entries from the database. Non-active user entries are those entries which do not have a password or PIN number. In this case the following happens: All documents received by the user are tagged as being deleted by the user.
  • Page 55 System Architecture Maintenance Script HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\Kernel\Accounts $(BACKUP) Backup directory as defined under the Key HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\MRS Globals in the Value BackupDirectory. $(FOLDER) Document Storage directory as defined under the Key HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\MRS Globals in the Value FolderDirectory. $INTERACTIVE This is a list of all interactive services, including those that are not executed by $NONINTERACTIVE.
  • Page 56 System Architecture Maintenance Script DocumentLifeTimeOutbound is defined in the Registry Key HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\MTA. $(LIFETIMEPASSTHROUGH) After the expiration of this time period (in days), all forwarded documents are deleted from the server and only the journal entry retained. The Value defined Registry DocumentLifeTimePassthrough HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\MTA.
  • Page 57 System Architecture Maintenance Script If counter based CIT is used, the sequence of DelDB-commands must be ended by the command DelDB record=Journal age=$(LifeTime). Through this, an implicit consistency check is made of the new message counters used by the CIT based counter. Example Backup Periodicity = 24h@0:00...

  • Page 58: The Mask Description Language Mdl

    System Architecture The Mask Description Language MDL DelDB record=Journal originator=$NONINTERACTIVE flags=DELREC age=10 DelDB record=Journal originator=$INTERACTIVE recipient=$INTERACTIVE flags=DELREC,DELORG age=3 In the example, <TaskGroup> Backup executes the following functions every 24 hours at 0:00: Execution of the script backup.bat Full database export to fullexp.exp Address book export to correl.txt In the example, <TaskGroup>...
  • Page 59 System Architecture The Mask Description Language MDL $attrib, field attributes are defined Example: ; MRS 3.0 Mask Description for TEST $mask PROFILE NAME ####################################################### PASSWORD ################################ PIN ################ PRIVILEGES ################################ GROUP ######################## PREFERRED ####################################################### MAILBOX ####################################################### STAND-IN ####################################################### ####################################################### FAXG3# #################### FAXG3-ID #################### VOICE#...
  • Page 60 System Architecture The Mask Description Language MDL ISDNTTX# PSERV,DNOREAD,CHAR,UNIQUE ISDNTTX-ID PSERV,CHAR PSERV,CHAR,UNIQUE,UPPER MAILBOX PSERV,CHAR,UPPER,UNIQUE PSERV,CHAR,UNIQUE,UPPER NAME CHAR PASSWORD CHAR,UPPER,KRYPT CHAR,UPPER,KRYPT PMI-HOSTNAME PSERV,LOWER,CHAR PMI-PASSWORD CIPH,CHAR PMI-SCHEDULE PSERV,CHAR PMI-USERNAME PSERV,CHAR PREFERRED CHAR,UPPER PRIVFAX# DNOREAD,CHAR PRIVILEGES CHAR,UPPER,PSUPER,HIDE PRIVTEL# DNOREAD,CHAR REMARK CHAR SMS# DNOREAD,CHAR SMTP PSERV,CHAR,LOWER,UNIQUE STAND-IN...
  • Page 61 System Architecture The Mask Description Language MDL KEYWORD CHAR CHAR,UNIQUE,UPPER CHAR,UNIQUE,UPPER NAME CHAR PREFERRED CHAR,UPPER PRIVFAX# DNOREAD,CHAR PRIVTEL# DNOREAD,CHAR REMARK CHAR SMS# DNOREAD,CHAR SMTP CHAR,LOWER,UNIQUE VOICE# DNOREAD,CHAR,UNIQUE CHAR $end $mask USER NAME ####################################################### PASSWORD ################################ PIN ################ PRIVILEGES ################################ GROUP ######################## PREFERRED ####################################################### MAILBOX...
  • Page 62 System Architecture The Mask Description Language MDL #################### #################### PRIVTEL #################### PRIVFAX #################### PHONE #################### $attrib ADDR1 CHAR ADDR2 CHAR CHAR,UNIQUE,UPPER CHAR CITY CHAR COMPANY CHAR COSTINFO CHAR COUNTRY CHAR DIVISION CHAR DNO,PSUPER,HIDE,CHAR,UNIQUE EFT# DNOREAD,CHAR EXCH CHAR,UNIQUE,UPPER FAXG3 DNO,PSUPER,HIDE,CHAR,UNIQUE FAXG3# DNOREAD,CHAR,UNIQUE FAXG3-HEADLINE CHAR...
  • Page 63 System Architecture The Mask Description Language MDL In the first portion ($mask) the mask layout is first “sketched”. The use of TAB’s is not allowed. The only rule is: the place holders (#-characters) must always follow and be on the same line as the field names. In the second portion ($attrib) an attribute is declared for each field.

  • Page 64: User And Short Database Fields Of Special Significance

    System Architecture USER and SHORT Database fields of special significance Attribute Significance The contents in this field are encrypted. KRYPT Only lowercase characters. LOWER Can only be modified by a user with Service privileges. PSERV Can only be modified by a user with Supervisor privileges. PSUPER Can only be modified by a user with User privileges.

  • Page 65: Distributed Mrs Server

    System Architecture Distributed MRS Server Field Significance Bit coded user privileges. In addition to the user privileges for PRIVILEGES this field are the privileges of the user defined as group GROUP. This entry corresponds to the key USER in group name. Privi- leges are currently coded in HEX.
  • Page 66 System Architecture Distributed MRS Server without Security The following steps should be followed: For a secure installation all services with an account must be started since the default system account has no access to the network. This account must have the privilege LogOnAsService and network access authorization.

  • Page 67: Firewalls Between Nodes Of A Distributed Mrs

    System Architecture Distributed MRS Server The Key HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\MRS Globals must be manually reproduced on all participating computers. This Key contains all the information that must be known for all MRS operations. The NameLoc can be started on the satellite system in the following manner: NameLoc addnode -kernel=<Kernel-Computer>...

  • Page 68: Remote System Link With A Nvs 2.20 Server

    System Architecture Remote System Link with a NVS 2.20 Server 2.10 Remote System Link with a NVS 2.20 Server For Remote System Links to a NVS 2.20 Server, the following settings are required by the MRS Server under the Key HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\MTA\ RemoteSystemLinks GlobalLink=0...
  • Page 69 System Architecture CIT – Computer Integrated Telephony When the signal is to be set, the MTA queries the database for the existence of the field CIT_<Service>, over which the incoming message is delivered. For the service Fax G3 this would be the database field CIT_FAXG3. If this database field is missing or not filled in for the user, the database field CIT would be checked.

  • Page 70: Counter Based Cit

    System Architecture CIT – Computer Integrated Telephony 0172234323 Here Mayer also receives a SMS message for each incoming message. A fax from FAXG3/2343223 is received for NVS:NODE/MAYER. User Mayer has in the database the following entries: USER MAYER CIT_VOICE SMS/0172234323 CIT_BASIC/23432 Mayer receives a SMS message for every incoming Voice-Message.

  • Page 71: Quotas

    System Architecture Quotas To switch on the counter based CIT the configuration dialog for the MTA must be opened in the MRS Monitor. In the tab Advanced should be selected and subsequently the button CIT Cache. In this dialog the option CIT reset when all messages are read or deleted must be activated.

  • Page 72: Transactions

    System Architecture Transactions Secondly, these two fields must be added to the database templates PROFILE and USER. Examples for this can be found in the section User Database Adaptations on page 347ff. QUOTA ############ QUOTAUSED ############ With the attribute: QUOTA CHAR,PSUPER QUOTAUSED CHAR,PSUPER...

  • Page 73: Server Based Computer Telephony Integration (Cti)

    System Architecture Server based Computer Telephony Integration (CTI) Transaction Usage Activates device rerouting. DIVERSION Blind transfer of a call to another device. FORWARD Hold. HOLD Sets monitor point. MONITOR Outgoing call set-up. PHONECALL State request from a telephone device. PHONESTATE Device type e.g.

  • Page 74: How The Watchdog Functions

    System Architecture Watchdog Processes The standard ‘Windows NT configuration does not immediately terminate a process due to an exception error. Instead, a dialog box is displayed informing the user of the error. During this time the failed process is still resident in the memory and the Watch- dog prohibits restarting of the process until confirmation by the user has been given.

  • Page 75: Watchdog Configuration

    System Architecture Watchdog Processes more than three crashes occur within an hour the Watchdog will no longer try to restart the server. To allow a cluster system (e.g. MSCS or VINCA) sufficient time to correct a problem itself, a waiting period can be configured before the APL or the MRS Server attempts restart.

  • Page 76: Speech Syntheses (Sapi)

    System Architecture Speech Syntheses (SAPI) manently shut-down from there. When shut-down temporarily, the Watchdog will always be automatically restarted when the MRS Server is restarted. 2.16 Speech Syntheses (SAPI) In addition to the Text-to-Speech module from Lernout&Hauspie the MRS Server also supports the standardized Microsoft interface Speech API for speech syntheses.

  • Page 77: Access Control Lists (Acl)

    System Architecture Groups 2.17.2 Access Control Lists (ACL) Access Control Lists are groups with a special <AttributeName>: DOMAIN CLASSNAME CLASS KEYNAME <Domain> GROUPATTR <Object> PERMISSION <AttributeValue> <Domain> <Object> <Access><Unique-ID> <Member> GROUP <Domain> <Object> G<Access><Unique-ID> GRP:<Group> GROUP <Object> is formed from #<Object Class> - <Object ID>...

  • Page 78: Tools

    System Architecture Tools All members of the group SUPERVISOR have full access to all telephones within the company. MARY has only the Read privilege and may only e.g. query a status. ACD Group DOMAIN CLASSNAME CLASS KEYNAME MYSERVER GROUP HOTLINE 12321 MARY MYSERVER GROUP...

  • Page 79: Kernel Registry Components

    System Architecture Kernel Registry Components would be used to copy a user database to the remote NT server \\BIG. Correlation data records can be deleted with the InfoTool by importing a file with the special KEY <<<DELETE>>>. In the following example the fax G3 address of user TEST would be deleted.
  • Page 80 System Architecture Kernel Registry Components HKEY_LOCAL_MACHINE\SOFTWARE\PP-COM\MRS\MRS Globals AdminAccount REG_SZ Windows NT Account Windows NT account used for installations with security options. This account is also used for starting services on non-kernel computers within a Distributed sys- tem. BackupDirectory REG_SZ Directory Backup directory.
  • Page 81 System Architecture Kernel Registry Components FastAsyncKernelShutdown REG_DWORD 0 or 1 All services are simultaneously shut-down when Windows NT is shut-down. Dependency is not taken into consideration when used. The database is securely shut-down, but some losses may occur if e.g. the MTA needs to write to the data- base.
  • Page 82 System Architecture Kernel Registry Components MirrorDirectory REG_SZ Directory Optional mirror directory for the documents directory. All documents are mirrored within this directory. Example: g:\mrs\mirror MrsBuildNumber REG_SZ This string contains the internal Build number of the MTA. MSClusterNodes REG_SZ The names of computers on which InfoStor can run are entered here with an MRS Server installed on a Microsoft Cluster Server.
  • Page 83 System Architecture Kernel Registry Components ServiceStartDelay REG_DWORD Seconds Time period in seconds in which the MRS Administrator waits before starting the Nameloc and other MRS Services. This is used when the automatic server start does not function when the computer is started, and a report is generated that the kernel module Nameloc could not be started.

  • Page 84: Converter

    System Architecture Kernel Registry Components TransportFormats REG_SZ The formats listed here are recognized by the router as valid for the SMI Transport MAILBOX, TCPIP, SPX, PIPE, ISDNSMI and MODEM. If the option Multidoc- Client is set to 1 then the format PMF would also be appended to the default list as an additional format.
  • Page 85 System Architecture Kernel Registry Components HKEY_LOCAL_MACHINE\SOFTWARE\PP-COM\MRS\MRS Globals\ Converter AllowPartialConversion REG_DWORD Send only if document (Multi Format Document (PMF)) and all attachments can be converted (0). Otherwise send document without reference to missing pieces (1). Default: 0 AlwaysDefaultLanguage REG_DWORD 0 or 1 With voice mails MRS attempts to recognize the language of a text to be given out (see DefaultLanguage).
  • Page 86 System Architecture Kernel Registry Components DDESleep REG_DWORD Milliseconds The application converter prints documents per DDE call-up for which some appli- cations require more time. Therefore waiting time is inserted after the call-up which works with all known installations. Some very slow computers may require the definition of an even longer waiting time.
  • Page 87 System Architecture Kernel Registry Components fontWeight REG_DWORD Font weight with text to fax conversion. This is meaningless when fax templates resp. cover pages are used since it is already implicitly included there. LogoGroup REG_MULTI_SZ The MRS user account and originator address are given per line and are separated by comma.
  • Page 88 System Architecture Kernel Registry Components the first page to fax using the printer driver. In this case the value should be increased. More likely is that during the conversion by the MTA Service, the application (e.g. WinWord) itself is used by the MTA to convert the document to a fax. It is possible through interaction that a dialog box appears and at this point the print- ing operation is blocked until the time-out has expired.
  • Page 89 System Architecture Kernel Registry Components PcmIsEurope PcmIsWave Voice-Ressource format µ-Law Wave. Compatibility mode for older QNX Servers. a-Law Wave. Default: 1 PrintTextfileWithProgram REG_MULTI_SZ Documents whose extensions are listed here, will not be faxed as text documents, but over a program to a fax printer. Examples are documents in RTF (Rich Text Format) or HTML (Hypertext Markup Language) who’s formatting instructions are contained in the text.

  • Page 90: Fax Printer Applications

    System Architecture Kernel Registry Components Since Fax G4 enables a higher resolution this effect consequently occurs rarely and a conversion from Fax G4 to Fax G3 does not effect the page composition. There- fore files can be extended by means of a fax conversion to G4. In this case the preset 200 dpi need to be replaced by a higher value of course.
  • Page 91 System Architecture Kernel Registry Components Line Value 0 or 1. With the value 0 no application conversion can be performed for the further specified file extensions. This is possible with 1. 0 or 1. With the value 0 the method “Print”, with 1 the method “PrintTo”...

  • Page 92: Licenses

    System Architecture Kernel Registry Components .lwp Thus allowing the application conversion for documents with the file extension “.lwp” with method “Print” command entered under HKEY_CLASSES_ROOT\WordPro.Documentshell\Print\command 2.19.5 Licenses The following Values are found in the Key HKEY_LOCAL_MACHINE\SOFTWARE\PP-COM\MRS\ MRS Globals\Licence Licenses REG_MULTI_SZ List of the installed licenses.
  • Page 93 System Architecture Kernel Registry Components MRS Globals\Location AccessCode REG_SZ This number is taken as default for ISDN resp. modem connection. Individual con- figuration is possible for ISDN resp. modem access. Example: 123456 AreaCode REG_SZ Area code without preceding zeros. Number is taken as default for the ISDN resp. modem connection.
  • Page 94 System Architecture Kernel Registry Components DateFormat REG_SZ Template Template is date display format which is comprised of various Tokens: Token Description Possible Values Day of Week [‘Sun’ .. ‘Sat’] [1..31] Month [1..12] Month [‘JANUARY’ .. ‘DECEMBER’] Month [‘January’ .. ‘December’] Century [19..20] Year...

  • Page 95: The Router

    System Architecture Kernel Registry Components MaxInternalLength REG_DWORD Maximum length of an internal dialing number. All numbers longer than the Max- InternalLength will be interpreted as an international dialing number and normal- ized as such. Default: 6 Normalize_UseExtLinePrefix REG_DWORD When set to 1 the DialNumber-Processor should also interpret “internally dialed” numbers, as well as those with outside dialing numbers.
  • Page 96 System Architecture Kernel Registry Components AddSendJournalToQuota REG_DWORD 0 or 1 The send journal is also evaluated in Quota computations. Default: 1 AccountingDatabase REG_DWORD 0 or 1 When set to 1 charge information is written to the GEB database. Default: 0 AutolearnAllfromProperty REG_DWORD 0 or 1 This option should be set to 1 in the event that no user data under MRS is to be administered, and personal fax ID’s are desired for fax receipt.
  • Page 97 System Architecture Kernel Registry Components NVS:NODE.CLASS/USER would then be transformed to NVS:NODE.CLASS@SSSTTT/USER SSS are the first three letters of the server name. TTT are the first three letters of the transport name. Example: In the remote system PERGAMON the line NVS:FAXG3.1 exists. This would be imported twice by the remote system link.
  • Page 98 System Architecture Kernel Registry Components scripts or referenced in the registry key per $(LIFETIME). The value in Docu- mentLifeTime specifies the age limit, so that a document may be deleted by the standard script. Default: 60 DocumentLifeTimeCompress REG_DWORD 1 to 1000 Maximum document life in days.
  • Page 99 System Architecture Kernel Registry Components File Systems REG_MULTI_SZ List of the directory tree over which MRS clients access the MRS file system. The directory /update is used for the automatic Client Software Update, / userdata contains individual user data (cover sheets, voice files, etc.), / logging contains MRS log files.
  • Page 100 System Architecture Kernel Registry Components MaintenanceActive REG_DWORD 0 or 1 Via this value you can deactivate the execution of the maintenance script. The script is performed by default. Default: 1 MaintenanceDontTouch REG_DWORD 0 or 1 The DELDB function changes the ’modification time’ of all files in the document folders so that the remove function of the maintenance task is under no circum- stances able to delete files before their expiry date.
  • Page 101 System Architecture Kernel Registry Components MaxHopCount REG_DWORD Maximum number of hops before mail is destroyed to prevent recursion. This value must be set high for complicated switching. Default: 0xA MaxLockTime REG_DWORD Seconds Maximum time a journal entry is allowed to be locked. Default: 0xC MaxPrivateRules REG_DWORD Maximum number of private rules that users can define.
  • Page 102 System Architecture Kernel Registry Components Default: 1 MonitorMemoryUsageAlerts REG_DWORD 0 or 1 Memory surveillance (1) with alert by memory shortages Default: 1 MultiAddresses REG_MULTI_SZ Normally this will restrict the router since a document is sent twice to a single address (e.g. two faxes to 02404906610). With some addresses it may be meaning- ful to allow simultaneous transmission.
  • Page 103 System Architecture Kernel Registry Components PredictiveConversionBeforeRout REG_DWORD 0 or 1 This value is intended for future extensions and currently meaningless. ProxyOpenDelay REG_DWORD Waiting time in milliseconds till the first occurrence of open proxy. Default: 10 ProxyRetryDelay REG_DWORD Waiting time in milliseconds till a new attempt is made to open the proxy pipe. Maximum number of attempts is 10.
  • Page 104 System Architecture Kernel Registry Components RemovePropertiesOnCarbonCopy REG_DWORD 0 or 1 When a carbon copy of a message is generated, the message´s properties fields are normally deleted on the copy. If you wish to retain these fields, alter the default setting of this value. Default: 1 RepeatStandardDeviation REG_DWORD 0 to 100 Standard deviation for kernel repeat strategy.
  • Page 105 System Architecture Kernel Registry Components SystemStartDelay REG_DWORD The MTA is idle for SystemStartDelay seconds before the APL’s are enabled. After a further SystemStartDelay seconds the system is running for the MTA and generates the message “system up”. Default: 60 UnSecureSMI REG_DWORD 0 or 1 Execution of forced validation on SMI transporters.

  • Page 106: Autoreporter

    System Architecture Kernel Registry Components nificantly lags behind in most cases, the VBS support in Outlook should be switched off. A list of possible formats is found on page 391 Default: BIN WriteLoginStat REG_DWORD 0 or 1 Current login statistics from client users are written to the correlation database when set to 1.

  • Page 107: Cit - Computer Integrated Telephony

    System Architecture Kernel Registry Components EVENTLOG type, writes the correspondingly matching log entries in the Windows Event Log.Two classifications of types are additionally available: LOG collects all log entries and sends them to the recipient. ACTIVE immediately sends all mes- sages as long as they conform to the log entry filter conditions.
  • Page 108 System Architecture Kernel Registry Components CitCounter REG_DWORD 0 or 1 Counter based CIT switch on (1). Default: 0 CitMessage REG_SZ Standard message by text capable CIT protocols (e.g. SMS). The text may contain following variables: Variables Significance Date {DATE} A portion of the text message is embedded in the {DIGEST[,<Max>]} CIT notification.
  • Page 109 System Architecture Kernel Registry Components Variables Significance Time {TIME} Example: {ORGNODE} message received from {ORGUSER} at {TIME}. CitMessageFile REG_SZ Voice file used for CIT notification per ISDN voice protocol. CitMessageMode REG_DWORD CIT notification mode: Mode Significance Text message Voice file CitUserBasedMessage REG_DWORD 0 or 1 The voice resp.

  • Page 110: Line Cache

    System Architecture Kernel Registry Components MaximumCacheTime REG_DWORD Seconds Maximum CIT cache time. Default: 0xe10 MinimumCacheTime REG_DWORD Seconds Minimum CIT cache time. Default: 0x3c NoCitOffSignal REG_SZ Protocols where a CIT reset is not required. Default: SMS,VOICE 2.19.10 Line Cache The following Values are found in the Key HKEY_LOCAL_MACHINE\SOFTWARE\PP-COM\MRS\MTA\LineCache CacheActive REG_DWORD 0 or 1 MTA line cache on (1) or off (0).
  • Page 111 System Architecture Kernel Registry Components AutoBiDirectionalLinks REG_DWORD 0 or 1 Remote system links are always directional. If a system builds a remote system link to another remote system, then mail can be sent to the remote system, but not received. If AutoBiDirectionalLinks 1 is entered then is the link automatically bi- directional.
  • Page 112 System Architecture Kernel Registry Components address book replication, and the optional imported logical line, all separated by a semicolon. The best method of configuring a remote system link is through the MTA configu- ration in the MRS Monitor. Example: NVS:TCPIP/NVS20PPC;CSync=120,10;Rep=3;Pwd=3701913046;OPT=TIME NVS:ISDNSMI/4924049066530;CSync=86400,30;Rep=3;Pwd=0;Prot=NVS:TXSF Every 120 seconds a connection attempt is made to system NVS20PPC over TCP/ IP transport.

  • Page 113: Routing Rules

    System Architecture Kernel Registry Components RemoteLocalServices REG_DWORD If the option “Adapt routing information” is selected, the information contained in the PREFERRED field of the remote system local user database would be incorpo- rated for routing to the user during the address book replication. Example: The database record “USER XYZ PREFERRED TCPIP”...
  • Page 114 System Architecture Kernel Registry Components AwakeCustomBackup REG_MULTI_SZ Possible storage of a user defined set of awake rules. If during the setting of the MTA, a different set of awake rules is installed, these rules would be stored here. A later resetting of the user defined rules would assume these values. AwakeType REG_DWORD Internal awake rules type.
  • Page 115 System Architecture Kernel Registry Components CarbonMode REG_SZ No carbon copies will be created without an entry. This value defines when a value in the carbon copy rules should be applied. The following values may be entered multiply and separated by a comma: Value Significance Apply to every document transmission...
  • Page 116 System Architecture Kernel Registry Components first (before routing is performed!) converted to FG3. If e.g. Microsoft Word documents were sent to the fax number of an MRS user, they would be transmit- ted as fax though due to routing optimization they would actually not be con- verted.

  • Page 117: Services

    System Architecture Kernel Registry Components Value Significance FMS routing through the FMS address book 2.19.13 Services The following Values are found in the Key HKEY_LOCAL_MACHINE\SOFTWARE\PP-COM\MRS\Services Access Protocol Layers REG_MULTI_SZ List of the installed MRS APL’s. As soon as the kernel is successfully started, the MRS administrator will uses this list to start-up the system.

  • Page 118: Database

    System Architecture Kernel Registry Components Recover-<NT-Name>-<Service> REG_MULTI_SZ These commands are executed by the Watchdog prior to the restart of a <Service> on the computer <NT-Name> in a distributed MRS Server. One command may be entered per line. Recover-<Service> REG_MULTI_SZ These commands are executed by the Watchdog prior to the restart of a <Service>. One command may be entered per line.
  • Page 119 System Architecture Kernel Registry Components CreateDnoAliases REG_DWORD 0 or 1 Flag between Setup and Infostor. When set to 1, ISDN dialing numbers are auto- matically included by the import of user data on a Windows NT domain. For these purposes the ISDN defined dialing areas are used. CreateMailAliases REG_DWORD 0 or 1 Flag between setup and Infostor.

  • Page 120: Important User Accounts

    System Architecture Kernel Registry Components Example: g:\mrs\InfoStor\Log MaintenanceDelay REG_SZ This entry corresponds with the Maintenance Priority slide control for performing the Maintenance Script in the MTA configuration of the MRS Monitor. MaxLockTime REG_DWORD Seconds Maximum lock time for journal database entries. Default: 0x3c 2.19.15 Important User Accounts The following Values are found in the Key...

  • Page 121: Name Locator

    System Architecture Kernel Registry Components 2.19.16 Name Locator In addition to the installation of a Distributed Server as described on on page 67, two other possibilities are available for the Registry Replication of the sub-tree MRS Glo- bals. One method is the Registry PushTime activate periodical replication, and the other through MonitorRegistry Changes of a replication when the kernel computer has changed something in the sub-tree.

  • Page 122: Xmrsvc

    System Architecture Kernel Registry Components When set to 1 the LocalSystemList is searched for other Name Locator instances. 2.19.17 XMRSVC The following Values are found in the Key HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\XmrSvc AutoReportFilter REG_MULTI_SZ Filter for the active alert reports generated by the MTA. The MTA uses the log entries generated by the MRS Server and passes through this filter for its active alert reports when they meet the criteria of its own filter.
  • Page 123 System Architecture Kernel Registry Components Default: 1024...
  • Page 124 System Architecture Kernel Registry Components...

  • Page 125: Telereg Api

    System Architecture TeleReg API 3 TeleReg API The TeleReg API administers registry entries for Telematic APL’s. The TeleReg API is used by the Dialogic, ISDN, and Gamma APL’s. The TeleReg API provides a uni- form configuration for these telematic APL’s, and a similar method of installation. Configuration data is transferred between the MRS Server and the MRS Monitor in a compressed form so that faster data transfer rates are achieved when performing Remote Administration over modem lines.
  • Page 126 System Architecture Registry Entries CLIMode REG_DWORD 0, 1 or 2 Calling Line Identification. When an entry in the user database field CostInfo exists, this information would be taken as default (2). If no entry exists, the exten- sion number of the user would be used as the CLI (1). If in addition to the exten- sion number the complete normalized international of the user is to be sent as the CLI, the mode 0 must be set.
  • Page 127 System Architecture Registry Entries FaxLicences REG_DWORD This is the number of allowable fax channels. Since this value is provided with licensing key, modification of this entry could result in a license infraction mes- sage. Example: 12 FaxResources REG_DWORD Number of fax channels as determined by hardware recognition. LineLicences REG_DWORD Number of allowed lines.

  • Page 128: Blobs (Binary Large Objects)

    System Architecture Registry Entries VoiceResources REG_DWORD Number of voice resources (Full Duplex Voice Channels) as determined by hard- ware recognition. During the configuration the number of found resources will be entered in LineLicences 3.1.2 Blobs (Binary Large Objects) Every registry entry administered by the TeleReg API may contain a 1reference to a Blob.
  • Page 129 System Architecture Registry Entries Status (Bit set) 0x0008 Device can poll documents from fax on demand servers. 0x0010 Device can function as a fax on demand server. 0x0020 Device can send and receive fax G4 documents. 0x0040 Device can poll fax G4 documents from fax on demand servers.
  • Page 130 System Architecture Registry Entries PrefixedANI REG_DWORD 0 or 1 When set to 1 the number (Automatic Number Identification (ANI)) is used with the prefixed digit for outside dialing from the device. This information is required for uniform charge cost information gathering. Default: 0 Private REG_MULTI_SZ Private data.

  • Page 131: Lines

    System Architecture Registry Entries Example: 0x11 Type REG_DWORD Device Type Type Device type -Device (Primary Rate Interface (PRI)) -Device (Basic Rate Interface (BRI)) Analog device Unknown device 3.1.4 Lines A line is defined as a physical bidirectional communication channel. With S ISDN- Boards this could be up to 30 Lines.

  • Page 132: Extension Number Ranges

    System Architecture Registry Entries Cost REG_DWORD Cost per charge impulse as of the local currency. Default: 12 EndChannel REG_DWORD End value when only a portion of available physical channels are used. NumChannels REG_DWORD Maximum NumChannels used in this line bundle. OAD REG_DWORD Every line is assigned a number (Originator Address, (OAD)).
  • Page 133 System Architecture Registry Entries special lines. This could be implemented so that incoming fax documents are routed to a special line (OAD). It the board delivers an ISDN Service Indicator it will be checked against a list of applicable protocols. A minimum of one extension number is required for a supported service.

  • Page 134: Originator Address

    System Architecture Registry Entries VarDigits REG_DWORD 0 oder 1 Extension numbers in this extension range may have a variable amount of digits when set to 1. Calls with less digits would also be taken after a short waiting period for the next digit. By voice applications it is helpful that the extension can be of varying length.
  • Page 135 System Architecture Registry Entries Example: 2404 AreaCodeEscape REG_SZ National dialing number and parallel to the Value found in Software\PP-COM\MRS\MRS Globals\Location When set this value will be used instead of the global value. Example: 0 Blob REG_DWORD Index number of the used Blob data range. Default: 0 CountryCode REG_SZ Country code dialing number and parallel to the Value found in...

  • Page 136: Protocols

    System Architecture Registry Entries 3.1.7 Protocols Protocols are supported services from the various APLs. There are various generic ser- vices such as FAXG3, VOICE, or VFS; and branched protocols from generic proto- cols (e.g. outgoing VFS with a coupled Script). Branched protocols may not have a Script assigned to them.
  • Page 137 System Architecture Registry Entries Attribute Significance Store-and-Forward operations for documents is allowed on this line This line may be used as a SMI transport for Client con- SMITR nections or for Remote System Links. This line supports transactions. TRANSACTION Originator validation. VALORG Recipient validation.
  • Page 138 System Architecture Registry Entries DispPerm REG_DWORD Bitmask used for activating graphic user interface and w3indow elements. DocReps REG_SZ Redial strategy. These parameters define how often and in which time intervals a repeat attempt is to be made by the router. The first parameter is the number of attempts that are to be made, and the second the time interval between attempts in seconds.
  • Page 139 System Architecture Registry Entries Chaining functions only within a designated time interval. If for example fax data is transmitted to a fax device then further jobs designated for this device can only be transmitted when the ISDN APL is still sending data to the ISDN card. If the data has already been transmitted to the ISDN card, then disconnect-phase has been initiated and further chaining is not possible.
  • Page 140 System Architecture Registry Entries allowed by the protocol. These entries are only valid when the format is set by EditPerm. FriendlyName REG_SZ User readable protocol name. An unique FriendlyName must be entered for each protocol. Example: Fax Group 3 Headline REG_SZ Default fax G3 headline which appears on the top of every fax page.
  • Page 141 System Architecture Registry Entries Type REG_DWORD Protocol type. Type Protocol Unknown protocol type Fax G3 transmission and receipt Fax G3 poll (call-back) Fax G3 Fax-on-Demand Server Fax G4 Euro-File-Transfer Server Euro-File-Transfer Client Voicemail transmission and receipt Scripted protocol based on the language D Scripted protocol based on the language E Scripted protocol based on the language GSM Message Waiting Indication...
  • Page 142 System Architecture Registry Entries...

  • Page 143: Isdn Apl

    System Architecture ISDN APL 4 ISDN APL The ISDN APL provides the MRS System with all available ISDN telematic services. In particular: Fax group 3 transmission and receipt Operation as fax concentrator (fax-fax conversion protocol) Fax group 4 transmission and receipt ISDN Teletex transmission and receipt Voice file transmission Euro file transfer server and client...

  • Page 144: Siemens Cornet-N Support

    System Architecture Siemens Cornet-N Support Eicon Server PRI Hypercope Hysdn Central4 Hypercope Hysdn Metro4 Only cards of a single manufacturer should be installed on the MRS Server. When more than one ISDN card is to be installed in the server it is also suggested that the cards also be of the same type.

  • Page 145: General Entries

    System Architecture Registry Entries In the following, only those additional registry entries for the TeleReg API will be dis- cussed. The registry entries of the TeleReg API are correspondingly marked and described in Chapter 3 of this manual. 4.3.1 General Entries The following Values are found in the Key HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\IsdnApl ALawCoding REG_DWORD 0 or 1...
  • Page 146 System Architecture Registry Entries DestNumberPlan REG_DWORD (TeleReg) See page 126. DestNumberType REG_DWORD (TeleReg) See page 126. DialInfoTimeout REG_SZ When a MRS computer is called, a period of time in seconds is waited between the numerical input for the desired extension. If the time-out expires the call is then terminated.
  • Page 147 System Architecture Registry Entries DtmfPeriods REG_DWORD 1…5 Number of 15 millisecond periods (1 corresponds to 30 milliseconds, 5 to 90 milli- seconds) in which a DTMF tone is continually recognized, so that it can be reported as recognized. Operational testing has proven that a value of 1 provides optimal results.
  • Page 148 System Architecture Registry Entries plan has been forwarded as “Unknown”. Also here this value then helps bringing to bear the setting made. Default: 0 IncReject REG_DWORD ETSI (DSS1) Reject Code. Default: 0x15 IntlDialMode REG_DWORD 0 or 1 The MRS servers expects all telematic numbers (more than 9 digits) to be in an international format (1).
  • Page 149 System Architecture Registry Entries MaxG3Speed REG_DWORD Maximum transmission rate of a G3 fax document. Attention should be given when configuring ITK fax G3 piggys. Those labeled 14400 should only be ran at 9600 for error free operation. The default value must be modified. Value Significance Maximum Transmission rate...
  • Page 150 System Architecture Registry Entries Default: 0x80 PrioThread REG_DWORD Priorities of several special threads that administer board events. This value must not be modified. Value Thread-Priority Highest Above Normal Normal Below Normal Lowest Default: 1 QueryBilling REG_DWORD (TeleReg) Activates/Deactivates billing option. See page 127. Default: 1 Restart REG_DWORD 0 or 1 When an error occurs the internal Watchdog will restart the card driver when set to...
  • Page 151 System Architecture Registry Entries Otherwise the entry exists only for compatibility reasons and should be deleted in favour of the private entry. SimulResDw REG_SZ Special switch used by quality assurance for error simulation. SmsProviderList REG_MULTI_SZ List of SMS Protocol accesses. Each line indicates the respective access number, the first digits of the dialing number and the accessible protocols.

  • Page 152: Blobs (Binary Large Objects)

    System Architecture Registry Entries VoiceResources REG_DWORD (TeleReg) Number of detected full duplex voice channels. See page 128. WaitForGeb REG_SZ 0 or 1 Should always be set to 1. The ISDN APL waits until charge cost information has been received before releasing a logical line. Default: 1 4.3.2 Blobs (Binary Large Objects)
  • Page 153 System Architecture Registry Entries Handle REG_DWORD (TeleReg) Unique CAPI handle used internally. See page 129. Lines REG_DWORD (TeleReg) Number of logical lines. See page 129. Name REG_SZ (TeleReg) Board description. This entry is also used for display in the MRS Monitor. This entry may not be modified! See page 129.

  • Page 154: Lines

    System Architecture Registry Entries Value Significance DebugItk Special internal debugging switch for ITK ISDN cards (1). Connects a D-channel monitor. DirectLine This value must be set to 1 for mixed ISDN card operation, for PBX and ISDN cards that are connected directly to the exchange.

  • Page 155: Extension Number Ranges

    System Architecture Registry Entries an enumerated Key_m is found for each line on a board. In these Keys the following Values are found:. Baudrate REG_DWORD (TeleReg) Transmission rate of the line. See page 131. Blob REG_DWORD (TeleReg) Index number of the Blob data range. Default: 0 BoundProtocols REG_DWORD (TeleReg)
  • Page 156 System Architecture Registry Entries If the board delivers an ISDN Service Indicator it will be checked against a list of applicable protocols. A minimum of one extension number is required for a supported service. These ser- vices are numbered and stored with their number under the Key HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\ISDNApl\Extensions as a separate Key.

  • Page 157: Originator Address

    System Architecture Registry Entries 4.3.6 Originator Address Every line is assigned a number (Originator Address, (OAD)). The TeleReg APL administers all available OAD numbers as enumerated Keys_n (01, 02, 03, …) under the Key HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\ISDNApl\OADs. These OAD numbers are used to determine the extension number from an incoming call.

  • Page 158: Protocols

    System Architecture Registry Entries 4.3.7 Protocols Protocols are a supported services from the various APLs. There are various generic services such as FAXG3, VOICE, or VFS; and branched protocols from generic proto- cols (e.g. outgoing VFS with a coupled Script). Branched protocols may not have a Script assigned to them.
  • Page 159 System Architecture Registry Entries EditPermGenerated REG_DWORD (TeleReg) The same as EditPerm but only for use with generated protocols (those created by other protocols). See page 138. FaxG3Chain REG_DWORD (TeleReg) Document chaining. See page 138. Default: 1 FaxG3Resend REG_DWORD (TeleReg) This switch determines whether a fax messages is resent due to an interruption. See page 139.
  • Page 160 System Architecture Registry Entries ParamBlock REG_SZ (TeleReg) Script parameters are given here. Private REG_MULTI_SZ (TeleReg) Private data. The ISDN APL uses this entry parallel to that of the INI configuration file under Windows 3.1. Depending upon the protocol, one protocol specific parameter is used per line (Value =…).
  • Page 161 System Architecture Registry Entries Fax G3 Value Significance CheckPageNumbers When set to 1an OK report is only sent when the number of sent pages reported by the CAPI driver corresponds to the number of pages in the document. Otherwise it would be possible to receive an “OK (2 pages sent)”...
  • Page 162 System Architecture Registry Entries Value Significance FfuSendOkRep When set to 1 an receipt report will be sent to the transmitting device from the MRS Server by success- ful transmissions in Fax Forward mode. FfuSendRundRep When set to 1 an receipt report (with all recipients) will be sent to the transmitting device from the MRS Server by successful transmission of a distribution list in Fax Forward mode.

  • Page 163: Voice & Fax-On-Demand Systems

    System Architecture Registry Entries Value Significance RecordTime Maximum recording for incoming messages in sec- onds. Default: 120 RemoteRecord When set to 1 the remote recording mode is activated. Deactivate with 0. StorePath Path to where Remote Recorded files are stored. PrivateMode REG_DWORD (TeleReg) Not used by the ISDN APL.
  • Page 164 System Architecture Registry Entries AclInternLen REG_DWORD Together with AclInternLenMax, an extension number range is fixed. This is the minimum length of the extension number range. If the server is called and the length of the caller ID is within the range between AclInternLen and AclIntern- LenMax, the ACL-function would be used and the display text displayed on the callers telephone.
  • Page 165 System Architecture Registry Entries which the log file are stored. <log-intervall> is interval at which new log files are created. Allowable are: Parameter Significance <x>D Every <x> days is created. <x>M Every <x> months is created. <x>h Every <x> hours is created. <x>m Every <x>...
  • Page 166 System Architecture Registry Entries Prgn=<Skriptname> <Parameter> Definition part Significance The actual Value whose contents will be explained in Prgn the following. Each script has an index n beginning with 1. A maximum of 16 scripts may be entered. <Scriptname> Script file name. <Parameter>...

  • Page 167: The Amis Protocol

    System Architecture The AMIS Protocol UseSpr REG_DWORD 0 or 1 Use speech recognition (1). XmrTopic REG_DWORD 0 or 1 Topic areas “VFS” not displayed by the ISDN APL in the MRS Monitor 0. Default: 1 4.4 The AMIS Protocol The Audio Messaging Interchange Specification (AMIS) is a protocol developed by the Electronic Messaging Association (EMA) for the exchange of voice messages between two dissimilar voice messaging systems.

  • Page 168: Configuration Of Amis Mailboxes

    System Architecture The AMIS Protocol The system number is comprised of these three parameters which the transmitting server conveys to the receiving server. Through use of the system number, non- delivery notifications can be sent to the originating server if necessary. Therefore it is important that the subscriber number in the extension defined for amis.c also be included.

  • Page 169: The Skript Dialer.c

    System Architecture The Skript dialer.c other AMIS server and <Mailboxnumber> the 1-16 digit AMIS-mailbox number of the recipient: Example: NVS:AMIS/4912345678#4711. To avoid having to continually enter long addresses, an alias (short) list can be config- ured for frequently used addresses. In the PREFERRED simply enter AMIS, and in the field AMIS the address information.

  • Page 170: What Are Redirected Numbers Aka Redirecting Numbers

    System Architecture What are Redirected Numbers aka Redirecting Numbers? default path (<MRSDIR>\res\vfs\dialer) would be used. The output would then be in the German language. Language Path German <MRSDIR>\res\vfs\dialer English <MRSDIR>\res\vfs\dialer\uk French <MRSDIR>\res\vfs\dialer\france Spanish <MRSDIR>\res\vfs\dialer\spain <MRSDIR> is the directory in which MRS is installed. LogName<n>...

  • Page 171: Why Are Not All Isdn Boards Suitable For Redirected Numbers

    System Architecture What are Redirected Numbers aka Redirecting Numbers? The PBX must support this method. The Voicemail Script must be capable of it as well. 4.6.1 Why are not all ISDN Boards suitable for Redirected Numbers? The delivery of Redirected Numbers to an application is embodied in the CAPI speci- fication but the implementation is up to the individual board manufacturer.

  • Page 172: Are There Any Known Problems With Pbxs

    System Architecture What are Redirected Numbers aka Redirecting Numbers? 4.6.4 Are there any known problems with PBXs? Siemens´ Hicom 300E does not transmit the Redirected Number as expected. With this PBX a different method, not evaluated by ISDN boards, is employed. It is, however, possible to use ISDN boards by Eicom.

  • Page 173: Dialogic Apl

    System Architecture Dialogic APL 5 Dialogic APL The Dialogic APL administers the integration of the Dialogic communications hard- ware in the MRS Server. Dialogic is one of America’s leading manufacturers in com- puter supported telephony and fax. When several Dialogic boards are used in conjunction, they can be coupled with one another through use of a ribbon cable to enable rapid communications between each other, and to free the CPU for other tasks.

  • Page 174: Functionality

    System Architecture Functionality tion. The BNC is used in conjunction with the DASS2 protocol which is used in England and Russia. Attention: The pin assignment of the RJ 48C is not the same as a standard ISDN RJ 45 connector. Voice and fax resources are connected to the Line Interface through the SC-Bus.

  • Page 175: Softly Terminating The Apl

    System Architecture Softly Terminating the APL 5.3 Softly Terminating the APL The Dialogic APL supports its soft termination via the net pause dlgapl command line instruction. After this command the Dialogic APL does not answer any calls any more while all other existing connections are handled without impairment until their normal termination.
  • Page 176 System Architecture Registry Entries Default: 0 CallRestartErrors REG_DWORD If through the calling of functions from the Dialogic SDK, the number of errors given here is returned, a restart of the CALL modules would be executed. All calls would be automatically interrupted and the physical lines restarted. Default: 10 Checkedn REG_DWORD 0, or 1 The TeleReg-API provides four tupels [(Checked1, CheckName1), …, (Checked4,...
  • Page 177 System Architecture Registry Entries ContinuousRecording REG_DWORD 0 or 1 The Dialogic boards either constantly forward all inbound data to the Dialogic APL (1) or the APL explicitly controlls data polling from the board (0). The former must be set when VFS scripts, speech recognition or software DTMF recognition is used.
  • Page 178 System Architecture Registry Entries ExtFaxRestart REG_DWORD 0 or 1 The external fax service (GammaFax see Checkedn) is stopped and automatically restarted, in order to retain all resources (1). This is occasionally required when an application does not properly shut-down the fax resources. Default: 1 FaxLicences REG_DWORD This is the number of allowable fax channels.
  • Page 179 System Architecture Registry Entries Default: 0x20 PrioThread REG_DWORD Priorities of several special threads that administer board events. This value should not be modified. Value Thread-Priority Highest Above Normal Normal Below Normal Lowest Default: 1 QueryBilling REG_DWORD 0 or 1 This switch is used to activate the billing option (1). If not activated, billing infor- mation is not displayed, even in the case of outgoing calls through the public exchange.

  • Page 180: Blobs (Binary Large Objects)

    System Architecture Registry Entries Default: 0 UseInternalCritical REG_DWORD 0 or 1 When this switch is active a special flag is used for all queries and signalization from data through user I/O functions. This flag signals the upper network layer that it should not wait until a critical section is released by a blocking thread.
  • Page 181 System Architecture Registry Entries PBX systems do not have this function, and in such a case the call must be routed through the public exchange, and therefore these prefixed digits. In a case such as this, the number of prefixed digits must be entered here. Default: 0 Blob REG_DWORD Index number of the Blob data area.
  • Page 182 System Architecture Registry Entries Name REG_SZ Board description. This entry is also used for display in the MRS Monitor. example: D/300SC-E1 PrefixedANI REG_DWORD 0 or 1 When set to 1 the number (Automatic Number Identification (ANI)) is used with the prefixed digit for outside dialing from the device. This information is required for uniform charge cost information gathering.

  • Page 183: Lines

    System Architecture Registry Entries 5.4.4 Lines A line is defined as a physical bidirectional communication channel. With S ISDN- Boards this could be up to 30 Lines. Each line is assigned an Originator Address (OAD), and the same OAD could be used for more than one line. Furthermore, a line is bound with at least one protocol.

  • Page 184: Extension Number Ranges

    System Architecture Registry Entries 5.4.5 Extension Number Ranges All incoming dialed numbers must correspond with its extension in the ranges listed here. So that incoming calls are taken by the Dialogic APL, a protocol must be assigned to the range and bound to a line. Additionally, the line OAD must correspond with that of number range.

  • Page 185: Originator Address

    System Architecture Registry Entries Start REG_SZ Extension number range lower limit. Example: 100 State REG_DWORD See page 182. VarDigits REG_DWORD 0 or 1 Extension numbers in this extension range may have a variable amount of digits when set to 1. Calls with less digits would also be taken after a short waiting period for the next digit.
  • Page 186 System Architecture Registry Entries Attribute Significance Line allows Store-and-Forward documents. Default: AttributesAllowed REG_DWORD Every protocol administered by the TeleReg API possesses attributes. These are bitmasks which contain the attributes allowed by the protocol. These entries are only valid when the attribute is set by EditPerm. Blob REG_DWORD Index number of the Blob data area.
  • Page 187 System Architecture Registry Entries EditPerm REG_DWORD Bit masks that allow modification of registry entries by the protocol. Modifiable Registry Entries 0x001 Name 0x002 FriendlyName 0x004 Description 0x008 Attributes 0x010 Formats 0x020 Private 0x040 ParamBlock 0x080 DocReps 0x100 ScriptName Default: 0 EditPermGenerated REG_DWORD The same as EditPerm but only for use with generated protocols (those created by other protocols).
  • Page 188 System Architecture Registry Entries Formats REG_MULTI_SZ List of documents and data formats valid for this logical line. These formats are described in Appendix 24.1 of this manual. Example: TG3 FormatsAllowed REG_DWORD Each protocol administered by the TeleReg API can process certain documents and file formats.

  • Page 189: Voice & Fax-On-Demand Systems

    System Architecture Registry Entries ScriptName REG_SZ File name of the protocol´s Script without extension. Example: SFOD State REG_DWORD See page 182. Type REG_DWORD Protocol Type. Type Protocol Unknown protocol type Fax G3 send and receive Fax G3 polling Fax G3 Fax-on-Demand Server Voicemail send and receive Script based protocol written in the programing lan- guage D...
  • Page 190 System Architecture Registry Entries...

  • Page 191: Ip Apl

    System Architecture IP APL 6 IP APL The IP APL implements an access to protocols analog to telematic APLs such as the ISDN or Dialogic APL. In so far IVR script protocols registered in the IP APL can be used e.g. by means of Voice over IP (VoIP). For that purpose the corresponding extension numbers are passed on to the IP APL in the used gatekeeper.
  • Page 192 The following are commonly used: TAPI 3.0 Is either based on H.323 TSP (e.g. Innovaphone IP 400) supplied by Microsoft with Windows 2000, or the software publisher provides a corresponding TSP for their system, e.g. for Siemens´ Hicom 150 with HG 1500 (Hicom Lan Bridge).

  • Page 193: General Configuration Instructions

    As devices no ISDN boards are available but the installed TAPI service provider. For the time being the following are supported: Cisco TSP Cisco Call Manager Microsoft H.323 TSP Innovaphone IP 400 Siemens HiPath TSP Siemens HiPath 5500 Media Extension Bridge Siemens HG 1500...

  • Page 194: Restart

    System Architecture General Configuration Instructions 6.1.2 Restart In this configuration tab you can decide whether to address a VoIP PBX via TAPI 2.1 with Wave interface or via TAPI 3.0. For TAPI 3.0 the option TAPI 2.1 must be deactivated. 6.1.3 Gatekeeper In the portion Calling a telephone...

  • Page 195: Siemens Hg 1500 Connection

    IP APL to the Innovaphone IP 400 system. The Innovaphone IP 400 is configured via an HTTP interface. In the IP configuration you first need to enter the IP address of Innovaphone IP 400 in the Ethernet Interface portion.
  • Page 196 System Architecture Innovaphone IP 400 Connection Define the MRS IP APL as H.323 gateway with gateway mode Gateway or gateway group (w.o. registration) Enter the MRS Server´s IP address as Remote gateway address . All supported extensions (numbers of voice mailboxes, control mode numbers, …)
  • Page 197 System Architecture Innovaphone IP 400 Connection Enter Innovaphone IP 400 as H.323 gateway called Central Gatekeeper with Gate- way mode Gatekeeper for remote clients . As IP address either enter XXX.XXX.XXX.0 if you want to register the end-points XXX.XXX.XXX.1 to XXX.XXX.XXX.255 at the gatekeeper. Alternatively you can enter 0.0.0.0 in case you want to have all end-points registered at the gatekee-...
  • Page 198 System Architecture Innovaphone IP 400 Connection All routing rules required for a call arriving at or coming from the MRS Server must be entered in the routing table: Example: GW12 -> GW1 : MRS Inbound Call rule -> GW12: MRS Outbound Call rule...

  • Page 199: Ip Apl Configuration

    In the Calling a telephone using TAPI 3 section of the Gatekeeper tab checkmark the Use H.323 gateway option and enter the Innovaphone IP 400 <IP Address>as speci- fied further above in the first step of the Innovaphone system configuration.

  • Page 200: Glossary

    System Architecture Glossary 6.4 Glossary Gatekeeper The gatekeeper is a unit taking on the assignment between IP addresses and telephone numbers. It is thus the central unit required for transition from the common telephone network to the IP network. Example: Cisco “Call Manager 3.0“. H.323 ITU (International Telecommuncications Union) standard for telephony services in packet-switched networks.

  • Page 201: 24 Apl

    System Architecture V.24 APL 7 V.24 APL Clients and servers can be coupled to the MRS Server over the V.24 APL. Further- more, the V.24 APL enables transmission, reception, and operational readiness (Fax- on-Demand Server) of fax G3 over class 2 fax-modems, as well as polling from other Fax-on-Demand servers.
  • Page 202 System Architecture Registry Entries HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\V24Apl ContIntFaxStr REG_SZ This one line message is affixed to fax transmission continuations. Example: Continuation of an interrupted message DefFaxRecipient REG_SZ Default recipient for undeliverable fax documents. Example: POSTMASTER DlgSessions REG_SZ For future dialog service expansions. Default: 16 FaxConnTimeInJrn REG_DWORD 0 or 1 Accumulated connection times for fax document transmissions are listed in the...

  • Page 203: Device Settings

    System Architecture Registry Entries InstalledProtocols REG_MULTI_SZ List of installed protocols for modem triggering. This entry cannot be altered. By each new start of the V.24 APL the list is re-initialized with reference to the avail- able protocol scripts as well as the protocols SMI Transport (Client/Server coupling), Fax G3 (reciept, transmission, and Fax-on-Demand), and Fax G3 Poll (fax polling).
  • Page 204 System Architecture Registry Entries Default: 0 CanVoice REG_DWORD 0 or 1 Voice is supported by the modem (1). This Value is currently non-functional. Default: 0 CountryCodeEscape REG_SZ International prefix. This number is set before the country code of the recipient when an international number is dialed.

  • Page 205: Protocols

    System Architecture Registry Entries This entry is only useful on this position when settings for the ISDN APL are to be configured differently than that global settings under Globals\Location\LocPrefixExtensions. PhoneNum REG_SZ Telephone number of the modem. International prefixes, area codes, PBX number, and the extension of the modem are to be separated with a hyphen Example: 49-1234-5678-90 Protocols REG_MULTI_SZ...
  • Page 206 System Architecture Registry Entries Protocol Description Fax G3 Send/Receive/Fax-on-Demand Server. FAXG3 Fax G3 Poll from a Fax-on-Demand Server. FAXG3REV A General State Machine (GSM) script connection. The fol- GSM,[Script-File] lowing GSM script language protocols are included: cit_basic.sm This protocol allows the setting of a MWI signal over a Siemens Hicom telephone system.
  • Page 207 System Architecture Registry Entries Protocol Description smsucp.sm Transmission of SMS messages to D2 and international networks via UCP protocol. UCP supports mutated vowels and special characters. To apply the following rules must be added: NVS:SMS.*/49172*=NVS:SMSUCP/49172* NVS:SMS.*/0049172*=NVS:SMSUCP/0049172* NVS:SMS.*/0172*=NVS:SMSUCP/0172* NVS:SMS.*/49173*=NVS:SMSUCP/49173* NVS:SMS.*/0049173*=NVS:SMSUCP/0049173* NVS:SMS.*/0173*=NVS:SMSUCP/0173* NVS:SMS.*/00*=NVS:SMSUCP/00* Various parameters can be additionally appended to a fax protocol and separated by a semicolon.

  • Page 208: Protocol Settings

    System Architecture Registry Entries COST Cost acquisition over this logical line is enabled in an out- ward direction only. Ensuing transmission costs will be stored in the Cost database. SMITR This line is designated as a SMI Transport. LOCAL Lines with this attribute will not be exported to systems con- nected by a Remote System Link.
  • Page 209 System Architecture Registry Entries CIT_Off REG_SZ This string is used together with the telephone number to turn off the MWI signal in the Hicom telephone system. Default: ##8 CIT_On REG_SZ This string is used together with the telephone number to activate the MWI signal in the Hicom telephone system.
  • Page 210 System Architecture Registry Entries OriginatorNumber REG_SZ Originator’s telephone number displayed by SMS message receipt. This number is taken from the originators GSM database field. If no entry exists, the default num- ber is used. Example: 491234567890 The following Values are found under the Key LIBNumber REG_SZ Modem access number to Libertel for the feed-in of SMS messages.

  • Page 211: Gamma Apl

    System Architecture Gamma APL 8 Gamma APL Integration of the GammaLink analog communications hardware and the MRS Server is provided through the Gamma APL. GammaLink is subsidiary of Dialogics, which is one of Americas leading manufacturers in the area of computer supported telephony and fax.

  • Page 212: General Entries

    System Architecture Registry Entries 8.2.1 General Entries The following Values are found in the Key HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\GammaApl DialBreak REG_SZ This character is inserted as a pause character, after the outside dialing number in a dialing string. Default: , IntlDialMode REG_DWORD 0 or 1 Normally, every dialing number is internationally normed by the MRS Server.

  • Page 213: Mail Apl

    System Architecture Mail APL 9 Mail APL 9.1 Standard User Mailbox All non-active document delivery is administered by the Mail APL. All users that are not connected with the MRS server through a SMI transport (Named Pipes, TCP/IP, V.24, SPX, ISDN etc.) receive their mail through the Mailbox administrator. The following shows the minimum required user database entries (e.g.: TESTUSER ).

  • Page 214: Mailing Lists

    System Architecture Mailing Lists 9.3 Mailing Lists The Mail APL administers mailing lists similar to those used in the Internet. For this purpose there are three commands that can be used in a text message to the user LISTPROC SUBSCRIBE Listname Name Surname Subscribe to a mailing list.
  • Page 215 System Architecture Printer Embedded Codes The printer “HP LaserJet III PostScript Plus v2010.118“ which is included in the Win- dows scope of supply and connected with the “MRS Server Fax Monitor“ port must be installed on the MRS Server. You can select an arbitrary printer name that ends with “...

  • Page 216: Lightweight Directory Access Protocol (Ldap)

    System Architecture Lightweight Directory Access Protocol (LDAP) <Content> Depending on the <Token> used, the corresponding content is here entered by the user. See above table. <EndTag> Example: “ /@ “ 9.5 Lightweight Directory Access Protocol (LDAP) The rudimentary support of the LDAP protocol described here serves exclusively to send messages with the recipient being searched for in an LDAP directory service.

  • Page 217: The Nil Protocol

    System Architecture The NIL Protocol Thereby, addresses with corresponding directories are defined. Allowable formats can additionally be assigned in which text files are automatically converted. In the standard configuration the MRS Server recognizes the addresses NVS:DIS / <File> (arbitrary file), NVS:FOD /<File> (Fax-on-Demand file in PP-COM Fax G3 of Fax G4 format) and NVS:TOD /<File>...

  • Page 218: Address Book Consistency

    System Architecture Address Book Consistency Consequently all Internet emails larger than 1000000 bytes would not be sent. Subsequently, the document would be deleted and the subject line modified with a message to the originator. In this case the originator receives a failure report. A type of Robinson list via which transmission to specific recipients is prevented.
  • Page 219 System Architecture Server CTI Journal has a length of 1 and is therefore a switch. A uppercase X activates the CTIJOURNAL CTI Journal for this user and the local telephone number of the user is entered in PHONE# Next an APL is required that functions as a CTI Transaction Provider. A line must also be provided with the form NVS:CTI.* so that a monitor point can be configured.

  • Page 220: Vanity Number Support

    System Architecture Vanity Number Support Status Entry CLASSNAME CLASS KEYNAME <Username> <Info> USER STATE <Info> := <State>|<Direction>|<OtherPartyNumber> <State> , CONNECTING , CONNECTED or BUSY . IDLE <Direction> for incoming calls, O for outgoing or undefined calls types. <OtherPartyNumber> Caller telephone number or that of number called. Example: USER STATE...
  • Page 221 System Architecture Vanity Number Support Option A 2 ABC 3 DEF 4 GHI 5 JKL 6 MNO 7 PQRS 8 TUV 9 WXYZ Option B 1 QZ 2 ABC 3 DEF 4 GHI 5 JKL 6 MNO 7 PRS 8 TUV 9 WXY Option A is mostly found in practice, therefore it is used by the MRS Server as default.

  • Page 222: Vanity Number Generation

    System Architecture Registry Entries Decimal Assigned Decimal Assigned è á ï í î ó ì ú Ä ñ Å Ñ É ß æ Please note that all characters not listed here except A to Z are not adopted. The names “Doe, John“, “DoeJohn“...
  • Page 223 System Architecture Registry Entries AutoAwake REG_DWORD 0 or 1 If the mailbox administrator is to perform timed supervision of the Journal entries, the value 1 (true) must be entered here. The administrator accesses the database routinely. Default: 0 CitJournal REG_DWORD Obsolete value.
  • Page 224 System Architecture Registry Entries DistribDefaultSets REG_DWORD 0 or 1 Automatically set to 1 by the Mail APL after the Default Distrib Setup has been installed. DistribLinePathlist REG_MULTI_SZ Paths are for every address defined under DistribLineProtocols. The directory can either be a logical directory within a share \\ <MRS Server> \Userdata or a physical directory on the MRS Server.
  • Page 225 System Architecture Registry Entries Example: NVS:DIS;SF,OUT;2048000;0;* NVS:FOD;SF,OUT;2048000;0;FG3,FG4 NVS:TOD;SF,OUT;2048000;0;TG3,TG4 NVS:XXX;SF,OUT;2048000;0;* DlgSessions REG_SZ For future expansion of dialog services. Default: 16 DoAddressBookConsistencyCheck REG_DWORD 0 or 1 Switch on Address book consistency checks (1) or off (0). Default: 1 EnterDeflectCallinCtiJournal REG_DWORD 0 or 1 With a call arriving at device A but being routed to device B via DEFLECT or , the CTI journal of device A used to feature “not reached”...
  • Page 226 System Architecture Registry Entries other implementations in which other fields are used, this field name can be modi- fied. Default: mail LdapSearchBase REG_SZ Search basis can be given in X.500 syntax for LDAP queries. Older versions of LDAP servers in the USA require a constant reference to the USA ( c=US ), even when the search result is not within the USA.

  • Page 227: Printer Embedded Codes

    System Architecture Registry Entries RefreshCtiMonitor REG_DWORD 300 to 86400 seconds All seconds specified here are newly set as CTI monitor points at the CTI provider (CTI APL, Hicom APL, ...). In this way the CTI journal is regularly restarted if e.g. the CTI provider does no longer know the monitor points set here because of a hard stop/start (crash).
  • Page 228 System Architecture Registry Entries Monitor. Please note that all settings made here only apply to the user defined style (see style value). The following values are stored in the key HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\MailApl\PEC BeginTag REG_SZ Initiates a PEC sequence. Default: < DateFormat REG_DWORD There are currently three defaulted formats for selection with the token specified in DateSeparator to be placed in between for separation in each case: Value...
  • Page 229 System Architecture Registry Entries FromUid REG_SZ Keyword to specify the originator´s MRS log-in token. Default: Uid PrioHigh REG_SZ Keyword to set a high send priority. Default: High PrioKey REG_SZ Keyword to specify the priority. Default: Prio PrioLow REG_SZ Keyword to set a low send priority. Default: Low PrioNormal REG_SZ Keyword to set the normal send priority.
  • Page 230 System Architecture Registry Entries Smtp REG_SZ Keyword for a recipient´s Internet e-mail address. Default: Smtp Style REG_DWORD This value specifies the keywords. Value 3 means ’user defined’ and releases the remaining values entered in this registry key. Default: 1 Subject REG_SZ Keyword for the message subject.

  • Page 231: Sap R/3 Apl

    System Architecture SAP R/3 APL 10 SAP R/3 APL 10.1 Introduction The SAP R/3 APL provides a gateway to the MRS Server for R/3 systems through use of the SAPconnect interface. All of the services installed on the MRS Server are also available to the R/3 user as soon as their extension numbers are incorporated in the MRS user database.

  • Page 232: Debug Entry For The Structhandler

    System Architecture Registry Entries EmptyFaxOriginator REG_SZ Documents without an originator are not accepted by SAP R/3. The SAP R/3 APL therefore inserts the default originator entry for documents missing an originator address. Default: "*XXX*" 10.3.2 Debug Entry for the StructHandler These Values are found in the registry under the Key HKEY_LOCAL_MACHINE\SOFTWARE\PP-COM\MRS\SapR3Apl\ StructHandler...

  • Page 233: Rfc Client Entries

    System Architecture Registry Entries Active REG_DWORD 0 or 1 This system is active and automatically started (1). Default: 1 AutoLearn REG_DWORD 0 or 1 The “Autolearn” mode must be activated (1) when under SAP canonical addresses (standard presetting under R/3) of the type DE(2404)123-456 are used because replies/documents must be delivered again to the SAP user exactly in this manner.
  • Page 234 System Architecture Registry Entries System[n]\Client ApplicationServerHost REG_SZ TCP/IP Host name or IP-Address of the SAP R/3 Server. ConnectRetryDelay REG_DWORD 10…600 Time in seconds for the execution of a reconnect attempt. Default: 10 Destination REG_SZ Description of the connection data entered in the saprfc.ini for the RFC server.

  • Page 235: Rfc Server Entries

    System Architecture Registry Entries RfcUser REG_SZ Corresponds to the RFC Client user ID as used in transaction sm59. Mandatory entry. Default: MRSC SmtpExpress REG_DWORD 0 or 1 If this option is activated, an express message notifies the SAP user about a new incoming Internet email.
  • Page 236 System Architecture Registry Entries GatewayHost REG_SZ TCP/IP Host name of the SAP Gateway or SAP R/3 Server. GatewayService REG_SZ TCP/IP Service (Port). Default: sapgw00 ProgramID REG_SZ Corresponds to the configured SAP R/3 program ID. Default: sapr3apl.mrs RfcTrace REG_DWORD 0 or 1 RFC-Trace on or off.

  • Page 237: Internet Mail

    System Architecture Internet Mail 11 Internet Mail The Internet Mail APL (SMTP APL) offers several services related to sending and receiving emails via the Internet. 11.1 SMTP (Simple Mail Transfer Protocol) SMTP (Simple Mail Transfer Protocol) defines an international standard for email traffic in the global Internet.

  • Page 238: Pop3 And Imap4 Server

    System Architecture POP3 and IMAP4 Server Relay Host, defining via the following strategy when it can be used by an orginator for message transmission. If neither firewall nor Trusted Domain entries have been defined, each originator is considered local and may thus use the SMTP server as relay. Firewall entries are compared with the originator´s physic IP address;...

  • Page 239: Registry Entries

    System Architecture Registry Entries which messages are being fetched has no entry in the user database, it will be treated as an Alias account for a complete User/Domain group. At the time of the connection all new messages would be fetched and any outgoing messages sent.
  • Page 240 System Architecture Registry Entries DocReps REG_SZ Repeated strategy. Through use of this option, the number of redial attempts and the interval between redials can be configured. Up to five different sequentially executed repeat counters can be set with varying time intervals. Default: 3-60,4-3000,0-0,0-0,0-0 DontRelay REG_MULTI_SZ An Internet email address received by the MRS Server cannot be forwarded to...
  • Page 241 System Architecture Registry Entries setting copying of documents can be ignored for certain folders by specifying the name of the folder for which MRS is to ignore this option. Imap4_JEntriesPerFetch REG_DWORD Number of journal entries transmitted all at once. With very large journals, journal entry compilation may lead to a timeout, when the entries are first to be collected and then transmitted in one go.
  • Page 242 System Architecture Registry Entries Imap4_PreLoginTimeout REG_DWORD Seconds After connection build-up on the IMAP Port, the MRS Server delays login for the period defined here since otherwise the connection would be terminated again. Without this timeout the normal timeout would come into effect, meaning a login delay of 600 seconds in most cases.
  • Page 243 System Architecture Registry Entries sponding security measures have not yet been taken, you can ask for another check on the respective Internet page to have the server removed from the list after the corresponding settings have been performed here. With Orbs you can accomplish this procedure in the presently fastest way via the link http://lookup.orbs.org/closed2.php3?address=<IP Address>.
  • Page 244 System Architecture Registry Entries Pop3Delete REG_SZ Messages polled POP3 Server specially flagged per default. Thus these messages are not polled anymore DELETE_POPPER when the next query is performed with a POP3 Client. Another possible setting would be RECIPIENT so that the message, flagged “Deleted by Recipient”, did not appear in any other client anymore.
  • Page 245 System Architecture Registry Entries ered to those who are entered in this special field. This step is necessary since oth- erwise a messeage would repeatedly be delivered to the same recipient. Example: X-RCPT-TO Pop3PollType REG_DWORD When a POP3 Mail import is performed the MRS Server checks if the account has an entry in the field GROUP in the user database.
  • Page 246 System Architecture Registry Entries Receive_AutoLearn REG_DWORD 0 or 1 When set to 1 an alias will automatically be created in the database by the SMTP APL for originators of incoming messages. Receive_CheckUserExist REG_DWORD 0 or 1 When this option is activated, the SMTP APL checks whether the recipient exists in the MRS user database.
  • Page 247 System Architecture Registry Entries Default: 0 Receive_nThreads REG_DWORD Maximum number of receive channels. Default: 16 Receive_Port REG_DWORD Here the TCP port on which the SMTP APL handles inbound mail traffic can be altered. Default setting is 25 but when used behind a firewall another setting my be more appropriate.
  • Page 248 System Architecture Registry Entries From: "Username" <user@domain.org> When you set this entry to 1, the address is taken from the From field so that a cor- rect user authorization can be realized and also possible non-delivery reports would arrive at the recipient. Default: 0 RelayAllowedSecs REG_DWORD Seconds When set to 0, everybody permitted per relaying can send messages via the SMTP...
  • Page 249 System Architecture Registry Entries the MX entry pointing to a host other than the recipient SMTP server. No unse- cured connection would be established either. SendFormats REG_SZ If special formats are wished by transmission e.g. fax always sent as JPEG, these can be entered similarly to those in POP3.
  • Page 250 System Architecture Registry Entries Example of the creation of a self-signed certificate to be used for testing resp. checking the basic SSL functionality: openssl req -x509 -newkey rsa:1024 -keyout key.pem -out req.pem -config config Two files are generated: the private key file key.pem and the certificate file req.pem.
  • Page 251 System Architecture Registry Entries name. Name of the individual department (e.g. marketing, sales, etc.) The qualified host name of the individual SMTP site (e.g. mail.cycos.com). If you are queried for “extra attributes”, simply ignore it. The csr.pem contents shouldabout look like this: -----BEGIN CERTIFICATE REQUEST----- MIIBETCBvAIBADBXMQswCQYDVQQGEwJBVTETMBEGA1UECBMKU29tZS1TdGF0ZTEh MB8GA1UEChMYSW50ZXJuZXQgV2lkZ2l0cyBQdHkgTHRkMRAwDgYJKoZIhvcNAQkB...

  • Page 252: Pop3 Mail Import Schedule

    System Architecture Registry Entries challengePassword_max = 20 [ v3_ca ] subjectKeyIdentifier=hash authorityKeyIdentifier=keyid:always,issuer:always basicConstraints = CA:true SSL_PassPhrase REG_SZ Password for SSL coding. The password is entered here coded so that at any rate it must be specified via the configuration from within the MRS Monitor. SSL_PrivateKeyFile REG_SZ File with the private key for SSL coding.

  • Page 253: Web Server (Web Apl)

    System Architecture Web Server (Web APL) 12 Web Server (Web APL) In front of the Web APL is a complete HTTP 1.0 web server which is used as an inter- face for the administration of user data, as access to user mailboxes via any HTML browser (Netscape Navigator, Microsoft Internet Explorer, WAP compatible mobile phone) and much more.
  • Page 254 System Architecture Registry Entries This procedure increases security, so that likelihood of manipulation on the URL containing the key is reduced. Default: 600 HTTP_MaxThreads REG_DWORD Maximum number of simultaneously started threads. This value also determines the maximum number of simultaneous connections to the Web Server. Default: 16 HTTP_Port REG_DWORD The port on which the Web Server listens for HTTP queries.

  • Page 255: Protocols

    System Architecture Registry Entries <Dialog Display> is a normal text displayed in the password query dialog by the Web Browser. SSL_CertificateFile REG_SZ Certificate file for SSL coding. SSL_Enable REG_DWORD 0 or 1 Enable (1) or disable (2) SSL coding. SSL_PassPhrase REG_SZ Password for SSL coding.
  • Page 256 System Architecture Registry Entries CGI_ScriptParams REG_MULTI_SZ Parameters handed over to the script. Enable REG_DWORD 0 or 1 This protocol is either active (1) or not (0). IsDefault REG_DWORD 0 or 1 Exactly one protocol is the default protocol used when the main URL is called, e.g. other protocols would...

  • Page 257: Print Apl

    System Architecture Print APL 13 Print APL Copies from incoming and outgoing documents can be automatically created and sent to a printer through the Printer APL. CarbonCopy Rules are defined for the creation and routing of documents. The flag NOPREFERRED should be set in this Rule, so that copies are not detoured by the Preferred rule.

  • Page 258: Default Printer Settings

    System Architecture Registry Entries Some printer drivers show abnormal behaviour when the function CreateDC is called in the usual way which can lead among other things to a Print APL crash. If this is the case set this value to 1 and check whether the thus activated diversion is a sufficient corrective.
  • Page 259 System Architecture Registry Entries DocInfoLine1 REG_SZ Information to be given in the first line of the print out. The following variables can be used for the contents of the line: Variable Significance Commentary line. %comm Charge costs. %cost %costid Cost center. Date of receipt on server.
  • Page 260 System Architecture Registry Entries Variable Significance %wrec An attempt is made to find the recipient in the user data base. If the recipient is found, then the name will be used instead of the fax ID. Default: %serv Nr: %mid from %org to %rec (Page %p of %P) DocInfoLine2 REG_SZ Information to be given in the second line of the print out.
  • Page 261 System Architecture Registry Entries Mode Significance Output direct in printer resolution. A 200dpi fax is PixelToPixel somewhat small when printed with a 600dpi printer. The fax is fitted to the width of the printing page. If FitToWidth the length of the fax is longer than the page, the rest will be printed on a new page.

  • Page 262: Individual Printer Settings

    System Architecture Registry Entries 13.2.2 Individual Printer Settings Each printer has a Key under the Key HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\PrintApl\Devices Each printer can be configured in the same manner as with the default printer. For that reason, only those entries that differ from those of the default printer have been listed below.

  • Page 263: File Interface (Fi Apl)

    System Architecture File Interface (FI APL) 14 File Interface (FI APL) This is some monster of the isle with four legs, who hath got, as I take it, an ague. Where the devil should he learn our language? I will give him some relief, if it be but for that.
  • Page 264 System Architecture Registry Entries BodyDelay REG_DWORD Seconds Break between reading/writing of the header and the corresponding body file in seconds. This is to ease race conditions in certain Novell network environments. CheckPrivileges REG_DWORD 0 or 1 Through activation of this option the PRIV-attribute is set on this logical FI APL line.
  • Page 265 System Architecture Registry Entries Example: TIF MaxPerPoll REG_DWORD Maximum number of jobs that can be read in and processed all at once. Thereby the load with a very large job including hundreds of documents is temporarily dis- tributed. PollRate REG_DWORD Interval in seconds in which the HdrOutDir is polled.

  • Page 266: Rules For Outbound Documents

    System Architecture Rules for outbound Documents Example: TG3;PMF TxtInDir REG_SZ Directory used for inbound document bodies. TxtOutDir REG_SZ Directory used for outbound document bodies. 14.2 Rules for outbound Documents The programming language E is used to write scripts that parse files which contain transmission data.

  • Page 267: Smi Transporter

    System Architecture SMI Transporter 15 SMI Transporter A SMI transport is used when a SMI interconnection is made between two servers (Remote System Link), or when a connection is created between a client and a server. In addition to those listed here, there are other types of SMI transports such as the ISDN APL.

  • Page 268: Spx Protocol

    System Architecture SPX Protocol TransferDirectory REG_SZ Transfer directory for pipe communication. Installed by the APL and must be shared under the name PIPEXFER$. This share is set correctly during the installa- tion. Default: <MrsRoot>\PipeBuff. The Value Entry NullSessionShares listed under the Key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ LanmanServer\Parameters Since a user context for the services exists, this is not required in a secure environment...

  • Page 269: Line Administration

    System Architecture SPX Protocol Default: 45 MaxDlgPerLine REG_DWORD 2…16 Maximum number of simultaneous dialogs on a line. Default: 4 ShortholdTime REG_DWORD 15…3600, 0 = no Shorthold Connection time-out. If no data is transferred within the time entered here, a dis- connect will be initiated.

  • Page 270: Tcp/Ip Protocol

    System Architecture TCP/IP Protocol SleepTimeWS32Rel REG_DWORD Seconds This value defines the (release) time in seconds that WSACleanup() waits before and after a call-up to give Winsock sufficent time for cleaning up internal data structures. The value should not be modified. Default: 1 15.3 TCP/IP Protocol Dependent upon the network TCP/IP Protocol.

  • Page 271: Firewall Mechanism

    System Architecture TCP/IP Protocol Now these clients resp. (sub-)networks can be configured in the registry. Netmap contains the network, netmask, and activation flags for clients or managed net- works whose name cannot be resolved in reverse. If the computers 194.77.158.1 - 194.77.158.126 in the network 194.77.158.0 (net- work mask 255.255.255.128) are configured for example through DHCP, the entry would have the following appearance: Netmap:...
  • Page 272 System Architecture TCP/IP Protocol If all 128 IP addresses in the network 194.77.158.128 (Netmask 255.255.255.128) are to be denied access to the MRS Server, the entry would have the following form: Netmap-Entry Significance 194.77.158.128,255.255.255.128,0 forbidden 194.77.158.128 to .255 194.77.158.0,255.255.255.128,1 allowed 194.77.158.0 to .127 Those that do not fit the above description would be denied access.

  • Page 273: Lines

    System Architecture TCP/IP Protocol Default: 0.0.0.0,0.0.0.0,1 15.3.3 Lines The following Value Entries are specified under the Key HKEY_LOCAL_MACHINE\SOFTWARE\PP-COM\MRS\TcpApl\Line DlgQueueSize REG_DWORD 16…128 Number of dialog elements that can be stored by the transporter if transfer ratio of 1:1 is not possible. Default: 32 HighWaterThreshold REG_DWORD 50…100 Percent When this value is reached the SMI queue sets all outgoing lines to busy till the...

  • Page 274: Tcp/Ip Specific Configuration

    System Architecture TCP/IP Protocol HKEY_LOCAL_MACHINE\SOFTWARE\PP-COM\MRS\TcpApl\LineAdmin MaxLines REG_DWORD 4…4096 Maximum number of lines. Default: 64 ShowSubLineInfo REG_DWORD 0 oder 1 Determines whether individual connections are displayed below the TCP/IP Line Information. Entries are ignored after the 256 line as well as sub-lines entries. This is done to reduce MRS Monitor workload.
  • Page 275 System Architecture TCP/IP Protocol Default: 1...
  • Page 276 System Architecture TCP/IP Protocol...

  • Page 277: Hicom Apl

    System Architecture Hicom APL 16 Hicom APL The Hicom APL enables the use of the ADL (Applications Connectivity Link) fea- tures of the Siemens Hicom 300-Series PBX. These features include switching, con- necting, display control, and the management of rerouting. The physical coupling can be either through a LAN and use of a TCP/IP protocol or through a serial interface with a protocol converter (“Protum-Box).

  • Page 278: Hicom Configuration

    System Architecture Hicom Configuration 16.2 Hicom Configuration The configuration batch of the Hicom 300E for ACL MSV1 (serial) is displayed in the following. CONFIGURATION-CPSM:A1,BSCISO,DVAVERB,5,"MRS",NO,9; CONFIGURATION-CPSM:A1,BSC,APPL,5,"MRSDGV","MRS","MRSDGV",9,0,"MRS"; CONFIGURATION-CPSM:A1,BSC,APPL,6,"MRSTDD","MRS","MRSTDD",9,3,"MRS2"; CONFIGURATION-TCSM:A1,BSC,KO,2,V24EBC,BSC1,6040,6041,6240,6241,6440,6441,6640, 6641,3,1,2,24,,3,3,YES,,,YES,4040; CONFIGURATION-TCSM:A1,BSC,ZU,2,3,9; CONFIGURATION-LCSM:A1,V24,3,V29_,DTE,9600,EXT,60,VDX; CONFIGURATION-DAPPL:05,"MRSDGV","MRSDGV","MRS",DGV;CHANGED-DAPPL:05,,,,CMS,DGV; CONFIGURATION-DAPPL:06,"MRSTDD","MRSTDD","MRS",TDD,SINGLE,00&15; CHANGED-DAPPL:06,,,,CMS,TDD; The configuration batch of the Hicom 300E for WAML (TCP/IP) is displayed in the following.

  • Page 279: Cti Monitoring

    System Architecture CTI Monitoring 16.4 CTI Monitoring For full CTI monitoring support, all phones and external lines must be constantly monitored. To monitor external lines a registry entry must be created under LineB- undleIDs in which the ID of the external line is entered. The entry has the appearance of: I02001 where I refers to ISDN, 2 to the number of the line bundle (in hex) and 001 to the number of lines (B-Channels) contained in the bun- dle (also in hex).
  • Page 280 System Architecture Registry Entries the Hicom may have the same ApplName, otherwise CTI monitoring will not be possible. The Hicom APL TSAP IDs xxxDGVR, xxxDGVS, xxxTDDR and xxxTDDS for trans- mission and receipt over the service DGV resp. TDD. xxx is to be replaced by the ApplName.

  • Page 281: Message Waiting Indication (Mwi) Settings

    System Architecture Registry Entries <Extension> CLASS KEYNAME <Index of the line in HicomPorts, first line corresponds to 0> Unknown devices or those newly connected to another Hicom are searched for and detected at all connected Hicoms. This is performed depending on whether an LED lamp has been defined in the CIT database field.

  • Page 282: Monitor Settings

    System Architecture Registry Entries CIT-RefreshTime REG_SZ hh:mm Unfortunately, the Hicom PBX does not register the state of LEDs either by a restart of a assembly unit (or the complete PBX), or by the resetting of a terminal device (pulling the plug out). Since the Hicom does not register when LEDs are again switched on, this information can be refreshed on a daily basis at a specified time.
  • Page 283 System Architecture Registry Entries Set MonitorDelay REG_DWORD Miliseconds If the Hicom APL is connected with a Hicom PBX via V.24 and a “Protum Box” and between five and ten telephones are to be monitored this option only works with some of the devices. No error message is generated by the Hicom PBX. So either the “Protum Box”...
  • Page 284 System Architecture Registry Entries...

  • Page 285: Computer Telephony Integration (Cti Apl)

    System Architecture Computer Telephony Integration (CTI APL) 17 Computer Telephony Integration (CTI APL) The CTI APL is the centralized CTI transaction provider in the MRS Server. It uses the protocol interfaces from various telephone exchanges and in turn provides all MRS Client applications with those functionalities contained within.

  • Page 286: Registry Entries

    System Architecture Registry Entries Ericsson MD110: Via the V.24-COM Port All manufacturers offer a TSAPI based test program for TSAPI/CSTA link func- tionality which can be run independently of the MRS Server. 17.3 Registry Entries In the Key HKEY_LOCAL_MACHINE\SOFTWARE\Cycos AG\CTIAPL the following values are found ExceptionNumbers REG_MULTI_SZ This value is used to switch off the MRS Server´s calling number normalization...

  • Page 287: Protocolspecific Values

    System Architecture Registry Entries Default: 3 Use<Protocol>_<Name> REG_DWORD 0 or 1 The CTI link <Name>, which uses <Protocol> is either activated (1) or deacti- vated (0). For each installed CTI link a key with the name of the individual CTI link is generated in which the specific settings of this link are entered.

  • Page 288: Tapi Protocol

    System Architecture Registry Entries HostName REG_SZ IP address of the PABX. MonitorTimeout REG_DWORD Internal timeout for applets that, within this timeframe, have to confirm monitor statuses send to them so that they are not considered inactive. 17.3.1.2 TAPI Protocol CitSF REG_DWORD Via the CTI APL logical line entered under CitSFAddr and by means of a tele- phone LED a user is notified about new incoming messages.

  • Page 289: Tsapi Protocol

    System Architecture Registry Entries PhoneSetStatus REG_DWORD 0 or 1 1 switches to a Hicom 150 mode obsolete by now. Default: 0 UniqueCallId REG_DWORD 0 or 1 When set to 1 the TAPI adopts the Call ID by means of LineGetRelatedCallID. The Call ID is used as UID in the MRS MonitorStatus transaction.
  • Page 290 System Architecture Registry Entries LoadBackupDelay REG_DWORD Seconds When the CTI APL is started the monitor points set last are read in again. This value defines the corresponding delay prior to the start of this procedure. Default: 5 LoginID REG_SZ Name of the account used by the CTI APL to log in to the PABX. MaxMonRange REG_DWORD Maximum number of static monitor points within a range.

  • Page 291: Generic Entries

    System Architecture Registry Entries Password REG_SZ Password for the account mentioned under LoginID to log in to the PABX. So far it was not used during all our tests resp. an empty password was sufficient. This however depends on the configuration of the PABX. PrivateProfile REG_DWORD Internal bit form.
  • Page 292 System Architecture Registry Entries If set and furthermore LocalLine is 1, this value is used instead of the global one. Example: 0 CallId REG_DWORD Intermediate storage of the Call ID used last. This value must not be modified! CorrField REG_SZ If MonTakeCorrel is 1, set a monitor point for all users having their telephone number entered in the database field defined here.
  • Page 293 System Architecture Registry Entries If the system delivered the numbers entirely without the preceding 0, thus e.g. 12345678, the corresponding calling number type had to be transmitted by the sys- tem as well. Otherwise a correct normalization could not be performed. For exam- ple a mobile phone number such as 171-654321 would be handled as international number from the USA if the system did not transmit the calling number type.
  • Page 294 System Architecture Registry Entries If set and furthermore LocalLine is 1, this value is used instead of the global one. Maximum length of an internal calling number. All numbers exceeding Max- InternalLength are considered international calling numbers and are normalized accordingly.
  • Page 295 System Architecture Registry Entries NumberRangeStop REG_SZ End of the calling number range. This range is exactly and exclusively required when there is an additional CTI link to another PABX with the same extension number and a different extension number range. NumMaxXmrLines REG_DWORD Mamimum number of lines displayed in the MRS Monitor.
  • Page 296 System Architecture Registry Entries...

  • Page 297: Vm Apl

    System Architecture VM APL 18 VM APL The VM APL contains a virtual machine executing E Scripts. Such a script is ACD.e (Automatic Call Distributor), which takes on the entire queuing logic and agent con- trol at a call center. At first a survey shall be given of the architecture of the call center realized by MRS followed by an overview of the resources used by the ACD and the configuration modes in the VM APL context.

  • Page 298: The Mrs Side

    System Architecture Call Center System Architecture in a queue. Above the UCD groups on the right you can see four a/b ports. These are needed for playing announcements to a waiting caller to make him holding the line. For this purpose the inherent routing logic is withdrawn from the UCD groups by the MRS Server as they would otherwise independently rout on the calls.

  • Page 299: Mrs Client Applications

    System Architecture Call Center System Architecture The various APLs that enable access to the MRS Server via different, normal commu- nication protocols are coupled up the Kernel. For call center application the following APLs are elementary: VM APL (Virtual Machine APL): The VM APL contains a virtual machine executing E Scripts.
  • Page 300 System Architecture Call Center System Architecture The below illustration shows the connection of the client software required for the MRS Server call center application and its connection to the MRS Server via MSP. TrayPhone/Event Bar Client GUI Server ACD Agent Client GUI ACD Supervisor Admin GUI...

  • Page 301: Overall Picture

    System Architecture Call Center System Architecture can see e.g. whether a call is just coming in or whether a connection has already been established. With TrayPhone calls to the individual telephone can be rerou- ted, immediately rejected or redirected to a voice box (if available) . 18.1.3 Overall Picture The below illustration shows the individual components described in the previous sec- tions connected.
  • Page 302 MRS Server MRS Client Wall TrayPhone/Event Bar Client GUI Kernel ACD Agent Client GUI ACD Supervisor Admin GUI Trunk-Lines Dialogic Report Client 5 ACDLoop Client/Admin GUI TAPI a/b a/b a/b a/b Hicom 150 4 x a/b Announcement Ports Voicemail Agent a/b a/b Phones UCD Device...

  • Page 303: Registry Entries

    System Architecture Registry Entries The MRS Server is connected to the Hicom 150 E at several points. The connecting strand most important to the call center is the CTI Link. In order to perform CTI and call center functionalities the CTI APL is connected to the PBX via the TAPI Service Provider (TSP) and the ACD Proxy.

  • Page 304: Automatic Call Distributor (Acd.e)

    System Architecture Automatic Call Distributor (ACD.e) 18.3 Automatic Call Distributor (ACD.e) The ACD Script is an Automatic Call Distribution application, or in other words, it automatically routes incoming calls to the agents thus being the central call center component. Contrary to standard call centers the MRS Call Center can also forward inbound messages (email, fax, voicemail) to agents for processing and via so called campaigns agents can initiate calls as well.

  • Page 305: Agents

    System Architecture Automatic Call Distributor (ACD.e) 18.3.1.1 Agents Agents are normal MRS user accounts with the following additional information resp. entries in the user database, usually entered in the Correlation Database in the format DOMAIN CLASSNAME CLASS KEYNAME <Domain> <Agent> <Name>...
  • Page 306 System Architecture Automatic Call Distributor (ACD.e) <Name> Significance Beyond that nine statuses (USERDEF1 to USERDEF9)are freely definable by the ACD Supervisor which can be used e.g. for statistic registration of various “Break” modes. ACD_LOGINREADY Switch. If an uppercase X is entered in the database the agent is immediately set to “Ready”...

  • Page 307: Acd Groups

    System Architecture Automatic Call Distributor (ACD.e) 18.3.1.2 ACD Groups An ACD Group in this sense is a MRS group which can have two different types of members. These are: Agents; Agents as permanent members of the ACD Group. Skills; that an agent must have to become a member of the ACD Group. Skills are realised via special groups again which have agents as members.
  • Page 308 System Architecture Automatic Call Distributor (ACD.e) <AttributeName> Significance Reference to the waiting loop or group of waiting loops assi- ACD_LOOP gned to this ACD Group. Example: GRP:<LoopList> or <Loop> Here the routing mode is defined. Valid values are LONGE- ACD_ROUTMODE STIDLE, CYCLE or LINEAR.
  • Page 309 System Architecture Automatic Call Distributor (ACD.e) <AttributeName> Significance <FixAgent> Points if the agent is dedicated to the ACD Address. Default: 150 <InternalAgent> Points if the agent is an internal one. Default: 500 <ExternAgent> Points if the agent is a remote one. Default: 100 <StateReady>...
  • Page 310 System Architecture Automatic Call Distributor (ACD.e) <AttributeName> Significance This MRS group, also called “Call Event Address“, is an ACD Group. As <AttributeValue> an arbitrary value can be entered. ACD Group mailbox as known from normal MRS users. If MAILBOX this attribute remains empty <ACDAddr> is default set. Additionally a user account must exist for this mailbox where at first all Store&Forward messages are routed to.

  • Page 311: Skills

    System Architecture Automatic Call Distributor (ACD.e) <AttributeName> Significance The service levels 3 to 7 specify 5 periods indicating the ratio SERVICELEVEL3 of the number of callers that were connected to an agent and SERVICELEVEL4 and the total number of calls within this period. This rate can SERVICELEVEL5 later continuously be monitored by the administrator.

  • Page 312: Waiting Loops

    System Architecture Automatic Call Distributor (ACD.e) <Domain> <Skill> <Agent 2> GROUP <Domain> <Skill> <Agent N> GROUP The numeric KEYNAME can, separated with a comma, be complemented by the entry SL=<Level>. <Level> ranges from 1 to 99 and indicates in percent to what extent an agent masters a certain skill.
  • Page 313 System Architecture Automatic Call Distributor (ACD.e) also apparent in the database without looking for the corresponding group attribute ACD_LOOP of an <ACDAddr>. <AttribName> Significance Telephone or internal device number of a PBX to reach this ACD_DEVICE waiting loop. Example: 440 440 is the default number of the first UCD device with a Hicom 150.
  • Page 314 System Architecture Automatic Call Distributor (ACD.e) <AttribName> Significance For the call center solution with the Hicom 150 four analog PLAYBACKDEV announcement ports are used. These are already globally con- figured by the script configuration (see ACD Script parameter PlayDev on page 342). If for a certain ACD Group only spe- cific announcement ports different from the global configura- tion are to be used the appropriate settings can be made here.

  • Page 315: Campaigns

    System Architecture Automatic Call Distributor (ACD.e) The designator of a waiting loop group <LoopList> starts like all groups without per- sons as members with the ’#’ character. Furthermore there are various group attributes of the format DOMAIN CLASSNAME CLASS KEYNAME <Domain>...
  • Page 316 System Architecture Automatic Call Distributor (ACD.e) <State> Significance (Locked) This job has been locked by the <Agent> for processing. If the agent has not finished working on the job within the time limited by <Sche- dule/End> or <Logout> has been set to 1 because the agent has logged himself off his call center workstation this <Item>...

  • Page 317: Thresholds

    System Architecture Automatic Call Distributor (ACD.e) DOMAIN CLASSNAME CLASS KEYNAME <Domain> <Campaign> <AttribName> <AttribValue> GROUPATTR that determine the features of this campaign group. <AttribName> Significance Optional indication or description of this campaign. DESCRIPTION Optional message ID if the campaign has been generated by a message.
  • Page 318 System Architecture Automatic Call Distributor (ACD.e) The correlation database contains entries with the following syntax, defining thres- holds: DOMAIN CLASSNAME CLASS KEYNAME <Domain> <Name> <Item> <ThresholdDescription> THRESHOLD <Name> is either the name of the ACD Group for which this threshold is valid or GLOBAL if the entry is to be valid for all ACD Groups without individual thresholds.
  • Page 319 System Architecture Automatic Call Distributor (ACD.e) Resource Significance Number of agents that according to their status can presently GROUP answer a call for the ACD Group. Corresponds in principle to AGENTS and is used when semantically the ACD Group is meant and not the agents. <ValueCondition>...
  • Page 320 System Architecture Automatic Call Distributor (ACD.e) <ActionList> is a sequence of activities executable when <ValueCondition> as well as <TimeProfileCondition> is fulfilled. The following activities have been implemen- ted so far: Activities Significance FORWARD=<DestNumber> Redirect calls to <DestNumber>. ALVARIABLE=<Attribute>&<VarName> Change the ACD variable attribute (see page 326) of a ACD Group.
  • Page 321 System Architecture Automatic Call Distributor (ACD.e) Activities Significance TIME Executing all activities belonging to the profile <TimePro- fileCondition>. WALL=<StateInWallCtrlFile> Activating a specific alarm status in the wall display con- trol file. For the structure of this control file see page 336. Instead of the long form entered in the table also the first three characters can be used.

  • Page 322: Time Profiles

    System Architecture Automatic Call Distributor (ACD.e) KEYNAME KEY AGENTS|<3|Test(OP)|ALC=RED&Agents too low! If the call center is accessible (time profile “Test“) and the number of agents drops below 3 issue the red alert message “Agents too low!“ in the ACD Supervisor. KEYNAME KEY GROUP||Test(BR)|WALL=SystemBreak Indicate “Break“...
  • Page 323 System Architecture Automatic Call Distributor (ACD.e) If the current time is not included in one of the defined day profiles the <State> speci- fied in the OTHERWISE entry applies. In case this entry does not exist an empty <State> definition is valid for all times outside the defined intervals. Calendar Profiles are stored in the Correlation Database in the following way: DOMAIN CLASSNAME...

  • Page 324: Special Routing Rules Depending On The Caller (A-Id Routing)

    System Architecture Automatic Call Distributor (ACD.e) ROUTING=<NewRoutingMode> Modifies the internal routing mode. LONGESTIDLE, CYCLE and LINEAR are allowed. PLAYBACK=<PlayBackFile> Activates a special announcement to replace the first greeting. 18.3.1.8 Special Routing Rules depending on the Caller (A-ID Routing) Depending on the caller´s telephone number the A-ID routing allows influencing the assignment of calls to the agents of an ACD Group.

  • Page 325: Acd Variables

    System Architecture Automatic Call Distributor (ACD.e) Examples: DOMAIN CLASSNAME CLASS KEYNAME <Domain> AIDROUT GLOBAL 4989|BAVARIAN The agents require the additional skill BAVARIAN for all callers whose telephone number begins with “4989“ (Munich). In the event that BAVARIAN is a non man- datory skill each agent of the dialled ACD Group can receive the call but it is more likely that it would be routed to agents with the skill BAVARIAN.

  • Page 326: Acd Group Variables

    System Architecture Automatic Call Distributor (ACD.e) 18.3.2.2 ACD Group Variables The variables refer to the respective ACD Group. They can be indicated in the ACD Supervisor or on the wall display. Variable Significance Last ACD call date. DLAC Waiting loop name. SNWL Average call duration in seconds.

  • Page 327: Acd Agent Variables

    System Architecture Automatic Call Distributor (ACD.e) Variable Significance Number of waiting fax messages for this group. NSFF Number of waiting emails for this group. NSFE Number of voice messages today. Number of fax messages today. Number of emails today. List of group alarm messages. Number of reachable agents.

  • Page 328: Acd Waiting Loop Variables

    System Architecture Automatic Call Distributor (ACD.e) Variable Significance Number of ACD calls per day. NACD Number of ACD calls per week. NACW Number of ACD calls per month. NACM List of calls for this agent. LAID List of all ACD Groups where this agent is member. LCEA Caller waiting time.

  • Page 329: Acd Campaign Variables

    System Architecture Automatic Call Distributor (ACD.e) Variable Significance Average waiting time in the waiting loop. List of all callers with A-ID. LAID Number of calls today. Number of calls this week. 18.3.2.5 ACD Campaign Variables These variables refer to campaigns. They can be indicated in the ACD Supervisor or on the wall display.
  • Page 330 System Architecture Automatic Call Distributor (ACD.e) … <Section> is either preset by the ACD Script (always starts with the string “Event“) or a new <Section> which is jumped at through triggering a threshold or from an “Event”. Such a new <Section> is a string that should not match one of the predefined “Event”...
  • Page 331 System Architecture Automatic Call Distributor (ACD.e) The following examples are adapted to the display of a Hicom 150 system telephone with an indication of one line and 24 columns. Event Group Agent Statuses EventLogout Center;Time=3; "! LOGOUT !" EventLogin Center;Time=3; "! LOGIN !"...
  • Page 332 System Architecture Automatic Call Distributor (ACD.e) EventBreak Center;Time=3; "! BREAK !" Rep;Center;Time=2; "Agent '&AG'" Rep;Center;Time=3; "is in BREAK" Rep;Center;Time=2; "'&NWC' calls in loop" Rep;Center;Time=2; "Av. wait-time: '&AWT'" EventWorkReady Center;Time=3; "! AFTER WORK (R)!" Center;Time=1; "You are member of:" Center;Time=1; "'&LCEA'" Rep;Center;Time=2;...
  • Page 333 System Architecture Automatic Call Distributor (ACD.e) Rep;Center;Time=3; "is in state" Rep;Center;Time=3; "'&UD2'" Rep;Center;Time=2; "'&NWC' calls in loop" Rep;Center;Time=2; "Av. wait-time: '&AWT'" EventUserDef3 Center;Time=3; "! &UD3 !" Rep;Center;Time=2; "Agent: '&AG'" Rep;Center;Time=3; "is in state" Rep;Center;Time=3; "'&UD3'" Rep;Center;Time=2; "'&NWC' calls in loop" Rep;Center;Time=2;...
  • Page 334 System Architecture Automatic Call Distributor (ACD.e) Rep;Center;Time=2; "Av. wait-time: '&AWT'" EventUserDef7 Center;Time=3; "! &UD7 !" Rep;Center;Time=2; "Agent: '&AG'" Rep;Center;Time=3; "is in state" Rep;Center;Time=3; "'&UD7'" Rep;Center;Time=2; "'&NWC' calls in loop" Rep;Center;Time=2; "Av. wait-time: '&AWT'" EventUserDef8 Center;Time=3; "! &UD8 !" Rep;Center;Time=2; "Agent: '&AG'" Rep;Center;Time=3;...
  • Page 335 System Architecture Automatic Call Distributor (ACD.e) Event Group Call Statuses EventCallAlerting Rep;Center;Time=3; "'&SCID' is calling .." Rep;Center;Time=3; "Redirected: '&SRDI'" Rep;Center;Time=3; "Prio '&NCEP'" Rep;Center;Time=3; "Wait-time: '&NLWT'" EventCallConnected Rep;Center;Time=3; "Partner: '&SCID'" Center;Time=3; "Redirected: '&SRDI'" Center;Time=3; "Prio '&NCEP'" Center;Time=3; "Wait-time: '&NLWT'" Rep;Center;Time=3; "'&NWC' calls are waiting" Rep;Center;Time=3;...

  • Page 336: Wall Display Control

    System Architecture Automatic Call Distributor (ACD.e) AlarmExtremSL3 Rep;Center;Time=2; "!! SL3 Alarm !!" Rep;Center;Time=5; "!SL3 dangerous low!" Rep;Center;Time=3; "'&NWC' calls in loop" Rep;Center;Time=3; "Av. wait-time: '&AWT'" AlarmAgents Rep;Center;Time=2; "!! Agent Alarm !!" Rep;Center;Time=5; "too few agents logged in" Rep;Center;Time=3; "'&NWC' calls in loop" Rep;Center;Time=3;...
  • Page 337 System Architecture Automatic Call Distributor (ACD.e) <Command> is a formatting command with the text to be displayed and additional control commands can be given separated by a semicolon. Within the text portion the above described ACD variables can be used as well. Possible commands are:: Command Significance The text is scrolled to the left in <msec>...
  • Page 338 System Architecture Automatic Call Distributor (ACD.e) Standard Events EventStart Gong=LOUD;Color=Rainbow;Time=5; "'&ACD'" Color=Rainbow;Time=5; "Time: &ST" Goto=EventNormal EventNormal Rep;Color=Green;Time=5; "W &NWL C &NCC L &RSL3%" Rep;Time=5; "T &NACW D &NACD A &NAR" Rep;Time=5; "V &NSFV F &NSFF E &NSFE" EventAgentChanged Gong=SOFT&SINGLE;Color=Yellow;Time=5;"Agent changed" Goto=LASTSTATE EventVoicemail Gong=SOFT&SINGLE;Color=Yellow;Time=5;...
  • Page 339 System Architecture Automatic Call Distributor (ACD.e) EventCampaign Gong=SOFT&SINGLE;Color=Yellow;Time=5; "Campaign received" Color=Yellow;Time=5; "&NCA campaign in group" Goto=LASTSTATE Special Events “BREAK“, “CLOSED“ and “OPEN“ These events are freely defineable and activated by a threshold. Here this is accom- plished through considering the time profile and a subsequent message for the call center statuses Open, Closed and Break.
  • Page 340 System Architecture Automatic Call Distributor (ACD.e) Event Group Alarm Statuses These events are freely defineable and activated by a threshold. AlarmSL3 Gong=Normal&SINGLE;Color=RED;Flash;Time=5; "SL is low" Color=RED;Time=5; "S-Level 3 -> &RSL3%" Rep;Color=RED;Time=5; "W &NWL C &NCC L &RSL3%" Rep;Color=RED;Time=5; "T &NACW D &NACD A &NAR"...

  • Page 341: Acd Script Parameter

    System Architecture Automatic Call Distributor (ACD.e) Goto=EventNormal EventNormal Rep;Color=Green;Time=5; "Ag R &NAR N &NNA" Rep;Time=5; "Ca A &NCA L &NLC C &NAC" Rep;Time=5; "Tr L &NTL U &NTC" 18.3.5 ACD Script Parameter The actual script parameters are stored in the registry value ParamBlock. Per line one parameter is stored in the format <Parameter>=<Value>...
  • Page 342 System Architecture Automatic Call Distributor (ACD.e) Default: NVS:CTI DlgAddr=<MRS Address> MRS address where the ACD Script sends transactions to in order to have announcements played. This is usually performed via the script protocol ACD- LOOP which with the Siemens Hicom 150 call center solution is installed e.g. via the Dialogic APL.
  • Page 343 System Architecture Automatic Call Distributor (ACD.e) <MaxCalls> is the maximum number of calls that can simultaneously be switched to this announcement port thus the same announcement is played in each case. <WaitTime> is the period the ACD Script waits to collect further calls where the same announcement is to be played.
  • Page 344 System Architecture Automatic Call Distributor (ACD.e) RoutMode=<Mode> Here the standard assignment mode is specified. Valid values for <Mode> are LONGESTIDLE, CYCLE or LINEAR. This assignment mode can individually be adapted for each ACD Group later on. Default: LONGESTIDLE The MRS ACD Script controls a number of assignment modes: Based on the agents´...
  • Page 345 System Architecture Automatic Call Distributor (ACD.e) The automatic after call work time is not running. This condition becomes meaningless through the appropriate selection of ACD_ONLREADY. The agent has a valid and active internal monitor point or he is a remote agent. The agent is not processing another call.
  • Page 346 System Architecture Automatic Call Distributor (ACD.e) Fewer factors are taken into account to determine the <RoutingPoints> : <Skill>, <FixAgent>, <InternalAgent>, <ExternAgent> Definition of the agent´s “Ready” status: The agent must be logged in and accept “messages” resp. “campaigns”. Further- more he must not exceed the maximum number of the corresponding jobs (ACD_MAXSFJOBS, ACD_MAXCAMPJOBS).

  • Page 347: Report Apl

    System Architecture Report APL 19 Report APL The Report APL provides an easily configurable means for accessing internal MRS Server data. This data is compiled in an easy to read format and can be sent to any MRS Address. The Report APL uses the program Crystal Reports from Seagate-Software for the cre- ation of report layouts and for static editing.
  • Page 348 System Architecture DBase Export Database Description “Bill Mayer” or the assigned fax G3 (FAXG3) number “4912345678”. Two correla- tion data records describe the relationship: Field/Column Data Record1 Data Record 2 DOMAIN CLASSNAME USER USER CLASS MAYER MAYER KEYNAME NAME FAXG3 Bill Mayer 4912345678 The following table describes the individual fields resp.

  • Page 349: The Geb.dbf Database

    System Architecture DBase Export Database Description 19.1.2 The GEB.DBF Database This database contains correlation data records from the internal MRS database GEB. Billing information is stored in this database. If the billing options of the MRS Server are activated, a GEB data record is created for all transmission jobs. The following table describes the individual fields resp.

  • Page 350: The Journal.dbf Database

    System Architecture DBase Export Database Description 19.1.3 The JOURNAL.DBF Database This database contains those data records found in the global server journal. The fol- lowing table describes the individual fields resp. tab separated columns of a JOURNAL data record: Field/Column Description Data record message ID.
  • Page 351 System Architecture DBase Export Database Description Field/Column Description 2 – TS_SUCCESS_OK Document successfully delivered to the recipient. 3 – TS_SUCCESS_FAILURE Original transmission and all re-transmission attempts have failed. 4 – TS_SUCCESS_REJECT Due to missing resources, the APL is currently not able to complete the transmission job and the kernel should attempt to retransmit the document at a later time.
  • Page 352 System Architecture DBase Export Database Description Field/Column Description Transaction state as text message in the server language. STATE Document format. A list of possible formats can be found on FORMAT page 391. Length of the file in bytes. LENGTH A mask from type T_DELETE with DELETE_* markers. Var- DELFLAG ious DELETE_* markers represent various views of the delete state of a document.
  • Page 353 System Architecture DBase Export Database Description Field/Column Description 0x0008 – DELETE_POPPER Only for journal data records. Read: Only documents not polled by a POP3 client. Delete: Documents polled by a POP3 client. Status code TS_FLAGS. A logical OR is used by the kernel for FLAGS new flags with existing flags.
  • Page 354 System Architecture DBase Export Database Description Field/Column Description 0x00001000 – TS_FLAGS_FORM These documents are created as a template. 0x00002000 – TS_FLAGS_MAXREPSFAIL Document status is FAILURE. Maximum number of repeat attempts has been reached. 0x00004000 – TS_FLAGS_AUTOTIMECPY Document created through an AWAKE-Routing Rule. 0x00008000 –...
  • Page 355 System Architecture DBase Export Database Description Field/Column Description 0x04000000 – TS_FLAGS_PARTIALCONVERSION This document may be partially converted. 0x08000000 – TS_FLAGS_FLAGGED This document marked as received from a IMAP4 client. 0x10000000 – TS_FLAGS_NOTRECENT This document polled by an IMAP4 client. 0x20000000 – TS_FLAGS_RESETCIT CIT signal reset by receipt of this report.

  • Page 356: Registry Entries

    System Architecture Registry Entries Field/Column Description NODE portion of the MRS address (Originator). ORIGSRVC USER portion of the MRS address (Originator). SOURCE NODE portion of the MRS address (Recipient). RECIPSRVC USER portion of the MRS address (Recipient). DEST Remark The syntax of MRS addresses can be found on page 23 of this manual. The fixed por- tion (NVS) of a MRS address is not stored in a journal database entry.

  • Page 357: Configuration Of The Individual Jobs

    System Architecture Registry Entries Job List REG_MULTI_SZ List of all currently defined report jobs. 19.2.3 Configuration of the Individual Jobs Every job has the Key HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\RepApl\Job\<JID> which contains the following Values. CR Export Destination REG_SZ Path\Filename This value defines where the completed job is stored, and how it is to be named. The file extension is automatically appended and is dependent upon the selected export format.
  • Page 358 System Architecture Registry Entries CR Export Mode REG_DWORD Export is by default to a file. Reports can also be directly exported to either Lotus Notes or Microsoft Exchange. Value Export to File Lotus Notes - Currently not implemented. Microsoft Exchange - Currently not implemented. CR Layout REG_SZ Path\Filename The Report Layout file is configured here.
  • Page 359 System Architecture Registry Entries DB Time Select Fixed Offset REG_DWORD Through the selection of a time range, only data from the data source that falls within this range would be exported. This applies only to data sources where a meaningful application exists. This offset is required when DB Time has a value between 6 and 10.
  • Page 360 System Architecture Registry Entries Value Mode Time units months Time units years DB Time Select Range REG_DWORD This entry is required when DB Time Select Mode has a value of 2, 3, or 4. This entry fixes the offset of the time range. DB Time Select to REG_SZ Format: Century,Year,Month,Day,Hour,Minute,Second,Timezone, All values must be comprised of 2 digits.
  • Page 361 System Architecture Registry Entries Name REG_SZ Report job name Recipients REG_MULTI_SZ 0 or 1,<MRS Address>, Report job recipients are listed per line. Addresses can be individually activated through this flag. Repeat Custom Days REG_DWORD For use with user defined repeat intervals. This offset is expressed in days. Repeat Custom Hours REG_DWORD For use with user defined repeat intervals.

  • Page 362: Default Layouts

    System Architecture Registry Entries Status REG_DWORD A report job has a definite status, at every point in time. With the exception of Last Result, the status “None” does not occur. Value Status Error Active Executing Finished Canceled Hold 19.2.4 Default Layouts The following Values are found in the Key HKEY_LOCAL_MACHINE\Software\PP-COM\MRS\RepApl\Layout Count REG_DWORD...
  • Page 363 System Architecture Registry Entries Data Sources REG_DWORD All data sources that are used in the report are given here. When more than source is used, the values would be added together. Value Data Source Correlation Journal Charge Name REG_SZ Default layout name. The file extension must be .RPT. Example: SysDsn.RPT...
  • Page 364 System Architecture Registry Entries...

  • Page 365: Setup

    System Architecture Setup 20 Setup During the Setup process, various generally used registry keys were created. Several of these keys should never be modified, whereas some can be adapted by the user at a later time. Many of the entries can be comfortably modified through the corresponding configuration DLL’s in the Servers Administration program MRS Monitor, or not so comfortably in the Registry editor regedt32 in Windows NT.

  • Page 366: Global Entries

    System Architecture Registry Entries FolderName REG_SZ Name of the Program Groups The name of the program groups. Example: MRS Server InstallationComplete REG_SZ Yes Once the Setup has been completed, and all path information is correct, this value is entered in the registry and the key set to yes. This information is used by the MRS de-installation program.
  • Page 367 System Architecture Registry Entries FolderDirectory REG_SZ Share or Directory The sub-directories Folder0 to Folder99 contain documents administered by the MRS Server. The FolderDirectory must be installed as a share in the event that the MRS Server is distributed over various NT computers. In this case the directory or share must be given in UNC notation.

  • Page 368: Licence Information

    System Architecture Registry Entries Tokens are always separated with a ‘.’. Major := 1-n Minor := 00-n[alpha][|i|p] [|(Debug)|(Checked)] i := Unofficial version for external testing p := Private version for development testing <empty> = Official release version Build := 1-n Example: 3.02.260 3.5alphai.260...

  • Page 369: Special User Accounts

    System Architecture Registry Entries HKEY_LOCAL_MACHINE\SOFTWARE\PP-COM\MRS\Services Kernel REG_MULTI_SZ Kernel services started at Server start. The computer where the service should be started, may be entered as parameter after the comma. More information over the procedure for distributed MRS Servers is found in the section Distributed MRS Server on page 65ff.

  • Page 370: Specific Site Entries

    System Architecture Registry Entries Example: POSTMASTER,309744525 Guest REG_SZ General guest access. Used also as Euro file transfer access with corresponding rights. This registry entry should not be deleted. By the first installation the default name GUEST is entered with the password GUEST. 20.1.6 Specific Site Entries The following Values are specified under the Key HKEY_LOCAL_MACHINE\SOFTWARE\PP-COM\MRS\...
  • Page 371 System Architecture Registry Entries CountryCode REG_SZ Country code. Example: 49 CountryCodeEscape REG_SZ International prefix. This number is set before the country code of the recipient when an international number is dialed. Example: 00 ExternalLinePrefix External line. Example: 0 Regio50 REG_SZ A comma separated list containing the area codes in the Regio50 Bereich.
  • Page 372 System Architecture Registry Entries...

  • Page 373: Remote Administration Of A Mrs Server

    System Architecture Remote Administration of a MRS Server 21 Remote Administration of a MRS Server In comparison to QNX based NVS systems, is the remote maintenance of a MRS Server not possible with internal MRS tools, but with the services provided by Win- dows NT.
  • Page 374 System Architecture Remote Administration of a MRS Server %SystemRoot%\SYSTEM32\RAS and is named MODEM.INF. Here is found the dial string of the modem. The entry DT should be replaced with XDT. In addition the following steps must be performed: 1. De-install the modem 2.

  • Page 375: The Mrs Monitor

    System Architecture The MRS Monitor continues to occur, the protocol settings in the remote access server as well as in the telephone book of the service computer should be checked. If the error (e.g. “Unknown user”, Password incorrect”, etc.) occurs, the spelling should be checked or the validity of the account.

  • Page 376: File Access

    System Architecture File Access Data transfer per modem is not fast. Debug filters can quickly lead to line over- loads. The service technician should create a set of useful MRS Monitor layout tem- plates. The difference between a normal layout and a template is that the computer name is not stored, and is requested each time the template is opened.

  • Page 377: The Registry Editor

    System Architecture The Registry Editor The asterisk signifies that the first available drive letter will be assigned. It is also pos- sible to explicitly define the drive by entering a letter and colon. To minimize the possibility of access errors or chaos on the service computer, all drive letter assignments should be canceled before terminating the remote access connec- tion.

  • Page 378: The Event Viewer

    System Architecture The Event Viewer 21.4 The Event Viewer The event log of the MRS Server can also be viewed. The command: start eventvwr \\MRSSERVER should be given to start the viewer. Other than connection associated delays, the oper- ation is the same as a local application. 21.5 Starting and Stopping the MRS Services In many service cases it is necessary to perform numerous shut-downs and re-starts of modules or the complete server.

  • Page 379: The Ultimate Emergency

    System Architecture The Ultimate Emergency Attention: In most cases when a service fails to start an error message is found in the Event Viewer under the “Applications Log”, if the error originates from a service itself, and if caused by outside interference (missing authorities, etc.) it would be found in the “System Log”.
  • Page 380 System Architecture The last bit of advice...

  • Page 381: User Database Adaptations

    System Architecture User Database Adaptations 22 User Database Adaptations 22.1 Configuration of the New User Wizard The new user Wizard simplifies the creation of a new user by suggesting many “sensi- ble” configuration settings. It then guides the administrator through a step-by-step pro- cess of checking and configuring the required data.
  • Page 382 System Architecture Configuration of the New User Wizard CLASSNAME CLASS KEYNAME <DB Entry> <Template> WIZARD USER Example: WIZARD USER FAXG3 4912345678%e WIZARD USER FAXG3-ID +49 1234 5678 %e Each template is made up of simple strings and place holders. The syntax for the place holders is as follows: %[n][m]{v} ([n] and [m] are optional, {v} is mandatory) Place holder Value...

  • Page 383: Bitmaps In Fax Logos

    System Architecture Bitmaps in Fax Logos CLASSNAME CLASS KEYNAME <Group Name> ISGROUP USER e.g. CLASSNAME CLASS KEYNAME USER USER ISGROUP USER SERVICE ISGROUP USER SUPERVISOR ISGROUP 22.2 Bitmaps in Fax Logos Through the use of a database reference, bitmap images can be fastened to fax logos. With this technique, photos or signatures can be incorporated into fax logos.
  • Page 384 System Architecture Bitmaps in Fax Logos this file is imported into the correlation database. Non-standard characters that are used in the description of a field which will later appear in insertable data fields must correspond and be coded in accordance with the codepage 437. This process must be repeated for the classes FC_ENGLISH and FC_GERMAN.

  • Page 385: Mrs Service Provider

    System Architecture MRS Service Provider 23 MRS Service Provider The MRS Service Provider is used as a global sub-structure for all client applications e.g. Lotus Notes LSX, TrayPhone, Outlook CTI Extensions or the MRS Client.While several client applications can run on a computer simultaneously only one instance of the MRS Service Provider is available.

  • Page 386: Mrs Service Provider And Tcp/Ip Apl On One Computer

    System Architecture MRS Service Provider and TCP/IP APL on one Computer Operating System (Program) (Service) MSP.EXE MSPSVC.EXE supported supported Windows 2000 with terminal server a. MSP.EXE should only be installed on the terminal server if you do not ind- tend to have the MRS Service Provider be used by more than one user at a time.

  • Page 387: Server

    System Architecture Registry Entries Directory REG_SZ Directory in which the cTree database files are stored. Default: Sub-directory data- base from Module. Example: D:\msp\bin\database Enabled REG_DWORD 0 or 1 Enables use of the database. If for example only an Applet is to be used, the data- base can be disabled by setting the value to 0.

  • Page 388: Transport

    System Architecture Registry Entries Default: 0 Module REG_SZ Path to the Service Provider Program. This path is not installed by the MSP. When not already running, the first Applet started by the MSP will install the path. Default: The complete path to the MSP. Example: D:\msp\bin\Msp.exe Service REG_DWORD 0 or 1 This value informs an applet of whether the MRS Service Provider is installed as...

  • Page 389: Tcp/Ip Transport

    System Architecture Registry Entries Enabled REG_DWORD 0 or 1 Enables or disables the SPX Transport. Default: Dependent upon the local configu- ration and that of the network stack. MspListenPort REG_DWORD SPX port number over which the SPX APL is to contact the MSP (e.g. for active delivery).

  • Page 390: User- Dependent Entries

    System Architecture Registry Entries Default: 0.0.0.0 Enabled REG_DWORD 0 or 1 Enables or disables the TCP/IP Transport. Default: Dependent upon the local con- figuration and that of the network stack. MspListenPort REG_DWORD TCP/IP port number over which the TCP/IP is to contact the MSP (e.g. for active delivery).

  • Page 391: Document Formats

    System Architecture Document Formats 24 Document Formats 24.1 Supported Document Formats MRS supports various document formats. In most cases they are given in the form of an acronym when necessary. We differentiate between formats that can include other formats, so that an upper class is formed from text, graphic and audio formats. In addi- tion there are also printer formats which appear only in connection with exported lines from the Print APL of the NVS Server.
  • Page 392 System Architecture Supported Document Formats Acronym Format Description Multi-page PCX format (standard-Fax-Format from Microsoft) Cycos Fax G3 Format Cycos Fax G4 Format BMP_COL Fax data converted to Windows BMP standard. A trilinear gray scale interpolation is performed. JPEG format. Adobe Postscript Format Compressed multi-page TIFF Fax G3 Format Compressed multi-page TIFF Fax G4 Format Compressed single page TIFF fax format.

  • Page 393: Multi Document Format (Pmf)

    System Architecture Multi Document Format (PMF) NVS Printer Formats The formats are only used by the Print APL of the NVS Server under QNX. In other words, only when a remote system link to a NVS Server exists. Acronym Format Description HP-PCL 4 Printer language with additional Cycos information for the Print APL of the NVS Server.
  • Page 394 System Architecture Multi Document Format (PMF) typedef struct char szObjIdent[16]; DWORD dwObjVersion; DWORD pObjNext; DWORD pThis; DWORD reserved[5]; } OBJ, FAR *LPOBJ; szObjIdent contains the string "PmfFile________", szObjVersion the version number of the PMF format, currently 0x01 and pObjNext an offset to the first representation that is comprised of the following structure OBJ_FILE, which contains the original document.
  • Page 395 System Architecture Multi Document Format (PMF) representation, which is referenced as pObjMore. This concerns a system object with sSystemType ‘PT’. szObjVersion is the version number for a structure with original files resp. con- verted files. Currently this is in both cases the structure OBJ_FILE and value is 0x01.
  • Page 396 System Architecture Multi Document Format (PMF) Value Description MIME Text 0x00080000 Greyscale Bitmap 0x00100000 Greyscale JPEG 0x00200000 Audio (AIFF) 0x00400000 Audio (AU) 0x00800000 TIFF Multipage (TIF_MUL) 0x01000000 Audio (WAV_A) 0x02000000 TIFF Multipage Fax G3 (TG3) 0x04000000 TIFF Multipage Fax G4 (TG4) 0x08000000 Audio (WAV_MU) 0x10000000...
  • Page 397 System Architecture Multi Document Format (PMF) Value Significance Example: A text is as TXT, RTF, and as MS Word document in one representation. First is the (dwInfo=0) file with the greatest amount of information loss (TXT) inserted and this flag set. Next is the RTF file (dwInfo=1) with the flag set and finally the MS Word document (dwInfo=2), without this flag, since no better representation follows.
  • Page 398 System Architecture Multi Document Format (PMF) Error Significance Irregular bit-group-size (needs to be 8) Source- and target-file cannot have the same name Source- and target-file are of the same data type End of file reached Error reading phoneme File (*.inf) Error opening phoneme File (*.inf) Error in section [PHONEMES] Keyword [PHONEMES] expected, found other...
  • Page 399 System Architecture Multi Document Format (PMF) Error Significance phoneme File too big (>32000 Bytes) Error opening file for writing Error opening file for reading Kerning parameter set to 0 Error opening phoneme File (*.dat) The sound filename in the phoneme directory of *.dat is missing File does not exist Fax(G3) synchronization word is missing Character '@' is missing in set section...
  • Page 400 System Architecture Multi Document Format (PMF) Error Significance Syntax error in fax-split description string Too many pages for fax adding For fax adding are only files of the same format possible Security Descriptor creation error CreatePipe() error ShellExecute() error PipeRead or PipeWrite error Error during fax printing A PMF file is expected Zero files were converted...
  • Page 401 System Architecture Multi Document Format (PMF) Error Significance Error during conversion of text to speech during Windows-Wave to M-Law conversion TTS: Error in parameter count TTS software, SelectEngine procedure returned an error TTS software, SelectVoice procedure returned an error TTS software, SetSpeechMode procedure returned an error File concatenation error, (disk full?) pObjMore is an offset in the PMF file to a further object of the type OBJ_FILE, which belongs to the current representation of the document.
  • Page 402 System Architecture Multi Document Format (PMF) Example: Text document with alternative representations pObjNext pObjNext Header pObjMore pObjMore The original contains numerous representations of a document. This is indicated through the flag PMF_FLAG_NEXTISALTERNATIVE. A fax G3 is the first conver- sion created from the original. Such a representation could be e.g. from the Exchange APL created.

  • Page 403: The Utility Checkpmf

    System Architecture Multi Document Format (PMF) Example: Text and attached image, converted to MIME pObjNext pObjNext Header MIME pObjMore The original consists of two files that are converted to a MIME document. 24.2.2 The Utility CheckPMF With the Utility CheckPMF one can view the contents of a PMF document and extract singular files.
  • Page 404 System Architecture Multi Document Format (PMF) Filename : D:\Folders\folder59\2401f2e3840.doc FilenameOriginal: g.doc Binary code Filename : D:\Folders\folder59\2401f2e3841.rtf FilenameOriginal: isdn.rtf Converted file 2: Fax (G4) Filename : D:\Folders\folder59\6901f2e38c3.FG4 FilenameOriginal: 6effects.FG4 Fax (G4) Filename : Error FilenameOriginal: ERROR: Conversion not possible yet This example shows a PMF file which contains a MIME message with binary data. The first conversions are those files contained within the MIME message: HTML file, Corel Draw file, RTF text, and a MS Word document.

  • Page 405: Privileges

    System Architecture Privileges 25 Privileges The following table contains a list of the most important standard privileges. Depen- dent upon the configuration, further privileges can be defined. New privileges are defined through a CORREL data record. Privileges are configured without hex computations through the PC client software. Privilege Significance SUPERVISOR Privilege...
  • Page 406 System Architecture Privileges Privilege Significance 0x07 Advanced USER SYS_ADVUSER This privilege is for client applications connecting it with specific functions. With the ACD Agent client these are e.g. the configuration options. 0x08 ACD Monitor Privilege SYS_ACDMONITOR The user may view current call center data via the ACD Supervisor client, but no configuration alte- rations can be executed.
  • Page 407 System Architecture Privileges Privilege Significance International Call Privilege SYS_INTERNAT 0x17 Telematic services can be used worldwide. Server File Access SYS_SERVERFILE 0x18 Access to the MRS Server virtual file system through the server file manager on the client. Local File Access SYS_LOCALFILE 0x19 Access to the local file system through an appro-...
  • Page 408 System Architecture Privileges Privilege Significance External Archive Query SYS_ARCHIVRECH 0x1D Allows researching of external archives. Currently not implemented under MRS. Telex Privilege SND_TLX 0x20 Telex messages may be sent. Telex services are not within the performance spectrum of the server and require a remote system link to a NVS server on a QNX basis.
  • Page 409 System Architecture Privileges Privilege Significance Euro-Filetransfer Receive EFT_LOAD 0x30 EFT server privilege. The MRS Server may act as an EFT server. If an EFT client queries a MRS Server, files may also be downloaded from the EFT server. Euro-Filetransfer Send EFT_SAVE 0x31 Same as “load”...
  • Page 410 System Architecture Privileges Privilege Significance Individual files may be stored or modified in the SFT_OWNER 0x50 MRS Server virtual file system. Enables file allo- cation to users. Individual files may be stored or modified in the SFT_GROUP 0x51 MRS Server virtual file system within the user group.

  • Page 411: Index Of Registry Entries

    System Architecture Index of Registry Entries Index of Registry Entries Access Protocol Layers 66, 117, 369 BackupDirectory 55, 80 AccessCode 93, 134, 157, 291, 370 BadPrinterCreateDC 257 AccountingDatabase 96 Baudrate 131, 155, 183, 203 AclAddress 163 BeginTag 228 AclDelayMessage 163 BindAddress 239, 253, 274, 280, 389 AclInternLen 164 Blob 128, 131, 133, 135, 137, 152, 155, 156, 157,...
  • Page 412 System Architecture Index of Registry Entries CIT_Off 209 CtiLogBlackList 223 CIT_On 209 CtiLogUnknown 223 CitActive 107 CIT-Beep 281 CitCacheActive 107 CitCounter 108 D1ProviderNumber 209 CIT-Display 281 D2ProviderNumber 209 CitJournal 223 Data Sources 363 CIT-LED 281 DatabaseDirectory 119 CitMessage 108 DatabaseImportMode 119 CIT-RefreshTime 282 DatabaseImportSource 119 CitSF 287, 288, 289...
  • Page 413 System Architecture Index of Registry Entries DialMode 146 DialogEnabled 97 EarlyCloseBoard 177 DialPlan 146 EditPerm 138, 158, 187 DigestFormat 209, 210 EditPermGenerated 138, 159, 187 DirectLine 154 EMailAddresses 258 Directory 387 EMailFaxWidth 86 DisplayColumns 164 EMailSecurityLevel 111 DisplayRows 164 EmptyFaxOriginator 232 DispPerm 138, 158, 186 Enable 256 DistribDefaultSets 224...
  • Page 414 System Architecture Index of Registry Entries FaxPollFilePath 202 HdrOutDir 264, 265 FaxPrintMode 260 HdrPattern 264 FaxResources 127, 147, 178 Headline 140, 159, 188, 202 FfuAmt 161 HicomPort 280 FfuSendErrRep 161 HicomPorts 280 FfuSendMidInId 161 HighWaterThreshold 268, 273 FfuSendOkRep 162 HostName 240, 288 FfuSendRundRep 162 HTTP_DefaultHTML 253 File Systems 99...
  • Page 415 System Architecture Index of Registry Entries IntRout 99 LogFilePath 122 IoPort 269, 274 LoginID 290 IsDefault 256, 262 LogName 165, 167, 170 LogoGroup 87 LogServer 122 LowerCaseAddresses 23, 99 JID 356 LowWaterThreshold 268, 273 Job List 357 JournalLayout 119 MaintenanceDontTouch 100 MaintenanceScript 100 Kernel 66, 117, 369 margin_b 87...
  • Page 416 System Architecture Index of Registry Entries MonitorRegistryChanges 121 MonitorTimeout 288 OAD 132, 133, 155, 156, 183, 184 MonTakeCorrel 294 OldStyleConnInd 149 MRS Domain 366 Organization 92, 368 MRS Server 366 OriginatorID 203 MrsBuildNumber 82 OriginatorNumber 210 MSClusterNodes 82 OrigNumberPlan 127, 149 MspListenPort 389, 390 OrigNumberType 127, 149 MultiAddresses 102...
  • Page 417 System Architecture Index of Registry Entries PrioHigh 229 RecursivReRout 26, 103 PrioKey 229 RefreshCtiMonitor 227 PrioLow 229 Regio50 95, 371 PrioNormal 229 RegistryPushTime 121 PrioThread 150, 179 RelayHost 248 PrioUrgent 229 RemoteLocalServices 113 Private 130, 140, 153, 160, 188 RemoteRecord 163 PrivateMode 130, 140, 154, 163, 188 RemoveFromCapaList 103 PrivateProfile 291...
  • Page 418 System Architecture Index of Registry Entries Send_MaxOut 248 StatisticsClasses 83 Send_Ras 248 StatMonitors 291 Send_RequireSSL 248 Status 362 SendDate 229 StatWinSize 104 SendFormats 249, 265 StdCharging 151 SendTime 229 StorePath 163 SendTimeout 249 StrictStatusReporting 236 SepTag 229 Style 230 ServerCache 388 Subject 230 ServerID 291 SupportedDevices 127, 151...
  • Page 419 System Architecture Index of Registry Entries Use Foreign Exports 356 WelcomeText 160 Use_ 287 UseAcdProxy 289 UseCapiDll 151 UseDefaults 262 XmrTopic 167 UseDestination 235, 236 UseForTextToFaxA4 89 UseInternalCritical 180 UseLines 289 UseNameServer 390 UseOCR 90 UseOriginalDocOnRout 105 UserDirCorrelField 160 UserDirectory 84, 367 UserRemovalExtension 105 UseSpr 167 UseTrustedDomains 113...
  • Page 420 System Architecture Index of Registry Entries...

Table of Contents