PREFACE

This book is valid for MyOffice@Net, release 5.0 on a Windows 2000 Server. GUIDELINES FOR MAINTENANCE AND ADMINISTRATION OF A SERVER/ SPECIALISED COMPUTER The following six general rules should be kept in mind for a good administration and maintenance of a server/specialised 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 PBC 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 PBC 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. Loosing the server also means loosing data. That's why for every production system (servers, specialised 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. Summarised: there should be a backup policy, carefully analysed, built on the existing IT infrastructure. 4. Account maintenance / authorised use

Keep a strict list of the accounts that will have access to the server and the privileges that they might have. If unauthorised 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. Specialised software for servers Strongly consider installing specialised 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. PBC applications can use a range of ports and kind of access. PBC Hilversum 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.

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 applications are especially helpful when a user is working from another location, with the Remote Office (SMA) facility active. The installed components are listed below. 1. Installation and configuration supporting components: - Login Module. Used to limit and secure the access to Licence Manager and Connection Manager@Net. - Licence Manager. Used to activate the licences for the MyOffice@Net modules. - Connection Manager@Net Module. Used to define communication paths between ISPBX and Call@Net Application server. - @Net Core Module. Interface for data exchange between ISPBX and MyOffice@Net applications. - @Net Framework Module. Used to build a supporting web site for the MyOffice@Net applications. - Microsoft Database Engine. Used for accessing three mandatory databases: Central Authentication, Connection Manager@Net and @Net Core. Note: MSDE can be used for small and medium systems only (up to 350 end-users). Systems serving more users must use SQL Server. 2. Security and administration module: - Central Authentication. Used to administer MyOffice@Net users and the applications they are allowed to use. 3. End user (or application) modules, can be used on a client PC: - Web Dialer. Users can dial a selected entry in a MyOffice@Net application. - Directory Browser. Users can search names/numbers in 3 web directories: personal, company or external. - Key Programming. Users can program ErgoLine function keys with their favorite facilities and numbers. - Phone Settings. Users can activate / deactivate facilities such as Follow-me. - Phone Display. Users can watch display information during call handling and use caller lists for calling back parties. - Group Display. Users, which are a group member, can monitor their group activities.

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 the MyOffice@Net suite, 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: 1. Web Clients with a Windows operating system and Internet Explorer; 2. A Web Server with a Windows 2000 Server operating system, Internet Information Server and the required MyOffice@Net modules installed; 3. A database server. This can be MSDE installed on the Web Server or a separate SQL Server. 4. The PBX, running software package Call@Net 2.9B or higher. The PBX can be one of the following: - a stand alone (single unit) PBX; - a networked (multi unit) PBX; (FIN = Fully Integrated Network; network protocol is proprietary IMP) - a DPNSS network. (Each DPNSS node can be a stand alone PBX or a FIN.) Both Open and Closed numbering schemes are supported, but Free Numbering scheme is not supported.

Call@Net Application Server

Web Server
LAN

PBX

Web Client
Figure 2-1 System setup

Web Client

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.asp 2. A login screen is shown and the user must enter the User name and Password.

Figure 2-2 An example of the MyOffice@Net login 3. Central Authentication (CA) will check if the user is known in the CA database. If so, a MyOffice@Net portal is shown. This portal shows the applications, which are granted for this user.

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

Figure 2-4 The Directory Browser application has started

3.

System Requirements

The system requirements are split up into requirements for the Call@Net Application server PC, the SQL Server PC and the Client PCs.

3.1.

Call@Net Application server Requirements

The Call@Net Application server PC (MyOffice@Net modules are installed on this PC) must meet the following requirements: Minimum PC requirements: - Pentium III, 1 GHz or higher; (recommended: Pentium IV, 2 GHz) - 256 MB RAM; (recommended: 512 Mb RAM) - 4 GB free space on the hard disk with NTFS file system; - Monitor: 800 x 600 pixels / 15" screen; - Ethernet card and UTP interface. Microsoft Windows 2000 Server with Service Pack 3 or higher; (the English version of the Windows operating system is recommended) Microsoft Internet Information Server (IIS) 5. Internet Explorer 5.5 or higher;

Note: Other software and/or applications are not allowed on the Call@Net Application server PC. (Such as a Domain Controller for example)

3.2.

SQL (Database) Server Requirements

MyOffice@Net requires 3 databases for Central Authentication (CA), Connection Manager@Net and @Net-Core. A choice must be made which software controls the database access. This choice is related to the size of the MyOffice@Net system (how many users participate in the system). For small and medium sized MyOffice@Net systems this can be Microsoft Data Engine (MSDE). For big systems SQL Server (SQL 2000) is required. 1. MSDE. MSDE 2000 with Service Pack 3 software must be installed on the Call@Net Application server PC before installation of MyOffice@Net. The 3 databases must then also reside on this PC. Note: MSDE is limited to 5 concurrent users. See appendix A for some examples concerning system size/amount of users. 2. SQL Server. SQL 2000 with Service Pack 3 is required. The SQL Server software is not

part of the MyOffice@Net software package. It can be obtained from Microsoft and should be installed on a separate PC. This PC is the database server of the MyOffice@Net system. The three MyOffice@Net databases must reside on this PC. - The PC that operates as database server must meet the following requirements: - Pentium III, 1 GHz or higher; (recommended: Pentium IV, 2 GHz) - 256 MB RAM; (recommended: 512 Mb RAM) - Monitor: 800 x 600 pixels / 15" screen; - Ethernet card. - Microsoft Windows 2000 Server with Service Pack 3 or higher; - Microsoft SQL Server 2000 with Service Pack 3.

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 client requirements are: Minimum PC requirements: Pentium II, 233 MHz; For W95 clients: 64 MB RAM; For WNT and W2000 clients: 128 MB RAM;(recommended: 256 Mb RAM) Monitor: 800 x 600 pixels / 15" screen; Ethernet card. Microsoft Windows 95, Windows NT, Windows 2000 Professional or Windows XP. (For Windows 95 also winsock2 software update must be installed.) Internet Explorer 5.5 or higher.

3.4.

Installed components on Client PCs

When the MyOffice@Net applications are started the first time on a client PC, software components are downloaded and installed. These software components are stored in one compressed file. This file is downloaded from the Call@net Server PC to each client PC. Note: In case of upgrading MyOffice@Net clients, it is possible to use SMS for downloading and installing the new software components. 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;

10

For the Directory Browser the following components are installed: Diabho Configurator: DiaBHOConfig.dll stored in C:\WINNT\System32. Diabho Interceptor: DiaBHO.dll stored in C:\WINNT\System32.

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

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

