[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2012054012A1 - Systèmes et procédés d'adaptateur de terminal multimédia voip - Google Patents

Systèmes et procédés d'adaptateur de terminal multimédia voip Download PDF

Info

Publication number
WO2012054012A1
WO2012054012A1 PCT/US2010/002803 US2010002803W WO2012054012A1 WO 2012054012 A1 WO2012054012 A1 WO 2012054012A1 US 2010002803 W US2010002803 W US 2010002803W WO 2012054012 A1 WO2012054012 A1 WO 2012054012A1
Authority
WO
WIPO (PCT)
Prior art keywords
profile
handset
call
user
line
Prior art date
Application number
PCT/US2010/002803
Other languages
English (en)
Inventor
Steven Lee Cooper
Original Assignee
Thomson Licensing
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Thomson Licensing filed Critical Thomson Licensing
Priority to PCT/US2010/002803 priority Critical patent/WO2012054012A1/fr
Publication of WO2012054012A1 publication Critical patent/WO2012054012A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102—Entity profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • 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/42229—Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location
    • H04M3/42263—Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location where the same subscriber uses different terminals, i.e. nomadism
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2203/00—Aspects of automatic or semi-automatic exchanges
    • H04M2203/60—Aspects of automatic or semi-automatic exchanges related to security aspects in telephonic communication systems
    • H04M2203/6081—Service authorization mechanisms

Definitions

  • VoIP Voice over Internet Protocol
  • IP internet protocol
  • VoIP telephone call is implemented by converting an analog voice signal from a telephone to a digital format and compressing or translating the signal into IP packets for transmission over an IP network.
  • MTA multimedia terminal adapter
  • MTAs and associated handsets on a user's premises are limited in several respects. For example, users currently cannot log a handset into multiple telephones lines/profiles provided by the MTA. Another limitation of currently available MTAs is that they prevent a user of one profile from accessing call logs of a different profile. In addition, such systems fail to record calls made to lines/profiles in certain scenarios. For example, in current MTA systems, when a handset that is allocated to one profile is used to answer a call directed to a different profile, the MTA systems fail to log the call in the call log of the profile to which the call was originally directed. Further, current MTA systems are configured to ring all handsets when a call is received on a particular line/profile, thereby permitting all users to access all calls, which can be undesirable in many situations.
  • an aspect of the present principles includes a prompt login feature that can be implemented through a handset to enable the handset to logon to multiple lines/profiles. This aspect permits a user to quickly logon an unauthorized handset to a line/profile as a call is received on the line/profile to enable the user to answer the call.
  • an MTA in accordance with one embodiment can be configured to enable flexible access of at least a portion of call logs between different profiles.
  • an incoming call can be received in accordance with VoIP.
  • a user can be prompted to log a handset on to a profile on which the call is being received.
  • login information can be received from the user and the handset can be allocated to the profile on which the call is being received to permit the user to answer the call.
  • the system can include a plurality of VoIP telephone handsets and an MTA.
  • the MTA can be configured to logon at least a first handset of the plurality of handsets to one or more profiles in response to receiving login information from the first handset.
  • An alternative exemplary embodiment is directed to a system.
  • the system can include a plurality of VoIP telephone handsets and an MTA.
  • the MTA can be configured to store a respective call log for each profile associated with respective telephone lines provided through the MTA such that at least a portion of a call log for a first profile is accessible by a handset that is not logged on to the first profile.
  • FIG. 1 is a block diagram of a VoIP communication system.
  • FIG. 2 is a block diagram of an MTA system and corresponding devices serviced by the MTA.
  • FIG. 3 is a block/flow diagram of a method for allocating a VoIP handset to a line/profile in accordance with a prompt login feature.
  • FIG. 4 is a block/flow diagram of a method for performing an outgoing call in accordance with a prompt login feature.
  • FIG. 5 is a block/flow diagram of a method for transferring a call by employing call logs.
  • FIG. 6 is a block/flow diagram of a method for logging a telephone call.
  • FIG. 7 is a block/flow diagram of a method for restricting ringing of devices in accordance with line/profile allocations that can be implemented at an MTA.
  • FIG. 8 is a block/flow diagram of a method for restricting ringing of devices in accordance with line/profile allocations that can be implemented at a telephone handset.
  • the system 100 can include one or more Voice over Internet Protocol (VoIP) telephone handsets 101-103 that are connected to and are in signal communication with a Multimedia Terminal Adapter (MTA) 105 of a VoIP system on a user's premises 107.
  • VoIP Voice over Internet Protocol
  • MTA Multimedia Terminal Adapter
  • three handsets are shown as an example; the MTA can service any number of handsets in accordance with design choice.
  • the MTA 105 can also service one or more other devices 104, such as a fax machine.
  • the MTA 105 can be connected to and can be in signal communication with a cable modem (CM) 106 to enable the devices 101-104 to access a cable network 108 using VoIP. It should be noted that the MTA 105 and the cable modem 106 can be separate units or can be integrated in a single unit.
  • the system 100 can further include a Cable Modem Termination System (CMTS) 1 10 (commonly referred to as a cable head-end) that can be in the local cable network 108 and can be configured to act as an interface between the local cable network 108 of a service provider and an IP network 112, such as the internet.
  • CMTS Cable Modem Termination System
  • the CMTS 110 can be connected to a telephony gateway 1 14 on the IP network 1 12 to provide access to a Plain Old Telephone Service (POTS) network 1 16, such as a Public Switch Telephone Network (PSTN).
  • POTS Plain Old Telephone Service
  • PSTN Public Switch Telephone Network
  • the MTA 105 can, for example, be configured to convert between analog voice signals and IP packetized voice signals while the telephony gateway 1 14 can, for example, be configured to convert between IP packetized voice and standard pulse code modulated signals for the POTS network.
  • processor or “controller” should not be construed to refer exclusively to hardware capable of executing software, and can implicitly include, without limitation, digital signal processor (“DSP”) hardware, read-only memory (“ROM”) for storing software, random access memory (“RAM”) and non-volatile storage.
  • DSP digital signal processor
  • ROM read-only memory
  • RAM random access memory
  • the MTA 105 can include a controller 202, which can be configured to manage operations of the MTA 105 and to manage communication with the handsets 101-103 and the other device(s) 104, such as a fax machine, using novel methods described in more detail below.
  • the user-interface 204 of the MTA 105 can include a display and a keypad to permit a user to configure and communicate with the MTA 105 as an alternative to using the handsets 101-103 and the other device(s) 104.
  • the controller 202 can employ the cable modem interface 206 to connect the MTA system 105 to the cable network 108 via the modem 106.
  • the MTA 105 can also include a telephone handset interface(s) 208 and a device interface 210 to permit the MTA 105 to communicate with handsets 101-103 and other device(s) 104, respectively, as shown. It should be understood that the interfaces 208 and 210 can be wired, wireless or can include both wired and wireless components.
  • the MTA 105 can further comprise a storage medium 212, on which a reference table 214 and call logs 216-222 can be stored.
  • the table 214 can include information that relates the handsets 101-103, and also the other device(s) 104, to one or more lines/profiles, which can be referenced by the controller 202 to keep track of the line/profile allocations and determine to which devices 101-104 calls should be forwarded, as discussed in more detail below. Additionally, call logs 216-222 can record a listing of calls answered and made on each line/profile and each device 101-104.
  • the MTA 105 services four lines/profiles, denoted as P.1-P.4. It should be noted that, in accordance with exemplary embodiments described herein, each profile is assigned and associated with a different line/telephone number.
  • each handset 101-103 can include a display 224, standard keys 226 and shortcut keys 228.
  • the standard keys 226 can include keys denoting digits, a "power on" button, a speaker phone button and a menu key.
  • the shortcut keys 228 can facilitate user-navigation to access certain information. For example, currently available VoIP systems require a user to navigate through a number of menus to access certain information, such as call logs.
  • the shortcut keys 228 can permit users to quickly access such information. For example, a user can select a "down arrow" to automatically display a contact list for a profile to which the handset is logged on and connected.
  • Shortcut keys 228 can further include additional keys, such as a dedicated key for automatically redialing the last-dialed telephone number.
  • the MTA 105 can facilitate prompt modification of line/profile assignments to handsets using a login feature.
  • the MTA 105 can permit each telephone handset 101-103 to be logged into multiple
  • any one or more of the handsets 101 -103 can be configured to display a menu in response to user- selection of a key 226.
  • the menu can provide an option for a user to log-on to one or more lines/profiles and can display a listing of lines/profiles available at the user's premises 107.
  • the handset can prompt a user to enter a password.
  • the password can be an administrator password that provides access to all available lines/profiles or can be specific to one or more lines/profiles.
  • the password can be alphanumeric or can comprise biometric data, such as a thumb/fingerprint.
  • the "password” can also correspond to data obtained through voice/command recognition, facial recognition using a built-in camera, or through other means.
  • the user can simply press a button, which would register the print, or say their name or a pass-phrase and the MTA 105 can permit the user to answer the call for the correct profile.
  • RFID radio frequency identification
  • the handset can transmit the password and an identifier for the requested line/profile to the MTA 105 via the interface 208.
  • the controller 202 can cross-reference the received password with a password stored in the storage medium 212 for the requested line/profile. If the passwords match, then the handset from which the request was received is listed under the requested line/profile in the reference table 214. In this way, the handset can be assigned to a particular line/profile to permit the handset to receive and make calls on the line/profile.
  • a user can de-allocate a line/profile from a handset in a similar manner.
  • the menu can provide an option for a user to deallocate one or more lines/profiles and can display a listing of lines/profiles to which the handset is allocated.
  • the user can select a line/profile to de-allocate, in response to which the handset can prompt the user to enter a password.
  • the handset can transmit the entered password and an identifier for the line/profile to be de-allocated to the MTA 105 via the interface 208.
  • the controller 202 can cross-reference the received password with a password stored in the storage medium 212 for the selected line/profile and can de-allocate the handset in the reference table 214 if the passwords match.
  • the prompt login feature discussed above can permit a user to conveniently access lines/profiles in a novel manner in a variety of situations.
  • the telephone/handsets 101-103 are initially allocated to respective lines/profiles P.1-P.3, where handset 101 is allocated line/profile P.l, handset 102 is allocate line/profile P. 2, etc.
  • handsets are restricted from accessing or receiving calls on lines/profiles to which the handsets are not logged on. If the MTA 105 receives a call on line/profile P.l, the login feature permits a user to quickly allocate a handset to the line/profile P.l.
  • the user can allocate the handset 102 to line/profile P.l to answer the call before the caller hangs up or before the call is forwarded to a voicemail server.
  • the MTA 105 and the handsets 101-103 can be configured such that a handset which is not allocated to a line/profile that is receiving a call can ring.
  • the handset 102 in the scenario described above can ring and can display a message prompting a user to enter a password for the line/profile on which a call is received and/or can notify the ⁇ user that the handset(s) logged on to the line/profile on which a call is received should be used, which in this case is handset 101.
  • the handset 102 can be allocated the line/profile P.l as described above and can answer the call using the handset 102 before the caller hangs up or before the call is forwarded to a voicemail server.
  • the method 300 can begin at step 302, in which the MTA 105 can receive a call in accordance with VoIP on a line/profile.
  • the MTA 105 can receive a call through the cable network 108, as discussed above with regard to FIG. 1.
  • a handset 101-103 can prompt a user to log the handset onto the line/profile on which the call is received.
  • a telephone/handset 102 can ring when a call is received on a line/profile P.l to which the handset 102 is not logged on and the user can be prompted to enter a password to logon to the line/profile P.l .
  • the handset 102 is configured to not ring for calls received on line/profiles to which the handset 102 is not logged on, as discussed in further detail below with respect to an exemplary embodiment, the user can hear a different handset ring.
  • the user can hear handset 101 ring in a different room and can direct the handset 102 to display a menu, where the user is prompted to log-on to the profile P. 1, as discussed above with regard to FIG. 2.
  • the menu can correspond to the same menu displayed at step 404 of method 400, which is discussed in more detail herein below.
  • the handset 101-103 can receive login information from the user. For example, as discussed above with regard to FIG. 2, the user can enter an administrator password or a password specific to the line/profile on which the call is received. Further, the handset can transmit the login information to the controller 202 to permit the controller 202 to verify the login information.
  • the controller 202 of the MTA 105 can determine whether the login information is correct. For example, as discussed above with regard to FIG. 2, the controller 202 can cross-reference the received password with a password stored for the line/profile on which the call is received. If the passwords do not match, then the controller 202 deems the information to be incorrect and the method can proceed to step 304 and can be repeated. If the passwords do match, then the controller 202 deems the information to be correct and the method can proceed to step 310. At step 310, the controller 202 of the MTA 105 can allocate the handset 101-103 to the line/profile on which the call is received to permit the user to answer the call.
  • the controller 202 can augment the reference table 214 so that an identifier for the handset, for example, handset 102 in the scenario described above, is listed under the line/profile on which the call is received. Thereafter, the controller 202 can grant the handset access to the telephone call.
  • the prompt login feature permits a user to answer a call using an unauthorized handset before the caller hangs up or before the call is forwarded to a voicemail server.
  • the login feature provides a significant advantage over MTA systems in which allocation of lines/profiles to handsets is relatively complex and is implemented during a system set-up.
  • the MTA 105 can be configured to employ a default line for each handset. For example, when a handset prompts a user to enter a password to logon to a line/profile, as described above, the handset can also prompt the user to select an option to set the line/profile as the default line profile for the handset. In turn, in response to user-selection of the option and verification that the password is correct, the controller 202 can insert an identifier for the handset under the requested line/profile in the reference table 214 and can flag the identifier to indicate that the requested line/profile is the default line for the handset. Thus, when a user attempts to make an outgoing call with the handset, the controller 202 can automatically connect the handset to that handset's default line/profile to permit the user to make the outgoing call on the default line.
  • the system 200 can permit a user to select a line/profile on which to make an outgoing call.
  • a method 400 for enabling a user to select a line/profile for an outgoing call in accordance with a login feature is illustrated.
  • the method 400 can begin at step 402 in which a handset 101- 103 can receive an indication that a user is making an outgoing call.
  • the handset can detect when the user lifts the handset from a base or when a user selects a power- on button within the set of keys 226.
  • the handset 101-103 can display a list of available profiles. For example, the handset can display the list automatically in response to receiving the indication that a user is making an outgoing call or can display the list in response to user-selection of a dedicated menu key from the set of keys 226.
  • the list can include all available lines/profiles and can include icons to indicate to which of the available lines/profiles the handset is logged on.
  • the handset 101-103 can receive a line/profile selection. For example, the user can scroll through the list using a cursor and can select the line/profile using one of the keys 226, such as a "select" key.
  • the list can have numbered entries for the lines/profiles and the user can select a digit among the keys 226 corresponding to the desired line/profile in the list.
  • the handset 101-103 can prompt the user to login to the selected profile.
  • the handset can perform step 408 if the handset is not logged onto the selected line/profile.
  • the handset can prompt the user to enter a password to login to the selected line/profile.
  • the handset 101-103 can receive login information from the user, for example, as described above with respect to step 306.
  • the controller 202 of the MTA 105 can determine whether the login information is correct, for example, as described above with respect to step 308. If the login information is not correct, then the method can proceed to step 408 and can be repeated. If the login information is correct, then the method can proceed to step 414.
  • the controller 202 can connect and log the handset on to the selected line/profile to permit the user to make an outgoing call.
  • the system 100 can be configured to permit a user to employ a handset to access at least a portion of one or more logs 216-222 for lines profiles to which the handset is not logged on in addition to the logs to which the handset is logged on.
  • the controller 202 can permit each handset 101-103 to access the last dialed telephone number and the telephone number of the last received call on each of the lines/profiles P.1-P.4 available on the user's premises 107.
  • This feature can permit a user to receive a call on one line/profile, hang up and choose another handset logged into a different line/profile, or simply choose another line/profile from the same handset, to callback that same number.
  • This feature can be useful if the user wishes to free up a main line so that he or she can receive other calls on the main line.
  • the system can provide a user with a menu option to permit the transfer of the call to another line/profile.
  • the method 500 can begin at step
  • the system can conduct a call in accordance with VoIP.
  • the handset 101 can receive or make a call on line/profile P.l .
  • the controller 202 and/or the handset 101 can store the telephone number of the current call.
  • the controller 202 can log the telephone number from which the call is received or to which the call was dialed in the log 216 for line/profile P.1.
  • the handset 101 can be configured to store the telephone number for the last call that was conducted on the handset.
  • the controller 202 can terminate the call.
  • the user can direct the handset 201 to terminate the call for purposes of transferring the call to another profile/line.
  • the controller 202 can switch access to a different line/profile.
  • the user can simply hang-up handset 101 and use handset 102, which is logged into profile P.2 in the exemplary scenario described above.
  • the controller 202 can change the line/profile to which the handset 101 is connected by permitting the user to select or log into another line/profile, such as P.2, by implementing the method 400 described above.
  • the controller 202 can permit the user to access a log for another line/profile.
  • the user can employ handset 102, which is logged on to line/profile P.2, to access the log 216 for the line/profile P.l.
  • the user can employ the handset 101 from line/profile P. 2 to access the log 216 for the line/profile P.1.
  • the user can select a dedicated menu key from keys 226, in response to which the handset can display an option to view logs 216-222.
  • the handset can display a list of the available logs and can permit the user to select any of the logs.
  • the handset can transmit the log-selection, which in this case is log 216 for line/profile P.l, to the controller 202.
  • the controller 202 can then provide the handset with a full log for the line/profile P.l, or simply the last received or last dialed telephone number, which can then be displayed to the user on the handset.
  • the handset can be given the same access to any of the other logs in a similar manner. Further, any other handset can be given the same access to any of the logs in the same manner described.
  • the controller 202 can be configured to permit unfettered access to log information of all profiles/lines only from lines/profiles that have been given administrator privileges. If the user attempts to access the call logs from another profile by using a profile without administrator privileges, an override password can be provided to permit temporary access to the call logs.
  • the controller 202 and/or the handset 101/102 can receive a selection of a telephone number from previous call. For example, after displaying the call log 216, or a portion of the call log 216, the user can select the last received/last dialed call on the line/profile P.l from the handset display 224. In turn, the handset can transmit the selection to the controller 202.
  • step 514 the controller 202 can establish call with the selected telephone number on the line/profile to which the controller 202 had switched access at step 508.
  • the controller 202 can dial the selected telephone number on the corresponding line/profile to which the handset 101/102 is logged on and connected.
  • the line/profile can be a default line/profile or can be selected by the user, as discussed above with respect to FIG. 4.
  • the method can proceed to step 513, in which the controller 202 can copy the telephone number, selected as described with respect to step 512, to a contact list associated with the profile on which the telephone handset 101/102 is logged on and connected.
  • a contact list associated with the profile on which the telephone handset 101/102 is logged on and connected.
  • the controller 202 can copy the telephone number to the contact list associated with the profile on which the telephone handset 101/102 is logged on and connected, which, in the example provided above, is profile P.2.
  • the controller 202 can store a contact list for each profile in the storage medium 212, in addition to other information about the profile.
  • steps 510-514 have been described with respect to a call transfer scenario, steps 510-514, with or without step 513, can be performed at any time by any one or more of the handsets.
  • step 510 can be performed at any time to permit the user to access the call log of a line/profile from a handset that is different from the line/profile to which the handset is logged on and connected.
  • the method 500 can optionally permit a user to employ a "transfer call” option.
  • the method can proceed to step 516, in which the handset 101 can display the "transfer call" option in response to user-selection of a telephone number in the call log 216 at step 512.
  • step 508 can be skipped.
  • the switch to a different handset/profile is not performed and the user remains on the handset 101 on line/profile P.l after completion of step 512.
  • the method can proceed to step 516 after terminating the call at step 506.
  • the user can select a menu option to transfer the call to another handset.
  • the user can prompt the display of a menu by selecting a menu-designated key from the set of keys 226. Further, the menu can display a "transfer call" option for user-selection.
  • the controller 202 and/or the handset 101 can receive the user-selected menu option to transfer the call to another line/profile.
  • the call can correspond to the telephone number selected at step 512 or to the call terminated at step 506.
  • the handset 101 can simply display the listing of other available handsets 102-103 along with a listing of lines/profiles to which each of the handsets are logged on.
  • the listing of handsets and corresponding lines/profiles can be stored at the handset 101 and updated periodically or can be received from the controller 202 each time a user selects the "transfer call" option, where the controller 202 compiles the listing of other handsets and corresponding lines/profiles from the reference table 214. Further, the user can select a corresponding handset to which the call should be transferred and a corresponding line/profile to which the selected handset is logged on.
  • the controller 202 can receive an indication of the selected handset and selected line/profile from the handset 101.
  • the method can proceed to step 514, in which the call can be established on the new line/profile selected at step 522.
  • the controller 202 can dial the telephone number of the call corresponding to the call selected in accordance with step 512 or to the call terminated at step 506.
  • the controller 202 can receive the telephone number selected in accordance with step 512 from the handset 101.
  • step 516 is performed after step 506, as indicated in FIG. 5, the handset 101 can transmit to the 3 controller 202 a predetermined code indicating that the telephone number of the last call conducted on the handset 101 should be dialed with the indication of the handset and line/profile selected by the user for the transfer.
  • the selected handset can automatically ring and, when the user turns on the selected handset, the controller 202 can dial the telephone number of the call, as stated above, to establish the call on the selected line/profile.
  • the MTA system 105 can also employ and configure the call logs to address other problems. For example, as mentioned above, in current VoIP systems, if a user answers a call that is intended for or made to a first profile with a handset that is on a second profile, the call is logged only on the call log for the second profile. Thus, the first profile has no record of a call that should be associated with its line/profile.
  • the MTA 105 can log a call both on the call log associated with the profile to which the call is made and the call log associated with the profile on which the call is answered. This aspect can permit the user of one line/profile, such as a father in a household, to see that a call to his line was answered by another line/profile. Then, the user of the line to which the call was intended or made can inquire as to what the call was about.
  • a method 600 for logging a telephone call in accordance with an exemplary embodiment is illustrated.
  • the method 600 can begin at step 602, in which the MTA 105 can receive a call on a first profile in accordance with VoIP.
  • the MTA 105 can receive the call on line/profile P.l, to which the handset 101 is logged on.
  • the MTA 105 can be configured to cause one or more of the handsets 101-103 to ring in response to receiving the call.
  • the MTA 105 can connect the call to a handset logged on to a second profile.
  • the MTA 105 can cause one or more of the handsets 101-103 to ring and a user can lift or power on a handset 102, in response to which the MTA can connect the handset 102 to the first profile.
  • the handset 102 can be logged on and connected to a profile, such as profile P. 2, that is different from the profile on which the call is received.
  • the MTA 105 can be configured to log the call on both the first and second profiles.
  • the MTA 105 can be configured to log the call in both the log 216 for the line/profile P.1 and the log 218 for the line/profile P. 2.
  • each handset can be configured to ring for incoming calls such that the handset rings only for calls received on lines associated with profiles to which the handset is logged on.
  • the MTA 105 can be configured to forward calls received on a line/profile to only those handsets to which a line/profile is logged on.
  • the handset itself can be configured to determine whether a received call is intended for a line/profile to which the handset is logged on and can be configured to cause itself to ring only for those calls received on the a line/profile to which the handset is logged on.
  • the method 700 can correspond to the first option provided above and can begin at step 702, in which the MTA 105 can receive an incoming call on a line/profile in accordance with VoIP.
  • the controller 202 can determine the handset or handsets to which the call should be forwarded.
  • the reference table 214 can indicate to which line(s)/profile(s) each handset is logged on.
  • the controller 202 can identify the line/profile on which a call is received and can use the table 214 to cross-reference the line/profile with the handsets that are logged on to the line/profile on which the call is directed.
  • the controller 202 can forward the call to only those handsets that are logged on to the profile on which the call is received.
  • the MTA 105 can restrict handsets that are not logged on to a line/profile on which a call is received from ringing when the call is received, and thereby prevent such handsets from answering the call.
  • a line can be dedicated for each handset or subscriber line interface card (SLIC).
  • the reference table 214 can be configured such that only one device entry can be made for each line/ profile.
  • the method 800 can correspond to the second option provided above and can be performed by any one or more of the handsets 101-103.
  • the method 800 can begin at step 802, in which the handset can receive an incoming call on a line/profile from the MTA 105 in accordance with VoIP. Further, the handsets can monitor the lines/profiles on which calls are received and can cause itself to ring only if it is logged on to the lines/profiles receiving the call. For example, at step 804, the handset can identify the line/profile on which call is received.
  • the controller 202 can transmit an identifier code with each call to permit the handset to determine the line/profile on which a ] 5 call is received.
  • the handset can determine whether the handset is logged on to the line/profile on which the call is received. For example, as discussed above with regard to FIG. 5, each handset can keep a listing of lines/profiles to which the handsets are logged on. Thus, here, the handset can compare the identified line/profile with the listing to determine whether the handset is logged on to the identified line/profile. If the handset is not logged on to the identified line/profile, then the method can proceed to step 802 and can repeat for another call.
  • the method can proceed to step 808, in which the handset can direct itself to ring to permit the user to answer the call. Accordingly, the handset can restrict itself from ringing when a call is received on a line/profile to which the handset is not logged on, and thereby prevent a user from answering a call using the handset. As described above, for example with respect to FIG. 3, the restriction, in either method 700 or method 800, can be overridden by providing an appropriate password. For example, the user can hear an incoming call on an authorized handset in another room and can employ the login feature to answer the call from a handset that is not logged on to the line/profile on which the call is received.
  • the ring restriction features can be configurable by line/profile.
  • the features can prevent calls from ringing on handsets in undesirable situations.
  • the features can prevent calls received on a line/profile P.4 dedicated to a fax device 104 from ringing all handsets.
  • the features can also prevent users, such as children, from answering a business line.
  • an SLIC line can be configured as a dedicated FAX line and the system can be configured such that a handset on any other SLIC or wireless handsets do not ring on incoming calls for the dedicated fax line.
  • the methods 700 and 800 can be modified.
  • the controller 202 can identify the line/profile on which a call is received and can use the table 214 to cross-reference the line/profile with the devices that are logged on to the line/profile on which the call is directed.
  • the method can proceed to step 706, in which the controller 202 can forward the call to only the other device 104.
  • the controller 202 can forward the call to one or more handsets, including those that are not logged on to the profile on which the call is received.
  • the handset can determine whether the line/profile on which the call is received is dedicated to an other device 104. For example, as discussed above, the handset can employ a listing of profiles and associated devices and can employ identifier codes transmitted from the controller 202 with the call.
  • the handset can restrict itself from ringing and the method can proceed to step 802 in which the handset can receive another call. Otherwise (i.e., the call is directed to one of the handsets), the handset can be configured to ring.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention porte sur des systèmes et des procédés d'adaptateur de terminal multimédia (MTA) conformes à la technique de voix sur protocole Internet (VoIP). Des MTA peuvent être configurés pour permettre à des combinés d'utiliser une fonction d'invite d'ouverture de session qui permet à des utilisateurs d'ouvrir une session du combiné sur de multiples profils simultanément, permettant ainsi à un utilisateur de répondre rapidement à un appel à partir d'un combiné initialement non autorisé. En outre, au moins une partie des journaux d'appel stockés au niveau du MTA pour chaque profil sont accessibles entre profils, afin de permettre au combiné de remplir diverses fonctions, telles qu'un transfert d'appel. En outre, le système peut être configuré de sorte que seul un dispositif attribué à une ligne particulière/un profil particulier puisse sonner et répondre à un appel reçu sur la ligne/le profil.
