
TollHound documentation¶
TollHound detects calling fraud on carrier voice networks (Cisco BroadWorks first) from call records, and blocks it through the carrier's own switch. These pages are grouped by who reads them.
| Section | For | What is there |
|---|---|---|
| Product | buyers, partners, new staff | what TollHound does, the fraud it finds, how it is deployed |
| Administration | carrier, reseller and enterprise admins; analysts | running TollHound for your own network or enterprises, and the detection rules |
| API | integrators | the REST API, webhooks and tokens |
| Operations | whoever runs TollHound | installing, settings, upgrades, monitoring, runbooks |
| Security | security reviewers | how TollHound protects carrier and subscriber data |
| Release notes | everyone | what changed in each release |
TollHound's own staff also see Engineering, Support and Sales sections in the internal site.
All documentation sits behind sign-in. Prospects and partners get PDFs or a guest account under NDA.
How these docs are built¶
The pages are Markdown in the repository, next to the code they describe, and change in the same
pull request as that code. Each page says in its front matter who it is for and how widely it may
be shared (sensitivity): customer pages go to the customer site, and the internal site has
every page. How to write them is in the internal site, under Engineering.