Hypothetical situation...

[pulse8]

I know that City Y is local, so otherwise I wouldn't choose that city, obviously.

Exactly.

My point is that it's not the responsibility of the ISP to know how every area code in this country is billed to another, they just need to know they exist. It's up to the person who's dialing their service to know how their long distance works.

 

[ThisIsMatt]

Originally posted by: Zenmervolt
How can you not know just by the number that it's long distance? You don't know which exchanges are local? I thought that this was basic stuff that everyone knew.

ZV

If by exchanges you mean prefixes, it's not possible. My area code covers a lot of places, local and long distance.

 

[Pers]

Originally posted by: GroundZero
my setup shows me the number being dialed, and i would have noticed if it was dialing a 1 first anyway.
not to mention the fact that i would have had to enable the modem to call long distance, and have given it permissions for calling the area code involved...
if you were stupid enough to think that an area code that wasn't the same as yours was going to be local, then eat the bill.
maybe you will have learned from your mistake.

what does that have to do with being stupid? if you're pathetic enough to take pride with your so called intelligence (or lack of) in such a pointless topic

you would know that just because the area code of the number used is different than the one of your area, doesn't mean the call is no longer local.

however, just because the area code is the same, still doesn't mean the number is local. I definately believe the person is at fault. If they were smart

(they'd probably need to be smarter than GroundZero tho

) they would have called the phone company to ask if the numbers they used were

local or not.

 

[ThisIsMatt]

Originally posted by: pulse8

I know that City Y is local, so otherwise I wouldn't choose that city, obviously.

Exactly.

My point is that it's not the responsibility of the ISP to know how every area code in this country is billed to another, they just need to know they exist. It's up to the person who's dialing their service to know how their long distance works.

I don't think you're following me. The ISP generates a list in a given area code, that's normal. However, their list is erroneus and states that City Y has a local number 555-5555, when in fact 555-5555 corresponds to City A in the same area code.

 

[bunker]

Bottom line is it's you who is making the call. It's your responsibility to check the number.

 

[Hammer]

you're fscked. your isp is not gonna pay for it. you might be able to neogiate something with the phone company though.

 

[Zenmervolt]

Originally posted by: ThisIsMatt

Originally posted by: Zenmervolt
How can you not know just by the number that it's long distance? You don't know which exchanges are local? I thought that this was basic stuff that everyone knew.

ZV

If by exchanges you mean prefixes, it's not possible. My area code covers a lot of places, local and long distance.

The exchange is the three digits after the area code. (xxx) yyy-zzzz. The "yyy" is the exchange.

ZV

 

[pulse8]

Originally posted by: ThisIsMatt

Originally posted by: pulse8

I know that City Y is local, so otherwise I wouldn't choose that city, obviously.

Exactly.

My point is that it's not the responsibility of the ISP to know how every area code in this country is billed to another, they just need to know they exist. It's up to the person who's dialing their service to know how their long distance works.

I don't think you're following me. The ISP generates a list in a given area code, that's normal. However, their list is erroneus and states that City Y has a local number 555-5555, when in fact 555-5555 corresponds to City A in the same area code.

I follow you and I'm telling you it's not their responsibility to know what's long distance for you and what isn't. If they made a mistake, it's the users responsibility to know what's local to their area.

 

[ThisIsMatt]

Originally posted by: Pers

Originally posted by: GroundZero
my setup shows me the number being dialed, and i would have noticed if it was dialing a 1 first anyway.
not to mention the fact that i would have had to enable the modem to call long distance, and have given it permissions for calling the area code involved...
if you were stupid enough to think that an area code that wasn't the same as yours was going to be local, then eat the bill.
maybe you will have learned from your mistake.

what does that have to do with being stupid? if you're pathetic enough to take pride with your so called intelligence (or lack of) in such a pointless topic

you would know that just because the area code of the number used is different than the one of your area, doesn't mean the call is no longer local.

however, just because the area code is the same, still doesn't mean the number is local. I definately believe the person is at fault. If they were smart

(they'd probably need to be smarter than GroundZero tho

) they would have called the phone company to ask if the numbers they used were

local or not.

I would bet, if people were honest, 99.9% of dialup users would trust that if the ISP says #555-5555 is in local city Y, then they would use that number without first checking.

 

[Zenmervolt]

Originally posted by: ThisIsMatt

Originally posted by: Pers

