Area Code Rules II

[Guest Mark B]

I will try this again with Screenshots, since my first attempt got no proper

responses...

 

Seems Windows, by default, forces a 1 before every area code when dialing

through Oulook, for example. Other than adding every US area code into the

Area Code Rules of the Dialing Properties and unchecking the Dial 1 Before

Area Code box, is there any way to get windows to stop dialing 1 before ALL

area codes?

 

Example Screen Shots in order....

 

http://njycamps.org/temp/1.jpg

 

http://njycamps.org/temp/2.jpg

 

http://njycamps.org/temp/3.jpg

[Guest Frankly Scarlett]

Re: Area Code Rules II

 

Big Question - WHY?

If you are calling within the US, then most likely you need to include a 1

before a long distance call. The 1 tells the phone system that you are

calling outside of your area code. It used to be the 2nd number was limited

to [0,1] for area codes and [2-9] for prefixes. However, with the need for

more phone numbers, they changed things to just a 1 as the first number

means long distance.

 

Windows determines it is a long distance call by looking at the full number

you are calling (415) 555-1212 and the number from your Phone /Modem options

(830) and deciding they are different and therefore a long distance call.

If you are calling a number with the same AC as your settings, then it will

not put in the number.

 

It doesn't cause problems (other than maybe more beeps when it dials). Some

of our users use Earthlink for Dialup. Instead of loading the Earthlink

software, we just create a dial-up connection (j20-30 Meg and causes

conflicts) and put in the numbers we think they will need. We also include

instructions for them to be able to change the phone number they call. This

they can do as an average user. The Earthlink Software requires them to be a

member of Administrators, which is against our policy. We have the numbers

programmed in and we include a comment indicating where that number is for.

When you hover over the number, it will tell you where it is for. The

listing deeper into the dial-up will list the number and the location, as

such:

14155551212 - San Francisco

18305551212 - Monterey

918305551212 - Monterey 9 First (Like in a Hotel)

 

Similarly, you (probably) program your cell phone to include 1 and the AC on

your phone numbers in your address book. If you are in that area code, no

problem. If you are out of that AC, then it dials properly and, again, no

problem.

 

"Mark B" <MarkB@discussions.microsoft.com> wrote in message

news:59337BAA-FC27-4AB4-BD51-68991D675A7D@microsoft.com...

>I will try this again with Screenshots, since my first attempt got no

>proper

> responses...

>

> Seems Windows, by default, forces a 1 before every area code when dialing

> through Oulook, for example. Other than adding every US area code into

> the

> Area Code Rules of the Dialing Properties and unchecking the Dial 1 Before

> Area Code box, is there any way to get windows to stop dialing 1 before

> ALL

> area codes?

>

> Example Screen Shots in order....

>

> http://njycamps.org/temp/1.jpg

>

> http://njycamps.org/temp/2.jpg

>

> http://njycamps.org/temp/3.jpg

>

[Guest HeyBub]

Re: Area Code Rules II

 

Frankly Scarlett wrote:

> Big Question - WHY?

> If you are calling within the US, then most likely you need to

> include a 1 before a long distance call. The 1 tells the phone system

> that you are calling outside of your area code. It used to be the 2nd

> number was limited to [0,1] for area codes and [2-9] for prefixes.

> However, with the need for more phone numbers, they changed things to

> just a 1 as the first number means long distance.

>

> Windows determines it is a long distance call by looking at the full

> number you are calling (415) 555-1212 and the number from your Phone

> /Modem options (830) and deciding they are different and therefore a

> long distance call. If you are calling a number with the same AC as

> your settings, then it will not put in the number.

>

> It doesn't cause problems (other than maybe more beeps when it

> dials). Some of our users use Earthlink for Dialup. Instead of

> loading the Earthlink software, we just create a dial-up connection

> (j20-30 Meg and causes conflicts) and put in the numbers we think

> they will need. We also include instructions for them to be able to

> change the phone number they call. This they can do as an average

> user. The Earthlink Software requires them to be a member of

> Administrators, which is against our policy. We have the numbers

> programmed in and we include a comment indicating where that number

> is for. When you hover over the number, it will tell you where it is

> for. The listing deeper into the dial-up will list the number and the

> location, as such: 14155551212 - San Francisco

> 18305551212 - Monterey

> 918305551212 - Monterey 9 First (Like in a Hotel)

>

> Similarly, you (probably) program your cell phone to include 1 and

> the AC on your phone numbers in your address book. If you are in that

> area code, no problem. If you are out of that AC, then it dials

> properly and, again, no problem.

>

 

Not true.

 

I'm in a city with multiple area codes (Houston). My 'phone number begins

with area code 713. If I try to dial another number within the city, say,

832-555-1212 by placing a "1" in front of the number, I get an intercept

with the message "It is not necessary to dial one before the number. Please

try your call again," then a disconnect.

 

To further complicate the issue, my VoIP lines don't care whether I put a

"1" in front of the number. If I want to call New York, whether I dial

"1212555...." or "212555...." is immaterial.

[Guest Bob I]

Re: Area Code Rules II

 

Perhaps this "workaround"? and just use "FG" for all catagories and then

use the fake "calling card" to make all calls?

 

How to Create Custom Calling Card Rules

http://support.microsoft.com/kb/167220/EN-US/

 

Mark B wrote:

> I will try this again with Screenshots, since my first attempt got no proper

> responses...

>

> Seems Windows, by default, forces a 1 before every area code when dialing

> through Oulook, for example. Other than adding every US area code into the

> Area Code Rules of the Dialing Properties and unchecking the Dial 1 Before

> Area Code box, is there any way to get windows to stop dialing 1 before ALL

> area codes?

>

> Example Screen Shots in order....

>

> http://njycamps.org/temp/1.jpg

