This Blog Is Not For Reading

A blog, just like any blog, only more so

  • Subscribe

  • Categories

  • RSS Bob Jonkman’s Microblog

    • bobjonkman repeated a notice by darius 20 February 2019
      RT @darius If I'm typing a bunch of unix command line stuff trying to figure out the right solution, and I eventually DO figure out the solution, one thing I do when possible is re-run the command with a comment like$ doing-the-thing.sh # This is the one that actually worksSo when I inevitably search my […]
    • Favorite 20 February 2019
      bobjonkman favorited something by darius: If I'm typing a bunch of unix command line stuff trying to figure out the right solution, and I eventually DO figure out the solution, one thing I do when possible is re-run the command with a comment like$ doing-the-thing.sh # This is the one that actually worksSo when I […]
    • Favorite 18 February 2019
      bobjonkman favorited something by kat: #tfw you think you know what you are doing... But type reboot on a remote server and your OWN workstation goes off.
    • New note by bobjonkman 18 February 2019
      And as a result I've spent the last two hours watching Emo Phillips on YouTube. https://www.youtube.com/watch?v=9nX_EaFBTPE et al.
    • Favorite 18 February 2019
      bobjonkman favorited something by indi: The second part of my interview with In-Sight Journal's Question Time about the term "Nones" is up! This part's about alternative terms. Looks like only one part left to go! https://medium.com/question-time/ask-mark-2-squeezing-more-some-things-from-nothings-eea9114021ff !atheism
    • Favorite 15 February 2019
      bobjonkman favorited something by clacke: The themes of TOS, TNG, DS9 and VOY all rearranged into one big beautiful thing!invidio.us/watch?v=-SRu_anT0PULots of VOY fans in the comments. 😀I'm overall not a big VOY fan, but it had many good aspects, and the theme music is definitely one of them.
    • bobjonkman repeated a notice by sim 15 February 2019
      RT @sim The less javascript a site uses and/or requires, the better.
    • Favorite 15 February 2019
      bobjonkman favorited something by sim: The less javascript a site uses and/or requires, the better.
    • New note by bobjonkman 11 February 2019
      *sigh*... 20 years ago... #User_Friendly
    • bobjonkman repeated a notice by lnxw37a2 11 February 2019
      RT @lnxw37a2 Every so often, I run across this. I laugh and laugh. I miss #User_Friendly. http://www.userfriendly.org/cartoons/archives/00jan/20000124.html #Depends

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