[VoIP] Valid CLID

[Chad Perkins]

> Opps first part was the brain fart.
>
> The second part sounds good to me but I think maybe there 
> should be more input from some of the others.
> 
> Dennis Hock

I've listened to the chatter on this over last couple weeks (via the web) while I got my 
e-mail and computer fixed.  I tend to agree with John N's basic line of thinking; good 
CNET etiquette says tandems (and other clients) should always transmit 
*meaningful* CallerID.  One should note that may not translate into a CNET dialable 
number, i.e. a call coming in through a portal might appear as 603-806-1499.  
Meaningful yes, dialable no (most CC 1 folks would have to dial it from their landlines 
as 1+10D but the one is not transmitted for national callerid).  Calls can also come in 
from other non-PSTN networks; those calls too should be transmitting their native 
number and/or other meaningful data.

One of pet peeves is that callerid data is often presented in a way the North 
American callerid boxes will mangle; that is something other than 10 digits.  For this 
to work for CC 1 numbers, the calling callerid number needs to be padding with 
something before transmission.  Myself I like 'bb1' followed by 7D.  Three blanks is 
fine with me, but our friends across the pond would want to see 8D.  Area code 200 
is okay with me, but note that while meaningful that it not only would have to be in 
ENUM to be dialable, but would also need to be in everyones dial plan (which is 
helpful for routing CC 1 CNET calls, but not so useful for international routing).

So, for the numerical part, I would encourage folks to transmit ten digits/characters.  
Some one should be able to look at that and/or the name and match that to 
something on the 411 page (for "native" CNET calls).

To use '200' or not to use '200'.  The 200 area code has been in CNET long before I 
was (as part of the dial plan samples).  Some of us need it to route outgoing calls 
that otherwise would be routed to the PSTN by Asterisk, and most of us I think strip it 
off just before sending the called number to ENUM.  This history of 200 as far as I 
know is limited routing calls to CNET in the dial plan.  I did see Greg post recently 
regarding seeding the ENUM with the 200 AC, but I haven't heard much from folks 
with respect to how many have implemented the changes to accept '200' calls.

c.