r/VOIP
Fresh DIDs tagged "Spam Risk" within ~3 calls despite verified A-attestation - is originating CLEC reputation the real driver?
- upvotes
- 3
- comments
- 9
Post
Highlighted: the lines this signal was extracted from
Licensed insurance agency running consent-based outbound. Trying to understand a tagging problem that per-number behavior doesn't explain. Setup: We buy pools of local DIDs through a wholesale provider that handles STIR/SHAKEN signing. Each rep gets a pool and we rotate. Per-number volume is roughly 30 dials/day, about 150/week. The provider says these DIDs sat unused in storage 12+ months before assignment. Problem: Brand new numbers show "Spam Risk" on AT&T within about three dials. Three calls cannot build a reputation on their own, so something upstream of per-number history is driving it. What I've ruled out using SIP traces: Signature is valid and the signed orig.tn matches the caller ID actually presented. Attestation A. No internal routing identifiers of ours leak into the outbound INVITE. Verified by full-message search. So this isn't a signature/caller-ID mismatch and it isn't attestation level. What I found in the LERG: I resolved every thousand-block in our pool to its carrier. 71% trace back to a single wholesale CLEC, spread across ~28 state-level entities. The two numbers that flagged together in my test sit in the same thousand-block. Worth noting for anyone doing this analysis: different thousand-blocks inside the same NPA-NXX belong to different carriers. One prefix in our pool splits across four separate carriers by block. Prefix-level lookups gave...
Keep reading with a free account
The rest of this post, and every signal for AT&T, is in your free account.