Tel. Dialer design prob for Split Area Codes

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

The area code rules do not support the new Split Area Codes that have evolved
recently, where part of an area code is local, and other part of an area code
requires a +1. This design causes all calls to an area code to either dial
+1 when only part of an area code requires it. This leads to frustrating
error messages from the telephone company, telling me not to dial the +1
prefix for some calls.

Suggestion: Create a "split area code" flag, which when set, allows the
user to put a +1 in the phone directory for just those phone numbers in that
area code that require it.
 
Hi John,

Today (12/3/04) I posted the following-"How do I add 1 before long distance
numbers?" I have been unable to get the dialing rules to add a "1" before
toll free numbers. Also, I learned, when I tried to dial an 800 number after
thinking I'd set the rules to place a "1" in front, that the "1" was not
applied and instead an "800" local number was dialed. I'm not sure if these
difficulties are because these "toll free" numbers are being phased out (Why
else have a conflict?) or there is a glitch in Outlook that doesn't allow
auto-entry of a "1" before the area code.

At any rate I don't quite understand what you mean by a "split area code
flag". Would that be, for example, represented as a checkmark in a dialog
box designating that the number is not local? The question that would have
to be answered is: "Is this a local number? If not check here.", or
something to that effect.
 
Wally said:
Hi John,

Today (12/3/04) I posted the following-"How do I add 1 before long distance
numbers?" I have been unable to get the dialing rules to add a "1" before
toll free numbers. Also, I learned, when I tried to dial an 800 number after
thinking I'd set the rules to place a "1" in front, that the "1" was not
applied and instead an "800" local number was dialed. I'm not sure if these
difficulties are because these "toll free" numbers are being phased out (Why
else have a conflict?) or there is a glitch in Outlook that doesn't allow
auto-entry of a "1" before the area code.

At any rate I don't quite understand what you mean by a "split area code
flag". Would that be, for example, represented as a checkmark in a dialog
box designating that the number is not local? The question that would have
to be answered is: "Is this a local number? If not check here.", or
something to that effect.
Click to expand...

12/4/05 - John adds:
Example of split area code:
407 area code in Orlando FL - Orlando & North - dial 407-NNX-XXXX
407 area code south of orlando - dial 1+407-NNX-XXXX (not a local call)
South of Orlando, 1+407 is an intrastate toll call
North of Orlando, 407 is a local call, but Area code is always required in
Florida.

At the contact level, the user should be able to flag one 407 number as local
and another as 1+407 and have outlook remember the difference. Right now,
outlook only remembers whether the last 407 number dialed required a 1 or
not.
You cannot have two different rules for the same area code
 
Outlook is not in play here. All dialing and processing of rules is
handled by the OS.
 
Back
Top