[VoiceOps] Terminating 800 traffic with Caller ID of an 800 #

Jay Hennigan jay at west.net
Fri Feb 17 01:22:48 EST 2012

On 2/16/12 4:41 PM, Justin B Newman wrote:

> In my view, if an intermediate carrier is refusing to route the call,
> they are in clear and direct violation of the FCC's recent orders. In
> October, the FCC made it quite clear that incorrect, incomplete, or
> otherwise untraceable billing information is not a basis for call
> blocking.

You may be right in terms of an intermediate carrier blocking it to a
non-toll-free destination number.  What about the terminating toll-free
carrier?   Do the FCC's orders specifically apply to calls terminating
on a toll-free number?  These are treated differently from conventional
lines in that the callee pays the freight and caller-ID blocking is
supposed to be ineffective.

A carrier could argue that TF numbers aren't capable of origination so
any call claiming to originate from one is by definition fraudulent and
therefore not valid.  This would be particularly true if the called
party is the one paying for the call.  Are carriers required by FCC to
deliver fraudulent calls?

In any case, the destination end user can certainly refuse it.  This is
 particularly true if the terminating number is toll-free and the ANI is
missing or populated with a spoofed TF origin.

I'm not sure if this is still the case but within the last year
Verizon's customer service number of 800-483-2000 would not accept calls
coming from a toll-free CLID and the reason for the failure wasn't
readily apparent to the caller.  I believe it gave a "call cannot be
completed as dialed" intercept.

Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net
Impulse Internet Service  -  http://www.impulse.net/
Your local telephone and internet company - 805 884-6323 - WB6RDV

More information about the VoiceOps mailing list