jeff.wilkinson@medtronic.com (Jeff Wilkinson) (03/23/91)
I'm trying to categorize all the ways that phone numbers can be structured for a mostly-automatic dialing system. We are going to be providing a product where the operator retrieves the number of a patient to be dialed from a database and sends it to the computer. The computer's job is then to dial the number. Sounds trivial, huh? Well, it would be, but we are trying to be as kind to the operator as possible. The Right Way (TM) to do this would have the operator enter the number into the database in the way that it appears in the phone book, adding the area code for numbers that need it (entering the area code is optional for numbers within the local area code). The computer would then take care of all the extra details like: - not doing anything extra for numbers within the PBX. - adding a network access to get outside dial tone, if this is a PBX. - stripping the local area code, if present. - adding a 1, or a WATS access code (in-state and out-state properly differentiated) if this is a toll call. Non-toll calls to different area codes, and intra-area code toll calls need to be considered, also (providing the ability to bypass the default long distance carrier to some areas might be fun, but not crtical). - adding the operator's PBX billing ID number, if required. - accounting for any other foibles introduced by the phone system which I don't know about. I recall that there was a discussion of phone number conventions awhile back in comp.dcom.telecom, but this might have only involved the proper format for international calls. (?). Is there anyone that has experience in this area? Is this a big problem (i.e., I need a large database of area code/exchange vs. area code/exchange tuples) or little? Any ideas? Do PBX's with carrier selection do this? To simplify matters somewhat, the assumption can be made that the device will be calling from North America. International destinations are a possibility, but if this complicates things significantly we'll just tell the operator to do those manually. Unfortunately, we have lost our newsfeed here for the past few months, so replies need to be sent to me directly. If I get some response I'll summarize it at a later date. Jeff Wilkinson jeff.wilkinson@medtronic.com Medtronic, Inc. 7000 Central Ave NE Voice +1-612-574-3770 Minneapolis, MN 5543 FAX +1-612-574-4951 My opinions are my own. Isn't that obvous by now?