telenor samordnet kommunikasjon samordnet mobilstatus for microsoft...

Telenor Samordnet kommunikasjon

–

Samordnet Mobilstatus

for Microsoft Lync

Configuration, test and problem solving

09.07.13

© Telenor ASA 2009: Copying of this document is not allowed. Redistribution of this document

outside the company that has received it as part of the delivery of Telenor ”Samordnet Mobilstatus”

is not allowed

© Telenor ASA Side 2

Contents

1 Introduction ........................................................................................... 6

1.1 Prerequisites ..................................................................................... 6

1.1.1 Firewall rules ................................................................................ 7

1.2 Mobilstatus presence weight and privacy rules ............................................... 8

1.2.1 Weight ....................................................................................... 8

1.2.2 Privacy rules ................................................................................ 8

2 Technical solution ................................................................................... 10

2.1 Deployment alternatives ...................................................................... 10

2.2 Requirements .................................................................................. 11

2.3 Limitations ...................................................................................... 13

3 Installation and configuration ..................................................................... 15

3.1 MobileStatus server ........................................................................... 15

3.1.1 Installation ................................................................................ 15

3.1.2 Configuration ............................................................................. 18

3.2 OCS MobileStatus server ...................................................................... 21

3.2.1 Known issues .............................................................................. 21

3.2.2 Installation of prerequisites for Lync 2010 ............................................. 22

3.2.3 Installation of prerequisites for Lync 2013 ............................................ 22

3.3 Add an trusted application server to the LyncTopology .................................... 22

3.3.1 In Lync Topology Builder (at Lync frontend server) ................................... 22

3.3.2 Install Lync bootstrapper at the Application server ................................... 25

3.3.3 Add OCSMobileStatus as an trusted application at the application server. ......... 29

3.3.4 Certificate ................................................................................. 30

3.3.4.1 Creating and installing a certificate .................................................. 30


3.3.5 Installation and configuration ........................................................... 37

3.3.6 Configuring the program ................................................................. 40

3.3.7 Testing the installation ................................................................... 44

3.3.8 Running ................................................................................... 44

3.3.8.1 Running as a service .................................................................. 45

4 Test ................................................................................................... 46

4.1 MobileStatus Server ........................................................................... 46

4.2 OCS MobileStatus Server ..................................................................... 47

5 Operation and management ....................................................................... 48

5.1 AD ............................................................................................... 48

5.2 Web admin ..................................................................................... 48

5.2.1 Status (Mobile network service interface) ............................................. 49

5.2.2 Debug information ....................................................................... 50

5.2.3 Manage server and configuration ....................................................... 51

5.3 MobileStatus Server ........................................................................... 51

5.3.1 Server management ..................................................................... 51

5.3.2 Status information ....................................................................... 52

5.4 OCS MobileStatus server ...................................................................... 53

5.4.1 Server management ..................................................................... 53

5.4.2 Status information ....................................................................... 54

6 Change management .............................................................................. 55

6.1 User changes phone numbers ................................................................ 55

6.2 Changing IP-address of MobileStatus server ............................................... 55

6.3 Changing IP-address of the OCS MobileStatus server ..................................... 55

6.4 Changing FQDN of the OCS MobileStatus server ........................................... 55

6.5 Changing certificate on the OCS MobileStatus server computer .......................... 55

7 General Troubleshooting ........................................................................... 57


7.1 Verifying connectivity with the external mobile network service .......................... 57

7.1.1 ProffNett connectivity ................................................................... 57

7.2 MobileStatus server health ................................................................... 59

7.3 OCS MobileStatus server health .............................................................. 59

7.4 Mobile status update sent to Lync ........................................................... 60

7.5 Lync related problems ......................................................................... 61

8 Troubleshooting routines ........................................................................... 62

8.1 MobileStatus server is not running ........................................................... 62

8.2 OCS MobileStatus server is not running ..................................................... 62

8.3 MobileStatus server is not updating mobile phone status ................................. 62

8.3.1 For any mobile number .................................................................. 62

8.3.2 For one or a few mobile numbers only .................................................. 63

8.4 Differences in the resulting Busy Icon and activity string seen by other contacts ....... 64

8.5 Mobile status not visible for all contacts ..................................................... 65

Appendix A. OCS MobileStatus settings ................................................................. 66

Appendix B. MobileStatus Error messages, cause and resolution .................................... 69

B.1 General errors .................................................................................. 69

B.2 Telenor Mobilt Bedriftsnett specific errors ................................................... 70

Appendix C. OCS MobileStatus error messages, cause and resolution ............................... 72

C.1 Non-fatal errors................................................................................ 72

C.2 Fatal errors ......................................................................................... 72

C.2.1 SSL Certificate problems ................................................................ 72

C.2.2 Office Communications Server problems .............................................. 73

C.3.3 License errors ............................................................................. 75

Appendix D. OCS MobileStatus problems ............................................................... 76

D.1 Missing prerequisites .......................................................................... 76

D.1.1 UCMA Core missing ....................................................................... 76


D.2 Active Directory communication .......................................................... 76

D.2.1 Not in a domain ........................................................................... 76

D.3 Certificate problems ........................................................................... 76

D.3.1 Missing local certificate .................................................................. 76

D.3.2 Missing Certification Authority certificate .............................................. 77

D.3.3 Incorrect certificate used ................................................................ 77

D.4 Office Communications Server timeouts .................................................... 77

D.4.1 Incorrect GRUU ........................................................................... 77

D.4.2 Firewall configuration .................................................................... 77

D.5 Lync 2013 API bug ............................................................................. 78

D.6 Summary of error messages .................................................................. 79

Appendix E. OCS MobileStatus Log configuration ...................................................... 80


1 INTRODUCTION

This document describes prerequisites, configuration and problem solving routines for the “Telenor

Samordnet kommunikasjon, Samordnet Mobilstatus”.

Mobilstatus updates users’ Lync presence state based on the busy/free state of their mobiles. The

Lync presence updates include both changing the Busy/Free indicator and an activity indicator

string (“Mobile phone busy”). Changing of busy indicator is based on rules that are configurable

and adaptable to specific customer needs.

The Mobilstatus software is divided into two modules: The MobileStatus Server and the OCS

