Skip to main content

Voice test plan

Use this plan to validate your voice setup on the Bandwidth Universal Platform before sending live traffic. Test everything you plan to use in production. The items below cover the most common cases, but if your traffic uses something not listed here, test it anyway and let your Implementation specialist know.

Before you begin

  • Numbers are assigned to a Voice Configuration Package (VCP). Numbers without a VCP are not active for voice.

  • Services are activated on your numbers (Inbound, Outbound National, and Outbound International as applicable).

  • Your VCP route plan reflects your production design, including failover routes.

  • Bandwidth's signaling and media IPs are allowed through your firewall and on your SBC. These IP’s should have been provided to you by your Implementation Specialist.

  • If using Programmable Voice, your Voice application is linked to your VCP and a fallback callback URL is configured.

Termination (outbound)

Test basic call setup and teardown

  • Completed call

    • Ensure two-way audio in the negotiated codec

    • Ensure DTMF (RFC 2833 or in-band)

    • Ensure call hold and transfer negotiate properly

    • Ensure the call remains up for at least 1 minute

  • Call canceled during ringback

Test errors

  • Invalid number (404)

  • User busy (486)

  • Blocked destination (403), for example international when not activated

  • Call Rejection (603)

Test call types

  • Intraregion

  • International

  • Toll-free out (if applicable)

  • Local (if applicable)

Test failover

  • Ensure your platform can send calls to every Bandwidth SBC (session border controller) you were given, and fails over between them

Test sessions/CPS for load (if possible)

Origination (inbound)

DID testing

  • Basic call setup and tear down

  • Completed call

    • Ensure live answer has two-way audio

    • Ensure IVR hears audio/DTMF properly

    • Ensure call hold and transfer are treated properly

    • Ensure voicemail rings through properly

    • Caller ID and inbound caller ID (CNAM) presented properly (CNAM if enabled on the VCP)

    • STIR/SHAKEN verification result present, if enabled on the VCP

    • Ensure packet loss/jitter is within acceptable levels (under 2% loss)

    • Ensure a call remains up for over 1 minute

  • Test inbound sessions/CPS

Toll-free testing

  • DID testing plan, plus the following:

    • Ensure your platform answers within 25 seconds

    • Revalidate CICs (Bandwidth will confirm this for ported numbers)

Programmable Voice testing (if applicable)

  • Inbound call triggers your callback and your BXML executes

  • Outbound call created via API, with answer and disconnect callbacks received

  • Every BXML verb your application uses (Gather, Transfer, Record, Bridge, Conference, and so on)

  • Fallback URL: take your primary callback host offline and confirm calls still complete

Failover and traffic shifting

Test this before go-live and at least once a year. During an outage, you should already know what happens and what to do.

  • Ensure your endpoints accept calls from all Bandwidth SBCs, not just the one you saw in initial testing

  • Take your primary endpoint down and confirm inbound calls reach your secondary route

  • Change a VCP route endpoint in the Bandwidth App and via API, and note how long the change takes to apply

  • Shift distribution percentages between endpoints and confirm traffic follows

  • Move a block of test numbers between VCPs and confirm they follow the new routing

  • Roll everything back and confirm you are on your production configuration

  • Subscribe to status.bandwidth.com

When something fails

Send your Implementation Specialist or Voice Onboarding Representative the Bandwidth Call ID, from/to numbers, timestamp with time zone, and a SIP trace or callback log if available.

Note: Please make Bandwidth aware of any other special use cases (remote call forwarding, unusual SIP header dependencies, predictable traffic spikes, etc.)

Related articles

  • Managing Voice Configuration Packages on the Universal Platform

  • Advanced Call Routing on the Universal Platform

Did this answer your question?