PREFACE ...........................................................................................................2 1. 2. 2.1. 2.2. 3. 3.1. 3.2. 3.3. 3.4. 3.5. 4. 4.1. 4.2. 4.3. 5. 5.1. 5.2. 5.3.

6. 6.1. 6.2. 6.3. 6.4. INTRODUCTION ............................................................................................4 MYOFFICE@NET ARCHITECTURE ...............................................................6 The Concept .............................................................................................................. 6 Deployment View ...................................................................................................... 6 SYSTEM REQUIREMENTS ............................................................................10 Call@Net Application Server Requirements ........................................................... 10 SQL (Database) Server Requirements ..................................................................... 11 Client PC Requirements ........................................................................................... 11 Installed components on Client PCs ........................................................................ 12 Network Information ............................................................................................... 12 UNIVERGE SV7000 REQUIREMENTS AND PREPARATIONS ...................14 Requirements ........................................................................................................... 14 Preparations ............................................................................................................. 14 Group Arrangements ............................................................................................... 14 SOPHO 2000 IPS REQUIREMENTS AND PREPARATIONS ......................15 Requirements ........................................................................................................... 15 Preparations ............................................................................................................. 15 Group Arrangements ............................................................................................... 15 SOPHO IS3000 REQUIREMENTS AND PREPARATIONS .........................16 Requirements ........................................................................................................... 16 Projecting IP Connections ........................................................................................ 18 Activate the Correct TMS Services (Optional) ........................................................ 20 Enable Phone Settings Functions (Optional) ............................................................ 20 6.4.1. Enable Follow Me and Don't Disturb .......................................................... 20 6.4.2. Enable Software SMA .................................................................................. 20 6.4.3. Enable Absent/present Switching ................................................................. 21 6.4.4. Enable AEM Message ................................................................................... 21 Group Arrangements ............................................................................................... 22 Saving Changes and Starting PVE Service ................................................................. 23 Multiple PBXs and MyOffice@Net .......................................................................... 23 6.7.1. DPNSS Clustered ISPBX ............................................................................. 24 6.7.2. Multi Unit ISPBX .......................................................................................... 25 INSTALLATION ............................................................................................26 Check SQL Server .................................................................................................... 26 Table of Contents i

6.5. 6.6. 6.7.

7. 7.1.

7.2. 7.3. 7.4. 7.5. 7.6. 8. 8.1. 8.2. 8.3. 8.4. 8.5. 8.6. 9. 9.1. 9.2. 9.3. 9.4. 9.5. 9.6. 9.7. 9.8. 9.9. 9.10. 9.11. 9.12. 10. 10.1. 10.2. 10.3. 10.4. 10.5. 10.6. 10.7. A. Table of Contents ii

MSDE Installation ......................................................................................................28 Check System Requirements ....................................................................................29 Server Installation .....................................................................................................30 Client Installation ......................................................................................................31 Upgrade & Reinstall ..................................................................................................31 GENERAL CONFIGURATION ...................................................................... 32 Internet Explorer Settings .........................................................................................32 Security Settings ........................................................................................................32 Activate the Licenses ................................................................................................36 Enable Access to the ISPBX ......................................................................................37 Additional Settings ....................................................................................................38 Choose the Authentication Mode .............................................................................38 APPLICATION CONFIGURATION. .............................................................41 User and Company Directory Configuration ...........................................................41 How to import users ................................................................................................43 Manually create the hierarchy of the customer ........................................................44 Manually create a MyOffice@Net user ....................................................................44 External Directory Configuration .............................................................................45 Web Directory Configuration ...................................................................................45 BTS Directory Configuration ....................................................................................47 Configure the Dialing rules .......................................................................................48 Assign MyOffice@Net modules to a user ................................................................49 Phone Settings Configuration (Optional) ..................................................................49 9.10.1. SMA Settings .................................................................................................49 Group Display Configuration ....................................................................................50 Voicemail Configuration ............................................................................................51 TROUBLESHOOTING ................................................................................... 53 General .....................................................................................................................53 Tracing: Diagnostic Monitor .....................................................................................55 SOPHO Info Console ...............................................................................................55 Directory Browser ....................................................................................................58 Group Display ...........................................................................................................58 Phone Settings ..........................................................................................................58 Microsoft Internet Explorer's Enhanced Security Configuration ..............................58 CONCURRENT USERS WITH MSDE AS DATABASE ENGINE ................. 63

MyOffice@Net Installation Guide

Release date : 19/Apr/2007

PREFACE
This book gives a description of the installation, configuration and maintenance aspects of MyOffice@Net, release 7.0. GUIDELINES FOR MAINTENANCE AND ADMINISTRATION OF A SERVER / SPECIALIZED COMPUTER The following general rules should be kept in mind for a good administration and maintenance of a Server / specialized computer: 1. Keep operating system and application software up-to-date Servers by their very nature form a critical part of the infrastructure. When they go down this will affect the entire business structure. It is imperative to keep the basic operating system and application software working and also up-to-date both for stability and security reasons. There can be an automated or semi-automated process for upgrades and patches. However sometimes upgrades and patches can have unpredictable interactions with running services. In case of doubts, please ask NEC Philips Unified Solutions about the possible impact of specific updates or fixes. 2. Don't run unnecessary services or applications Reduce risk by not running any non-essential service or application. It's about the possible interactions between them (e.g. ports that are used by other applications too), the Server capacity or security lacks that might be introduced by those applications. When there is a need for combinations of applications then NEC Philips Unified Solutions should be contacted. Also check the manufacturer's features of the other product. Be aware of the impact on the services that should be provided. 3. Back up your data All computers will have a moment in time when they will fail (hardware or software). Servers usually host data. Losing the Server also means losing data. That's why for every production system (Servers, specialized machines) backup of the system and data is a must. The backup procedure depends on many factors, like the volume of data, rate of data change, the recovery procedure, time for backup and recovery, and the response of the applications. Sometimes an automatic backup cannot work. There are applications that must be aware when the backup process is starting. This information you can find in the specifications (requirements) of the products involved. Summarized: there should be a backup policy, carefully analysed, built on the existing IT infrastructure.

4. Account maintenance / authorized use Keep a strict list of the accounts that will have access to the Server and the privileges that they might have. If unauthorized users can have access to the Server, then the entire Server activity can be compromised, or even worse, affecting the business, e.g. when confidential information is accessed. 5. Specialized software for Servers Strongly consider installing specialized software to provide: anti-virus protection, maintenance tools, and/or firewall. Firewall policy can be implemented in the entire network based on enterprise firewalls. Where these are not available, a "desktop" solution is welcomed. NEC Philips Unified Solutions applications can use a range of ports and kind of access. NEC Philips Unified Solutions can be contacted for information about ports and accesses. Antivirus and firewall software has to be included in the list of applications that must be updated periodically. Some of the most used maintenance tools are ScanDisk and Defrag. After an unpredictable event, scanning the disk can be automatically or manually driven. Defragmentation is a must. Database applications are very sensitive to this issue. There could be performance bottlenecks or application errors. 6. Physical security A power failure is one of the most often events, and also one of the dangerous. A good Uninterruptible Power Supply (UPS) will filter the current and in case of a general power down, it will provide the system a few minutes allowing the applications to close properly. Without an UPS, data can be lost or damaged (open files, unfinished changes in database, or files impossible to be recovered). Finally, also consider a correct location and environment (air conditioning, ventilation) for the equipment. 7. Computer Names Be very careful with changing the name of a computer. This brings a lot of changes. Many applications will need a reinstallation!

1.

Introduction

MyOffice@Net consists of a number of web enabled telephony applications, which add, enlarge or replace functionality of an ordinary phone. These applications can be run from the users' desktop or laptop PC using Internet Explorer. MyOffice@Net release 7.0 is available on the UNIVERGE SV7000, and networks with SV7000 and SOPHO iS3000 Hybrid Communication Systems and/or SOPHO 2000 IPS IP Communication Servers (Optional). MyOffice 7.0 will be delivered as part of projects only (while MyOffice 6.1 remains available as a product). The contents of MyOffice 7.0 is based on the functionality of MyOffice 6.1, but with restrictions. The actual contents of each package will also depend on the PBX environment that must be supported for the project. To implement this strategy, MyOffice 7.0 has been divided into 'kernel' functions and 'optional' functions. Kernel functions are available 'off-the-shelve' for all projects. Optional functions require an additional investigation during project preparation, to decide whether it can run in the environment of the project. In the environmental variables (such as Windows OS, etc.) the same division between kernel and optional is made. The specification of kernel and optional functionality is given in the FCO. This manual describes installation and maintenance of the total of kernel and optional functionality. Optional functions and variables are indicated as (Optional) in this manual. Note: NOT ALL FUNCTIONS DESCRIBED IN THIS MANUAL CAN BE INSTALLED IN ALL ENVIRONMENTS. ALWAYS REFER TO THE FCO, AND CONTACT THE SUPPORT CENTRE IF SOME ASPECTS ARE NOT CLEAR! The installed components are listed below. 1. Server components: - Central Authentication; - License Manager; Used to activate the licenses for the MyOffice@Net modules. - Diagnostic Monitor; Used to monitor and set trace levels for the MyOffice@Net applications - Security Configurator; Used to configure the MyOffice@Net server according to the customers security policy - SOPHO Info Console; Used to display information about the installed components on the MyOffice@Net server - Directory Browser; Users can search names/numbers in 3 web directories: personal, company or external. - Phone Settings (Optional); Users can activate/deactivate facilities such as Follow-me. - Phone Display; Users can watch display information during call handling and use caller

2. 3.

4. 5.

