Delivery Failure Notification

Last Updated : Oct 25, 2021 |

Avaya Oceana® may undergo outages or maintenance windows longer than 15 minutes. The users who message the contact center during an outage period may be unaware that the message has not been delivered to the Contact Center.

The Delivery Failure Notification feature provides automatic configurable notification to the users that the message has not been processed and to retry again later. The system notifies the users with a message similar to the following:

Unfortunately the system is unavailable at the moment. Please try your message again later.

You can modify the notification in the deployment excel file.

The users are also notified that the messages sent to the Contact Center are not processed if Avaya Oceana® has reached the maximum capacity. In this scenario, the system notifies the users with a message similar to the following:

Unfortunately the system is busy at the moment. Please try your message again later.

You can modify the notification in the deployment excel file.

Important:

This feature does not need any configuration. Defaulted messages are in place for both the system busy and system unavailable scenarios. You can modify the default messages in the deployment excel file.

Operation

The Messaging Connector specifies if it is currently receiving messages UP or not Down. When the status is UP, normal message processing continues. If the status is DOWN, a configurable notification is sent to the users notifying them that the message has not been processed and to retry again later.

Scenario

Operation

Avaya Oceana® planned or unplanned reboot - Messaging Connector not impacted

The Messaging Connector monitors the status of Avaya Oceana®. The endpoint is notified to set the application in a DOWN state. New messages beyond that time, receive the configured delivery failure message.

Upon Avaya Oceana® recovery, the Messaging Connector sets the application to an UP state using the endpoint. Further messages after this point do not receive the delivery failure notification.

Avaya Oceana® planned or unplanned reboot - Messaging Connector rebooted

A timing issue may occur. If the Messaging Connector is rebooted first OR both Avaya Oceana® and the Messaging Connector are rebooted at the same time, the status of the application cannot be updated to DOWN, therefore delivery failure messages are not sent.

Disaster recovery failover - Avaya Oceana® and Messaging Connector

Not Supported.

Network Outages

If a network failure occurs between the Messaging Connector and Avaya Oceana®, the Messaging Connector detects this outage and updates the application status to DOWN which resets on recovery.

Where the network outage isolates the Messaging Connector from being able to communicate with Avaya Oceana®, the status cannot be set to DOWN and therefore no delivery failure message is sent to the user.

System Busy

When Avaya Oceana® reaches maximum capacity and new messages arrive, one of the following can occur:
  • The new message is part of an existing conversation that is in queue or open with an agent. The message is processed as no new chatroom needs to be created.

  • The new message does not have an existing conversation open or in queue. A new chatroom is necessary but Avaya Oceana® does not have the capacity to create this. Therefore, a system busy message is sent to the user notifying them to retry later.

Limitations

  • The user message is retried by the application for up to 15 minutes. Therefore, if the system recovers and the Messaging Connector is in an UP status within 15 minutes of the user sending the message, the retried message may be received even though the user has received a delivery failure notification.

  • The user continues to see the failed message in their transcript history on the social messaging application. However, the failed message is not visible to the agent.

  • During complete outage of the messaging component, for example, power outage, it is not possible to set the status to DOWN, therefore users do not receive the delivery failure notification message.