<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
The caveat being, if you deviate in any way from the Provider defaults,
some of them have a bad habit of reverting your trunk to their internal
N-digit standard when some random tech goes through periodic cleanup or
upgrades (not that we've ever seen that happen :-}.<br>
<br>
That said, 110% agreed. now if only we can convince the Providers...<br>
<br>
David Hiers wrote:
<blockquote
cite="mid:2873f3700912230757k7975d13eg6dcc176185067a5f@mail.gmail.com"
type="cite">
<pre wrap="">I'm all for e.164 everywhere, no assumptions required.
David
On Tue, Dec 22, 2009 at 1:32 PM, Carlos Alvarez <a class="moz-txt-link-rfc2396E" href="mailto:carlos@televolve.com"><carlos@televolve.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 12/22/09 1:31 PM, Peter Beckman wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I'm kinda sick of all of us US-based folk thinking we don't have to use
our country code. I think all wholesale VoIP providers, even if they just
handle US/Canada, should require the use of the leading country code for
all
calls, NANPA-terminated included, and for origination that CallerID should
ALWAYS include the country code.
</pre>
</blockquote>
<pre wrap="">I agree that country code plus number is the bare minimum, but I've only run
into one carrier that refused to ("couldn't") do that. Ironic because they
also do international origination, so calls are delivered to us without any
way to know if they are US area+number or country+number.
</pre>
<blockquote type="cite">
<pre wrap="">You know how hard it is to standardize, both internally and globally,
when most telecom providers only support 10 digit caller ID? What about
the UK? What about China? And when callerID comes in, and it doesn't
conform to NANPA NPANXXXXXX, what country IS it from? I can guess, but
I'd like to know, not guess.
</pre>
</blockquote>
<pre wrap="">I've never run into an issue with the CID side of things. I don't think
it's that important, but maybe others do. We just pass it along as it is.
--
Carlos Alvarez
TelEvolve
602-889-3003
Advanced phone services simplified
_______________________________________________
VoiceOps mailing list
<a class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a>
</pre>
</blockquote>
<pre wrap=""><!---->_______________________________________________
VoiceOps mailing list
<a class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a>
</pre>
</blockquote>
<br>
</body>
</html>