If the Boxer application sends a request to the ENS, the ENS processes the request and sends a response with a response code and message to the Boxer application.

The following table lists all the response codes and messages in the Boxer application logs and the ENS logs.

Response Code Message Description
14 SubscribeAgain

If a subscription failed, then the ENS sends a subscribe again message to the Boxer application.

8

ErrorSubscribeOrUpdateDb

When you try to add a user or device details to the database during subscription, you might receive this error .

23

UnAuthorizedRequest

Authentication failed (API token mismatch) for the request from the Boxer application.

32 Failed (Handled Exception)

Registration failed with a handled exception. For example, the URL is not in the correct format.

17

Success

Indicates that the registration is successful.
3 UpdateSuccess

The Boxer application receives this response when the:

  • Get the Public Key request is successful and the database is updated accordingly.
  • The synchronization key for the user success and the database is updated accordingly.
  • Any device details updated in database, such as, update device token is successful.
4 UpdateFail ENS sends this response for multiple reasons. When you receive this response, verify the corresponding ENS logs and troubleshoot based on the message in the logs.
5

TokenDoesNotExists

ENS sends this response when the device record is absent.

When you send a force register, (by changing the notification sound in the Boxer application setting) a new device is created on the ENS server.

6

UserAlreadySubscribed

ENS sends this response when a user is already subscribed on the ENS server.

7

UserSubscribed

User subscription is successful.

9

NoRecordExists

ENS sends this response when a user record is absent.

When you send a force register, (by changing the notification sound in the Boxer application setting) a new user is created on the ENS server.

15

UserSubscribedNotUpdatedInDb

User subscribed but failed to add device details in the database. In this case, ensure that the connection from the ENS to the database is working correctly or the user has permission to update the database.

16

FailedToGetEwsUrlFromAutoDiscovery

Unable to determine the Exchange version after autodiscovery.

21

EmailFetchfailed

Fetching email information from the EWS failed.

24 DeviceUnregisteredUserUnsubscribed

Unsubscribe successful and the user is unregistered.

25

DeviceUnregistered

The device is deleted from the database.

26

DeviceNotRegistered

The device is not registered.

28

UserSubscriptionNotFound

User record does not exist.

29

UserRecordPresentNotSubscribed

User records are present but not subscribed.

30

SubscribedNeedsUpdate

User has already subscribed and must be added to the database.

34

InvalidDecryptedPayload

Payload is encrypted with a wrong public key.

35

EWSUrlMismatch

Unsubscribing with the wrong EWS URL. The EWSUrl for the register request and Exchange service is not the same.

36

InvalidAuthType

Indicates the invalid authentication type.

Troubleshooting ENS with On-Premise Exchange Server

This section describes the steps to confirm that the client certificate is available at the Exchange endpoint. When a customer is using ENS with on-premise Exchange and certificate-based authentication (CBA) enabled, you must confirm that the client certificate is appearing at the Exchange endpoint. Traffic might reach the Exchange CAPI2 logs before the traffic reaches the Exchange IIS.

Cause: The CAPI2 logs are part of the Event Viewer. You can check the CIAP2 logs to confirm whether the client certificate appeared on the Exchange server. The devices are set up to check the client certificate for any SSL sessions for security issue. In this case, the client certificate must authenticate the user.

  1. Enable CAPI2 logs in the Event Viewer.
  2. Confirm that the client certificate is appearing correctly.

In the Event Viewer, ensure the extended usage has client authentication listed, check if the root certificate and certificate chain are valid.

Note: The following images are for example only, the actual information might be different.

Click on the log line and open up the certificate details as shown in the following image. Ensure the ExtendedKeyUsage has Client Authentication listed.

Check if the root certificate and the certificate chain is valid.

Ensure the certificate is not revoked.