January 2023 Summaries

We recently redesigned our key build and deployment pipeline to support our Vonage Contact Center platform using a GitOps design that moves away from traditional DevOps methods. GitOps is a collaboration of best practices from DevOps and Security, focusing on Infrastructure as Code (IaC), Pull Requests (PRs), and Continuous Integration / Continuous Delivery (CI/CD) processes. We implemented a security-compliant pipeline that adheres to the principles of Least Privilege and Separation of Duties, providing timely deployment feedback to developers while reducing deployment friction and improving DevEx. Our architecture involves three distinct steps: processing GitHub repository_dispatch events, accepting or rejecting updates, and deploying applications. We created a CLI tool for seamless cloud infrastructure deployments and an in-house CI/CD framework to support Micro-FrontEnd projects, enhancing the developer experience and aiding in migrating existing components to the new pipeline.

This article guides developers in integrating the Vonage Voice API and OpenAI API to create an application that receives a prompt from a user via phone call, sends it to a generative AI service, and then sends a response back to the user with the Vonage Messages API. The application uses GitHub Codespaces for deployment and can be customized by editing the starter code provided in the repository. To get started, developers need to create a new Vonage app, generate an API key and private key, and install the necessary dependencies using npm and Vonage CLI. They also need to configure the OpenAI API, which includes generating an API key and setting up the Images API to generate images based on user prompts. The application uses the Nexmo Call Control Object (NCCO) to interact with the Vonage Voice API and the Vonage Messages API to send messages over WhatsApp. Once deployed, developers can test the application by calling a linked phone number and sending a message to receive a response from the bot.

Vonage has introduced Silent Authentication as part of its Verify API, a recent development in personal authentication workflows that uses mobile phone SIMs to verify identities. This method removes the need for One-Time Passwords (OTPs) sent via SMS, reducing annoyance and increasing user flow resistance. Security benefits include reduced phishing threats by moving authentication directly between carrier and mobile device. However, limitations exist, such as requiring a mobile device with cellular data enabled, which can be a blocker in some cases. The Silent Authentication workflow involves starting the process with a call to start the verification, followed by a series of redirects to complete the request, and finally sending the code to be checked. Successful completion results in a seamless user experience, marking the start of a series of products from Vonage this year.

Vonage has introduced Silent Authentication to its Verify API, a new method of personal authentication that uses a mobile phone's SIM for identity verification, reducing the reliance on One-Time Passwords (OTPs). This approach streamlines user authentication processes, particularly for e-commerce platforms, by eliminating additional steps such as OTPs, which can deter user engagement. Silent Authentication enhances security by moving authentication directly between the carrier and the mobile device, thereby reducing the risk of phishing attacks. However, it is not without limitations, as it requires a mobile device with cellular data, which may not be universally accessible. While the implementation process involves several steps for developers, it ultimately offers users a seamless login experience. Vonage is currently offering this feature in its Alpha phase, with more products expected to follow in 2023.

The Vonage Developer Relations team concluded their year with a successful apidays conference in Paris, attracting 1700 attendees. The event featured various sessions and activities, including a workshop by Benjamin Aronov on AI Studio, a networking party hosted by Benjamin with special guest Arnaud Lauret discussing API best practices, and a live demo by Guillaume Faas on Video APIs. Vonage also held a festive photo competition as part of their 10th Anniversary Soiree, which concluded with the winner being Tad. The event was a great opportunity for developers to connect and learn about Vonage APIs, and the team looks forward to more events in 2023.

The Vonage Voice API allows for easy integration with ASP.NET applications, enabling features such as making and receiving phone calls. To set up this functionality, developers must create a Vonage application, generate public and private keys, and configure their ASP.NET project in Visual Studio. The `appsettings.json` file is used to store sensitive information like the Application ID and Private Key path. A new controller called VoiceController is created to handle business logic for making a Text-to-Speech phone call, which uses the VonageClient to create a call with specified endpoints and credentials. Once set up, developers can run the app and make a successful Text-to-Speech phone call.

The Vonage DevRel team has been working hard on new projects, releases, and content for the upcoming year of 2023. The team launched several new features, including a Firebase extension that allows users to add video chat to their applications quickly and easily, as well as a Background Blur API that enables users to blur or replace their background in real-time. Additionally, the Vonage Node SDK v3.0.0 was released, featuring improved code organization and parameter objects instead of function callbacks. The team also introduced a Laravel Vonage Helpdesk application that allows customers to contact businesses across multiple channels. The DevRel team invites developers to join their pilot developer advisory board and is open to feedback on future projects.

Virtual meetings have a different vibe from in-person meetings due to the need for a shared environment, which can distract participants and affect their privacy during video calls. To address this, solutions like background blurring or replacing it with another image can be applied to reduce distractions and maintain participants' natural backgrounds. Both of these solutions can be easily implemented using OpenTok's API in Vonage Video applications by adding just a few lines of code. The tutorial guides users through the process of setting up their project, initializing the session and publisher objects, applying filters, and clearing video effects. With this solution, users can customize the appearance of their application and build further logic into their production application.