Professional Documents
Culture Documents
INTRODUCTION ............................................................................................4
2.
2.1.
2.2.
3.
3.1.
3.2.
3.3.
3.4.
3.5.
4.
4.1.
4.2.
4.3.
Requirements ........................................................................................................... 14
Preparations ............................................................................................................. 14
Group Arrangements ............................................................................................... 14
5.
5.1.
5.2.
5.3.
Requirements ........................................................................................................... 15
Preparations ............................................................................................................. 15
Group Arrangements ............................................................................................... 15
6.
6.1.
6.2.
6.3.
6.4.
Requirements ........................................................................................................... 16
Projecting IP Connections ........................................................................................ 18
Activate the Correct TMS Services (Optional) ........................................................ 20
Enable Phone Settings Functions (Optional) ............................................................ 20
6.4.1. Enable Follow Me and Don't Disturb .......................................................... 20
6.4.2. Enable Software SMA .................................................................................. 20
6.4.3. Enable Absent/present Switching ................................................................. 21
6.4.4. Enable AEM Message ................................................................................... 21
Group Arrangements ............................................................................................... 22
Saving Changes and Starting PVE Service ................................................................. 23
Multiple PBXs and MyOffice@Net .......................................................................... 23
6.7.1. DPNSS Clustered ISPBX ............................................................................. 24
6.7.2. Multi Unit ISPBX .......................................................................................... 25
6.5.
6.6.
6.7.
7.
INSTALLATION ............................................................................................26
7.1.
Table of Contents
PREFACE ...........................................................................................................2
Table of Contents
ii
7.2.
7.3.
7.4.
7.5.
7.6.
8.
8.1.
8.2.
8.3.
8.4.
8.5.
8.6.
9.
9.1.
9.2.
9.3.
9.4.
9.5.
9.6.
9.7.
9.8.
9.9.
9.10.
9.11.
9.12.
10.
TROUBLESHOOTING ................................................................................... 53
10.1.
10.2.
10.3.
10.4.
10.5.
10.6.
10.7.
General .....................................................................................................................53
Tracing: Diagnostic Monitor .....................................................................................55
SOPHO Info Console ...............................................................................................55
Directory Browser ....................................................................................................58
Group Display ...........................................................................................................58
Phone Settings ..........................................................................................................58
Microsoft Internet Explorer's Enhanced Security Configuration ..............................58
A.
MyOffice@Net
Installation Guide
PREFACE
This book gives a description of the installation, configuration and maintenance aspects of
MyOffice@Net, release 7.0.
GUIDELINES FOR MAINTENANCE AND ADMINISTRATION OF A SERVER /
SPECIALIZED COMPUTER
The following general rules should be kept in mind for a good administration and maintenance
of a Server / specialized computer:
1. Keep operating system and application software up-to-date
Servers by their very nature form a critical part of the infrastructure. When they go down
this will affect the entire business structure. It is imperative to keep the basic operating
system and application software working and also up-to-date both for stability and security
reasons. There can be an automated or semi-automated process for upgrades and
patches. However sometimes upgrades and patches can have unpredictable interactions
with running services. In case of doubts, please ask NEC Philips Unified Solutions about
the possible impact of specific updates or fixes.
2. Don't run unnecessary services or applications
Reduce risk by not running any non-essential service or application. It's about the possible
interactions between them (e.g. ports that are used by other applications too), the Server
capacity or security lacks that might be introduced by those applications.
When there is a need for combinations of applications then NEC Philips Unified Solutions
should be contacted.
Also check the manufacturer's features of the other product. Be aware of the impact on
the services that should be provided.
3. Back up your data
All computers will have a moment in time when they will fail (hardware or software).
Servers usually host data. Losing the Server also means losing data. That's why for every
production system (Servers, specialized machines) backup of the system and data is a
must. The backup procedure depends on many factors, like the volume of data, rate of
data change, the recovery procedure, time for backup and recovery, and the response of
the applications.
Sometimes an automatic backup cannot work. There are applications that must be aware
when the backup process is starting. This information you can find in the specifications
(requirements) of the products involved.
Summarized: there should be a backup policy, carefully analysed, built on the existing IT
infrastructure.
1.
Introduction
2.
3.
4.
5.
Check the following link to ShareNet for up-to-date information about which version of
Windows is needed: http://nsointra.pbc.be.philips.com/commonnet/prodmgmt/plct_docs/
Windows%20Support.xls.
LICENSING
To use MyOffice functionality the licenses should be present as described in the FCO. The
proper dongles and license files/strings should be present at installation.
2.
MyOffice@Net Architecture
2.1.
The Concept
MyOffice@Net consists of a number of web based telephony applications that are started on
a Web Client. The end user has access to the applications independent of the location and the
time of day; only access to the corporate intranet is necessary. Once logged on to
MyOffice@Net, all granted applications can be used without the need of a separate logging on
for each MyOffice@Net application during that session.
2.2.
Deployment View
3. A Microsoft LAN controlled by a domain controller between server and client PC's.
Preferrably the server and clients are part of the same domain. Other configurations are
Optional.
4. A database Server. This can be MSDE or SQL 2000 installed on the Web Server or SQL
2000 on a separate SQL Server. The database server contains several databases for
storage of own data (United database) and for the company directory (OpenWorX,
BTS(Optional)).
5. The PBX, either:
- a UNIVERGE SV7000 release 21.
The connection is based on the OpenWorX Application Interface (OAI) link, when in
a mixed network with SV7000.
- a SOPHO iS3000 release Call@Net 3.3 or higher.
The connection is based on PVE, OM, switching services and CSTA.
The PBX can be one of the following:
a stand alone (single unit) PBX;
a DPNSS network. (each DPNSS node can be a stand alone PBX or a FIN);
a network (multi unit) PBX; FIN (Fully Integrated Network), network protocol is
proprietary IMP.
- a SOPHO 2000 IPS release 12.2 (Optional) when in a mixed network with SV7000.
The connection is based on the OpenWorX Application Interface (OAI) link.
Both Open and Closed numbering schemes are supported, but Free Numbering scheme is not
supported.
The process flow as experienced by a user of a Web Client starting a MyOffice@Net
application, is as follows:
1. A user of a Web Client browses with the Internet Explorer to the Internet Address (URL)
of the Web Server. An example of such a URL is: http://pc22/ca/myoffice.aspx
2. A login screen is shown and the user must enter the Username and Password.
3.
System Requirements
The system requirements are split up into requirements for the Call@Net Application Server,
the SQL Server and the Client PCs. As far as service packs are concerned the latest available
service packs always need to be installed as soon as new service packs become available.
Check the following link to ShareNet for up-to-date information about which version of
Windows is needed and which service pack http://nsointra.pbc.be.philips.com/commonnet/
prodmgmt/plct_docs/Windows%20Support.xls.
3.1.
The Call@Net Application Server (MyOffice@Net modules are installed on this PC) must
meet the following requirements:
-
Minimum PC requirements:
- Pentium IV, 2 GHz or higher;
- 1 GB RAM;
- 4 GB free space on the hard disk with NTFS file system;
- Ethernet card (2 cards recommended). Two Ethernet cards are recommended to
enhance basic security. In that case a fixed IP address relation of MyOffice@Net and
PBX can be programmed on a PBX-LAN separate from the customers LAN. This is a
minimal solution intended for basic installations. A more advanced security solution
using VLAN configuration is preferred.
Windows Server 2003 operating system with SP1 or R2. The English version of the
Windows operating system is recommended.
IIS 6.0
Note: -
Other software and/or applications are only allowed on the Call@Net Application
Server in special cases i.e. Directory Distribution Services, Management@Net.
MyOffice@Net server cannot coexist with Management@Net versions lower than
3.1.0 or CC250 or Business ConneCT, on 1 PC.
We strongly advise to always have the latest Windows Service Pack installed; the
Windows problems solved in the Service Packs may influence the proper working of all
applications running on the Server, and/or influence Server security.
MyOffice@Net requires MDAC 2.8, to check the MDAC version use Microsoft
Component checker or open the registry (regedit) and search for the following key:
HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess\FullInstallVer
10
3.2.
A choice must be made which software controls the database access. This choice is related to
the size of the MyOffice@Net system (i.e. how many users participate in the system). For
small and medium sized MyOffice@Net systems (up to 400 clients) this can be Microsoft SQL
Desktop Engine (MSDE). For large systems SQL Server (SQL 2000) is required.
1. MSDE; MSDE 2000 with Service Pack 4 must be installed before installation of
MyOffice@Net.
Note: MSDE is limited to 5 concurrent users and 2 GB database size limit. See appendix A for
some examples concerning system size/amount of users.
2. SQL Server; SQL 2000 with Service Pack 4 is required. The SQL Server software is not
part of the MyOffice@Net software package. It can be obtained from Microsoft.
Note: During the installation the system administrator username (sa) and password is used,
therefore the SQL Server authentication should be mixed mode (SQL Server and Windows
authentication).
A SQL Server must meet the following requirements:
- Pentium III, 1 GHz or higher; (recommended: Pentium IV, 2 GHz)
- 1 GB RAM;
- Typical 500 MB hard disk space and additional space per database.
- Monitor: 1024 x 768 pixels / 17" screen;
- Ethernet card.
- Microsoft Windows 2000 (SP4) or 2003 Server (SP1);
- Microsoft SQL Server 2000 (SP4).
3. SQL Server 2005 (Optional). If support of SQL 2005 is required, please contact the
support desk.
3.3.
Client PC Requirements
PC's on which the MyOffice@Net applications are used, are called Clients in the context of
this book. These are the end user PC's. The minimum requirements are:
-
Note: The client operating systems mentioned above will only be supported as long as they are
11
3.4.
When the user of the client PC has administrative rights and the proper versions of the client
side software components are not present on the client PC, they are down loaded
automatically from the Call@Net Server at the first usage of the MyOffice@Net applications.
Restart the client PC when requested.
For general use the following components are installed:
-
Registry settings:
-
(string)
(DWord)
(DWord)
For installation of the client components see chapter 7.5. "Client Installation".
3.5.
Network Information
For communication between Server and Client, the following TCP ports (Server Side) are
used:
-
From the client side, random UDP and TCP ports are used.
12
13
4.
4.1.
Requirements
4.2.
Preparations
SYS 1 INDEX 79
SYS 1 INDEX 31
SYS 1 INDEX 241
SYS 1 INDEX 241
SYS 1 INDEX 241
SYS 1 INDEX 864
SYS 1 INDEX 864
SYS 1 INDEX 864
SYS 1 INDEX 864
bit 6
bit 2
bit 3
bit 7
bit 0
bit 2
bit 4
bit 5
must be 0
(OAI in service)
contents must be '0x06' for OAI
must be '1'
(OAI)
must be '1'
(SCFs)
must be '1'
(DTerm Display)
must be '1'
(built-in TCP)
must be '1'
(CCIS SMFN Indication is in service)
must be '1'
(8-port monitoring)
must be '0'
(reset connection)
If settings are incorrect, start monitor on OAI gives error 0x01020002 function not supported.
MAT commands
1. To read the software package release: DISS
2. To read/change ASYD:
ASYD
In the 'System' field, enter '1'.
In the 'index' field enter '241'.
Change bit 7 to a '1'.
4.3.
Group Arrangements
Only UCD groups and Call Pickup groups can be monitored. Nested groups are not
supported.
If Group Display is used, a 'Special Monitored Number' must be assigned in the SV7000. To
assign this number use the MAT commands AMNON and ALGNN.
14
5.
5.1.
Requirements
5.2.
Preparations
Program the (fixed) IP address and subnet mask of the SOPHO 2000 IPS PBX. The address
must be reachable from your MyOffice@Net Server, so it must be on the same subnet. Use
MatWorX to check the IP address and subnet mask via the command:
0B00 > 00 > for the IP address
5.3.
Group Arrangements
Only UCD groups and Call Pickup groups can be monitored. Nested groups are not
supported.
15
6.
6.1.
Requirements
ISPBX's connected to the Call@Net Application Server must meet the following
requirements:
-
Running software package SIP@Net 4.0 or higher, this to enable the use of software SMA
in MyOffice@Net 7.0 (Optional);
CIE package version 10.03 or higher;
The appropriate licenses, options and boundaries must be set, see tables below.
Number
Description
34
40
56
Description
64
121
123
16
Number
Description
277
CSTA boundary
324
Maximum number of sockets per unit; set to 100 (Default = 50; Max = 500
325
Maximum number of sockets per task (CPU3000 only); must be set to 50 (Max)
353
365
367
PVE maximum extension monitors; (Default = 50; Max = 65534); (*** For
Phone Display ***)
368
PVE maximum group monitors; (Default =5; Max = 65534); (*** For Group
Display ***)
370
371
379
380
411
SMA Unit; (Default )1 This boundary defines the unit number of the virtual SMA
ports.
17
6.2.
Projecting IP Connections
The Call@Net Application Server needs access to the ISPBX for PVE data exchange,
Operational Maintenance (OM) over IP and CSTA over TCP/IP. To enable this, a Client
Service Profile (CSP) is used. A CSP is an entity that states whether or not a TCP/IP user is
allowed to start a service and if so, which Logical Device Name (LDN) will be used. It is not
possible to assign services directly to the IP port. The services and their corresponding LDN's
must be assigned to a V.24 port and then mapped over IP using a Client Service Profile.
Note: Existing V.24 connections still can be used as the Client Service Profile only maps the
authority class and protection level to the IP connection and doesn't block the use of the
existing V.24 connections.
Normally, only a selective group of users should be able to connect to either one of the
services. Protection is introduced by means of a relation between the CSP and IP address of
the Call@Net application Server. This means the ISPBX will only accept OM and CSTA
commands coming from a trusted IP address therefore the IP address of both ISPBX as
Call@Net application Server must be fixed. The following steps describe the procedure to
18
define the CSP and to assign this profile to the Call@Net Application Server.
Note: In addition to the trusted IP address protection it is highly recommended to protect the
ISPBX's by creating a dedicated ISPBX-LAN (or VLAN) Using this setup connection of the
Call@Net application Server to the PBX-LAN needs to use a fixed IP address, the
connection to the company LAN however can use DHCP
Note: The default CSP (profile 0) should never be used as this profile does not use the trusted IP
protection mechanism.
19
6. Check authority classes and protection level of the OM device found or assigned in step
1. This device is used by MyOffice@Net modules (e.g. Phone Settings) to change settings
using OM commands.
Example:
- DIAUPR:VDU01; where VDU01 is the used terminal.
- CHSEAU: CHDEAU: CHSEPR: and CHDEPR: can be used to change authority classes
and protection levels of the used terminal.
More IP related OM commands:
-
network.
6.3.
The TMS service 4 (Automatic Directory Dialling) must be defined with a preferred window
(service) size of 5. This can be realized with OM command ASTMSW.
6.4.
The Phone Settings functions Call forward when busy / on no answer and voice mail are default
available for every end-user. The other functions are only available for end-users when their
phone number meets certain PBX conditions. These PBX conditions are described in the
following sections.
6.4.1.
End-users can only use Follow me in Phone Settings when FCM 7 is assigned to their phone
number.
End-users can only use Don't disturb in Phone Settings when FCM 25 is assigned to their
phone number.
6.4.2.
To be able to use Software SMA (SOPHO Mobility Access or Remote Office) each user needs
to be able to change their destination. This is controlled by FCM 75 change SMA destination
entitled. How to setup Software SMA can be found in the "Network and Routing Facilities Explained" manual
20
6.4.3.
End-users can only use Present/Absent for Group calls when their phone number is part of a
group and the group property 'Switch in/out of group' has been set to YES. (See also 6.5.
"Group Arrangements".) The following (Read Only) Facility Class Mark is assigned: FCM 19
(Group member). (This can be checked with OM command DIFACM).
End-users can only use Present/Absent for Executive/Secretary calls when their phone number
is part of an Executive/Secretary pool and the group property 'Switch in/out of group' has been
set to YES. The following (Read only) Facility Class Mark is assigned: FCM 21 (Executive) or
FCM 22 (Secretary).
6.4.4.
In MyOffice@Net, Presence Management is a feature for Phone Settings users. Users can set
a message and transfer their calls at the same time. This way other users will be able to see
the reason of absence if they call this user. The system works with status profiles i.e. In the
office, Out of the office. Each user can set their default daily routine in the scheduler, and
each user can also set a short-term status change to deviate from the default routine.
For example a user arrives every day at 9:00h and leaves at 18:00h, so the default schedule
says In the office between 9:00h and 18:00h on weekdays. If at any given day the user wants
to leave early, they can switch the short-term profile Out of the office until 18:00h. The
short-term profile overrules the schedule and the system will transfer all calls to the Out of
office destination. At 18:00h the timer expires and the system will switch to the schedule,
since in this case the schedule will say after 18:00h Out of the office the status will not change.
Another example: the same user has a meeting until 11:00h they switch the short-term profile
just before the meeting to In a meeting. All calls will be transferred to the In a meeting
destination. At 11:00h the timer expires, and the stem will switch the calls back according to
the schedule, in this case the In the office destination. If the meeting takes longer then the
dedicated time, the system doesnt know that of course.
This feature cooperates with AEM messaging on the iS3000 platform. If this is configured
correctly the users can also turn their Presence Management status on/off by using a prefix. So
our user from the second example could dial the prefix to extend the meeting period if the
meeting takes longer. Another benefit is that these AEM messages are also visible on the
operator console SV60E and telephone sets, so also non MyOffice@Net users will benefit.
A prefix can contain the until date or time the message should be active. After this date or
time the stem falls back to the default state as scheduled by the user. Table 6-4 "AEM Message
prefixes" gives an overview of the default prefixes. The default prefixes are *573nn and
21
*583nnhhmm (or *583nnddmm). The *573 and *583 are the actual prefixes, the 4th digit (3)
results in window 83 is used on the SS router, nn = message number, hhmm = hour/minute
and ddmm = day/month.
Message
In the Office
00
*57300
42
Lunch
43
Meeting
44
Working at home
45
Holiday
46
Reset message
The last digit is the expected number length after the prefix, 6 digits including time or date.
2. Assign the TMS window to use, per default the Switching Services router uses window 83
size 1 for AEM. The TMS Digit position declares which number in the prefix corresponds
to the default window, in our case digit 4 of the prefix: ASTMSD:4;
If necessary the windows size can be changed via ASTMSW: ASTMSW:83,1;
6.5.
Group Arrangements
The MyOffice@Net application Group Display needs group definitions to be projected in the
ISPBX. All type of groups can be distinguished: normal, ACD etc. Creating and modifying
groups is beyond the scope of this manual. Consult the Call@Net Voice Facilities manual for
details concerning group arrangements.
22
6.6.
Start the PVE service on the ISPBX to enable data exchange with the Call@Net Application
Server. (The supporting module @Net-Core is the interface to the PVE service on the ISPBX.)
Startup is realized with OM command STSRVC:0,<unit-nr>;. Verification of the running
service: DISRVC:0,<unit-nr>;.
-
The PBX reply started means the PVE service is running on the PBX.
The PBX reply connected means the PVE service is running on the PBX and @Net
Core is running on the Call@Net Application Server.
Make a backup of changed projecting by creating a new MIS file with OM command GEBUMI.
6.7.
The phone numbers used in a MyOffice@Net system need to be unique. For single unit PBXs
and FINs (FIN = Fully Intergrated Network) the phone numbers (DNRs) are unique by
default. The DNR (Directory number = phone number) is used to identify the internal phone
number.
For a DPNSS network, it is possible that the phone numbers in the network are not unique. To
solve the problem of not unique phone numbers in a MyOffice@Net system serving multiple
PBXs (a network), the term NDNR (Network DNR) is used. The NDNR must be unique
within the served (PBX) network.
Closed numbering scheme. When phone numbers (DNRs) in a DPNSS network are unique
for every PBX of this DPNSS cluster, the numbering scheme is called CLOSED. (The first
digit(s) of the phone numbers differ for every PBX of the DPNSS cluster.) For this type of
numbering scheme the NDNR = DNR.
Open numbering scheme. When phone numbers (DNRs) in a DPNSS network are NOT
unique for every PBX of this DPNSS cluster, the numbering scheme is called OPEN. For every
23
PBX of this DPNSS cluster the CLID (Cluster Identity) is used to identify each DPNSS node.
For this type of numbering scheme the NDNR = CLID + DNR. The 'N' (Network part) of
the NDNR is equal to the CLID.
Example: the DNR range of PBX1 and PBX2 is both 3000 ~ 4999. The CLID of PBX1 is 11
and the CLID of PBX2 is 12. The NDNR range of PBX1 is now 113000 ~ 114999 and the
NDNR range of PBX2 is 123000 ~ 124999.
The table below lists the option, which is involved in the type of numbering scheme. This
option must be set the same for each node in a DPNSS network.
Number
Description
40
6.7.1.
When the PBX is a DPNSS node, the following points must be taken into account:
-
24
Each node can be a single unit PBX or a multi unit PBX (FIN); (For a FIN the rules of 6.7.2.
"Multi Unit ISPBX"apply.)
Each node needs an IP connection to the IP network;
Each node needs its own PVE connection to the MyOffice@Net Server;
Each node needs its own CSTA connection to the MyOffice@Net server;
Each node needs its own OM connection to the MyOffice@Net Server (Optional, for PS
only);
Each node needs one SS connection to the MyOffice@Net Server (Optional, for PS only).
NDNR = DNR when option 40 = ON. NDNR = CLID + DNR when option 40 = OFF.
6.7.2.
When the PBX is a multi unit PBX (FIN) the following points must be taken into account:
-
25
7.
Installation
7.1.
When you want to use MSDE as database engine, skip this procedure. This procedure
describes how to check that the SQL Server is running and accessible, which is necessary for
the MyOffice@Net installation. Execute this procedure before you start with 7.4. "Server
Installation".
Preconditions:
1. Check the requirements for the SQL Server, section 3.2. "SQL (Database) Server
Requirements"
2. SQL Server 2000 is installed. (How to install this package is beyond the scope of this
manual.)
Steps:
1. Log on as Administrator to the SQL Server.
2. Check if the SQL Server is running. (When the SQL database engine is not running, restart
it.)
- Open the SQL Server Enterprise Manager: Start Menu > Programs > Microsoft SQL
Server > Enterprise Manager.
- Expand the SQL Server database tree.
- Check if the SQL databases are connected (SQL Server icon is green) and if not,
connect it: select the SQL Server, right click on it and select 'connect'. Figure 7-1
"Create the SQL Server Database connection." shows an example of how to connect
the SQL Server to the databases.
26
27
7.2.
MSDE Installation
When you want to use SQL Server as database engine OR you are using an already installed
and running version of MSDE, skip this procedure. This procedure describes how to install
MSDE on the Call@Net Application Server. Execute this procedure before you start with 7.4.
"Server Installation".
28
Preconditions:
1. Check the system requirements for the Call@Net Application Server.
Steps:
1. Log on as Administrator to the Call@Net Application Server.
2. Read the readme.txt file in the MSDE2000 folder on the CD-ROM.
3. Start the Installation of MSDE from the CD-ROM:
- Select Start > Settings > Control Panel.
- Select Add/Remove Programs > Add New Programs.
- Browse on the CD to MSDE2000 and run the file install.bat. DO NOT RUN
setup.exe!
4. Follow the instructions of the MSDE installation program.
5. The installation will be executed and the PC needs a reboot tot start MSDE.
6. Continue to check the necessary windows components.
7.3.
Use section 3.1. "Call@Net Application Server Requirements" to check the hardware and
software requirements. To check if the required windows components are running use the
following procedure:
29
7.4.
Server Installation
Click 'Next' after the required data is entered. The installation procedure tries to
connect to the database with the given input. When this fails, check if the settings is
correct.
7. The installation will be executed and asks for a reboot confirmation at the end. Click OK.
8. Wait until the PC is restarted and the installation has finished.
30
7.5.
Client Installation
When the MyOffice@Net applications are used on a client PC, some client side software
components are needed. These software components are stored in one compressed file. This
file can either be deployed to the client PC prior to first usage of the MyOffice@Net
application, or be down loaded automatically from the Call@Net Server on the first activation
of the MyOffice@Net application. The choice depends on whether or not the users of client
PC's have local administrative rights.
Deployment prior to first usage is the proper mechanism when the users of the client PC's
don't have administrator rights on their own PC. The deployment can be done via standard
Windows tooling such as SMS or Active Directory. To support this type of deployment, an MSI
file with the client software components is delivered together with the MyOffice@Net
package. From this file the client side components are installed by the Windows Installer
package; this package is standard in Windows 2000 and Windows XP.
When the user of the client PC has administrative rights and the proper versions of the client
side software components are not present on the client PC, they are down loaded
automatically from the Call@Net Server at the first usage of the MyOffice@Net applications.
Restart the client PC when requested.
Note: When you want to upgrade from an existing version of MyOffice 7.0 to a newer client
package, install the msi file with the following command line parameters:
msiexec /i "MyOffice@Net Client Components.msi" REINSTALL=ALL
REINSTALLMODE=vomus
To enable easy access to the MyOffice application, a shortcut can be placed on the desktop of
the client PC. If different users must be able to login into MyOffice, it is advised to create a socalled 'Program URL' (like "C:\Program Files\Internet Explorer\IEXPLORE.EXE" -new http://
PHILIPS-6CQ5QZG/CA/myoffice.aspx"). The shortcut should be deployed to the end users
with standard IT procedures.
7.6.
31
8.
General Configuration
The following procedures describe the configuration of the general part of MyOffice@Net.
8.1.
The following settings are recommended for Internet Explorer on client (and Server) PC:
-
Disable the setting: Reuse windows for launching shortcuts. You can find this setting
by selecting (in Internet Explorer): Tools > Internet Options > Advanced. The setting is
located in the Browsing section.
For the setting Check for newer versions of stored pages, we advise: Automatically.
You can find this setting by selecting (in Internet Explorer): Tools > Internet Options >
General (Temporary Internet files section) > Settings. When you select another option,
this can lead to either old pages being displayed (too few refreshed) or slower responses
and higher server load (too many refreshes).
If a proxy server is used, make sure either the option Automatically detect settings or
the option ByPass proxy server for local addressess is selected. You can find these
settings by selecting (in Internet Explorer): Tools > Internet Options > Connections-tab
and then click the "LAN Settings" button.
8.2.
Security Settings
After installation of MyOffice@Net the server security policies have to be set in order to
match the security policy of the network. MyOffice@Net is equipped with the SOPHO
Operating System Security Configurator tool. This tool can be used to:
-
Enable DCOM and other Services or Tasks for MyOffice@Net, if the password of the
PBC-UserAccount has changed. This can happen if the security policy forces you to change
passwords every x days.
Note: If you changed either the name (PBC-UserAccount) or the password with the Security
Configurator, you have to run it again after a reinstall or upgrade of MyOffice@Net.
If neither option is valid for your installation this procedure can be skipped.
You find the Security Configurator in
Start\Programs\MyOffice@Net\Support\Security Configurator.
32
2. After starting the Security Configurator, the Windows Firewall tab shows:
33
3. Set all check boxes for the MyOffice@Net applications to enable these applications. If no
Windows Firewall is present this list will be empty. If Management@Net is also installed
on the same Call@Net Application server more programs and services will appear in the
list.
4. Click OK.
34
2. If required according to the security policy the default useraccount PBC-Useraccount can
be changed to a valid username on the domain. The password can also be changed. The
tool will enable DCOM and other Services or Tasks for the new user for MyOffice@Net.
3. Click OK to close the window.
35
8.3.
Connect both the MyOffice@Net application dongle and the OpenWorX OAI dongle to the
MyOffice@Net server. The popup 'New hardware found' can appear when the
MyOffice@Net dongle is inserted. When not automatically registered, the driver for this
application dongle can be found:
-
36
8.4.
Steps:
1.
2.
3.
4.
37
8.5.
Additional Settings
The Miscellaneous part of the administrator window is used to change various additional
settings.
1. Start MyOffice@Net and log in as user 'Administrator' (no password).
2. Go to 'System Settings'.
3. Go to the 'Miscellaneous' tab to enter or change the following settings:
- Language
Here you select the default language, which will be offered to all users when using
MyOffice@Net applications. When additional languages are installed, MyOffice@Net
users can select their preferred language with Personal Settings.
Note: if you change the default language, the MyOffice server must be rebooted to make the
setting active.
Email Server
Enter the name of the mail server.
- Voicemail
Here you select whether the integrated voicemail is used or an external voicemail
system and you enter the voicemail number.
The voicemail server is defined in the Advanced Settings window. See also section
9.12. "Voicemail Configuration".
Click Save changes.
4. Click Go to Additional Settings to enter or change the following settings:
- Display Group Number Only
Activate the check-box when only phone numbers must be displayed in the Group
Display module instead of the names from the directory.
- Audio File
This file is played when a new call arrives for the group. Any *.wav sound file can be
selected but dont overdo it! Audio files are played completely when an event happens,
a 5 minute music file will play 5 minutes.
5. Click Apply to save your changes.
6. Click Back to return to the first Miscellaneous window.
-
8.6.
After installation of MyOffice@Net, the authentication mode to login to the application has to
be chosen. There are two possibilities: Authentication via the central authentication web
portal OR Integrated windows authentication.
38
Steps:
1.
2.
3.
4.
5.
6.
Figure 8-1 Nslookup of mailserver, the server with the lowest MX preference will be
registerd in the Mail Configuration window
39
Steps:
1. Start IIS Management Console: Start Menu > Programs > Administrative Tools > IIS
Management Console
(or select Start > Administrative Tools > Internet Services Manager).
2. Expand the Default Web Site tree
3. 'Right click' on CA and select properties
4. In the Directory Security TAB press Edit Anonymous Access and Authentication Control
5. Remove the check box Anonymous Access and choose Integrated windows authentication
6. Press OK (twice) and restart the IIS service (via Control panel > Administrative tools >
Services)
40
9.
Application Configuration.
This chapter describes the configuration of the MyOffice@Net application modules. When a
certain module is not used, the associated section can be skipped. After this chapter, the
applications are ready to be started on the MyOffice@Net clients.
9.1.
The company directory is not only used as source for the directory browser, it is also used for
user administration.
Note: When Windows accounts are used for logging in MyOffice@Net, you're automatically
logged in by your normal user account when starting MyOffice@Net. Use this URL to be
able to login as Administrator to CA: http://<MyOffice@NetServerName>/ca/
MyOffice.aspx?WCI=Login. Localhost is not allowed as <servername> , IP address is.
Steps:
1. Login to MyOffice@Net as Administrator (default no password). The first login from a
new PC will trigger a download of client components. Accept the download and press OK
2. Select the System Settings option.
3. Select the Company Directory window. This administrator interface looks almost the
same as the window of a user login in to Directory Browser, you can search the database
with names of employees already entered etc. However, when you login as administrator
you can also enter data.
41
The top part of the Company Directory UI shows the following fields:
- The element selection dropdown list, you can enter Employee, Hierarchy or Extension
data, select Extension to see if the data is entered automatically via the MATSync process.
- The search field(s) can be used to enter search criteria to search the database.
- The search button will search the database.
- The clear button clears the search field.
The middle part of the screen is where the information is displayed.
On the bottom-left side of the screen six buttons can be found (in employee view) to configure
the appearance of the electronic phone book. Basically, all users can choose their own search
and result criteria, the administrator decides what fields they can choose from and what the
default criteria are. From left to right:
The 'Directory Browser' button gives access to the electronic phone book.
The 'Personal Details button' is used to determine what fields from the phone
book will be displayed when 'detailed information' of a directory entry is
displayed. since you are logged on as Administrator these are the details of the
administrator.
The 'Configuration' button allows you to change the appearance of the search
fields and results. Every user has the option to do this.
The fields as added in the 'Search on' section are scanned by the browser to find
the text string the end-user invoked.
The fields as added in the 'Find as result' section are returned to the end-user
his/her browser.
The 'Combine Search Fields' checkbox is used to offer only one field in the
Company Directory for defining a text string to search for. The search fields are
selected in the Personal Settings section.
The 'Import' button allows you to import users from a csv file (which can be
opened as an excel sheet). The template is provided via the download link.
The 'Protection' button allows the system administrator to restrict the number
of fields available to the user to search on or find as result.
The 'Default Config' button allows the administrator to choose the default
settings for the users.
On the bottom of the screen you also see an extension field and dial button. The administrator
user interface is an extended normal user interface. The normal users cannot change the
company directory however. On the bottom right side of the screen are the edit buttons, to
add, change or delete entries. To change or delete an entry it first has to be selected from the
list. The buttons are not active until you click on an item in the list.
42
9.2.
43
9.3.
1.
2.
3.
4.
5.
6.
7.
In the Company Directory window, select Hierarchy from the element selection box
Click in the tree on the left on company level.
Enter the new company name in the field on the right and press Save.
Expand in the tree on the left on the new companys division level.
Enter the new division names in the field on the right and press Save.
Expand in the tree on the left on the new companys department level.
Enter the new department names in the field on the right and press Save.
Note: The default hierarchy can only be deleted after all extensions are moved to the new
hierarchy structure. All extensions, as well as all employees need to be part of the hierarchy
structure to be able to use them in the group display pane of the MyOffice@Net UI. If an
extension is not part of a specific department (for instance a telephone in a conference
room) the extension can be stored on company level.
9.4.
1.
2.
3.
4.
5.
6.
7.
8.
9.
44
9.5.
External numbers can be entered in the database via the following procedure:
Steps:
1.
2.
3.
4.
Like to the company directory also the external directory can be imported using a CSV file.
9.6.
By Web Directories of MyOffice@Net are meant; any web based directories available on the
internet. The Web Directory Configuration creates a hyperlink to this internet phone book.
When the user is searching this directory via MyOffice@Net the results will be scanned for
telephone numbers. If a number is found on that external web page, a hyperlink is created
from this telephone number to the MyOffice@Net dialler, thus allowing the user to dial this
number by a single click. The background application responsible is the Diabho number scan.
This application requires local settings on the client PC, these browser extensions will be
down loaded to the user on first use. Diabho is based on a text search engine there for will
only work if the internet directory gives text based results as well.
45
Steps:
1. Login to MyOffice@Net as Administrator
2. Select System Settings.
3. Select the Web Directory tab.
Match
NL
http://www.detelefoongids.nl/
detelefoongids
http://www.dastelefonbuch.de/
dastelefonbuch
UK
http://www.infobel.com/uk/
infobel
BE
http://www.infobel.com/belgium/
infobel
Philips
http://pww.phonedirectory.bnl.philips.com/ phonedirectory
46
9.7.
In MyOffice@Net 7.0 access is possible to the BTS/Phoneware database (as used by the
Supervisor 60E). MyOffice@Net 7.0 is only compatible with BTS data schema 2.3.0. BTS must
be installed on an English (US) SQL server, either on the MyOffice server or on a separate
server.
To configure the BTS directory:
1.
2.
3.
4.
5.
47
9.8.
To enhance flexibility in dialing outside the company, a set of dialing rules can be configured
so that possible prefixes are automatically added to or removed from the dialed number.
The dialing rules are applied to all calls setup from MyOffice@Net applications.
To configure the dialing rules:
1.
2.
3.
4.
5.
48
9.9.
1.
2.
3.
4.
5.
9.10.
In the Connectivity tab of the System Settings window, you can split the call forwarding
settings up into internal and external.
See section 6.4. "Enable Phone Settings Functions (Optional)" how to entitle iS3000 end-users
for all or parts of the Phone Settings functions.
iS3000 End-users can also activate/deactivate:
-
49
9.11.
50
My Groups displays only the group(s) of which the user is a member or supervisor,
All Groups lets the user choose from all available groups in the ISPBX.
9.12.
Voicemail Configuration
If a voice mail application is installed on your network, you can add a voice mail button to the
MyOffice@Net portal:
1.
2.
3.
4.
For more information on configuring voice mail, please refer to the documentation that came
with the voice mail application.
51
52
10.
Troubleshooting
10.1.
General
United database contains the CA account information, the personal directories and the
Directory Browser configuration data, the 'mirrored' PBX data, the SMA data, the
Function Key Menu's and Phone Display's List of Calls data.
PBX database (belongs to the CM@Net module) contains the PBX connection
information.
"Phonebook" database is the source for BTS Directory (Optional).
53
Figure 10-1 Setting the default network library protocol for an SQL Server's client.
? A security warning appears when a MyOffice@Net application is started...
Such a warning can popup when Phone Display, Group Display or Directory Browsers'
External directory is used for the first time. Activate the check-box Always trust content from
NEC Philips Unified Solutions B.V. and confirm with the Yes button. A possible restart of the PC
can be executed later.
? Applications are crashing after 1 day...
When you work with Application Pools in IIS, check the properties of NECPhilips Pool1 and
NECPhilips Pool2:
1. Open the Internet Information Services (IIS) Manager.
2. Right click on NECPhilips Pool1.
3. Select Properties.
4. Check that on the Recycling tab, all options are cleared.
5. Check that on the Performance tab, the option Idle timeout is unselected.
6. Click OK.
54
3. Type:
aspnet_regiis.exe -i
10.2.
10.3.
With the SOPHO Info Console you can activate tracing and make a snapshot of the current
status of a computer. This information can be very useful for debugging purposes by the
Technical Support department.
The current status can be saved in a file. Together with the snapshot you can include some
attachments (database files, etc.). The option Create generates a ZIP file and a SID file
(system info data). Both files must be sent to Technical Support when requested.
55
Automatically all files with extension .dfl/.mdb/.log/.ini/.txt/.pb that are in the folder Philips, are
extracted. This includes:
-
PC System info such as OS info (plus installed service packs), memory usage, running
processes, network configuration settings and DCOM settings.
relevant registry info.
License Manager info such as fingerprint and license string.
databases (info) and more.
56
5. On the Info menu, click User and enter the requested information for the Technical
Support department.
6. On the Info menu, click Create. This may take several minutes.
7. On the Info menu, click Save As and enter an understandable name for the ZIP and SID
file.
List of menu functions:
1. Info
1. Create
2. Open
3. Close
4. Save
5. Save As
6. User
7. Print
8. Print Preview
9. Print Setup
10. Recent File
11. Send
12. Exit
2. Edit
1. Copy
2. Select All
3. View
1. Toolbar
2. Status Bar
3. Refresh
4. Actions 1. Open
2. View
3. Attach
4. Detach
5. More Info
6. Properties
5. Options 1. Trace Settings
2. Attachments
3. Startup Empty
57
10.4.
Marked: the ZIP file is split up in several ZIP files, having a size
that fits on a 3.5 1.44 MB floppy disk
Directory Browser
10.5.
Group Display
? Modified user names in the ISPBX are not visible in the Group Display application...
Restart the Group Display application to synchronize with the ISPBX PVE service. Notice, that
for MyOffice@Net the following rule applies for Name search ("look-up"):
1. Search in Directory Browser / Personal Directory;
2. Search in Directory Browser / Company Directory;
3. Search in @Net Core (PVE) database. (This data is coming from the PBX.)
10.6.
Phone Settings
? When I switch to office I get a message 'Please switch to office with your set...
Phone Settings remembers the latest office telephone set you have used. When you switch to
office, your DNR is moved to that set. If you did not use a local telephone set before, Phone
Settings does not know were you are. By switching to office with your telephone set once, the
address of the set is made known to the system.
10.7.
58
Make sure that you select the check-box and click OK.
2. First time you send information to the web-application (e.g.: specify the login name) you
will get the following dialog:
Make sure that you select the check-box and click Yes.
3. First time the web-application tries to show a pop-up dialog (e.g. to install an ActiveX
component or to show an error-dialog) you will get the following dialog due to the fact
that the pop-up is blocked by default:
59
Make sure that you select the check-box and click OK.
Note that the previous dialog refers to the 'Information Bar' as shown in the next figure:
Right-click on the Information Bar and then click install ActiveX Control.
You will get a dialog to accept installation of a required ActiveX Control as shown in the
following figure:
60
61
5. First time you try to specify a number you will get the following dialog:
Right-click in the Information Bar and then click Always Allow Pop-ups from this site.
A confirmation dialog is shown:
Click Yes.
62
A.
MSDE can handle up to 5 concurrent users. A concurrent user is a database user. This can be
a person, who wants access to the database but it can also be an application (such as
SuperVisor 60E). The databases, which need to be accessed using MSDE for MyOffice@Net
are: United and possibly Phonebook.
Calculation rules: every SysManager, SuperVisor 60E or MyOffice@Net kernel "occupies" 1
CU (Concurrent user). The @Net Central Authentication module occupies 0.1 CU and the
MyOffice@Net Directory Browser occupies 0.01 CU.
Example 1: how many DB users can be served properly by a stand-alone MyOffice@Net
system?
-
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?
-
63
64