[VoIP] Valid CLID

[Shane Young]

The + indicates it's supposed to be in e.164 format which includes the  
country code (1 in this case)


My preference would be to send non-NA ANI as +country-code and the number
North ameican could be sent as either 7 digits or +1 and seven digits.



Quoting Dennis D Hock <hockd at dteenergy.com>:

>
> I agree with John.  Iknow we have had this discussion previously I guess I
> haven't had my mind on it enough to understand but I don't see the need for
> the 200 yet, if ever in CNET.  I think if for the US members or NANP
> members we send either a 1nxx-xxxx or nxx-xxxx as the CLID for our calls
> with the caveat that in general it be a dialable somehow answered number
> even if only a announcement of some type.
>
> As a thought if the day should come do we want / need to use a NPA should
> we immediately apply a 3 digit NPA or possibly simply break the NANPA into
> say ten location areas?  Each area could be a single digit allowing a good
> section of the country to be encompassed under a single digit NPA code.
> Although this veers away from current practice it might make it more
> palatible for many of us who would like to dial a standard set of yet
> minimum digits.  Thoughts anyone?
>
> That  +12691212 is my number throguh Gregs tandem.  Not exactly sure why
> the + is appended onto the front of the number.
>
> Dennis Hock
>
> -----voip-bounces at ckts.info wrote: -----
>
>
> To: Voice Over IP Tandem for Analog Switches <voip at ckts.info>
> From: John Novack <jnovack at stromberg-carlson.org>
> Sent by: voip-bounces at ckts.info
> Date: 05/16/2007 03:43PM
> Subject: Re: [VoIP] Valid CLID
>
>
>
> Shane Young wrote:
>> So, this brings up a good topic for discussion...
>>
>> What *should* we use as a valid CLID?
>>
> Since I opened my mouth, I would suggest sending a valid CNET number
> that could be returned. Perhaps some even have the ability, or should
> would, do a "return call" so either 1+NXX-XXXX or NXX-XXXX for North
> America.
> Sorry my mind STILL can't get around the open numbering plan to offer a
> suggestion there.
> Sending the "200" NPA never made much sense to me either. Perhaps I
> can't see where CNET will ever have to go beyond 7 digit dialing for
> North America, and  the current International scheme.
>
>> Here are some examples of what I've received:
>>
>> VT1005_Line_1
>>
> Fairly simple to change the Motorola to use a 7 digit number. I have
> found that the user name and number must match, which seems to be an
> Asterisk limitation. I could be wrong on that, as it has been a couple
> of months since I messed with the VT 1005
>> 9550000
>>
> Simple enough to have each device report its CLID, or use one CLID that
> reflects a good callback number.
> Also would be nice to either send a name or some device identifier. I
> probably need to re examine some of mine as well for that.
>> 2184886566
>>
> Guessing that is someones PSTN number?
>> 12639900
>>
> That should also work, if the dialplan is programmed correctly.
> I allow dialing as either 7 digits, 1 plus seven digits for North
> America, though I never dial it that way myself my portal will accept
> that format
>> +12691212
>>
> Bet that is Dennis Hock through Greg's switch. I suppose a return call
> could parse that into a good CNET number
>> I'm pretty sure when I send CLID it's 10 digits with 200 being the NPA
>> like 2008217383
>>
> Why not simply get rid of the 200 NPA??
>
>> I *think* that 7 digits in the US is what most people are sending.
>>
> CNET expects 1 plus 7 digits for the DNS/ENUM to work properly, but 7
> digit CLID for North America is what I consider ideal.
>
>
> Just my opinion, though
>
> John Novack
>
> _______________________________________________
> VoIP mailing list
> VoIP at ckts.info
> http://lists.ckts.info/mailman/listinfo/voipProject Web Page:
> http://www.ckts.info/
> _______________________________________________
> 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