Set Up a Go Dev Environment for Voice Calls

This guide shows how to set up a development environment in five minutes to trigger API requests and start serving Plivo XML to control your call flow. It also shows how to test your code using tunneling software to expose the local dev server to the public internet.

Install Go, Gin, and the Plivo Go SDK

To get started, install and set up Go, the Gin web framework, and Plivo’s Go SDK.

You can install Go from the official installer. To set up the other packages, first create a project directory using the command mkdir mygoapp, then change to that directory and install the Gin and Plivo packages using the go command.

go get github.com/gin-gonic/gin
go get github.com/plivo/plivo-go/v7

Alternatively, you can install them by cloning the Plivo Go repository and Gin repository into your GOPATH.

Trigger an API request

Now you can create a file in the project directory and execute code to trigger any Plivo API. Here’s some example code that makes an outbound call. Create a file called MakeCall.go and paste into it this code.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
package main

import (
	"fmt"

	"github.com/gin-gonic/gin"
	"github.com/plivo/plivo-go/v7"
)

func main() {
	r := gin.Default()
	r.GET("/outbound-call", func(c *gin.Context) {
		c.Header("Content-Type", "application/JSON")
		client, err := plivo.NewClient("<auth_id>", "<auth_token>", &plivo.ClientOptions{})
		if err != nil {
			fmt.Print("Error", err.Error())
			return
		}
		response, err := client.Calls.Create(
			plivo.CallCreateParams{
				From:         "<Caller_ID>",
				To:           "<Destination_Number>",
				AnswerURL:    "http://s3.amazonaws.com/static.plivo.com/answer.xml",
				AnswerMethod: "GET",
			},
		)
		if err != nil {
			fmt.Print("Error", err.Error())
			return
		}
		fmt.Printf("Response: %#v\n", response)
		c.JSON(200, response)
	})
	r.Run() // listen and serve on 0.0.0.0:8080 (for windows "localhost:8080")
}
Note:
  • Replace the placeholders <auth_id> and <auth_token> with your authentication credentials, which you can find on the overview page of the Plivo console.
  • We recommend that you store your credentials in the auth_id and auth_token environment variables to avoid the possibility of accidentally committing them to source control. If you do this, you can initialize the client with no arguments and it will automatically fetch the values from the environment variables.
  • You can use os.Setenv and os.Getenv function to store environment variables and fetch them while initializing the client.
  • Replace the placeholder <Caller_ID> with a phone number you’ve purchased, and <Destination_Number> with the phone number you’ll be calling. Both phone numbers should be in E.164 format.
  • <Destination_Number> can also be a SIP endpoint. If you’re calling a SIP endpoint, the <Destination_Number> placeholder should be a valid SIP URI. Example: sip:john1234@phone.plivo.com

Save the file and run it.

go run MakeCall.go

You can follow the same approach to trigger other API requests. Refer to our detailed API reference to see all the API requests available on the Voice API platform.

Serve an XML document and manage callbacks

When you receive a call on a Plivo voice-enabled number, you can control the call flow by declaring an Answer URL for the Plivo application associated with that phone number. Plivo will invoke the Answer URL specified and expect a valid XML response to handle the call.

Note: You can use Answer URLs with both outbound API calls and inbound calls. In the outbound API call example above, we specified the Answer URL along with the Make Call API request; for incoming calls, you’d specify the Answer URL in the Plivo application associated with the phone number.

In addition to requests to the Answer URL, Plivo initiates other HTTP requests to your application server based on specific XML elements in your Answer XML document. Such requests are broadly classified into two categories:

Action URL requests: These requests are typically invoked at the end of an XML element’s execution, and the server expects XML instructions to carry forward the call in response to these requests. This happens, for example, when a caller provides Touch-Tone input during GetInput XML execution.

Callback URL requests: These requests serve as webhooks to pass the application server information about events through the course of an XML element’s execution, such as when a conference participant is muted or unmuted. No XML instructions are expected in response to these requests.

Set up a Go Gin-Gonic server to serve XML and manage callbacks

Here’s how to set up a Go server to serve XML documents and manage callbacks.

Use this code snippet to start a local server.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
package main

import (
	"github.com/gin-gonic/gin"
	"github.com/plivo/plivo-go/v7/xml"
)

func main() {
	r := gin.Default()
	r.GET("/receive_call", func(c *gin.Context) {
		c.Header("Content-Type", "application/xml")
		response := xml.ResponseElement{
			Contents: []interface{}{
				new(xml.SpeakElement).
					AddSpeak("Hello, you just received your first call", "MAN", "en-US", 1),
			},
		}
		c.String(200, response.String())
		r.Run() // listen and serve on 0.0.0.0:8080 (for windows "localhost:8080")
}

Save this code in any file — we called ours receive_call.go. To run this file on the server, go to the folder where the file resides and enter:

 go run receive_call.go

You should see your basic server app in action on http://localhost:8080/receive_call/.

Ngrok setup

To serve XML documents, your local server must connect with Plivo API services. For that, we recommend using ngrok, which exposes local servers running behind NATs and firewalls to the public internet over secure tunnels. Using ngrok, you can set webhooks that can talk to the Plivo server.

ngrok block diagram

Install ngrok and run it on the command line, specifying the port that hosts the application on which you want to receive messages (8080 in this case):

./ngrok http 8080

This starts the ngrok server on your local server. Ngrok will display a forwarding link that you can use as a webhook to access your local server over the public network. You should be able to see your basic server application in action at https://<nrgok_URL>/receive_call/.

Sample ngrok CLI

You can follow the same approach to serve other XML documents to manage call flows. Refer to our detailed XML reference to see all the XML elements available on the Voice API platform.