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

1

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.

2

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.

3

A Web Server with a Windows 2000 Server operating system. all granted applications can be used without the need of a separate logging on for each MyOffice@Net application during that session. Internet Information Server and the required MyOffice@Net modules installed. Web Clients with a Windows operating system and Internet Explorer. 2. 3. MyOffice@Net Architecture The Concept MyOffice@Net consists of a number of web based telephony applications that are started on a Web Client.a networked (multi unit) PBX. only access to the corporate intranet is necessary. but Free Numbering scheme is not supported. A database server. 4 . Once logged on to the MyOffice@Net suite. 4. network protocol is proprietary IMP) . The end user has access to the applications independent of the location and the time of day.1. (Each DPNSS node can be a stand alone PBX or a FIN. (FIN = Fully Integrated Network. running software package Call@Net 2. The PBX can be one of the following: . the following devices are involved: 1.2.2. Deployment View In MyOffice@Net. This can be MSDE installed on the Web Server or a separate SQL Server.9B or higher. .a stand alone (single unit) PBX.a DPNSS network. The PBX.) Both Open and Closed numbering schemes are supported. 2. 2.

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. 5 . A user of a Web Client browses with the Internet Explorer to the Internet Address (URL) of the Web Server. is as follows: 1.asp 2. A login screen is shown and the user must enter the User name and Password. An example of such a URL is: http://pc22/ca/myoffice.

If so. 6 . which are granted for this user. This portal shows the applications. a MyOffice@Net portal is shown.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.

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

Figure 2-4 The Directory Browser application has started

8

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

9

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

You can find this setting by selecting (in Internet Explorer): Tools > Internet Options > Advanced.Download signed ActiveX controls. Internet Explorer Settings The following setting is recommended for Internet Explorer on client (and server) PC: Disable the setting: Reuse windows for launching shortcuts. Select Local intranet . The setting is located in the Browsing section. .which should at least be set to Medium-low and press the Custom Level .For the Directory Browser the following components are installed: Diabho Configurator: DiaBHOConfig.dll stored in C:\WINNT\System32. Script ActiveX controls marked safe for scripting. You can find these settings by selecting (in Internet Explorer): Tools > Internet Options > Security.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).dll stored in C:\WINNT\System32.Run ActiveX controls and plug-ins.5.. Diabho Interceptor: DiaBHO. 3. The following settings are mandatory for Internet Explorer on a client PC when using Key Programming: Enable the settings: . For Phone Display the following component is installed: Phonedisplay client component: ClientPDhandler. button. 11 .dll stored in C:\WINNT\System32. This Setting must be set to enabled or prompt.. For Group Display the following components are installed: Groupdisplay client component: gdclient.

