Dialing rules

[Wai Doan Hsu]

How do I tell Windows which area codes are local and which are long
distance in the dialing rules?

 

[Austin M. Horst]

Read the Help first:
Click [Start]
Help
Click the Index tab
Type area codes, rules overview
Also see area codes, specifying rules

Click [Start]
Settings
Control Panel
Phone and Modem Options
Click the Dialing Rules tab
Select a location (create a new one if none exists)
Click [Edit...]
Click the Area Code Rules tab

It's easiest to just have the PC dial 1 plus the area code
all the time. 1-234-555-0000
That works whether it's long distance or local.
You might have to dial all numbers that way if you live in
certain parts of the United States where "Overlay" area
codes are used.


Austin M. Horst

 

[Wai Doan Hsu]

Read the Help first:
Click [Start]
Help
Click the Index tab
Type area codes, rules overview
Also see area codes, specifying rules

Click [Start]
Settings
Control Panel
Phone and Modem Options
Click the Dialing Rules tab
Select a location (create a new one if none exists)
Click [Edit...]
Click the Area Code Rules tab

It's easiest to just have the PC dial 1 plus the area code
all the time. 1-234-555-0000
That works whether it's long distance or local.
You might have to dial all numbers that way if you live in
certain parts of the United States where "Overlay" area
codes are used.


Austin M. Horst

That's not what I'm asking, though. I asked how do I tell Windows
which area codes are local and which are long distance in the dialing
rules.

I have several area codes that are local to me. My phone system
allows me to pick a location when I first configure it. For that
location, I can set any rules that Windows will let me set. But I
can't figure out how to tell it which area codes are local.

It's not a matter of dialing an area code or not. If I tell Windows
to use a credit card for long distance and international, it will do
what I want providing that Windows actually knows what calls are long
distance and which ones are not. The part I can't figure out is how
to tell Windows which area codes are local. For me, local and long
distance calls are determined by distance, not by whether I need to
dial an area code.

 

[John C.]

Windows does not determine if you are charged for a call,
the phone company does. If you dial a "local" or toll-free
number using a calling card or credit card, you are not
going to be charged for the call.
But it's not neccessary to dial all those numbers if you
don't have to, so specify a seperate rule for local, long-
distance, and international calls.
See Calling Cards in Windows Help.

 

[Wai Doan Hsu]

Windows does not determine if you are charged for a call,
the phone company does. If you dial a "local" or toll-free
number using a calling card or credit card, you are not
going to be charged for the call.
But it's not neccessary to dial all those numbers if you
don't have to, so specify a seperate rule for local, long-
distance, and international calls.
See Calling Cards in Windows Help.

Each company that issues a calling card has its own rules on how much
it charges. Mine charges for all calls. I don't want to use it for
local calls because it costs me money.

I know that Windows does not determine if I am charged for a call.
Sort of. Windows does decide what is local and long distance. If I
tell Windows to use a calling card number for long distance calls,
Windows needs to know what numbers are long distance. If it thinks
that local calls are long distance calls, then it is in effect
determining if I am charged for a call or not since it is using my
calling card information to place a local call.

I've already looked at all the Windows help. I have one remaining
question, which is the one I've been asking from the beginning. How
do I tell Windows what numbers are local and what are long distance?
I've already specified a different rule for local, long distance, and
international calls. But if Windows doesn't know which is which, it
does no good.

 

[Wai Doan Hsu]

Each company that issues a calling card has its own rules on how much
it charges. Mine charges for all calls. I don't want to use it for
local calls because it costs me money.

I know that Windows does not determine if I am charged for a call.
Sort of. Windows does decide what is local and long distance. If I
tell Windows to use a calling card number for long distance calls,
Windows needs to know what numbers are long distance. If it thinks
that local calls are long distance calls, then it is in effect
determining if I am charged for a call or not since it is using my
calling card information to place a local call.

I've already looked at all the Windows help. I have one remaining
question, which is the one I've been asking from the beginning. How
do I tell Windows what numbers are local and what are long distance?
I've already specified a different rule for local, long distance, and
international calls. But if Windows doesn't know which is which, it
does no good.

In case I did not make it clear, I DO have to use an area code for
local calls with a different area code. And obviously not all calls
with a different area code are local. So how do I get Windows to
recognize that even though I am specifying an area code, I do not want
it to look at the calling card information for long distance, if it is
not long distance? If other area codes are required to be dialed, but
are still local calls, how can I get Windows to know this?