MobileStatus. The MobileStatus Server gets the presence status from the Mobile Network (I figure:

TSG = Telenor Service Gateway. The OCS MobileStatus module handles this data and updates the

Lync server presence values.

1.1 Prerequisites

The Telenor Mobilstatus service depends on “Telenor ProffNett Sentralbord Pluss” (PNSP) or the

“Mobilt Bedriftsnett Mobilstatus API”. It is recommended to postpone the installation of the mobile

status software until PNSP or Mobilstatus API has been delivered.

If using PNSP, the public IP address running the MobileStatus server should have been provided to

Telenor when the PNSP service was ordered. If this is not the case, or if the IP address of the

MobileStatus Server has later been changed, the MobileStatus server will not receive any status

updates.

The computer running OCS MobileStatus must be part of the customer Active Directory domain.

The users’ mobile phone number must be defined in the AD, in one of the fields: Telephone Number,

Home Phone, Mobile, IP Phone or Pager. It is recommended to define the mobile number as

“Telephone Number” if the “Telenor Samordnet kommunikasjon, Samordnet telefoni” is used due to

the privacy rules limiting access to other phone number entries.

OCS MobileStatus requires a license key to run, and will not start without it. Contact Telenor

customer support to obtain a license key.


The OCS MobileStatus server periodically contacts an external software license management

system to verify the license key and to submit a count of active mobile status users. These

statistics contains only a count and no other user or confidential data is exchanged. Be aware that

if the OCS MobileStatus server fails to contact the license management system for 14 days, the

software will stop processing mobile status changes and log this error condition.

1.1.1 Firewall rules

Dependent on the architecture chosen for the deployment, at least one firewall rule must be

configured for the Telenor ProffNett servers to be able to publish mobile status events to the

MobileStatus server.

Connection Source Destination Protocol

Host Port Host Port

PNSP

[TO]

MobileStatus

server

212.17.131.10,

212.17.131.11,

212.17.131.12,

212.17.131.13

- Public IP address of

MobileStatus server

2000 TCP

MobileStatus

server

[TO]

Telenor Mobilt

Bedriftsnett

Public IP

address of

MobileStatus

server

- tsg.telenor.no 80 TCP/ HTTP

OCS

MobileStatus

server

[TO]

External

software license

management

OCS

MobileStatus

- secure.mobileservices.dk 443 TCP/

HTTPS

OCS

MobileStatus

server

[TO]

MobileStatus

server

OCS

MobileStatus

- MobileStatus server 42 331 TCP

OCS

MobileStatus

server

[TO]

OCS Server/

Frontend

OCS

MobileStatus

- OCS Server/Frontend 5061 TCP/TLS


OCS Server/

Frontend

[TO]

OCS

MobileStatus

server

OCS Server/

Frontend

- OCS MobileStatus server OCSApplication

Port (default =

45871)

TCP

1.2 Mobilstatus presence weight and privacy rules

The Mobilstatus solution uses standard Lync mechanisms for publication of mobile phone status as

Lync Enhanced Presence. This implies that the standard Lync rules controls both “when” the final

user presence state is changed and “who” will see this.

1.2.1 Weight

A presence state includes a “Busy Value”, i.e. an “Availability Value” representing the availability-

weight of the presence state. The OCS server will only update the busy state if the new value is

higher, i.e. has more weight, then the existing presence state of the user. The weight of the mobile

status presence state is configurable and with a default value of 6449. Some of the standard

values used by Lync Communicator are as follows:

Presence state Icon Numerical value

Available

3000-3999

Busy

6000-6999

Do Not Disturb

9000 – 9999

Be Right Back

12000 – 12999

Away

15000 – 15999

Offline

18000 - 18999

This means that changing the setting specifying the mobile status presence weight to 10 000 will

make the mobile status busy state override “Do Not Disturb”.

1.2.2 Privacy rules

The same standard privacy rules in Lync related to the publication of personal information also

apply to the sharing of presence, including the “Mobile Phone Busy” presence state. The visibility

depends on the access level the owner of the mobile phone has defined for a specific contact:


1. Blocked: No mobile status information visible

2. Public: Visibility of mobile status changes only if the owner is logged into the Lync-server

3. Company, Team and Personal: Mobile status changes visible independent of the user is

online or not.


2 TECHNICAL SOLUTION

The figure below shows how “Telenor Samordnet Mobilstatus” relates to the Lync reference

architecture:

2.1 Deployment alternatives

The solution consists of two separate software servers to be deployed in the customer network:

1. MobileStatus server: Receives status messages from Telenor ProffNett or Telenor Mobilt

Bedriftsnett

2. OCS MobileStatus server: Receives status messages from the MobileStatus Server and

publishes this to the OCS server. The computer running this server needs to be a member

of the AD

Several options exist for the deployment of these servers in the customer network and the

placement depends on the customer preferences, network security topology and scaling needs.


Alternatives:

1. The MobileStatus Server on a dedicated physical or virtual computer in the DMZ zone

and the OCS MobileStatus Server at a dedicated physical or virtual computer in the

secure network segment

2. Both servers co-located in the same network as ad and Lync frontend pool servers.

Note

The OCS MobileStatus Server can not be co-located with the Lync frontend server. In

Lync all third party programs has to be installed at trusted application servers added to

the Lync Topology by the Topology builder.

2.2 Requirements

In addition to the firewall requirements described above, the mobile status solution has the

following requirements:

Network: The Mobilstatus solution and the mobile network mobile status services (Telenor

ProffNett and Telenor Mobilt Bedriftsnett) communicate over the existing Internet connection

of the company. A customer firewall needs to be opened as described in “1.1.1 Firewall rules”.

The traffic volume is limited to approximately 20 bytes per user per status change.

Hardware:

o MobileStatus server: 64- or 32-bits HW architecture


o OCS MobileStatus server: 64-bits HW architecture required.

Operating system:

o MobileStatus server: Microsoft Windows XP, Microsoft Windows Vista, Microsoft

Windows 7, Microsoft Windows Server 2003, Microsoft Windows Server 2008 or

Microsoft Windows Server 2012.

o OCS MobileStatus server: Microsoft Windows Server 2003 R2 ,Microsoft Windows

Server 2008 or Microsoft Windows Server 2008 R2 or Microsoft Windows Server 2012.

Lync 2010 is normally set up on Server 2008 or Microsoft Windows Server 2008 R2

Lync 2013 is normally set up on Windows Server 2008 R2 sp1 or Microsoft Windows

Server 2012.

Lync: Lync RTM Enterprise or Standard Edition

AD: The computer running OCS MobileStatus must be part of an Active Directory domain.

Office Communications Server users are linked to the mobile phone numbers using the

telephone number fields in the Active Directory user properties. When OCS MobileStatus starts,

or during a scheduled reload, it will read all users who are enabled for Lync (have a SIP URI),

and have at least one phone number from Active Directory. The user objects in the Active

Directory are used if they have a SIP URI and at least one phone number configured. A user can

be excluded if the user object’s “Description” field (on the Telephones tab of the User

properties in “Active Directory Users and Computers”) contains the string “No OCSMS”.

o The service looks up user identities in AD from the mobile numbers received from the

mobile network and requires the phone numbers of the users to be registered in the AD.

Mobile network interfaces:

o Telenor ProffNett: ProffNett Sentralbord Pluss (PNSP)

o Telenor Mobilt Bedriftsnett: Telenor Service Gateway API Status Push

The table below lists minimum requirements related to architectural choices and hardware, related

to the number of mobile status users.

Number of users

System requirements of MobileStatus server

< 1000 64 or 32 bit platform 2 GB RAM 2 GHz CPU

1000 – 10 000

64 or 32 bit platform 4 GB RAM

2 GHz multi core CPU

> 10 000 64 or 32 bit platform 4 GB RAM



Number of users

System requirements OCS MobileStatus server (both standalone or collocated with MobileStatus server.)

< 1000 64 bit platform 2Gb RAM 2 GHz CPU

1000 – 10 000

64 bit platform 4 GB RAM


> 10 000 64 bit platform 4 GB RAM


2.3 Limitations

PNSP will fail to deliver the correct mobile phone status in some situations, a failure that will also

result in the wrong mobile phone status reflected in Lync by the Mobilstatus solution. PNSP sends

full synchronization of status twice a day which will result in the correct status to be reset. The

status will so be corrected as soon as a new call is initiated or received.

The following scenarios will result in the wrong mobile phone status:

Case 1:

1. A calls B

2. A and B get status “Busy”

3. C calls B and C is not in the same ProffNett group as B

4. C listens to B's Voice Message and hangs up

5. Error: B’s status becomes “Available” although B is still talking to A

Case 2:

1. A calls B


3. A phone with A’s twin subscription (“tvilling”) SIM card makes a call and hangs up

4. Error: A gets status “Available” although A is still talking to B

5. B has still a correct status of “Busy”

Case 3:

1. A calls B


3. B is configured with call forward chain on no answer to C and D

4. B doesn’t answer and the call is forwarded to C who answers the call

5. B gets status “Available”

6. B makes an outgoing call

7. B gets status “Busy”


8. C hangs up

9. Failure: B gets status “Available” although B is still busy

Case 4

1. A calls B


3. B rejects call

4. Failure: A gets hang with status “Busy”


3 INSTALLATION AND CONFIGURATION

The MobileStatus server and the OCS MobileStatus server are installed separately and in this

order.

3.1 MobileStatus server

Before installation starts, and if using ProffNett, it is recommended to verify network connectivity

with the ProffNet mobile status servers by opening a command shell and pinging the IP-

addressees in range 212.17.131.10 - 212.17.131.13.

3.1.1 Installation

This installation will install the server program, running as a Microsoft Windows Service, and a

stand-alone configuration program which is a standard Windows application. The configuration

program is installed on the same PC as the service. The server program will be automatically

deployed as a Windows service and configured to start automatically.

The MobileStatus Server program is installed by executing the installation program ’Setup-

MobileStatus Server-2.2.0-English.exe’, supplied on CD-ROM or downloaded from the Internet.

(Latest version per 1st April 2011: Mobile Status Server 2.6.2 )

MobileStatus Server Setup

Please press [Next >] to

continue the installation

process.


License Agreement

Please read the Software

License Agreement carefully

and only check ’I accept the

terms in the License

Agreement’ and [Next >] to

continue the installation if you

understand and agree to the

terms and conditions set

forward in the agreement.

Install Location

MobileStatus installation

program has the default install

location folder: ’C:\Program

Files\Mobilestatus Server’. A

different destination folder can

be selected by using the

[Browse…] button.

Please press [Install] to

continue the installation

process.


Firewall setup

A dialog window asking if the

Windows Firewall should

automatically be configured

may be presented during

installation.

If a firewall is running on the

server, the answer should be

[Yes]. If not select [No].

If answering [Yes] and the

firewall is not running, the error

messages can be neglected.

Installing

The installation program

subsequently installs the

program and copies relevant

files to the installation

directory.


Completion

It is recommended that the

“Run configuration program” is

selected. Then press [Finish] to

finalize the installation process

and start the configuration of

the MobileStatus Server

program.

3.1.2 Configuration

The MobileStatus Server program consists of two parts, one being the server running as a Microsoft

Windows Service, and the other being the configuration program which is a standard Windows

application. The configuration program needs to be deployed on the same PC as the service.

The MobileStatus Server is configured and managed through the MobileStatus Configuration

program. After the initial configuration, it can also be configured through the web server interface

built-into the server (see “5.2 Web admin”).

MobileStatus Configuration

Select [Edit] and [Settings] to open the

settings dialog window.

Be aware that it may take several seconds

until the dialog window becomes visible.


Services:

Define the external mobile status services

to use. This is a multiple choice selection

making it possible to configure the solution

to receive status from several sources

simultaneously.

If using Telenor ProffNett PNSP, select [Use

Telenor ProffNett].

If using Telenor Mobilt Bedriftsnett, select

[Use Telenor Mobilt Bedriftsnett Status]. For

this, you also need to configure the

username and password in the [Operator]

tab.

StatusPlan only available in Denmark.

Operator

The Operator settings tab only applies if

using TelenorMobilt Bedriftsnett.

[URL]: The existing default URL should

be http://tsg.telenor.no/TSG/

(remember last slash-character)

[Username]: The username provided by

Telenor for accessing the Mobilt

Bedriftsnett Status service

[Password]: The password provided by

Telenor for accessing the Mobilt

Bedriftsnett Status service

http://tsg.telenor.no/TSG/


E-mail

These settings are used for specifying an e-

mail address to which the MobileStatus

server should send alerts in case of

problems.

To enable this, select [Use e-mail alerting

on errors].

See the table below for an explanation of

the other configuration settings.

E-mail alerting

SMTP Server The SMTP server to be used by the MobileStatus server for delivering

relay outgoing mails

From address The source address to be used when sending alerts

Recipients A semi-colon separated list of e-mail addresses which should

receive e-mail alerts. Default MobileStatus alert e-mail address of

Telenor is [email protected]

Test This will verify the settings by making OCS MobileStatus attempt to

send an e-mail using the entered values

Advanced e-mail options

Username If your SMTP server requires login, enter the username here. Note

that the MobileStatus server only supports “Basic authentication”

and not “Integrated Windows Authentication”

Password The SMTP server login password

Use SSL for SMTP If checked, MobileStatus Server will use SSL encryption when

communicating with the SMTP server


Port The port number to connect to the SMTP server on. The default is 25

Web

If you want to use the web interface, you

must configure a username and a password.

Without these, the web interface will be

disabled. The "Allow remote support to

access the web administration" must then

also be checked.

[Username]: The username you want to

use to log in to the web interface.

[Password]: The password you want to

use to log in to the web interface

[Allow remote support to access the

web administration]: Must be checked

for enabling access to the web interface

3.2 OCS MobileStatus server

The deployment of the OCS Mobile Status application requires five steps:

1. Add a trusted application pool server into Lync topology (not nessesary if other third party

applications, who can share the same server exists in the Lync Topology)

2. Run setup at the server(installs the replica service, lync prequsites and certificate)

3. Add OCSMobilestatus as a trusted application

4. Installation of the program files and initial configuration

5. Configuring the program

3.2.1 Known issues

OCS MobileStatus server uninstaller will not uninstall any Lync software. To uninstall the Lync

programs at the trusted application server you have to follow the documentation on how to

decommission a Lync server.


3.2.2 Installation of prerequisites for Lync 2010

For Windows Server 2008 the .NET Framework 3.5 Service pack 1 is installed by adding this feature

in the server Manager

3.2.3 Installation of prerequisites for Lync 2013

For Windows Server 2008 R2 Service Pack 1, the .NET Framework 4.5 and PowerShell 3.0

should be downloaded and installed. Also the Windows identity Foundation 3.5 should be

added form the Server Manager under “Features”.

For Windows Server 2012, .NET Framework 4.5 and Power Shell 3.0 is already installed. The

only requirement is Windows Identity Foundation 3.5 which can be added from the Server

Manager under ”Features”.

Because of stability issues in the earlier versions of Lync2013, we recommend upgrading to

Lync2013 with the Cumulative update that was released on July 1 2013 or newer.

Here are some useful links:

Lync 2013 Prerequisites

Microsoft .NET Framework 4.5

Installing Windows PowerShell3.0

Microsoft Management Framework with PowerShell3.0

Upgrading to latest 2013 version: http://support.microsoft.com/kb/2809243.

3.3 Add an trusted application server to the LyncTopology

The following steps are similar for Lync 2010 and lync 2013.

3.3.1 In Lync Topology Builder (at Lync frontend server)

Add the server as a trusted application server in LyncTopologibuilder.

http://technet.microsoft.com/en-us/library/gg398686.aspx

http://www.microsoft.com/en-us/download/details.aspx?id=30653

http://technet.microsoft.com/en-us/library/jj205328.aspx

http://www.microsoft.com/en-us/download/details.aspx?id=29939

http://support.microsoft.com/kb/2809243


Adding the server on Microsoft Server 2008


Adding the server on Microsoft Server 2012


3.3.2 Install Lync bootstrapper at the Application server

Run setup from the Lync server RTM setup media and run through the following steps:


Velg Install or Update Lync Server System


1. Install Local Configuration Store

a. Select to retreive the configuration directly from The Central Management Store, if

the application server is on the same network as the CMS server. (Normaly located

at LyncFE server)

2. Setup or Remove Lync Server Components

3. Request, Install or Assign Certficates

4. Start Services starts the Lync Server Replica service.

3.3.3 Add OCSMobileStatus as an trusted application at the application server.

From Lync Server Management Shell (Run as administrator)

New-CsTrustedApplication -ApplicationId OCSMobileStatus -TrustedA


pplicationPoolFqdn <appserver FQDN> -Port 45871

After this cmdlet has succeded,

run

Enable-CsTopology

3.3.4 Certificate

The communication between OCS MobileStatus and the Office Communications Server

infrastructure is encrypted using Transport Layer Security (TLS). TLS requires certificates to

validate server identity and perform the encryption. This means that the server running OCS

MobileStatus must have a certificate which is trusted by the Office Communications Server

infrastructure, and the Office Communications Server with which the OCS MobileStatus

communicates must have a certificate which is trusted on the computer that runs OCS

MobileStatus.

If OCS MobileStatus is installed on the same computer as the Office Communications Server with

which it communicates, the necessary certificates are normally already generated and installed

during the Office Communications Server deployment. In that case it is normally not required to

create a separate certificate for OCS MobileStatus.

A certificate must be generated if OCS MobileStatus is running on a different computer. Depending

on the organization’s Public Key Infrastructure, the actual procedure may vary. The procedures

required for a regular installation are described in this chapter.

3.3.4.1 Creating and installing a certificate

Creating a certificate for the computer which is running OCS MobileStatus is easiest done by use of

Lync Server Deployment wizzard


Lync Server 2010 Certificate Installation (Lync Server 2013 is similar)

In the certificate wizard you can request, import or assign certificates.

A Lync enviornement is normaly set up with an internal certification authority and certificates

generated by this CA is used for all internal certificates.

We will now show screenshots of the generation of a certificate. In a new deployment this

certificate is also assigned in the same operation by clicking next, next… Therefore we do not have

added screenshots of that process.

We now show the certificate generation.


Next

If direct access to CA, use choice send the request immedeatly.

NEXT


If you have more than 1 actual CA you may have to select the right CA.

NEXT

Normally just click NEXT here.


NEXT

Friendly name . Here you can choice what you like. Fqdn or just a part of that is normally used

here.

Bith length now has to be at least 2048, (2048 is recommended)

If you want to move the certificate to an other hardware it is important to marke the private key as

exportable.

NEXT


Organisation is mandatory .

All 3 is mandatory to fill in.


Then you see the fqdn of the server is automatic filled in as the subject name of the certificate as it

has to be.

Just click NEXT

No subject alternate names is nessesary.

NEXT


Then you get the cr summary. Check that the information is correct before you click next next …

and there you go.

Finish.

3.3.5 Installation and configuration

OCS MobileStatus is installed using the installation program “Setup-OCSMobilestatus.exe”. The

installation program will also check for necessary prerequisites, and will install the required

Microsoft Visual C++ 2008 and UCMA Core Redistributable packages.

If any prerequisites which are not part of the installation package are missing, the installation

cannot complete.


Install Wizard

Preconditions are tested and resolved

automatically during startup.

Wait until this step has been finalized.

If the Visual C++ 2008 Redistributable

Package was previously installed, the install

wizard may give an error message and stop.

If this happens, restart the installation

program. If this doesn’t solve the problem,

the server needs to be restarted.

Welcome

Select [Next >] to start the installation.

License Agreement

Select [I accept the license agreement]

and [Next >] to proceed.


Destination Folder

Change default folder if necessary (default

can be kept).

Select [Next >] to proceed.

Start Menu

Change default selections if necessary

(defaults can be kept).

Select [Next >] to proceed.

Ready to Install

Select [Next >] to start installation.


Setup Complete

Unless you are upgrading from a previous

version and want to keep your settings, it is

recommended that you let the installation

program write the defaults to the registry.

Select [Run OCS MobileStatus

Configuration program now] to proceed with

configuring the program.

Select [Finish >] to complete the setup and

start the configuration program.

3.3.6 Configuring the program

All settings used by OCS MobileStatus can be defined in the OCS MobileStatus Configuration

program.

The Configuration program can also be used to control the OCS MobileStatus Windows service.

The settings are divided into three tabs:

• Connections

• E-mail

• Other

The settings in the “Connections” tab relate to OCS MobileStatus connectivity to the Lync Server

environment and the MobileStatus Server. The settings in the “E-mail” tab are used for e-mail

alerting in case of fatal errors and warning messages in the OCS MobileStatus application.

The settings in the “Other” tab are for advanced configuration and typing the License key.

When you have changed configuration settings, you must save the settings by clicking the “Save”

button. Changes do not take effect before they are saved and the OCS MobileStatus service or

console applications have been restarted.


Connections

The settings on the

“Connections” tab in the

Configuration program relate

to OCS MobileStatus’

connections to the Lync

Server environment and the

MobileStatus Server.

See the table below for the

available settings in this

dialog.

MobileStatus Server

Server FQDN / IP The hostname or IP address of the server where MobileStatus Server

is installed.

Lync Server connections are found by the application automatically

E-mail

OCS MobileStatus can send e-

mails to configured addresses

in case of errors and warnings

which have impact on the

function of OCS MobileStatus.

To enable e-mail alerts,

configure the settings related

to the e-mail server, From

address and To addresses.

The table below describes the

configuration parameters. The

other selections in this tab are:

[Save settings]: Saves the

current configuration

values

[Reset]: Resets the values

to previously saved values


E-mail alerting

E-mail alerting enabling OCS MobileStatus will send alerts about warnings and fatal errors

using the settings configured here if this option is checked

SMTP server The SMTP server to use when sending alert e-mails.

From address The sender e-mail address of the alert e-mails.

To addresses Enter a semi-colon separated list of e-mail addresses which

should receive the e-mail alerts. Default Mobilstatus alert e-mail

address of Telenor is [email protected]

Test This will verify the settings by making OCS MobileStatus attempt

to send an e-mail using the entered values

If your server requires login or other advanced settings, these can be set in the lower part of the

window.

Advanced e-mail options

Username The username to use if the SMTP server requires login. If a

username is configured, the e-mail alerting system will attempt to

log on to the SMTP server. Note that the OCS MobileStatus server

supports both “Basic authentication” and “Integrated Windows

Authentication”.

Password The password to use when the SMTP server requires login.

Use SSL for SMTP Enable this option if the server uses SSL encryption.

Port The SMTP server's port number. Default is 25.


Other

The settings on the “Other”

tab are used for advanced

configuration as well as the

License key information.

See table below for the

specific settings.

Active Directory

Active Directory Import root

path

When importing users for which OCS MobileStatus should set the

presence, it will automatically search for enabled users in the

Active Directory. If you would like OCS MobileStatus to not use the

entire Active Directory when importing, you can select a sub-tree

of the Active Directory by entering the LDAP path of an

Organizational Unit. You can also browse to the OU by clicking the

“Browse” button.

Country code When OCS MobileStatus receives a status update from the mobile

phone network, the phone numbers are received with a country

code. If the user phone numbers in the Active Directory are not

configured with a country code, you must enter a country code

prefix, so the numbers match. The country code prefix must be

entered with +, e.g. +47 for Norway.

Import interval Select a periodic update interval to determine how often OCS

MobileStatus should check for updates in the Active Directory.

Advanced Settings

OCS Busy text The text to be displayed next to users in Office Communicator and

other client applications when the user’s mobile phone is busy.

Default is “Mobile phone busy”.

OCS Busy value The OCS availability value to be set when a user’s mobile phone is

busy. This should be a value close to 6500, as the value will

determine the color of the icon next to user when the user’s


mobile phone is busy. Default is 6499.

License key

Company name Enter the company name exactly as typed in your license key

information.

License Key Enter the license key exactly as typed in your license key

information.

The license key information can be validated by clicking the “Check” button. This will contact the

license server to check your input.

3.3.7 Testing the installation

To test the configuration settings and the proper functioning of OCS MobileStatus it is possible to

run the program as a console application.

On startup it will establish contact with the Lync Server and the MobileStatus Server. When

connection to both has been established, it will begin to handle incoming mobile phone status

updates.

To verify that configuration settings are correct, run the OCS MobileStatus Console application and

verify that it can connect to both the MobileStatus Server and the Lync Server. Also verify that

when a mobile phone for a configured user changes state, the user should have his or her presence

information updated in Lync (Communicator).

Note that if you run the OCS MobileStatus Console application on Windows 2008 it must run with

administrative privileges to be able to access the certificate.

To run OCS MobileStatus as a command line application, you can start it by double-clicking it from

the program installation folder (default is C:\Program Files\OCS MobileStatus). The program is

named “OCSMobileStatusConsole.exe”. Be sure that the server is not already running as a service

when the program is started in this way.

3.3.8 Running

OCS MobileStatus is available as both a Windows command line application and a Windows

Service. The service can run unattended, and automatically start when Windows starts, but the

command line application is better for debugging configuration issues.

To run OCS MobileStatus as a command line application, you can start it by double-clicking it from

the program installation folder (default is C:\Program Files\OCS MobileStatus). The program is

named “OCSMobileStatusConsole.exe”. (If the server is running Windows 2008, the OCS

MobileStatus Console application needs to be run with administrative privileges to give it access to

the Machine certificate store). Before running the program as a command line application, be sure


that the program is not already running as a service. If this is the case, first stop the service using

the windows service control panel.

The installation program configures the Windows Service, but does not start it automatically, as it

will not run without the necessary configuration settings. The service is configured to start

automatically when Windows starts.

When you have verified that the configuration settings are correct using the command line

application, you should use the OCS MobileStatus Windows Service to run OCS MobileStatus in a

production environment.

3.3.8.1 Running as a service

You can start the OCS MobileStatus service using the Configuration program. To start the service,

open the “Service” page in the configuration program and click the “Start” button.

If you make changes to the configuration settings, it is required to restart the service. You can stop

the OCS MobileStatus using the “Stop” button on the “Service” page in the configuration program.

If the service starts and does not stop immediately, it is working properly and connected to both

the Lync Server and the MobileStatus Server.

If the service stops unexpectedly, look in the Windows Event Viewer Application log for the cause,

and use the command line application to check for problems.


4 TEST

After the initial installation, make sure the servers are up and running and make test calls to

mobiles enabled for mobile status.

Verify the successful update of the mobile phone status on the specific Lync user. Regardless of

the outcome of this test, verify the operation of the servers and configuration as described below.

4.1 MobileStatus Server

Look at any error/warning messages and verify the operation of the MobileStatus using one of the

two following means (see also “5.1. AD”):

1. Select “Log” in the ’Edit’ menu in the menu bar of the MobileStatus configuration program

2. Access the built-in web server by opening the following URL in a web browser:

http://<address of MobileStatus server>:2000/adminstration/administration, where IP-

address is the address of the MobileStatus server provided to Telenor.

Verify that the information indicates a healthy and operative MobileStatus server, i.e. status

"System OK"/"Ready and waiting"/"Connected" and a time for last connection with the Telenor

ProffNett service. Be aware that it may take up to 6 minutes after start/restart until the server is

detected by the Telenor service.

When the status indicates an established connection to the Telenor mobile status service, the

operation is ready for testing.


Also take a look in the system application event log and look for any warning or error messages

logged by the MobileStatus server.

4.2 OCS MobileStatus Server

On startup, the server will establish contact with the Office Communications Server and the

MobileStatus Server. When connection to both has been established, it will begin to handle

incoming mobile phone status updates.

The easiest way to discover any problems is to start the server and open the system application

event log and look for any warning or error messages logged by the OCS MobileStatus server.

Also take a look in the program log file for any warning or error messages. The file location is

configured by the registry setting “LogConfiguration”. The default location is C:\Program Files\OCS

Mobilestatus\ ocsmobilestatus-<year>-xxxxx.log).

