throughout this description , the embodiments and examples shown should be considered as exemplars , rather than limitations on the apparatus and methods of the present invention . referring now to fig1 there is shown a block diagram of an environment in accordance with the invention . the system includes a client computer 100 , a data network 120 , a web server 130 , a gateway 140 , a switch 150 , a public switched network ( psn ) 160 and plural telephones 170 . the client computer 100 may comprise a general purpose computer . the client computer 100 may be , for example , a pc running a microsoft windows operating system . the client computer 100 may include an output device , such as a display 101 , and an input device , such as a keyboard 102 and / or a pointing device 103 ( e . g ., mouse , track ball , light pen , or data glove ). the client computer 100 may be a computing device such as a workstation , server , portable computer , personal digital assistant ( pda ), computing tablet , two - way messaging device ( e . g ., blackberry ™), smart display terminal , and the like . the client computer 100 connects with and communicates on the data network 120 and includes an interface therefore . the client computer 100 may comprise an assembly of devices , such as a television and a set - top box which interfaces to the data network 120 . the client computer 100 includes software and / or hardware for providing the functionality and features of the invention . the client computer 100 may therefore include one or more of : logic arrays , memories , analog circuits , digital circuits , software , firmware , and processors such as microprocessors , field programmable gate arrays ( fpgas ), application specific integrated circuits ( asics ), programmable logic devices ( plds ) and programmable logic arrays ( plas ). the hardware and firmware components of the client computer 100 may include various specialized units , circuits , software and interfaces for providing the functionality and features of the invention . the invention may be embodied in whole or in part in software which operates on the client computer 100 and may be in the form of an application program , an applet ( e . g ., a java applet ), a browser plug - in , a com object , a dynamic linked library ( dll ), a script , one or more subroutines , an operating system component or service , or a terminate and stay resident program ( tsr ). the hardware and software of the invention and its functions may be distributed such that some components are performed by the client computer 100 and others by other devices . the data network 120 provides lower layer network support for the client computer 100 to interact with other devices , including the web server 130 and the gateway 140 . the data network 120 is packet - switched and may comprise a common or private bi - directional data network , and may be , for example the internet . the web server 130 may be of the type known in the art and has the ability to serve web pages to the client computer 100 , as requested in the manner known in the art . it should be appreciated that the web server 130 is representative of any source of web pages available to the client computer 100 . thus , for example , the web server 130 could be accessible from the internet , or it could be a part of an intranet and represents any number of web servers . the psn 160 is a common carrier network which provides circuit switching and / or ip telephony between public users . the psn 160 may be the public switched telephone network ( pstn ). the psn 160 may operate according to standards such as ss6 or ss7 . the telephones 170 may be ordinary analog telephones connected to the psn . the telephones 170 may be digital devices ( e . g ., sip devices or telephone sets connected through a pbx ) for providing voice communications . the telephones 170 may also be wireless voice communications devices such as cell phones . there may be one or more telephones 175 located proximate the client computer 100 , or in a location under common control of the user of the client computer 100 . the telephone 175 is of the same type as the telephone 170 . the switch 150 may be a voice switch , circuit switch and / or an ip switch and may be compliant with standards such as ss6 or ss7 . the switch 150 is compatible with the psn 160 , and has the ability to set up and tear down telephone connections in the psn 160 . the gateway 140 interfaces between the packet - switched data network 120 and the switch 150 . the gateway 140 may be a signaling gateway platform ( sgp ), which is an intelligent service exchange node that integrates services between circuit and packet networks . the gateway 140 may be integrated into the psn 160 or the switch 150 . referring now to fig2 there is shown a data flow diagram in accordance with the invention . a unit of data 210 is passed through an object packager 220 . the object packager 220 recognizes a telephone number in the data unit 210 and packages a phone number object 230 corresponding to the telephone number . the phone number object 230 may be embedded in the data unit 210 , or may be separate . the phone number object 230 may include one or more telephone numbers . for example , each telephone number in a data unit may correspond to a single object . alternatively , each data unit may have a single phone number object for all of its telephone numbers . alternatively , there may be a single phone number object for all telephone numbers identified by the client computer 100 , or for all telephone numbers for a given application program . by “ data unit ,” it is meant a defined group of data . the data unit 210 must be of a type which can include a telephone number which is displayable on a display ( e . g ., display 101 in fig1 ) and thereby viewable by a human . the data unit 210 may consist only of contiguous text ( e . g ., an ascii text file ), or may consist of a mixture of displayable and non - displayable data ( e . g ., a word processing document ). the data unit may be a file or may be part of a file . the data unit 210 may comprise a number of objects ( e . g ., contact information used in a contact management program ). the text in the data unit 210 may be encoded , such as in ascii . the data unit 210 may be , for example , an email message , an instant message ( im ), a spreadsheet , a web page , a record in a contact management database , or a word processing document . the phone number object 230 may include the telephone number and / or may include a reference to the telephone number within the data unit 210 . the phone number object 230 is defined such that the telephone number is activatable . once activated , a telephone call may be initiated from a trigger from the client computer 100 through the data network 120 to the switch 150 via the gateway 140 . the telephone call may connect the user &# 39 ; s telephone 175 and one or more other telephones 170 via the psn 160 . the trigger may identify the telephone numbers to be dialed . although the phone number object 230 may be considered as an “ object ” in the sense of object - oriented programming , the phone number object 230 may transcend the limitations of object - oriented programming . thus , the phone number object 230 may represent , for example , a flag in a data structure which is used to indicate performance of a separate subroutine . the phone number object 230 may be viewed as including “ hooks ” for allowing initiation of telephone calls using the corresponding telephone number . the phone number object 230 therefore is a shorthand for an attachment between a displayed telephone number and telephone call initiation functions . referring now to fig3 there is shown a flow chart of a method of displaying telephone numbers by the client computer 100 in accordance with the invention . in a first step ( step 310 ), a data unit is presented . a data unit may be “ presented ” when the data unit is passed to a functional unit which will perform later processing . in this case , the functional unit is considered to be passive . alternatively , a data unit may be “ presented ” when a functional unit which will perform later processing fetches the data unit . in this case , the functional unit is considered to be active . all data units available to the client computer 100 may be presented . however , it may be desirable to limit presentation of data units to those of certain characteristics . presentation may be limited or triggered based upon data characteristics such as storage location ( e . g ., specified folders ), file type , file format , data format or file size . presentation may also be limited or triggered based upon events , such as when particular application programs call up data units , or when data units are about to be displayed . when the user makes a selection ( e . g ., of an icon or option ), such selection is referred to as an “ event .” upon the occurrence of an event , an action or command may be initiated . presentation may also be limited or triggered by a combination of data characteristics and events . for example , step 310 may be performed only on word processing documents , spreadsheet documents , email documents , an instant messages ( im ), contact files and web pages . furthermore , step 310 may be further restricted such that it is performed only when the corresponding application is displaying the data unit . next , the data unit is scanned for telephone numbers ( step 320 ). the data unit may be parsed or otherwise processed using one or more algorithms for identifying telephone numbers . for example , the data unit may be scanned for a series of numerals in the exact pattern “( xxx ) xxx - xxxx .” alternatively , a more generic algorithm would search for a series of four or more digits , with no intervening characters except a dash or matched parentheses . the particular algorithm used will depend on a number of factors , including the degree of desired accuracy , the processing capabilities of the client computer , the desired efficiency or speed , and the types of telephones numbers which should be identified . after telephone numbers are identified ( step 330 ), the telephone numbers may be wrapped as phone number objects ( step 340 ). steps 330 - 340 may be performed on all or only a limited number of telephone numbers per data unit . step 340 may be performed on all telephone numbers within a data unit , or may be limited to those telephone numbers having desired qualities . the user may be provided with options to control which data units are processed . this may be useful if the display of a source document must remain true . for example , a user may wish that data units located in a particular folder , or having a particular file format , or having some format of file name , should be skipped . there may be available to the user a display of options , such that the display lists which applications and which file types are available for processing , and the user can make selections or deselections as desired . also , data files may include an indicator that their display should not be altered . steps 310 - 340 are performed automatically , and may always begin or may always be completed before the data unit is displayed . steps 310 - 340 may be performed in conjunction with , as a consequence of , or be triggered by a command , instruction or event to display the data unit . for example , a normal display function may be altered to cause steps 310 - 340 to be performed . when the telephone numbers are displayed as part of a display of the data unit , the telephone numbers have a display attribute which renders the telephone numbers conspicuous to a user ( step 350 ). step 350 may be performed in a number of ways . in one alternative , a normal display of the data unit may be altered prior to display such that the telephone numbers will be conspicuous . for example , just prior to display of a web page , html tags and javascript may be added so that the telephone numbers will be displayed by the browser and provided with appropriate functionality ( e . g . click - to - call ). the format of the tags may follow the standard http :// url format , may have a custom format , or otherwise . the tags may include a target source which determines when and how the telephone call will be initiated . in a second alternative , immediately after a normal display , the telephone numbers or the entire data unit may be redisplayed such that the telephone numbers are conspicuous . in a third alternative , the normal display of the telephone numbers may be overlaid with the conspicuous attributes . a telephone number may be made conspicuous in many ways . for example , the displayed telephone number may have a distinctive color or font , or it may be underlined or highlighted . the telephone number may be displayed such that it appears identical or similar to a hyperlink . the display may be conspicuous at all times , or may be temporary , such as on mouse roll - over . the conspicuous display may be a “ right - click ” menu , so that when a user uses a mouse to click on the telephone number with a secondary mouse button , a menu of options may be displayed adjacent the telephone number . furthermore , different types of telephone numbers may have different attributes . for example , local and toll - free telephone numbers may be displayed in one color ( e . g ., green ), and long distance telephone numbers may have a different color ( e . g ., blue ). once displayed , the user may wish to activate the telephone number . thus , an activation instruction by the user of a displayed telephone number may be detected ( step 360 ). next , a telephone call is caused to be initiated using the displayed telephone number ( step 370 ). referring now to fig4 there is shown a flow chart of a method of displaying an object associated with a telephone number as an active object in accordance with the invention . this method is useful , for example , for databases which have objects such as peoples &# 39 ; names associated with a telephone number . these objects are not telephone numbers or like telephone numbers , but because of their intended usage they are associated with a telephone number . for convenience , these objects will be referred to as “ name objects .” the term “ name objects ” is not limited to names , though . for example , contact management databases typically store records comprising a contact &# 39 ; s name and one or more telephone numbers for the contact . in such a case , it may be desirable to provide streamlined activation of the associated telephone number if the user activates a display of the contact &# 39 ; s name . in this example , the contact &# 39 ; s name is a name object . in a first step ( step 410 ), a data unit is presented in the manner discussed with respect to step 310 ( fig3 ). next , the data unit is scanned for name objects and telephone numbers ( step 420 ), in a manner akin to that discussed with respect to step 320 ( fig3 ). after the name objects and telephone numbers are identified ( step 430 ), the name objects may be wrapped as phone number objects ( step 440 ). steps 430 - 440 may be performed on all or only a limited number of the name objects and the telephone numbers per data unit . step 440 may be performed on all name objects and telephone numbers within a data unit , or may be limited to those name objects and / or telephone numbers having desired qualities . steps 410 - 440 are performed automatically , and may always begin or may always be completed before the data unit is displayed . steps 410 - 440 may be performed in conjunction with , as a consequence of , or be triggered by a command , instruction or event to display the data unit . for example , a normal display function may be altered to cause steps 410 - 440 to be performed . alternatively , steps 410 - 440 may be performed in a database system in conjunction with creating , modifying or accessing records . when the name objects are displayed as part of a display of the data unit , the name objects have a display attribute which renders the name objects conspicuous to a user ( step 450 ) in a manner akin to that discussed with respect to step 350 ( fig3 ). once displayed , the user may wish to activate the name object . thus , an activation instruction by the user of a displayed name object may be detected ( step 460 ). next , a telephone call is caused to be initiated using the telephone number associated with the displayed name object ( step 470 ). although exemplary embodiments of the present invention have been shown and described , it will be apparent to those having ordinary skill in the art that a number of changes , modifications , or alterations to the invention as described herein may be made , none of which depart from the spirit of the present invention . all such changes , modifications and alterations should therefore be seen as within the scope of the present invention .