Quote:
|
You have no way of knowing who is responsible for the glitch that created the error. It could have been a phone company switching error for all you know.
|
Yes, I do know because I ask and I work in telephony.
Lets say the person lives in a 543 area code. The destination phone number is 869-444-3920 and because he' s on a base (that of course has its own PBX or equivalent) he has to dial out to the LEC be it by 9 or 8 etc.
So the person dials out with an 8-869-444-3920 to what he/she knows is a long distance number (because of the differnt NPA or area codes) execpt they do not dial a 1 before the number. You ALWAYS have to dial 1 before a long distance number, the LEC has to have that to deliver onto long distance trunking (landlines). So instead of dialing 869-444-3920 , the LEC/switch assumes a 7 digit local number and tries connecting to 869-4443. If that happens to be a valid NXX-XXXX then VOILA! the call completes.
Its a very simple system that in 3 1/2 years the people at my local military base has proved over and over to not understand. No, its not a LEC issue VC, its the person dialing the number issue.
BTW, if a piece of paper shows UIC, UNIT DESIGNATION, HS, MOB PAX Station and arrival information, coordinates etc etc would that bne considered important info ?? I think it probably is and the military guy I work with does too.