Originally posted by: GroundZero
my setup shows me the number being dialed, and i would have noticed if it was dialing a 1 first anyway.
not to mention the fact that i would have had to enable the modem to call long distance, and have given it permissions for calling the area code involved...
if you were stupid enough to think that an area code that wasn't the same as yours was going to be local, then eat the bill.
maybe you will have learned from your mistake.

what does that have to do with being stupid? if you're pathetic enough to take pride with your so called intelligence (or lack of) in such a pointless topic

you would know that just because the area code of the number used is different than the one of your area, doesn't mean the call is no longer local.

however, just because the area code is the same, still doesn't mean the number is local. I definately believe the person is at fault. If they were smart

(they'd probably need to be smarter than GroundZero tho

) they would have called the phone company to ask if the numbers they used were

local or not.

I would bet, if people were honest, 99.9% of dialup users would trust that if the ISP says #555-5555 is in local city Y, then they would use that number without first checking.

Mark me as being in that 0.01% then. I always check. I live outside of a city in a rural area. The ISP listings for the local city are about half long distance and half local. (Half the city is long distance, half isn't.) I always check the exchange.

ZV

 

[bunker]

I would bet, if people were honest, 99.9% of dialup users would trust that if the ISP says #555-5555 is in local city Y, then they would use that number without first checking

I will agree with you. As I said in a previous post I did the same damn thing. But I didn't even think about blaming the ISP for it, I knew it was my own stupidity.

I called and schmoozed the phone company and they took the charges off.

 

[ThisIsMatt]

Originally posted by: pulse8

Originally posted by: ThisIsMatt

Originally posted by: pulse8

I know that City Y is local, so otherwise I wouldn't choose that city, obviously.

Exactly.

My point is that it's not the responsibility of the ISP to know how every area code in this country is billed to another, they just need to know they exist. It's up to the person who's dialing their service to know how their long distance works.

I don't think you're following me. The ISP generates a list in a given area code, that's normal. However, their list is erroneus and states that City Y has a local number 555-5555, when in fact 555-5555 corresponds to City A in the same area code.

I follow you and I'm telling you it's not their responsibility to know what's long distance for you and what isn't. If they made a mistake, it's the users responsibility to know what's local to their area.

No, you're not following me. No sh!t it's not their responsibility to know what's long distance to me. That is NOT THE ISSUE. The issue is that they said # 555-5555 is in city Y, when in fact it's NOT in city Y.

 

[ThisIsMatt]

Originally posted by: Zenmervolt

Originally posted by: ThisIsMatt

Originally posted by: Zenmervolt
How can you not know just by the number that it's long distance? You don't know which exchanges are local? I thought that this was basic stuff that everyone knew.

ZV

If by exchanges you mean prefixes, it's not possible. My area code covers a lot of places, local and long distance.

The exchange is the three digits after the area code. (xxx) yyy-zzzz. The "yyy" is the exchange.

ZV

Ok, there are about 50 different exchanges in my area code. Want to memorize which ones are local and which aren't?

 

[pulse8]

Originally posted by: ThisIsMatt

Originally posted by: pulse8

Originally posted by: ThisIsMatt

Originally posted by: pulse8

I know that City Y is local, so otherwise I wouldn't choose that city, obviously.

Exactly.

My point is that it's not the responsibility of the ISP to know how every area code in this country is billed to another, they just need to know they exist. It's up to the person who's dialing their service to know how their long distance works.

I don't think you're following me. The ISP generates a list in a given area code, that's normal. However, their list is erroneus and states that City Y has a local number 555-5555, when in fact 555-5555 corresponds to City A in the same area code.

I follow you and I'm telling you it's not their responsibility to know what's long distance for you and what isn't. If they made a mistake, it's the users responsibility to know what's local to their area.

No, you're not following me. No sh!t it's not their responsibility to know what's long distance to me. That is NOT THE ISSUE. The issue is that they said # 555-5555 is in city Y, when in fact it's NOT in city Y.

That's not the issue! The issue is that some numbnut used their service with that number not knowing that it was long distance for them, which brings us back to my point. It's not their responsibility to know what's long distance for you. If they've made a mistake, it's up to the user at that point to know that it's not near them.

 

[Zenmervolt]

Originally posted by: ThisIsMatt

Originally posted by: Zenmervolt

Originally posted by: ThisIsMatt

Originally posted by: Zenmervolt
How can you not know just by the number that it's long distance? You don't know which exchanges are local? I thought that this was basic stuff that everyone knew.

ZV

If by exchanges you mean prefixes, it's not possible. My area code covers a lot of places, local and long distance.

The exchange is the three digits after the area code. (xxx) yyy-zzzz. The "yyy" is the exchange.

ZV

Ok, there are about 50 different exchanges in my area code. Want to memorize which ones are local and which aren't?

How can you not know by experience? You don't have to know which one's aren't, just know which one's are local. If you're not sure, dial with the telephone and don't dial a "1" before the number, if you get an error message, then it's long distance. If you get a modem, it's local. It's 20 seconds of work max. It's not like I sit down and memorise the local exchanges, I just always check the one's I'm not sure about. It's not rocket science, and it's not time consuming.

ZV

 

[ThisIsMatt]

Originally posted by: Zenmervolt

Originally posted by: ThisIsMatt

Originally posted by: Pers

Originally posted by: GroundZero
my setup shows me the number being dialed, and i would have noticed if it was dialing a 1 first anyway.
not to mention the fact that i would have had to enable the modem to call long distance, and have given it permissions for calling the area code involved...
if you were stupid enough to think that an area code that wasn't the same as yours was going to be local, then eat the bill.
maybe you will have learned from your mistake.

what does that have to do with being stupid? if you're pathetic enough to take pride with your so called intelligence (or lack of) in such a pointless topic

you would know that just because the area code of the number used is different than the one of your area, doesn't mean the call is no longer local.

however, just because the area code is the same, still doesn't mean the number is local. I definately believe the person is at fault. If they were smart

(they'd probably need to be smarter than GroundZero tho

) they would have called the phone company to ask if the numbers they used were

local or not.

I would bet, if people were honest, 99.9% of dialup users would trust that if the ISP says #555-5555 is in local city Y, then they would use that number without first checking.

Mark me as being in that 0.01% then. I always check. I live outside of a city in a rural area. The ISP listings for the local city are about half long distance and half local. (Half the city is long distance, half isn't.) I always check the exchange.

ZV

See, and that's different. The cities that are local to me are X, Y, Z, etc, and they're local as a whole. If you give me a city, I can tell you if it's local or not. Give me a prefix and I'll have to look it up for sure. But if you tell me you're in city Y and give me your number, I guess I'm an idiot for believing that you live in city Y when really you were lying and live in city H across the state, but in the same area code.

 

[ThisIsMatt]

Originally posted by: Zenmervolt

Originally posted by: ThisIsMatt

Originally posted by: Zenmervolt

Originally posted by: ThisIsMatt

Originally posted by: Zenmervolt
How can you not know just by the number that it's long distance? You don't know which exchanges are local? I thought that this was basic stuff that everyone knew.

ZV

If by exchanges you mean prefixes, it's not possible. My area code covers a lot of places, local and long distance.

The exchange is the three digits after the area code. (xxx) yyy-zzzz. The "yyy" is the exchange.

ZV

Ok, there are about 50 different exchanges in my area code. Want to memorize which ones are local and which aren't?

How can you not know by experience? You don't have to know which one's aren't, just know which one's are local. If you're not sure, dial with the telephone and don't dial a "1" before the number, if you get an error message, then it's long distance. If you get a modem, it's local. It's 20 seconds of work max. It's not like I sit down and memorise the local exchanges, I just always check the one's I'm not sure about. It's not rocket science, and it's not time consuming.

ZV

I don't have to dial a 1 to reach long distance numbers in the same area code, it's not even set up to dial a 1.

 

[Zenmervolt]

Originally posted by: ThisIsMatt

Originally posted by: Zenmervolt

Originally posted by: ThisIsMatt

Originally posted by: Pers

Originally posted by: GroundZero
my setup shows me the number being dialed, and i would have noticed if it was dialing a 1 first anyway.
not to mention the fact that i would have had to enable the modem to call long distance, and have given it permissions for calling the area code involved...
if you were stupid enough to think that an area code that wasn't the same as yours was going to be local, then eat the bill.
maybe you will have learned from your mistake.

what does that have to do with being stupid? if you're pathetic enough to take pride with your so called intelligence (or lack of) in such a pointless topic

you would know that just because the area code of the number used is different than the one of your area, doesn't mean the call is no longer local.

however, just because the area code is the same, still doesn't mean the number is local. I definately believe the person is at fault. If they were smart

(they'd probably need to be smarter than GroundZero tho

) they would have called the phone company to ask if the numbers they used were

local or not.

I would bet, if people were honest, 99.9% of dialup users would trust that if the ISP says #555-5555 is in local city Y, then they would use that number without first checking.

Mark me as being in that 0.01% then. I always check. I live outside of a city in a rural area. The ISP listings for the local city are about half long distance and half local. (Half the city is long distance, half isn't.) I always check the exchange.

ZV

See, and that's different. The cities that are local to me are X, Y, Z, etc, and they're local as a whole. If you give me a city, I can tell you if it's local or not. Give me a prefix and I'll have to look it up for sure. But if you tell me you're in city Y and give me your number, I guess I'm an idiot for believing that you live in city Y when really you were lying and live in city H across the state, but in the same area code.

Oh, I'm sorry. I didn't realise that the only way for this to happen was deliberate mis-information by the ISP.

Did it ever occur to you that this was an accident? Take some responsibility.

ZV

 

[Nutdotnet]

Nevermind.

Postcount +1

BUT...that is ODD that you don't have to dial a 1 for long distance. Hell, my entire state is one area code and I still have to dial a 1.

 

[ThisIsMatt]

Originally posted by: Zenmervolt

Originally posted by: ThisIsMatt

Originally posted by: Zenmervolt

Originally posted by: ThisIsMatt

Originally posted by: Pers

Originally posted by: GroundZero
my setup shows me the number being dialed, and i would have noticed if it was dialing a 1 first anyway.
not to mention the fact that i would have had to enable the modem to call long distance, and have given it permissions for calling the area code involved...
if you were stupid enough to think that an area code that wasn't the same as yours was going to be local, then eat the bill.
maybe you will have learned from your mistake.

what does that have to do with being stupid? if you're pathetic enough to take pride with your so called intelligence (or lack of) in such a pointless topic

you would know that just because the area code of the number used is different than the one of your area, doesn't mean the call is no longer local.

however, just because the area code is the same, still doesn't mean the number is local. I definately believe the person is at fault. If they were smart

(they'd probably need to be smarter than GroundZero tho

) they would have called the phone company to ask if the numbers they used were

local or not.

I would bet, if people were honest, 99.9% of dialup users would trust that if the ISP says #555-5555 is in local city Y, then they would use that number without first checking.

Mark me as being in that 0.01% then. I always check. I live outside of a city in a rural area. The ISP listings for the local city are about half long distance and half local. (Half the city is long distance, half isn't.) I always check the exchange.

ZV

See, and that's different. The cities that are local to me are X, Y, Z, etc, and they're local as a whole. If you give me a city, I can tell you if it's local or not. Give me a prefix and I'll have to look it up for sure. But if you tell me you're in city Y and give me your number, I guess I'm an idiot for believing that you live in city Y when really you were lying and live in city H across the state, but in the same area code.

Oh, I'm sorry. I didn't realise that the only way for this to happen was deliberate mis-information by the ISP.

Did it ever occur to you that this was an accident? Take some responsibility.

ZV

So I have to take responsibilty for their mistake? Do you care that the ISP isn't even apologetic for making the mistake and made no effort to say they would correct it?

 

[bunker]

[/quote]So I have to take responsibilty for their mistake? Do you care that the ISP isn't even apologetic for making the mistake and made no effort to say they would correct it?[/quote]

Disclaimer: The display of a number does not mean that it is a flat-rate local call. That determination can only be made by your local telephone provider.

 

[ThisIsMatt]

Originally posted by: Nutdotnet
Nevermind.

Postcount +1

BUT...that is ODD that you don't have to dial a 1 for long distance. Hell, my entire state is one area code and I still have to dial a 1.

No, I do not have to dial a 1 OR the area code to reach this number.

 

[pulse8]

So I have to take responsibilty for their mistake? Do you care that the ISP isn't even apologetic for making the mistake and made no effort to say they would correct it?

Why should they be apologetic for your ignorance?

 

[ThisIsMatt]

Originally posted by: bunker

So I have to take responsibilty for their mistake? Do you care that the ISP isn't even apologetic for making the mistake and made no effort to say they would correct it?[/quote]

Disclaimer: The display of a number does not mean that it is a flat-rate local call. That determination can only be made by your local telephone provider.[/quote]So they might as well just hash out a bunch of phone numbers and have you sort through them looking for a local one, because that's basically what they've done by providing incorrect numbers for local cities.

 

[Zenmervolt]

So I have to take responsibilty for their mistake? Do you care that the ISP isn't even apologetic for making the mistake and made no effort to say they would correct it?

Judging from this thread, I can think of some obvious reasons as to why they aren't apologetic.

Regardless of whether or not their listing was in error, the final determination of whether it was a local call was your responsibility. Welcome to life.

ZV