Example: Ola.nordmann has made a call: AggregateState 2 means busy and AggregateState 3

means free.


5 OPERATION AND MANAGEMENT

5.1 AD

The OCS MobileStatus server synchronizes information from the AD during startup and periodically.

If phone numbers are changed in the AD, this change will be reflected in OCS MobileStatus.

The users’ mobile phone number must be defined in the AD, in either of the fields: Telephone

Number, Home Phone, Mobile, IP Phone or Pager. It is recommended to define the mobile number

as “Telephone Number” if the “Telenor UC One Number” is used (due to the privacy rules limiting

access to other phone number entries).

A user can be excluded if the user object’s “Description” field (on the Telephones tab of the User

properties in “Active Directory Users and Computers”) contains the string “No OCSMS”.

Note that phone numbers defined by the users themselves using Communicator is NOT available in

the AD and thereby not for the Mobilstatus solution.

The OCS MobileStatus server will print warning messages during startup of any duplicate phone

numbers registered in the AD.

5.2 Web admin

The MobileStatus Server can be accessed through the Internet via a standard web browser,

provided the firewall is configured for this facility, i.e. it is open for the specific source address. This

interface provides status information and simple management of both the MobileStatus and OCS

MobileStatus server.

To use this interface, the MobileStatus server web access must have been enabled and configured