lists for calling back parties. - Group Display; Users, which are a group member, can monitor their group activities. Client components: In Client component .msi file, to be deployed to client PC's Database engine: - Microsoft SQL Desktop Engine; Depending on the number of clients, this is either the Microsoft Data Engine (MSDE), which is part of the product, or a SQL Server, which is not part of the product. Sentinel Driver Office Integration component

Check the following link to ShareNet for up-to-date information about which version of Windows is needed: http://nsointra.pbc.be.philips.com/commonnet/prodmgmt/plct_docs/ Windows%20Support.xls. LICENSING To use MyOffice functionality the licenses should be present as described in the FCO. The proper dongles and license files/strings should be present at installation.

2.
2.1.

MyOffice@Net Architecture
The Concept

MyOffice@Net consists of a number of web based telephony applications that are started on a Web Client. The end user has access to the applications independent of the location and the time of day; only access to the corporate intranet is necessary. Once logged on to MyOffice@Net, all granted applications can be used without the need of a separate logging on for each MyOffice@Net application during that session.

2.2.

Deployment View

In MyOffice@Net, the following devices are involved:

Figure 2-1 Deployment view 1. Web Clients with a Windows operating system and Internet Explorer. Other web browsers are not supported as MyOffice@Net web pages are active Server pages (asp). This technology is used to create web pages with a dynamic content. For the execution of the scripts on these pages, components are used that are not always supported by all web browsers; 2. A Web Server with a Windows Server 2003 operating system, Internet Information Server and the required MyOffice@Net modules installed. This web server is also referred to as Call@Net Application Server, as more Call@Net applications can be installed on this Server (i.e. Management@Net); Note: MyOffice@Net server cannot coexist with Management@Net versions lower than 3.1.0 or CC250 or Business ConneCT, on 1 PC. See also the FCO.

3. A Microsoft LAN controlled by a domain controller between server and client PC's. Preferrably the server and clients are part of the same domain. Other configurations are Optional. 4. A database Server. This can be MSDE or SQL 2000 installed on the Web Server or SQL 2000 on a separate SQL Server. The database server contains several databases for storage of own data (United database) and for the company directory (OpenWorX, BTS(Optional)). 5. The PBX, either: - a UNIVERGE SV7000 release 21. The connection is based on the OpenWorX Application Interface (OAI) link, when in a mixed network with SV7000. - a SOPHO iS3000 release Call@Net 3.3 or higher. The connection is based on PVE, OM, switching services and CSTA. The PBX can be one of the following: a stand alone (single unit) PBX; a DPNSS network. (each DPNSS node can be a stand alone PBX or a FIN); a network (multi unit) PBX; FIN (Fully Integrated Network), network protocol is proprietary IMP. - a SOPHO 2000 IPS release 12.2 (Optional) when in a mixed network with SV7000. The connection is based on the OpenWorX Application Interface (OAI) link. Both Open and Closed numbering schemes are supported, but Free Numbering scheme is not supported. The process flow as experienced by a user of a Web Client starting a MyOffice@Net application, is as follows: 1. A user of a Web Client browses with the Internet Explorer to the Internet Address (URL) of the Web Server. An example of such a URL is: http://pc22/ca/myoffice.aspx 2. A login screen is shown and the user must enter the Username and Password.

Figure 2-2 An example of the MyOffice@Net login 3. MyOffice@Net will check if the user is known in the database. If so, a MyOffice@Net portal is shown. This portal shows the applications, which are granted for this user. Note: If Windows Integrated Authentication is used, the login step is skipped and the user will get the MyOffice@Net portal immediately.

Figure 2-3 An example of the MyOffice@Net portal 4. After selection of the desired application, the application is started.

3.

System Requirements

The system requirements are split up into requirements for the Call@Net Application Server, the SQL Server and the Client PCs. As far as service packs are concerned the latest available service packs always need to be installed as soon as new service packs become available. Check the following link to ShareNet for up-to-date information about which version of Windows is needed and which service pack http://nsointra.pbc.be.philips.com/commonnet/ prodmgmt/plct_docs/Windows%20Support.xls.

3.1.

Call@Net Application Server Requirements

The Call@Net Application Server (MyOffice@Net modules are installed on this PC) must meet the following requirements: Minimum PC requirements: - Pentium IV, 2 GHz or higher; - 1 GB RAM; - 4 GB free space on the hard disk with NTFS file system; - Ethernet card (2 cards recommended). Two Ethernet cards are recommended to enhance basic security. In that case a fixed IP address relation of MyOffice@Net and PBX can be programmed on a PBX-LAN separate from the customers LAN. This is a minimal solution intended for basic installations. A more advanced security solution using VLAN configuration is preferred. Windows Server 2003 operating system with SP1 or R2. The English version of the Windows operating system is recommended. IIS 6.0 Other software and/or applications are only allowed on the Call@Net Application Server in special cases i.e. Directory Distribution Services, Management@Net. MyOffice@Net server cannot coexist with Management@Net versions lower than 3.1.0 or CC250 or Business ConneCT, on 1 PC. We strongly advise to always have the latest Windows Service Pack installed; the Windows problems solved in the Service Packs may influence the proper working of all applications running on the Server, and/or influence Server security. MyOffice@Net requires MDAC 2.8, to check the MDAC version use Microsoft Component checker or open the registry (regedit) and search for the following key:
HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess\FullInstallVer

Note: -

10

3.2.

SQL (Database) Server Requirements

A choice must be made which software controls the database access. This choice is related to the size of the MyOffice@Net system (i.e. how many users participate in the system). For small and medium sized MyOffice@Net systems (up to 400 clients) this can be Microsoft SQL Desktop Engine (MSDE). For large systems SQL Server (SQL 2000) is required. 1. MSDE; MSDE 2000 with Service Pack 4 must be installed before installation of MyOffice@Net. Note: MSDE is limited to 5 concurrent users and 2 GB database size limit. See appendix A for some examples concerning system size/amount of users. 2. SQL Server; SQL 2000 with Service Pack 4 is required. The SQL Server software is not part of the MyOffice@Net software package. It can be obtained from Microsoft. Note: During the installation the system administrator username (sa) and password is used, therefore the SQL Server authentication should be mixed mode (SQL Server and Windows authentication). A SQL Server must meet the following requirements: - Pentium III, 1 GHz or higher; (recommended: Pentium IV, 2 GHz) - 1 GB RAM; - Typical 500 MB hard disk space and additional space per database. - Monitor: 1024 x 768 pixels / 17" screen; - Ethernet card. - Microsoft Windows 2000 (SP4) or 2003 Server (SP1); - Microsoft SQL Server 2000 (SP4). 3. SQL Server 2005 (Optional). If support of SQL 2005 is required, please contact the support desk.

3.3.

Client PC Requirements

PC's on which the MyOffice@Net applications are used, are called Clients in the context of this book. These are the end user PC's. The minimum requirements are: Pentium II, 233 MHz Memory: 128 MB RAM (recommended: 256 MB RAM) Ethernet card Windows 2000 Professional (+SP4) or Windows XP Professional (+SP2) Internet Explorer 6.x (+SP1) or 7.0

Note: The client operating systems mentioned above will only be supported as long as they are

11

still supported by Microsoft.

3.4.

Installed components on Client PCs

When the user of the client PC has administrative rights and the proper versions of the client side software components are not present on the client PC, they are down loaded automatically from the Call@Net Server at the first usage of the MyOffice@Net applications. Restart the client PC when requested. For general use the following components are installed: Event Distributor: MBP.ocx stored in C:\WINNT\System32. Used by Phone Display and Group Display; Browser Machine: BrowserMachine.dll stored in C:\WINNT\System32. Used by Central Authentication, Phone Display and Group Display;

For Phone Display the following component is installed: Phone Display client component: ClientPDhandler.dll stored in C:\WINNT\System32.

For Group Display the following components are installed: Group Display client component: gdclient.dll stored in C:\WINNT\System32.

Registry settings: The following is added to the registry: HKEY_CURRENT_USER\Software\Microsoft\ Internet Explorer\MenuExt\Dial from SOPHO Values: - (Default):" HTTP://<MO server>/IEDialer/IEDialer.aspx - Contexts: Hex 34 (52) - Flags: Hex 1 (1) (string) (DWord) (DWord)

For installation of the client components see chapter 7.5. "Client Installation".

3.5.

Network Information

For communication between Server and Client, the following TCP ports (Server Side) are used: 8086; used for Remoting Service, Remoting Interface. 80; used for http:// Request Full directory browser /CA.

From the client side, random UDP and TCP ports are used.

12

Communication between Server and PBX: TCP/IP port 60000 for -> Matsynchronisation: Getting extension information. TCP/IP port 60030 for -> CTI Commands. Note: Between the Server and the PBX, NO NAT router. So - Client --- Server --- PBX = OK - Client --- FIREWALL --- Server --- PBX = OK (if firewall is well configured) - Client --- | NAT | --- Server --- PBX = OK - Client --- | NAT | --- Server --- |NAT| --- PBX = Not OK ! - Client --- | NAT | --- Server --- FIREWALL --- PBX = OK (if firewall is well configured)

13

4.
4.1.

UNIVERGE SV7000 Requirements and Preparations

Requirements

System software release R21 or higher must be loaded. MyOffice@Net handles Telephone Numbers (Network Data).

4.2.

Preparations

The following ASYD/ASYDL setting should be present: (to read and change the setting use the MAT command ASYD/ASYDL) ASYD ASYD ASYD ASYD ASYD ASYDL ASYDL ASYDL ASYDL SYS 1 INDEX 79 SYS 1 INDEX 31 SYS 1 INDEX 241 SYS 1 INDEX 241 SYS 1 INDEX 241 SYS 1 INDEX 864 SYS 1 INDEX 864 SYS 1 INDEX 864 SYS 1 INDEX 864 bit 6 bit 2 bit 3 bit 7 bit 0 bit 2 bit 4 bit 5 must be 0 (OAI in service) contents must be '0x06' for OAI must be '1' (OAI) must be '1' (SCFs) must be '1' (DTerm Display) must be '1' (built-in TCP) must be '1' (CCIS SMFN Indication is in service) must be '1' (8-port monitoring) must be '0' (reset connection)

