Date   
Re: Problems retrieving details programatically

Jeremy Schaeffer
 


Sort of. They changed to https only, I never got the time to re-write my java to do https, its a lot more complicated. You have to deal with ssl. - Jeremy

On 7/23/2019 9:47 AM, Wahl, James R. wrote:
I'm having similar issues. Did you ever get it resolved?


  

Re: Problems retrieving details programatically

Wahl, James R.
 

I'm having similar issues. Did you ever get it resolved?

Problems retrieving details programatically

John Nevius
 

All,

I've been successfully running, since about 2014, a python program to derive the local calling area for NANPA rate centers.  This is done through a python program that posts the XML string:
(where the npa and nxx values are inserted into the string for the %s

This works successfully for multiple queries but then fails on a query that should be valid.  e.g.

. . . . . processing RC JERSEYCITY, NJ in LATA 224
. . . . . processing RC HACKENSACK, NJ in LATA 224
. . . . . processing RC NEWARK, NJ in LATA 224
. . . . . processing RC UNION CITY, NJ in LATA 224
. . . . . processing RC MORRISTOWN, NJ in LATA 224
. . . . . processing RC BAYONNE, NJ in LATA 224
. . . . . processing RC CLIFFSIDE, NJ in LATA 224
. . . . . processing RC ORADELL, NJ in LATA 224
. . . . . processing RC ENGLEWOOD, NJ in LATA 224
. . . . . processing RC LEONIA, NJ in LATA 224
. . . . . processing RC SUCCASUNNA, NJ in LATA 224

For the last query (NPANXX = 201230) all I get is:
<Response [200]>

This problem is repeated multiple times, sometimes on consecutive queries sometimes after multiple successful queries

This problem is repeatable.  I've tried inserting a short (1 second) pause before I make each query, with no apparent difference.  

Has anyone seen this or have a suggested work-around?

Re: Mobile number portability

czg7777
 

You quoted a Wikipedia article, which goes on to mention that:

...
Numbers are only portable within a LIR (local interconnection region), regions defined by the ILEC and approved by the Canadian Radio-television and Telecommunications Commission (CRTC), each of which cover a number of exchanges. Each LIR has a Point of Interconnection (POI) exchange through which calls are routed, and if a number is ported out to a different LIR then calls to that destination will be rejected by the POI switch.
Not all exchanges support LNP, typically there needs to exist competition within an exchange before an ILEC will enable portability, and then only by request. Most small local independent telephone company exchanges are exempted from competition and local number portability requirements. Numbers in the rarely used non-geographic area code 600 are not portable.

Local interconnection regions follow ILEC switching arrangements, and typically cover relatively small areas. See https://localcallingguide.com/lca_listlir.php for a list.



On Dec 23, 2018, at 11:02 AM, belanger@... wrote:

My question was in reference to the definition on telephone portability. See below. It could be that I misinterpret the part on geographic portability.

As czg7777 mentioned, landline caller have long distance reaching me on my cell phone. So I thought that if geographic portability is provided by some means I could request my cell phone number to be moved to the city where I actually live?

Local number portability (LNP) for fixed lines, and full mobile number portability (FMNP) for mobile phone lines, refers to the ability of a "customer of record" of an existing fixed-line or mobile telephone number assigned by a local exchange carrier (LEC) to reassign the number to another carrier ("service provider portability"), move it to another location ("geographic portability"), or change the type of service ("service portability").[1] 

Re: Mobile number portability

belanger@...
 

My question was in reference to the definition on telephone portability. See below. It could be that I misinterpret the part on geographic portability.

As czg7777 mentioned, landline caller have long distance reaching me on my cell phone. So I thought that if geographic portability is provided by some means I could request my cell phone number to be moved to the city where I actually live?

Local number portability (LNP) for fixed lines, and full mobile number portability (FMNP) for mobile phone lines, refers to the ability of a "customer of record" of an existing fixed-line or mobile telephone number assigned by a local exchange carrier (LEC) to reassign the number to another carrier ("service provider portability"), move it to another location ("geographic portability"), or change the type of service ("service portability").[1] 

Re: Mobile number portability

John Novack
 



czg7777 wrote:
What do you mean by "updated to a different city"? Numbers are assigned to a particular rate centre. This is based on landline technology and not particularly relevant for mobile usage, since the local calling area generally changes according to wherever the mobile phone happens to be. The only relevance is that calls to a mobile number from a landline will be charged according to the "home" rate centre of the mobile number.


I have a mobile number ( in the US ) in a rate center some 80 miles from my billing address. it was ported from an RCF number, which originally, 18 years ago, a land line.  Since my carrier considered my current location within THEIR local calling area, they allowed the port, though given that it was requested the first day porting to and from mobile numbers were allowed, it did take 3 months.
In the US, at least, it seems the location and name for numbers is up to the whim of the particular carrier, and often doesn't even change once a number is ported away to another carrier.

Anymore, in the US at least, so many providers have nationwide calling unlimited included, locations, and even the NPA, are close to being meaningless. Mostly only the IILEC carriers vary.
Customers move around the country, keep their numbers, I assume even changing their billing address, and nothing else changes. Only the "copper" fixed land lines and their offshoots seem to continue the 30 year old configurations and restrictions.

John Novack




-- 

Dog is my Co-pilot

Re: Mobile number portability

czg7777
 

What do you mean by "updated to a different city"? Numbers are assigned to a particular rate centre. This is based on landline technology and not particularly relevant for mobile usage, since the local calling area generally changes according to wherever the mobile phone happens to be. The only relevance is that calls to a mobile number from a landline will be charged according to the "home" rate centre of the mobile number.


Mobile number portability

belanger@...
 

Hi,
Is it possible in Canada to have a cell phone number updated, within the same area code, to a different city. If yes what is the procedure?
Thanks

Re: DNVRCOSLDS0

czg7777
 

Yes, I am looking into it. Unlike some other carriers, CenturyLink still provides switch information.

DNVRCOSLDS0

Christopher Lombardo
 

Is it possible to get the Denver Sullivan switch and prefix list back in the localcallingguide.com search?  Example:  303-368 has no switch information.  

Thank you.

I also found this post from 2016 which includes all the NPA/NXXs that were moved into the Denver Rate Center at the same time:

Denver Colorado rate center

rsklar@...
01/29/16   

Missing from the database entries for these CLLI's since Aurora and Denver Sullivan were combined into Denver:

 

AURRCOMBRS1 - 303-261

 

AURRCOMADS0 - 303-326 340 341 343 344 360 361 363 364 365 366 367 676 677 724 739

                            720-553 777 847 848 857 858 859

 

DNVRCOOUDS0 - 303-317

 

DNVRCOSLDS0 - 303-283 306 337 338 368 369 614 636 671 695 696 743 745 750 751 752 755 873

                           720-744 747 748

Re: OMNIPOINT/TMOBILE Info Incorrect

John Novack
 

Probably a corporate or legal reason.
Omipoint was bought/merged into VoiceStream MANY years ago, along with PowerTel and perhaps some others. 20 years ago perhaps?
VoiceStream changed their name to T-Mobile MORE than 10 years ago.
All sorts of legal reasons the NANPA shows names that are different than a company marketing name used for public consumption.

John Novack

czg7777 wrote:
Hi, Justin:

NANPA still shows it as Omnipoint in their databases. LCG does the same thing but the URL goes to TMobile.

On Sep 17, 2018, at 2:37 PM, Justin <jb_92104@...> wrote:

I'm not sure I'm writing the correct email address, but I'm curious as to why

OCN: 6626 OMNIPOINT COMMUNICATIONS ENTERPRISES, L.P.

has not been updated to TMOBILE on the local-calling-guide website? for example: area code 484 prefix 995 says OMNIPOINT and eventually ended up to be TMOBILE.

Thanks, Justin
San Diego




-- 

Dog is my Co-pilot

Re: OMNIPOINT/TMOBILE Info Incorrect

czg7777
 

Hi, Justin:

NANPA still shows it as Omnipoint in their databases. LCG does the same thing but the URL goes to TMobile.

On Sep 17, 2018, at 2:37 PM, Justin <jb_92104@...> wrote:

I'm not sure I'm writing the correct email address, but I'm curious as to why

OCN: 6626 OMNIPOINT COMMUNICATIONS ENTERPRISES, L.P.

has not been updated to TMOBILE on the local-calling-guide website? for example: area code 484 prefix 995 says OMNIPOINT and eventually ended up to be TMOBILE.

Thanks, Justin
San Diego



OMNIPOINT/TMOBILE Info Incorrect

Justin
 

I'm not sure I'm writing the correct email address, but I'm curious as to why

OCN: 6626 OMNIPOINT COMMUNICATIONS ENTERPRISES, L.P.

has not been updated to TMOBILE on the local-calling-guide website? for example: area code 484 prefix 995 says OMNIPOINT and eventually ended up to be TMOBILE.

Thanks, Justin
San Diego


Re: HTTPS with CloudFlare

czg7777
 

Yes. I was going to point out that you should be seeing a Cloudflare IP, not that one.

On Sep 9, 2018, at 12:21 PM, mike@... wrote:

Never mind, I figured it out.

There was a cached DNS entry in my recursive server with a long TTL for localcallingguide.com

Re: HTTPS with CloudFlare

mike@...
 

Never mind, I figured it out.

There was a cached DNS entry in my recursive server with a long TTL for localcallingguide.com

Re: HTTPS with CloudFlare

mike@...
 

Yep, see below:

$ curl -v https://localcallingguide.com

* About to connect() to localcallingguide.com port 443 (#0)

*   Trying 204.11.194.30...

* Connected to localcallingguide.com (204.11.194.30) port 443 (#0)

* Initializing NSS with certpath: sql:/etc/pki/nssdb

*   CAfile: /etc/pki/tls/certs/ca-bundle.crt

  CApath: none

* NSS error -12263 (SSL_ERROR_RX_RECORD_TOO_LONG)

* SSL received a record that exceeded the maximum permissible length.

* Closing connection 0

curl: (35) SSL received a record that exceeded the maximum permissible length.

Re: HTTPS with CloudFlare

czg7777
 

Are you querying with HTTPS? Assuming I have configured Cloudflare correctly, all traffic should be routed via HTTPS now. 

HTTPS with CloudFlare

mike@...
 

I noticed that sometime late yesterday I began having issues querying the API because of some TLS errors. The site comes up fine in a web browser, but if I run curl from my CentOS 7 machine or my OS X machine, I get errors about an SSL record exceeding the maximum permissible length or unknown protocol.

Anybody else run into this?

Re: Union Telephone Info Incorrect

czg7777
 

This site is not updated in real time. It will appear in the next update.

On Jun 28, 2018, at 10:02 AM, gdutra@... wrote:

On their site it states that Amber Kerr is the current contact. This is correct however on your site for some reason the contact field is not updating.

Re: Union Telephone Info Incorrect

gdutra@...
 

On their site it states that Amber Kerr is the current contact. This is correct however on your site for some reason the contact field is not updating.