[VoIP] Number portability in CNET

Steph Kerman stfkerman at jps.net
Sat Oct 27 11:13:55 CDT 2007


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
>>> code in that prefix. I am in the process of constructing a 411 service
>>> to live at 555-1212, and I do have 555-2368 ringing on my desk. But if
>>> someone wanted another 555 number I'd be happy to write a line in the
>>> dialplan to send calls somewhere else.
>>>
>>> --
>>> David Josephson
>>>
>>>
>>>       
>> _______________________________________________
>> VoIP mailing list
>> VoIP at ckts.info
>> http://lists.ckts.info/mailman/listinfo/voip
>> Project Web Page: http://www.ckts.info/
>>
>>     
>
> --Shane
> +1-821-7311 CNET
>
> ----------------------------------------------------------------
>
> _______________________________________________
> VoIP mailing list
> VoIP at ckts.info
> http://lists.ckts.info/mailman/listinfo/voip
> Project Web Page: http://www.ckts.info/
>
>   


More information about the VoIP mailing list