[VoiceOps] VNXX

[Hiers, David]

I guess I'd have to see the particular context for usage of VNXX that we're talking about.  It was quite the item back about 5 years ago, but now it's probably just used to fluff up some marketing slide deck or something.

Lots of legacy stuff running around in our thought patterns.  DID, for instance, seems to be still legally defined (via current tariffs, court documents, etc) to have a very specific meaning of a copper trunk powered by the customer, over which a small number of digits can be signaled.  In spite of all the legacy meaning, we kick that term around in VOIP discussions all the time.

The real answers are probably buried in a couple dozen FCC docs and Federal Registers, but who's got the time?

:)



David Hiers

CCIE (R/S, V), CISSP
ADP Dealer Services
2525 SW 1st Ave.
Suite 300W
Portland, OR 97201
o: 503-205-4467
f: 503-402-3277 

-----Original Message-----
From: Alex Balashov [mailto:abalashov at evaristesys.com] 
Sent: Monday, August 10, 2009 8:49 AM
To: Hiers, David
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] VNXX

Thanks David.  I presume this is mainly accomplished on VoIP subscriber 
"lines?"

I'm just very confused about this term because it seems like a narrow 
subset of a broader and more cosmological truth about VoIP.  Yes, VoIP 
makes it very easy for someone to order DIDs that aren't in the rate 
center in which they are geographically located, without any sort of 
billable "call forwarding" events or subscriber characteristics as far 
as the originating or terminating carriers are concerned.  They're dumb 
pipes.

So what?  Why does this merit the term "virtual NXX" and how does it 
specifically relate to intercarrier comp issues?  I live in Georgia;  if 
I get a DID from a number block homed to NEWARK NJ, does that mean I 
have a "virtual NPA?"  "Virtual NPA-NXX?"  If I get a Moscow DID, do I 
have a "virtual country code?"  Why the focus on VNXX specifically as a 
piece of terminology?

I think putting the question that way cuts to the essence of what I'm 
probably missing...


Hiers, David wrote:

> Unless things have changed recently... 
> 
> A virtual NXX is an NXX assigned to a subscriber that comes from a rate center that does not physically contain the subscriber.  If you live in HACKENSACK, and your TN is from NEWARK, you've got a virtual NXX.
> 
> 
> 
>  
> 
> David Hiers
> 
> CCIE (R/S, V), CISSP
> ADP Dealer Services
> 2525 SW 1st Ave.
> Suite 300W
> Portland, OR 97201
> o: 503-205-4467
> f: 503-402-3277 
> 
> 
> -----Original Message-----
> From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Alex Balashov
> Sent: Sunday, August 09, 2009 3:58 PM
> To: voiceops at voiceops.org
> Subject: [VoiceOps] VNXX
> 
> What does the FCC and/or intercarrier compensation reform crowd mean, 
> exactly, when they say "Virtual NXX?"
> 
> Is that some class of clever remote call forwarding schemes from a CO 
> where the call between it and your rate center is rated LD by the ILEC, 
> but which some call forwarding product manages to get around or mitigate 
> somehow?
> 
> Or does it refer to carriers picking up inbound calls at the LATA 
> supertandems by carriers from rate centers in which they don't have 
> direct end-office trunking and whose number blocks are not homed to the 
> tandems (any tandems) to which the carrier is connected?  This was 
> rather common during the dialup boom and often skirted the 
> 'DS1-of-consistent-usage = DEOT needed' requirement in most form ICAs, 
> as I understand it.
> 


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


This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.