Registry settings: The section HKEY_LOCAL_MACHINE\Software\Philips\Interceptor is added to the registry of every MyOffice@Net client PC (by Directory Browser installation part).

3.5.

Internet Explorer Settings

The following setting is 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.

The following settings are mandatory for Internet Explorer on a client PC when using Key Programming: Enable the settings: - Download signed ActiveX controls. This Setting must be set to enabled or prompt. - Run ActiveX controls and plug-ins. Script ActiveX controls marked safe for scripting. You can find these settings by selecting (in Internet Explorer): Tools > Internet Options > Security. Select Local intranet ,which should at least be set to Medium-low and press the Custom Level ... button.

11

4.
4.1.

ISPBX requirements and Preparations

ISPBX Requirements

ISPBX's connected to the Call@Net Application server must meet the following requirements: Running software package Call@Net 2.9B or higher; (Call@Net 2.10 is recommended) The appropriate licences, options and boundaries must be set, see tables below. Number 56 Description Call@Net Application Service

Table 4-1 Required ISPBX Licences for MyOffice@Net. Number 64 121 123 Description Activate CFWB on assign; set to YES (ON) (*** For Phone Settings / CF ***) PVE active; set to YES (ON) PVE short XML; set to YES (ON)

Table 4-2 Required ISPBX System Options for MyOffice@Net. Number 13 325 365 367 368 370 371 379 380 Description Maximum number of hotlines (0 .. 512); (*** For Phone Settings / SMA ***) Maximum number of sockets per task (CPU3000 only); set to 50 (Default) PVE listen port; set to 2596 (Default) PVE maximum extension monitors; (0 .. 65534); (*** For Phone Display ***) PVE maximum group monitors; (0 .. 65534); (*** For Group Display ***) PVE manager id; set to 1 (Default) PVE server id; 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)

Table 4-3 Required ISPBX System Boundaries for MyOffice@Net.

12

Boundary 13 determines the number of hotlines, which can be set simultaneously (both normal and delayed). Hotlines are set for example when SMA is activated in Phone Settings. Example: boundary 13 = 5 (This is the default setting). 2 Hotlines are used for phones in the elevators, in case of emergencies and 1 delayed hotline is permanently present on the Director's phone. Now only 2 users can make use of the SMA facility. Boundary 367 determines the number of users, who can use Phone Display. 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. 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. Verifying ISPBX licences, options and boundaries can be done as follows: Licence check: DILICS:<license-number>,<unit-number>; Option check: DIMDAT:1,<option-index-number>,<unit-number>; Boundary check: DIMDAT:0,<boundary-index-number>,<unit-number>;

4.2.

Projecting IP Connections

The Call@Net Application server needs access to the ISPBX for PVE data exchange, Operational Maintenance (OM) over IP and Switching Services (SS) over IP. To enable this, a Client Server profile is used on the ISPBX. The default Client Server profile can be used, but this is not recommended for security reasons. (Any Client can access the ISPBX using this profile.) A dedicated Client Server profile is defined to enable access from the Call@Net Application server to the ISPBX. The following steps describe the procedure to define the profile for the Call@Net Application server and the ISPBX device assignment to the profile. Note: A Client Server Profile is used as a protection mechanism. The Call@Net Application server is connected to an IPSBX and operates as IP client via a Client Server Profile. The Call@Net software in the ISPBX operates as IP server and checks the rights through the Client Server Profile. To activate IP connections for OM and SS, execute the following steps: 1. Verify if OM and SS devices exist on the V.24 ports of the CPU (or CIE-2). Example:

13

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, OM journalling is skipped, which is recommended when the Key Programming application is used. 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. 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 (for example: Key Programming, 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. Note: Existing V.24 connections still can be used as the Client Sevice 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. More IP related OM commands: DITCPC: for displaying the IP configuration of CPU3000 and CIE boards.

14

EXPING: for checking if a system component can be reached by the ISPBX on the IP

network.

4.3.

Activating the correct TMS Services

The TMS services (windows) 80 and up must be disabled, this can be obtained by using OM command: CHTMSL. 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.

4.4.

Key Programming compatibility requirements

Users, who use Key Programming, should automatically see their own phone type such as ErgoLine D 325, D330 or D340 when starting Key Programming. This will only be the case when the following requirements (concerning PBX packages and ErgoLine packages) are met: PPU Package PMC Package D325 D330 without download D340 without download D330 downloadable D340 downloadable 170.03.01 / 270.03.01 410.04.01 / 510.04.01 2.01.50.01 1.07.xy.01 1.07.xy.01 3.01.3y.02 3.01.4y.02

Table 4-4 Required Software packages for sending phone equipment type for Key Programming. When the users' phone does contain an older software release as in this table and/or the PPU / PMC package is older then in this table, the phone equipment type is not automatically resolved and the user has to select the correct phone type before starting programming keys with KP.

4.5.

Enabling Phone Settings functions

The Phone Settings functions Call forward when busy / on no answer and voicemail 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.

15

4.5.1.

Enabling 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.

4.5.2.

Enabling SMA

For each user, who wants to use the SMA facility, two DTX-I circuits are necessary next to the default (internal) hardware address. It is possible to create a pool of SMA circuits to serve the SMA users. How to setup SMA (SOPHO Mobility Access or Remote Office) can be found in the "Network and Routing Facility Implementation Manual". All users using SMA, must have FCM 58 (Keytone dialing) assigned on their Access DNR. The BSPT of the regular DNR (the desk phone) must have a higher priority then the BSPT of the SMA - Personal DNR. If not, the wrong Name information will be displayed. Example: use BSPT 95 for the desk phone number and 98 for the SMA - Personal number. Assigning FCM 57 to SMA users and applying Desksharing adds more functionality to the SMA users.

4.5.3.

Enabling 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 4.6. Group arrangements) The following (Read Only) Facility Classmark 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 Classmark is assigned: FCM 21 (Executive) or FCM 22 (Secretary).

4.6.

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

16

groups is beyond the scope of this manual. Consult the Call@Net Voice Facilities manual for details concerning group arrangements. 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.

4.7.

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.) Start-up 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 PC.

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

4.8.

Using a BIM as a Router

For CCS systems, the BIM should be programmed as a router to the CIE-2. The BIM has 2 network cards. One of the network cards must be assigned to the same network segment, where the Call@Net Application server is located. The other network card must be assigned to a different network segment, which also contains the CIE-2. The picture below shows an example.

17

MyOffice@Net Server

BIM
192.170.1.1 192.170.1.12

CIE-2

192.168.1.4

192.168.1.20

