Objective
Provide clear guidance on updating your server code so that applications using the OpenTok can migrate smoothly to the Unified environment.
Applies To
- Video API
- Migrate from OpenTok to Unified
- Server SDK
Procedure
1. Each Server SDK has its own migration guide. Please follow the guide for your SDK when updating your code:
- Node Migration Guide
- Java Migration Guide
- .NET Migration Guide
- Python Migration Guide
- PHP Migration Guide
- Ruby Migration Guide
2. After applying the changes from the migration guide for your SDK, confirm that your integration works correctly by testing the following:
- Create a Session successfully using Unified credentials.
- Generate a Token for the Session and verify it is valid.
Additional Information
In addition to the migration guides, you may find the following resources useful for development and troubleshooting:
- Node: Developer Guide, Reference, Release Note
- Java: Developer Guide, Reference, Release Note
- .NET: Developer Guide, Release Note
- Python: Developer Guide, Release Note
- PHP: Developer Guide, Release Note
- Ruby: Developer Guide, Reference, Release Note
Articles in this section
- Migrating Video REST API from OpenTok to Unified
- Video Client SDK Changes from OpenTok to Unified
- How to Migrate from OpenTok Server SDK to Unified Server SDK
- Credential Differences Between OpenTok and Unified Environments
- In which Regional Media Zones can I use Experience Composer?
- How do I monitor Video API call quality in real-time?
- JWT Tokens in the TokBox and Unified Environments
- Android SDK 2.28.2 error when using the application context
- What happens if your session lasts more than 8 hours?
- Updates to using the Vonage Media Library in Native SDKs from version 2.27.x onwards