Getting someone to explain my configuration
Routing tables, regular expressions and SDP profiles, read back to you in plain English. And the same capability facing the other way: describe the match you want, get the regex.
Every session border controller accumulates configuration that outlives the person who wrote it: routing tables with forty entries, regular expressions nobody remembers the intent of, and SDP profiles named after a project from four years ago.
None of it is hard to read. The cost is that reading it requires the one engineer who knows the box, and that engineer is busy, on holiday, or has left. This is the category where Butler behaves least like a search tool and most like a colleague who has read the manual.
Pick a question, read the whole exchange
Both of these ran against a synthetic demo fleet, so the device names and addresses are ours rather than a customer’s.
- Incoming from carriers. When a call arrives from a carrier, the SBC adds a prefix to the dialled number. A number like +1 415 555 1234 becomes 0051+14155551234 for the first domestic trunk.
- Outgoing from your network. Calls matching 0xxx patterns go to SUT-00 on the relay routes, and calls matching 2xxx patterns go to SUT-02.
- International against domestic. Numbers starting 115 or 105 route as international, and the same prefixes with a US ten-digit number route as domestic.
“I’m on mobile and cant figure out the regex now” is the whole argument in one sentence, typos and all. The engineer is away from their desk, the information is in a form that needs a desk, and one message removes the dependency. Worth noticing earlier in the thread too: asked about a box called SBC-01, Butler listed what actually exists and asked which one was meant, rather than picking the closest name and running with it.
- This is a multi-carrier SBC cluster handling domestic US calls over two carrier trunks and international calls over two separate international trunks.
- It also carries test traffic from SIPp generators, and inter-SBC routing for load distribution and resilience.
- The SUT-02 unit has no external ITSP trunk and serves as a downstream node for relayed traffic.
An illustration rather than a case study: nobody has asked this in anger, because both of the teams using Butler already knew their own networks. It is here because it is the first day on an unfamiliar box, and the answer does the thing that matters on a first day, which is separating what is configured from what is actually carrying calls. Note the last line as well. It got to the end of a complete answer and then offered the question you would have asked next.
The prompts, and where each one leads
Nothing here needs you to know a field name or navigate to a configuration page.
The obvious first question of anyone handed an unfamiliar box.
The routes as configured, in the order they are evaluated, in the thread rather than behind a login.
A rule is doing something you did not expect and you need to know what it actually matches, not what it was meant to.
The expression broken down piece by piece, with what each fragment admits and what it excludes.
You are away from your desk and somebody needs an answer now. Telling Butler your constraint changes how it answers.
A short prose summary sized for a phone screen, with no syntax to parse.
How to get the most out of it
One number and maybe a time. Butler finds the call and says whose side ended it.
Counts, groupings, thresholds and KPIs across a population of calls.
Explain my configuration
Routing tables, regex and SDP profiles in plain English.
Ask in French, Spanish or Portuguese, get the answer from the English documentation.
Changes, reports, files and email, each one waiting for your yes.
Paste the complaint in the customer’s own words and let Butler find the call.
Ask Butler what your own routing does
Deployed in 48 hours, month to month, in the chat app your team already has open.
By submitting this form, your information will be processed in accordance with our Privacy Policy.