This Blog Is Not For Reading

A blog, just like any blog, only more so

  • Subscribe

  • Categories

  • RSS Bob Jonkman’s Microblog

    • Favorite 31 July 2019
      bobjonkman favorited something by natecull: Dear everyone who is considering making a video of yourself talking rather than just writing the *exact same words* into a text file, a blog post or a PDF:Unless you're specifically targeting people who literally cannot read...Please don't.Sincerely, A Person Who Doesn't Have Literal Free Hours To Hear You Slooooowly […]
    • Favorite 28 July 2019
      bobjonkman favorited something by kensanata: I recommend people just turn off voice assistants whenever they can. That includes smart watches and the like! If you don’t depend on them, then there always the chance of activating them by mistake and of voice samples getting sent and stored where they don’t belong and listened to by […]
    • bobjonkman repeated a notice by floxadvocate 27 July 2019
      RT @floxadvocate Happy System Administrator DayToday, please remember to thank the professionals who keep your computers and network functioning https://sysadminday.com/https://www.sys-admin-day.de/https://www.LOPSA.org/#sysadm #LOPSA
    • Favorite 27 July 2019
      bobjonkman favorited something by floxadvocate: Happy System Administrator DayToday, please remember to thank the professionals who keep your computers and network functioning https://sysadminday.com/https://www.sys-admin-day.de/https://www.LOPSA.org/#sysadm #LOPSA
    • Favorite 17 July 2019
      bobjonkman favorited something by wolfie: @ink_slinger also "blood is thicker than water" is actually short for "The blood of the covenant is thicker than the water of the womb" which means that friendship formed in hardship is stronger than family bonds, the exact opposite of the shorthandAnd curiosity killed the cat used to stop people […]
    • Favorite 17 July 2019
      bobjonkman favorited something by inkslinger: "Pull yourself up by your bootstraps" was originally satire because that is, um, impossible. It's now stated without irony."Just a few bad apples," when referring to police, conveniently ignoring the full aphorism ials actually: One bad apple *spoils the bunch.*
    • Favorite 27 June 2019
      bobjonkman favorited something by selfcare: Fix something small that gets in your way. Sew on a button, clean a grimy keyboard.
    • New note by bobjonkman 27 June 2019
      Just this once, only for this video and no other, should you #ReadTheComments!https://youtu.be/1OfxlSG6q5Y
    • bobjonkman repeated a notice by gudenau 27 June 2019
      RT @gudenau @dirb @Loki This is what a real toaster is like. https://youtu.be/1OfxlSG6q5Y
    • Favorite 27 June 2019
      bobjonkman favorited something by gudenau: @dirb @Loki This is what a real toaster is like. https://youtu.be/1OfxlSG6q5Y

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