This Blog Is Not For Reading

A blog, just like any blog, only more so

  • Subscribe

  • Categories

  • RSS Bob Jonkman’s Microblog

    • Delete 27 August 2023
      Bob Jonkman deleted notice {{tag:gs.jonkman.ca,2023-08-27:noticeId=1114720:objectType=note}}.
    • New note by bobjonkman 3 August 2023
      From a few years ago... All gone now, and I promised $SPOUSE it would never come back. https://gs.jonkman.ca/attachment/221480
    • Favorite 3 August 2023
      bobjonkman favorited something by clacke: I tried for over four decades to grow an impressive personality, but it was a lot of effort and not much payoff, so now I'm just trying to grow an impressive beard instead.
    • bobjonkman repeated a notice by clacke 3 August 2023
      RT @clacke I tried for over four decades to grow an impressive personality, but it was a lot of effort and not much payoff, so now I'm just trying to grow an impressive beard instead.
    • bobjonkman repeated a notice by clacke 27 July 2023
      RT @clacke did you watch Oppenheimer, the film about the moral implications of the things we create, starring an actor who also played a Gotham City psychiatrist who went insaneordid you watch Barbie, the film about the moral implications of the things we create, starring an actress who also played a Gotham City psychiatrist who […]
    • Favorite 27 July 2023
      bobjonkman favorited something by clacke: did you watch Oppenheimer, the film about the moral implications of the things we create, starring an actor who also played a Gotham City psychiatrist who went insaneordid you watch Barbie, the film about the moral implications of the things we create, starring an actress who also played a Gotham […]
    • New comment by bobjonkman 29 June 2023
      @steve Wait, you or Dr. Cooley are at Perimeter? Giving any public lectures? If so, I'll hop on my bike to attend! @Perimeter
    • bobjonkman repeated a notice by steve 29 June 2023
      RT @steve From jodi on Mastodon: I’m looking forward to meeting students at TRISEP 2023 being held @Perimeter!
    • New note by bobjonkman 8 June 2023
      Several other authors of software that accesses the Twitter API have come to that conclusion as well. When #Twidere, my phone app to access Twitter stopped accessing Twitter back in January I pretty much abandoned Twitter. I still check Twitter with its WebUI, less than once a week, but I no longer post or engage […]
    • Favorite 8 June 2023
      bobjonkman favorited something by steve: I finally had a chance to figure out why my social bridging software was no longer able to talk to Twitter. Indeed, it's because under Twitter's new leadership, python-twitter has been deemed as violating something in their terms of service. It says I can submit a ticket, but they make […]
«
»

Telephone Number Format Standards

Posted by Bob Jonkman on March 20th, 2010

Telephone Dial

Standardized Telephone Number formats work even on old phones!

There are many different address books and directories online, and there are almost just as many different ways they store telephone numbers. I guess most people don’t realize that there are actually standards for representing phone numbers. A little bit of standardization would go a long way towards interoperability.

The standard for phone number formatting is set by the International Telecommunication Union in [E.123] and [E.164] (see the references below). The standards documents are available for a fee from the ITU [available at no charge since 2010 –Bob.] . A summary is available in the Google (UseNet) discussion group, titled Need ITU-T E.123 summary.

In short, a North American telephone number should look like:

+C-AAA-PPP-NNNN;ext=xxxx

  • “+” shows where the dialing prefix goes. This is one of either the International Direct Dialing (IDD) prefix (for Canada this is “011” for overseas dialing) or the National Direct Dialing (NDD) prefix (“1” for calls within North America, omitted for toll-free calls),
  • “C” is the Country Code (North America’s CC is “1”, and it is omitted for dialing within North America),
  • “AAA” is the area code (always required for dialing in Kitchener, Toronto, and other jurisdictions),
  • “PPP” is the Exchange (or Private Branch Exchange “PBX”; look in the phone book to see which exchanges are supported),
  • “NNNN” is the local portion of the number,
  • “;ext=” optionally identifies the next portion as an extension and “xxxx” are the digits for that extension. This syntax is usable in URIs and e-mail.

Note that the sequence “AAA-PPP-NNNN” is called a “local number” and “+C-AAA-PPP-NNNN” is called a “global number”. The “-” (hyphen) is a visual separator, as are “.” (period) , “(” (left bracket) and “)” (right bracket), which dialing applications should ignore.

I’m mostly interested in making phone number formats in e-mail addressbooks compliant with e-mail standards. The document that covers this is the IETF’s [RFC3191], "Minimal GSTN address format in Internet Mail" . The requirement is that GSTN (Global Switched Telephone Network) numbers use the global-number syntax (“+C-AAA-PPP-NNNN”).

Global-number GSTN numbers can be used for other purposes as well, such as Web page URIs. See [RFC3966], "The tel URI for Telephone Numbers". This document re-iterates that:

5.1.4.
Global Numbers Globally unique numbers are identified by the leading “+” character. Global numbers MUST be composed with the country (CC) and national (NSN) numbers as specified in E.123 [E.123] and E.164 [E.164]. Globally unique numbers are unambiguous everywhere in the world and SHOULD be used.
5.1.5.

Local Numbers Local numbers are unique only within a certain geographical area or a certain part of the telephone network, e.g., a private branch exchange (PBX), a state or province, a particular local exchange carrier, or a particular country. URIs with local phone numbers should only appear in environments where all local entities can successfully set up the call by passing the number to the dialling software. Digits needed for accessing an outside line, for example, are not included in local numbers. Local numbers SHOULD NOT be used unless there is no way to represent the number as a global number.

Local numbers SHOULD NOT be used for several reasons. Local numbers require that the originator and recipient are configured appropriately so that they can insert and recognize the correct context descriptors. Since there is no algorithm to pick the same descriptor independently, labelling numbers with their context increases the chances of misconfiguration so that valid identifiers are rejected by mistake. The algorithm to select descriptors was chosen so that accidental collisions would be rare, but they cannot be ruled out.

If you work at a company that does work with organizations and staff members outside of the context of your area code (ie. internationally) be sure to standardize your directory on global-number syntax.

–Bob.

Need a consultant? Bob Jonkman can be reached by telephone at +1-519-635-9413

References:

Image: Telephone Dial by Leo Reynolds, used under Creative Commons v2.0 BY-NC-SA.

This entry was posted on Saturday, March 20th, 2010 at 1:42 am and is filed under code, smtp, telephone, valid html. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

«
»
 
Better Tag Cloud