How to Migrate Your .NET Voice Application from Twilio to Plivo

21 Dec 2021

Migrating from Twilio to Plivo is a seamless and painless process. The two companies’ API structures, implementation mechanisms, XML structure, SMS message processing, and voice call processing are similar. We wrote this technical comparison between Twilio and Plivo APIs so that you can scope the code changes for a seamless migration.

Understanding the differences between Twilio and Plivo development

Most of the APIs and features that are available on Twilio are also available on Plivo and the implementation mechanism is easier as the steps involved are almost identical. This table gives a side-side comparison of the two companies’ features and APIs. An added advantage with Plivo is that not only can you code using the old familiar API/XML method, you can also implement your use cases using PHLO (Plivo High Level Objects), a visual workflow builder that lets you create workflows by dragging and dropping components onto a canvas — no coding required.

Features and APIs	Twilio	Plivo	Similarities	Implementation Interface
Voice API: Make phone calls	✅	✅	Request and response variables’ structure	API PHLO
Programmatically manage call flows	Twiml	Plivo XML	XML element and its attributes structure	XML PHLO
Geo Permissions	✅	✅	Feature parity	Console
Number Lookup API	✅	✅	API Parity	API
Phone number management	✅	✅	Feature parity	API Console
Call Insights	✅	✅	Feature parity	Console
Validating Requests	✅	✅	Feature parity	API XML
Subaccounts	✅	✅	Feature parity	API
Speech recognition	✅	✅	Feature parity	XML
SSML (Speech Synthesis Markup Language)	✅	✅	Feature parity	XML PHLO
Browser and Mobile SDKs	✅	✅	Feature parity	Browser Android iOS
Transcription	✅	✅	Feature parity	API XML PHLO
Custom SIP Headers	✅	✅	Feature parity	API XML PHLO Browser SDK Mobile SDKs
HTTP callbacks	✅	✅	Feature parity	API XML PHLO

Plivo account creation

Start by signing up for a free trial account that you can use to experiment with and learn about our services. The free trial account comes with free credits, and you can add more as you go along. You can also add a phone number to your account to start testing the full range of our voice and SMS features. A page in our support portal walks you through the signup process.

You can also port your numbers from Twilio to Plivo, as we explain in this guide.

Migrating your voice application

As mentioned earlier, you can migrate your existing application from Twilio to Plivo by refactoring the code, or you can try our intuitive visual workflow builder PHLO. If you prefer the API approach, you can follow one of the voice quickstart guides based on your preferred language and web framework. Plivo offers server SDKs in seven languages: Python, Node.js, .NET, Java, Python, Ruby, and Go. For another alternative that lets you evaluate Plivo’s SMS APIs and their request and response structure, use our Postman collections.

How to make an outbound call

Let’s take a look at the process of refactoring the code to migrate your app from Twilio to Plivo to set up a simple .NET application to make an outbound call by changing just a few lines of code.

Twilio Plivo

using System;
using Twilio;
using Twilio.Rest.Api.V2010.Account;


class Program
{
    static void Main(string[] args)
    {
        string accountSid = Environment.GetEnvironmentVariable("TWILIO_ACCOUNT_SID");
        string authToken = Environment.GetEnvironmentVariable("TWILIO_AUTH_TOKEN");

        TwilioClient.Init(accountSid, authToken);
    
        var call = CallResource.Create(
            url: new Uri("http://demo.twilio.com/docs/classic.mp3"),
            to: new Twilio.Types.PhoneNumber("+14155551212"),
            from: new Twilio.Types.PhoneNumber("+14155551212")
        );
        Console.WriteLine(call.Sid);
    }
}

using System;
using System.Collections.Generic;
using Plivo;
using Plivo.Exception;

namespace PlivoExamples
{
    internal class Program
    {
        public static void Main(string[] args)
        {
           string authId = Environment.GetEnvironmentVariable("PLIVO_AUTH_ID");
           string authToken = Environment.GetEnvironmentVariable("PLIVO_AUTH_TOKEN");
            var api = new PlivoApi(authId,authToken);
            try
            {
                var response = api.Call.Create(
                    to:new List<String>{"+15671234567"},
                    from:"+14151234567",
                    answerMethod:"GET",
                    answerUrl:"https://s3.amazonaws.com/static.plivo.com/answer.xml"
                );
                Console.WriteLine(response);
            }
            catch (PlivoRestException e)
            {
                Console.WriteLine("Exception: " + e.Message);
            }
        }
    }
}

Alternatively, you can implement the same functionality using one of our PHLO templates. For example, if you want to make an outbound call, your PHLO would be this:

Create a PHLO for outbound calls

How to receive an incoming call

You can migrate an application for receiving and handling an incoming call from Twilio to Plivo just as seamlessly, as in this example:

Twilio Plivo

using System.Web.Mvc;
using Twilio.AspNet.Mvc;
using Twilio.TwiML;

public class VoiceController : TwilioController
{
    [HttpPost]
    public ActionResult Index()
    {
        var response = new VoiceResponse();
        response.Say("hello world!", voice: "alice");

        return TwiML(response);
    }
}

using System;
using Plivo.XML;
using System.Collections.Generic;
using Microsoft.AspNetCore.Mvc;

namespace Receivecall
{
    public class ReceivecallController : Controller
    {
      public IActionResult Index()
      {
         Plivo.XML.Response resp = new Plivo.XML.Response();
         resp.AddSpeak("Hello, you just received your first call",
         new Dictionary<string, string>() 
            {
                  {"loop","3"}
            });
         var output = resp.ToString();
         Console.WriteLine(output);
         return this.Content(output, "text/xml");
        }
    }
}

Here again, you can implement the same functionality using one of our PHLO templates. Your PHLO would look like:

Create a PHLO to receive incoming call

For more information about migrating your Voice applications to Plivo, check out our detailed use case guides, available for all seven programming languages and PHLO.

How to forward an incoming call

You can migrate an application for forwarding an incoming call from Twilio to Plivo just as seamlessly, as in this example:

Twilio Plivo

using System.Web.Mvc;
using Twilio.AspNet.Mvc;
using Twilio.TwiML;

public class VoiceController : TwilioController
{
    [HttpPost]
    public ActionResult Index()
    {
        var response = new VoiceResponse();
        response.Dial("415-123-4567");
        response.Say("Goodbye");

        return TwiML(response);
    }
}

using System;
using Plivo.XML;
using System.Collections.Generic;
using Microsoft.AspNetCore.Mvc;

namespace Receivecall
{
	public class ForwardcallController : Controller
	{
		public IActionResult Index()
		{
		Plivo.XML.Response resp = new Plivo.XML.Response();
		Plivo.XML.Dial dial = new Plivo.XML.Dial(new
		Dictionary<string, string>() {
		});

		dial.AddNumber("+15671234567",
			new Dictionary<string, string>() { });
		resp.Add(dial);
	
		var output = resp.ToString();
		Console.WriteLine(output);
	
		return this.Content(output, "text/xml");
		}
	}
}

Here again, you can implement the same functionality using one of our PHLO templates. Your PHLO would look like:

Create a PHLO to receive incoming call

For more information about migrating your Voice applications to Plivo, check out our detailed use case guides, available for all seven programming languages and PHLO.

More use cases

You can migrate your applications serving other use cases too.

Simple and reliable

And that’s all there is to migrating your .NET voice app from Twilio to Plivo. Our simple APIs work in tandem with our Premium Communications Network. See for yourself — sign up for a free trial account.