Reading the documentation in your own language
The ProSBC knowledge base is written and indexed in English. Ask Butler a configuration question in French, Spanish or Portuguese and you get the answer in the language you asked it.
There is an engineer on most teams who knows voice networks perfectly well and does not read English. They can hear a one-way audio fault and tell you it is a NAT problem before they open anything. What they cannot do is read the documentation for the session border controller in front of them, because it only exists in English.
The workaround costs an hour. Find the right page without being able to skim it, paste it through a translator, and then judge whether a machine translation of a technical document got the field names right. Most people give up and ask a colleague, which turns one person’s question into two people’s afternoon.
Translating the question, not the page
This part is worth a paragraph, because the obvious approach does not work. A knowledge base indexed in English returns nothing useful for a query typed in Portuguese; the words simply do not match. Translating the retrieved page afterwards does not help either, since you have to find the right page first, and finding it was the hard part.
Butler goes the other way round. It reads the intent of your question, composes its search in English, retrieves the English source, and renders the answer back into the language you wrote in. You never see the English and you never have to guess at the search term. Every question below was asked in a fresh session so no language could carry over, every answer came back in the language it was asked in, and every underlying search was issued in English.
Pick a question, read the whole exchange
Every one of these ran against synthetic demo data, and every checkable claim in them has been verified against the product documentation.
Read the last message rather than the code block. Butler names a configuration field only where it has actually seen that field, and a walk-me-through question is exactly where the temptation to fill a gap with something plausible would otherwise sit. Where the concept is clear but the precise fields are not, it offers to go and read the real NAP on your own box and show you what is genuinely on it. In a language where checking the documentation yourself is the hard part, that offer is the safeguard.
One tool call, seven seconds, and a complete answer: where the list lives, the format it wants, and the fact that nothing takes effect until you activate. Note the last line, too. Nobody asked for the portal route, and it offered one anyway, for whoever would rather click than call an API.
- NAP est un point d’interconnexion SIP, le “qui” à qui on parle. Il définit une destination SIP : IP proxy, ports, transports, ACLs.
- Route est une règle de routage d’appel, le “comment” et le “où”. Elle décide quel NAP de sortie reçoit l’appel et applique les transformations de numéros.
The priority and weight ordering and the default routing script both check out against the knowledge base. This is a question that takes a new engineer the better part of a week to assemble from the documentation, answered in one paragraph, in French.
- O transcoding é capado pela licença, portanto a capacidade disponível depende do que está licenciado.
- Software transcoding cobre só G.711 a-law para u-law (PCMA para PCMU).
- Para verificar a capacidade atual, use get_license_status. Posso consultar a licença do seu equipamento se me indicar o host_id.
This is the commercially inconvenient one. The honest answer is that this conversion needs the hardware transcoding unit, and that is what came back rather than the answer the customer was hoping for. Correct as of September 2026. Software G.729 is on the roadmap, so check the current position before you budget for hardware.
- Su SBC tiene en caché la dirección IP antigua del hostname SIP de su operador. Los registros DNS en el SBC no se actualizan automáticamente cuando cambia un registro externo.
Two things happened here that are easy to miss. The engineer said not to execute anything, and Butler stopped at the explanation, which is the whole of what was asked for. Then, rather than guessing at a name it did not have, it offered to go and list the real ones. A VoIP engineer who cannot read the English documentation got the concept, the exact action name and an offer to find the missing detail, without leaving the chat.
How it stays accurate
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.
Routing tables, regex and SDP profiles in plain English.
A knowledge base in your language
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 in the language you think in
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.