- Shipped
- October 4, 2026 at 8:44 PM UTC
- Author
- Kamo
- Commit
- 1a68e28
[kamo-outbound-gate] gains a GotoIf on kamo-asterisk-support's managed [kamo-toll-fraud-blocked] list, between the SP13 AI-transfer line and the Goto onward, and a (blocked) branch that tags OBBLOCK, plays the not-available prompt and hangs up with cause 21. An allowed call no guard matches still ends at the same Goto. 911 and 933 never reach the gate. **************** makes the same edit on the running node: one guarded, idempotent edit of the gate's Goto after '; sp13:ai-xfer-outbound', refusing with nothing written when that anchor is missing or [kamo-toll-fraud-blocked] is not yet in the managed policy section; it backs up, reloads the dial plan and verifies what Asterisk loaded. The fixture is the k1m1 file as of 2026-10-04.