LAN
Figure 4-1 The BIM as a router to the CIE-2 To reach the CIE-2 from the Call@Net Application server (which is the MyOffice@Net server), take the following steps: 1. On the BIM, in the TCP/IP properties (Network Neighborhood), select the Routing tab and set the 'Enable IP Forwarding' check box.

18

Figure 4-2 Enable IP Forwarding on a BIM 2. Add a new route entry in the routing table of the Call@Net Application server. Example using Figure 4-1 The BIM as a router to the CIE-2: - route add 192.170.1.0 mask 255.255.255.0 192.168.1.20 -p - '192.170.1.0' and the mask defines the network to go to (CIE-2). - '192.168.1.20' is the IP address of the BIM (router). - The flag '-p' is used to make this entry permanent in the routing table on the BIM.

19

4.9.

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 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 4-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

20

(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.

4.9.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 4.9.2. Multi unit ISPBXapply.) 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 OM connection to the MyOffice@Net server; each node needs one SS connection to the MyOffice@Net server. NDNR = DNR when option 40 = ON. NDNR = CLID + DNR when option 40 = OFF.

4.9.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; at least one unit needs an OM connection to the MyOffice@Net server; only one unit of the FIN needs an SS connection to the MyOffice@Net server. NDNR = DNR when option 40 = ON. NDNR = CLID + DNR when option 40 = OFF.

21

5.

Installation

This chapter describes the installation procedures. The procedures provide details on further selections to be made during installation. The default language for MyOffice@Net is English. During installation, you can choose to install all or no additional languages. Notice that not all releases of MyOffice@Net contain additional languages and the different languages might not be available at the same time.

5.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 5.3. Typical installationor 5.4. Custom installation. Preconditions: 1. Check the requirements for the SQL Server PC, section 3.2. SQL (Database) Server Requirements 2. SQL Server 2000 (or SQL Server 7.0) is installed. (How to install this package is beyond the scope of this manual.) Steps: 1. Log on as Administrator to the SQL Server PC. 2. Check if the SQL Server is running. (When the SQL database engine is not running, reboot the SQL Server PC.) - 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 5-1 Connect SQL Server to the databases. shows an example of how to connect the SQL Server to the databases.

22

Figure 5-1 Connect SQL Server to the databases. 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 5-2 SQL Server authentication mode shows an example selecting the authentication type.

23

Figure 5-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;

24

- Click "Network Configuration" and check TCP/IP is one of the enabled protocols. 5. Enable access for the Directory Browser module to the CA database: - Start the registry editor on the SQL Server PC: Start Menu > Run > Regedit. - When it doesn't exist, add a DWORD field called DisallowAdhocAccess to the registry entry:
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\Providers\MSDA SQL Assign the value 0 to the created DWORD.

Close the registry editor. Stop and restart the SQL Server: SQL Server > Properties > Stop / Start.

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

5.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 Server PC. Execute this procedure before you start with 5.3. Typical installationor 5.4. Custom installation. Preconditions: 1. Check the system requirements for the Call@Net Application server PC. Steps: 1. Log on as Administrator to the Call@Net Application server PC. 2. Read the readme.txt file in the MSDE2000 folder. 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. Browse on the CD to MSDE2000 and run the file set_password.bat. This will set the password for user sa to Philips. 7. Continue with the installation of MyOffice@Net software.

25

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

5.3.

Typical installation

When you don't want default settings, skip this procedure and execute the custom installation. This procedure describes the typical installation of MyOffice@Net. All modules are installed on the Call@Net Application server PC. Execute this procedure when: You want to install all modules and use default installation paths AND: You want to install all additional languages, which are available. 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 PC. Steps: 1. Log on as Administrator to the Call@Net Application server PC. 2. 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. 3. Click 'Next' in the 'Welcome' screen. 4. Select Typical in the 'Setup type' screen and click 'Next'. 5. 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' and Philips for 'Password'. Note: Username and Password are as listed above when MSDE was installed before with MyOffice@Net 4.x / 5.x or Management@Net 1.x. When SQL Server is used as database engine, enter the name of the SQL Server PC in the 'Server:' field, sa for 'LoginID:' and sa for 'Password:'

26

Note: Username and Password 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. 6. The 'Start Copying Files' screen offers you a possibility to verify the choice that you made. When all is OK, click the 'Next' button. 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. -

5.4.

Custom installation

When you executed the typical installation, skip this procedure. This procedure describes the custom installation of MyOffice@Net and gives you the opportunity to specify: deviating installation paths, which modules will be installed, if all or none of the additional languages will be installed,

Preconditions: 1. Check the ISPBX requirements. 2. Check the system requirements for the Call@Net Application server PC. Steps: 1. Log on as Administrator to the Call@Net Application server PC. 2. 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. 3. Click 'Next' in the 'Welcome' screen. 4. Select Custom in the Setup type screen and click 'Next'. 5. The 'Select Components' screen appears. - Select the modules that need to be installed. - Select "Additional Languages" when other languages, next to English, must be installed. - Do not select "Additional Languages" but consult 5.6. The language installation program when you only want to install some (and not all) additional languages. - Click 'Next'. 6. The 'Get MSDE or SQL Server info' screen appears. - When MSDE is used as database engine, enter the name of the MyOffice@Net server

27

PC in the 'Server:' field, sa for 'LoginID' and Philips for 'Password'. Note: Username and Password are as listed above when MSDE was installed before with MyOffice@Net 4.x or Management@Net 1.x. When SQL Server is used as database engine, enter the name of the SQL Server PC in the 'Server:' field, sa for 'LoginID:' and sa for 'Password:' (Installation scenario 3)

Note: Username and Password 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 'Choose MyOffice@Net PROGRAM-files destination' screen offers the possibility to customize the folder for the MyOffice@Net program files. In most cases the default selection will be OK. Click 'Next' after the desired folder has been selected. 8. The 'Choose MyOffice@Net DATA-files destination' screen offers the possibility to customize the folder for the MyOffice@Net data files. In most cases the default selection will be OK. Click 'Next' after the desired folder has been selected. 9. The 'Start Copying Files' screen offers you a possibility to verify the choices that you made. When you want to make modifications in the current settings, use the 'Back' button. When all is OK, click the 'Next' button. 10. A 'Select Website' screen can appear. It is used to select an existing website, which resides on this PC. Select a website from the list and click 'Next' after the selection has been made. (Else the default value 'Default Website' is used) Installation and copying of MyOffice@Net files is started now. 11. The last installation screen informs you of a PC reboot. Click 'Finish' 12. Wait until the PC is restarted and the installation has finished. 13. The installation of the MyOffice@Net suite is completed. -

5.5.

Upgrading & re-installation.