with a username, password as described in “3.1.2 Configuration”.

To access this interface, open the following URL in a web browser: http://<address of MobileStatus

server>:2000/adminstration. The <address of MobileStatus server> is the IP address or FQDN of the

MobileStatus server. To log on to this interface, use the configured username and password.


MobileStatus Web admin

The interface provides the following options:

[See status]: Overall status information

of the external mobile network service

interface

[See debug information]: Further details

about status and health

[Manage server]: For management

(start/stop) and configuration of the

server

5.2.1 Status (Mobile network service interface)

See status

This interface gives overall status

information of the external mobile network

service:

[Last heartbeat]: Time and date for last

received heartbeat message from the

mobile network interface.

[Last reset]: The start time of the

MobileStatus Server or the time when

“Clear Information” was selected in the

configuration program.

[Total reports]: The total number of

status updates received from the

mobile network since start or reset.

[Total users]: The number of unique

MSISDNs for which the MobileStatus

Server has received status updates

since start or reset.


5.2.2 Debug information

See debug information

This interface gives detailed status and debug information of the MobileStatus server:

[Phonebook]: Shows current status of each known MSISDN as well as the source and

date/time of the last update

[OCS MobileStatus Connection]: Status and statistics of the OCS MobileStatus server

[Server warning messages]: Error and warning messages logged to the Window Application

Event log by the MobileStatus server (and optionally e-mailed)

[Client errors]: Error and warning messages logged to the Window Application Event log by

the OCS MobileStatus server (and optionally e-mailed)


5.2.3 Manage server and configuration

Manage server

This interface gives information about the

connection between MobileStatus and OCS

MobileStatus. It also provides the following

management of the respective servers:

[Restart]: Restart the respective server

[Stop]: Stops the respective server

[Configure]: Starts a web interface for

(re)configuring the respective server.

For further information about

configuration of the MobileStatus and

OCS MobileStatus server, see “3.1.2

Configuration” and “3.3.6 Configuring

the program” respectively.

If stopping or restarting the MobileStatus Server, the connection to the Web admin interface will be

lost and you will need to reconnect.

5.3 MobileStatus Server

This section describes the operation and management of the MobileStatus server. Note that

status, debug and simple management can also be done using the Web admin interface described

in “5.2 Web admin”.

5.3.1 Server management

In addition to using the Web admin interface, the MobileStatus server service can be started,

stopped and restarted using the standard Windows services control panel under the name “Telenor

MobileStatus Server”.

Management of the server can also be done using the MobileStatus configuration program:


Select [Edit] and [Manage service] to open

the management dialog window.



The following operations are available:

[Stop]: Stops the MobileStatus service

[Start]: To start the service

The server is installed as a Windows service and configured to start automatically. It is also

installed with the service recovery settings of [Restart the service] on first and second failure and

with [Take no action] on subsequent failures.

5.3.2 Status information

The MobileStatus configuration program, located in the Windows start menu, provides status and

debugs information and also access to the configuration program. Log messages are also sent to

the default system application event log and to the e-mail address if enabled and configured.


The window is divided into three sections:

1. Connection: Contains status information about the connection to the mobile network

service:

• Client: The IP-address of the remote mobile network service


• Status: Overall state of the MobileStatus server. See table below for a description

of all status messages.

• Ping: Timestamp for last received heartbeat message from the mobile network

service

