This Blog Is Not For Reading

A blog, just like any blog, only more so

  • Subscribe

  • Categories

  • RSS Bob Jonkman’s Microblog

    • New note by bobjonkman 13 December 2018
      That was fun! I'm actually working on a for-reals Emergency Broadcast System at @RadioWaterloo -- I'll pass on your video so we can use it as our fallback audio track :)
    • Favorite 12 December 2018
      bobjonkman favorited something by scarlett: always remember "punishable with a fine" means "legal for rich people"
    • New note by bobjonkman 12 December 2018
      I was out. Back to the archives for me.
    • bobjonkman repeated a notice by fdroidorg 11 December 2018
      RT @fdroidorg Do you have experience with #Flatpak? Then we need your help!We want to package #Repomaker as #Flatpak to make it easier for people to install. We already have a running flatpak and are only missing the final bits. Any help is highly appreciated!See "Packaging Repomaker as Flatpak" for more information: https://forum.f-droid.org/t/f-droid-roles/4202
    • bobjonkman repeated a notice by tindall 11 December 2018
      RT @tindall Understanding these things, I feel that it is my duty, to myself and to my community, to reject and replace the products and services of as many spying companies with those of non-spying companies and nonprofit groups as rapidly and thoroughly possible.That can only be done with free software. So, I am a […]
    • Favorite 11 December 2018
      bobjonkman favorited something by tindall: Understanding these things, I feel that it is my duty, to myself and to my community, to reject and replace the products and services of as many spying companies with those of non-spying companies and nonprofit groups as rapidly and thoroughly possible.That can only be done with free software. So, […]
    • bobjonkman repeated a notice by indi 11 December 2018
      RT @indi The 2018 iteration of Indi's alternative holiday playlist has started going up today! Over the next two weeks, 100 holiday songs that are non-religious and don't sound like the standard holiday fare will be featured. https://www.canadianatheist.com/2018/12/indis-alternative-holiday-playlist-2018-100-to-91/ !atheism !secular !SecularHumanism
    • Favorite 11 December 2018
      bobjonkman favorited something by indi: The 2018 iteration of Indi's alternative holiday playlist has started going up today! Over the next two weeks, 100 holiday songs that are non-religious and don't sound like the standard holiday fare will be featured. https://www.canadianatheist.com/2018/12/indis-alternative-holiday-playlist-2018-100-to-91/ !atheism !secular !SecularHumanism
    • bobjonkman repeated a notice by ronhouk 4 December 2018
      RT @ronhouk Just got a grant for my #library to get 15 laptops. they'll be using #Linux and we will be teaching classes on open source software.
    • Favorite 4 December 2018
      bobjonkman favorited something by ronhouk: Just got a grant for my #library to get 15 laptops. they'll be using #Linux and we will be teaching classes on open source software.

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