[VoIP] Number portability in CNET

[David Josephson]

As with most software-defined realities, we can do any or all of those 
things. The whole 7-digit dialed number is part of the ENUM query, so 
Greg's server could indeed look up each individual number, or look for 
ranges of numbers.

I should have written more of a preface. I was responding to the latest 
round about office code hoarding. Since this topic comes up tiresomely 
often, implying that someone would like one of the office codes that 
someone else is sitting on, we could reach a consensus that we'd ask 
Greg to carve out some of the office code in the ENUM table, if the 
original assignee of that office code was not using it, and/or unable to 
forward a desired number to someone who *would* use it.

Whether the call is forwarded by redirect or by tandem switching of 
course depends on the architecture of the two involved offices.

--
David Josephson
> How does this fit in with David's comment?
>
> If the full 7-digit number is looked up in ENUM for each call to allow 
> sharing of office codes doesn't that require ENUM to be updated for all 
> new line assignments at local switches?  I thought only the 3-digit 
> office code was being looked up and that there was discussion about 
> extending this to the thousands digit to allow sharing of office codes 
> in blocks of 1000 numbers, but that it had not been done.
>
> Steph
>
> Shane Young wrote:
>   
>> There is no need to do either.
>>
>> Since we always lookup every number in DNS via ENUM, greg just points  
>> the "ported" number to the new destination.
>>
>> It's a lot like the way real LNP works.
>> --Shane
>>
>>
>> Quoting Steph Kerman <stfkerman at jps.net>:
>>
>>   
>>     
>>> Send by redirecting at the originating point or send by tandeming
>>> through your system?
>>>
>>> Steph
>>>
>>> David Josephson wrote:
>>>     
>>>       
>>>> I think that anyone who has an office code should be able to provide
>>>> routing to other CNET numbers, should anyone else have a desire for a