If settings are incorrect, start monitor on OAI gives error 0x01020002 function not supported. MAT commands 1. To read the software package release: DISS 2. To read/change ASYD: ASYD In the 'System' field, enter '1'. In the 'index' field enter '241'. Change bit 7 to a '1'.

4.3.

Group Arrangements

Only UCD groups and Call Pickup groups can be monitored. Nested groups are not supported. If Group Display is used, a 'Special Monitored Number' must be assigned in the SV7000. To assign this number use the MAT commands AMNON and ALGNN.

14

5.
5.1.

SOPHO 2000 IPS Requirements and Preparations

Requirements

System software R12.2 must be loaded.

5.2.

Preparations

Program the (fixed) IP address and subnet mask of the SOPHO 2000 IPS PBX. The address must be reachable from your MyOffice@Net Server, so it must be on the same subnet. Use MatWorX to check the IP address and subnet mask via the command:
0B00 > 00 > for the IP address

and, 0B00 > 01 > for the subnet mask Ping the IP address from your MyOffice@Net server.

5.3.

Group Arrangements

Only UCD groups and Call Pickup groups can be monitored. Nested groups are not supported.

15

6.
6.1.

SOPHO iS3000 Requirements and Preparations

Requirements

ISPBX's connected to the Call@Net Application Server must meet the following requirements: Running software package SIP@Net 4.0 or higher, this to enable the use of software SMA in MyOffice@Net 7.0 (Optional); CIE package version 10.03 or higher; The appropriate licenses, options and boundaries must be set, see tables below. Description CSTA PBC application CSTA PBC seat, the number of licenses, see FCO. Call@Net Application Service

Number 34 40 56

Table 6-1 Required ISPBX Licenses for MyOffice@Net. License 56 Call@Net Application Service. With this allowance license SOPHO functionality is provided as a TCP/IP service towards a Call@Net Application Server. Number 64 121 123 Description Activate CFWB on assign; must be set to TRUE (Default = FALSE); (***For Phone Settings / SMA***) PVE active; must be set to TRUE (Default = FALSE) PVE short XML; set to TRUE (Default = TRUE )

Table 6-2 Required ISPBX System Options for MyOffice@Net. Option 64 This option defines if CFWB (Call Forwarding When Busy) relation will be activated on creation of the relation by Phone Settings. Option 121 This option is used to enable (TRUE) or disable (FALSE) the possibility to start the PVE service. When this option is FALSE it is not possible to start the PVE service using OM command STSRVC or a operational system start. Once the PVE service is started no check is done on this option. Option 123 This option determines whether the output of the PVE manager is short or long XML; when TRUE, the output is short XML (2-character XML element names); when FALSE, the output is long XML (complete element names).

16

Number 277 324 325 353 365 367 368 370 371 379 380 411