Version 4.0 was the first product release of MyOffice@Net. It is not possible to upgrade from a former MyOffice@Net DROP release (version 2.x / 3.x) to this version or a higher version. Starting from version 4.0, MyOffice@Net can be removed, re-installed or upgraded to the latest version. When MSDE (Version MSDE 1) was installed with MyOffice@Net 4.0, it will not be removed during an un-install of MyOffice@Net. When you want to update MSDE version 1 to MSDE2000 (not required!), read the file readme.txt of MSDE2000 on the MyOffice@Net CD-ROM and follow the instructions, listed in this file.

28

Before upgrading a running MyOfice@Net system, the service "World Wide Web Publishing Service" must be stopped to prevent errors in the installation, due to the fact that MyOffice clients keep parts of MyOffice@Net running. To stop this service: Start > Settings > Control Panel > Administrative Tools > Services. Select the World Wide Web Publishing service. Stop this service and start the upgrade procedure. Restart the service after the upgrade has finished. (With a PC reboot, the service will be started automatically.)

For detailed instructions on upgrading to a new version, consult the Field Change Order and/ or the ReadMe on the Product CD-ROM. MyOffice@Net clients start automatically with the latest software after upgrading the Call@Net Server with the latest MyOffice@Net software. When automatically downloading of new software components is disabled, the new MyOffice@Net client components must be distributed and registered on every MyOffice client in another way. SMS can be used to do this. The cabinet file, which holds the MyOffice client components, must be unpacked. All components can be distributed and registered to the MyOffice clients by using SMS. The cabinet file name and location is on the Call@Net server PC: C:\inetpub\wwwroot\atnetframework\framework.cab. Note: How to unpack the cabinet file and how to distribute using SMS are assumed to be common knowledge of IT administrators.

5.6.

The language installation program

To install all additional languages that were shipped on the MyOffice@Net CD-ROM, the MyOffce@Net overall installation procedure can be used. In case you want to install only a selection of additional languages or languages that were not shipped on the original CD-ROM the Language Installer can be used. This program can be found on the MyOffice@Net CD in the folder "Languages - disk1". In order to use the Language Installer: 1. Copy the folder "Languages" (including all sub-folders) to a local disk (to harddisk C: for example). 2. Start the Language Installer: start "setup.exe" in the subfolder "disk1" on your local disk. Use command switch '/?' for more information about running the installer program in different modes.

29

Adding languages All languages that are available to the Language Installer reside under the folder "Languages\Resources". To make new languages available to the Language Installer, execute step 1 as described above. Then add (copy) a folder with resource files for the new language (which has been downloaded from NSONET) to the "Resources" folder. After you copied all necessary languages to the "Resources" folder on your local disk, you can start the installation of additional languages by executing step 2 as described above. Note: Never delete/remove/change one of the files that are part of a language, even if you don't use resources for a specific module of the product.

30

6.

General Configuration

The procedures below describe the configuration of the common / general part of MyOffice@Net suite.

6.1.

Activate the @Net licences.

Preconditions: 1. The USB dongle is connected to a USB port / the dongle is connected to the parallel printer port. 2. The required licence file is present in the folder: C:\Philips\Data Files\Licence-Manager. Steps: 1. Start the Licence Manager: Start-Menu > Programs > MyOffice@Net > Configurators > Licence Manager. Note: Access with default username 'System Administrator' and empty password. 2. Load the licence file: Licence Manager > Menu > Load licence File. 3. Verify all the necessary licences are present. An example of an overview of MyOffice@Net licences is shown in Figure 6-1 Licences for MyOffice@Net 4. Close the Licence Manager.

31

Figure 6-1 Licences for MyOffice@Net

6.2.

Enable access to the ISPBX.

Preconditions: The database engine is running and the database of CM@Net is reachable. Steps: 1. Start CM@Net module: Start-Menu > Programs > MyOffice@Net > Configurators > CM@Net Connection Configurator. A screen as in Figure 6-2 CM@Net Connection Configurator appears.

32

Note: Access with default username 'System Administrator' and empty password.

Figure 6-2 CM@Net Connection Configurator 2. For a single unit PBX: - The ISPBX must be defined as destination: CM@Net menu > Configure > Create > PBX CPU3000 / PBX CCS. - Select the newly created ISPBX and enter data, see the example in Figure 6-3 ISPBX data - Enter a meaningful name for the ISPBX in the field "Destination Name' - Select the appropriate ISPBX type (CPU3000 or CCS) in the 'PBX type' selection listbox. - Select / add the appropriate unit number in the 'Select unit number' selection listbox. - Define the IP address in the field 'host name or IP address'. - Activate the 'Advanced Settings' checkbox. - Accept the default setting for the Operational Maintenance TCP/IP port. - Activate the Switching Services checkbox and accept the default TCP/IP port setting. - Activate the PVE checkbox and accept the default TCP/IP port setting. - Click 'Apply' to save the changes. 3. For a multi unit PBX (FIN): - The ISPBX must be defined as destination: CM@Net menu > Configure > Create >

33

PBX CCS. Select the newly created ISPBX and enter data. Enter a meaningful name for the ISPBX in the field "Destination Name'. Select the CCS type in the 'PBX type' selection listbox. Select / add the appropriate unit numbers in the 'Select unit number' selection listbox. For each unit: define the IP address in the field 'host name or IP address'. For each unit: activate the 'Advanced Settings' checkbox. For at least one unit: accept the default setting for the Operational Maintenance TCP/ IP port. - For each unit: activate the PVE checkbox and accept the default TCP/IP port setting. - For only one unit of the FIN: activate the Switching Services checkbox and accept the default TCP/IP port setting. - Click 'Apply' to save the changes. 4. For each PBX of a DPNSS cluster: - When the PBX is a single unit, excute step 2 for this PBX. - When the PBX is a multi unit (FIN), execute step 3 for this PBX. 5. Close the CM@Net Connection Configurator. -

Figure 6-3 ISPBX data

34

6.3.

Configure @Net Core

Preconditions: OM, PVE and SS connections to the ISPBXs have been created with CM@Net. Steps: 1. Start the @Net Configurator: Start-Menu > Programs > MyOffice@Net > Configurators > @Net Configurator. See for an example Figure 6-4 @Net Configurator. 2. Go to the System Language Setting section and select the default language, which will be offered to all users when using MyOfffice@Net applications. (When additional languages are installed, MyOffice users can select their preferred language with Personal Settings. Personal Settings is a small part of the Central Authentication module, which is accessible for MyOffice users.) 3. Go to the Name resolving settings section and enter the full domain name of the Server, that runs the CA application. When this field is left blank and remote users try to use MyOffice@Net applications, this probably will not work, because they are not on the same network segment as when they are at the office. Defining the full domain name of the Call@Net Server PC (the PC running CA) makes sure the correct domain is accessed for starting MyOffice applications, even when users are working from a remote location. On a (W-NT/2000) client PC the setting can be checked: - Start > Run > nslookup <full domain name> An example of a full domain name: moserver.bcs.cs.philips.com. - The name and the IP address is listed, when the name is known and correct. - An error message is returned when the name is unknown or not correct. (Non existent domain) 4. Confirm the settings and close the @Net Configurator by clicking the 'OK' button. 5. Now, reboot the Call@Net Application server PC. The defined PBXs with CM@Net will be synchronised with the MyOffice system and the general part of the configuration is now ready.

