nanog mailing list archives
Re: phone fun, was GeoIP database issues and the real world consequences
From: Owen DeLong <owen () delong com>
Date: Wed, 13 Apr 2016 13:52:13 -0700
On Apr 13, 2016, at 13:34 , Jean-Francois Mezei <jfmezei_nanog () vaxination ca> wrote: On 2016-04-13 16:18, Peter Beckman wrote:And further to that, throw in Local Number Portability (LNP) and you really need to know the full number in order to know which switch the specific number is assigned to. Not all 408-921 prefixed numbers will go to that switch in West San Jose.Is there the equivalent of BGP for number portability where every telco has the full table of who owns each prefix as well as individual routes for ported numbers ?
Sort of, but it’s called SS7 and it’s really more like multiple layers of DNS than like BGP.
Or is there a central database that is consulted before a dialed number starts to be connected so originating telco knows to send call ?
Well, yes and no, but AIUI, the common SS7 database is a lot more like the DNS root zone.
Or does the originating telco route the call to the original onwer of the prefix and lets that original owner figure out how to terminate the call ?
Generally within a country code (NANP is one country code even though it’s many countries (US, CA, much of the Caribbean), the central SS7 database will do a longest-match pointed to the correct Telco and possibly the correct switch at that telco. However, there are all kinds of different redirects possible within said telco as well, such as call forwarding (in multiple forms), cellular registration, VOIP gateways with portable SIP registrations, etc.
From a long distance billing point of view, if Bell Canada connects to anumber originally onwed by AT&T but ported to Verizon, with whom would Bell share long distance revenues ?
Generally, Verizon. AT&T won’t usually participate in the call process at all. (see above). Owen
Current thread:
- Re: phone fun, was GeoIP database issues and the real world consequences, (continued)
- Re: phone fun, was GeoIP database issues and the real world consequences Jay Hennigan (Apr 13)
- Re: phone fun, was GeoIP database issues and the real world consequences John Levine (Apr 14)
- Re: phone fun, was GeoIP database issues and the real world consequences Owen DeLong (Apr 14)
- Re: phone fun, was GeoIP database issues and the real world consequences John R. Levine (Apr 14)
- Re: phone fun, was GeoIP database issues and the real world consequences Larry Sheldon (Apr 14)
- Re: phone fun, was GeoIP database issues and the real world consequences Jean-Francois Mezei (Apr 14)
- Re: phone fun, was GeoIP database issues and the real world consequences Owen DeLong (Apr 14)
- Message not available
- Message not available
- Message not available
- Message not available
- Re: phone fun, was GeoIP database issues and the real world consequences Jonathan Smith (Apr 14)
- Re: phone fun, was GeoIP database issues and the real world consequences Peter Beckman (Apr 13)
- Re: phone fun, was GeoIP database issues and the real world consequences Jean-Francois Mezei (Apr 13)
- Re: phone fun, was GeoIP database issues and the real world consequences Owen DeLong (Apr 13)
- Re: phone fun, was GeoIP database issues and the real world consequences John Levine (Apr 13)
- Re: phone fun, was GeoIP database issues and the real world consequences John Levine (Apr 13)
- Re: phone fun, was GeoIP database issues and the real world consequences Matthew Kaufman (Apr 13)
- Re: phone fun, was GeoIP database issues and the real world consequences Larry Sheldon (Apr 13)
- Re: GeoIP database issues and the real world consequences Carlos M. Martinez (Apr 13)
- Re: GeoIP database issues and the real world consequences Steve Atkins (Apr 11)
- Re: GeoIP database issues and the real world consequences John Levine (Apr 11)
- Re: GeoIP database issues and the real world consequences Laszlo Hanyecz (Apr 11)
- Re: GeoIP database issues and the real world consequences Sean Donelan (Apr 11)
- Re: GeoIP database issues and the real world consequences Leo Bicknell (Apr 12)