US20020049768A1 - Method and apparatus for identifying and replying to a caller - Google Patents
Method and apparatus for identifying and replying to a caller Download PDFInfo
- Publication number
- US20020049768A1 US20020049768A1 US09/789,050 US78905001A US2002049768A1 US 20020049768 A1 US20020049768 A1 US 20020049768A1 US 78905001 A US78905001 A US 78905001A US 2002049768 A1 US2002049768 A1 US 2002049768A1
- Authority
- US
- United States
- Prior art keywords
- caller
- reply
- voice
- message
- identifying
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/48—Arrangements for recalling a calling subscriber when the wanted subscriber ceases to be busy
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/53—Centralised arrangements for recording incoming messages, i.e. mailbox systems
- H04M3/533—Voice mail systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
- H04M2201/40—Electronic components, circuits, software, systems or apparatus used in telephone systems using speech recognition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2242/00—Special services or facilities
- H04M2242/22—Automatic class or number identification arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2242/00—Special services or facilities
- H04M2242/30—Determination of the location of a subscriber
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/38—Graded-service arrangements, i.e. some subscribers prevented from establishing certain connections
- H04M3/382—Graded-service arrangements, i.e. some subscribers prevented from establishing certain connections using authorisation codes or passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42025—Calling or Called party identification service
- H04M3/42034—Calling party identification service
- H04M3/42042—Notifying the called party of information on the calling party
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42025—Calling or Called party identification service
- H04M3/42034—Calling party identification service
- H04M3/42059—Making use of the calling party identifier
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42229—Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42314—Systems providing special services or facilities to subscribers in private branch exchanges
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/53—Centralised arrangements for recording incoming messages, i.e. mailbox systems
- H04M3/533—Voice mail systems
- H04M3/53325—Interconnection arrangements between voice mail systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/53—Centralised arrangements for recording incoming messages, i.e. mailbox systems
- H04M3/533—Voice mail systems
- H04M3/53333—Message receiving aspects
- H04M3/53341—Message reply
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/53—Centralised arrangements for recording incoming messages, i.e. mailbox systems
- H04M3/533—Voice mail systems
- H04M3/53333—Message receiving aspects
- H04M3/5335—Message type or catagory, e.g. priority, indication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/0024—Services and arrangements where telephone services are combined with data services
- H04M7/0036—Services and arrangements where telephone services are combined with data services where the data service is an information service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/009—Arrangements for interconnection between switching centres in systems involving PBX or KTS networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/72—Finding out and indicating number of calling subscriber
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99943—Generating database or data structure, e.g. via user interface
Definitions
- the present invention relates to voice messaging, and in particular to a method and apparatus for responding to both internal (those from within the same voice messaging system) and external voice messages (those from outside the voice messaging system).
- a voice mail system provides a voice mailbox that allows an inbound voice message to be stored when the user is away from the receiving telephone or in the event a busy signal is encountered by a caller, so that the recipient can learn of the call.
- the caller may also choose to leave a message directly in the voice mailbox of the recipient of the call when a “live call” is not necessary or desired.
- VMS Voice over IP Services
- a recipient of an internal call from another person having an account on the same VMS to listen to a message stored in his or her voice mailbox and, by operating the keys on a telephone keypad, to initiate a reply to the message.
- the recipient does not need to identify the extension of the source of the call because the VMS supplies the source extension.
- an internal call is generally identified by the extension from which the call was placed (source/extension), not the caller. Thus, if the caller did not use his or her own phone, a reply would be sent to the calling extension, not to caller's personal extension.
- a receiver can reply with a “live call” to the calling extension by pressing keys on the number pad and being directly connected.
- a message direct to the voice mail box of the calling extension can be created by pressing the appropriate keys to initiate the reply command; the recipient records the reply message and hangs up; the VMS automatically sends the recorded reply message to the voice mailbox of the calling extension.
- this reply feature is only available for calls between users having accounts on the same VMS (internal callers), and only when the voice message includes a return voice mailbox address of the original calling location.
- Recipients of calls from external callers people external to the VMS
- the recipient cannot automatically send a reply to such messages since the reply feature cannot identify the source of the call. Rather, the recipient must listen to the message, write down the name and number of the caller and then after hanging up, call back the person who left the message.
- Voice messaging also allows internal communication from one caller to multiple recipients on the same VMS system without the caller initiating a call to each individual recipient's voice mailbox.
- Two or more VMSs of a similar type may be connected together to operate as a single VMS.
- the two VMSs can be at different locations.
- the network may operate through, for example, a dial up (e.g., analog line) connection, or a digital connection (e.g., an Integrated Services Digital Network (ISDN) lines).
- a dial up e.g., analog line
- a digital connection e.g., an Integrated Services Digital Network (ISDN) lines.
- ISDN Integrated Services Digital Network
- AMIS Audio Messaging Interchange Specification
- AMIS-A available for analog telephone lines (AMIS-A) or for a digital network (AMIS-D).
- AMIS-A protocol distributes messages via a voice dial-up line; Dual Tone Multi Frequency (DTMF) tones are used for signaling.
- DTMF Dual Tone Multi Frequency
- voice message networking does not allow a receiver of a message to automatically reply to caller on a different VMS. Therefore, a person on a VMS can receive an internal message (i.e., from a caller on a same VMS or VMS network) and an external message (i.e., from a different VMS, mobile phone, home phone, etc.), but cannot reply in the same manner to each type of message.
- an internal message i.e., from a caller on a same VMS or VMS network
- an external message i.e., from a different VMS, mobile phone, home phone, etc.
- a recipient of a call is provided with the ability to reply to an internal or external voice message in a common manner.
- a caller generated identifier is used to search a database for caller information.
- a method for forming a reply to a voice message on a first voice mail system including the steps of identifying a caller, retrieving information related to the identified caller, and providing the retrieved information to a second voice mail system information to enable a call recipient to reply to the voice message.
- a method of retrieving information about a caller includes the steps of identifying a calling location of the caller, recording a vocal utterance made by the caller and accessing a database as a function of the identified calling location and the recorded vocal utterance.
- a method of replying to a caller includes the steps of identifying a calling location of the caller, storing a vocal utterance made by the caller, accessing a database as a function of the identified calling location and the recorded vocal utterance to retrieve caller information, wherein the caller information includes a caller reply location and sending a reply to the caller reply location.
- a method of storing a single voice mail message from a caller includes the steps of identifying a calling location of the caller, recording a spoken name uttered by the caller, accessing a database as a function of the identified location and the recorded spoken name to retrieve the caller information and recording a message uttered by the caller and storing the recorded spoken name and the recorded message information together as a single voice mail message.
- a system for retrieving information about a caller includes means for identifying a calling location of the caller, means for storing a vocal utterance made by the caller and means for accessing a database as a function of the identified calling location and the recorded vocal utterance.
- a system for replying to a caller includes means for identifying a calling location of the caller, means for recording a vocal utterance made by the caller, means for accessing a database as a function of the identified calling location and the recorded vocal utterance to retrieve caller information, wherein the caller information includes a caller reply location and means for sending a reply to the caller reply location.
- the calling location is different from the caller reply location.
- the reply is an electronic mail message or a recorded message.
- the caller reply location is a voice mailbox.
- the vocal utterance is converted to a string of characters, wherein the database is accessed as a function of the string of characters.
- the voice utterance is identified using speaker verification or speech recognition to access the database.
- FIG. 1 is a block diagram of a voice messaging system according to one embodiment of the present invention.
- FIG. 2 is a flowchart illustration of a process for replying to a voice message
- FIG. 3 is an example process for adding a voice signature to a voice message
- FIG. 4 is a block diagram of a call handling reply system in a telephone environment at a customer location
- FIG. 5 is a block diagram of a call handling reply system connected to a remote office that does not have a VMS;
- FIG. 6 is a block diagram of a call handling reply system connected to a remote office through a central office;
- FIG. 7 is a block diagram of a call handling reply system connected to a remote office having a VMS;
- FIG. 8 is a block diagram of a call handling reply system connected to an AMIS-A compliant VMS;
- FIG. 9 is a block diagram of multiple call handling reply systems configured between a headquarters office and multiple remote offices.
- FIG. 10 is a representation of caller information stored in a voice directory database.
- a method and apparatus for identifying a caller is provided to allow a common method of replying to internal (from a same voice mail system) and external (from a different voice mail system or external to the voice mail system) calls.
- a call handling reply system intercepts incoming messages and provides caller information, including a return address, to a Voice Mail System (VMS).
- VMS Voice Mail System
- the caller may be identified (at least in part) by his/her spoken name which is used to search a database of caller information.
- a system 10 for handling phone calls of user 1 includes a Private Branch Exchange (PBX) 110 , a call handling reply system 115 , a voice mail system (VMS) 120 and a VPIM interface 125 .
- a second system 20 for user 2 includes a PBX 155 , a call handling reply system 115 , a voice mail system 145 and a Voice Profile for Interface Mail Extension (VPIM) interface 140 .
- the PBXs 110 , 155 may be connected by either analog or digital lines 111 , 154 to the call handling reply systems 1115 .
- PBX systems 110 , 155 may be replaced by other electronic switching or computer devices connected directly to a Local Area Network (LAN) to distribute calls.
- LAN Local Area Network
- Each user of the PBX may use a single call handling reply system.
- the call handling reply system 115 may be connected to the voice mail systems 120 , 145 over a T1, T1 and RS-232, or an analog and RS-232 serial connection 116 , 147 .
- call handling reply system 115 may operate with only one VMS and one PBX system.
- the voice mail systems 120 , 145 may be connected to the VPIM interfaces 125 , 140 through connections 121 , 141 .
- the VPIM interface may also be embedded in its respective VMS which would allow the VMS to be connected directly to voice directory database 135 .
- the VPIM interfaces 125 , 140 are connected to a data network 130 , e.g., an internet, and communicate using the VPIM protocol. In one embodiment, a proprietary protocol may be used.
- a voice directory database 135 is provided and is connected to the data network 130 through connection 131 . Additionally, the voice directory database 135 is connected to the call handling reply systems 115 through connections 112 , and communicate using a standard or proprietary database protocol. PBXs 110 , 155 are connected to a Public Switch Telephone Network (PSTN) 160 via connections 108 , 158 , respectively.
- PSTN Public Switch Telephone Network
- PSTN 160 is commonly accessed by telephones, fax machines and PBX systems.
- user 1 places a call to user 2; user 1 and user 2 being connected through PBX 110 , PSTN 160 and PBX 155 .
- the call handling reply systems 115 provide a hardware and software interface between the PBXs 110 , 155 and VMSs 120 , 145 as described in greater detail below.
- the call handling reply systems 115 handle calls on PBXs 110 , 155 ; they identify the caller and the reason the call was sent to the call handling reply systems (e.g., busy, no answer, forwarded, etc.) and they enable VMSs 120 or 145 to reply to the call in a common manner, regardless of whether the call is internal (i.e., from the same VMS system) or external (i.e., from outside the VMS, e.g., mobile phone, home phone, etc.).
- the call handling reply systems 115 handle calls on PBXs 110 , 155 ; they identify the caller and the reason the call was sent to the call handling reply systems (e.g., busy, no answer, forwarded, etc.) and they enable VMSs 120 or 145 to reply to the call in a common manner, regardless of whether the call is internal (i.e., from the same VMS system) or external (i.e., from outside the VMS, e.g., mobile phone, home phone, etc.).
- VPIM Voice Profile for Internet Mail
- EMA Electronic Messaging Association
- VPIM Voice Profile for Internet Mail
- EMA Electronic Messaging Association
- VPIM Voice Profile for Internet Mail
- ESMTP/MIME Enhanced Simple Mail Transport Protocol/Multiple Purpose Internet Mail Extension
- VPIM allows VMSs with different priorities, delivery standards and features to communicate according to a caller's messaging expectations as defined by the caller's VMS. Without VPIM, messages can only be transferred between same type VMSs made by the same manufacturer, using a common proprietary protocol.
- VPIM interface 125 connects VMS 120 through data network 130 (e.g., the Internet) to VPIM interface 140 .
- a service provider such as Unifi Communications, Inc., Lowell, Mass.
- the service provider may maintain a voice directory database of callers so that a VMS may access a voice mail address of a caller.
- Service providers may provide global customer information to local users to allow messaging and replying to messages in a global environment.
- service providers may communicate with other service providers to update customer information in voice directory databases and to ensure that the service providers can communicate with each other when necessary. Other methods of automatically or manually updating the voice directory database may be used.
- Voice directory database 135 is accessible by call handling reply systems 115 through data network (e.g., Internet) protocol connections 127 and 132 , or directly through database protocol connections 112 .
- Voice directory database 135 provides caller information, including a reply address, to the call handling reply system 115 that has queried voice directory database 135 in order to identify the caller.
- an automatic number identification (ANI), caller identification (CID), or other known method of identification of the telephone call is associated with the caller location (step 206 ).
- the ANI/CID is used to identify the calling extension and does not necessarily identify the actual caller. For example, if an employee of a business placed a call, the ANI/CID for the call would only give information related to the company's main number, although it might possibly identify an extension from which the call was placed. The ANI/CID, however, does not necessarily identify the actual caller placing the call.
- step 207 a determination is made as to whether or not the called party, user 2, is able to answer the call, i.e., busy, no answer, or calls forwarded. If user 2 is available, the process proceeds to step 208 where the caller is connected and a “live call” will ensue.
- call handling reply system 115 intercepts the call in step 209 , and receives information about the call from PBX 110 , including ANI/CID information and the reason for the call (e.g., busy, forwarded, no answer, etc.).
- Call handling reply system 115 requests the caller (i.e., user 1) to speak his or her name.
- call handling reply system 115 records the spoken name. In an alternate embodiment, any tones which uniquely identify a caller in a secure manner may be recorded by the call handling system in step 212 .
- the caller record may include information such as the caller name, company name, caller address, a recording of the caller's spoken name in a voice file, direct telephone number and voice mailbox number.
- the entries in the voice directory database may be updated by a standard service provider or may be dynamically updated by users of the database.
- the database is not limited to any particular format or look up protocol.
- One example of a hierarchial directory that may be used is an X500 directory by Control Data Systems; the X500 directory may be accessed, for example, using Lightweight Directory Access Protocol (LDAP) developed by Netscape.
- LDAP Lightweight Directory Access Protocol
- a caller record in voice directory database 135 may also include information pertaining to how to handle calls to a voice mailbox. For example, conditions to forward some calls or all calls based on a caller's identity may be included in the caller record. An option which is listed as caller research may be chosen to allow an operator to attempt to register an unidentified caller through a series of questions by the operator.
- Voice directory database 135 may include information regarding usual caller expectations for message handling; these may be initially defined at the time a caller is entered into the voice directory database. For example, different VMSs may include different features or the features may be defined differently. By defining user preferences in the database, the desired information is automatically obtained when the caller information is retrieved by a call handling reply system.
- a preference may be a caller that requests a message to be delivered to a different mailbox location, for example, a person traveling for an extended period of time, or to support an all-in-one mailbox.
- Voice directory database 135 may also perform feature normalization which can resolve problems when a feature has a different meaning on different systems.
- a priority definition may instruct a VMS to deliver the message immediately, while another VMS may define a priority as a message that must be delivered within sixty minutes.
- VPIM allows these caller expectations to be communicated so as to allow a call to be handled according to the caller's expectations.
- Voice directory database 135 may also include dialing plans of callers accessing the database.
- the dialing plans identify the callers in a manner to prevent mishandled calls due to same phone numbers or extensions assigned to different callers at different locations.
- the database may be arranged to uniquely identify each VMS caller and may store entries by relating potential callers with potential recipients.
- a caller may be identified by a node number, a physical address number and/or a dial plan number.
- any numbers that are the same in any two nodes are resolved to allow unique identification of each caller.
- a service provider may assign each address a prefix to be appended to a destination address. If a company does not add a prefix, the service provider may maintain default prefixes for a given company.
- the caller's identity cannot be identified merely by the ANI/CID found in step 206 .
- the combination of the identified ANI/CID along with the voice signature recorded in step 212 can be used however to search the voice directory database 135 .
- all entries having the ANI/CID identification are retrieved from the voice directory database 135 to create a smaller temporary directory database, (step 215 ).
- the phone number being called may be used to create a smaller temporary directory database in step 215 .
- an ANI/CID number may not be available.
- any caller identifier such as any tones which uniquely identify a caller in a secure manner which are recorded by the call handling system 115 (in step 212 ), may used to search the database.
- the temporary database includes only a list of text names taken from the voice directory database 135 .
- This temporary database would include a list of hose names from the voice directory database 135 which matched the ANI/CID and another list based on the phone number being called.
- the temporary database may include the list of names identified by the ANI/CID, as well as the associated caller records.
- step 218 the call handling reply system searches text names in the temporary database (created in step 215 ) using the recorded spoken name of the caller; the spoken name was recorded by the call handling reply system in step 212 .
- the process of identifying a caller's text name in a database from a recorded spoken name may be performed by a variety of technologies such as speech recognition and/or speaker verification. In other words, the spoken name is connected to text.
- the spoken name may be processed by a speech recognition system such as ReCite by Pure Speech, or by similar speech recognition systems by Lernout and Hauspie, Dragon Systems or IBM.
- the speech recognition system recognizes what name is spoken, but does not distinguish who has spoken the name.
- Such a system operates by matching phonemes, which are the smallest increments of speech that distinguish one utterance from another in a language or dialect.
- a speaker verification system may also be used to identify not only what is spoken, but also who has spoken it and may be used to identify a situation when a caller speaking a name is not that person. Speaker verification could be used in applying a higher level of security to the system.
- the caller it is determined if the caller can be identified from the names in the temporary database in step 221 . If the caller's name is found in the list of names in the temporary database (step 221 ), then the entry in the voice directory database 135 related to the caller name is retrieved (step 239 ).
- the retrieved caller information may include a previous recording of the spoken name, the caller's name, telephone number, reply mailbox address and other caller information.
- the voice directory database does not need to be accessed in this step.
- the information retrieved in step 239 is used to create a Simplified Message Desk Interface (SMDI) data packet.
- This data packet includes information such as the reply address of the caller (e.g., user 1) and will be used to allow the recipient (e.g., user 2) of the voice mail message to reply to the voice mail message left by the external caller (e.g., user 1).
- the data packet may also include a date/time stamp and special handling instructions (e.g., urgent, private, etc.).
- the call is then transferred, step 245 , to user 2's VMS 145 with the data packet.
- VMS 145 receives the call and prompts the caller to record a message.
- the caller records the message in step 248 .
- the recorded spoken name will be appended to any voice mail message the caller creates so as to act as a voice signature for the caller.
- the caller is invited to leave a message.
- the recorded name becomes part of the voice mail message and may be transported with the message sent from the voice mail system.
- a voice signature as part of the voice mail message allows an unidentified caller (e.g., user 1) to be identified by their voice signature when the called party (e.g., user 2) retrieves the message from the VMS.
- the voice signature may be stored in the voice directory database 135 for future use. For example, the voice signature may be used by the recipient when composing a reply message to verify the reply message is being sent to the correct caller.
- the recipient of the message may listen to the recorded message in step 251 and then may press reply keys to reply to the recorded message in step 254 .
- the keys pressed by the recipient may be any keys that allow a reply to a message, either a live return call or a message for user 1's voice mail box, such that the recipient no longer needs to distinguish between a message from an internal or an external caller.
- the recipient is either connected or may record a reply message in step 257 .
- the call handling reply system may be identifying a caller as the caller is recording a message.
- the reply message is sent to the original caller in step 260 .
- the recipient creating the reply message may verify the return caller information. For example, after retrieving a message from the caller, the call handling reply system may prompt the recipient to verify the caller. The recipient may press a key to hear the voice signature recorded by the caller associated with the recorded message. The recipient may then determine if the voice signature is the caller to whom the recipient wants to reply. If it is, then the recipient may compose a reply message. If not, the recipient may still choose to reply or may choose to independently make a live call or to create a new message.
- the reply message may be sent to a service provider, such as the operator of voice directory database 135 for forwarding to the original caller, as discussed above in connection with the voice directory database 135 .
- the reply message is sent using a VPIM interface to a data network, such as the Internet, and then sent to the VMS of the original caller, or over analog phone lines to the caller.
- step 221 when the caller cannot be identified from the entries in the temporary database based on a search for the caller name, the caller is prompted to input a return phone number in step 224 .
- the return phone number is entered by pressing the keys on the phone to generate DTMF signals.
- the voice directory database 115 is searched in step 227 to determine if the caller can be identified. If an entry matching the return phone number is found in the database in step 230 , then the caller is identified and the process continues at step 239 in which the caller information, including the reply address, is retrieved as discussed above.
- step 230 the call is passed to the VMS 145 in step 233 .
- the return address of the caller is not passed to VMS 145 . Therefore, in step 235 , the caller records the message on VMS 145 and the reply feature is unavailable to the recipient of the message. The recipient may still reply to the message if desired by alternate methods, e.g., listening to the message where user 1 has left a number where he can be reached.
- an outbound delivery message system may be used.
- An address of a service provider e.g., the operator of a voice directory database
- VMS 145 is provided to VMS 145 with the voice mail message from the caller who cannot be identified in the database 135 .
- a recipient of the voice mail message chooses to reply to the message, then the reply message is sent to the address of the service provider.
- the service provider may then use a computer system to automatically call a phone number associated with the original caller in order to provide the reply message to the caller.
- the reply message is provided as a live call to the original caller based on a telephone number entered by the original caller or after research is performed by a service provider, can be delivered to the original caller's voice mail box.
- an operator may intercept the call when the caller cannot be identified by a search of the voice directory database 135 .
- the operator may request information to allow the caller to be entered into the voice directory database 135 along with any associated information about the caller to allow the reply feature to work when the recipient attempts to reply to the call.
- the information may include, for example, the name of the caller, voice mail address, return phone number, and VPIM address (e.g., a standard E-mail address, usually a phone number at a domain address).
- the voice directory database 135 is then manually or automatically updated with the caller information and a data packet is sent with the voice message to VMS 145 .
- FIG. 1 The voice messaging system shown in FIG. 1 may be incorporated in many forms in a remote office and/or in a headquarters office.
- FIGS. 4 - 9 illustrate various voice messaging systems in greater detail, as well as more detailed connections of a call handling reply system between a PBX and a VMS system.
- a call handling reply system may be included within a telephony environment 485 (e.g., a customer premise environment).
- a call handling reply system 420 is shown connected between PBX 410 and VMS 430 .
- Call handling reply system 420 is invisible to both PBX 410 and VMS 430 and receives all busy/no answer calls.
- Call handling reply system 420 determines an identity of a caller by querying voice directory database 440 , packets the information about the caller and passes the call with the packeted caller information to VMS 430 to allow a call handling reply.
- the SMDI link provides a data packet including a reply address of the caller to VMS 430 .
- call handling reply system 420 is connected to voice directory database 440 (which stores caller information) through a Local Arca Network (LAN) card.
- Call handling reply system 420 may also include a Voice Bridge Personal Computer (VB-PC) board, such as a VB-1001 by Voice Technologies Group, and may include eight ports per board and one Multi-Vendor Integration Protocol (MVIP) interface.
- VB-PC board emulates digital phones to allow an interface from a computer to PBX 410 .
- Call handling reply system 420 may also include an interface to VMS 430 using a T1 card, for example, an AG-T1 interface card in the PC and at least one RS-232 serial port.
- AG-T1 interface board may include one T1 termination, one MVIP interface with enhanced compliant MVIP switching, with twenty-four ports digital signal processing (DSP) voice and call processing per board, at seven MIPS per port.
- DSP digital signal processing
- An AG-8 card included in call handling reply system 420 may include eight ports per board with DSP processing power of ten MIPS per port.
- a call handling reply system 520 is connected to a voice directory database 440 and a remote office 580 having a PBX 570 , but the remote office 580 is not connected to its own VMS.
- the remote office 580 shares a VMS 430 located at a main office 585 and receives all the benefits of the system, including a call handling reply capability to external and internal calls.
- Busy/no answer calls from remote PBX 570 are channeled through a T1 datalink 578 or may be sent directly to main office 585 using PSTN lines (not shown).
- a stand-alone hardware unit 560 may be used to interact with PBX 570 and VMS 430 .
- One example hardware unit is Voice Bridge II by Voice Technologies Group. This hardware unit may be used to retrieve caller identification information through a digital phone line if the caller is a member of local PBX 570 .
- Hardware unit 560 may act as a third party monitor and provide call information through, for example, ANI/CID, dialed number identification service (DNIS) or direct inward dial (DID), to the call handling reply system 520 at main office 585 .
- the hardware unit 560 captures caller information which would not otherwise be transferrable by analog phone lines out of PBX 570 in order to limit the number of entries which are searched in database 440 .
- call handling reply system 520 is used to process incoming SMDI data from the remote office 580 , as well as to receive calls from another source in addition to the hardware unit 560 .
- Call handling reply system 520 resolves any overlapping dialing plans between its local PBX 410 and any remote offices to which it may be connected.
- the function of datalink 578 is to channel analog phone lines from the remote office 580 to main office 585 .
- Channel banks 550 , 575 may be used to convert analog lines to digital lines or digital lines to analog lines. Therefore, the connection may include analog lines instead of the T1 lines. If analog lines are used, the digital circuit to send SMDI data from remote office 580 may be replaced using a single connected analog line with two modems (not shown).
- a call handling reply system 520 in main office 685 is connected to remote office 680 through a central office (CO) 642 .
- Main office 685 is configured as discussed above in connection with FIG. 5.
- Remote office 680 shares VMS 430 in the main office 685 and has access to the call handling reply feature through call handling reply system 520 .
- Busy/no answer calls to main office 685 may be received by CO 642 over dedicated modem or data connections.
- CO 642 sends busy/no answer calls to main office 685 via analog lines 646 or in the alternative, T1 lines.
- Call handling reply system 520 receives SMDI data from CO 642 over SMDI lines 646 , performs a directory lookup in voice directory database 440 , creates an SMDI packet and sends the packet to VMS 430 .
- the live call is then passed to VMS 430 and appears to VMS 430 as if it came directly from a PBX.
- Analog resources on call handling reply system 520 remain in use during the entire time the caller is creating the voice message.
- FIG. 7 shows another embodiment in which the main office 785 is connected to remote office 780 in a manner similar to the connections shown in FIG. 5, with the addition of a VMS 755 in remote office 780 .
- T1 datalink 778 includes two live voice channels per external busy/no answer call. One channel is used to provide call handling reply system 720 with a live caller from remote office 780 . The second channel is used to feed remote VMS 755 when it records a message from a caller. Both channels are used while the caller leaves the message. Calls made to retrieve messages may be local calls in this embodiment.
- call handling reply system 820 is connected to an AMIS-A compliant VMS 830 .
- VPIM or other voice message networking may be used.
- those users without a VPIM interface may also use call handling reply system 820 .
- Call handling reply system 820 includes an analog telephony card to receive outbound network messages sent from a VMS using AMIS-A.
- the messages received by call handling reply system 820 are converted to a format, such as a proprietary digital format or a VPIM format, to allow the messages to be delivered to another destination.
- An AMIS voice mail system may be registered with voice directory database 440 to receive inbound messages from a service provider. Inbound messages may be delivered digitally to call handling reply system 820 where they will be converted to AMIS-A messages and delivered to a local VMS.
- FIG. 9 is a block diagram of multiple call handling reply systems configured between a headquarters office and multiple remote offices.
- a headquarters office 930 connects a call handling reply system 940 between PBX 935 and VMS 945 through a T1 connection (e.g., AG-T1) or analog line (not shown).
- PBX 935 is reconfigured to map calls normally received over the previously connected T1 or analog lines to a digital phone extension.
- Call handling reply system 940 is connected to the digital phone extension via a VB-PC board and is connected through a LAN card to Wide Area Network (WAN) router 947 .
- Call handling reply system 940 includes information for local members using call handling reply system 940 and information about external members with whom individuals at headquarters office 930 are doing business.
- a call received by PBX 935 at headquarters office 930 is forwarded to a general digital extension.
- call handling reply system 940 receives this call and identifies the caller and the reason the call arrived (e.g., busy, no answer, forwarded, etc.).
- Caller information is retrieved from a query to voice directory database 902 .
- Voice directory database 902 may be included in a service provider transport system that transfers voice messages and can identify differences in VMS standards.
- a T1 channel in headquarters office 930 or an optional analog line (not shown) is captured to connect call handling reply system 940 to VMS 945 .
- An SMDI data packet is created and includes a reply address for the caller that was retrieved from voice directory database 902 and an identifier for the channel that was captured for use.
- the SMDI data packet includes the information to allow a reply to the caller.
- the SMDI packet is sent to VMS 945 prior to call handling reply system 940 initiating a ring on a T1 or analog line to VMS 945 .
- VMS 945 answers the line and retrieves information about the call from the SMDI packet.
- Call handling reply system 940 attaches the digital extension of the caller to the T1 channel connected to VMS 945 .
- Call handling reply system 940 passes voice data between PBX 935 and VMS 945 .
- Busy/no answering call handling for the other remote offices in FIG. 9 are similar to the call handling described above in connection with FIGS. 4 - 8 .
Abstract
A voice mail system in which a recipient of a call is provided with the ability to reply to an internal or external voice message in a common manner. A method for providing a reply includes identifying a caller, and retrieving an address of the caller from a database. Caller origination information is automatically provided with a recorded message from the caller to enable a recipient of the recorded message to reply. Identifying the caller may include searching a database using a voice signature of the caller to identify caller information.
Description
- The present invention relates to voice messaging, and in particular to a method and apparatus for responding to both internal (those from within the same voice messaging system) and external voice messages (those from outside the voice messaging system).
- A voice mail system (VMS) provides a voice mailbox that allows an inbound voice message to be stored when the user is away from the receiving telephone or in the event a busy signal is encountered by a caller, so that the recipient can learn of the call. The caller may also choose to leave a message directly in the voice mailbox of the recipient of the call when a “live call” is not necessary or desired.
- One additional feature of a VMS allows a recipient of an internal call (from another person having an account on the same VMS) to listen to a message stored in his or her voice mailbox and, by operating the keys on a telephone keypad, to initiate a reply to the message. To initiate a reply to the internal message, the recipient does not need to identify the extension of the source of the call because the VMS supplies the source extension. However, an internal call is generally identified by the extension from which the call was placed (source/extension), not the caller. Thus, if the caller did not use his or her own phone, a reply would be sent to the calling extension, not to caller's personal extension.
- A receiver can reply with a “live call” to the calling extension by pressing keys on the number pad and being directly connected. Alternatively, a message direct to the voice mail box of the calling extension can be created by pressing the appropriate keys to initiate the reply command; the recipient records the reply message and hangs up; the VMS automatically sends the recorded reply message to the voice mailbox of the calling extension. Again, this reply feature is only available for calls between users having accounts on the same VMS (internal callers), and only when the voice message includes a return voice mailbox address of the original calling location. Recipients of calls from external callers (people external to the VMS), such as cellular phone users, etc., cannot automatically send a reply to such messages since the reply feature cannot identify the source of the call. Rather, the recipient must listen to the message, write down the name and number of the caller and then after hanging up, call back the person who left the message.
- Voice messaging also allows internal communication from one caller to multiple recipients on the same VMS system without the caller initiating a call to each individual recipient's voice mailbox.
- Two or more VMSs of a similar type may be connected together to operate as a single VMS. The two VMSs can be at different locations. The network may operate through, for example, a dial up (e.g., analog line) connection, or a digital connection (e.g., an Integrated Services Digital Network (ISDN) lines).
- Sending messages and replies in a voice message network requires a protocol for communicating between the separate VMS systems. A widely-used protocol for distributing voice messages using analog lines between networked VMS systems is the Audio Messaging Interchange Specification (AMIS), available for analog telephone lines (AMIS-A) or for a digital network (AMIS-D). The AMIS-A protocol distributes messages via a voice dial-up line; Dual Tone Multi Frequency (DTMF) tones are used for signaling.
- Individual VMS companies have also developed their own proprietary protocols to use between their own VMS systems. However, due to the proprietary nature, these protocols only work between VMS systems made by the same company; VMS equipment from different companies, each with its own proprietary protocol, are unable to communicate with one another.
- Currently, voice message networking does not allow a receiver of a message to automatically reply to caller on a different VMS. Therefore, a person on a VMS can receive an internal message (i.e., from a caller on a same VMS or VMS network) and an external message (i.e., from a different VMS, mobile phone, home phone, etc.), but cannot reply in the same manner to each type of message.
- What is needed is a system that allows a recipient to reply to any internal or external voice message in a common manner. Additionally, a system is needed to return a call to an actual caller, not just the location (calling extension) from which the message or call is sent.
- In one embodiment of the present invention, a recipient of a call is provided with the ability to reply to an internal or external voice message in a common manner.
- In another embodiment, a caller generated identifier is used to search a database for caller information.
- In another embodiment, a method is provided for forming a reply to a voice message on a first voice mail system, including the steps of identifying a caller, retrieving information related to the identified caller, and providing the retrieved information to a second voice mail system information to enable a call recipient to reply to the voice message.
- In another embodiment, a method of retrieving information about a caller is provided and includes the steps of identifying a calling location of the caller, recording a vocal utterance made by the caller and accessing a database as a function of the identified calling location and the recorded vocal utterance.
- In another embodiment, a method of replying to a caller includes the steps of identifying a calling location of the caller, storing a vocal utterance made by the caller, accessing a database as a function of the identified calling location and the recorded vocal utterance to retrieve caller information, wherein the caller information includes a caller reply location and sending a reply to the caller reply location.
- In another embodiment, a method of storing a single voice mail message from a caller includes the steps of identifying a calling location of the caller, recording a spoken name uttered by the caller, accessing a database as a function of the identified location and the recorded spoken name to retrieve the caller information and recording a message uttered by the caller and storing the recorded spoken name and the recorded message information together as a single voice mail message.
- In another embodiment, a system for retrieving information about a caller includes means for identifying a calling location of the caller, means for storing a vocal utterance made by the caller and means for accessing a database as a function of the identified calling location and the recorded vocal utterance.
- In another embodiment, a system for replying to a caller includes means for identifying a calling location of the caller, means for recording a vocal utterance made by the caller, means for accessing a database as a function of the identified calling location and the recorded vocal utterance to retrieve caller information, wherein the caller information includes a caller reply location and means for sending a reply to the caller reply location.
- In one embodiment, the calling location is different from the caller reply location.
- In another embodiment, the reply is an electronic mail message or a recorded message.
- In another embodiment, the caller reply location is a voice mailbox.
- In another embodiment, the vocal utterance is converted to a string of characters, wherein the database is accessed as a function of the string of characters.
- In another embodiment the voice utterance is identified using speaker verification or speech recognition to access the database.
- FIG. 1 is a block diagram of a voice messaging system according to one embodiment of the present invention;
- FIG. 2 is a flowchart illustration of a process for replying to a voice message;
- FIG. 3 is an example process for adding a voice signature to a voice message;
- FIG. 4 is a block diagram of a call handling reply system in a telephone environment at a customer location;
- FIG. 5 is a block diagram of a call handling reply system connected to a remote office that does not have a VMS;
- FIG. 6 is a block diagram of a call handling reply system connected to a remote office through a central office;
- FIG. 7 is a block diagram of a call handling reply system connected to a remote office having a VMS;
- FIG. 8 is a block diagram of a call handling reply system connected to an AMIS-A compliant VMS;
- FIG. 9 is a block diagram of multiple call handling reply systems configured between a headquarters office and multiple remote offices; and
- FIG. 10 is a representation of caller information stored in a voice directory database.
- In accordance with one embodiment of the present invention, a method and apparatus for identifying a caller is provided to allow a common method of replying to internal (from a same voice mail system) and external (from a different voice mail system or external to the voice mail system) calls. A call handling reply system intercepts incoming messages and provides caller information, including a return address, to a Voice Mail System (VMS). The caller may be identified (at least in part) by his/her spoken name which is used to search a database of caller information.
- As shown in FIG. 1, a
system 10 for handling phone calls ofuser 1 includes a Private Branch Exchange (PBX) 110, a callhandling reply system 115, a voice mail system (VMS) 120 and aVPIM interface 125. Similarly, asecond system 20 foruser 2 includes aPBX 155, a callhandling reply system 115, avoice mail system 145 and a Voice Profile for Interface Mail Extension (VPIM)interface 140. ThePBXs digital lines PBX systems handling reply system 115 may be connected to thevoice mail systems serial connection handling reply system 115 may operate with only one VMS and one PBX system. Thevoice mail systems VPIM interfaces connections voice directory database 135. The VPIM interfaces 125, 140 are connected to adata network 130, e.g., an internet, and communicate using the VPIM protocol. In one embodiment, a proprietary protocol may be used. - A
voice directory database 135 is provided and is connected to thedata network 130 throughconnection 131. Additionally, thevoice directory database 135 is connected to the call handlingreply systems 115 throughconnections 112, and communicate using a standard or proprietary database protocol.PBXs connections - The operation of the components in FIG. 1 will now be described in connection with the flowchart of FIG. 2.
PSTN 160 is commonly accessed by telephones, fax machines and PBX systems. In this example,user 1 places a call touser 2;user 1 anduser 2 being connected throughPBX 110,PSTN 160 andPBX 155. The call handlingreply systems 115 provide a hardware and software interface between thePBXs VMSs - The call handling
reply systems 115 handle calls onPBXs VMSs - In one embodiment, a standard protocol, Voice Profile for Internet Mail (VPIM) developed by the Electronic Messaging Association (EMA) (a group made up of independent voice mail manufacturers), allows compliant VMSs to transfer messages to each other. VMSs which are VPIM compliant are able to communicate with each other, even if each VMS is made by a different manufacturer with its own proprietary protocol, since the VPIM protocol is common between them. VPIM is built on top of the Enhanced Simple Mail Transport Protocol/Multiple Purpose Internet Mail Extension (ESMTP/MIME) that allows each VMS to send and receive messages, such as voice messages, to one another over the Internet using the ESMTP/MIME standard to define a structure of the message. VPIM allows VMSs with different priorities, delivery standards and features to communicate according to a caller's messaging expectations as defined by the caller's VMS. Without VPIM, messages can only be transferred between same type VMSs made by the same manufacturer, using a common proprietary protocol.
VPIM interface 125 connectsVMS 120 through data network 130 (e.g., the Internet) toVPIM interface 140. - In another embodiment, a service provider, such as Unifi Communications, Inc., Lowell, Mass., may be used to transfer voice messages between VMSs when VPIM compliant messages are not available or are not used by all parties to a call. The service provider may maintain a voice directory database of callers so that a VMS may access a voice mail address of a caller. Service providers may provide global customer information to local users to allow messaging and replying to messages in a global environment. In addition, service providers may communicate with other service providers to update customer information in voice directory databases and to ensure that the service providers can communicate with each other when necessary. Other methods of automatically or manually updating the voice directory database may be used.
-
Voice directory database 135 is accessible by call handlingreply systems 115 through data network (e.g., Internet)protocol connections database protocol connections 112.Voice directory database 135 provides caller information, including a reply address, to the call handlingreply system 115 that has queriedvoice directory database 135 in order to identify the caller. - For example, when a call is initiated (
step 203 in FIG. 2) andPBX 155 receives a first ring of the telephone call, an automatic number identification (ANI), caller identification (CID), or other known method of identification of the telephone call, is associated with the caller location (step 206). The ANI/CID is used to identify the calling extension and does not necessarily identify the actual caller. For example, if an employee of a business placed a call, the ANI/CID for the call would only give information related to the company's main number, although it might possibly identify an extension from which the call was placed. The ANI/CID, however, does not necessarily identify the actual caller placing the call. - In
step 207, a determination is made as to whether or not the called party,user 2, is able to answer the call, i.e., busy, no answer, or calls forwarded. Ifuser 2 is available, the process proceeds to step 208 where the caller is connected and a “live call” will ensue. - When a busy/no answer/call forwarded signal is encountered, call handling
reply system 115 intercepts the call instep 209, and receives information about the call fromPBX 110, including ANI/CID information and the reason for the call (e.g., busy, forwarded, no answer, etc.). Call handlingreply system 115 requests the caller (i.e., user 1) to speak his or her name. Instep 212, call handlingreply system 115 records the spoken name. In an alternate embodiment, any tones which uniquely identify a caller in a secure manner may be recorded by the call handling system instep 212. - An example of a caller record in
voice directory database 135 is shown in FIG. 10. The caller record may include information such as the caller name, company name, caller address, a recording of the caller's spoken name in a voice file, direct telephone number and voice mailbox number. The entries in the voice directory database may be updated by a standard service provider or may be dynamically updated by users of the database. The database is not limited to any particular format or look up protocol. One example of a hierarchial directory that may be used is an X500 directory by Control Data Systems; the X500 directory may be accessed, for example, using Lightweight Directory Access Protocol (LDAP) developed by Netscape. - As shown in FIG. 10, a caller record in
voice directory database 135 may also include information pertaining to how to handle calls to a voice mailbox. For example, conditions to forward some calls or all calls based on a caller's identity may be included in the caller record. An option which is listed as caller research may be chosen to allow an operator to attempt to register an unidentified caller through a series of questions by the operator. -
Voice directory database 135 may include information regarding usual caller expectations for message handling; these may be initially defined at the time a caller is entered into the voice directory database. For example, different VMSs may include different features or the features may be defined differently. By defining user preferences in the database, the desired information is automatically obtained when the caller information is retrieved by a call handling reply system. One example of a preference may be a caller that requests a message to be delivered to a different mailbox location, for example, a person traveling for an extended period of time, or to support an all-in-one mailbox.Voice directory database 135 may also perform feature normalization which can resolve problems when a feature has a different meaning on different systems. For example, in one system, a priority definition may instruct a VMS to deliver the message immediately, while another VMS may define a priority as a message that must be delivered within sixty minutes. As discussed above, VPIM allows these caller expectations to be communicated so as to allow a call to be handled according to the caller's expectations. -
Voice directory database 135 may also include dialing plans of callers accessing the database. The dialing plans identify the callers in a manner to prevent mishandled calls due to same phone numbers or extensions assigned to different callers at different locations. The database may be arranged to uniquely identify each VMS caller and may store entries by relating potential callers with potential recipients. A caller may be identified by a node number, a physical address number and/or a dial plan number. When entries are made to initialize files in a voice directory database, any numbers that are the same in any two nodes are resolved to allow unique identification of each caller. To uniquely identify individual mailboxes, a service provider may assign each address a prefix to be appended to a destination address. If a company does not add a prefix, the service provider may maintain default prefixes for a given company. - In one embodiment, the caller's identity cannot be identified merely by the ANI/CID found in
step 206. The combination of the identified ANI/CID along with the voice signature recorded instep 212, can be used however to search thevoice directory database 135. In order to perform a more accurate and timely search of thevoice directory database 135, all entries having the ANI/CID identification are retrieved from thevoice directory database 135 to create a smaller temporary directory database, (step 215). In one embodiment, the phone number being called may be used to create a smaller temporary directory database instep 215. In an alternate embodiment, an ANI/CID number may not be available. In addition, any caller identifier, such as any tones which uniquely identify a caller in a secure manner which are recorded by the call handling system 115 (in step 212), may used to search the database. - In one embodiment, the temporary database includes only a list of text names taken from the
voice directory database 135. This temporary database would include a list of hose names from thevoice directory database 135 which matched the ANI/CID and another list based on the phone number being called. In another embodiment, the temporary database may include the list of names identified by the ANI/CID, as well as the associated caller records. - In
step 218, the call handling reply system searches text names in the temporary database (created in step 215) using the recorded spoken name of the caller; the spoken name was recorded by the call handling reply system instep 212. The process of identifying a caller's text name in a database from a recorded spoken name may be performed by a variety of technologies such as speech recognition and/or speaker verification. In other words, the spoken name is connected to text. - In one embodiment of searching a temporary database, the spoken name may be processed by a speech recognition system such as ReCite by Pure Speech, or by similar speech recognition systems by Lernout and Hauspie, Dragon Systems or IBM. The speech recognition system recognizes what name is spoken, but does not distinguish who has spoken the name. Such a system operates by matching phonemes, which are the smallest increments of speech that distinguish one utterance from another in a language or dialect.
- A speaker verification system may also be used to identify not only what is spoken, but also who has spoken it and may be used to identify a situation when a caller speaking a name is not that person. Speaker verification could be used in applying a higher level of security to the system.
- Next, it is determined if the caller can be identified from the names in the temporary database in
step 221. If the caller's name is found in the list of names in the temporary database (step 221), then the entry in thevoice directory database 135 related to the caller name is retrieved (step 239). The retrieved caller information may include a previous recording of the spoken name, the caller's name, telephone number, reply mailbox address and other caller information. In one embodiment, i.e., when the temporary database includes the associated caller records and the list of names retrieved from thevoice directory database 135 as identified by the ANI/CID and/or by a number being called, the voice directory database does not need to be accessed in this step. - The information retrieved in
step 239 is used to create a Simplified Message Desk Interface (SMDI) data packet. This data packet includes information such as the reply address of the caller (e.g., user 1) and will be used to allow the recipient (e.g., user 2) of the voice mail message to reply to the voice mail message left by the external caller (e.g., user 1). The data packet may also include a date/time stamp and special handling instructions (e.g., urgent, private, etc.). - The call is then transferred,
step 245, touser 2'sVMS 145 with the data packet.VMS 145 receives the call and prompts the caller to record a message. The caller records the message instep 248. As shown in FIG. 3, the recorded spoken name will be appended to any voice mail message the caller creates so as to act as a voice signature for the caller. After a caller is prompted for his or her spoken name, the caller is invited to leave a message. The recorded name becomes part of the voice mail message and may be transported with the message sent from the voice mail system. Recording a voice signature as part of the voice mail message allows an unidentified caller (e.g., user 1) to be identified by their voice signature when the called party (e.g., user 2) retrieves the message from the VMS. The voice signature may be stored in thevoice directory database 135 for future use. For example, the voice signature may be used by the recipient when composing a reply message to verify the reply message is being sent to the correct caller. - The recipient of the message may listen to the recorded message in
step 251 and then may press reply keys to reply to the recorded message instep 254. The keys pressed by the recipient may be any keys that allow a reply to a message, either a live return call or a message foruser 1's voice mail box, such that the recipient no longer needs to distinguish between a message from an internal or an external caller. After the sequence of reply keys are pressed, the recipient is either connected or may record a reply message instep 257. It should be noted that depending on the capabilities of the components in the call handling reply system, the VMS and the voice directory database, (and potentially depending on other factors as well), several of the above steps may be performed in parallel; e.g., the call handling reply system may be identifying a caller as the caller is recording a message. - Based on the identifying information in the data packet transferred to
VMS 145, the reply message is sent to the original caller instep 260. In one embodiment, using the voice signature of the caller (which is the spoken name of the caller recorded in thevoice directory database 135 in step 212), the recipient creating the reply message may verify the return caller information. For example, after retrieving a message from the caller, the call handling reply system may prompt the recipient to verify the caller. The recipient may press a key to hear the voice signature recorded by the caller associated with the recorded message. The recipient may then determine if the voice signature is the caller to whom the recipient wants to reply. If it is, then the recipient may compose a reply message. If not, the recipient may still choose to reply or may choose to independently make a live call or to create a new message. - The reply message may be sent to a service provider, such as the operator of
voice directory database 135 for forwarding to the original caller, as discussed above in connection with thevoice directory database 135. In one embodiment, the reply message is sent using a VPIM interface to a data network, such as the Internet, and then sent to the VMS of the original caller, or over analog phone lines to the caller. - Returning now to step221, when the caller cannot be identified from the entries in the temporary database based on a search for the caller name, the caller is prompted to input a return phone number in
step 224. The return phone number is entered by pressing the keys on the phone to generate DTMF signals. - Using the phone number entered by the caller, the
voice directory database 115 is searched instep 227 to determine if the caller can be identified. If an entry matching the return phone number is found in the database instep 230, then the caller is identified and the process continues atstep 239 in which the caller information, including the reply address, is retrieved as discussed above. - However, if an entry in the database matching the return phone number is not found and, therefore, the caller is not identified in
step 230, then the call is passed to theVMS 145 instep 233. In one embodiment, since the caller was not identified, the return address of the caller is not passed toVMS 145. Therefore, in step 235, the caller records the message onVMS 145 and the reply feature is unavailable to the recipient of the message. The recipient may still reply to the message if desired by alternate methods, e.g., listening to the message whereuser 1 has left a number where he can be reached. - In one embodiment when the caller is not identified, an outbound delivery message system may be used. An address of a service provider (e.g., the operator of a voice directory database) is provided to
VMS 145 with the voice mail message from the caller who cannot be identified in thedatabase 135. If a recipient of the voice mail message chooses to reply to the message, then the reply message is sent to the address of the service provider. The service provider may then use a computer system to automatically call a phone number associated with the original caller in order to provide the reply message to the caller. The reply message is provided as a live call to the original caller based on a telephone number entered by the original caller or after research is performed by a service provider, can be delivered to the original caller's voice mail box. - In another embodiment when the caller is not identified, an operator may intercept the call when the caller cannot be identified by a search of the
voice directory database 135. The operator may request information to allow the caller to be entered into thevoice directory database 135 along with any associated information about the caller to allow the reply feature to work when the recipient attempts to reply to the call. The information may include, for example, the name of the caller, voice mail address, return phone number, and VPIM address (e.g., a standard E-mail address, usually a phone number at a domain address). Thevoice directory database 135 is then manually or automatically updated with the caller information and a data packet is sent with the voice message toVMS 145. - The voice messaging system shown in FIG. 1 may be incorporated in many forms in a remote office and/or in a headquarters office. FIGS.4-9 illustrate various voice messaging systems in greater detail, as well as more detailed connections of a call handling reply system between a PBX and a VMS system.
- In one alternative embodiment shown in FIG. 4, a call handling reply system may be included within a telephony environment485 (e.g., a customer premise environment). A call handling
reply system 420 is shown connected betweenPBX 410 andVMS 430. Call handlingreply system 420 is invisible to bothPBX 410 andVMS 430 and receives all busy/no answer calls. Call handlingreply system 420 determines an identity of a caller by queryingvoice directory database 440, packets the information about the caller and passes the call with the packeted caller information toVMS 430 to allow a call handling reply. - In one embodiment, the SMDI link provides a data packet including a reply address of the caller to
VMS 430. In this embodiment, call handlingreply system 420 is connected to voice directory database 440 (which stores caller information) through a Local Arca Network (LAN) card. Call handlingreply system 420 may also include a Voice Bridge Personal Computer (VB-PC) board, such as a VB-1001 by Voice Technologies Group, and may include eight ports per board and one Multi-Vendor Integration Protocol (MVIP) interface. The VB-PC board emulates digital phones to allow an interface from a computer toPBX 410. Call handlingreply system 420 may also include an interface toVMS 430 using a T1 card, for example, an AG-T1 interface card in the PC and at least one RS-232 serial port. AG-T1 interface board may include one T1 termination, one MVIP interface with enhanced compliant MVIP switching, with twenty-four ports digital signal processing (DSP) voice and call processing per board, at seven MIPS per port. An AG-8 card included in call handlingreply system 420 may include eight ports per board with DSP processing power of ten MIPS per port. - In another embodiment of a voice messaging system shown in FIG. 5, a call handling
reply system 520 is connected to avoice directory database 440 and aremote office 580 having aPBX 570, but theremote office 580 is not connected to its own VMS. In this embodiment, theremote office 580 shares aVMS 430 located at amain office 585 and receives all the benefits of the system, including a call handling reply capability to external and internal calls. Busy/no answer calls fromremote PBX 570 are channeled through a T1 datalink 578 or may be sent directly tomain office 585 using PSTN lines (not shown). - A stand-
alone hardware unit 560 may be used to interact withPBX 570 andVMS 430. One example hardware unit is Voice Bridge II by Voice Technologies Group. This hardware unit may be used to retrieve caller identification information through a digital phone line if the caller is a member oflocal PBX 570.Hardware unit 560 may act as a third party monitor and provide call information through, for example, ANI/CID, dialed number identification service (DNIS) or direct inward dial (DID), to the call handlingreply system 520 atmain office 585. Thehardware unit 560 captures caller information which would not otherwise be transferrable by analog phone lines out ofPBX 570 in order to limit the number of entries which are searched indatabase 440. - In this embodiment, additional software in the call handling
reply system 520 is used to process incoming SMDI data from theremote office 580, as well as to receive calls from another source in addition to thehardware unit 560. Call handlingreply system 520 resolves any overlapping dialing plans between itslocal PBX 410 and any remote offices to which it may be connected. In this embodiment, the function of datalink 578 is to channel analog phone lines from theremote office 580 tomain office 585.Channel banks remote office 580 may be replaced using a single connected analog line with two modems (not shown). - In another alternative embodiment shown in FIG. 6, a call handling
reply system 520 inmain office 685 is connected toremote office 680 through a central office (CO) 642.Main office 685 is configured as discussed above in connection with FIG. 5.Remote office 680shares VMS 430 in themain office 685 and has access to the call handling reply feature through call handlingreply system 520. Busy/no answer calls tomain office 685 may be received byCO 642 over dedicated modem or data connections.CO 642 sends busy/no answer calls tomain office 685 viaanalog lines 646 or in the alternative, T1 lines. Call handlingreply system 520 receives SMDI data fromCO 642 over SMDIlines 646, performs a directory lookup invoice directory database 440, creates an SMDI packet and sends the packet toVMS 430. The live call is then passed toVMS 430 and appears toVMS 430 as if it came directly from a PBX. Analog resources on call handlingreply system 520 remain in use during the entire time the caller is creating the voice message. - FIG. 7 shows another embodiment in which the
main office 785 is connected toremote office 780 in a manner similar to the connections shown in FIG. 5, with the addition of aVMS 755 inremote office 780. In this embodiment, T1 datalink 778 includes two live voice channels per external busy/no answer call. One channel is used to provide call handlingreply system 720 with a live caller fromremote office 780. The second channel is used to feedremote VMS 755 when it records a message from a caller. Both channels are used while the caller leaves the message. Calls made to retrieve messages may be local calls in this embodiment. - Another embodiment is shown in FIG. 8 in which call handling
reply system 820 is connected to an AMIS-Acompliant VMS 830. In the previously discussed embodiments, VPIM or other voice message networking may be used. However, in this embodiment shown in FIG. 8, those users without a VPIM interface may also use call handlingreply system 820. Call handlingreply system 820 includes an analog telephony card to receive outbound network messages sent from a VMS using AMIS-A. The messages received by call handlingreply system 820 are converted to a format, such as a proprietary digital format or a VPIM format, to allow the messages to be delivered to another destination. An AMIS voice mail system may be registered withvoice directory database 440 to receive inbound messages from a service provider. Inbound messages may be delivered digitally to call handlingreply system 820 where they will be converted to AMIS-A messages and delivered to a local VMS. - FIG. 9 is a block diagram of multiple call handling reply systems configured between a headquarters office and multiple remote offices. In the embodiment shown in FIG. 9, a
headquarters office 930 connects a call handlingreply system 940 betweenPBX 935 andVMS 945 through a T1 connection (e.g., AG-T1) or analog line (not shown).PBX 935 is reconfigured to map calls normally received over the previously connected T1 or analog lines to a digital phone extension. Call handlingreply system 940 is connected to the digital phone extension via a VB-PC board and is connected through a LAN card to Wide Area Network (WAN) router 947. Call handlingreply system 940 includes information for local members using call handlingreply system 940 and information about external members with whom individuals atheadquarters office 930 are doing business. - The handling of a call received by the
headquarters office 930 of FIG. 9 will now be described. A call received byPBX 935 atheadquarters office 930 is forwarded to a general digital extension. As previously described, call handlingreply system 940 receives this call and identifies the caller and the reason the call arrived (e.g., busy, no answer, forwarded, etc.). Caller information, including a reply address, is retrieved from a query to voicedirectory database 902.Voice directory database 902 may be included in a service provider transport system that transfers voice messages and can identify differences in VMS standards. - A T1 channel in
headquarters office 930 or an optional analog line (not shown) is captured to connect call handlingreply system 940 toVMS 945. An SMDI data packet is created and includes a reply address for the caller that was retrieved fromvoice directory database 902 and an identifier for the channel that was captured for use. The SMDI data packet includes the information to allow a reply to the caller. The SMDI packet is sent toVMS 945 prior to call handlingreply system 940 initiating a ring on a T1 or analog line toVMS 945.VMS 945 answers the line and retrieves information about the call from the SMDI packet. Call handlingreply system 940 attaches the digital extension of the caller to the T1 channel connected toVMS 945. Call handlingreply system 940 passes voice data betweenPBX 935 andVMS 945. - Busy/no answering call handling for the other remote offices in FIG. 9 are similar to the call handling described above in connection with FIGS.4-8.
- The process of enabling a call handling reply as discussed in the embodiments above may be included in current telephony environments and may also be included in new PBX and/or VMS platforms.
- Having now described a few embodiments, it should be apparent to those skilled in the art that the foregoing is merely illustrative and not limiting, having been presented by way of example only. Numerous modifications and other embodiments are within the scope of one of ordinary skill in the art and are contemplated as falling within the scope of the invention.
Claims (17)
1. A method of retrieving information about a caller comprising the steps of:
recording a vocal utterance made by the caller; and
accessing a database to retrieve information about the caller as a function of the recorded vocal utterance.
2. The method of claim 1 , comprising:
identifying a calling location of the caller; and
accessing the database as a function of the identified calling location and the received caller identifying tones.
3. A method of replying to a caller comprising the steps of:
identifying a calling location of the caller;
recording a vocal utterance made by the caller;
accessing a database as a function of the identified calling location and the recorded vocal utterance to retrieve caller information, wherein the caller information includes a caller reply location; and
sending a reply to the caller reply location.
4. The method of claim 3 , wherein the calling location is different from the caller reply location.
5. The method of claim 3 , wherein the reply is an electronic mail message.
6. The method of claim 3 , wherein the reply is a recorded message.
7. The method of claim 3 , wherein the caller reply location is a voice mailbox.
8. The method of claim 3 , comprising:
converting the vocal utterance to a string of characters, wherein the database is accessed as a function of the string of characters.
9. A method of storing a single voice mail message from a caller comprising the steps of:
identifying a calling location of the caller;
recording a spoken name uttered by the caller;
accessing a database as a function of the identified location and the recorded spoken name to retrieve the caller information; and
recording a message uttered by the caller and storing the recorded spoken name and the recorded message information together as a single voice mail message.
10. A system for retrieving information about a caller comprising:
means for identifying a calling location of the caller;
means for storing a vocal utterance made by the caller; and
means for accessing a database as a function of the identified calling location and the recorded vocal utterance.
11. A system for replying to a caller comprising:
means for identifying a calling location of the caller;
means for storing a vocal utterance made by the caller;
means for accessing a database as a function of the identified calling location and the recorded vocal utterance to retrieve caller information, wherein the caller information includes a caller reply location; and
means for sending a reply to the caller reply location.
12. A method of forming a reply to a voice message on a first voice mail system, comprising the steps of:
identifying a caller providing the voice message;
retrieving information related to the identified caller; and
providing the retrieved information to a second voice mail system to enable the reply.
13. The method of claim 12 , wherein the retrieving information step includes retrieving a reply address of the caller.
14. The method of claim 12 , wherein the identifying a caller step includes identifying a caller using speech recognition.
15. The method of claim 12 , wherein the identifying a caller step includes identifying a caller using DTMF tones.
16. The method of claim 12 , wherein the identifying a caller step includes identifying a caller using automatic number identification.
17. The method of claim 12 , wherein the identifying a caller step includes identifying a caller using speaker verification.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/789,050 US20020049768A1 (en) | 1998-06-05 | 2001-02-20 | Method and apparatus for identifying and replying to a caller |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/092,764 US6292799B1 (en) | 1998-06-05 | 1998-06-05 | Method and apparatus to automatically address a voice mail reply to a voice mail message |
US09/789,050 US20020049768A1 (en) | 1998-06-05 | 2001-02-20 | Method and apparatus for identifying and replying to a caller |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/092,764 Continuation US6292799B1 (en) | 1998-06-05 | 1998-06-05 | Method and apparatus to automatically address a voice mail reply to a voice mail message |
Publications (1)
Publication Number | Publication Date |
---|---|
US20020049768A1 true US20020049768A1 (en) | 2002-04-25 |
Family
ID=22235041
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/092,764 Expired - Fee Related US6292799B1 (en) | 1998-06-05 | 1998-06-05 | Method and apparatus to automatically address a voice mail reply to a voice mail message |
US09/789,050 Abandoned US20020049768A1 (en) | 1998-06-05 | 2001-02-20 | Method and apparatus for identifying and replying to a caller |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/092,764 Expired - Fee Related US6292799B1 (en) | 1998-06-05 | 1998-06-05 | Method and apparatus to automatically address a voice mail reply to a voice mail message |
Country Status (6)
Country | Link |
---|---|
US (2) | US6292799B1 (en) |
EP (1) | EP1084557A4 (en) |
JP (1) | JP2002517953A (en) |
CN (1) | CN1146214C (en) |
AU (1) | AU748758B2 (en) |
WO (1) | WO1999063734A1 (en) |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030046400A1 (en) * | 2001-08-22 | 2003-03-06 | Owen Friel | Contacting a destination terminal from an originating terminal via a packet-based communications network |
FR2856543A1 (en) * | 2003-06-20 | 2004-12-24 | Sin Etke Technology Co Ltd | ANSWERING SYSTEM FOR CUSTOMER SERVICE |
WO2006135591A1 (en) * | 2005-06-10 | 2006-12-21 | Lucent Technologies, Inc. | Systems and methods for providing location enabled voice mail |
US20080181373A1 (en) * | 2007-01-31 | 2008-07-31 | Brown Jr Thomas W | Call Messaging System |
US20090239507A1 (en) * | 2007-08-31 | 2009-09-24 | William Joseph Sigmund | Systems and Methods for Providing Enhanced Voicemail Services |
US7861088B1 (en) * | 2002-12-10 | 2010-12-28 | Verizon Laboratories Inc. | Method and system for verifiably recording voice communications |
US20110085646A1 (en) * | 2008-06-30 | 2011-04-14 | At&T Mobility Ii Llc | Call Handling Treatment for Voicemail Systems |
US7996036B1 (en) * | 2001-03-13 | 2011-08-09 | At&T Intellectual Property Ii, L.P. | Method and system for providing mobility to enhanced call service features at remote locations |
US20120237008A1 (en) * | 2009-10-20 | 2012-09-20 | At&T Intellectual Property I, L.P. | Message Routing and Determining a Message Recipient in a Unified Messaging System |
US9130895B2 (en) | 2009-10-20 | 2015-09-08 | At&T Intellectual Property I, L.P. | Automatic integrated escalation in a unified messaging system |
US20170353602A1 (en) * | 2016-06-07 | 2017-12-07 | International Business Machines Corporation | Populating contact information on an electronic communication device |
Families Citing this family (90)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9134398B2 (en) | 1996-09-09 | 2015-09-15 | Tracbeam Llc | Wireless location using network centric location estimators |
WO1998010307A1 (en) | 1996-09-09 | 1998-03-12 | Dennis Jay Dupray | Location of a mobile station |
US6236365B1 (en) | 1996-09-09 | 2001-05-22 | Tracbeam, Llc | Location of a mobile station using a plurality of commercial wireless infrastructures |
US6456709B1 (en) * | 1997-03-13 | 2002-09-24 | Metro One Telecommunications, Inc. | Method and apparatus for monitoring telephonic members and providing directory assistance |
US20020136367A1 (en) * | 1997-03-13 | 2002-09-26 | Elsey Nicholas J. | Technique for facilitating communications with a party after initial unsuccessful communications therewith |
US6779358B2 (en) * | 1997-12-30 | 2004-08-24 | International Water Makers, Inc. | Water collection and dispensing machine |
US7522931B2 (en) * | 1998-06-05 | 2009-04-21 | Netnumber, Inc. | Method and apparatus for accessing a network computer to establish a push-to-talk session |
US7283620B2 (en) * | 1999-02-26 | 2007-10-16 | At&T Bls Intellectual Property, Inc. | Systems and methods for originating and sending a voice mail message to an instant messaging platform |
US6882708B1 (en) * | 1999-02-26 | 2005-04-19 | Bellsouth Intellectual Property Corporation | Region-wide messaging system and methods including validation of transactions |
US6707890B1 (en) | 2002-09-03 | 2004-03-16 | Bell South Intellectual Property Corporation | Voice mail notification using instant messaging |
US6223165B1 (en) | 1999-03-22 | 2001-04-24 | Keen.Com, Incorporated | Method and apparatus to connect consumer to expert |
TW445740B (en) * | 1999-11-05 | 2001-07-11 | Ind Tech Res Inst | Message management system and method roaming mobile communication subscribers in multi-site enterprise environment |
US6539079B1 (en) * | 1999-11-12 | 2003-03-25 | Ameritech Corporation | Method and system for providing enhanced call waiting |
CA2322123A1 (en) * | 1999-12-14 | 2001-06-14 | Nortel Networks Corporation | Voice messaging system |
US6823047B1 (en) * | 1999-12-16 | 2004-11-23 | Nortel Networks Limited | Voice messaging system |
WO2001050693A1 (en) * | 2000-01-05 | 2001-07-12 | Www.Internet Solutions Limited | Messaging system |
US6850928B1 (en) * | 2000-01-12 | 2005-02-01 | Avaya Technology Corp. | System and method for automatically retrieving proprietary and standard directory object formats |
US10641861B2 (en) | 2000-06-02 | 2020-05-05 | Dennis J. Dupray | Services and applications for a communications network |
US10684350B2 (en) | 2000-06-02 | 2020-06-16 | Tracbeam Llc | Services and applications for a communications network |
US9875492B2 (en) | 2001-05-22 | 2018-01-23 | Dennis J. Dupray | Real estate transaction system |
US6636590B1 (en) * | 2000-10-30 | 2003-10-21 | Ingenio, Inc. | Apparatus and method for specifying and obtaining services through voice commands |
WO2002037800A2 (en) * | 2000-11-06 | 2002-05-10 | Anphia Van Ellinckhuijzen | An information transmittal system |
US7289623B2 (en) | 2001-01-16 | 2007-10-30 | Utbk, Inc. | System and method for an online speaker patch-through |
US20020133402A1 (en) | 2001-03-13 | 2002-09-19 | Scott Faber | Apparatus and method for recruiting, communicating with, and paying participants of interactive advertising |
US6704403B2 (en) | 2001-09-05 | 2004-03-09 | Ingenio, Inc. | Apparatus and method for ensuring a real-time connection between users and selected service provider using voice mail |
US7580850B2 (en) | 2001-12-14 | 2009-08-25 | Utbk, Inc. | Apparatus and method for online advice customer relationship management |
US7167701B1 (en) * | 2001-12-18 | 2007-01-23 | Bellsouth Intellectual Property Corporation | Voice mailbox with management support |
US7937439B2 (en) | 2001-12-27 | 2011-05-03 | Utbk, Inc. | Apparatus and method for scheduling live advice communication with a selected service provider |
KR20030083209A (en) * | 2002-04-19 | 2003-10-30 | 삼성전자주식회사 | Method for providing caller identification in mobile communication system |
JP2004280515A (en) * | 2003-03-17 | 2004-10-07 | Nec Corp | Method of automatically returning e-mail and portable terminal device |
US7698183B2 (en) | 2003-06-18 | 2010-04-13 | Utbk, Inc. | Method and apparatus for prioritizing a listing of information providers |
US7441203B2 (en) * | 2003-08-11 | 2008-10-21 | Core Mobility, Inc. | Interactive user interface presentation attributes for location-based content |
US20050039135A1 (en) * | 2003-08-11 | 2005-02-17 | Konstantin Othmer | Systems and methods for navigating content in an interactive ticker |
US7430724B2 (en) * | 2003-08-11 | 2008-09-30 | Core Mobility, Inc. | Systems and methods for displaying content in a ticker |
US7370283B2 (en) * | 2003-08-11 | 2008-05-06 | Core Mobility, Inc. | Systems and methods for populating a ticker using multiple data transmission modes |
US20050210391A1 (en) * | 2003-08-11 | 2005-09-22 | Core Mobility, Inc. | Systems and methods for navigating content in an interactive ticker |
US7343564B2 (en) | 2003-08-11 | 2008-03-11 | Core Mobility, Inc. | Systems and methods for displaying location-based maps on communication devices |
US7886009B2 (en) | 2003-08-22 | 2011-02-08 | Utbk, Inc. | Gate keeper |
US20050069095A1 (en) * | 2003-09-25 | 2005-03-31 | International Business Machines Corporation | Search capabilities for voicemail messages |
US8837698B2 (en) * | 2003-10-06 | 2014-09-16 | Yp Interactive Llc | Systems and methods to collect information just in time for connecting people for real time communications |
US8140389B2 (en) | 2003-10-06 | 2012-03-20 | Utbk, Inc. | Methods and apparatuses for pay for deal advertisements |
US8024224B2 (en) | 2004-03-10 | 2011-09-20 | Utbk, Inc. | Method and apparatus to provide pay-per-call advertising and billing |
US9984377B2 (en) | 2003-10-06 | 2018-05-29 | Yellowpages.Com Llc | System and method for providing advertisement |
US7428497B2 (en) | 2003-10-06 | 2008-09-23 | Utbk, Inc. | Methods and apparatuses for pay-per-call advertising in mobile/wireless applications |
US7366683B2 (en) | 2003-10-06 | 2008-04-29 | Utbk, Inc. | Methods and apparatuses for offline selection of pay-per-call advertisers |
US9202220B2 (en) * | 2003-10-06 | 2015-12-01 | Yellowpages.Com Llc | Methods and apparatuses to provide application programming interface for retrieving pay per call advertisements |
US8027878B2 (en) * | 2003-10-06 | 2011-09-27 | Utbk, Inc. | Method and apparatus to compensate demand partners in a pay-per-call performance based advertising system |
US7424442B2 (en) | 2004-05-04 | 2008-09-09 | Utbk, Inc. | Method and apparatus to allocate and recycle telephone numbers in a call-tracking system |
US8121898B2 (en) | 2003-10-06 | 2012-02-21 | Utbk, Inc. | Methods and apparatuses for geographic area selections in pay-per-call advertisement |
US7272400B1 (en) | 2003-12-19 | 2007-09-18 | Core Mobility, Inc. | Load balancing between users of a wireless base station |
US7123697B2 (en) * | 2004-01-14 | 2006-10-17 | Comverse Ltd. | Method and system for providing a call answering service between a source telephone and a target telephone |
US7231019B2 (en) * | 2004-02-12 | 2007-06-12 | Microsoft Corporation | Automatic identification of telephone callers based on voice characteristics |
US20080096587A1 (en) * | 2004-03-11 | 2008-04-24 | Peter Rubinstein | Telephone for Sending Voice and Text Messages |
US20050249339A1 (en) * | 2004-05-05 | 2005-11-10 | Arnoff Mary S | Providing notification of voicemail (VM) messages using instant messaging (IM) transport |
US7873149B2 (en) * | 2004-06-01 | 2011-01-18 | Verizon Business Global Llc | Systems and methods for gathering information |
US8392193B2 (en) * | 2004-06-01 | 2013-03-05 | Verizon Business Global Llc | Systems and methods for performing speech recognition using constraint based processing |
CA2571843C (en) * | 2004-12-27 | 2014-12-30 | Bce Inc. | Methods and systems for rendering voice mail messages amenable to electronic processing by mailbox owners |
US7864930B2 (en) * | 2004-12-27 | 2011-01-04 | Bce Inc. | Systems and methods for registration and retrieval of voice mail contact information |
US20060159237A1 (en) * | 2004-12-27 | 2006-07-20 | Clark David W | Systems and methods for rendering voice mail contact information available to a called party |
CA2571847C (en) * | 2004-12-27 | 2014-04-08 | Bce Inc. | Method and system to enable submission and subsequent retrieval of enhanced voice mail messages |
US9202219B2 (en) | 2005-02-16 | 2015-12-01 | Yellowpages.Com Llc | System and method to merge pay-for-performance advertising models |
US8538768B2 (en) | 2005-02-16 | 2013-09-17 | Ingenio Llc | Methods and apparatuses for delivery of advice to mobile/wireless devices |
US7979308B2 (en) | 2005-03-03 | 2011-07-12 | Utbk, Inc. | Methods and apparatuses for sorting lists for presentation |
US8934614B2 (en) * | 2005-02-25 | 2015-01-13 | YP Interatcive LLC | Systems and methods for dynamic pay for performance advertisements |
US20060217110A1 (en) * | 2005-03-25 | 2006-09-28 | Core Mobility, Inc. | Prioritizing the display of non-intrusive content on a mobile communication device |
US7353034B2 (en) | 2005-04-04 | 2008-04-01 | X One, Inc. | Location sharing and tracking using mobile phones or other wireless devices |
US8761154B2 (en) | 2005-09-28 | 2014-06-24 | Ebbe Altberg | Methods and apparatuses to access advertisements through voice over internet protocol (VoIP) applications |
US8599832B2 (en) | 2005-09-28 | 2013-12-03 | Ingenio Llc | Methods and apparatuses to connect people for real time communications via voice over internet protocol (VOIP) |
US9197479B2 (en) | 2006-01-10 | 2015-11-24 | Yellowpages.Com Llc | Systems and methods to manage a queue of people requesting real time communication connections |
US7720091B2 (en) | 2006-01-10 | 2010-05-18 | Utbk, Inc. | Systems and methods to arrange call back |
US8125931B2 (en) | 2006-01-10 | 2012-02-28 | Utbk, Inc. | Systems and methods to provide availability indication |
US8681778B2 (en) | 2006-01-10 | 2014-03-25 | Ingenio Llc | Systems and methods to manage privilege to speak |
US8625749B2 (en) * | 2006-03-23 | 2014-01-07 | Cisco Technology, Inc. | Content sensitive do-not-disturb (DND) option for a communication system |
US8391447B2 (en) * | 2006-05-02 | 2013-03-05 | Smith Micro Software, Inc | Visual voice messaging state synchronization |
US20070274465A1 (en) * | 2006-05-02 | 2007-11-29 | Core Mobility, Inc. | Providing unified access to voice messages from disparate systems |
EP2074836A2 (en) * | 2006-08-17 | 2009-07-01 | Core Mobility, Inc. | Presence-based communication between local wireless network access points and mobile devices |
US20080069316A1 (en) * | 2006-09-20 | 2008-03-20 | Sbc Knowledge Ventures, L.P. | Method and apparatus for processing voicemail messages in a multi-user setting |
US9317855B2 (en) | 2006-10-24 | 2016-04-19 | Yellowpages.Com Llc | Systems and methods to provide voice connections via local telephone numbers |
US8135123B2 (en) * | 2007-01-03 | 2012-03-13 | At&T Intellectual Property I, L.P. | Methods, systems, and products for responding to communications |
US8451825B2 (en) | 2007-02-22 | 2013-05-28 | Utbk, Llc | Systems and methods to confirm initiation of a callback |
US20080192905A1 (en) * | 2007-02-13 | 2008-08-14 | Cisco Technology, Inc. | Storage and retrieval of a caller's spoken name |
US20080262910A1 (en) * | 2007-04-20 | 2008-10-23 | Utbk, Inc. | Methods and Systems to Connect People via Virtual Reality for Real Time Communications |
US20080263460A1 (en) * | 2007-04-20 | 2008-10-23 | Utbk, Inc. | Methods and Systems to Connect People for Virtual Meeting in Virtual Reality |
US9277019B2 (en) | 2007-06-18 | 2016-03-01 | Yellowpages.Com Llc | Systems and methods to provide communication references to connect people for real time communications |
US8838476B2 (en) * | 2007-09-07 | 2014-09-16 | Yp Interactive Llc | Systems and methods to provide information and connect people for real time communications |
US9538493B2 (en) | 2010-08-23 | 2017-01-03 | Finetrak, Llc | Locating a mobile station and applications therefor |
US8892444B2 (en) * | 2011-07-27 | 2014-11-18 | International Business Machines Corporation | Systems and methods for improving quality of user generated audio content in voice applications |
CN104254127B (en) * | 2013-06-28 | 2018-08-21 | 展讯通信(上海)有限公司 | Page communication method and apparatus |
US10692156B2 (en) | 2014-09-05 | 2020-06-23 | Thomas Skala | Payment system and method |
US10057423B1 (en) * | 2015-12-03 | 2018-08-21 | Babak Sheikh | System and method for responding to telephone calls and written communications |
Family Cites Families (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0036619A1 (en) * | 1980-03-25 | 1981-09-30 | Siemens Aktiengesellschaft | Circuit arrangement for a telephone exchange, particularly for a private automatic branch exchange, with a message store for recalling |
US4942598A (en) * | 1988-03-04 | 1990-07-17 | Motorola, Inc. | Telephone answering machine in paging systems with automatic number identification based message operations |
US4924496A (en) | 1988-05-12 | 1990-05-08 | Romek Figa D/B/A Abraham & Sons | Automatic incoming telephone call originating number and party display system |
JPH02134052A (en) * | 1988-11-15 | 1990-05-23 | Nippon Telegr & Teleph Corp <Ntt> | Automatic reply telephone system |
US5046088A (en) | 1989-10-31 | 1991-09-03 | Dialogic Corporation | Converter for in-band routing and/or origination information |
US5040208A (en) * | 1989-11-03 | 1991-08-13 | International Business Machines Corporation | Coordinated voice and data display having temporary storage of transaction data |
JPH03174858A (en) * | 1989-12-04 | 1991-07-30 | Tamura Electric Works Ltd | Automatic answering telephone system |
US5646839A (en) * | 1990-05-29 | 1997-07-08 | Mcic Communications Corporation | Telephone-based personnel tracking system |
US5390236A (en) * | 1992-03-31 | 1995-02-14 | Klausner Patent Technologies | Telephone answering device linking displayed data with recorded audio message |
WO1994006236A2 (en) | 1992-08-26 | 1994-03-17 | Bellsouth Corporation | Personal number communications system |
US5594784A (en) * | 1993-04-27 | 1997-01-14 | Southwestern Bell Technology Resources, Inc. | Apparatus and method for transparent telephony utilizing speech-based signaling for initiating and handling calls |
DE4436175B4 (en) * | 1993-10-12 | 2005-02-24 | Intel Corporation, Santa Clara | Device for remote access to a computer from a telephone handset |
FR2711872B1 (en) * | 1993-10-21 | 1996-02-09 | Jean Pierre Talvard | Independent portable device forming directory and telephone dialer. |
DE4401518A1 (en) * | 1994-01-20 | 1995-07-27 | Telefonbau & Normalzeit Gmbh | Method for operating an automatic ordering system in communication switching systems |
US5608784A (en) * | 1994-01-24 | 1997-03-04 | Miller; Joel F. | Method of personnel verification using voice recognition |
US5799061A (en) * | 1994-04-26 | 1998-08-25 | Greater Harris County 9-1-1 Emergency Network | Computer integrated telephony system for the processing of 9-1-1 calls for service |
ATE200172T1 (en) | 1994-10-31 | 2001-04-15 | Worldvoice Licensing Inc | CONTROL METHOD FOR THE TRANSMISSION OF TELEPHONE ANNOUNCEMENTS |
US5684862A (en) | 1995-05-24 | 1997-11-04 | Advance Systems Development Company, L.C. | Telephone voice message store and forward method |
US5809128A (en) * | 1996-11-01 | 1998-09-15 | Interactive Telecom Inc. | Method and apparatus permitting notification and control of blocked incoming calls over a data network |
US5940476A (en) * | 1996-06-28 | 1999-08-17 | Distributed Software Development, Inc. | System and method for identifying an unidentified caller |
GB2312593A (en) * | 1996-04-26 | 1997-10-29 | Ibm | Voice mail with remote voice processing |
US5740230A (en) * | 1996-05-31 | 1998-04-14 | Octel Communications Corporation | Directory management system and method |
KR0185013B1 (en) * | 1996-06-07 | 1999-05-15 | 이계철 | Automatic answering service method |
US6005922A (en) * | 1996-11-12 | 1999-12-21 | Nortel Networks Corporation | Voice mail system and method of inter-voice mail system communication |
KR100268664B1 (en) * | 1996-12-21 | 2000-10-16 | 윤종용 | Apparatus and method for controlling automatic answering service of portable telephone in a base station |
US6038305A (en) * | 1997-03-28 | 2000-03-14 | Bell Atlantic Network Services, Inc. | Personal dial tone service with personalized caller ID |
US6122357A (en) * | 1997-03-28 | 2000-09-19 | Bell Atlantic Network Services, Inc. | Providing enhanced services through double SIV and personal dial tone |
US5943395A (en) * | 1997-05-30 | 1999-08-24 | Northern Telecom Limited | Telephone apparatus, systems, and processes to enhance access for TDD and/or TTY devices |
US6061432A (en) * | 1997-12-23 | 2000-05-09 | Bell Atlantic Network Services, Inc. | Voice mail system for obtaining routing information from signaling nodes |
-
1998
- 1998-06-05 US US09/092,764 patent/US6292799B1/en not_active Expired - Fee Related
-
1999
- 1999-06-04 CN CNB998079529A patent/CN1146214C/en not_active Expired - Fee Related
- 1999-06-04 EP EP99955380A patent/EP1084557A4/en not_active Withdrawn
- 1999-06-04 JP JP2000552828A patent/JP2002517953A/en active Pending
- 1999-06-04 AU AU43347/99A patent/AU748758B2/en not_active Ceased
- 1999-06-04 WO PCT/US1999/012656 patent/WO1999063734A1/en not_active Application Discontinuation
-
2001
- 2001-02-20 US US09/789,050 patent/US20020049768A1/en not_active Abandoned
Cited By (48)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7996036B1 (en) * | 2001-03-13 | 2011-08-09 | At&T Intellectual Property Ii, L.P. | Method and system for providing mobility to enhanced call service features at remote locations |
US20030046400A1 (en) * | 2001-08-22 | 2003-03-06 | Owen Friel | Contacting a destination terminal from an originating terminal via a packet-based communications network |
US7861088B1 (en) * | 2002-12-10 | 2010-12-28 | Verizon Laboratories Inc. | Method and system for verifiably recording voice communications |
FR2856543A1 (en) * | 2003-06-20 | 2004-12-24 | Sin Etke Technology Co Ltd | ANSWERING SYSTEM FOR CUSTOMER SERVICE |
WO2006135591A1 (en) * | 2005-06-10 | 2006-12-21 | Lucent Technologies, Inc. | Systems and methods for providing location enabled voice mail |
US20060291629A1 (en) * | 2005-06-10 | 2006-12-28 | Lucent Technologies Inc. | Systems and methods for providing location enabled voice mail |
US20080181373A1 (en) * | 2007-01-31 | 2008-07-31 | Brown Jr Thomas W | Call Messaging System |
US8401526B2 (en) | 2007-08-31 | 2013-03-19 | At&T Mobility Ii Llc | Systems and methods for providing a password reset feature |
US8831573B2 (en) | 2007-08-31 | 2014-09-09 | At&T Mobility Ii Llc | Video greetings for voicemail systems |
US20100159888A1 (en) * | 2007-08-31 | 2010-06-24 | William Joseph Sigmund | Voicemail Forwarding Functionality for Communications Networks |
US20100159886A1 (en) * | 2007-08-31 | 2010-06-24 | William Joseph Sigmund | Systems and Methods for Updating Voicemail With Selective Establishment of PDP Contexts and Data Sessions |
US20100159891A1 (en) * | 2007-08-31 | 2010-06-24 | William Joseph Sigmund | Enhanced Messaging With Language Translation Feature |
US20100159890A1 (en) * | 2007-08-31 | 2010-06-24 | William Joseph Sigmund | Video Greetings for Voicemail Systems |
US20100167699A1 (en) * | 2007-08-31 | 2010-07-01 | William Joseph Sigmund | Systems and Methods for Consolidating Wireline and Wireless Voicemail Boxes |
US20100189229A1 (en) * | 2007-08-31 | 2010-07-29 | At&T Mobility Ii Llc | Toggling Voicemail Class of Service |
US20100195807A1 (en) * | 2007-08-31 | 2010-08-05 | At&T Mobility Ii Llc | Secure Visual Voicemail |
US20100222024A1 (en) * | 2007-08-31 | 2010-09-02 | At&T Mobility Ii Llc | Systems and Methods for Providing a Password Reset Feature |
US20090253407A1 (en) * | 2007-08-31 | 2009-10-08 | William Joseph Sigmund | Systems and Methods for Providing Enhanced Voicemail Services |
USRE46952E1 (en) | 2007-08-31 | 2018-07-10 | Nuance Communications, Inc. | Systems and methods for consolidating wireline and wireless voicemail boxes |
US20090253413A1 (en) * | 2007-08-31 | 2009-10-08 | William Joseph Sigmund | Systems and Methods for Providing Enhanced Voicemail Services |
US9210558B2 (en) | 2007-08-31 | 2015-12-08 | At&T Mobility Ii Llc | Updating voicemail with selective establishment of PDP contexts and data sessions |
US8306509B2 (en) | 2007-08-31 | 2012-11-06 | At&T Mobility Ii Llc | Enhanced messaging with language translation feature |
US8340644B2 (en) | 2007-08-31 | 2012-12-25 | At&T Mobility Ii Llc | Voicemail forwarding functionality for communications networks |
US8351903B2 (en) | 2007-08-31 | 2013-01-08 | At&T Mobility Ii, Llc | Updating voicemail with selective establishment of PDP contexts and data sessions |
US20090239507A1 (en) * | 2007-08-31 | 2009-09-24 | William Joseph Sigmund | Systems and Methods for Providing Enhanced Voicemail Services |
US8406743B2 (en) * | 2007-08-31 | 2013-03-26 | At&T Mobility Ii Llc | Systems and methods for consolidating wireline and wireless voicemail boxes |
US8412162B2 (en) | 2007-08-31 | 2013-04-02 | At&T Mobility Ii Llc | Systems and methods for providing enhanced voicemail services |
US8442496B2 (en) | 2007-08-31 | 2013-05-14 | At&T Mobility Ii Llc | Enhanced messaging with language translation feature |
US8478239B2 (en) | 2007-08-31 | 2013-07-02 | At&T Mobility Ii Llc | Video greetings for voicemail systems |
US8489074B2 (en) | 2007-08-31 | 2013-07-16 | At&T Mobility Ii Llc | Systems and methods for providing enhanced voicemail services |
US8503988B2 (en) | 2007-08-31 | 2013-08-06 | At&T Mobility Ii Llc | Systems and methods for providing a password reset feature |
US8509745B2 (en) | 2007-08-31 | 2013-08-13 | At&T Mobility Ii Llc | Voicemail archival and forwarding functionality for communications networks and devices |
US8515395B2 (en) | 2007-08-31 | 2013-08-20 | At&T Mobility Ii Llc | Systems and methods for providing enhanced voicemail services |
US8548438B2 (en) | 2007-08-31 | 2013-10-01 | At&T Mobility Ii Llc | Systems and methods for providing enhanced voicemail services |
US8688082B2 (en) | 2007-08-31 | 2014-04-01 | At&T Mobility Ii Llc | Systems and methods for consolidating wireline and wireless voicemail boxes |
US8737580B2 (en) | 2007-08-31 | 2014-05-27 | At&T Mobility Ii Llc | Toggling voicemail class of service |
US8977241B2 (en) | 2007-08-31 | 2015-03-10 | At&T Mobility Ii Llc | Voicemail forwarding functionality for communications networks |
US8798241B2 (en) | 2007-08-31 | 2014-08-05 | At&T Mobility Ii Llc | Secure visual voicemail |
US20090253412A1 (en) * | 2007-08-31 | 2009-10-08 | William Joseph Sigmund | Systems and Methods for Providing Enhanced Voicemail Services |
US8843117B2 (en) | 2007-08-31 | 2014-09-23 | At&T Mobility Ii Llc | Voicemail archival and forwarding functionality for communications networks and devices |
US8923825B2 (en) | 2007-08-31 | 2014-12-30 | At&T Mobility Ii Llc | Enhanced messaging with language translation feature |
US8798238B2 (en) | 2008-06-30 | 2014-08-05 | At&T Mobility Ii Llc | Call handling treatment for voicemail systems |
US20110085646A1 (en) * | 2008-06-30 | 2011-04-14 | At&T Mobility Ii Llc | Call Handling Treatment for Voicemail Systems |
US8934615B2 (en) * | 2009-10-20 | 2015-01-13 | At&T Intellectual Property I, L.P. | Message routing and determining a message recipient in a unified messaging system |
US9130895B2 (en) | 2009-10-20 | 2015-09-08 | At&T Intellectual Property I, L.P. | Automatic integrated escalation in a unified messaging system |
US20120237008A1 (en) * | 2009-10-20 | 2012-09-20 | At&T Intellectual Property I, L.P. | Message Routing and Determining a Message Recipient in a Unified Messaging System |
US20170353602A1 (en) * | 2016-06-07 | 2017-12-07 | International Business Machines Corporation | Populating contact information on an electronic communication device |
US10110733B2 (en) * | 2016-06-07 | 2018-10-23 | International Business Machines Corporation | Populating contact information on an electronic communication device |
Also Published As
Publication number | Publication date |
---|---|
EP1084557A4 (en) | 2004-11-17 |
AU4334799A (en) | 1999-12-20 |
CN1346567A (en) | 2002-04-24 |
EP1084557A1 (en) | 2001-03-21 |
CN1146214C (en) | 2004-04-14 |
AU748758B2 (en) | 2002-06-13 |
WO1999063734A9 (en) | 2000-03-09 |
US6292799B1 (en) | 2001-09-18 |
JP2002517953A (en) | 2002-06-18 |
WO1999063734A1 (en) | 1999-12-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6292799B1 (en) | Method and apparatus to automatically address a voice mail reply to a voice mail message | |
US9462120B2 (en) | Caller ID memo system | |
US6442242B1 (en) | Multifunction autoattendant system and method of operation thereof | |
KR100293398B1 (en) | Voice processing system | |
US6775272B2 (en) | Virtual PBX system | |
US8031855B2 (en) | Method for providing enhanced directory assistance upon command using out-of-band signaling | |
US7072452B1 (en) | Saving and forwarding customized messages | |
US20060233338A1 (en) | User-configurable call answering/redirection mechanism | |
US7272214B2 (en) | Flexible distributed/centralized architecture for voice/unified messaging system | |
CA2349309A1 (en) | Unified communications automated personal name addressing | |
EP1267557A1 (en) | Caller selection of an alternate call destination when called terminal is unavailable | |
US20040096043A1 (en) | Technique for assisting a user with information services at an information/call center | |
US9088587B2 (en) | Method, communication system and communication terminal for the transmission of data | |
CN1860465B (en) | System and method for emulating local telephone service by Internet | |
US6643365B1 (en) | System for providing calling party selection of destination when multiple telephones share the same telephone number | |
Cheston III et al. | System for obtaining forwarding information for electronic system using speech recognition | |
US6834106B1 (en) | Call control system and method | |
EP1111891A2 (en) | Method for addressing a message from a telephone | |
US7730188B1 (en) | Virtual voice/company/office network tool kit, method, and computer program product | |
EP1434415B1 (en) | Flexible distributed/centralized architecture for voice/unified messaging system | |
US20040202152A1 (en) | Remote policy assistant with PSTN/internet inter-working for QoS and enabled services |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: ENTERPRISE BANK, MASSACHUSETTS Free format text: SECURITY INTEREST;ASSIGNOR:NETNUMBER, INC;REEL/FRAME:035202/0478 Effective date: 20150317 |
|
AS | Assignment |
Owner name: NETNUMBER, INC., MASSACHUSETTS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:ENTERPRISE BANK;REEL/FRAME:053380/0856 Effective date: 20200729 |