PCT/US2010/002803 2010-10-20 2010-10-20 Systèmes et procédés d'adaptateur de terminal multimédia voip WO2012054012A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2010/002803 WO2012054012A1 (fr) 2010-10-20 2010-10-20 Systèmes et procédés d'adaptateur de terminal multimédia voip

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2010/002803 WO2012054012A1 (fr) 2010-10-20 2010-10-20 Systèmes et procédés d'adaptateur de terminal multimédia voip

Publications (1)

Publication Number Publication Date
WO2012054012A1 true WO2012054012A1 (fr) 2012-04-26

Family

ID=44202184

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2010/002803 WO2012054012A1 (fr) 2010-10-20 2010-10-20 Systèmes et procédés d'adaptateur de terminal multimédia voip

Country Status (1)

Country Link
WO (1) WO2012054012A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013178150A1 (fr) * 2012-09-13 2013-12-05 中兴通讯股份有限公司 Procédé de traitement d'informations, et procédé et dispositif d'envoi d'informations de priorité

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1229708A2 (fr) * 2001-02-05 2002-08-07 Tenovis GmbH & Co. KG Méthode flexible pour l'enregistrement des utilisateurs en divers téléphones-IP dans un système de télécommunications IP
US20040054719A1 (en) * 2002-09-17 2004-03-18 Daigle Brian K. Providing uniform settings for multiple resources in a client-server environment
EP1655888A1 (fr) * 2004-11-06 2006-05-10 TECON Technologies AG Méthode et dispositif pour la identification d'un abonné et de la ligne d'abonné

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1229708A2 (fr) * 2001-02-05 2002-08-07 Tenovis GmbH & Co. KG Méthode flexible pour l'enregistrement des utilisateurs en divers téléphones-IP dans un système de télécommunications IP
US20040054719A1 (en) * 2002-09-17 2004-03-18 Daigle Brian K. Providing uniform settings for multiple resources in a client-server environment
EP1655888A1 (fr) * 2004-11-06 2006-05-10 TECON Technologies AG Méthode et dispositif pour la identification d'un abonné et de la ligne d'abonné

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013178150A1 (fr) * 2012-09-13 2013-12-05 中兴通讯股份有限公司 Procédé de traitement d'informations, et procédé et dispositif d'envoi d'informations de priorité
US9736225B2 (en) 2012-09-13 2017-08-15 Zte Corporation Information processing method, and priority information sending method and device