2. Information: Information about mobile status reports received

“Telenor MobileStatus Server”: This log window, enabled by selecting [Log Window] in the [Edit]

meny, enables you to see the real-time communication log between the MobileStatus server and

the status service of the mobile network operator, as well as the communication between the

MobileStatus Server and the OCS MobileStatus server.

1.

Connection status messages

Offline Not connected to a mobile network status source. This is only used

during startup and shutdown of the server.

Listening on port xxxx Ready and waiting for the first connection from ProffNett PNSP. This

state is only used when waiting for first connection.

System OK A heartbeat was received

Connection down No heartbeat received for 6 minutes

Ready and waiting Ready and waiting for status update from mobile network

Connected ProffNett is sending a status update

Further information is available by selecting the [Open the troubleshooting web interface] in the

main configuration window. See “5.2.2 Debug information” for further information about this debug

information web interface.

5.4 OCS MobileStatus server

5.4.1 Server management

The OCS MobileStatus server can be run as a console application or as a Windows service. If run as

a service, start, stop and restart of the OCS MobileStatus Server are done using the standard

windows services control panel:

1. Start the ’Services’ panel located in the System Control Panel

2. Double click on “Telenor OCS MobileStatus Server”

If run as a console application, the server can be stopped by typing “Ctrl+C” in the command

windows.


5.4.2 Status information

OCS MobileStatus server log messages to the file specified in the registry key “LogConfiguration”

(see “3.3.6 Configuring the program”). The default location is C:\Program Files\OCS Mobilestatus\

ocsmobilestatus-<year>-xxxxx.log). See “Appendix E. OCS MobileStatus Log configuration” for a

description of the log roll-over mechanism and log configuration settings.

Messages printed to the log file are also sent to the default system application event log.


6 CHANGE MANAGEMENT

6.1 User changes phone numbers

If a user’s phone number is changed in the AD, the changes will not be applied until an AD re-

synchronization by the OCS MobileStatus server has been performed. This is done periodically and

during startup of the OCS MobileStatus server as described in “5.1 AD”.

6.2 Changing IP-address of MobileStatus server

If the IP-address of the MobileStatus server changes, either due to changes in network

infrastructure or if the server is moved (reinstalled) on another computer, the following steps are

required:

1. Telenor customer service is contacted and given the new IP-address for changes in the

ProffNett PNSP service.

2. Verify the “LocalHostName” setting of the OCS MobileStatus server (see “3.3.6 Configuring

the program”)

3. Add any changes to the firewall to enable the status messages to pass through from the

ProffNett PNSP servers and the Mobilestatus server (see “1.1 Prerequisites”)

6.3 Changing IP-address of the OCS MobileStatus server

No changes are necessary if the OCS MobileStatus server keeps the same FQDN. If this is not the

case, see next section.

6.4 Changing FQDN of the OCS MobileStatus server

The OCS MobileStatus sever requires that the computer has a valid certificate and this must be

verified. The certificate is locked to a specific FQDN so changing the FQDN of the existing server

makes it necessary to create and install a new certificate.

The FQDN was used during installation in enabling the trust relationship between the OCS server

and OCS MobileStatus server. When changing the FQDN, this process has to be repeated and the

recommended procedure is to do a reinstallation of the OCS MobileStatus server.

6.5 Changing certificate on the OCS MobileStatus server computer

If the certificate on the computer running the OCS MobileStatus server is changed, the OCS

MobileStatus server must be reconfigured to use the new certificate. This is done using the

Connection Tab in the OCS MobileStatus server configuration program (see “3.3.6 Configuring the

program”).


7 GENERAL TROUBLESHOOTING

In addition to network infrastructure related problems, 7 main problem sources exist:

1. Failure in the mobile network mobile status service

2. Connectivity problems with the mobile network mobile status service

3. MobileStatus server related problems

4. Problems with the OCS MobileStatus server

5. Failure to resolve the Lync user identity from the mobile phone number

6. Communication problems between the OCS MobileStatus server and the Lync server

7. Mobile status updates on a user not visible for other user(s).

There is a multitude of troubleshooting methods to identify these problem sources and solve the

problem but the following test procedure is recommended:

The rest of this chapter describes how to verify the health and operation of each part of the

Mobilstatus solution. See also further information on accessing status and debug information in “5

Operation and management” and the troubleshooting routines described in “8 Troubleshooting

routines”.

7.1 Verifying connectivity with the external mobile network service

7.1.1 ProffNett connectivity

The MobileStatus server receives periodically heartbeat messages from ProffNett and successful

reception of heartbeats indicates connectivity. Verify the connectivity and successful reception of

a mobile phone status update using the MobileStatus server configuration program:



Verify:

From the host computer, verify

network connectivity by

pinging the ProffNett IP-

addresses range

212.17.131.10 –

212.17.131.13.

Client: Identifies the IP-

address to the active

ProffNett server. Should be an

address in the range

212.17.131.10 –

212.17.131.13

Status: Should indicate

“System OK”

Ping: Time and date of the last

received heartbeat message

That the server receives a

status update when a phone

call is made. Look for:

o “Connection status

changed” message in

the log window

(enabled by [Edit] and

[Log Window]

o Phone number and

status printed in the

information field “Last”

If lack of connectivity with ProffNett is indicated, three failure sources exist:

1. No heartbeat received yet: It may take several minutes after startup of the MobileStatus

server until the ProffNett servers detect this and start submitting heartbeat messages.

2. A firewall blocks the traffic between the ProffNett servers and the MobileStatus server.

Verify that the network firewall allows traffic to flow on TCP-port 2000 from the IP-address

range 212.17.131.10 – 212.17.131.13 to the IP-address of the MobileStatus server.

3. ProffNett is not configured with the correct IP-address of the MobileStatus server. Contact

Telenor customer support to verify this.


7.2 MobileStatus server health

Check that:

1. The MobileStatus server process (“Telenor MobileStatus Server”) is running by using Windows

Services management tool or the system “Task Manager”. If not running, start the service

using the standard Windows Services management tool.

2. The MobileStatus server configuration program can be started

3. No warning or error messages from the MobileStatus server is printed to the default system

application event log

If the MobileStatus server stops functioning, check the Windows Application Event log for errors.

The program will log all fatal errors to the Application Event log. See “Appendix B. MobileStatus

Error messages, cause and resolution” for further information.

Status of the server can be accessed either through the Configuration program Log Window or

Web Access as described in “5.2 Web admin” and “5.3.2 Status information”.

7.3 OCS MobileStatus server health

Check that:

1. The OCS MobileStatus server process (“Telenor OCS MobileStatus Server“) is running by using

Windows Services management tool and the system “Task Manager” (if started by console the

OCS MobileStatus service will be stopped and you have to look for the OCS MobileStatus

console process in task manager). If not running, start server either as a console application or

as a windows service as described in ”5.4 OCS MobileStatus server”

2. No warning or error messages from the OCS MobileStatus server is printed to the default

system application event log

3. No warning or error messages are printed to the program log file. The name and path is

configured through the registry setting “LogConfiguration” (Default location is C:\Program

Files\OCS Mobilestatus\ ocsmobilestatus-<year>-xxxxx.log)

4. That the OCS MobileStatus server has established a connection to the MobileStatus server as

follows:


Connection between OCS

MobileStatus and MobileStatus

server

Open a web browser on the

address http://IP

address:2000/dump

In “OCS MobileStatus

Connections” section (bottom),

verify:

Client IP: That the address of

the OCS MobileStatus server is

printed

Info time: Timestamp for last

info packet submitted

Updates since

restart/reconnect: Successful

status updates sent

If the OCS MobileStatus console application or the service stop functioning check the Windows

Application Event log for errors. The program will log all fatal errors to the Application Event log.

See “Appendix B. MobileStatus Error messages, cause and resolution” and “Appendix D. OCS

MobileStatus problems” for further information.

For troubleshooting purposes, it is recommended to run the server as a command line application.

If already started as a windows service it needs to be stopped first (see “5.4 OCS MobileStatus

server”). To run OCS MobileStatus as a command line application, simply run “OCS MobileStatus

Console” from the OCS MobileStatus start menu folder.

If the server throws an Exception, it is recommended to run the server as a console application by

first starting a command shell, change directory to the program folder (default: C:\Program

Files\OCS Mobilestatus\) and then type the command “OCSMobilestatusConsole.exe”). When the

Exception is thrown, select [OK] in the debug dialog window. This will print a full stack trace in the

command window that is necessary for further problem solving.

7.4 Mobile status update sent to Lync

If the OCS MobileStatus server receives an status update, it may fail to submit this to the Lync

server if it fails to resolve the Lync user identity from the mobile phone number. This error condition

is logged to the log file specified in the configuration of the OCS MobileStatus server (Default

location is C:\Program Files\OCS Mobilestatus\ ocsmobilestatus-<year>-xxxxx.log). Such failure

may be caused by:


1. User not a valid Lync user

2. Changes to the AD have not been synchronized to the OCS MobileStatus server. Currently,

synchronization only occurs during startup and if any changes are made, the server needs

to be restarted.

3. The mobile of the user is not correctly specified in the AD as described in “5.1 AD”.

4. Multiple Lync users registered with the same phone number. Notification of duplicate

entries is logged to the console window on startup, if the server is started as a console

application, and to the log file.

7.5 Lync related problems

An Lync infrastructure is complex and a multitude of problem sources may cause a status update

to fail or to be invisible for others.

There is nothing special with the handling of mobile status compared to the handling of other

presence information in Lync and Communicator, i.e. both regarding to when a status change

overrides an existing presence state but also the visibility of the change for other contacts. See

“1.2 Mobilstatus presence weight and privacy rules” for further information.

For all other Lync related problems, the most important tool for locating and solving is the “Lync