35

Figure 6-4 @Net Configurator

6.4.

Configure Central Authentication for Administrator

The initial configuration steps are described in this procedure. After these steps MyOffice@Net can be used and tested by the user 'sa'. Preconditions: CA database is reachable. Steps: 1. Start MyOffice@Net/Central Authentication and login with user name 'Administrator' and the default empty password.

36

Note: When WinNT accounts are used for logging in, you're automatically logged in by your normal user account when starting MyOffice. Use this URL to be able to login as Administrator to CA: http://<MyOffice@NetServerName>/ca/ca.asp?WCI=Login Select 'Administration' in the 'Choose an application' window. Select 'add user' in the 'MyOffice@Net - Administration' window. Create user 'test'. This user account can be used to test the MyOffice@Net suite. The 'MyOffice@Net - user properties' screen appears. Define a valid NDNR (used in one of the defined ISPBXs) in the 'phone number' field. 6. Scroll to the 'Applications' section and add licences for all applications that will be used by the customer for user 'test'. 7. Save the settings for the new user 'test'. 8. Edit user 'Administrator'. 9. Add a Directory Browser license to user 'Administrator' This enables the Administrator to use the Directory Browser Configurator. 10. Save the settings for 'Administrator'. Note: More configuration steps are listed in chapter 7. Application Configuration.. 2. 3. 4. 5.

37

7.

Application Configuration.

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

7.1.

Dialer configuration

Note: This chapter is only applicable when the SS router connection needs to be shared with SysManager 410 or Management@Net. The Dialer of MyOffice@Net needs a Switching Services connection to each of the defined ISPBXs in the MyOffice@Net system. When SysManager 410 or Management@Net is used as ISPBX management system for the same ISPBXs, then the SS connections are already used by the SysManager or Management@Net server. To make sure the Dialer can use these SS connections as well, some modifications must be executed on the SysManager server PC and on the Call@Net Application server PC. Actually, the Dialer will be configured to use the SS connections of the SysManager server. 1. The Destination names of the target ISPBXs (see Figure 6-3 ISPBX data) must be the same as defined for the target ISPBXs in the CM database for SysManager (or Management@Net). 2. Copy the following files from the Call@Net Application server PC to the SysManager server PC: - Dialer.exe - CallSetupps.dll - DLRConfigTool.exe When default installation paths have been used during MyOffice@Net installation, the files are located in the folder: C:\Program Files\Philips\Dialer-Module on the Call@Net Application server PC. Advice: use/create the same destination folder on the SysManager server PC. 3. Edit the registry of the SysManager server PC: - Start the registry editor: Start Menu > Run > Regedit. - Open or create the registry key: HKEY_LOCAL_MACHINE\Software\Philips\Dialer-Module Create a new string variable for this key with the name: Diagnostic Facility File Location Assign the value C:\Philips\Data files\Diagnostics\Dialer-Module to

the created string variable. - Close the registry editor. 4. Some components must now be registered on the SysManager server PC:

38

Open a DOS command prompt with the active folder C:\Program Files\Philips\Dialer-Module (The folder to which you copied the three files

of step 1) - Execute: regsvr32 callsetupps.dll - Execute: dialer /regserver 5. Add ODBC settings on the SysManager (or Management@Net) server PC: (PC running on W2000; when the PC is running on WinNT, skip this step and continue with step 6.) - Start the ODBC Administrator program: Start Menu > Run > odbcad32. - The "ODBC Data Source Administrator" window appears. Select the TAB "System DSN". - Click the ADD button. The "Create New Data Source" window appears. - Select 'SQL Server' driver and click FINISH. The window "Create a new data source to SQL Server' appears. - Enter PVEDB at the 'Name:' field. Enter the name of the PC that keeps the PVEDB at the 'Server:' field. This is the Call@Net Application Server PC when using MSDE, but it is the SQL Server PC when using SQL Server. - Click Next. Click the button 'Client Configuration...' in the new appeared window. The 'Edit Network Library Configuration' window appears. - Select TCP/IP in the 'Network Libraries' section. Enter the name of the PC that keeps the PVEDB at the 'Computer name:' field. This is the Call@Net Application Server PC when using MSDE, but it is the SQL Server PC when using SQL Server. Accept the default port number 1433 and save the settings by clicking OK. - Select ' With SQL Server authentication using a login ID and password entered by the user' for the question 'How should SQL Server verify the authenticity of the login ID?'. When MSDE is used enter sa for "Login ID" and Philips for "Password". When SQL Server is used enter sa for "Login ID" and sa for "Password". Note: Username and Password may be different when an existing SQL Server is used. Select 'Connect to SQL Server to obtain default settings for the additional configuration options' and click NEXT. - Accept default settings in the following windows by clicking NEXT twice. Click FINISH in the last window and OK in the confirmation window. - Click OK in the "ODBC Data Source Administrator" window to save the new ODBC setting. - Proceed with step 7. 6. Add ODBC settings on the SysManager server PC: (SysManager PC running on WinNT) - Start the ODBC Administrator program: Start Menu > Run > odbcad32. - The "ODBC Data Source Administrator" window appears. Select the TAB "System DSN". -

39