. options and boundaries must be set. = 100) Table 4-3 Required ISPBX System Boundaries for MyOffice@Net. (*** For Group Display ***) PVE manager id. set to 50 (Default) PVE listen port.10 is recommended) The appropriate licences.4. (*** For Phone Display ***) PVE maximum group monitors... set to YES (ON) (*** For Phone Settings / CF ***) PVE active. 65534).9B or higher. set to 2596 (Default) PVE maximum extension monitors. Number 13 325 365 367 368 370 371 379 380 Description Maximum number of hotlines (0 . Number 64 121 123 Description Activate CFWB on assign. (Call@Net 2. 4. = 100) Maximum number of known IP addresses. set to YES (ON) Table 4-2 Required ISPBX System Options for MyOffice@Net. 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. set to 10 (Default = 0. (0 . Max. see tables below.1. set to 1 (Default) PVE server id. set to 10 (Default = 0. set to YES (ON) PVE short XML. Number 56 Description Call@Net Application Service Table 4-1 Required ISPBX Licences for MyOffice@Net. set to 12345 (Default) Maximum number of profiles. 512). 65534). (*** For Phone Settings / SMA ***) Maximum number of sockets per task (CPU3000 only). Max. (0 . 12 .

The default Client Server profile can be used. Option check: DIMDAT:1. but they can only observe the first 5 groups. Licensed users for Phone Display: 100. Example: boundary 13 = 5 (This is the default setting). which can be set simultaneously (both normal and delayed).) A dedicated Client Server profile is defined to enable access from the Call@Net Application server to the ISPBX. All licensed users are able to use Group Display. a Client Server profile is used on the ISPBX. Operational Maintenance (OM) over IP and Switching Services (SS) over IP. To activate IP connections for OM and SS. Example: boundary 368 = 5 (This is the default setting). Example: boundary 367 = 50 (This is the default setting). 2 Hotlines are used for phones in the elevators. The Call@Net software in the ISPBX operates as IP server and checks the rights through the Client Server Profile.<option-index-number>. Example: 13 . but Phone Display doesn't get information from the ISPBX. Projecting IP Connections The Call@Net Application server needs access to the ISPBX for PVE data exchange. Hotlines are set for example when SMA is activated in Phone Settings. options and boundaries can be done as follows: Licence check: DILICS:<license-number>. The Call@Net Application server is connected to an IPSBX and operates as IP client via a Client Server Profile.<unit-number>. The following steps describe the procedure to define the profile for the Call@Net Application server and the ISPBX device assignment to the profile. Verify if OM and SS devices exist on the V. Licensed users for Group Display: 100. due to boundary 367. (Any Client can access the ISPBX using this profile. user 51 is allowed to use Phone Display. who can use Phone Display. due to boundary 368. Boundary 367 determines the number of users. Boundary 368 determines the number of groups.24 ports of the CPU (or CIE-2). Now only 2 users can make use of the SMA facility.<unit-number>. in case of emergencies and 1 delayed hotline is permanently present on the Director's phone.<unit-number>. 4.<boundary-index-number>. Note: A Client Server Profile is used as a protection mechanism. 50 Users are able to use Phone Display. execute the following steps: 1. Number of groups defined in the PBX: 25. that can be observed. Boundary check: DIMDAT:0.Boundary 13 determines the number of hotlines. but this is not recommended for security reasons.2. To enable this. Verifying ISPBX licences.

If necessary assign devices with ASDEVC.1. 1 means allowed and VDU010 is the logical device name of the OM connection found in step 1. where VDU01 is the used terminal.24 connections.0. which is recommended when the Key Programming application is used. This device is used by MyOffice@Net modules (for example: Key Programming. If needed. Example: .168.CHPROF:1.5 is the IP address of the Call@Net Application server and 1 is the Client Service Profile identity.5 is the IP address of the Call@Net Application server. 2. Check authority classes and protection level of the OM device found or assigned in step 1. Phone Settings) to change settings using OM commands. Note: The recommended OM equipment type is the combination 14 & 15.CHSEAU: CHDEAU: CHSEPR: and CHDEPR: can be used to change authority classes and protection levels of the used terminal.18 is the CPU address. More IP related OM commands: DITCPC: for displaying the IP configuration of CPU3000 and CIE boards.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. 14 .DIIPPR:192. assign a Client Service Profile to the client.CHIPPR:192.1. Check the services on this Client Service Profile. If needed.DIAUPR:VDU01.SYSMSS. .CHPROF:1.5.168. Example: .168. 3. 1 means allowed and SYSMSS is the logical device name of the SS connection found in step 1. Note: Existing V. assign the required services to the Client Service Profile.1.DIPROF:1.168. Example: . With using these types. where 1 is the Client Service Profile id.1. 5. 1 means SS. Example: .1. where 1 is the Client Service Profile identity.1. Examples: . where 11.- DIPORT:11. where 192. where 192.5. . 6.18.1.20&&25.1.VDU010. Check if the client Call@Net Application server is related to a Client Service Profile. OM journalling is skipped. 4. where 1 is the Client Service Profile id. 0 means OM.

03. These PBX conditions are described in the following sections. 4.01. 15 . 4. this can be obtained by using OM command: CHTMSL.07.02 Table 4-4 Required Software packages for sending phone equipment type for Key Programming.01. The TMS service 4 (Automatic Directory Dialling) must be defined with a preferred window (service) size of 5.xy.04.01 3. 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.5.04.3y. Activating the correct TMS Services The TMS services (windows) 80 and up must be disabled.01.- EXPING: for checking if a system component can be reached by the ISPBX on the IP network.01 / 270.01 1. 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.4y.01 2.01 1.03. D330 or D340 when starting Key Programming. should automatically see their own phone type such as ErgoLine D 325. The other functions are only available for end-users when their phone number meets certain PBX conditions.01 / 510.02 3. This can be realized with OM command ASTMSW. 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.xy.07. Enabling Phone Settings functions The Phone Settings functions Call forward when busy / on no answer and voicemail are default available for every end-user. Key Programming compatibility requirements Users. who use Key Programming.3. 4.01 410.50.

who wants to use the SMA facility. - 4. two DTX-I circuits are necessary next to the default (internal) hardware address. ACD etc. must have FCM 58 (Keytone dialing) assigned on their Access DNR. (See also 4.3. the wrong Name information will be displayed. The following (Read only) Facility Classmark is assigned: FCM 21 (Executive) or FCM 22 (Secretary). All type of groups can be distinguished: normal. How to setup SMA (SOPHO Mobility Access or Remote Office) can be found in the "Network and Routing Facility Implementation Manual".6. All users using SMA. 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.5.Personal number.2. 4. Group arrangements The MyOffice@Net application Group Display needs group definitions to be projected in the ISPBX. (This can be checked with OM command DIFACM).5. End-users can only use Don't disturb in Phone Settings when FCM 25 is assigned to their phone number.4. 4. It is possible to create a pool of SMA circuits to serve the SMA users.Personal DNR. Creating and modifying 16 . 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.1. Assigning FCM 57 to SMA users and applying Desksharing adds more functionality to the SMA users.6. The BSPT of the regular DNR (the desk phone) must have a higher priority then the BSPT of the SMA .5. If not. Enabling SMA For each user. Example: use BSPT 95 for the desk phone number and 98 for the SMA . Group arrangements) The following (Read Only) Facility Classmark is assigned: FCM 19 (Group member). 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.

) calls. The BIM has 2 network cards. Example: DINARS:0. all ISPBXs must use the same call pickup code..<unit-nr>. Saving Changes and starting PVE Service Start the PVE service on the ISPBX to enable data exchange with the Call@Net Application server. Group members. where the Call@Net Application server is located.7. CHACDD. One of the network cards must be assigned to the same network segment. which also contains the CIE-2. The PBX reply started means the PVE service is running on the PBX. CRGRPA. 4. ASGRPM. Make a backup of changed projecting by creating a new MIS file with OM command GEBUMI. the BIM should be programmed as a router to the CIE-2. In case of a FIN or a DPNSS cluster. The picture below shows an example. . The other network card must be assigned to a different network segment. 17 . 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. 4.34. Details concerning these OM commands can be found in the Call@Net OM commands (MML) manual. Using a BIM as a Router For CCS systems. Verification of the running service: DISRVC:0. who are enabled to pick up group (or exec. Consult the Call@Net Voice Facilities manual for details concerning group arrangements./secr. Users of Group Display must be supervisor or member of the group they wish to monitor. The code (prefix) for individual call pickup can be found using OM command DINARS.8. DEGRPM. must have FCM 20 assigned. Related OM commands: DIGRPA. (The supporting module @Net-Core is the interface to the PVE service on the ISPBX.) Start-up is realized with OM command STSRVC:0.groups is beyond the scope of this manual.<unit-nr>.

168.MyOffice@Net Server BIM 192.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). On the BIM.1. 18 . select the Routing tab and set the 'Enable IP Forwarding' check box.1.1.1 192.1. in the TCP/IP properties (Network Neighborhood). take the following steps: 1.170.12 CIE-2 192.170.4 192.168.

0' and the mask defines the network to go to (CIE-2).170.'192. .'192. Add a new route entry in the routing table of the Call@Net Application server. 19 .1.20' is the IP address of the BIM (router).0 192.255.0 mask 255.Figure 4-2 Enable IP Forwarding on a BIM 2.168. .1.170.route add 192.20 -p .The flag '-p' is used to make this entry permanent in the routing table on the BIM.255.1. Example using Figure 4-1 The BIM as a router to the CIE-2: .1.168.

The 'N' (Network part) of the NDNR is equal to the CLID. When phone numbers (DNRs) in a DPNSS network are unique for every PBX of this DPNSS cluster. For single unit PBXs and FINs (FIN = Fully Intergrated Network) the phone numbers (DNRs) are unique by default. This option must be set the same for each node in a DPNSS network. MyOffice@Net uses NDNR = CLID + DNR. The CLID of PBX1 is 11 and the CLID of PBX2 is 12. Number 40 Description Closed number scheme in network. When option 40 is set. The table below lists the option. the numbering scheme is called OPEN. (Default = OFF) Table 4-5 ISPBX System Options for Open/Closed numbering scheme. (The first digit(s) of the phone numbers differ for every PBX of the DPNSS cluster. For this type of numbering scheme the NDNR = CLID + DNR. The NDNR must be unique within the served (PBX) network. With option 40 = OFF (default). the PBX uses a closed numbering scheme and the NDNR = DNR. When option 40 is not set (this is the default setting). Example: the DNR range of PBX1 and PBX2 is both 3000 ~ 4999.) For this type of numbering scheme the NDNR = DNR. it is possible that the phone numbers in the network are not unique. the PBX uses an open numbering scheme and the NDNR = CLID + DNR. To solve the problem of not unique phone numbers in a MyOffice@Net system serving multiple PBXs (a network). Open numbering scheme. the term NDNR (Network DNR) is used. Closed numbering scheme. When phone numbers (DNRs) in a DPNSS network are NOT unique for every PBX of this DPNSS cluster. even for single unit PBXs or multi unit PBXs 20 . Note: MyOffice@Net is always using the NDNRs of all PBXs.4. The NDNR range of PBX1 is now 113000 ~ 114999 and the NDNR range of PBX2 is 123000 ~ 124999.9. For every PBX of this DPNSS cluster the CLID (Cluster Identity) is used to identify each DPNSS node. Multiple PBXs and MyOffice@Net The phone numbers used in a MyOffice@Net system need to be unique. which is involved in the type of numbering scheme. the numbering scheme is called CLOSED. The DNR (Directory number = phone number) is used to identify the internal phone number. For a DPNSS network.

only one unit of the FIN needs an SS connection to the MyOffice@Net server. at least one unit needs an OM connection to the MyOffice@Net server. NDNR = CLID + DNR when option 40 = OFF. then NDNR = DNR. (For a FIN the rules of 4. each node needs one SS connection to the MyOffice@Net server.) each node needs an IP connection to the IP network. 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). DPNSS clustered ISPBX When the PBX is a DPNSS node. 4.1. Multi unit ISPBXapply.9.(FIN).9. 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 node needs its own PVE connection to the MyOffice@Net server. each node needs its own OM connection to the MyOffice@Net server. NDNR = DNR when option 40 = ON.9. 4. NDNR = DNR when option 40 = ON. each unit needs its own PVE connection to the MyOffice@Net server.2. the following points must be taken into account: each node can be a single unit PBX or a multi unit PBX (FIN). 21 . NDNR = CLID + DNR when option 40 = OFF.2.

. Check SQL Server When you want to use MSDE as database engine.) Steps: 1. The default language for MyOffice@Net is English. . section 3. Check the requirements for the SQL Server PC. During installation. SQL (Database) Server Requirements 2. which is necessary for the MyOffice@Net installation.2. Typical installationor 5. Preconditions: 1.) . This procedure describes how to check that the SQL Server is running and accessible.Check if the SQL databases are connected (SQL Server icon is green) and if not.1. you can choose to install all or no additional languages. shows an example of how to connect the SQL Server to the databases. Notice that not all releases of MyOffice@Net contain additional languages and the different languages might not be available at the same time.Expand the SQL Server database tree. Custom installation. Execute this procedure before you start with 5. right click on it and select 'connect'. (When the SQL database engine is not running.5.3.4. Log on as Administrator to the SQL Server PC. reboot the SQL Server PC. 22 . 5.0) is installed. SQL Server 2000 (or SQL Server 7. Installation This chapter describes the installation procedures.Open the SQL Server Enterprise Manager: Start Menu > Programs > Microsoft SQL Server > Enterprise Manager. connect it: select the SQL Server. Check if the SQL Server is running. 2. skip this procedure. (How to install this package is beyond the scope of this manual. Figure 5-1 Connect SQL Server to the databases. The procedures provide details on further selections to be made during installation.

. Figure 5-2 SQL Server authentication mode shows an example selecting the authentication type.Select the SQL Server. 3.Select SQL Server properties by a right mouse click on the selected SQL Server. 23 .Select TAB "Security" and select SQL Server and Windows as authentication mode. Check the correct authentication mode for logging in on the SQL Server: . . which is used for MyOffice@Net.Figure 5-1 Connect SQL Server to the databases.

Select the SQL Server. 24 . . which is used for MyOffice@Net.Figure 5-2 SQL Server authentication mode 4.Select SQL Server properties by a right mouse click on the selected SQL Server. Check the correct communication protocol is selected for the SQL Server: .

Enable access for the Directory Browser module to the CA database: .4. Continue with the installation of MyOffice@Net software. - Close the registry editor. 7. The installation will be executed and the PC needs a reboot tot start MSDE. Steps: 1. .bat. . Note: It is advised to secure the MSDE/SQL database access by using a (non empty) password for all users.Click "Network Configuration" and check TCP/IP is one of the enabled protocols. Check the system requirements for the Call@Net Application server PC.3. 3.Browse on the CD to MSDE2000 and run the file install. 5. MSDE installation When you want to use SQL Server as database engine OR you are using an already installed and running version of MSDE. Browse on the CD to MSDE2000 and run the file set_password.Select Add/Remove Programs > Add New Programs. See Microsoft knowledge base article Q313418 5. Follow the instructions of the MSDE installation program. Read the readme.2. Typical installationor 5.txt file in the MSDE2000 folder. Stop and restart the SQL Server: SQL Server > Properties > Stop / Start.exe! 4. 25 . 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. Log on as Administrator to the Call@Net Application server PC.Select Start > Settings > Control Panel. DO NOT RUN setup. This will set the password for user sa to Philips. Execute this procedure before you start with 5.Start the registry editor on the SQL Server PC: Start Menu > Run > Regedit. Start the Installation of MSDE from the CD-ROM: . Preconditions: 1.When it doesn't exist. This procedure describes how to install MSDE on the Call@Net Server PC. 6. skip this procedure. 5..bat. 2. Custom installation. .

Note: Username and Password are as listed above when MSDE was installed before with MyOffice@Net 4. sa for 'LoginID:' and sa for 'Password:' 26 . The 'Get MSDE or SQL Server info' screen appears. Default path for executable files: C:\Program Files\Philips\ Default path for data files: C:\Philips\Data Files\ Preconditions: 1. Start the Installation of MyOffice@Net from the CD-ROM: . This procedure describes the typical installation of MyOffice@Net. Typical installation When you don't want default settings. . 2.When MSDE is used as database engine.Select Start > Settings > Control Panel. Select Typical in the 'Setup type' screen and click 'Next'. Steps: 1. 4.Browse on the CD to MyOffice@Net\Disk1 and start setup. Check the system requirements for the Call@Net Application server PC.x or Management@Net 1. which are available. Check the ISPBX requirements. Execute this procedure when: You want to install all modules and use default installation paths AND: You want to install all additional languages.exe. enter the name of the SQL Server PC in the 'Server:' field.Note: It is advised to secure the MSDE/SQL database access by using a (non empty) password for all users.x.x / 5. 2. the default name 'local' can be used in the 'Server:' field. skip this procedure and execute the custom installation. When SQL Server is used as database engine. Log on as Administrator to the Call@Net Application server PC. 3. .Select Add/Remove Programs > Add New Programs. Click 'Next' in the 'Welcome' screen.3. All modules are installed on the Call@Net Application server PC. enter sa for 'LoginID' and Philips for 'Password'. See Microsoft knowledge base article Q313418 5. . 5.

6.4. The installation will be executed and asks for a reboot confirmation at the end. Click 'Next' in the 'Welcome' screen.Select Add/Remove Programs > Add New Programs. The 'Start Copying Files' screen offers you a possibility to verify the choice that you made. . . which modules will be installed. Log on as Administrator to the Call@Net Application server PC.Select Start > Settings > Control Panel. .exe. 2. 7. . next to English.Select "Additional Languages" when other languages. This procedure describes the custom installation of MyOffice@Net and gives you the opportunity to specify: deviating installation paths. The 'Get MSDE or SQL Server info' screen appears. Wait until the PC is restarted and the installation has finished. - 5. The language installation program when you only want to install some (and not all) additional languages.Note: Username and Password may be different when an existing SQL Server is used. Preconditions: 1. must be installed. The installation procedure tries to connect to the database with the given input. Custom installation When you executed the typical installation. check if the settings is correct. . skip this procedure. When all is OK. 3. Start the Installation of MyOffice@Net from the CD-ROM: . 4.Click 'Next'. enter the name of the MyOffice@Net server 27 . 5.When MSDE is used as database engine. if all or none of the additional languages will be installed.Select the modules that need to be installed. 8. Check the system requirements for the Call@Net Application server PC. Check the ISPBX requirements. . Click OK. When this fails. The 'Select Components' screen appears. 6. Steps: 1.6. 2. Select Custom in the Setup type screen and click 'Next'. Click 'Next' after the required data is entered.Do not select "Additional Languages" but consult 5. . click the 'Next' button.Browse on the CD to MyOffice@Net\Disk1 and start setup.

The 'Choose MyOffice@Net PROGRAM-files destination' screen offers the possibility to customize the folder for the MyOffice@Net program files. 28 . check if the settings is correct. The 'Choose MyOffice@Net DATA-files destination' screen offers the possibility to customize the folder for the MyOffice@Net data files. 10. Upgrading & re-installation. It is not possible to upgrade from a former MyOffice@Net DROP release (version 2. Note: Username and Password are as listed above when MSDE was installed before with MyOffice@Net 4. Starting from version 4. sa for 'LoginID:' and sa for 'Password:' (Installation scenario 3) Note: Username and Password may be different when an existing SQL Server is used. use the 'Back' button. In most cases the default selection will be OK. (Else the default value 'Default Website' is used) Installation and copying of MyOffice@Net files is started now.5. enter the name of the SQL Server PC in the 'Server:' field. Click 'Next' after the desired folder has been selected. 8. 13. read the file readme. it will not be removed during an un-install of MyOffice@Net.txt of MSDE2000 on the MyOffice@Net CD-ROM and follow the instructions. Click 'Next' after the required data is entered. 11. Wait until the PC is restarted and the installation has finished. When MSDE (Version MSDE 1) was installed with MyOffice@Net 4.x) to this version or a higher version. In most cases the default selection will be OK. which resides on this PC.PC in the 'Server:' field. MyOffice@Net can be removed. When SQL Server is used as database engine. When this fails.x. The 'Start Copying Files' screen offers you a possibility to verify the choices that you made. The installation procedure tries to connect to the database with the given input. It is used to select an existing website. 7.x or Management@Net 1. Version 4.0 was the first product release of MyOffice@Net. Click 'Finish' 12. re-installed or upgraded to the latest version. When you want to update MSDE version 1 to MSDE2000 (not required!). Select a website from the list and click 'Next' after the selection has been made. listed in this file. - 5. The last installation screen informs you of a PC reboot. When you want to make modifications in the current settings.0. The installation of the MyOffice@Net suite is completed.0. Click 'Next' after the desired folder has been selected. 9. sa for 'LoginID' and Philips for 'Password'. When all is OK.x / 3. click the 'Next' button. A 'Select Website' screen can appear.

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. Start the Language Installer: start "setup.exe" in the subfolder "disk1" on your local disk. 5. 29 .6. Select the World Wide Web Publishing service. Copy the folder "Languages" (including all sub-folders) to a local disk (to harddisk C: for example). due to the fact that MyOffice clients keep parts of MyOffice@Net running. Note: How to unpack the cabinet file and how to distribute using SMS are assumed to be common knowledge of IT administrators. This program can be found on the MyOffice@Net CD in the folder "Languages . In order to use the Language Installer: 1. the new MyOffice@Net client components must be distributed and registered on every MyOffice client in another way. Use command switch '/?' for more information about running the installer program in different modes. the service "World Wide Web Publishing Service" must be stopped to prevent errors in the installation. consult the Field Change Order and/ or the ReadMe on the Product CD-ROM. SMS can be used to do this. MyOffice@Net clients start automatically with the latest software after upgrading the Call@Net Server with the latest MyOffice@Net software. the MyOffce@Net overall installation procedure can be used. The cabinet file. When automatically downloading of new software components is disabled. The language installation program To install all additional languages that were shipped on the MyOffice@Net CD-ROM. 2.cab. (With a PC reboot.Before upgrading a running MyOfice@Net system. the service will be started automatically. which holds the MyOffice client components. To stop this service: Start > Settings > Control Panel > Administrative Tools > Services. The cabinet file name and location is on the Call@Net server PC: C:\inetpub\wwwroot\atnetframework\framework. Stop this service and start the upgrade procedure. All components can be distributed and registered to the MyOffice clients by using SMS.) For detailed instructions on upgrading to a new version. Restart the service after the upgrade has finished.disk1". must be unpacked.

30 . you can start the installation of additional languages by executing step 2 as described above. 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.Adding languages All languages that are available to the Language Installer reside under the folder "Languages\Resources". Note: Never delete/remove/change one of the files that are part of a language. After you copied all necessary languages to the "Resources" folder on your local disk. even if you don't use resources for a specific module of the product.

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

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

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

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

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

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

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

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). .Start the registry editor: Start Menu > Run > Regedit. The Dialer of MyOffice@Net needs a Switching Services connection to each of the defined ISPBXs in the MyOffice@Net system. the files are located in the folder: C:\Program Files\Philips\Dialer-Module on the Call@Net Application server PC. the Dialer will be configured to use the SS connections of the SysManager server.1. This chapter describes the configuration of the MyOffice@Net application modules.dll .Close the registry editor. Application Configuration.exe . 2. Dialer configuration Note: This chapter is only applicable when the SS router connection needs to be shared with SysManager 410 or Management@Net.CallSetupps. 7. Some components must now be registered on the SysManager server PC: 38 . After this chapter.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. Copy the following files from the Call@Net Application server PC to the SysManager server PC: . To make sure the Dialer can use these SS connections as well. Actually. some modifications must be executed on the SysManager server PC and on the Call@Net Application server PC. 1. 3. Edit the registry of the SysManager server PC: . 4.exe When default installation paths have been used during MyOffice@Net installation. . the associated section can be skipped. When SysManager 410 or Management@Net is used as ISPBX management system for the same ISPBXs.7.Dialer.DLRConfigTool. then the SS connections are already used by the SysManager or Management@Net server. the applications are ready to be started on the MyOffice@Net clients. Advice: use/create the same destination folder on the SysManager server PC. When a certain module is not installed or not used.

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

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

(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. This database is the Phonebook database used by SysManager 410/Management@Net and SuperVisor 60E. Management@Net or SuperVisor60E. This TAB defines the location and access parameters to the Phoneware database. Login to CA as Administrator. Step 3 and 4 below can then be skipped. (Be sure you already executed 6. shows an example. the Company directory of the Directory Browser can't be used.directory needs to be linked to a database with NDNR related information of the customer. Note: When the customer doesn't use SysManager 410 / Management@Net and/or SuperVisor 60E with the Phoneware database. Select the TAB 'Company Directory Config'.4. Select the Application 'Directory Browser Configurator'. The database must be of the SQL type because the SQL database engine (or MSDE) is used as control and access interface. 1. 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. Help text for Administrators is included in the screens itself. The customer is licensed to use this database only in combination with SysManager 410. Configure Central Authentication for Administrator) 2. Figure 7-1 Configure Company directory. 41 . 3.

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

. 7.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.Figure 7-2 Configure External directory. 6. The end-user can use these defaults or modify the fields to personal wishes. . . 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. Select the TAB 'Default Settings'.The fields as added in the 'Find as result' section are returned to the end-user his/her browser.The 'soundex' box is used to enable successful search execution when typing errors occur in the searched text string. See Figure 7-3 Configure Default Settings for an 43 . Click 'Apply' to activate the settings. .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 fields as added in the 'Search on' section are scanned by the browser to find the text string the end-user invoked.

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

Figure 7-4 Configure Directory Protection 7. Key Programming configuration The MyOffice@Net application Key Programming needs a reserved pool of function key menus. This pool is the same for every ISPBX in a multiple PBX network (FIN or DPNSS cluster. - Note: When the system administrator also uses Key Programming Manager (part of the Management@Net suite). which is used for individual phone programming. can't be changed on the telephone set anymore.) The function key menus of this pool must have their softkeys assigned. Function keys of a telephone set.3. 45 . Take notice of the following: This pool must be reserved exclusively for the Key Programming module and NOT overlap the range of menus. this tool can be used to manage the softkey assignment. Consult the CE manual of the ErgoLine sets chapter 2-10. This is due to the usage of OM command CHFKDA with priority 3. meaning no local change is allowed. which are programmed with Key Programming. table 2-7 for an overview of all softkeys.

Start the @Net Configurator: Start-Menu > Programs > MyOffice@Net > Configurators > @Net Configurator. Present/Absent switching for Executive/Secretary calls. Select the Function key menu pool section and define the dedicated function key menu range. 46 . the original EHWA is assigned to the Desk NDNR. this range definition will be used on ALL defined PBXs of the MyOffice@Net system. which are programmed locally (or with OM commands). Execute the following steps on the Call@Net Application server PC: 1.1.- All function keys of the telephone set. A hotline is created between the Access NDNR and the remote extension.4. 7.5.4. See chapter 4. Don't disturb. the System Administrator fills the SMA Settings table with the data listed below. (Actually. To start the SMA function the SMA setting "Working at remote location" in Phone Settings is activated by the user. Confirm the settings and close the @Net Configurator by clicking the 'OK' button. Two events are executed: the Personal EHWA is assigned to the Desk NDNR (user DNR). Local settings should be incorporated in Key Programming when using it to program function keys of a telephone set. Present/Absent switching for group calls. Call forward on no answer for internal and/or external calls. Enabling Phone Settings functions how to entitle end-users for all or parts of the Phone Settings functions.) 3. SOPHO Mobility Access (SMA). The SMA user enters his / her remote phone number in the Phone Settings application (including trunk access code and area code). SMA settings To be able to use SMA. are overwritten by the Key Programming contents. Follow me. When the user is back in the office and deactivates SMA. 7. This range of menus must be an unused pool in the PBX. Voicemail. 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. 2. Reboot the PC: any change in the function key menu pool range needs the Call@Net Application server to reboot. See for an example Figure 6-4 @Net Configurator.

the user has to dial when working on the remote location and setting up the remote connection. Desk EHWA: hardware address of the users phone number. who is entitled to use the SMA facility. EHWAs etc. see Figure 7-5 Adding SMA settingsfor an example. the following data must be entered: Desk NDNR: phone number of the user.Press Add to add a new entry.Select an entry of the list and press Modify to change settings of the selected entry. 2. Confirm the settings and close the @Net Configurator by clicking the 'OK' button. Start the @Net Configurator: Start-Menu > Programs > MyOffice@Net > Configurators > @Net Configurator. Go to the SMA Settings section: . Personal EHWA: hardware address. See for an example Figure 6-4 @Net Configurator.For each user. which will be assigned to the user when the user activates SMA with Phone Settings application. Access NDNR: access number. 3. (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. Execute the following steps on the Call@Net Application server PC: 1.Select an entry of the list and press Remove to delete the selected entry. 47 . - Note: Using NDNRs ensures the system knows where to find DNRs. . .

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

7. Note: When changes are made in a group (add/delete group and/or group members) in one of the ISPBXs. Select Voicemail & Settings In Application Properties.3. There are 2 kinds of Group Display.6. Voicemail configuration If MyMail@Net is installed on your network. In User Administration. Confirm the settings and close the @Net Configurator by clicking the 'OK' button. 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. Figure 7-6 Voicemail configuration. Log in to MyOffice@Net as Administrator. 3. 2. you can add a Voicemail button to the MyOffice@Net portal: 1. 4. the Group Display application needs to be restarted to synchronize with the changes. For more information on configuring voicemail. see the MyMail@Net 550 Customer Engineer Manual. Select Server Administration. enter the location of the MyMail@Net server's login script. 49 . All Groups lets the user choose from all available groups in the ISPBX.

See Figure 8-1 Define a new user in CA. 5.2. 3. .1. for an example. and click the Search button. Click the Add New button.'Password' and 'Confirm Password' need the same value when used. It contains the user names and passwords and the access rights to the various @Net applications. 7. User Administration To add a new user: 1.'E-mail address' is used to supply password information in case a user forgets his or her password. to make sure the phone number is unique in the MyOffice@Net system. Delete or Edit users. Advice is to use a password to prevent mis-use of a specific entry by others. Select the MyOffice@Net tab. . After login to Central Authentication as Administrator you can Add. 8.'Phone number' is the active phone number in the ISPBX of the end-user. . this user must also be known by the Windows operating system (user account).'Username' is the CA login name for the end-user. enter the user's name in the search box.'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. 4. Authentication Manager (CA) Introduction The Central Authentication database is used to control access for all web clients. Take care that after adding a new user.8. Enter optional attributes for the user: . you're automatically logged in by your normal user account when starting MyOffice. click the Apply button. 8. Note: When WinNT accounts are used for logging in. and enter attributes for the user: .asp?WCI=Login 2. 50 . Select User Administration. 6. Select the Personal Properties tab. The NDNR of the user must be used. To save your changes. Use this URL to be able to login as Administrator to CA: http://<MyOffice@NetServerName>/ca/ca. Log in to MyOffice@Net as Administrator.

6.8. 8. 4. for example. Steps: 1. Define the path and name of the intermediate file. Make a choice to import Domain accounts or PhoneWare database entries. Access to the domain server of the network must be enabled when domain accounts will be used. 2. Import data to CA database You can import user data into the Central Authentication database with the Central Authentication Import Tool. Start the import tool: Start > Programs > MyOffice@Net > Configurators > CA Import Tool. 3. which will be used to store the Domain accounts or PhoneWare entries. 2. click the Apply button. 5. when the system is initially started up at the customer site. Figure 8-1 Define a new user in CA. Preconditions: 1. the Call@Net Application server PC needs a reboot to synchronize with the PBX. 51 . User data can be imported from Domain accounts. You will be prompted if necessary. the Phoneware database or from a predefined file in "csv" format.) Note: When more users are licensed to use Phone Display in an already operational system. To save your changes. Click the button 'Export'. An operational PhoneWare database is present and accessible. Select check boxes for the applications that you want to assign to the user. (Some applications require a login name and password. This procedure is recommended when you want to add lots of users to the CA database at once. 9. A file as defined in step 4 is created. Specify the name of the PC running the database engine that controls the CA database.3. Log on as Administrator to the Call@Net Application server PC.

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

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

CA for end-users is known as 'Personal Properties'. 13. Start CA to verify the users have been added and to modify some settings. 12. CA for end-users All end-users have limited access to the Central Authentication module. This application part is also accessible from other MyOffice@Net applications. E-mail address. Enable the applications for all users at once or specific for each user. Save the modifications and leave CA / user administration 8. Language (when more languages are available). End-users can change the following items with Personal Properties: Password. 11. Which MyOffice@Net applications start automatically when starting Windows 54 .4.Figure 8-4 Import tool confirmation.

2. Customizing MyOffice@Net This chapter describes how MyOffice@Net can be customised. The applications Directory Browser. Group Display and Phone Display can be customised. (See also the note of 8. Login as Administrator to MyOffice@Net. Figure 9-1 Administrator options Select option 'Customize portal mode'. User Administration). A window as in Figure 9-2 Portal Customization windowappears. 55 .9. A window as in Figure 9-1 Administrator options appears.

The colors are built up of the basic colors RED. GREEN and BLUE.1.Figure 9-2 Portal Customization window 9. GREEN and BLUE. Some examples are listed in the table below: 56 . Each value is in the range from 0 ~ 255. the colors of the buttons and the MyOffice@Net web portal. Changing Colors The following items can be changed: the colors of the application windows and the font 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. A color can be changed by adding values to these three basic colors.

- Clicking SAVE stores the changes you made. To change the Image colors (buttons): 1. 57 . Web Home Page layout The Directoy Browser. Group Display and Phone Display applications can be integrated in a company's Web Home Page. An example is given in Figure 9-3 Integrated MyOffice@Net portals in a WEB HomePage.2. GREEN and BLUE of the 'Image Colors' area.: Note: Construct the home page in such a way that the part containing the MyOffice@Net portal is NOT dynamically refreshed.) The example in Figure 9-3 Integrated MyOffice@Net portals in a WEB HomePage. To change the colors of the application windows and fonts: 1. (Refreshing the MyOffice@Net portal has unwanted side effects. 2. GREEN and BLUE of the 'Portal Frame and Text Colors' area. Clicking DEFAULT restores the MyOffice@Net default color settings. Change the values of RED. (Changes after your last SAVE are discarded !) 9. such as increasing the load on the server and interruptions to end users' displays. GREEN and BLUE coding for creating colors.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. A preview of the changes can be observed in the 'Color Preview' area. Clicking BACK quits from the Portal Customisation window. Only after you clicked SAVE the results can be observed. Change the values of RED. 2. It is possible to modify the presentation style.

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

7. 4. the SMA data. Consult 5. 10.1.. At least. It is recommended to have the SQL Server and the Call@Net Application server in the same Windows domain. Troubleshooting General ? Which information is stored in which database? CA database contains the CA account information. Select: Start > Programs > Administrative Tools > Internet Service Manager.. Click 'Edit' in the section: 'Anonymous access and authentication control'.. Use the right mouse button and select 'properties'. Save CA properties by clicking 'OK' Note: Of course all MyOffice users must have permission to logon to the Call@Net Application server PC. PVE database contains the 'mirrored' PBX data. Disable (de-activate) the 'Anonymous access' checkbox and click 'OK'. the personal directories and the Directory Browser configuration data. Check SQL Server for the correct setting on the SQL Server PC. ? The Call@Net Application server is reacting very slowly. "Phonebook" database is the source for Directory Browser's Company Directory. The access rights to CA may be restricted.. 2.1. For the Call@Net Application server (client of SQL Server) 59 . 6.10. 5. the Function Key Menu's and Phone Display's List of Calls data. ? Automatic logon to MyOffice applications using the users' WinNT names doesn't work. 3. Open properties for: Internet Information Server###BOT_TEXT###lt;this PC name>\Default web server\CA. Select the TAB 'Directory Security'. execute the following steps on the Call@Net Application server: 1. This can be checked on the PC running the Domain Controller. To check and change this. PBX database (belongs to the CM@Net module) contains the PBX connection information. make sure the connection between SQL Server and Call@Net application server uses the TCP/IP protocol.

4. appears. Group Display or Directory Browsers' External directory is used for the first time. ? A security warning appears when a MyOffice@Net application is started. A window as in Figure 10-1 Setting the default network library protocol for an SQL Server's client. 2.. A possible restart of the PC can be executed later.. Set the default network library protocol to TCP/IP.. Confirm the setting by clicking the buttons 'Apply' and 'OK'. Enter C:\Winnt\system32\cliconfig.execute the following steps: 1. Such a warning can pop-up when Phone Display.. Open the configurator by Start > run. Figure 10-1 Setting the default network library protocol for an SQL Server's client. Activate the checkbox Always trust content from Philips Communications Systems BV and confirm with the Yes button.exe (clicfg. 3.exe). 60 .

\Phone-Settings_PS\ PS.\CallLogObserver\ CallLogObserver. MED HTTP IO TRACE. . When all listed keys are set to 1. all information is included in the trace file. . but I don't know how to activate it. 1. 2.\PSEngine\ PSE. ExtensionObserver. MED COM CALLBACK TRACE.. Some modules of MyOffice@Net generate trace files when the correct registry keys have been set. all information is included in the trace file. 3.2. For Phone Display a lot of keys can be set. \EventDistributor MEE\ MEE COM CALL TRACE. MED INTERNAL TRACE.. Monitor.\CallLogObserver\ CallLogObserver. . For Group Display a lot of keys can be set. 61 . Events. When generated.10. \Monitor\ CallObserver. . MEE COM CALLBACK TRACE. . MED INTERNAL TRACE. For Key Programming the following registry keys must be set to 1: . a module's trace file can be found in the folder: C:\Philips\Diagnostic files###BOT_TEXT###lt;application-name> Set all trace keys in: HKEY_LOCAL_MACHINE\Software\Philips\Common\Diag@Net\Trace Level Settings\. When all listed keys are set to 1. Events.\EventDistributor MED\ MED COM CALL TRACE. MED HTTP IO TRACE. which keys to set. Ask the helpdesk. MED COM CALLBACK TRACE.\CallLogControl\ CallLogControl.\EventDistributor MED\ MED COM CALL TRACE. Monitor. MEE INTERNAL TRACE. EventQueue.. \EventDistributor MEE\ MEE COM CALL TRACE. which keys to set. GITPointer. MEE INTERNAL TRACE. . Tracing ? The Philips Helpdesk asked me for trace files for problem solving. \Monitor\ CallObserver. EventQueue. \PhoneDisplay Handler\ Phone Display Handler 4. MEE COM CALLBACK TRACE. .\Key-Programming_WCKP\ KP. ExtensionObserver. Ask the helpdesk. GITPointer. .\PSEngine\ PSE. For Phone Settings the following registry keys must be set to 1: .\CallLogControl\ CallLogControl.

that for the MyOffice@Net suite the following rule applies for Name search ("look-up"): 1. SM410 or a Management@Net configuration. defined in the Directory Browser Configurator. 10. ? Missing marbles in the Directory Browser's External Directory. "+" and "-" are not counted. Restart the Group Display application to synchronize with the ISPBX PVE service.4. Check the link to the database with the aid of the Directory Browser Configurator..3. which comprises the Phoneware database. The number must contain at least the number of digits.- \Group-Display_GroupDisplayServer\ Miscellaneous. but may be inside a phone number. To do this.. 10.. Notice. and select Restart to restart the program. Search in Directory Browser / Company Directory. Directory Browser ? The Company Directory of the Directory Browser doesn't work at all. No "A href" (HTML) tag already around it. Search in @Net Core (PVE) database. Search in Directory Browser / Personal Directory. The HTML code of the directory must fulfill the following requirements: No more then 2 HTML tags inside a phone number... 3. the CallLog Control service on the MyOffice server needs to be restarted: Start Services program via Start/Programs/ Administrative Tools/Services.. Then press right mouse button. Phone Display ? More users are licensed to use Phone Display.) 62 . but the caller lists don't work for them.5. 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. Select CallLogControl. Names 10. 2. The new users are not yet registered for call logging.. Group Display ? Modified user names in the ISPBX are not visible in the Group Display application.. (This data is coming from the PBX.

Maximum DB users: (5 .01 = 90. A concurrent user is a database user. Calculation rules: every SysManager.1. CA occupies 0. 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. Example 1: how many DB users can be served properly by a stand-alone MyOffice@Net system? PVE occupies 1 CU. 63 . The databases. CA. CA occupies 0.01 = 390. 2 x SV60E occupy 2 CUs. SuperVisor 60E or Call@Net application server (PVE) "occupies" 1 CU (Concurrent user).1) / 0. who wants access to the database but it can also be an application (such as SuperVisor 60E). which need to be accessed using MSDE for MyOffice@Net are: CM@Net.4. PVE and possibly Phonebook.1 CU. SM410 occupies 1 CU.A.1 CU and the MyOffice@Net Directory Browser occupies 0. This can be a person. Concurrent users with MSDE as database engine MSDE can handle up to 5 concurrent users.1) / 0. Maximum DB users: (5 .1 CU. The @Net Central Authentication module occupies 0.01 CU.

64 .