We began our tour last time with a look at what you can do on the Plivo console to monitor and manage our SMS API. The series continues here with a similar survey for our Voice API.
The Voice menu overview
To get to the Voice menu, visit the Plivo console and click on the second icon.
The console displays the Voice Overview page, which shows some basic usage information.
Moving to the next menu item takes you to the Advanced Insights page. It shows information that can help you identify call quality issues so you can fix them quickly.
XML and PHLO applications
The next menu choice brings you to a list of the Plivo XML applications and PHLOs associated with your account. In Plivo parlance, an application is a set of answer, hangup, and message URLs that you use to control what happens to your incoming calls and messages, while our PHLO visual workflow design tool lets you build applications graphically. Clicking on an application name brings you to a screen of details about the application.
The entries in the Voice section of this page define URLs the application looks at in the event of an incoming call to that number or when the call is hung up. Upon receipt of an incoming call Plivo makes a synchronous HTTP request to your application using the URL specified in the Primary Answer URL field. The API expects an XML document in response. Plivo also sends a few parameters with the HTTP request that your application can act upon before responding.
If there were a URL specified for messaging it would work the same way. You can read more about the process in our documentation.
The next menu choice is Endpoints, which displays a list of SIP endpoints associated with your account. A SIP endpoint can be any IP phone, mobile phone, wireless device, or PC that uses Session Initiation Protocol (SIP) to perform communications operations.
Click on the Logs submenu to bring up the Voice log: a list of every voice API URL call made, which you can filter a number of ways or export for analysis elsewhere.
When you click on a call entry on the log page, you can see details about the call.
That’s a ton of information about the call itself — and if that doesn’t tell you enough, well, there’s more. A note in the last box on the page directs you to the call debug log entries. The debug log contains details for all callbacks that Plivo sends.
With all the information in the logs you should be able to understand any issues you encounter. (But if you need help, our support team is always here for you.)
In addition to call logs, we give you access to recording and transcription logs.
If you click on an item in the log, you can see details about that item.
The final group of menu items falls under the category of Settings. The first setting entry determines whether to use Call Insights. Because the feature is still in beta and therefore free to everyone, it’s enabled by default.
The Push Credentials screen lets you store the credentials you need if you’re working with Plivo’s iOS SDK or Android SDK. Once you have credentials issued by Apple and Google you can enter them here.
Geo Permissions can help you protect your account from fraud by restricting the set of countries your account can call. Get more information from our documentation.
Finally, Other Settings lets you enable destination number validation (which can give you better delivery rates and cost savings from not sending messages to numbers that are incapable of accepting them), enable HTTP Basic Auth on all GET recording media requests for enhanced security, and providing consent for Plivo to store and have access to logs and media packet capture files.
All about the console
That’s our quick tour of the Voice menus. To dig deeper, visit your console page and see what your data looks like. Also check out our other console tours of the SMS, Zentrunk, Number Lookup, and Phone Numbers menus. If you have any questions, you can find the answers in our documentation or on our support portal.