Click the ADD button. The "Create New Data Source" window appears. Select 'SQL Server' driver and click FINISH. The window "ODBC SQL Server Setup' appears. - Enter PVE at the 'Data Source Name:' field. Enter the name of the PC that keeps the PVE database at the 'Server:' field. This is the Call@Net Application Server PC when using MSDE, but it is the SQL Server PC when using SQL Server. - Click on the "Options >>" button. Enter PVE at the 'Database Name' of the Login section. - Click OK to add this entry to the ODBC Administrator. - Click OK in the "ODBC Data Source Administrator" window to save the new ODBC setting. 7. Modify some (DCOM) settings on the SysManager server PC: - Start the DCOM configurator: Start Menu > Run > dcomcnfg. - In the Applications TAB of the DCOM configurator, select Philips Dialer_Callsetup and click the 'Properties' button. - Go to the Identity TAB of the properties window and select radio button The interactive user. - Click OK in the Properties window and also in the DCOM configurator window to save this modification. 8. Modify some (DCOM) settings on the Call@Net Application server PC: - Start the DCOM configurator: Start Menu > Run > dcomcnfg. - In the Applications TAB of the DCOM configurator, select Philips Dialer_Component and click the 'Properties' button. - Go to the Location TAB of the properties window and activate Run application on the following computer. Enter the IP address of the SysManager server PC. Example: \\192.168.1.77 - Go to the Security TAB of the properties window and activate Use custom launch permissions and click on the "Edit..." button. - Select "Interactive" in the "Registry Value Permissions" window and click on the "Add..." button. - Select "Everyone (all users)" and click 'Add'. - Click OK several times to save and activate the modifications. 9. Configure the Dialer on the SysManager server PC: - Start the copied tool: C:\Program Files\Philips\DialerModule\DLRConfigTool.exe

- Select the desired destination (ISPBX) and close this tool. 10. Reboot the Call@Net Application server PC and the SysManager server PC.

7.2.

Directory Browser configuration

To benefit from the full functionality of the Directory Browser application, the Company

40

directory needs to be linked to a database with NDNR related information of the customer. This database is the Phonebook database used by SysManager 410/Management@Net and SuperVisor 60E. The customer is licensed to use this database only in combination with SysManager 410, Management@Net or SuperVisor60E. The database must be of the SQL type because the SQL database engine (or MSDE) is used as control and access interface. The four sections of the Directory Browser configurator can easily be selected by typing the ALT key and the underlined character of the TAB title. (For example: ALT + C for the Company Directory when the English Language is used) The ? button loads the Directory Browser online help for end users. Help text for Administrators is included in the screens itself. 1. Login to CA as Administrator. (Be sure you already executed 6.4. Configure Central Authentication for Administrator) 2. Select the Application 'Directory Browser Configurator'. Note: When the customer doesn't use SysManager 410 / Management@Net and/or SuperVisor 60E with the Phoneware database, the Company directory of the Directory Browser can't be used. Step 3 and 4 below can then be skipped. 3. Select the TAB 'Company Directory Config'. This TAB defines the location and access parameters to the Phoneware database. Figure 7-1 Configure Company directory. shows an example.

41

Figure 7-1 Configure Company directory. 4. For 'Login Name' and 'Password' fill in the appropriate values, used for accessing the database. Click 'Save' to store the settings. 5. Select the TAB 'External Directory Configurator'. This TAB defines the location and access parameters to an external phonebook. Figure 7-2 Configure External directory. shows an example. Click 'Save' to store the settings.

42

Figure 7-2 Configure External directory. 6. Select the TAB 'Default Settings'. This TAB is related to the Company directory and used to define the DEFAULT fields that will be scanned when end-users start the browser functionality. The end-user can use these defaults or modify the fields to personal wishes. - 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 fields as added in the 'Personal Details Fields' section are used to determine what fields from the phonebook will be displayed when 'detailed information' of a Company or Personal directory entry is displayed. - The 'soundex' box is used to enable successful search execution when typing errors occur in the searched text string. - The 'Combine Search Fields' box is used to offer only one edit field in the Company Directory for defining a text string to search for. 7. Click 'Apply' to activate the settings. See Figure 7-3 Configure Default Settings for an

43

example.

Figure 7-3 Configure Default Settings 8. Select the TAB 'Directory Protection'. This TAB is related to the Default settings TAB: - Only the selected fields in the 'Available fields' area are visible in the "Available fields' window of the 'Default settings' TAB. - When none of the checkboxes in the 'Allow users to configure' is set, the 'Default Settings' TAB of all users will only show the checkboxes 'Soundex' and 'Combine Search Fields' - An activated box 'Personal Details' enables users to configure this item in their 'Default Settings' TAB. - An activated box 'Find as result' enables users to configure this item in their 'Default Settings' TAB. - An activated box 'Search on' enables users to configure this item in their 'Default Settings' TAB. 9. Click 'Apply changes' to activate the settings. See Figure 7-4 Configure Directory Protection for an example.

44

Figure 7-4 Configure Directory Protection

7.3.

Key Programming configuration

The MyOffice@Net application Key Programming needs a reserved pool of function key menus. Take notice of the following: This pool must be reserved exclusively for the Key Programming module and NOT overlap the range of menus, which is used for individual phone programming. This pool is the same for every ISPBX in a multiple PBX network (FIN or DPNSS cluster.) The function key menus of this pool must have their softkeys assigned. Consult the CE manual of the ErgoLine sets chapter 2-10, table 2-7 for an overview of all softkeys.

Note: When the system administrator also uses Key Programming Manager (part of the Management@Net suite), this tool can be used to manage the softkey assignment. Function keys of a telephone set, which are programmed with Key Programming, can't be changed on the telephone set anymore. This is due to the usage of OM command CHFKDA with priority 3, meaning no local change is allowed.

45

All function keys of the telephone set, which are programmed locally (or with OM commands), are overwritten by the Key Programming contents. Local settings should be incorporated in Key Programming when using it to program function keys of a telephone set.

Execute the following steps on the Call@Net Application server PC: 1. Start the @Net Configurator: Start-Menu > Programs > MyOffice@Net > Configurators > @Net Configurator. See for an example Figure 6-4 @Net Configurator. 2. Select the Function key menu pool section and define the dedicated function key menu range. This range of menus must be an unused pool in the PBX. (Actually, this range definition will be used on ALL defined PBXs of the MyOffice@Net system.) 3. Confirm the settings and close the @Net Configurator by clicking the 'OK' button. 4. Reboot the PC: any change in the function key menu pool range needs the Call@Net Application server to reboot.

7.4.

Phone Settings configuration

End-users have the possibility to 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. SOPHO Mobility Access (SMA). Voicemail. Present/Absent switching for group calls. Present/Absent switching for Executive/Secretary calls.

See chapter 4.5. Enabling Phone Settings functions how to entitle end-users for all or parts of the Phone Settings functions.

7.4.1.

SMA settings

To be able to use SMA, the System Administrator fills the SMA Settings table with the data listed below. The SMA user enters his / her remote phone number in the Phone Settings application (including trunk access code and area code). To start the SMA function the SMA setting "Working at remote location" in Phone Settings is activated by the user. Two events are executed: the Personal EHWA is assigned to the Desk NDNR (user DNR). A hotline is created between the Access NDNR and the remote extension. When the user is back in the office and deactivates SMA, the original EHWA is assigned to the Desk NDNR.

46

