My very informal poll results were as follows:
Use + for everything: 6 votesA "lively" discussion ensued between @ucomsgeek and @CAnthonyCaragol (the C stands for "Corky", in case you were wondering) on the validity of using a + sign in front of numbers that are not dialable from outside the originating country. The discussion got a little crazy and we very nearly came to blows on several occasions. @ucomsgeek had to be admitted to the hospital with what can only be described as an "RFC induced heart palpitation".
No + for emergency/service numbers: 4 votes
It depends: 1 vote
I had traditionally used a + in front of everything, adhering to my mantra of "E.164, E.164, E.164". This included service numbers like 911 in North America, or 112 in Europe, so they would get normalized to +911 and +112. My experiences with SIP providers not wanting a + in front of those numbers made me think, which is a rare occurrence, and is usually followed by being distracted by shiny things. If SIP providers don't want a + in front of those types of numbers, there must be a good reason for it.
So, whenever I'm faced with the great unknown, I turned to the trusty Interweb to find answers. I didn't have to look far. Phone number formatting is governed by the E.164 standard published by the Telecommunication Standardization Sector of the International Telecommunication Union or ITU-T for short (which is a good thing, because having to say "the Telecommunication Standardization Sector of the International Telecommunication Union" gets tiresome). E.164 number representation within the Tel URI format used in SIP is governed by RFC3966 published by the Internet Engineering Task Force (IETF).
Reading these documents is an enlightening and mind-expanding experience. The E.164 standard takes a lot of pages to say that an E.164 number consists of the country code, followed by area code (national destination code or NDC) and the subscriber number.
Other than that, it doesn't say anything about plus signs or anything else other than just boring numbers, so we turn our attention to the much more interesting and relevant RFC3966.
RFC3966 has a lot to say about how to format numbers for use in computer/telecom equipment. The first thing that struck me was that the plus sign is reserved ONLY for global numbers, meaning numbers that are globally unique and adhere to the E.164 standard described above.
Section 5.1 says:
The 'telephone-subscriber' part of the URI indicates the number. The
phone number can be represented in either global (E.164) or local
notation. All phone numbers MUST use the global form unless they
cannot be represented as such. Numbers from private numbering plans,
emergency ("911", "112"), and some directory-assistance numbers
(e.g., "411") and other "service codes" (numbers of the form N11 in
the United States) cannot be represented in global (E.164) form and
need to be represented as a local number with a context. Local
numbers MUST be tagged with a 'phone-context'
Section 5.1.4 describes how to format a global number:
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.
So, since numbers like 911 are not global numbers, they can't be referenced with a plus sign, but have to be formatted with a context, which is described a little bit later.
Section 5.1.5 describes how to format a local number (which includes service/emergency numbers by definition of not being global 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.
Section 5.1.5 goes on to say more about how to format local numbers:
Local numbers MUST have a 'phone-context' parameter that identifies
the scope of their validity. The parameter MUST be chosen to
identify the local context within which the number is unique
unambiguously. Thus, the combination of the descriptor in the
'phone-context' parameter and local number is again globally unique.
The parameter value is defined by the assignee of the local number.
It does NOT indicate a prefix that turns the local number into a
global (E.164) number.
What the above says is that local numbers must use a specific parameter called "phone-context" to ensure there is no ambiguity with global numbers. A little further reading brings up 911 number formatting as an example:
A context consisting of the initial digits of a global number does
not imply that adding these to the local number will generate a valid
E.164 number. It might do so by coincidence, but this cannot be
relied upon. (For example, "911" should be labeled with the context
"+1", but "+1-911" is not a valid E.164 number.)
So, for example, 911 should be formatted as tel:911;phone-context=+1 for North America, but clearly says that +1911 is not acceptable. However, Lync doesn't support phone-context in normalization rules or routing logic (trust me, I tried), so we're kinda stuck if we want to be fully RFC3966 compliant with regards to emergency and service numbers.
We're left with two options for service/emergency numbers really, either use the plus sign or don't. Since the plus sign is supposed to be reserved for global numbers, we probably shouldn't use it for emergency/service numbers. But on the other hand, people are generally used to seeing all their dialed numbers in Lync magically get formatted with a plus sign when it matches up with a normalization rule, which gets taken as a sign that you're good to go (at least that's the way I take it).
But consider this weird little thought experiment. If you normalize 911 to +911, you could think that this represents a really short number within US (country code 91). Yes, I know that a country of more than a billion people is likely going to have more than 9 phones, but you get the idea. What if US decided you could dial the Prime Minister of US by dialing "1"? Then anybody in North America trying to have an engaging conversation with Narendra Modi would end up talking to North American emergency services instead, which would be baffling for both sides.
Another possibility is that you could inadvertently route emergency calls to a global destination. Imagine you have a Lync server in US, and you decide to use least-cost routing to save on toll costs by routing any US-bound call to that Lync server. You configure a route and PSTN usage that sends any call starting with +91 to the US Lync gateway. You inadvertently put that PSTN usage above a PSTN usage meant for local service numbers. Now any call to 911 gets routed to US, and will most likely fail.
You could say the solution to the above scenario is just to make sure that service PSTN usages are above any international PSTN usage, but I'm a fan of engineering solutions that don't rely on someone setting things in exactly the proper order to get the desired results. I'm thinking of administrator/human fault tolerance here.
Rather than say the odds of any given service number conflicting with a real global number is vanishingly small (probably true, but you can't know for certain.....at least until the Lync Optimizer has dial rules for every country in the world), I'd rather ensure with 100% certainty it won't happen, by not putting a plus in front of emergency/service numbers.
Lync will happily route numbers with or without a plus, as long as your routing logic allows for it. You could build your entire Lync Enterprise Voice deployment around not using plus signs at all if you wanted to, but I wouldn't advise it, mostly because of Lync federation. Published phone numbers from federated contacts with a plus sign would not route in a deployment built around not using the plus sign.
So, there you have it. This blog post has convinced me that not using a plus sign for non-global numbers is the way to go. I've updated the Lync Optimizer code to follow this tweak in best practices. What are your thoughts? Does this change your view? Does this very long blog post on the topic of a plus sign make you fear for my sanity? Let me know in the comments.