<!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">
Florian Overkamp wrote:
<blockquote cite="mid1098809556.417e80d4f3c1f@www.obsimref.com"
type="cite">
<pre wrap="">Hi,
Citeren "Bownes, Robert" <a class="moz-txt-link-rfc2396E" href="mailto:Robert.Bownes@ogs.state.ny.us"><Robert.Bownes@ogs.state.ny.us></a>:
</pre>
<blockquote type="cite">
<pre wrap="">The problem with 800 numbers is that they are not unique. The same 800
number may be routed differently on a LATA or geographic basis. See
<a class="moz-txt-link-freetext" href="http://www.nanpa.com/nas/public/nonGeoNpasInServiceReport.do?method=disp">http://www.nanpa.com/nas/public/nonGeoNpasInServiceReport.do?method=disp</a>
layNonGeoNpasInServiceReport for a list of the non geographic numbers.
</pre>
</blockquote>
<pre wrap=""><!---->
Uhm, I'm not in the US, so correct me if I'm wrong, but in the Netherlands, the least
thing you can expect is that a 0800 number belongs to one organisation. Therefore, if
this organisation chooses to publish the number through DUNDi, they should never
have to expect conflicts with other organisations. They control the route (as they
should) and they can decide wether or not to deal with it in a certain way. We can also
choose what to do with 0800 numbers called by mobile users. This has two purposes:
the cost to accept the call is higher, but also we can route differently based on the
fact we have no clue about their whereabouts.
I don't think this is a problem. People disclosing 0800 numbers through the e164
context in DUNDi should consider callers coming in on this route as 'roaming'. No
assumptions on whereabouts can be made.
Or am I missing something here ?
</pre>
</blockquote>
<br>
Yes, if Robert is correct, what you're missing is that "The problem
with 800 numbers is that they are not unique". So, for example, you
could have a number +1 800 234 5678 which goes to one company when
called from some US states, but goes to another company when called
from other US states.<br>
<br>
I don't know if that is (still?) correct, but I do remember in the past
my family's business needed to have a separate toll-free number for
callers in 49 states, and a different number for callers in our home
state, and that callers using the wrong one would not get through.<br>
<br>
I'm not sure if those numbers which were for in-state calls only were
assigned to different entities in other states.. It seems pretty
insane to do that, but who knows. 5 minutes of googling didn't seem to
give me an answer..<br>
<br>
-SteveK<br>
<br>
</body>
</html>