Description CSTA boundary Maximum number of sockets per unit; set to 100 (Default = 50; Max = 500 Maximum number of sockets per task (CPU3000 only); must be set to 50 (Max) Maximum number of OM datablocks = 200 (Default = 100; Max = 200) PVE listen port; set to 2596 (Default) PVE maximum extension monitors; (Default = 50; Max = 65534); (*** For Phone Display ***) PVE maximum group monitors; (Default =5; Max = 65534); (*** For Group Display ***) PVE manager id; must be set to 1 (Default) PVE Server id; must be set to 12345 (Default) Maximum number of profiles; set to 10 (Default = 0; Max. = 100) Maximum number of known IP addresses; set to 10 (Default = 0; Max. = 100) SMA Unit; (Default )1 This boundary defines the unit number of the virtual SMA ports.

Table 6-3 Required ISPBX System Boundaries for MyOffice@Net. Boundary 277 CSTA boundary, this boundary should be at least the number of MyOffice users. Boundary 324 &325 These boundaries are related. The amount of sockets per unit (324) should always be at least 10 more than the amount of sockets per task (325) Recommended settings are in the table Boundary 353 This boundary defines the maximum number of OM datablocks which are available in a unit/system. MyOffice@Net users send OM commands via TCP/IP to the PBX, so the default amount of datablocks can be reached.It is advised to allow the maximum amount. Boundary 367 Determines the number of extensions that can be concurrently monitored by either Phone Display, Group Display or both. Example: boundary 367 = 50 (This is the default setting). Licensed users for Phone Display: 100. 50 Users are able to use Phone Display, user 51 is allowed to use Phone Display, but Phone Display doesn't get information from the ISPBX, due to boundary 367.

17

Boundary 368 Determines the number of groups, that can be observed. Example: boundary 368 = 5 (This is the default setting). Licensed users for Group Display: 100. Number of groups defined in the PBX: 25. All licensed users are able to use Group Display, but they can only observe the first 5 groups, due to boundary 368. Boundary 370 & 371 These id numbers are intended for future use, for the moment defaults should not be changed. Boundary 379 & 380 It is recommended to keep the amount of profiles and known IP addresses to a minimum. For an explanation on these settings see the next section: 6.2. "Projecting IP Connections". Boundary 411 OM command CHSMAR (used by e.g. MyOffice@Net) is rejected when the SMA user (DNR) is not present in the same unit where the virtual SMA circuits are configured.This boundary is introduced to prevent this. The boundary must be set in all units of the multi unit configuration. Verifying ISPBX licenses, options and boundaries can be done as follows: License check: DILICS:<license-number>,<unit-number>; Option check: DIMDAT:1,<option-index-number>,<unit-number>; Boundary check: DIMDAT:0,<boundary-index-number>,<unit-number>;

6.2.

Projecting IP Connections

The Call@Net Application Server needs access to the ISPBX for PVE data exchange, Operational Maintenance (OM) over IP and CSTA over TCP/IP. To enable this, a Client Service Profile (CSP) is used. A CSP is an entity that states whether or not a TCP/IP user is allowed to start a service and if so, which Logical Device Name (LDN) will be used. It is not possible to assign services directly to the IP port. The services and their corresponding LDN's must be assigned to a V.24 port and then mapped over IP using a Client Service Profile. Note: Existing V.24 connections still can be used as the Client Service Profile only maps the authority class and protection level to the IP connection and doesn't block the use of the existing V.24 connections. Normally, only a selective group of users should be able to connect to either one of the services. Protection is introduced by means of a relation between the CSP and IP address of the Call@Net application Server. This means the ISPBX will only accept OM and CSTA commands coming from a trusted IP address therefore the IP address of both ISPBX as Call@Net application Server must be fixed. The following steps describe the procedure to

18

define the CSP and to assign this profile to the Call@Net Application Server. Note: In addition to the trusted IP address protection it is highly recommended to protect the ISPBX's by creating a dedicated ISPBX-LAN (or VLAN) Using this setup connection of the Call@Net application Server to the PBX-LAN needs to use a fixed IP address, the connection to the company LAN however can use DHCP Note: The default CSP (profile 0) should never be used as this profile does not use the trusted IP protection mechanism.

PROCEDURE: Activate IP connections to ISPBX

To activate IP connections for OM and CSTA, execute the following steps: Actions 1. Verify if OM and SS devices exist on the V.24 ports of the CPU (or CIE-2). Example: - DIPORT:11,18,20&&25; where 11,18 is the CPU address. - If necessary assign devices with ASDEVC. Note: The recommended OM equipment type is the combination 14 & 15. With using these types, the changes are not kept in the OM journal. If ordinary OM devices are selected regular backups must be made to avoid the journal to grow to big. 2. Check if the client Call@Net Application Server is related to a Client Service Profile. Example: - DIIPPR:192.168.1.5; where 192.168.1.5 is the IP address of the Call@Net Application Server. 3. If needed, assign a Client Service Profile to the client. Example: - CHIPPR:192.168.1.5,1; where 192.168.1.5 is the IP address of the Call@Net Application Server and 1 is the Client Service Profile identity. 4. Check the services on this Client Service Profile. Example: - DIPROF:1; where 1 is the Client Service Profile identity. 5. If needed, assign the required services to the Client Service Profile. Examples: - CHPROF:1,0,1,VDU010; where 1 is the Client Service Profile id, 0 means OM, 1 means allowed and VDU010 is the logical device name of the OM connection found in step 1. - CHPROF:1,1,1,SYSMSS; where 1 is the Client Service Profile id, 1 means SS, 1 means allowed and SYSMSS is the logical device name of the SS connection found in step 1.

19

6. Check authority classes and protection level of the OM device found or assigned in step 1. This device is used by MyOffice@Net modules (e.g. Phone Settings) to change settings using OM commands. Example: - DIAUPR:VDU01; where VDU01 is the used terminal. - CHSEAU: CHDEAU: CHSEPR: and CHDEPR: can be used to change authority classes and protection levels of the used terminal. More IP related OM commands: DITCPC: for displaying the IP configuration of CPU3000 and CIE-2 boards. EXPING: for checking if a system component can be reached by the ISPBX on the IP

network.

6.3.

Activate the Correct TMS Services (Optional)

The TMS service 4 (Automatic Directory Dialling) must be defined with a preferred window (service) size of 5. This can be realized with OM command ASTMSW.

6.4.

Enable Phone Settings Functions (Optional)

The Phone Settings functions Call forward when busy / on no answer and voice mail are default available for every end-user. The other functions are only available for end-users when their phone number meets certain PBX conditions. These PBX conditions are described in the following sections.

6.4.1.

Enable Follow Me and Don't Disturb

End-users can only use Follow me in Phone Settings when FCM 7 is assigned to their phone number. End-users can only use Don't disturb in Phone Settings when FCM 25 is assigned to their phone number.

6.4.2.

Enable Software SMA

To be able to use Software SMA (SOPHO Mobility Access or Remote Office) each user needs to be able to change their destination. This is controlled by FCM 75 change SMA destination entitled. How to setup Software SMA can be found in the "Network and Routing Facilities Explained" manual

20

6.4.3.

Enable Absent/present Switching

End-users can only use Present/Absent for Group calls when their phone number is part of a group and the group property 'Switch in/out of group' has been set to YES. (See also 6.5. "Group Arrangements".) The following (Read Only) Facility Class Mark is assigned: FCM 19 (Group member). (This can be checked with OM command DIFACM). End-users can only use Present/Absent for Executive/Secretary calls when their phone number is part of an Executive/Secretary pool and the group property 'Switch in/out of group' has been set to YES. The following (Read only) Facility Class Mark is assigned: FCM 21 (Executive) or FCM 22 (Secretary).

6.4.4.

Enable AEM Message

In MyOffice@Net, Presence Management is a feature for Phone Settings users. Users can set a message and transfer their calls at the same time. This way other users will be able to see the reason of absence if they call this user. The system works with status profiles i.e. In the office, Out of the office. Each user can set their default daily routine in the scheduler, and each user can also set a short-term status change to deviate from the default routine. For example a user arrives every day at 9:00h and leaves at 18:00h, so the default schedule says In the office between 9:00h and 18:00h on weekdays. If at any given day the user wants to leave early, they can switch the short-term profile Out of the office until 18:00h. The short-term profile overrules the schedule and the system will transfer all calls to the Out of office destination. At 18:00h the timer expires and the system will switch to the schedule, since in this case the schedule will say after 18:00h Out of the office the status will not change. Another example: the same user has a meeting until 11:00h they switch the short-term profile just before the meeting to In a meeting. All calls will be transferred to the In a meeting destination. At 11:00h the timer expires, and the stem will switch the calls back according to the schedule, in this case the In the office destination. If the meeting takes longer then the dedicated time, the system doesnt know that of course. This feature cooperates with AEM messaging on the iS3000 platform. If this is configured correctly the users can also turn their Presence Management status on/off by using a prefix. So our user from the second example could dial the prefix to extend the meeting period if the meeting takes longer. Another benefit is that these AEM messages are also visible on the operator console SV60E and telephone sets, so also non MyOffice@Net users will benefit. A prefix can contain the until date or time the message should be active. After this date or time the stem falls back to the default state as scheduled by the user. Table 6-4 "AEM Message prefixes" gives an overview of the default prefixes. The default prefixes are *573nn and

21

*583nnhhmm (or *583nnddmm). The *573 and *583 are the actual prefixes, the 4th digit (3) results in window 83 is used on the SS router, nn = message number, hhmm = hour/minute and ddmm = day/month. Message In the Office Out of the Office Lunch Meeting Working at home Holiday Reset message Table 6-4 AEM Message prefixes Note: These AEM message numbers are fixed and can therefor not be used for other system messages any more. As can be observed from the table above For this purpose the two prefixes need to be added on the iS3000 platform. The Result-ID for these prefixes is 82. 1. Assign the AEM prefixes (*583 & *573) in the initial dialling analysis tree with the correct amount of numbers to follow the prefix.
ASINTN:0,*583,2,82,,6; ASINTN:0,*573,2,82,,2;

Message number Prefix 00 42 43 44 45 46 *57300 *58342hhmm, hh = hour mm= minute *58343hhmm, hh = hour mm= minute *58344hhmm, hh = hour mm= minute *58345hhmm, hh = hour mm= minute *58346ddmm, dd = day mm= month *573nn, nn = message number (42-46)

The last digit is the expected number length after the prefix, 6 digits including time or date. 2. Assign the TMS window to use, per default the Switching Services router uses window 83 size 1 for AEM. The TMS Digit position declares which number in the prefix corresponds to the default window, in our case digit 4 of the prefix: ASTMSD:4; If necessary the windows size can be changed via ASTMSW: ASTMSW:83,1;

6.5.

Group Arrangements

The MyOffice@Net application Group Display needs group definitions to be projected in the ISPBX. All type of groups can be distinguished: normal, ACD etc. Creating and modifying groups is beyond the scope of this manual. Consult the Call@Net Voice Facilities manual for details concerning group arrangements.

22

Related OM commands: DIGRPA, CRGRPA, ASGRPM, DEGRPM, CHACDD. Details concerning these OM commands can be found in the Call@Net OM commands (MML) manual. Users of Group Display must be supervisor or member of the group they wish to monitor. Group members, who are enabled to pick up group (or exec./secr.) calls, must have FCM 20 assigned. The code (prefix) for individual call pickup can be found using OM command DINARS. Example: DINARS:0,34; In case of a FIN or a DPNSS cluster, all ISPBXs must use the same call pickup code.

6.6.

Saving Changes and Starting PVE Service

Start the PVE service on the ISPBX to enable data exchange with the Call@Net Application Server. (The supporting module @Net-Core is the interface to the PVE service on the ISPBX.) Startup is realized with OM command STSRVC:0,<unit-nr>;. Verification of the running service: DISRVC:0,<unit-nr>;. The PBX reply started means the PVE service is running on the PBX. The PBX reply connected means the PVE service is running on the PBX and @Net Core is running on the Call@Net Application Server.

Make a backup of changed projecting by creating a new MIS file with OM command GEBUMI.

6.7.

Multiple PBXs and MyOffice@Net

The phone numbers used in a MyOffice@Net system need to be unique. For single unit PBXs and FINs (FIN = Fully Intergrated Network) the phone numbers (DNRs) are unique by default. The DNR (Directory number = phone number) is used to identify the internal phone number. For a DPNSS network, it is possible that the phone numbers in the network are not unique. To solve the problem of not unique phone numbers in a MyOffice@Net system serving multiple PBXs (a network), the term NDNR (Network DNR) is used. The NDNR must be unique within the served (PBX) network. Closed numbering scheme. When phone numbers (DNRs) in a DPNSS network are unique for every PBX of this DPNSS cluster, the numbering scheme is called CLOSED. (The first digit(s) of the phone numbers differ for every PBX of the DPNSS cluster.) For this type of numbering scheme the NDNR = DNR. Open numbering scheme. When phone numbers (DNRs) in a DPNSS network are NOT unique for every PBX of this DPNSS cluster, the numbering scheme is called OPEN. For every

23

PBX of this DPNSS cluster the CLID (Cluster Identity) is used to identify each DPNSS node. For this type of numbering scheme the NDNR = CLID + DNR. The 'N' (Network part) of the NDNR is equal to the CLID. Example: the DNR range of PBX1 and PBX2 is both 3000 ~ 4999. The CLID of PBX1 is 11 and the CLID of PBX2 is 12. The NDNR range of PBX1 is now 113000 ~ 114999 and the NDNR range of PBX2 is 123000 ~ 124999. The table below lists the option, which is involved in the type of numbering scheme. This option must be set the same for each node in a DPNSS network. Number 40 Description Closed number scheme in network. (Default = OFF)

Table 6-5 ISPBX System Options for Open/Closed numbering scheme. When option 40 is not set (this is the default setting), the PBX uses an open numbering scheme and the NDNR = CLID + DNR. When option 40 is set, the PBX uses a closed numbering scheme and the NDNR = DNR. Note: MyOffice@Net is always using the NDNRs of all PBXs. With option 40 = OFF (default), MyOffice@Net uses NDNR = CLID + DNR; even for single unit PBXs or multi unit PBXs (FIN). Be sure you use NDNRs as well and NOT just the DNRs in such case. Another option is to set option 40 to ON for MyOffice@Net systems serving single unit PBXs or multi unit PBXs (FIN), then NDNR = DNR.

6.7.1.

DPNSS Clustered ISPBX

When the PBX is a DPNSS node, the following points must be taken into account: Each node can be a single unit PBX or a multi unit PBX (FIN); (For a FIN the rules of 6.7.2. "Multi Unit ISPBX"apply.) Each node needs an IP connection to the IP network; Each node needs its own PVE connection to the MyOffice@Net Server; Each node needs its own CSTA connection to the MyOffice@Net server; Each node needs its own OM connection to the MyOffice@Net Server (Optional, for PS only); Each node needs one SS connection to the MyOffice@Net Server (Optional, for PS only). NDNR = DNR when option 40 = ON. NDNR = CLID + DNR when option 40 = OFF.

24

6.7.2.

Multi Unit ISPBX

When the PBX is a multi unit PBX (FIN) the following points must be taken into account: Each unit needs its own IP connection to the IP network; Each unit needs its own PVE connection to the MyOffice@Net Server; Each unit needs its own CSTA connection to the MyOffice@Net Server; At least one unit needs an OM connection to the MyOffice@Net Server (Optional, for PS only); Only one unit of the FIN needs an SS connection to the MyOffice@Net Server (Optional, for PS only). NDNR = DNR when option 40 = ON. NDNR = CLID + DNR when option 40 = OFF. All units must have the same PBX name.

25

7.

Installation

This chapter describes the installation procedures. The default language for MyOffice@Net is English. Additional languages are included in the installation; they can be enabled after installation, see chapter 8.5. "Additional Settings". You can also change the default language.

7.1.

Check SQL Server

When you want to use MSDE as database engine, skip this procedure. This procedure describes how to check that the SQL Server is running and accessible, which is necessary for the MyOffice@Net installation. Execute this procedure before you start with 7.4. "Server Installation". Preconditions: 1. Check the requirements for the SQL Server, section 3.2. "SQL (Database) Server Requirements" 2. SQL Server 2000 is installed. (How to install this package is beyond the scope of this manual.) Steps: 1. Log on as Administrator to the SQL Server. 2. Check if the SQL Server is running. (When the SQL database engine is not running, restart it.) - Open the SQL Server Enterprise Manager: Start Menu > Programs > Microsoft SQL Server > Enterprise Manager. - Expand the SQL Server database tree. - Check if the SQL databases are connected (SQL Server icon is green) and if not, connect it: select the SQL Server, right click on it and select 'connect'. Figure 7-1 "Create the SQL Server Database connection." shows an example of how to connect the SQL Server to the databases.

26

Figure 7-1 Create the SQL Server Database connection. 3. Check the correct authentication mode for logging in on the SQL Server: - Select the SQL Server, which is used for MyOffice@Net; - Select SQL Server properties by a right mouse click on the selected SQL Server; - Select TAB "Security" and select SQL Server and Windows as authentication mode. Figure 7-2 "SQL Server authentication mode" shows an authentication type selection example.

27

Figure 7-2 SQL Server authentication mode 4. Check the correct communication protocol is selected for the SQL Server: - Select the SQL Server, which is used for MyOffice@Net; - Select SQL Server properties by a right mouse click on the selected SQL Server; - Click "Network Configuration" and check TCP/IP is one of the enabled protocols. Note: It is advised to secure the MSDE/SQL database access by using a (non empty) password for all users. See Microsoft knowledge base article Q313418

7.2.

MSDE Installation

When you want to use SQL Server as database engine OR you are using an already installed and running version of MSDE, skip this procedure. This procedure describes how to install MSDE on the Call@Net Application Server. Execute this procedure before you start with 7.4. "Server Installation".

28

Preconditions: 1. Check the system requirements for the Call@Net Application Server. Steps: 1. Log on as Administrator to the Call@Net Application Server. 2. Read the readme.txt file in the MSDE2000 folder on the CD-ROM. 3. Start the Installation of MSDE from the CD-ROM: - Select Start > Settings > Control Panel. - Select Add/Remove Programs > Add New Programs. - Browse on the CD to MSDE2000 and run the file install.bat. DO NOT RUN setup.exe! 4. Follow the instructions of the MSDE installation program. 5. The installation will be executed and the PC needs a reboot tot start MSDE. 6. Continue to check the necessary windows components.

7.3.

Check System Requirements

Use section 3.1. "Call@Net Application Server Requirements" to check the hardware and software requirements. To check if the required windows components are running use the following procedure:

PROCEDURE: Check required Windows components

Actions 1. Select Start - Control Panel - Add or Remove Programs 2. On Windows 2000 servers browse to the list of installed components to see if .Net Framework 1.1 is installed, if not install it before continuing. (on Windows 2003 systems, select Start > Control Panel > Administrative Tools) 3. Select Add Remove Windows Components 4. Select Application Server 5. Click on Details 6. Select ASP.NET 7. Select Enable Network COM+ Access 8. Select Internet Information Services (IIS) 9. Click on Details 10. Select Internet Information Services Manager 11. Select World Wide Web Services 12. Click on Details 13. Select Active Server Pages

29

14. Click on OK (3x) 15. Click on Next 16. Click on Finish 17. Reboot the system.

7.4.

Server Installation

The default installation paths: - Default path for executable files: C:\Program Files\Philips\ - Default path for data files: C:\Philips\Data Files\ Preconditions: 1. Check the ISPBX requirements. 2. Check the system requirements for the Call@Net Application Server. Steps (on Windows 2003 systems): 1. Log on as Administrator to the Call@Net Application Server. 2. Install the Sentinel dongle driver from the CD-ROM. 3. Start the Installation of MyOffice@Net from the CD-ROM: - Select Start > Settings > Control Panel. - Select Add/Remove Programs > Add New Programs. - Browse on the CD to MyOffice@Net\Disk1 and start setup.exe. 4. Click 'Next' in the 'Welcome' screen. 5. Select the destination folder and click Next. 6. The 'Get MSDE or SQL Server info' screen appears. - When MSDE is used as database engine, the default name '(local)' can be used in the 'Server:' field; enter sa for 'LoginID' with the sa password for 'Password'. If no password was set previously the application installer will ask whether to change the password. - When SQL Server is used as database engine, enter the name of the SQL Server in the 'Server:' field, sa for 'LoginID:' with the sa password for 'Password:' Note: For default installations of SQL Server the sa password is 'sa'. That may be different when an existing SQL Server is used. Click 'Next' after the required data is entered. The installation procedure tries to connect to the database with the given input. When this fails, check if the settings is correct. 7. The installation will be executed and asks for a reboot confirmation at the end. Click OK. 8. Wait until the PC is restarted and the installation has finished. -

30

7.5.

Client Installation

When the MyOffice@Net applications are used on a client PC, some client side software components are needed. These software components are stored in one compressed file. This file can either be deployed to the client PC prior to first usage of the MyOffice@Net application, or be down loaded automatically from the Call@Net Server on the first activation of the MyOffice@Net application. The choice depends on whether or not the users of client PC's have local administrative rights. Deployment prior to first usage is the proper mechanism when the users of the client PC's don't have administrator rights on their own PC. The deployment can be done via standard Windows tooling such as SMS or Active Directory. To support this type of deployment, an MSI file with the client software components is delivered together with the MyOffice@Net package. From this file the client side components are installed by the Windows Installer package; this package is standard in Windows 2000 and Windows XP. When the user of the client PC has administrative rights and the proper versions of the client side software components are not present on the client PC, they are down loaded automatically from the Call@Net Server at the first usage of the MyOffice@Net applications. Restart the client PC when requested. Note: When you want to upgrade from an existing version of MyOffice 7.0 to a newer client package, install the msi file with the following command line parameters:
msiexec /i "MyOffice@Net Client Components.msi" REINSTALL=ALL REINSTALLMODE=vomus

To enable easy access to the MyOffice application, a shortcut can be placed on the desktop of the client PC. If different users must be able to login into MyOffice, it is advised to create a socalled 'Program URL' (like "C:\Program Files\Internet Explorer\IEXPLORE.EXE" -new http:// PHILIPS-6CQ5QZG/CA/myoffice.aspx"). The shortcut should be deployed to the end users with standard IT procedures.

7.6.

Upgrade & Reinstall

Upgrade to release 7.0 from an older version of MyOffice@Net is not supported.

31

8.
8.1.

General Configuration
Internet Explorer Settings

The following procedures describe the configuration of the general part of MyOffice@Net.

The following settings are recommended for Internet Explorer on client (and Server) PC: Disable the setting: Reuse windows for launching shortcuts. You can find this setting by selecting (in Internet Explorer): Tools > Internet Options > Advanced. The setting is located in the Browsing section. For the setting Check for newer versions of stored pages, we advise: Automatically. You can find this setting by selecting (in Internet Explorer): Tools > Internet Options > General (Temporary Internet files section) > Settings. When you select another option, this can lead to either old pages being displayed (too few refreshed) or slower responses and higher server load (too many refreshes). If a proxy server is used, make sure either the option Automatically detect settings or the option ByPass proxy server for local addressess is selected. You can find these settings by selecting (in Internet Explorer): Tools > Internet Options > Connections-tab and then click the "LAN Settings" button.

8.2.

Security Settings

After installation of MyOffice@Net the server security policies have to be set in order to match the security policy of the network. MyOffice@Net is equipped with the SOPHO Operating System Security Configurator tool. This tool can be used to: Enable MyOffice@Net applications in case the Windows Firewall is turned on; Note: The Windows Firewall is introduced in Windows XP Professional, Service Pack 2 and Windows Server 2003, Service Pack 1. Enable DCOM and other Services or Tasks for MyOffice@Net, if the password of the PBC-UserAccount has changed. This can happen if the security policy forces you to change passwords every x days. Note: If you changed either the name (PBC-UserAccount) or the password with the Security Configurator, you have to run it again after a reinstall or upgrade of MyOffice@Net. If neither option is valid for your installation this procedure can be skipped. You find the Security Configurator in
Start\Programs\MyOffice@Net\Support\Security Configurator.

32

PROCEDURE: Windows Firewall Configuration

The following settings enable clients to connect to the MyOffice@Net Server. Actions 1. 2. 3. 4. 5. 6. 7. 8. 9. Open Windows Firewall in the Control Panel. Make sure Windows Firewall is On (General tab). Select the Exceptions-tab. Click Add Port. Specify a name for the port; e.g.: HTTP-Port-80 Specify 80 for Port number and select TCP-option. Click the Change scope-button. Select the Custom list option. Specify the subnet(s) that should be allowed to connect to this machine via HTTP-port 80; e.g.: 192.168.111.0/255.255.255.0 where 192.168.111.0 is your subnet-address and 255.255.255.0 is the corresponding subnet-mask. If you need more subnets then separate them with a comma. 10. Click the OK-button (twice). 11. Select the Advanced-button. 12. Select the Ethernet-adapter used to connect to your clients. 13. Click on the Settings-button on the right-side. 14. Check the option "Web Server (HTTP)". 15. Click OK-button. 16. Click OK-button again to close Windows Firewall.

PROCEDURE: Configure the MyOffice@Net server for Windows Firewall

Actions 1. Open the Security Configurator via: 2. After starting the Security Configurator, the Windows Firewall tab shows:
Start\Programs\MyOffice@Net\Support\Security Configurator

33

3. Set all check boxes for the MyOffice@Net applications to enable these applications. If no Windows Firewall is present this list will be empty. If Management@Net is also installed on the same Call@Net Application server more programs and services will appear in the list. 4. Click OK.

34

PROCEDURE: Change name/password PBC-UserAccount

Actions 1. After selecting the Identity tab, the following appears:

2. If required according to the security policy the default useraccount PBC-Useraccount can be changed to a valid username on the domain. The password can also be changed. The tool will enable DCOM and other Services or Tasks for the new user for MyOffice@Net. 3. Click OK to close the window.

35

8.3.

Activate the Licenses

Connect both the MyOffice@Net application dongle and the OpenWorX OAI dongle to the MyOffice@Net server. The popup 'New hardware found' can appear when the MyOffice@Net dongle is inserted. When not automatically registered, the driver for this application dongle can be found: for Windows 2003 in C:\Program Files\Common Files\SafeNet Sentinel\Sentinel System Drivers for Windows 2000 SP 4 or higher in C:\Program Files\Rainbow Technologies\Sentinel System Drivers

Select sntnlusb.inf for the driver and press OK. Note that in case of an iS3000, there is no OAI dongle. Preconditions: 1. The dongles are connected to a USB port. 2. The required license file is accessible. Activate the MyOffice@Net Licenses Steps: 1. Start the License Manager: Start-Menu > Programs > MyOffice@Net > Configurators > License Manager. 2. Load the license file: License Manager > Menu > Load license File. 3. Verify all the necessary licenses are present. 4. Close the License Manager. Activate The OpenWorX OAI license MyOffice@Net communicates to the SOPHO 2000 IPS or UNIVERGE SV7000 via the OAI link. This link is controlled by a license and corresponding dongle. This hardware key can use a special CTI OAI license or an ordinary OWXRuntime license if OpenWorX is installed on the MyOffice@Net server. Steps: 1. Start the NEC Security Device: Start-Menu > Programs > MyOffice@Net > Configurators > NECConfig. 2. If the Security Device ID is not read automatically then update the driver for the

36

corresponding USB dongle first. 3. Enter the serial number and activation key of the dongle in the fields on top of your screen, press add serial number . 4. The middle part of the NEC Security Device shows the installed applications and activation keys. The required application is called OAIDLL 5. The lower part of the NEC Security Device can be used if a dongle needs to be replaced. To replace a security key press Remove driver and remove the old dongle. Connect the new dongle to the system and press Install driver. 6. Close the NEC Security Device. Note: Removing the dongle will immediately result in system failure, there is no 72 hrs. grace period.

8.4.
Steps: 1. 2. 3. 4.

Enable Access to the ISPBX

Start MyOffice@Net and log in as user 'Administrator' (no password). Go to 'System Settings'. Go to the 'Connectivity' tab. Click the New-button (in the lower right corner) and enter the connection. Enter a meaningful name in the PBX Name field. Select the required Synchronization option. - "Synchronize Always" means every time you reboot the computer. This option is recommended for the iS3000 because of the dynamic moves of database entries. - "Synchronize Once means only the next time you reboot the computer. This option is recommended for the SV7000 and 2000 IPS. Enter the IP address in the IP Address / HostName field. Select the appropriate PBX type. If the PBX type is SV7000, you can specify the 'Special Monitored Number' that is used for 'Call Pickup' in Group Display. You also have to define that number in the SV7000 PBX, see chapter 4. "UNIVERGE SV7000 Requirements and Preparations". If the PBX type is SV7000, you can specify a username and password for the MAT interface towards the PBX; configure the same username and password on the PBX. In the call forwarding section of the window, you can define if the user can enter different destinations for in- and external calls. If splitting is selected, this should be enabled in the PBX; if splitting is enabled in the PBX, you can switch it off, so that is it disabled on the OAI/CSTA interface. 5. Click Apply.

37

8.5.

Additional Settings

The Miscellaneous part of the administrator window is used to change various additional settings. 1. Start MyOffice@Net and log in as user 'Administrator' (no password). 2. Go to 'System Settings'. 3. Go to the 'Miscellaneous' tab to enter or change the following settings: - Language Here you select the default language, which will be offered to all users when using MyOffice@Net applications. When additional languages are installed, MyOffice@Net users can select their preferred language with Personal Settings. Note: if you change the default language, the MyOffice server must be rebooted to make the setting active. Email Server Enter the name of the mail server. - Voicemail Here you select whether the integrated voicemail is used or an external voicemail system and you enter the voicemail number. The voicemail server is defined in the Advanced Settings window. See also section 9.12. "Voicemail Configuration". Click Save changes. 4. Click Go to Additional Settings to enter or change the following settings: - Display Group Number Only Activate the check-box when only phone numbers must be displayed in the Group Display module instead of the names from the directory. - Audio File This file is played when a new call arrives for the group. Any *.wav sound file can be selected but dont overdo it! Audio files are played completely when an event happens, a 5 minute music file will play 5 minutes. 5. Click Apply to save your changes. 6. Click Back to return to the first Miscellaneous window. -

8.6.

Choose the Authentication Mode

After installation of MyOffice@Net, the authentication mode to login to the application has to be chosen. There are two possibilities: Authentication via the central authentication web portal OR Integrated windows authentication.

38

Authentication via the central authentication web portal This is the standard option. Users login via a loginscreen with a username and password stored in the database. If the user forgets the password a button can be selected to have the system send the password to the email of that user. The email address of the user must therefor be known in the CA database. Also, the Mail server must be registered, execute the follwing steps to do so.

Steps: 1. 2. 3. 4. 5. 6. Start a command prompt via Start > Run >cmd. Enter nslookup, enter set type=MX, enter your domain. Write down the name of the mail exchanger with the lowest MX preference. Login to MyOffice@Net as Administrator. Go to the Miscellaneous tab. Enter the name of the mailserver found and press Apply.

Figure 8-1 Nslookup of mailserver, the server with the lowest MX preference will be registerd in the Mail Configuration window Integrated windows authentication IF YOU DO NOT WANT TO USE INTEGRATED WINDOWS AUTHENTICATION THEN SKIP THIS PART. In this case, when a request for download of a MyOffice@Net web page is sent to the web server, IIS will first check if this request comes from a known user in the active directory. The active directory username is then compared with the CA database. If both settings are correct the user will directly gain entry to the required MyOffice@Net application. If not the request will be redirected to the MyOffice@Net login screen.

39

Steps: 1. Start IIS Management Console: Start Menu > Programs > Administrative Tools > IIS Management Console (or select Start > Administrative Tools > Internet Services Manager). 2. Expand the Default Web Site tree 3. 'Right click' on CA and select properties 4. In the Directory Security TAB press Edit Anonymous Access and Authentication Control 5. Remove the check box Anonymous Access and choose Integrated windows authentication 6. Press OK (twice) and restart the IIS service (via Control panel > Administrative tools > Services)

40

9.

Application Configuration.

This chapter describes the configuration of the MyOffice@Net application modules. When a certain module is not used, the associated section can be skipped. After this chapter, the applications are ready to be started on the MyOffice@Net clients.

9.1.

User and Company Directory Configuration

The company directory is not only used as source for the directory browser, it is also used for user administration. Note: When Windows accounts are used for logging in MyOffice@Net, you're automatically logged in by your normal user account when starting MyOffice@Net. Use this URL to be able to login as Administrator to CA: http://<MyOffice@NetServerName>/ca/ MyOffice.aspx?WCI=Login. Localhost is not allowed as <servername> , IP address is. Steps: 1. Login to MyOffice@Net as Administrator (default no password). The first login from a new PC will trigger a download of client components. Accept the download and press OK 2. Select the System Settings option. 3. Select the Company Directory window. This administrator interface looks almost the same as the window of a user login in to Directory Browser, you can search the database with names of employees already entered etc. However, when you login as administrator you can also enter data.

Figure 9-1 Company directory

41

The top part of the Company Directory UI shows the following fields: - The element selection dropdown list, you can enter Employee, Hierarchy or Extension data, select Extension to see if the data is entered automatically via the MATSync process. - The search field(s) can be used to enter search criteria to search the database. - The search button will search the database. - The clear button clears the search field. The middle part of the screen is where the information is displayed. On the bottom-left side of the screen six buttons can be found (in employee view) to configure the appearance of the electronic phone book. Basically, all users can choose their own search and result criteria, the administrator decides what fields they can choose from and what the default criteria are. From left to right: The 'Directory Browser' button gives access to the electronic phone book. The 'Personal Details button' is used to determine what fields from the phone book will be displayed when 'detailed information' of a directory entry is displayed. since you are logged on as Administrator these are the details of the administrator. The 'Configuration' button allows you to change the appearance of the search fields and results. Every user has the option to do this. The fields as added in the 'Search on' section are scanned by the browser to find the text string the end-user invoked. The fields as added in the 'Find as result' section are returned to the end-user his/her browser. The 'Combine Search Fields' checkbox is used to offer only one field in the Company Directory for defining a text string to search for. The search fields are selected in the Personal Settings section. The 'Import' button allows you to import users from a csv file (which can be opened as an excel sheet). The template is provided via the download link. The 'Protection' button allows the system administrator to restrict the number of fields available to the user to search on or find as result. The 'Default Config' button allows the administrator to choose the default settings for the users. On the bottom of the screen you also see an extension field and dial button. The administrator user interface is an extended normal user interface. The normal users cannot change the company directory however. On the bottom right side of the screen are the edit buttons, to add, change or delete entries. To change or delete an entry it first has to be selected from the list. The buttons are not active until you click on an item in the list.

42

9.2.

How to import users

1. Login to MyOffice@Net as Administrator. 2. Select System Settings. 3. In the Company Directory window, click on the Import button (in the lower left corner). 4. Right-click the link: Download Template CSV and select either the full unicode template or the minimal template. 5. Select save target as, this action will save the template in csv format. This template can be used to import users. The template is a CSV text file. You can view and edit this file in Notepad or Excel. the first line in this file shows the fixed field names. Do not change these field names. The system mandatory fields are: Companyname and Extension, for correct operation of MyOffice@Net the following fields must be filled for each user: - pbxID; only applicable in multi-pbx environments - extension; - firstName; - middleName; only if applicable; - lastName; - email; - division; the 2nd level of the hierarchy; - department; the lowest level of the hierarchy; - alternateNumber; - companyname; the top level of the hierarchy; - PBC_LoginName; the name used for basic authentication, if not supplied the combination of first and lastname will be entered, this entry must be unique.; - PBC_NTLogin; the domain login name of the user, including the domain used (only required when using the Windows login). When the complete hierarchy information is entered this import automatically creates the companys hierarchy. If the hierarchy information is not supplied the entries will all go to the default hierarchy. Note: To assign more than one extension to a user, use the other extension fields like 'AlternateNumber'. It is allowed to assign an extension to more than one user, however in some applications where number/name translations are done (like Phone Display) the name might be incorrect. 6. Upload the thus created CSV file using the Browse and Upload buttons. 7. Use the Back button to see the results in the company directory.

43

9.3.
1. 2. 3. 4. 5. 6. 7.

Manually create the hierarchy of the customer

In the Company Directory window, select Hierarchy from the element selection box Click in the tree on the left on company level. Enter the new company name in the field on the right and press Save. Expand in the tree on the left on the new companys division level. Enter the new division names in the field on the right and press Save. Expand in the tree on the left on the new companys department level. Enter the new department names in the field on the right and press Save.

Note: The default hierarchy can only be deleted after all extensions are moved to the new hierarchy structure. All extensions, as well as all employees need to be part of the hierarchy structure to be able to use them in the group display pane of the MyOffice@Net UI. If an extension is not part of a specific department (for instance a telephone in a conference room) the extension can be stored on company level.

9.4.
1. 2. 3. 4.

Manually create a MyOffice@Net user

5. 6.

7. 8. 9.

Select Employee from the element selection box. Press the new button. Enter the primary user information of the user in the appropriate fields. Enter the security details of the user. The NT login name is the full username of the windows domain <domainname>\<username>. When this is used the windows authentication will be used as authentication for MyOffice@Net. When basic authentication is preferred enter username and password in the appropriate fields. The user name must be unique. To assign more than one extension to a user, use the other extension fields like 'AlternateNumber'. Select user role MyOffice. Select the extension number and PBX of the new user from the drop down lists. It is allowed to assign an extension to more than one user, however in some applications where number/name translations are done (like Phone Display) the name might be incorrect. The name that the SQL server finds first will be the one used for display. Enter the Pin code to be used for voicemail, without Pin code the user will not get a voicemail box. Select the Company, Division and Department of the user in the appropriate fields. Press Apply to save the entry.

44

9.5.

External Directory Configuration

External numbers can be entered in the database via the following procedure: Steps: 1. 2. 3. 4. Login to MyOffice@Net as Administrator. Select System Settings. Select the External Numbers tab. Add a external number by clicking the 'New' button (in the lower right corner).

Like to the company directory also the external directory can be imported using a CSV file.

Figure 9-2 External directory configuration

9.6.

Web Directory Configuration

By Web Directories of MyOffice@Net are meant; any web based directories available on the internet. The Web Directory Configuration creates a hyperlink to this internet phone book. When the user is searching this directory via MyOffice@Net the results will be scanned for telephone numbers. If a number is found on that external web page, a hyperlink is created from this telephone number to the MyOffice@Net dialler, thus allowing the user to dial this number by a single click. The background application responsible is the Diabho number scan. This application requires local settings on the client PC, these browser extensions will be down loaded to the user on first use. Diabho is based on a text search engine there for will only work if the internet directory gives text based results as well.

45

Steps: 1. Login to MyOffice@Net as Administrator 2. Select System Settings. 3. Select the Web Directory tab.

Figure 9-3 Web directory configuration 4. To assign a new Internet Directory press New and enter the appropriate values: - Name; any name can be used - URL; the address of the internet phone book. Directory URL NL D UK BE Philips http://www.detelefoongids.nl/ http://www.dastelefonbuch.de/ http://www.infobel.com/uk/ http://www.infobel.com/belgium/ Match detelefoongids dastelefonbuch infobel infobel

http://pww.phonedirectory.bnl.philips.com/ phonedirectory

Table 9-1 Examples of External Directories URL's and their matches 5. Click 'Save' to store the settings.

46

9.7.

BTS Directory Configuration

In MyOffice@Net 7.0 access is possible to the BTS/Phoneware database (as used by the Supervisor 60E). MyOffice@Net 7.0 is only compatible with BTS data schema 2.3.0. BTS must be installed on an English (US) SQL server, either on the MyOffice server or on a separate server. To configure the BTS directory: 1. 2. 3. 4. 5. Start MyOffice@Net and login as Administrator (no password). Go to System Settings. Go to the Miscellaneous tab. Go to Configure the Usage of the BTS Directory. For SQL Server, Login Name, Password and Database Name fill in the appropriate values for accessing the database. 6. Fill in other fields as required. 7. Press Save to store the settings.

Figure 9-4 BTS directory configuration

47

9.8.

Configure the Dialing rules

To enhance flexibility in dialing outside the company, a set of dialing rules can be configured so that possible prefixes are automatically added to or removed from the dialed number. The dialing rules are applied to all calls setup from MyOffice@Net applications. To configure the dialing rules: 1. 2. 3. 4. 5. Start MyOffice@Net and login as Administrator (no password). Go to System Settings. Go to the Miscellaneous tab. Go to Configure the Dialing rules. Fill in the National Access Code, International Access Code and Country Code as valid for your local site. 6. Fill in the Outside Line Prefix and the Internal Number Length as valid for your PBX. Only numbers longer than the Internal Number Length are converted! 7. Press Apply Changes to save the entered values. 8. Test with some typical external numbers: fill in the number as present in the directory and press Test Dialing Rules. The converted number is shown.

Figure 9-5 Dialing rules

48

9.9.
1. 2. 3. 4. 5.

Assign MyOffice@Net modules to a user

Log in to MyOffice@Net as Administrator. Select Advanced Settings. Select User Administration. Enter the (first part of the) user's name in the search box, and click the Search button. Select check boxes for the applications that you want to assign to the user. (Some applications require a login name and password. You will be prompted if necessary.) 6. To save your changes, click the Apply button.

9.10.

Phone Settings Configuration (Optional)

End-users can activate/deactivate the following functions using Phone Settings: Call forward when busy for internal and/or external calls. Call forward on no answer for internal and/or external calls. Follow me. Don't disturb. Voice mail - phone number to listen voice mail messages; used by Phone Display to connect to voice mail server. Present/Absent switching for group calls.

In the Connectivity tab of the System Settings window, you can split the call forwarding settings up into internal and external. See section 6.4. "Enable Phone Settings Functions (Optional)" how to entitle iS3000 end-users for all or parts of the Phone Settings functions. iS3000 End-users can also activate/deactivate: SOPHO Mobility Access (SMA). Present/Absent switching for Executive/Secretary calls.

9.10.1. SMA Settings

SOPHO Mobility Access (Software SMA) offers SOPHO iS3000 features to the 'remote telephone user'. The remote user can be connected via the PSTN, ISDN, GSM or private network. Once the connection is established between the remote user and the iS3000, the remote user can act like a local user, with the restrictions of the intervening network.

49

Figure 9-6 Functional Diagram of SMA. For all iS3000 programming issues, refer to the Call@Net FIM Networking and Routing manual. A MyOffice@Net SMA user starts the SMA function by selecting the Working at remote location option and entering the remote phone number in the Phone Settings application (including trunk access code and area code). The SMA functionality requires license (number 66) "Number of SMA users". This license verifies the number of activated Software SMA users against the number licensed. An SMA user is activated when its CLI-number has been assigned to a virtual SMA circuit. This assignment is done via the MyOffice@Net Phone settings application. The only thing Phone settings checks in order to use Software SMA is that the DNR of the user has FCM 75 "Change SMA relation entitled". If so, the user can define the remote location and activate or de-activate Software SMA via Phone Settings.

9.11.

Group Display Configuration

If not previously done execute the following steps: 1. 2. 3. 4. Start MyOffice@Net and log in as Administrator. Go to 'System Settings'. Go to the 'Miscellaneous' tab. Click Go to Additional Settings to enter or change the following settings: - Display Group Number Only Activate the check-box when only phone numbers must be displayed in the Group Display module instead of the names from the directory. - Audio File This file is played when a new call arrives for the group. Any *.wav sound file can be selected but dont overdo it! Audio files are played completely when an event happens, a 5 minute music file will play 5 minutes.

50

5. Click Apply to save your changes. Note: When changes are made in a group (add/delete group and/or group members) in one of the ISPBXs, the Group Display application needs to be restarted to synchronize with the changes. There are 2 kinds of Group Display. In User Administration, you can give users access to one of the following: My Groups displays only the group(s) of which the user is a member or supervisor, All Groups lets the user choose from all available groups in the ISPBX.

9.12.

Voicemail Configuration

If a voice mail application is installed on your network, you can add a voice mail button to the MyOffice@Net portal: 1. 2. 3. 4. Log in to MyOffice@Net as Administrator. Click Advanced Settings and select Server Administration. Select Voicemails & Settings. In Application Properties, enter the location of the Voicemail Server's login script.

For more information on configuring voice mail, please refer to the documentation that came with the voice mail application.

51

Figure 9-7 Voicemail configuration.

52

10.
10.1.
-

Troubleshooting
General

? Which information is stored in which database? United database contains the CA account information, the personal directories and the Directory Browser configuration data, the 'mirrored' PBX data, the SMA data, the Function Key Menu's and Phone Display's List of Calls data. PBX database (belongs to the CM@Net module) contains the PBX connection information. "Phonebook" database is the source for BTS Directory (Optional).

? Automatic login to MyOffice@Net applications using the users' WinNT names doesn't work... The access rights to CA may be restricted. To check and change this, execute the following steps on the Call@Net Application Server: 1. Select: Start > Programs > Administrative Tools > Internet Service Manager. 2. Open properties for: Internet Information Server\<this PC name>\Default web Server\CA. 3. Use the right mouse button and select 'properties'. 4. Select the TAB 'Directory Security'. 5. Click 'Edit' in the section: 'Anonymous access and authentication control'. 6. Disable (deactivate) the 'Anonymous access' check-box and click 'OK'. 7. Save CA properties by clicking 'OK' Note: Of course all MyOffice@Net users must have permission to login to the Call@Net Application Server. This can be checked on the PC running the Domain Controller. ? The Call@Net Application Server is reacting very slowly... It is recommended to have the SQL Server and the Call@Net Application Server in the same Windows domain. At least, make sure the connection between SQL Server and Call@Net application Server uses the TCP/IP protocol. Consult 7.1. "Check SQL Server" for the correct setting on the SQL Server. For the Call@Net Application Server (client of SQL Server) execute the following steps: 1. Open the configurator by Start > run... 2. Enter C:\Winnt\system32\cliconfig.exe (clicfg.exe). A window as in Figure 10-1 "Setting the default network library protocol for an SQL Server's client." appears. 3. Set the default network library protocol to TCP/IP. 4. Confirm the setting by clicking the buttons 'Apply' and 'OK'.

53

Figure 10-1 Setting the default network library protocol for an SQL Server's client. ? A security warning appears when a MyOffice@Net application is started... Such a warning can popup when Phone Display, Group Display or Directory Browsers' External directory is used for the first time. Activate the check-box Always trust content from NEC Philips Unified Solutions B.V. and confirm with the Yes button. A possible restart of the PC can be executed later. ? Applications are crashing after 1 day... When you work with Application Pools in IIS, check the properties of NECPhilips Pool1 and NECPhilips Pool2: 1. Open the Internet Information Services (IIS) Manager. 2. Right click on NECPhilips Pool1. 3. Select Properties. 4. Check that on the Recycling tab, all options are cleared. 5. Check that on the Performance tab, the option Idle timeout is unselected. 6. Click OK.

54

? CallLog does not start up... This is caused by problems in installation of Microsoft.Net component. Reinstall it in the foolwing way: 1. Open the Cmd window. 2. Go to:
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322

3. Type:
aspnet_regiis.exe -i

10.2.

Tracing: Diagnostic Monitor

? How can I look at trace files while they are created... Some modules of MyOffice@Net generate trace files when the correct registry keys have been set. These files are stored in the Philips \ data files folder. Normally these files cannot be opened when they are active, only a copy of the file can be viewed. The Diagnostic Monitor allows you to see events as they happen. So you can check the progress and behaviour of a module, if the need arises. The same tool is used to start and stop tracing, and it allows you to save trace files for further investigation. You find the diagnostic monitor DiagMonitor.exe in C:\Program Files\Common Files\Philips\Diag@Net. In the left pane, you can select a process (called a Diag@Net client) and in the right pane you see the Events and Exceptions for that process as they happen. If the Diag@Net clients are not conclusive via the menu Options and Trace Level Settings, you can select more detailed monitoring (tracing) for some modules. Also filters can be created to exclude successful events, log only exceptions or all events etc. Note: Use the Diagnostic monitor wisely. Dont trace all events at the same time as this will not give you the right information.And too much active traces can result in system instability.

10.3.

SOPHO Info Console

With the SOPHO Info Console you can activate tracing and make a snapshot of the current status of a computer. This information can be very useful for debugging purposes by the Technical Support department. The current status can be saved in a file. Together with the snapshot you can include some attachments (database files, etc.). The option Create generates a ZIP file and a SID file (system info data). Both files must be sent to Technical Support when requested.

55

Automatically all files with extension .dfl/.mdb/.log/.ini/.txt/.pb that are in the folder Philips, are extracted. This includes: PC System info such as OS info (plus installed service packs), memory usage, running processes, network configuration settings and DCOM settings. relevant registry info. License Manager info such as fingerprint and license string. databases (info) and more.

? How do I extract information... 1. To start the tool, click the Windows Start button, point to Programs, a SOPHO product , Technical Support and then click SOPHO Info Console. 2. If you want to add file types: on the Options menu, click Attachments. Now you can enter the file type in the New Criterion text box and click on the Add button and the OK button. 3. If you want to adjust the trace settings: on the Options menu, click Trace Settings. Now it is possible to launch Diag@Net. 4. In the SOPHO Info Console window, in the right pane list view, select which system files you want included in the saved ZIP file. On the Actions menu, click Attach. A blue mark indicates that the item will be added.

56

5. On the Info menu, click User and enter the requested information for the Technical Support department. 6. On the Info menu, click Create. This may take several minutes. 7. On the Info menu, click Save As and enter an understandable name for the ZIP and SID file. List of menu functions: 1. Info 1. Create 2. Open 3. Close 4. Save 5. Save As 6. User 7. Print 8. Print Preview 9. Print Setup 10. Recent File 11. Send 12. Exit 2. Edit 1. Copy 2. Select All 3. View 1. Toolbar 2. Status Bar 3. Refresh 4. Actions 1. Open 2. View 3. Attach 4. Detach 5. More Info 6. Properties 5. Options 1. Trace Settings 2. Attachments 3. Startup Empty

Enter information for the Technical Support department

Include a file to the ZIP file Exclude a file from the ZIP file Show extra information about a selected item Adjust trace settings via Diag@Net Define the type of files that are added to the ZIP file Marked: start-up empty Unmarked: start-up and directly create (extract) a set of local system info data

57

4. Split ZIP File

Marked: the ZIP file is split up in several ZIP files, having a size that fits on a 3.5 1.44 MB floppy disk

10.4.

Directory Browser

? The Company Directory of the Directory Browser doesn't work at all... Check the link to the database in the Server Administration window. 1. Login to MyOffice@Net as Administrator. 2. Select Advanced Settings. 3. Select Server Administration. ? The photo of the MyOffice@Net user is not uploaded... Check that user IIS_WPG has write access to the folder Inetpub\wwwroot\directorybrowser\photos.

10.5.

Group Display

? Modified user names in the ISPBX are not visible in the Group Display application... Restart the Group Display application to synchronize with the ISPBX PVE service. Notice, that for MyOffice@Net the following rule applies for Name search ("look-up"): 1. Search in Directory Browser / Personal Directory; 2. Search in Directory Browser / Company Directory; 3. Search in @Net Core (PVE) database. (This data is coming from the PBX.)

10.6.

Phone Settings

? When I switch to office I get a message 'Please switch to office with your set... Phone Settings remembers the latest office telephone set you have used. When you switch to office, your DNR is moved to that set. If you did not use a local telephone set before, Phone Settings does not know were you are. By switching to office with your telephone set once, the address of the set is made known to the system.

10.7.

Microsoft Internet Explorer's Enhanced Security Configuration

? The clients encounter many popup windows... The Microsoft Internet Explorer's Enhanced Security Configuration reduces a server's vulnerability to attacks, by applying more restrictive security settings. As a consequence, it may prevent access to trusted resources and Web sites on a corporate intranet. You will be confronted with a number of dialogs you have to click through, before the MyOffice@Net

58

web-applications are trusted by Windows. The following steps give you an idea of what you should expect though this list may not be complete. 1. First time start-up of MyOffice@Net (on Win2003 +Sp1) after installation, you will get the following dialog:

Make sure that you select the check-box and click OK. 2. First time you send information to the web-application (e.g.: specify the login name) you will get the following dialog:

Make sure that you select the check-box and click Yes. 3. First time the web-application tries to show a pop-up dialog (e.g. to install an ActiveX component or to show an error-dialog) you will get the following dialog due to the fact that the pop-up is blocked by default:

59

Make sure that you select the check-box and click OK. Note that the previous dialog refers to the 'Information Bar' as shown in the next figure:

Right-click on the Information Bar and then click install ActiveX Control. You will get a dialog to accept installation of a required ActiveX Control as shown in the following figure:

60

Click on the More options-button. Now you can select the option Always install software from and then click the Install-button. 4. First time you select a defined pbx-connection during creation/adding of a user, you will get the following dialog due to the fact that the page about:blank is not trusted by default:

Click Add twice and then click Close.

61

5. First time you try to specify a number you will get the following dialog:

Click No to turn-off the AutoComplete-option. 6. First time you start GroupDisplay an Information Bar is shown due to the fact that Group Display tries to start-up in a second pop-up dialog, which is being blocked by default.

Right-click in the Information Bar and then click Always Allow Pop-ups from this site. A confirmation dialog is shown:

Click Yes.

62

A.

Concurrent users with MSDE as database engine

MSDE can handle up to 5 concurrent users. A concurrent user is a database user. This can be a person, who wants access to the database but it can also be an application (such as SuperVisor 60E). The databases, which need to be accessed using MSDE for MyOffice@Net are: United and possibly Phonebook. Calculation rules: every SysManager, SuperVisor 60E or MyOffice@Net kernel "occupies" 1 CU (Concurrent user). The @Net Central Authentication module occupies 0.1 CU and the MyOffice@Net Directory Browser occupies 0.01 CU. Example 1: how many DB users can be served properly by a stand-alone MyOffice@Net system? MyOffice@Net kernel occupies 1 CU. CA occupies 0.1 CU. Maximum DB users: (5 - 1.1) / 0.01 = 390.

Example 2: how many DB users can be served properly by a MyOffice@Net system when SM410 and 2 x SV60E use the same MSDE? MyOffice@Net kernel occupies 1 CU. SM410 occupies 1 CU. 2 x SV60E occupy 2 CUs. CA occupies 0.1 CU. Maximum DB users: (5 - 4.1) / 0.01 = 90.

63

64