Server Logging Tool”, more info about this tool is found at http://technet.microsoft.com/nb-

no/library/gg558599(en-us).aspx

http://technet.microsoft.com/nb-no/library/gg558599(en-us).aspx

http://technet.microsoft.com/nb-no/library/gg558599(en-us).aspx


8 TROUBLESHOOTING ROUTINES

8.1 MobileStatus server is not running

If the MobileStatus server is not running, use the following problem solving routine:

1. Verify that the server is not running using the Windows Services management tool or the

system “Task Manager”.

If not running, start the service using the standard Windows Services management tool.

If it still doesn’t starts, continue to next step.

2. Open the default Windows System Application event log and look for any error or warning

messages logged by the MobileStatus server. Any such message will in most circumstances

identify the problem.

3. If the problem can’t be solved locally, contact Telenor customer support.

8.2 OCS MobileStatus server is not running

If the OCS MobileStatus server is not running, use the following problem solving routine:

1. Verify that the server is not running using Windows Services management tool or the system

“Task Manager”.

If not running, start the service using the standard Windows Services management tool.

If it still doesn’t starts, continue to next step.


messages logged by the OCS MobileStatus server. Any such message will in most

circumstances identify the problem.

3. Look for any warning or error messages in the program log file. The name and path is

configured through the registry setting “LogConfiguration” (Default location is C:\Program

Files\OCS Mobilestatus\ ocsmobilestatus-<year>-xxxxx.log)

4. If the problem can’t be solved locally, contact Telenor customer support.

8.3 MobileStatus server is not updating mobile phone status

8.3.1 For any mobile number

1. Verify if the user itself sees the status update when logged in using Lync Communicator. If this

is the case, i.e. related to the visibility of the status update to other contacts, this is related to

Lync presence privacy issues. See “1.2.2 Privacy rules” for further information.


2. Verify that the MobileStatus server is running using the Windows Services management tool or

the system “Task Manager”.

If not running, use the problem solving routine described in “8.1 MobileStatus server is

not running”.

3. Verify that the OCS MobileStatus server is running using the Windows Services management

tool or the system “Task Manager”.

If not running, use the problem solving routine described in “8.2 OCS MobileStatus

server is not running”.

4. Verify connectivity with the external mobile network service using the information described in

“5.3.2 Status information”. Look for information about connection status and perform a test

call when looking in the information field about last status message received and in log window.

If connectivity problems are indicated, verify that the company firewall doesn’t block

the communication (see “1.1.1 Firewall rules”)

5. Verify that the firewall is not blocking the communication with the external license

management system as described in “1.1.1 Firewall rules”. The OCS MobileStatus server will

stop processing mobile status updates if it fails to establish a connection for a period of 14

days. If this is the case, this problem will be indicated in the Application event log.


messages logged by the MobileStatus server. Any such message will in most circumstances

identify the problem.

7. If the problem can’t be solved locally, contact Telenor customer support. If using ProffNett,

please verify that the correct global IP-address of the MobileStatus server has been provided

to Telenor.

8.3.2 For one or a few mobile numbers only

Two main causes for this exist:

i. Mobile phone number(s) is not registered in the company subscription group or enabled for

mobile status (ProffNett or Mobilt Bedriftsnett).

ii. The OCS MobileStatus server fails to resolve the Lync user from the mobile phone number

received from the mobile network service. This may be because this user is not a Lync user, not

registered with the mobile phone number in the AD or this specific phone number is registered

on multiple users.

Use the following troubleshooting routine:

1. Verify that this problem is just related to one or a few users. If this is not the case, use the

routine described above in “8.3.1 For any mobile number”.


2. Verify if the user itself sees the status update when logged in using Lync Communicator. If this

is the case, i.e. related to the visibility of the status update to other contacts, this is an effect of

the standard Lync presence privacy rules. See “1.2.2 Privacy rules” for further information.

3. Start the MobileStatus server configuration program and enable the log window as described in

“5.3.2 Status information”.

4. Do a test call from/to the mobile phone number and identify any information about a status

update received on this specific call by looking in the information field about last status

message received in the MobileStatus server log window.

If no information received from the external mobile network service, the number is

probably not enabled for mobile status. Contact Telenor customer support.

If the status indicates that the MobileStatus server received an update, proceed to

next step.

5. Verify that the mobile phone number is registered on this respective user in the AD.

6. Verify that the user is not disabled for MobileStatus in AD by a “No OCMS” in the “Description”

field.


messages logged by the MobileStatus server and OCS MobileStatus. Any such message will in

most circumstances identify the problem.

8. Look for any messages about duplicate registration of a phone number in AD in the OCS

MobileStatus program log file. The name and path is configured through the registry setting

“LogConfiguration” (Default location is C:\Program Files\OCS Mobilestatus\ ocsmobilestatus-

<year>-xxxxx.log). Multiple instances of a phone number on different users are not allowed

since this service must be able to identify a specific user based only on the phone number.

9. Look for any other messages in the OCS MobileStatus server log file that may indicate the

problem.

10. If the problem can’t be solved locally, contact Telenor customer support. If using ProffNett,

please verify that the correct global IP-address of the MobileStatus server has been provided

to Telenor.

8.4 Differences in the resulting Busy Icon and activity string seen by

other contacts

Any differences in the Busy Icon or activity string seen by other contacts are an effect of the

generic Lync presence privacy rules and presence aggregation rules. See “1.2 Mobilstatus

presence weight and privacy rules” for an explanation of this.


8.5 Mobile status not visible for all contacts

Any differences in the Busy Icon or activity string seen by other contacts are an effect of the

generic Lync presence privacy rules and presence aggregation rules. See “1.2 Mobilstatus

presence weight and privacy rules” for an explanation of this.


APPENDIX A. OCS MOBILESTATUS SETTINGS

If you should require central management of the OCS MobileStatus configuration settings, you can

change all settings in the Windows Registry. The path in which the settings are stored is:

HKEY_LOCAL_MACHINE\Software\BluePosition\OCS MobileStatus

The values are as described in the table below.

Setting name Type Default

value

Required Notes

CCSServer String None Yes Hostname or IP of MobileStatus

server.

ADImportRootPath String None No LDAP path to an organizational

unit which contains the users to

automatically set Lync status

for. If not configured, uses all

users from the entire Active

Directory.

ADImportPrependCountryCode String None No The country code to prepend to

the numbers imported from the

AD. Only used if the numbers do

not start with + or 00.

ADImportInterval DWORD 1440 No The interval in minutes for

automatic import from Active

Directory. Value can be one of:

0 (meaning only on startup), 60,

120, 240, 720, 1440

LocalHostName String None Yes Hostname of the computer

running the OCS Mobile Status

application. Must be in a form

which can be resolved by the

Lync server.

OCSGRUU String None Yes GRUU (Globally Routable User-

agent URI).

OCSServer String None Yes DNS name of the Lync server or

pool to communicate with.

OCSServerTLSPort Integer 5061 Yes The port on which the Lync

server listens for incoming TLS

connections.


OCSApplicationPort Integer 45871 Yes Port used by OCS Mobile Status

for incoming communication

from the Lync server. Must be

the same as configured while

creating the GRUU in the

Configuration program.

OCSBusyValue Integer 6499 Yes The availability value used when

setting a user’s status to ‘Mobile

phone busy’. For the best user

experience, the value should

near or equal to 6500 as the

Lync Communicator client

treats those values as “busy”.

OCSMobileBusyString String Mobile

phone

busy

Yes The custom activity string used

when setting a user’s status to

‘Mobile phone busy’.

CertificateSerialNumber String None No If configured it must be the

hexadecimal serial number of

the certificate to use for TLS

communication with the Lync

server.

If CertificateSerialNumber is

configured, only a certificate

with that serial number is used. If

it is not configured, the Local

Machine certificate store is

searched for a certificate which

has the value of the

LocalHostName configuration

setting as either the Subject

Name or the Subject Alternate

Name.

SMTPAlerting String True No ‘True’ or ‘False’ to define

whether SMTP alerting is

enabled

SMTPFrom String Yes The From address when OCS

MobileStatus sends an e-mail

alert

SMTPPassword String No The password used when

sending e-mail alerts. Only used

if a SMTP username is also

configured.


SMTPPort DWORD 25 The port number to connect to

the SMTP server on.

SMTPServer String Yes The SMTP server to use when

OCS MobileStatus sends an e-

mail alert.

SMTPRecipients String Yes A semi-colon separated list of

SMTP addresses that should

receive e-mail alerts.

SMTPUsername String No The username to use when

sending e-mail alerts when the

server requires login. If

configured, a login will be

attempted on the server.

SMTPUseSSL String No ‘True’ or ‘False’ depending on

whether the SMTP server

requires SSL/TLS encryption.

LogConfiguration String Set by the installer to make OCS

MobileStatus log to a file in the

program installation folder.

InstallPath String Set by the installer to contain

the installation directory. Do not

change this value.

RuntimeInformation String Contains runtime state

information which is used by

OCS MobileStatus when the

service is restarted.


APPENDIX B. MOBILESTATUS ERROR MESSAGES, CAUSE AND

RESOLUTION

This appendix describes the error messages which the MobileStatus Server may log to the Windows

Application Event log or e-mail to the SMTP Alert recipient e-mail address.

B.1 General errors

Error message Cause Resolution

Unable to bind socket. Maybe an other instance of MobileStatus Server is already running.

Another program is using TCP port 42331.

Close the other program and restart MobileStatus Server.

Telenor status system down. No connection.

It has been too long since the last heartbeat was received from Telenor.

Check the connectivity of the MobileStatus Server. Verify that Telenor is sending status data using Proffnett.

Error when saving status information: message

MobileStatus Server was unable to store the current status database. The message contains further information.

The fix is dependent on the actual cause. The message contains information from the operating system about the actual cause.

