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 30 May 2023
      I'd be more inclined to say "people voting the way the polls said they should..."
    • bobjonkman repeated a notice by hubert 30 May 2023
      RT @hubert I have to laugh and shake my head at Smith calling it a "Miracle on the Praries". No, you were leading in the polls pretty much the whole time. You're in a strongly conservative province. I mean, if you're saying that it's a miracle that the majority of Albertans chose to ignore your […]
    • bobjonkman repeated a notice by blacksam 28 May 2023
      RT @blacksam I’ve been getting more into the game Gaslands with my son and also with adult friends. It’s a Mad Max-esque tabletop game where you’re expected to create your own game pieces by kitbashing with toy cars. I already have all the crafting, painting and 3d printing supplies I need from my other wargaming […]
    • Favorite 28 May 2023
      bobjonkman favorited something by blacksam: I’ve been getting more into the game Gaslands with my son and also with adult friends. It’s a Mad Max-esque tabletop game where you’re expected to create your own game pieces by kitbashing with toy cars. I already have all the crafting, painting and 3d printing supplies I need from […]
    • Favorite 28 May 2023
      bobjonkman favorited something by blacksam: Here are a couple more cars I've made for #gaslands
    • Favorite 28 May 2023
      bobjonkman favorited something by tobias: I'm in need of a little Nerd-Pr0n... what little useful thing comes into your mind as tool of at the Linux command line? Not a super-nerdy command to sophisticated resolve a problem, but a tool for actual problems that would also be useful for n00bs to take their fear about […]
    • bobjonkman repeated a notice by tobias 28 May 2023
      RT @tobias I'm in need of a little Nerd-Pr0n... what little useful thing comes into your mind as tool of at the Linux command line? Not a super-nerdy command to sophisticated resolve a problem, but a tool for actual problems that would also be useful for n00bs to take their fear about using the CLI?So […]
    • Favorite 23 May 2023
      bobjonkman favorited something by steve: From mcnees@mastodon.social on Mastodon: If you aren't too busy, take a minute to look through NASA's Project Apollo archive on Flickr. https://www. flickr.com/photos/projectapoll oarchive/albums This is a totally safe use of your time, you definitely won't look up two hours from now and ask where your morning went. Images: NASA
    • bobjonkman repeated a notice by geniusmusing 9 May 2023
      RT @geniusmusing @lnxw48a1 I have my own workaround for just this issue. I raise my hand to the "Stop/Hold" position. Get to a point where I can stop and leave myself a note on the next thing to do. Then let them interrupt me. I have even done this to my former boss and the […]
    • Favorite 9 May 2023
      bobjonkman favorited something by lnxw48a1: https://www.monkeyuser.com/2018/focus/ This is me.

Archive for the 'telephone' Category

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