The following table lists Office Communications Server events
that are related to outbound routing.

Table 9. Outbound routing events

Event ID

Description

Cause and Resolution

46001

The Outbound Routing Application is starting.

46002

The Outbound Routing Application was started.

46003

The Outbound Routing Application is stopping.

46004

The Outbound Routing Application was stopped.

46005

Unexpected exception occurred in the Outbound Routing
Application.

46006

Outbound Routing Application is running under an account that is
not authorized to connect to the server.

46007

Unable to load the application manifest file from the
installation directory.

CAUSE: The file has been deleted, or the service account does
not have permission to read from the installation directory, or the
file is corrupted.

RESOLUTION: Verify that the file exists. If it does not,
reinstall the program. If it does exist, verify that the service
account has permission to read the file. If the service account has
read permission on the file, then it is corrupted, and you should
reinstall the program.

46008

Unable to compile the application manifest file from the
installation directory.

CAUSE: The file is corrupted and contains errors.

RESOLUTION: Reinstall $(SERVER_PRODUCT_GENERICNAME_STR).

46009

An attempt to route to a gateway failed.

CAUSE: Could not route to Gateway <gateway_name>, the
attempt failed with response code: <response_code>. Failure
occurrences: <number_of_failures>, since
<date/time>.

RESOLUTION: Verify that the specified gateway is running and is
properly configured.

46010

An attempt to route to the following Gateway
<gateway_name> succeeded. Any previous errors have been
resolved.

46011

This phone usage, and any routes which reference it, will not be
used.

CAUSE: The phone usage contains one or more invalid field
values.

46012

These two phone usages, and any routes which reference them,
will not be used.

CAUSE: Two phone usages contain identical attribute name field
values.

46013

These two phone usages, and any routes which reference them,
will not be used.

CAUSE: Two phone usages contain identical distinguished name
field values.

46014

This route will not be used.

CAUSE: This route contains an invalid value.

RESOLUTION: Use a valid value for the route.

46015

These routes will not be used.

CAUSE: These two routes contain identical names.

RESOLUTION: Rename one of the routes.

46016

This phone usage is unknown. It will not be used.

CAUSE: A phone route references a phone usage that is not
valid.

46017

This phone route has an empty gateway list.

46018

All configuration data was successfully loaded.

46019

All configuration data was loaded, but some bad data was
detected and will not be used.

46020

An unexpected exception occurred while loading configuration
data.

46021

Unable to load settings from configuration file.

CAUSE: The OutboundRouting application is incorrectly installed,
or its configuration file has been incorrectly modified.

RESOLUTION: Verify that the OutboundRouting.exe.config file
exists in the installation directory and verify the settings.

46022

Unable to parse user UC policy.

RESOLUTION: Verify that the user UC policy is valid.

46023

A UC Policy contains an unknown phone route usage.

46024

The outbound routing app was disabled.

46025

The outbound routing app was enabled.

46026

A PBX gateway has been marked as down.

RESOLUTION: Verify that the gateway is running and that it can
respond to calls.

46027

A PBX gateway is now responding to requests after some
failures.

46028

Unexpected exception occurred while processing a request. This
event will only be reported every 15 minutes even if more
exceptions are encountered.

46029

Unexpected exception occurred while processing a response. This
event will only be reported every 15 minutes even if more
exceptions are encountered.