Question
If my application server goes down, will the callback events be retried?
Applies To
- Vonage Video API
- Session Monitoring
Answer
For Unified environment or when using secure callback feature is enabled
Our service will use a retry and backoff policy to try and deliver any individual callback (e.g. archiveStopped, archiveAvailable, etc) of any type (Session Monitoring, Archiving, SIP, or Experience Composer) for up to 24hr. After 24hrs, the individual callback retry logic will stop and the individual callback event will no longer be sent. The retry logic strategy, is based on exponential backoff (the wait doubles before each retry).
The initial backoff retry is 5 seconds and then time between retries doubles each time increase to every 15 min until 24hours is reached.
-
- initial_back_off: 5 seconds
- max_back_off: 15 minutes
- max_retry_time: 24 hours
For Tokbox environment (not using secure callback feature)
We will retry 4 times for each event that we fail to deliver to the application server. If the platform detects 50 delivery failures within a 30 minutes time frame, the event forwarding will be disabled. A notification email is sent to the customer. To re-enable event forwarding, the callback URL must be configured again via the Vonage Video API account Portal.
Additional Information
- To configure session monitoring, please refer to our article How to configure the Session Monitoring Callbacks
- To know which environment you are using please refer to our article How-to-recognize-if-I-m-using-Vonage-Video-API-Unified-Environment-or-Vonage-Video-API-OpenTok-environment
Articles in this section
- Identifying the source of events in Vonage Video Session Monitoring
- What is Session Monitoring?
- How to Configure Session Monitoring Callbacks
- What can callback events be used for?
- Is Session monitoring real-time?
- Do you guarantee the callback event delivery?
- What happens to the callback events if my application server goes down?
- How can I test that the Callback URL is working?