Similar Documents

Publication Publication Date Title
US7092386B2 (en) Network telephone system and methods therefor
US7366116B2 (en) Network telephone system and methods therefor
US8756328B2 (en) Caller-callee association of a plurality of networked devices with direct dial through thin client
US5668862A (en) Method and apparatus for providing user controlled call management services
US20130182703A1 (en) System and method for providing automatic determination of a call type in telephony services over a data network
JP2003514449A (ja) Ｐｂｘフューチャを公衆回線を介して拡張するための方法および装置
CN101409740A (zh) 一种电话来电处理方法、系统和电话终端与控制台
KR101082744B1 (ko) 일반전화와 인터넷전화 서비스를 모두 제공하는 게이트웨이장치 및 그 방법
WO2016095349A1 (fr) Procédé de réalisation de service ivr de passerelle domestique, et passerelle domestique
US20080043957A1 (en) System and method for allowing a communication device to have multiple, hierarchically prioritized numbers
US20090274141A1 (en) Ip telephone system and ip telephone method
US11363354B2 (en) Prioritized call sessions
US8014383B2 (en) Communication system
US20040196868A1 (en) Method and system for prioritizing a telephone call
CN101217648A (zh) 视频监控信息的传递方法、装置及系统
CN101335640B (zh) 一种通信终端自动获取配置的方法及设备
US8160227B1 (en) System and method for establishing roaming line numbers
WO2012054012A1 (fr) Systèmes et procédés d'adaptateur de terminal multimédia voip
US20090252158A1 (en) Application server allowing the distribution of a call intended for a terminal connected to a gateway to all terminals connected to this gateway
KR100613221B1 (ko) 메시지 통합관리 시스템, 메시지 통합관리 시스템의메시지 확인 방법 및 서비스 제공방법
EP1542442B1 (fr) Systeme de communication
US7236578B2 (en) System and method for remotely accessing caller ID information
CN215072558U (zh) 固定电话双模通信选择装置
JP2004129157A (ja) 電話装置
KR20060018155A (ko) 웹 환경을 이용한 사설교환기의 서비스 기능 관리 시스템및 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10776200

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10776200

Country of ref document: EP

Kind code of ref document: A1