FRINK Advanced Services
Request a demo

Call testing

One routing change.
Two ways to learn it broke something.

Today, after a change someone dials a few numbers and hopes. International, emergency and inbound routes are tested when a user reports they fail.

01 · Scenarios

What must always work?

Yesterday

Someone remembers to dial three numbers after the change window.

Today with FRINK

Scenarios for every route that must always work – international, inbound, site-to-site. Emergency numbers are never dialled.

02 · Run

How often?

Yesterday

Tests run once, if at all.

Today with FRINK

Suites run after every change, in one click. Scheduled runs are on the roadmap.

03 · Failure

What broke, and where?

Yesterday

A failed test means another round of log collection.

Today with FRINK

The failed test call's step-by-step flow, with the step that failed.

04 · Result

Broken routes found first

Yesterday

The first real call fails. A user tells you.

Today with FRINK

The test run fails. Nobody else notices.

What changes

  • Routes tested after a changeYesterday: Three, by handToday with FRINK: Every scenario in the suite
  • Who finds the breakYesterday: A userToday with FRINK: The run after the change
  • EvidenceYesterday: "It didn't connect"Today with FRINK: Call flow of the failed step

Worked example · Insight 09

The change nobody made

A Friday-evening route change failed calls all weekend. A site-to-site suite run after the change would have failed straight away.

Read the full case
  1. What must always work?
    Site-to-site suite run after the change.
  2. How often?
    The run fails on the changed route pattern.
  3. What broke, and where?
    The run shows which call failed after the change.
  4. Broken routes found first
    Change reverted before Monday.

See it on your own infrastructure.

A demo on a live system, then a proof of concept inside your network – fully offline if it has to be.