For each user, who is entitled to use the SMA facility, the following data must be entered: Desk NDNR: phone number of the user. Desk EHWA: hardware address of the users phone number. Access NDNR: access number, the user has to dial when working on the remote location and setting up the remote connection. Personal EHWA: hardware address, which will be assigned to the user when the user activates SMA with Phone Settings application. (This is the personal number hardware address of the SMA loop.) Traffic Class: the minimum required traffic class to be able to use this SMA link.

Note: Using NDNRs ensures the system knows where to find DNRs, EHWAs etc. Execute the following steps on the Call@Net Application server PC: 1. Start the @Net Configurator: Start-Menu > Programs > MyOffice@Net > Configurators > @Net Configurator. See for an example Figure 6-4 @Net Configurator. 2. Go to the SMA Settings section: - Press Add to add a new entry; see Figure 7-5 Adding SMA settingsfor an example. - Select an entry of the list and press Modify to change settings of the selected entry; - Select an entry of the list and press Remove to delete the selected entry. 3. Confirm the settings and close the @Net Configurator by clicking the 'OK' button.

47

Figure 7-5 Adding SMA settings

7.5.

Group Display configuration

Execute the following steps on the Call@Net Application server PC: 1. Start the @Net Configurator: Start-Menu > Programs > MyOffice@net > Configurators > @Net Configurator. See for an example Figure 6-4 @Net Configurator. 2. Go to the Group Display Settings section: - Activate the checkbox 'Display Number Only' when only phone numbers must be displayed in the Group Display module. - Go to the Group Settings section and enter the Call Pickup code for group members. This allows group members to pick-up calls for fellow group members (when they are entitled for this facility). This call pick-up code is the same for all ISPBXs in the MyOffice@Net system. (When a call pick-up code is already listed but not accessible ("greyed out"), the MyOffice@Net system has already resolved the pick-up code.)

48

3. Confirm the settings and close the @Net Configurator by clicking the 'OK' button. 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.

7.6.

Voicemail configuration

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

For more information on configuring voicemail, see the MyMail@Net 550 Customer Engineer Manual.

Figure 7-6 Voicemail configuration.

49

8.
8.1.

Authentication Manager (CA)

Introduction

The Central Authentication database is used to control access for all web clients. It contains the user names and passwords and the access rights to the various @Net applications. After login to Central Authentication as Administrator you can Add, Delete or Edit users. Take care that after adding a new user, this user must also be known by the Windows operating system (user account).

8.2.

User Administration

To add a new user: 1. Log in to MyOffice@Net as Administrator. Note: When WinNT accounts are used for logging in, you're automatically logged in by your normal user account when starting MyOffice. Use this URL to be able to login as Administrator to CA: http://<MyOffice@NetServerName>/ca/ca.asp?WCI=Login 2. Select User Administration. 3. Select the Personal Properties tab. 4. Click the Add New button, and enter attributes for the user: - 'Username' is the CA login name for the end-user. - 'Phone number' is the active phone number in the ISPBX of the end-user. The NDNR of the user must be used, to make sure the phone number is unique in the MyOffice@Net system. See Figure 8-1 Define a new user in CA. for an example. 5. Enter optional attributes for the user: - 'Password' and 'Confirm Password' need the same value when used. Advice is to use a password to prevent mis-use of a specific entry by others. - 'WinNT login name' must be defined for each user if you want to avoid that users have to login each time they access the MyOffice@Net applications. - 'E-mail address' is used to supply password information in case a user forgets his or her password. 6. To save your changes, click the Apply button. 7. Select the MyOffice@Net tab, enter the user's name in the search box, and click the Search button.

50

8. 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.) Note: When more users are licensed to use Phone Display in an already operational system, the Call@Net Application server PC needs a reboot to synchronize with the PBX. 9. To save your changes, click the Apply button.

Figure 8-1 Define a new user in CA.

8.3.

Import data to CA database

You can import user data into the Central Authentication database with the Central Authentication Import Tool. User data can be imported from Domain accounts, the Phoneware database or from a predefined file in "csv" format. This procedure is recommended when you want to add lots of users to the CA database at once, for example, when the system is initially started up at the customer site. Preconditions: 1. Access to the domain server of the network must be enabled when domain accounts will be used. 2. An operational PhoneWare database is present and accessible. Steps: 1. Log on as Administrator to the Call@Net Application server PC. 2. Start the import tool: Start > Programs > MyOffice@Net > Configurators > CA Import Tool. 3. Make a choice to import Domain accounts or PhoneWare database entries. 4. Define the path and name of the intermediate file, which will be used to store the Domain accounts or PhoneWare entries. 5. Specify the name of the PC running the database engine that controls the CA database. 6. Click the button 'Export'. A file as defined in step 4 is created.

51

Note: It is also possible to create the intermediate file yourself with Excel or a text editor and use this file as starting point for importing data to the CA database.

Figure 8-2 Start CA Import tool 7. You can edit this intermediate file, but the layout must comply to the following specification: - The first line contains the LABELS of the data fields and are separated by a comma. - Each line is separated by a Carriage Return/Line Feed. - Empty fields contain no characters, even no SPACE character. - Every line contains the same amount of data fields. - The data in the intermediate file has NO (single or double) quotes around it. 8. Use at least the fields: 'USERNAME' and 'DNR' when importing data to CA. When Domain login names will be used, use 'NTACCOUNT' as well.

52

Figure 8-3 Example of a CSV file 9. The file will be imported to the CA database by clicking the 'Import to CA' button. 10. A confirmation screen will appear, see the example below:

53

Figure 8-4 Import tool confirmation. 11. Start CA to verify the users have been added and to modify some settings. 12. Enable the applications for all users at once or specific for each user. 13. Save the modifications and leave CA / user administration

8.4.

CA for end-users

All end-users have limited access to the Central Authentication module. CA for end-users is known as 'Personal Properties'. This application part is also accessible from other MyOffice@Net applications. End-users can change the following items with Personal Properties: Password, Language (when more languages are available), E-mail address, Which MyOffice@Net applications start automatically when starting Windows

54

9.

Customizing MyOffice@Net

This chapter describes how MyOffice@Net can be customised. The applications Directory Browser, Group Display and Phone Display can be customised. Login as Administrator to MyOffice@Net. (See also the note of 8.2. User Administration). A window as in Figure 9-1 Administrator options appears.

Figure 9-1 Administrator options Select option 'Customize portal mode'. A window as in Figure 9-2 Portal Customization windowappears.

55

Figure 9-2 Portal Customization window

9.1.

Changing Colors

The following items can be changed: the colors of the application windows and the font colors; the colors of the buttons and the MyOffice@Net web portal.

