Interexchange carrier

Interexchange carrier (IXC) is a U.S. legal and regulatory term for a telecommunication company, commonly called a long-distance telephone company. It is defined as any carrier that provides services across multiple local access and transport areas (interLATA). Calls made on telephone circuits within the local geographic area covered by one local network are handled only by that intraLATA carrier, commonly called a local telephone exchange carrier. Local calls are usually defined by connections made without additional charge whether the connected call is in the same LATA or connects to another LATA with no charge. IntraLATA usually refers to rated or toll calls between LATA within state boundaries, as opposed to interstate, or calls between LATAs in different states.

Call handling

An IXC carries traffic, usually voice traffic, between telephone exchanges. Telephone exchanges are usually identified in the United States by the LATA indicated by three-digit area code (NPA) and the first three digits of the phone number (NPA-NXX) within the LATA. Different exchanges generally cover different geographic locations, connected as separate central offices (COs, also called "wire centers").

IXCs originally carried voice traffic on analog lines, but voice traffic has since become largely digitized. Therefore, voice traffic is more typically a data stream and can be intermixed with data traffic such as uplinks for DSL. Most commonly, links between IXCs and COs are ATM links carried on optical fiber.

For voice traffic transfer, IXCs use softswitches and VoIP protocols and error correction. ITSPs can thereby connect between VoIP to POTS, computer to computer, computer to phone, and IP devices to other phone services.[1]

Carrier identification code

Each carrier (interexchange or local exchange) is assigned a four-digit identification code, the Carrier Identification Code (CIC) which was used with feature groups. The interexchange carrier to which calls from a subscriber line are routed by default is known as the Presubscribed Interexchange Carrier (PIC). To give telephone users the possibility of opting for a different carrier on a call-by-call basis, Carrier Access Codes (CAC) were devised. These consist of the digits 101 followed by the four-digit CIC. The CAC is dialed as a prefix immediately before dialing a long-distance phone number.

In popular usage, CACs are often referred to as dial-around codes (because they allow dialing around the PIC). Sometimes they are even called "PIC codes", though this term is inaccurate, since the code is being used to avoid the PIC, not to use its services.

When CICs were first introduced in 1983, they were only three digits long, and the CAC consisted of the digits 10 followed by the three-digit CIC. In 1998, the CIC had to be extended to four digits. Existing carriers' codes were prefixed with 10. Thus, a pre-1998 CAC of the form 10-XXX became 101-0XXX.[2] Since the CACs starting with 10-10 are generally the oldest and best-known ones, CACs are sometimes referred to as 10-10 codes.

Use of CACs is popular with telephone users who wish to avoid paying a regular monthly fee for access to inexpensive long-distance service. They can also be useful if encountering a "circuits busy" condition when all long distance trunks are tied up; a CAC allows selection of an alternate carrier, which may have other open long-distance trunks. This feature gave rise to slamming and the lesser known cramming technique of telephone fraud.

As multiple competitive long-distance carriers have been permitted in countries other than the United States, schemes similar to the CIC/CAC have spread worldwide. They are now used in (among other countries) Canada, Germany, and Japan.

Although CACs are no longer widely used, PICs and CICs are still common.

gollark: `myVariable = () => { myVariable = "MWAHAHAHAHA" }`
gollark: Not a well-typed one, at least.
gollark: Because you literally cannot write a general function `max` which returns the biggest of two numbers.
gollark: `if err != nil { return err }`, `lol no generics`, and `if x > y { return x } else { return y }`, yes.
gollark: Oh, Go has awful error handling and really hates abstracting things too, that's another difference from JS.

See also

References

  1. "About Softswitches in general". IXC. 19 September 2012.
  2. See the FCC's FAQ on the subject.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.