Talk:CLLI code

Untitled
was this invented by BC Tel? —Preceding unsigned comment added by 24.244.73.150 (talk) 01:17, 29 November 2009 (UTC)
 * No, this is an Americanism and was concocted by Bellcore. CLLI codes do exist for all Telus exchanges, but the concept did not originate there. K7L (talk) 03:06, 3 June 2013 (UTC)

CLLI codes to calculate distance
From the intro:
 * CLLI codes are useful to telecommunications companies for ordering phone service, for the rating of call detail records for billing purposes, and to assist in tracing calls. CLLI codes are associated with Vertical and Horizontal coordinates (frequently abbreviated to "V and H coordinates"), which were developed by AT&T researcher Jay K. Donald to provide a relatively simple method of calculating distance between two network locations. Various mileage-sensitive services are priced according to the V and H coordinates associated with the two endpoints' CLLI codes.

I'm a little unsure about this... the rate centre (and the V/H coordinates for billing purposes) is not the wire centre (the location of the actual switch, which has its own V/H coordinates). indicates that +1-905-625 and +1-416-620 are 21km (13mi) apart (for billing purposes), even though physically both are on the same switch.

Odessa, Ontario appears to be a legal fiction in that it has its own rate centre, coordinates (V: 04634 H: 02220), local calling area and CO codes (+1-613-386) even though the exchange physically does not exist (a search for a "386 exchange" only returns a CLLI for a Collins Bay, Ontario switch CLBAON02DS0 at V: 4629, H: 2204, which is the +1-613-389 suburban exchange). Sydenham (613-376) and Deseronto (613-396) appear to be just as fictional. If there's no physical exchange building, is there a CLLI for these basically-fictional (but still very much billable) rate centres? K7L (talk) 03:06, 3 June 2013 (UTC)


 * Re your first paragraph, historically, exchanges were located in the area from which cable pairs radiated to homes and businesses. Interexchange connections, normally long distance, would connect each exchange to a toll switch (which depending on hardware might also serve as the local exchange in its own location).  To calculate long distance charges, the location of each exchange - the Rate Centre - was used to calculate the distance, then apply the distance on a table of rate steps.


 * For example, London, Ontario to St. Thomas, Ontario, if it was calculated as 28 miles by the V & H coordinates, then this distance would be checked on the Bell Canada "intra-company" (Ontario, Quebec and eastern NWT) tariff, and found to fall within the, say, 27 to 40 mile rate step, and the rate per minute for that step would be used to rate the call. For a very long time, phone companies have used "route averaged pricing" for long distance rates - though they have different tariffs for intra-company, inter-company, and even more than one tariff for different inter-company.  More on that below.  By route averaged, it means that whatever the distance is between Toronto and Montreal, the rate is the same as between two points in Northern Ontario that are just as far apart, in spite of the fact that the Toronto-Montreal route has a very high line capacity and is very economical compared to the low-capacity lines into northern Ontario communities.


 * (London and St. Thomas are now local to each other, due to Extended Area Service being implemented, consequently raising the rates for local service to cover the higher number of local numbers that can be called.)


 * Nowadays, due to digital technology, local exchanges are often serving only as remotes, sometimes as simple as a digital loop carrier, for an exchange in a different location. Most communities in the Yukon are actually remotes off of one exchange far away, but they function as virtual exchanges on their own, and thus remain their own rate centres.  905-625 and 416-620 would at one time have been separate exchange equipment, but now it is more efficient to run 905-625 off of 416-620, and the technology is smart enough to distinguish them.


 * As to different tariffs, Northwestel, at least from 1992 to 2007, had two intra-company tariffs (Intra 1 is the long-existing schedule for calls within the operating area, Intra 2 was added in 1992 to replace the Bell Canada intra-company schedule for calls within the Eastern Arctic area just acquired from Bell), two adjacent-company tariffs (Adjacent 1 is the long-existing schedule for calls from the original operating area to Alberta and to points in B.C. not served by Northwestel, though it used to also apply to Atlin, BC; Adjacent 2 was added in 1992 to replace the Bell intra-company schedule for calls between the Eastern Arctic area and points in Ontario and Quebec); two Trans-Canada schedules (Trans-Canada 1 was for calls between the original operating area and points in Canada not covered by Intra 1 or Adjacent 1, and applied to the Eastern Arctic until 1992 when it was transferred to the Intra 1 schedule; Trans-Canada 2 is for calls between the Eastern Arctic and points in Canada not covered by Intra 1, Intra 2 or Adjacent 2; when the acquisition occurred in 1992, the rest of the Northwestel operating area moved from the Bell "Northwest" schedule to the Intra 1 schedule); two U.S. schedules (one from the original operating area, one from the Eastern Arctic); two Alaska schedules; two Hawaii schedules. The reason for the two schedules was because Northwestel long distance rates were kept artificially high by the CRTC, while at the same time, Bell was allowed to rebalance its rates with local service rates; when the Eastern Arctic was transferred, the low Bell rates were protected while the Northwestel rates, slowly at first and then more rapidly after 1996, were allowed to be lowered by the CRTC, to the point that they are now nearly identical.  It is possible that someday, they will be amalgamated into eight schedules - Intra, Adjacent 1, Adjacent 2, Trans-Canada 1, Trans-Canada 2, US, Alaska, Hawaii. GBC (talk) 15:41, 7 April 2015 (UTC)


 * Oh, yes, why two "adjacent" definitions for Northwestel? That has to do with natural communications routing.  Northern Canada has a pattern of north-south transportation and communications, rather than east-west.  Highways, airline routes, communications lines, traditionally extended north from the south.  Yukon and the western NWT were originally covered by NPA 403, Alberta's area code, as microwave lines extended in that fashion, and the operators placing long distance calls were in Edmonton (NPA 403 as well).  Bell Canada provisioned service in the east, and extended communication lines from Ontario and Quebec, originally as high-frequency radio and later as satellites; the eastern NWT started as area code 418, but when DDD was introduced, it was on NPA 819.  Until about 1994, calls between the two portions of the Northwestel operating area - say Yellowknife to Iqaluit, routed south to Edmonton, across Canada to Quebec, then north again.  Ontario and Quebec were "adjacent" to the east, while Alberta and B.C. were "adjacent" to the west.  Saskatchewan, Manitoba and the Atlantic provinces were "Trans-Canada" to both east and west areas of Northwestel. GBC (talk) 15:50, 7 April 2015 (UTC))

External links modified
Hello fellow Wikipedians,

I have just modified one external link on CLLI code. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20121021031250/http://www.state.ia.us/government/com/util/docs/misc/NRRIC.pdf to http://www.state.ia.us/government/com/util/docs/misc/NRRIC.pdf

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 16:38, 28 July 2017 (UTC)

Remove SWASONXTSG1 as an example
The site name Swastika is not needed ...either use a different example or just delete

Thanks 69.159.168.200 (talk) 17:47, 23 February 2023 (UTC)