>

> http://njycamps.org/temp/2.jpg

>

> http://njycamps.org/temp/3.jpg

>

[Guest Mark B]

Re: Area Code Rules II

 

Not sure why I cant just have someone answer the question, but if you are

just dying to know WHY, the reason is our users have placed too many 911

calls by mistake and we've set up our phone system to prepend the 1

automatically, so with Windows ALSO prepending 1 to every long distance call,

dialing does not work through Outlook.

 

OK, there it is, hope that makes everyone happy. Can I please get an answer

to my question?

 

 

 

"Frankly Scarlett" wrote:

> Big Question - WHY?

> If you are calling within the US, then most likely you need to include a 1

> before a long distance call. The 1 tells the phone system that you are

> calling outside of your area code. It used to be the 2nd number was limited

> to [0,1] for area codes and [2-9] for prefixes. However, with the need for

> more phone numbers, they changed things to just a 1 as the first number

> means long distance.

>

> Windows determines it is a long distance call by looking at the full number

> you are calling (415) 555-1212 and the number from your Phone /Modem options

> (830) and deciding they are different and therefore a long distance call.

> If you are calling a number with the same AC as your settings, then it will

> not put in the number.

>

> It doesn't cause problems (other than maybe more beeps when it dials). Some

> of our users use Earthlink for Dialup. Instead of loading the Earthlink

> software, we just create a dial-up connection (j20-30 Meg and causes

> conflicts) and put in the numbers we think they will need. We also include

> instructions for them to be able to change the phone number they call. This

> they can do as an average user. The Earthlink Software requires them to be a

> member of Administrators, which is against our policy. We have the numbers

> programmed in and we include a comment indicating where that number is for.

> When you hover over the number, it will tell you where it is for. The

> listing deeper into the dial-up will list the number and the location, as

> such:

> 14155551212 - San Francisco

> 18305551212 - Monterey

> 918305551212 - Monterey 9 First (Like in a Hotel)

>

> Similarly, you (probably) program your cell phone to include 1 and the AC on

> your phone numbers in your address book. If you are in that area code, no

> problem. If you are out of that AC, then it dials properly and, again, no

> problem.

>

> "Mark B" <MarkB@discussions.microsoft.com> wrote in message

> news:59337BAA-FC27-4AB4-BD51-68991D675A7D@microsoft.com...

> >I will try this again with Screenshots, since my first attempt got no

> >proper

> > responses...

> >

> > Seems Windows, by default, forces a 1 before every area code when dialing

> > through Oulook, for example. Other than adding every US area code into

> > the

> > Area Code Rules of the Dialing Properties and unchecking the Dial 1 Before

> > Area Code box, is there any way to get windows to stop dialing 1 before

> > ALL

> > area codes?

> >

> > Example Screen Shots in order....

> >

> > http://njycamps.org/temp/1.jpg

> >

> > http://njycamps.org/temp/2.jpg

> >

> > http://njycamps.org/temp/3.jpg

> >

>

>

>

[Guest Mark B]

Re: Area Code Rules II

 

WOW I think this worked!

 

Even though that webpage you sent me too ha sthe wrong steps for WIndows XP,

I think I figured it out, and it is working! I need to test some more, and

then try it on my boss's computer (oh joy) but WOW that seems to be working!

 

THANKS!!!!!!!!!!!!!!!!!!!!!

 

 

 

"Bob I" wrote:

> Perhaps this "workaround"? and just use "FG" for all catagories and then

> use the fake "calling card" to make all calls?

>

> How to Create Custom Calling Card Rules

> http://support.microsoft.com/kb/167220/EN-US/

>

> Mark B wrote:

> > I will try this again with Screenshots, since my first attempt got no proper

> > responses...

> >

> > Seems Windows, by default, forces a 1 before every area code when dialing

> > through Oulook, for example. Other than adding every US area code into the

> > Area Code Rules of the Dialing Properties and unchecking the Dial 1 Before

> > Area Code box, is there any way to get windows to stop dialing 1 before ALL

> > area codes?

> >

> > Example Screen Shots in order....

> >

> > http://njycamps.org/temp/1.jpg

> >

> > http://njycamps.org/temp/2.jpg

> >

> > http://njycamps.org/temp/3.jpg

> >

>

>

[Guest Bob I]

Re: Area Code Rules II

 

You're welcome, I didn't find a "XP" specific workaround, but the

procedure was similar. So I hope it works out satisfactorily.

 

Mark B wrote:

> WOW I think this worked!

>

> Even though that webpage you sent me too ha sthe wrong steps for WIndows XP,

> I think I figured it out, and it is working! I need to test some more, and

> then try it on my boss's computer (oh joy) but WOW that seems to be working!

>

> THANKS!!!!!!!!!!!!!!!!!!!!!

>

>

>

> "Bob I" wrote:

>

>

>>Perhaps this "workaround"? and just use "FG" for all catagories and then

>> use the fake "calling card" to make all calls?

>>

>>How to Create Custom Calling Card Rules

>>http://support.microsoft.com/kb/167220/EN-US/

>>

>>Mark B wrote:

>>

>>>I will try this again with Screenshots, since my first attempt got no proper

>>>responses...

>>>

>>>Seems Windows, by default, forces a 1 before every area code when dialing

>>>through Oulook, for example. Other than adding every US area code into the

>>>Area Code Rules of the Dialing Properties and unchecking the Dial 1 Before

>>>Area Code box, is there any way to get windows to stop dialing 1 before ALL

>>>area codes?

>>>

>>>Example Screen Shots in order....

>>>

>>>http://njycamps.org/temp/1.jpg

>>>

>>>http://njycamps.org/temp/2.jpg

>>>

>>>http://njycamps.org/temp/3.jpg

>>>

>>

>>