[VoiceOps] Conferencing NPAs

[Ujjval Karihaloo]

I am not going to block and then have FCC knock on my door, I was just sharing info.

Level 3 restricts calls to these anyway...after they hit L3 capacity, so I don't need to worry..Just tell Customers L3 is blocking it and they need to get other Conf Dial-in numbers from their Conf Provider - like someone here suggested - is the best way to handle this I think.

Ujjval Karihaloo
VP Voice Engineering
IP Phone: +13032428610
E-Fax: +17202391690

SimpleSignal Inc.
88 Inverness Circle East
Suite K105
Englewood, CO  80112



-----Original Message-----
From: Alex Balashov [mailto:abalashov at evaristesys.com] 
Sent: Wednesday, December 09, 2009 11:55 AM
To: Paul Timmins
Cc: Ujjval Karihaloo; voiceops at voiceops.org
Subject: Re: [VoiceOps] Conferencing NPAs

Paul Timmins wrote:

> Michigan has mandatory thousands block pooling, and active LNP in most 
> of those exchanges. I'm sure many of these other states are the same. 
> Blocking this is a really dangerous thing to do, even if you don't care 
> that the FCC would take a dim view. 906-204 for example has cingular 
> cell phones in it.

I was about to say, Ujjval:  if you're going to block things, at least 
take care to block them at the NPA-NXX-Y pooled level.  90% of the 
markets in the country are pooled;  NPA-NXX is no longer a useful way 
to determine which carrier a call is being routed to, and has not been 
for a long time.  As Paul says, in MI there may be little to no 
correlation between NPA-NXX and what you (or L3) are/is seeking to block.

LNP dips are ideal, but 7-digit prefixes will still get you get 
somewhere;  NPA-NXX will not.


-- 
Alex Balashov - Principal
Evariste Systems
Web     : http://www.evaristesys.com/
Tel     : (+1) (678) 954-0670
Direct  : (+1) (678) 954-0671