Unable to start status server. Error: message

Unable to start the Telenor Proffnett or StatusPlan interfaces. The message contains the error from the operating system.


Error while storing e-mail alert message prior to sending. Sending alert even though it may be a duplicate.

An error occured while storing the alert e-mail about to be sent.

Try to restart the MobileStatus Server. The error will not cause the MobileStatus Server to fail, but it will resend similar error messages.

Telenor MobileStatus cannot handle clients other than OCS MobileStatus and MobileStatus Relay. Client will be disconnected.

A client which is not allowed with your license type has tried to connect to the MobileStatus Server.

Upgrade your license to a full MobileStatus Server license.

Unable to restart service: message (code)

The MobileStatus Server was unable to restart the MobileStatus Server service.


Unable to stop service: message (code)

The MobileStatus Server was unable to stop the MobileStatus Server service.



B.2 Telenor Mobilt Bedriftsnett specific errors


Invalid Telenor Username. Cannot initialize Mobilt Bedriftsnett status monitoring. No status will be received from Mobilt Bedriftsnett.

The Telenor Mobilt Bedriftsnett username cannot be empty.

Configure the correct Mobilt Bedriftsnett username

Invalid Telenor password. Cannot initialize Mobilt Bedriftsnett status monitoring. No status will be received from Mobilt Bedriftsnett.

The Telenor Mobilt Bedriftsnett password cannot be empty.

Configure the correct Mobilt Bedriftsnett password

Unable to initialize Telenor status monitoring. No status will be received from Mobilt Bedriftsnett.

Either Telenor Mobilt Bedriftsnett cannot be reached or the username/password combination is invalid.

Check the username and password, and that Telenor Mobilt Bedriftsnett is in service.

Telenor Mobilt Bedriftsnett: Unable to connect to event services.

Most likely invalid XML was received from Mobilt Bedriftsnett

Try to restart the MobileStatus Server. If the error is repeated verify that Telenor Mobilt Bedriftsnett is in service.

Telenor Mobilt Bedriftsnett: Login failed. message (code)

Invalid username or password for Mobilt Bedriftsnett is configured.

Check the username and password. If they are correct, verify that Telenor Mobilt Bedriftsnett is in service.

Telenor Mobilt Bedriftsnett: Logout error (code) message


This is not a critical error. It occurred during shutdown of the Mobilt Bedriftsnett connection. Verify that Telenor Mobilt Bedriftsnett is in service.

Telenor Mobilt Bedriftsnett: Error starting monitoring. message



Telenor Mobilt Bedriftsnett: Error connecting to event service. message (code)



Telenor Mobilt Bedriftsnett: Exception while getting event: message

An error occured while retrieving a status update from Mobilt Bedriftsnett. The message contains more details on the cause.

The fix is dependent on the actual cause. Try to restart the MobileStatus Server. If the error is repeated verify that Telenor Mobilt Bedriftsnett is in service.

Telenor Mobilt Bedriftsnett: Exception while cleaning up after previous error. message

This is a follow-up from the previous error. The message contains more details on the cause.

The fix is dependent on the actual cause. Try to restart the MobileStatus Server. If the error is repeated verify that Telenor Mobilt Bedriftsnett is in service.



Telenor Mobilt Bedriftsnett: Received too many errors on getEvent. Re-initializing interface.

Most likely Telenor Mobilt Bedriftsnett has experienced problems, and MobileStatus Server will attempt to recover.

This is not a critical error although status updates may have been lost in case Mobilt Bedriftsnett was unstable.

Telenor Mobilt Bedriftsnett: Unable to recover from monitoring error (message). Mobilt Bedriftsnett monitoring is not functioning.

There are severe problems with Mobilt Bedriftsnett. MobileStatus Server has given up trying to recover.


Telenor Mobilt Bedriftsnett: message while recovering from previous error: stacktrace

Severe problem getting status from Telenor Mobilt Bedriftsnett


Telenor Mobilt Bedriftsnett: Invalid XML received. message - XML

Telenor Mobilt Bedriftsnett sent invalid XML for a status update. message contains the problem and XML the data received.


Telenor Mobilt Bedriftsnett: Unknown CSTA event type: eventtype. Ignoring event.

Telenor Mobilt Bedriftsnett sent invalid XML for a status update. Eventtype contains the invalid data.


Telenor Mobilt Bedriftsnett: Unknown event received: eventtype

Telenor Mobilt Bedriftsnett sent invalid XML for a status update. Eventtype contains the invalid data.



APPENDIX C. OCS MOBILESTATUS ERROR MESSAGES, CAUSE AND

RESOLUTION

This appendix describes the error messages which OCS MobileStatus may log to the Windows

Application Event log or e-mail to the SMTP Alert recipient e-mail address.

C.1 Non-fatal errors

Non-fatal errors indicate failure to receive mobile status information. OCS MobileStatus is still

working, but external issues are the cause of problems receiving status.


Connection to MobileStatus Server lost. MSS address: hostname/IP

OCS MobileStatus lost the connection to the MobileStatus Server - the cause may be network problems, server outage etc.

This is not a fatal error. OCS MobileStatus will try to reconnect continously. The alert is only sent once until connectivity has been restored. Fix the network problems and verify that MobileStatus Server is running.

C.2 Fatal errors

Fatal errors make OCS MobileStatus stop operation. The errors can be due to invalid configuration

parameters, or external problems which impact OCS MobileStatus operations in such a way that it

is not possible or feasible for OCS MobileStatus to continue running.

C.2.1 SSL Certificate problems


No certificate with private key found with subject name localhostname. (exception details)

The server running OCS MobileStatus does not have a certificate with a private key with the subject name localhostname

The server must have an SSL certificate with the same name as the server's local hostname (set in the configuration program).

Unreadable certificate store (LocalMachine). Cannot read certificate to use with OCS communication. Shutting down. (exception details)

OCS MobileStatus was unable to open the Windows LocalMachine certificate store.

The exception details may contain further information about the cause.

Insufficient permissions to read LocalMachine certificate store. Cannot read certificate to use with OCS communication. Shutting down. (exception details)

The account used to run OCS MobileStatus does not have read permissions for the Windows LocalMachine certificate store.

Fix the permissions - verify by opening the store using MMC (as described in the Installation and Configuration guide)



The LocalMachine certificate store contains invalid values. Cannot read certificate to use with OCS communication. Shutting down.

OCS MobileStatus was unable to open the Windows LocalMachine certificate store.


Found certificate with the configured serial number (certificate serial number), but it has no private key. Unable to use this certificate (Subject name: subjectname)

The certificate configured does not have a private key. The certificate must have a private key.

Use a different certificate. Remember to export the certificate including the private key from the CA. (Described in the Installation and Configuration guide).

No certificate with the configured serial number SerialNumber found. Cannot continue without a valid certificate for communication with Office Communications Server

The certificate which was selected in the configuration program no longer exists on the computer.

Verify that the certificate still exists in the Windows LocalMachine certificate store.

Certificate issued to subjectname not found. Cannot continue without a valid certificate for communication with Office Communications Server

The certificate which was selected in the configuration program no longer exists on the computer.

Verify that the certificate still exists in the Windows LocalMachine certificate store.

Certificate failure while creating OCS endpoint for sipuri. Likely cause is incorrect or invalid SSL certificate or remote certificate is not trusted. (exception details)

The certificate is incorrect or invalid (maybe too old), or the OCS server does not trust the certificate.

Verify the certificate details and the chain of trust in the certificate used. The exception details may contain further information about the cause.

C.2.2 Office Communications Server problems


Invalid configuration values. Either LocalHostName, OCS Application Port or OCS GRUU are invalid. (exception details)

One of the mentioned configuration parameters contain invalid data.

Check the configuration.

OCS Application Port value OCSApplicationPort is not a valid TCP port number (exception details)

The OCS Application Port configuration parameter is invalid

Check the configuration. The port number must be between 1025 and 65535.



Error occured while establishing Lync Platform connection. (exception details)

A problem occured when initializing the connection to the Lync Frontend server.

This is most likely due to an invalid certificate or invalid configuration settings regarding the Lync server (e.g. port or hostname).

Unable to start Lync Platform connection. BeginStartup returned null. (exception details)


This is most likely due to an invalid certificate or invalid configuration settings regarding the Lync server(e.g. port or hostname).

Unable to start Lync Platform connection. BeginStartup returned an invalid value. (exception details)


This is most likely due to an invalid certificate or invalid configuration settings regarding the Lync server(e.g. port or hostname).

Unable to start Lync Platform connection. It has already been started or was terminated for an unknown reason.

The connection to the Lync serverwas either already established or was terminated for an unknown reason.


Unable to start Lync Platform connection. It was not possible to listen on the configured OCS Application Port (OCSApplicationPort). Verify that no other applications are using the port. (exception details)

Another application is using the TCP port configured as OCS Application Port.

Close the other program (may be determined by running "netstat -anb" on the server) or change the OCS Application Port configuration parameter. Note that changing the port requries a new GRUU to be created.

Unable to start Lync Platform connection. The platform startup operation completed unsuccessfully. (exception details)

Other reasons than the above cause the connection to the Lync serverto fail.


Unable to start up Lync Platform connection. Lync connection could not be established. (exception details)

The Lync connection could not be established


Error while shutting down Lync platform connection (exception details)

An error occured while closing the connection to the Lync server.


Invalid parameter while shutting down Lync platform connection (exception details)

An error occured while closing the connection to the Lync server.


RealTimeException creating Lync endpoint sipuri (exception details)

An error occured while establishing a SIP endpoint for the user defined with sipuri.




RealTimeException while publishing presence for sipuri (exception details)

An error occured while publishing presence for the user defined with sipuri.


ArgumentNullException while publishing presence for sipuri (exception details)



