This Blog Is Not For Reading

A blog, just like any blog, only more so

  • Subscribe

  • Categories

  • RSS Bob Jonkman’s Microblog

    • Favorite 16 August 2018
      bobjonkman favorited something by mcnees: Follow-up: George Paget Thomson, one of the physicists who experimentally confirmed wave behavior of the electron, was the son of J. J. Thomson, the physicist credited with verifying that the electron is a distinct particle.Dad showed that the electron is a particle, and his son, in an act of filial […]
    • bobjonkman repeated a notice by silverwizard 16 August 2018
      RT @silverwizard ♲ @Ed Maste (ed_maste@twitter.com): #FreeBSD folks - would you come to a hackathon in Kitchener-Waterloo or Hamilton the week before or after BSDCan 2019 (which is May 14-19)?
    • New note by bobjonkman 15 August 2018
      This article is just so full of good, pithy pullquotes: "Those hoping to make positive social change have to convince people both that something in the world needs changing and there is a constructive, reasonable way to change it. Authoritarians and extremists, on the other hand, often merely have to muddy the waters and weaken […]
    • New note by bobjonkman 15 August 2018
      How very true: "in the 21st century it is the flow of attention, not information (which we already have too much of), that matters." https://www.technologyreview.com/s/611806/how-social-media-took-us-from-tahrir-square-to-donald-trump/
    • Favorite 15 August 2018
      bobjonkman favorited something by d3jblog: ♲ @zeynep tufekci (zeynep@twitter.com): "Power always learns, and powerful tools always fall into its hands. This is a hard lesson of history but a solid one." My new piece on the digital road from Obama '08 to Tahrir to Trump—for MIT @techreview. #longform technologyreview.com/s/611806/how-s… https://www.technologyreview.com/s/611806/how-social-media-took-us-from-tahrir-square-to-donald-trump/ https://www.technologyreview.com/s/611806/how-social-media-took-us-from-tahrir-square-to-donald-trump/
    • bobjonkman repeated a notice by d3jblog 15 August 2018
      RT @d3jblog ♲ @zeynep tufekci (zeynep@twitter.com): "Power always learns, and powerful tools always fall into its hands. This is a hard lesson of history but a solid one." My new piece on the digital road from Obama '08 to Tahrir to Trump—for MIT @techreview. #longform technologyreview.com/s/611806/how-s… https://www.technologyreview.com/s/611806/how-social-media-took-us-from-tahrir-square-to-donald-trump/ https://www.technologyreview.com/s/611806/how-social-media-took-us-from-tahrir-square-to-donald-trump/
    • bobjonkman repeated a notice by liamerven 15 August 2018
      RT @liamerven Hey #Fediverse. When you post pictures, please please please with puppies on top fill in that description box for the visually impaired. You will be helping us out tremendously. We want to enjoy your pictures as much as others do. You don't have to write a novel, but just fill in some details.Thanks […]
    • Favorite 15 August 2018
      bobjonkman favorited something by liamerven: Hey #Fediverse. When you post pictures, please please please with puppies on top fill in that description box for the visually impaired. You will be helping us out tremendously. We want to enjoy your pictures as much as others do. You don't have to write a novel, but just fill […]
    • Favorite 15 August 2018
      bobjonkman favorited something by jb55: just deleted my google account from my phone... so far it seems the world did not end.
    • Favorite 15 August 2018
      bobjonkman favorited something by startuplab: You probably radically underestimate:- How much you know that other people don't.- How valuable it is for you to publish it.

Archive for March, 2010

Telephone Number Format Standards

Posted by Bob Jonkman on 20th March 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.

Posted in code, smtp, telephone, valid html | 4 Comments »

 
Better Tag Cloud