The colors are built up of the basic colors RED, GREEN and BLUE. A color can be changed by adding values to these three basic colors. The created color is the mixture of the basic colors and is displayed in the most right column next to the numeric values of RED, GREEN and BLUE. Each value is in the range from 0 ~ 255. Some examples are listed in the table below:

56

RED 255 0 0 0 255 255

GREEN 0 255 0 0 255 235

BLUE 0 0 255 0 255 0

RESULT RED GREEN BLUE BLACK WHITE YELLOW

Table 9-1 RED, GREEN and BLUE coding for creating colors. To change the colors of the application windows and fonts: 1. Change the values of RED, GREEN and BLUE of the 'Portal Frame and Text Colors' area. 2. A preview of the changes can be observed in the 'Color Preview' area. To change the Image colors (buttons): 1. Change the values of RED, GREEN and BLUE of the 'Image Colors' area. 2. Only after you clicked SAVE the results can be observed.

Clicking SAVE stores the changes you made. Clicking DEFAULT restores the MyOffice@Net default color settings. Clicking BACK quits from the Portal Customisation window. (Changes after your last SAVE are discarded !)

9.2.

Web Home Page layout

The Directoy Browser, Group Display and Phone Display applications can be integrated in a company's Web Home Page. It is possible to modify the presentation style. An example is given in Figure 9-3 Integrated MyOffice@Net portals in a WEB HomePage.: Note: Construct the home page in such a way that the part containing the MyOffice@Net portal is NOT dynamically refreshed. (Refreshing the MyOffice@Net portal has unwanted side effects, such as increasing the load on the server and interruptions to end users' displays.) The example in Figure 9-3 Integrated MyOffice@Net portals in a WEB HomePage.

57

shows a correctly constructed page with 4 frames. Do not periodically refresh frame 2 which contains the MyOffice@Net portal.

Figure 9-3 Integrated MyOffice@Net portals in a WEB HomePage. - The portal layout presentation in the Home Page can be in 3 different formats: Horizontal, Vertical or FreeFormat. The desired layout can be selected with the selection box 'Portal Layout' of the Portal Customization screen. See Figure 9-2 Portal Customization window. - To integrate the MyOffice@Net applications to a Web Home Page, add the following line to the HomePage script: <iframe src=myofficeserver/ca/myoffice.asp?uitype=portalframe></iframe> This line enables the portal for the Horizontal and Vertical format. - To enable the portal for FreeFormat as well, add the following lines to the HomePage script: <iframe src=myofficeserver/ca/myoffice.asp?uitype=portalframe></iframe> <iframe id = 2></iframe> (for Directory Browser.) <iframe id = 8></iframe> (for Group Display.) <iframe id = 256></iframe> (for Phone Display.)

58

10.
10.1.

Troubleshooting
General

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

? Automatic logon to MyOffice 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 (de-activate) the 'Anonymous access' checkbox and click 'OK'. 7. Save CA properties by clicking 'OK' Note: Of course all MyOffice users must have permission to logon to the Call@Net Application server PC. 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 5.1. Check SQL Server for the correct setting on the SQL Server PC. For the Call@Net Application server (client of SQL Server)

59

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'.

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 pop-up when Phone Display, Group Display or Directory Browsers' External directory is used for the first time. Activate the checkbox Always trust content from Philips Communications Systems BV and confirm with the Yes button. A possible restart of the PC can be executed later.

60

10.2.

Tracing

? The Philips Helpdesk asked me for trace files for problem solving, but I don't know how to activate it... Some modules of MyOffice@Net generate trace files when the correct registry keys have been set. When generated, a module's trace file can be found in the folder:
C:\Philips\Diagnostic files\<application-name>

Set all trace keys in:

HKEY_LOCAL_MACHINE\Software\Philips\Common\Diag@Net\Trace Level Settings\..

1. For Key Programming the following registry keys must be set to 1: - \Key-Programming_WCKP\ KP. - \PSEngine\ PSE. 2. For Phone Settings the following registry keys must be set to 1: - \Phone-Settings_PS\ PS. - \PSEngine\ PSE. 3. For Phone Display a lot of keys can be set. When all listed keys are set to 1, all information is included in the trace file. Ask the helpdesk, which keys to set. - \CallLogControl\ CallLogControl. - \CallLogObserver\ CallLogObserver. - \EventDistributor MED\ MED COM CALL TRACE, MED COM CALLBACK TRACE, MED HTTP IO TRACE, MED INTERNAL TRACE. \EventDistributor MEE\ MEE COM CALL TRACE, MEE COM CALLBACK TRACE, MEE INTERNAL TRACE. \Monitor\ CallObserver, EventQueue, Events, ExtensionObserver, GITPointer, Monitor. \PhoneDisplay Handler\ Phone Display Handler

4. For Group Display a lot of keys can be set. When all listed keys are set to 1, all information is included in the trace file. Ask the helpdesk, which keys to set. - \CallLogControl\ CallLogControl. - \CallLogObserver\ CallLogObserver. - \EventDistributor MED\ MED COM CALL TRACE, MED COM CALLBACK TRACE, MED HTTP IO TRACE, MED INTERNAL TRACE. \EventDistributor MEE\ MEE COM CALL TRACE, MEE COM CALLBACK TRACE, MEE INTERNAL TRACE. \Monitor\ CallObserver, EventQueue, Events, ExtensionObserver, GITPointer, Monitor.

61

\Group-Display_GroupDisplayServer\ Miscellaneous, Names

10.3.

Directory Browser

? The Company Directory of the Directory Browser doesn't work at all... Check the link to the database with the aid of the Directory Browser Configurator. When no Phoneware database is present (No SM410 or SV60E) the link can't be created and the Company Directory can't be used. The customer has to buy SV60E, SM410 or a Management@Net configuration, which comprises the Phoneware database. ? Missing marbles in the Directory Browser's External Directory... The HTML code of the directory must fulfill the following requirements: No more then 2 HTML tags inside a phone number. "+" and "-" are not counted, but may be inside a phone number. No "A href" (HTML) tag already around it. The number must contain at least the number of digits, defined in the Directory Browser Configurator.

10.4.

Phone Display

? More users are licensed to use Phone Display, but the caller lists don't work for them... The new users are not yet registered for call logging. To do this, the CallLog Control service on the MyOffice server needs to be restarted: Start Services program via Start/Programs/ Administrative Tools/Services. Select CallLogControl. Then press right mouse button, and select Restart to restart the program.

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 the MyOffice@Net suite 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.)

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: CM@Net, CA, PVE and possibly Phonebook. Calculation rules: every SysManager, SuperVisor 60E or Call@Net application server (PVE) "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? PVE 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? PVE 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