ArgumentException while publishing presence for sipuri (exception details)



XmlException while publishing presence for sipuri (exception details)



C.3.3 License errors


No license key or company configured. OCS MobileStatus will not start without license information.

The configuration does not contain either Company name or License key (or both)

Enter the Company name and License key in the configuration program

The license key is invalid. OCS MobileStatus will not start without valid license information

The license key does not match the company name

Verify the typing of the company name and license key in the configuration program. Use the test functionality of the configuration program to verify the input.

Unable to contact license server for more than two weeks. Shutting down.

OCS MobileStatus was never able to reach the online license service for longer than the grace period.

The server must be able to reach the address secure.mobileservices.dk using TCP port 443 (https) to validate the license and report user count.

Last contact with license server was date, which is more than two weeks. Shutting down.

OCS MobileStatus is no longer able to reach the license service.

The server must be able to reach the address secure.mobileservices.dk using TCP port 443 (https) to validate the license and report user count.

License is invalid. Shutting down OCS MobileStatus. (response)

The configured license is invalid. Verify the configured license. The response text may contain further information about the reason.


APPENDIX D. OCS MOBILESTATUS PROBLEMS

D.1 Missing prerequisites

D.1.1 UCMA Core missing

If you are running OCS MobileStatus which does not have the Lync Communications Server Unified

Communications Managed API Core (UCMA Core) files installed, the program will not start. The

event log message will contain the following information “Could not load file or assembly SIPEPS”.

To resolve the problem make sure that the prerequisites are installed correctly.

D.2 Active Directory communication

D.2.1 Not in a domain

The computer running OCS MobileStatus must be part of an Active Directory domain. It uses Active

Directory to retrieve users who have a telephone number and a SIP URI (ie. are enabled for Lync

Communications Server). If the computer running OCS MobileStatus is not part of a domain, an

event log message containing the following is logged: “The specified domain either does not exist

or could not be contacted”.

Resolve the problem by joining the computer to an Active Directory domain containing the users

for whom OCS MobileStatus should change presence.

D.3 Certificate problems

D.3.1 Missing local certificate

If the event log message contains information such as “Service cannot be started.

System.ArgumentNullException: Value cannot be null. Parameter name: certificate” the problem is

caused by either a missing local certificate or incorrect information in the LocalHostName or

CertificateSerialNumber configuration parameters.

OCS MobileStatus cannot communicate with the Lync Communications Server unless you have

installed a certificate which it can use. In some cases OCS MobileStatus cannot find the correct

certificate in the certificate store.

OCS MobileStatus cannot find a certificate if you do not have a certificate installed with the same

subject name as the configuration parameter LocalHostName, or you have configured a

CertificateSerialNumber which does not match any of the installed certificates.

It is required that the certificate has a private key.

To resolve the problem make sure that you have installed the correct certificate, and that:

The configuration parameter LocalHostName matches the subject name (or Subject

Alternate Name).


If you have configured the Certificate Serial Number parameter, that the certificate has the

given serial number.

D.3.2 Missing Certification Authority certificate

A TLS session cannot be established if the computer running OCS MobileStatus does not know the

certification authority which created the certificate used by the Lync Communications Server. This

will result in OCS MobileStatus stopping while trying to establish connection to the Lync

Communications Server to publish presence for a user. The failure in the event log will contain

information such as “The certificate chain was issued by an authority that is not trusted”.

This is normally only a problem if the computer running OCS MobileStatus is not in the same

domain as the computer running Lync Communications Server, or the certificate used on the Lync

Communications Server is using a self-signed certificate.

To resolve the problem install the certificate for the certification authority used to sign the Lync

Communications Server certificate on the computer running OCS MobileStatus.

D.3.3 Incorrect certificate used

If you have configured OCS MobileStatus to use an incorrect certificate, such as one with a

different DNS name than the server running OCS MobileStatus, you may get an error message

such as this: “RealTimeException creating Lync endpoint SIP URI”.

D.4 Office Communications Server timeouts

D.4.1 Incorrect GRUU

If OCS MobileStatus has been configured with an incorrect GRUU, the Office Communications

Server may not be able to send data to OCS MobileStatus.

This results in timeouts when OCS MobileStatus establishes endpoints to use for publishing user

presence in Lync Communications Server. To resolve the problem verify that the GRUU used is the

correct one, and that the application is provisioned within Active Directory.

D.4.2 Firewall configuration

The Lync Communications Server cannot send data to OCS MobileStatus if the firewall on the

computer running OCS MobileStatus is not configured to allow traffic to the TCP port set with the

OCSApplicationPort configuration parameter.

This results in timeouts when OCS MobileStatus establishes endpoints to use for publishing user

presence in Office Communications Server. To resolve the problem allow communications to the

port configured with the OCSApplicationPort parameter.

Also, if a firewall blocking the OCS MobileStatus server to contact the external license

management system for a 14 days, the server will stop processing mobile status updates.


D.5 Lync 2013 API bug


Unhandled Exception:

System.ArgumentException: The

xml representing the category

data is invalid. See inner exception

for details. --->

System.Xml.XmlException:

Possibly Bad Xml, Serializer failed

to deserialize the given object, see

inner exception. --->

System.InvalidOperationException:

There is an error in XML document

(1, 2). --->

System.InvalidOperationException:

The specified type was not

recognized:

name='presentingState',

Lync2013 API bug. Upgrade to newest Lync version or turn on registry setting to make the system ignore these errors.

There was a bug in ealier versions of the Lync Server 2013 API that OCS MobileStatus uses, and a

fix was released as a Lync 2013 Cumulative Update 2 in July 2013.

The bug is encountered if a Lync 2013 user changes status to “Presenting”. – This can be done in

Windows 8 if the user has two monitors, and configures the display output to be duplicated on the

two monitors.

It is not a presence state that the user can enter into manually in the Lync client.

Unfortunately the Lync 2013 Unified Communications Managed API (UCMA) 4.0 which OCS

MobileStatus uses, will trigger an error when it encounters that state. In the default configuration of

OCS MobileStatus, the software will treat it as a fatal error, and shut down.

The problem can be solved by upgrading Lync2013 to Microsoft’s Lync 2013 Cumulative update 2

that was released in July 2013, or newer.

The Microsoft update is described here:

http://support.microsoft.com/kb/2809243.

http://support.microsoft.com/kb/2809243


D.6 Summary of error messages

The table below summarizes the miscellaneous error messages the OCS MobileStatus server logs

to the Windows application event log, a short description of the problem and a reference to the

relevant above subchapter addressing this problem.

Error message Reference

Could not load file or assembly SIPEPS D.1.1 UCMA Core missing

The specified domain either does not exist or

could not be contacted

D.2.1 Not in a domain

Service cannot be started.

System.ArgumentNullException: Value cannot

be null. Parameter name: certificate

D.3.1 Missing local certificate

The certificate chain was issued by an

authority that is not trusted

D.3.2 Missing Certification Authority certificate

RealTimeException creating OCS endpoint SIP

URI

D.3.3 Incorrect certificate used

System.InvalidOperationException: The

specified type was not recognized:

name='presentingState'

D.5 Lync 2013 API bug


APPENDIX E. OCS MOBILESTATUS LOG CONFIGURATION

By default OCS MobileStatus will log to a text file in the installation folder. The log file will rotate

once when it reaches a size of 100 MB. This means that no more than 200 MB of log files will be

stored.

The log file is useful for product support in case of problems, but during normal operation it is not

necessary to analyze the log file.

The log file size and format as well as rotation can be configured. Since this is an advanced

trouble-shooting step, there is no configuration for the log file options. However, it is possible to

change the settings using the Windows Registry Editor.

The logging configuration is read by OCS MobileStatus from the value called LogConfiguration

in the registry key is HKEY_LOCAL_MACHINE\Software\BluePosition\OCS MobileStatus.

The default setting is:

The table below specifies the possible parameter options, their default values and descriptions.

Option Default Value Description

append true Specifies if new log messages should be appended to the log file

instead of overwriting the file first.

buffer 0 Specifies the I/O buffer size in kilobytes. It is possible to specify size

units like this: "1 MB". Supported units are "KB", "MB" and "GB". A value

of 0 disables this feature. Enabling the I/O buffering greatly improves

the logging performance but has the disadvantage that log messages

are temporarily stored in memory and are not immediately written to

disk.

filename ocsmobilestatus.log Specifies the filename of the log file.

indent false Indicates if the logging output should automatically be indented.

maxparts 2 Specifies the maximum amount of log files at any given time when log

rotating is enabled or the maxsize option is set. Specify 0 for no limit.

See below for information on the default value for this option.

maxsize 102400 Specifies the maximum size of a log file in kilobytes. When this size is

reached, a backup of the log file is created and the original file is reset.

It is possible to specify size units like this: "1 MB". Supported units are

"KB", "MB" and "GB". A value of 0 disables this feature.

rotate None Specifies the rotate mode for log files. Please see below for a list of

available values. A value of "none" disables this feature.

text(append="true", filename="ocsmobilestatus.log", maxparts="2", maxsize="102400")


The append option specifies if new log messages should be appended to the destination file

instead of overwriting the file. The default value of this option is "true".

The rotate option specifies the date log rotate mode. When this option is used, the filename of the

resulting log consists of the value of the filename option and an appended time stamp (the used

time stamp format thereby is "yyyy-MM-dd-HH-mm-ss"). To avoid problems with daylight saving

time or time zone changes, the time stamp is always in UTC (Coordinated Universal Time). The

following table lists the available rotate modes together with a short description.

Rotate Mode Description

None Rotating is disabled

Hourly Rotate hourly

Daily Rotate daily

Weekly Rotate weekly

Monthly Rotate monthly

telenor samordnet kommunikasjon samordnet mobilstatus for microsoft...

Documents