US7092386B2 - Network telephone system and methods therefor - Google Patents
Network telephone system and methods therefor Download PDFInfo
- Publication number
- US7092386B2 US7092386B2 US10/644,642 US64464203A US7092386B2 US 7092386 B2 US7092386 B2 US 7092386B2 US 64464203 A US64464203 A US 64464203A US 7092386 B2 US7092386 B2 US 7092386B2
- Authority
- US
- United States
- Prior art keywords
- phone
- network
- call
- data
- command
- 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.)
- Expired - Fee Related, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5038—Address allocation for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5046—Resolving address allocation conflicts; Testing of addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5092—Address allocation by self-assignment, e.g. picking addresses at random and testing if they are already in use
-
- 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
- H04M3/42323—PBX's with CTI arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/253—Telephone sets using digital voice transmission
- H04M1/2535—Telephone sets using digital voice transmission adapted for voice communication over an Internet Protocol [IP] network
-
- 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
Definitions
- One embodiment of the present invention includes a telephony interface, a network interface and a local area network (LAN).
- the telephony interface provides connectivity between one or more netphones and an external telephone network such as a PSTN telephone system.
- the network interface provides connectivity between one or more computers and an external computer network such as the Internet.
- the local area network provides interconnectivity between the netphone(s), the computer(s), the telephony interface and the network interface.
- FIG. 22B shows a diagram illustrating a segment of the data transmission frame of FIG. 22A for a Type 1 Command in accordance with an embodiment of the present invention
- FIG. 42A shows a flow chart illustrating the process of self-configuring a network phone added to the network in accordance with an embodiment of the present invention
- FIG. 45 shows a flow chart illustrating the process of self-configuring a Trunk Line Card Device that is added to the network in accordance with an embodiment of the present invention
- FIG. 50B shows a flow chart illustrating another process of picking up a parked call in accordance with an embodiment of the present invention
- FIG. 1 shows a functional block diagram of a Telephone Device 10 for connection to a LAN (Local Area Network), in accordance with an embodiment of the present invention.
- Network connection to the Telephone Device 10 is made through 10/100/1000 Megabit/sec Ethernet cables 24 of the LAN, although other network wiring technologies, such as high speed optical cable, may also be used.
- RJ-45 type connectors are utilized to connect telephone device 10 to LAN cables 24 , but other acceptable connectors are also utilized, as is well known to those skilled in the art.
- An Ethernet controller 18 interfaces the Micro-controller & Memory Circuitry 14 to the LAN via a standard data, address, and control bus 15 .
- An example of such device is the ASIX AX88796 L Local Bus Fast Ethernet Controller (with ADSP-21065L) or the Intel LXT971A Fast Ethernet Transceiver (with PPC855T).
- FIG. 18 shows a flow chart 400 illustrating the processing steps for the voice mail function, in accordance with an embodiment of the present invention.
- the process starts at step 402 with phone 1 calling phone 2 .
- phone 1 sends a ‘Ring’ command to phone 2 .
- the phone 2 rings, in step 408 .
- the number of rings is compared with a preset value NR and, if the number of rings does not exceed the preset value, as determined in step 420 , the process continues at step 404 . If the number of rings does exceed the preset value NR, as determined in step 420 , the caller begins the voice mail function at step 422 .
- the network phone system described herein utilizes two basic data frame configurations as a basis for communication between network phone system components.
- a Type 1 (and 1 A) frame is primarily utilized for transmitting voice or character data.
- a Type 2 frame is primarily utilized for transmitting commands. The distinguishing characteristics of each of the frame configurations are programmed into the fields 620 shown in FIG. 22A .
- Paging is applied only for Speaker Phone(s). When Paging happens, every one of the Speakerphones with the same Group Paging bit turned on will be transmitted with the same Paging Command.
- FIG. 24 shows a flow chart 750 illustrating the process of configuring a Voice Mail Device added to the network, in accordance with an embodiment of the present invention.
- This process is similar to that described above for adding new phones.
- phone # 1 must be previously installed and operational.
- a Voice Mail device is placed online in the network.
- the Voice Mail Device broadcasts the ‘Device Type’ command and the ‘Phone Directory Request’ command, in step 756 and waits in steps 757 and 759 for a response.
- phone # 1 broadcasts the phone directory of numbers.
- the Voice Mail Device acknowledges receipt of the phone directory, in step 760 , and all network devices update their LUTs to include the Voice Mail Device information, in step 762 .
- phone 1 sends a ‘Call Disconnect’ message, in step 918 , to the Trunk Line Card/Digital Assistant (the outside caller), or visa-versa, if the outside caller terminated the call.
- Phone number router 4087 Phone number router self-configuration.
Abstract
One embodiment of the present invention includes a telephony interface, a network interface and a local area network (LAN). The telephony interface provides connectivity between one or more netphones and an external telephone network such as a PSTN telephone system. The network interface provides connectivity between one or more computers and an external computer network such as the Internet. The local area network provides interconnectivity between the netphone(s), the computer(s), the telephony interface and the network interface. In some embodiments, there may be two or more netphones which can communicate with each other internally via the LAN, in addition to communicating with the external telephone network. Similarly, there may be two or more computers that can also communicate with each other internally via the same LAN, in addition to the external computer network. By combining both the internal and external connectivity needs of both the netphone(s) and computer(s), the entry cost of installing both the netphone(s) and the computer(s) is dramatically lowered. In addition, once the network infrastructure has been installed, the existing netphone(s) and computer(s) can be very easily relocated within the network, and new netphone(s) and computer(s) can be added to the network with minimal changes to the network.
Description
This is a continuation-in-part application of and claims priority of U.S. patent application Ser. No. 10/242,291 filed Sep. 11, 2002, titled “Self-Configuring Network Telephone System”, which is incorporated by reference herein.
The present invention pertains to a local area network-coupled telephone system and method. More particularly, the present invention describes a self-configuring local area network phone system for use in Ethernet networks.
The use of local area networks (LAN) to support telephone systems has become increasingly popular as the speed available on the LAN have increased. It is not uncommon to find current Ethernet based networks capable of data rates from 100 Mbits/sec to 1000 Mbits/sec (1 Gbit/sec). This has made it more practical to integrate digitized voice traffic onto these networks without impacting the main data traffic also flowing on the network. In many companies and organizations, most users have computer systems connected into a LAN system. Traditionally, these users have a telephone line connected to their office as well. The costs associated with maintaining both LAN and telephone wiring systems can be reduced if either the LAN system or the telephone wiring system is eliminated. Because the networking requirements of most office computers cannot be met by traditional phone networks, this means that the telephone wiring system should be eliminated and the telephone system should operate over the LAN. Benefits of this arrangement include the use of the existing LAN wiring, easy expandability for new users, potentially increased functionality, and reduced cost.
One system in which a telephone system operates over a LAN includes a Personal Computer (PC) connected to the LAN and having an interface module for connecting to an analog telephone. A disadvantage of such a system is that the user must have a PC on and operating to use his phone. Additionally, connecting multiple phones to the LAN requires a hub device. The disadvantage of the required hub device is that a secondary wiring system connecting each analog phone to the hub must be supplied, in addition to the LAN. This reduces the cost effectiveness of LAN-based communication.
Another system that is available uses telephone units connected directly to the LAN via Ethernet connections, but requires a central controller, also connected to the LAN, to manage all call traffic. The central controller, which has an interface to the Public Switched Telephone Network (PSTN), supports only a limited number of call stations. Multiple controllers can be interconnected to increase the capacity of the system, but at increased cost.
For the smaller office, the above systems are still too complex and expensive. Many small office organizations cannot afford the dedicated Information Technology (IT) support necessary to set up and operate these systems. Even larger organizations can benefit from a system of reduced complexity that benefits from greatly reduced startup and configuration time periods. Therefore, there is a need for a LAN-based phone system that is lower in overall cost, is faster to setup and configure, and requires less IT support, than the above-described systems.
One embodiment of the present invention includes a telephony interface, a network interface and a local area network (LAN). The telephony interface provides connectivity between one or more netphones and an external telephone network such as a PSTN telephone system. The network interface provides connectivity between one or more computers and an external computer network such as the Internet. The local area network provides interconnectivity between the netphone(s), the computer(s), the telephony interface and the network interface.
In some embodiments, there may be two or more netphones which can communicate with each other internally via the LAN, in addition to communicating with the external telephone network. Similarly, there may be two or more computers that can also communicate with each other internally via the same LAN, in addition to the external computer network.
One advantage of the present invention is that by combining both the internal and external connectivity needs of both the netphone(s) and computer(s), the user does not have to install for example a DSL modem, a router, an Ethernet switch and a telephone switch, thereby dramatically lowering the entry cost of installing both the netphone(s) and the computer(s).
Another advantage is that once the network infrastructure has been installed, the existing netphone(s) and computer(s) can be very easily relocated within the network, and new netphone(s) and computer(s) can be added to the network with minimal changes to the network, if any is needed.
Note that the various features of the present invention can be practiced alone or in combination. These features of the present invention will be described in more detail below in the detailed description of the invention and in conjunction with the following figures.
These and other features, aspects and advantages of the present invention will become better understood with regard to the following description, appended claims, and accompanying drawings where:
The Micro-controller & Memory Circuitry 14 is coupled to the Display Interface Circuitry 20, Key Pad Interface circuitry 22, Telephone Circuitry 16, and USB (Universal Serial Bus) Interface Circuitry 26. Power supply and clock functions in Power Supply Module 12 are supplied to Micro-controller & Memory Circuitry 14, Telephone Circuitry 16, Ethernet Circuitry 18, Display Circuitry 20, Keyboard Circuitry 22, and USB Interface Circuitry 26 via Power Bus 13. Micro-controller & Memory Circuitry 14 includes a CPU/DSP (Central Processing Unit/Digital Signal Processor) that fetches, decodes, and executes the program that resides in its internal or external memory. An example of such a device is the Analog Devices ADSP-21065L or Motorola PPC855T CPU. Memory configurations can include (but are not limited to) flash, EPROM (electronically programmable read only memory), EEPROM (electronically erasable programmable read only memory), RAM (random access memory), DRAM (dynamic random access memory), SRAM (static random access memory), and SDRAM (synchronous DRAM ). The primary functions of the Micro-controller & Memory Circuitry 14 are to control and communicate with Telephone Circuitry 16, Ethernet Circuitry 18, Display Circuitry 20, Key Pad Interface circuitry 22, and USB Interface Circuitry 26 within telephone device 10, as well as communicate with other network devices connected to the LAN. For example, this may include decoding keypad signals from Key Pad Interface circuitry 22, receiving, decoding, and transferring voice data (via voice recognition) and tone signals to and from Telephone Circuitry 16, receiving/transmitting USB data from USB Interface Circuitry 26, displaying incoming network data and keypad inputs, displaying help menus, and other functions on Display Circuitry 20. A separate keyboard 28 may also be attached via Key Pad Interface circuitry 22.
The analog phone LAN interface device 30 also contains Hands-Free Interface circuitry 36 for connection to speaker and microphone 38 to provide hands-free operation that is absent from many analog phone sets. A numerical keypad is optional for analog phone LAN interface device 30, because most analog phone sets 34 already contain a numeric keypad.
TABLE 1 | ||||||
Numeric Key | Function Key | Variable Key | ||||
Description | Control Key | Description | Control Key | | Control Key | |
68 | Value, |
66 | Value, |
63 | Value, |
|
1 | 01 | > | 10 | A | 30 | |
2 | 02 | < | 11 | B | 31 | |
3 | 03 | help | 12 | |
32 | |
4 | 04 | clear | 13 | D | 33 | |
5 | 05 | msg ( |
14 | |
34 | |
6 | 06 | save ( |
15 | F | 35 | |
7 | 07 | send ( |
16 | |||
8 | 08 | brdcast | 17 | |||
9 | 09 | |
18 | |||
0 | 0A | xfer | 19 | |||
* | 0B | conf | 1A | |||
# | 0C | page ( |
1B | |||
spare | 00 | hdfree | 1C | |||
pkup | 1D | |||||
hold | 1E | |||||
prog ( |
| |||||
bridge | ||||||
20 | ||||||
park | 21 | |||||
To connect internally generated calls from the network phones D11–D55 to Public Switched Telephone Networks (PSTN) 208, an interfacing device called a Trunk Line Card/Digital Attendant is required. The Trunk Line Card interfaces the analog circuitry of the outside phone lines (PSTN) to the digital circuitry required by a digital attendant. In the present embodiment, both functions are included in device 204. The Digital Attendant converts the MAC (media access control) addresses used by the LAN devices (including the network phones D11–D55) to telephone numbers understandable by standard telephone systems. The Digital Attendant, together with the trunk line card, convert the digital data streams representing the audio conversation to the frequency and signal levels of the outside phone lines. Trunk Line card/Digital Attendant 204 also serves to convert outside dialed connections to the appropriate MAC address of a network phone. The Digital Attendant/Trunk Line card 204 are either packaged together (for example on the same printed circuit board) and installed in a PC, or packaged separately. If separately packaged, the digital attendant is housed in a stand alone console with various types of display indicators (LEDs, LCD displays, etc) and controls to intercept and direct calls within the LAN system.
In like manner, calls originating from a External Network 206 are interfaced through a Data Network Line Card line card/digital attendant 202 for conversion to/from MAC addresses utilized by the network phones. External Network 206 may be a wide area network (WAN) such as the Internet, a Virtual Private Network (VPN), or may be implemented by more local communication systems utilizing microwave, laser, or buried cable for building to building or intercampus connections. It may be convenient to limit LAN coverage to within a given building or structure, for example, and utilize a microwave or laser based system for building to building or structure to structure communication. For communication with locations farther apart, the use of Internet or a VPN may be suitable. In this case, the Data Network Line Card/digital attendant line card 202 and network phones are programmed to support Internet protocols. Data Network Line Card 202 and Trunk Line Card/Digital Attendant 204 may, for example, reside in a PC connected to the LAN, or may each be a separate device. The capability may additionally be built into Switch10 192 or into a separate console type device as described above.
In this embodiment, only two lines and two phone numbers are assigned by the phone company. As a result, only two open lines are available at any one time between users on phones P# 1–P# 10. Device 306 includes an extension identification utility that allows an incoming caller to pick an appropriate extension to which the call is directed. Such a utility can be completely automated, with prerecorded selections that allow the incoming caller to access directories of all internal phone extensions. Or, if preferred, trunk line card/digital attendant device 306 can be set up to provide human operator intervention to route calls.
If phone 2 is busy, as determined in step 406, the type of handset for phone is determined in step 410. If the handset is analog, as determined in step 410, a call waiting tone is generated, in step 414, for the user on phone 2. If the handset is digital, as determined in step 410, the handset is rung, in step 412. In both steps 412 and 414, the user on phone 2 is allowed to interrupt the current call and pickup the incoming call from phone 1, in step 416.
If the phone is answered, as determined in step 416, the process ends. If the phone is not answered, as determined in step 416, the user at phone 1 has decided not to interrupt his current call and the number of ring attempts is again determined in step 420. If the number of ring attempts exceeds NR, then the caller on phone 1 begins the voice mail function at step 422.
At step 422, phone 2 sends a ‘Voice Message Storage Request’ command to the voice mail device. In step 424, the voice mail device sends a ‘Call Connected Status’ message to phone 2, and phone 2 sends a ‘Call Connected Status’ message to phone 1. In step 426, the voice mail device sends voice data (“leave a message” greeting) to phone 2, and phone 2 forwards the voice data (greeting) to phone 1. In step 428, phone 1 sends voice data (the message) to phone 2, which sends it to the voice mail device. In step 430, phone 1 sends phone 2 a ‘Call Disconnect’ command, and phone 2 forwards to the voice mail device the ‘Call Disconnect’ command. In step 432, the voice mail device sends a ‘Voice Message Available’ command to phone 2, and the Voice Message Available Indicator Lamp 67 is lit thereon to so indicate. Optionally, display 62 displays a ‘1 Msg Available’ message.
In an alternative embodiment, the voice mail device sends the call connected status and voice data (greeting) directly to phone 1, in step 427 following step 422. In step 429, phone 1 sends the voice data (message) to the voice mail device and, in step 431, phone 1 sends the ‘Call Disconnect’ command to the voice mail device. In step 432, the voice mail device sends a ‘Voice Message Available’ command to phone 2, which lights the Voice Message Available Indicator Lamp 67.
Step 466 indicates the subsequent message traffic between phone # 1, and phone # 2. Phone # 1 first sends a ‘Voice Message Storage Request’ command to phone # 2. Phone # 2 then sends a ‘Voice Message Storage Request’ command to the voice mail device.
In a first alternative following step 466, the voice mail device sends a ‘Call Connected’ message to phone to phone # 1, and a voice data (the “greeting”) to phone # 1, in step 468 a.
In a second alternative following step 466, the voice mail device sends a ‘Call-connected’ message to phone # 2, which then sends a ‘Call-connected’ message to phone # 1, in step 468 b. Also, in step 468 b, the voice mail device sends a voice data (the “greeting”) directly to phone # 2, which then sends a voice data greeting to phone # 1.
At phone # 1, the user hears the “greeting” on speaker, in step 470. In step 472, the user records the voice message.
In a first alternative following step 472, phone # 1 sends the voice message recorded by the user directly to the voice mail device, in step 474 a.
In a second alternative following step 472, phone # 1 sends the voice message to phone # 2, which in turn sends the message to the voice mail device, in step 474 b. In step 476 a, phone # 1 sends a ‘Call-Disconnect’ message to the voice mail device. In step 476 b, phone # 1 sends the ‘Call Disconnect’ command to phone # 2, which then sends the ‘Call Disconnect’ command to the voice mail device.
In step 478, the display indicates the message has been sent and, in step 480, the voice mail device sends a ‘Voice Message Available’ command to phone # 2, resulting in the message indicator 67 illuminating at phone # 2.
In step 524, phone # 1 sends a ‘Data Message Storage Request’ command to phone # 2 which then sends a ‘Data Message Storage Ready’ command back to phone # 1. In step 526, phone # 1 sends the data message to phone # 2. In step 528, phone # 2 sends a ‘Data Message Storage Acknowledge’ command to phone # 1 which sends an ‘End’ command to phone # 2. In step 530, phone # 1 display indicates the message has been sent, and the message indicator 67 illuminated at phone # 2.
The start of the data frame begins with a preamble 602 of 7 bytes representing a sequence of 56 bits having alternating 1 and 0 values that are used for synchronization. They serve to give components in the network time to detect the presence of a signal, and prepare to read the signal before the frame data arrives. Following the preamble 602 is a 1-byte segment called a start frame delimiter 604, which is a sequence of 8 bits ‘10101011’ indicating the start of the frame. The start frame delimiter 604 is followed by the destination Media Access Control (MAC) address 606 and the source MAC address 608. The destination MAC address field 606 identifies the station that are to receive the frame. The source MAC address identifies the station that originates the frame. The IEEE 802.3 standard permits these address fields to be either 2-bytes or 6-bytes in length, but most current Ethernet implementations use 6-byte addresses. A destination address may specify either an “individual address” for a single station, or a “multicast address” for a group of stations. A destination address of all 1 bits refers to all stations on the LAN and is called a “broadcast address”. The type/length field 610 is used to indicate the nature of the MAC client protocol, or the length of data in the subsequent MAC client data field 612. If the value of this field 610 is less than or equal to 1500, then the type/length field 610 indicates the number of bytes in the MAC client data field 612. If the value of this field is greater than or equal to 1536, then the type/length field 610 indicates the nature of the MAC client protocol (protocol type). The MAC client data field 612 contains the data to be transferred from the source station to the destination station or stations. The maximum size of this field is 1500 bytes. If the size of this field is less than 46 bytes, the use of the subsequent “Pad” field 614 is necessary to bring the frame to size up to the minimum length. A minimum Ethernet frame size is 64 bytes counting from the destination MAC Address field 606 through the frame check sequence field 616. The frame check sequence field 616 contains a 4-byte cyclical redundancy check (CRC) value used for error checking. When a source station assembles a MAC frame, it performs a CRC calculation on all the bits in the frame from the destination MAC address 606 through the pad field 614 (that is, all the fields except the preamble 602, start frame delimiter 604 and frame check sequence 616). The source station stores the values in this field and transmits it as part of the frame. When the frame is received by the destination station, it performs an identical check. If the calculated value does not match the value in this field, the destination station assumes an error has occurred during transmission and discards the frame.
While the present invention utilizes the format and protocol for communication in Ethernet LAN systems, in accordance with prior art established by the IEEE 802.3 standards, a new coding structure is established to enable operation of the network phones on an Ethernet LAN. Compatibility with the IEEE 802.3 protocol is maintained to assure that the network phones are compatible with and do not disrupt any existing devices connected to an Ethernet LAN system, as has been previously described in FIGS. 6–11 , and FIGS. 15–17 .
The network phone system described herein utilizes two basic data frame configurations as a basis for communication between network phone system components. A Type 1 (and 1A) frame is primarily utilized for transmitting voice or character data. A Type 2 frame is primarily utilized for transmitting commands. The distinguishing characteristics of each of the frame configurations are programmed into the fields 620 shown in FIG. 22A .
Table 2 contains the format and bit code information for the command status header field 622 in a Type 1 Command data frame. The command/status header includes two bytes of information, shown in the first and second columns labeled Byte 1 and Byte 2. Byte 1 codes are given by entries in the 2nd through sixth rows. Byte 2 codes (Command/Status Codes) are shown in Table 4.
TABLE 2 | ||
|
|
Description |
xxxx:xxxx | yyyy:yyyy | Binary Bit Code, |
Command/Status | ||
xxxx:xxxx:yyyy:yyyy | ||
————:xxx— | accessory | |
————:000— | network phone | |
————:001— | USB port | |
————:010_to———:111— | reserved | |
————:———x | count bit = 0, | |
payload is ≧ 46 bytes for |
||
1 frame | ||
yyyy:yyyy | Command/Status Code. See | |
Table 4. | ||
TABLE 3 | |||
|
|||
|
Command/ | ||
Command/Status | Status | Byte Count | Description |
xxxx:xxxx | yyyy:yyyy | zzzz:zzzz | Binary Bit Code, |
Command/Status | |||
(2 bytes) | |||
xxxx:xxxx yyyy:yyyy | |||
————:xxx— | accessory | ||
————:000— | network phone | ||
————:001— | USB port | ||
————:010_to | reserved | ||
————:111— | |||
————:———x | count bit = 1, | ||
payload is < 46 bytes for | |||
Type 1A frame | |||
yyyy:yyyy | Command Code. See | ||
Table 4. | |||
zzzz:zzzz | Byte count | ||
Table 3 contains the format and bit code information for the command/status header field 622 and the Byte Count field 632 in a Type 1A Command data frame of FIG. 22C . The command/status header includes two bytes of information, shown in the first and second columns labeled Byte 1 and Byte 2. Byte 1 codes are given by entries in the 2nd through sixth rows. Byte 2 codes are shown in Table 4. This table contains an additional column labeled ‘Byte Count’, which is the information contained in field 632, a single byte of information of value 0–43 that indicates the value in fields 634. The Byte Count is required because, without it, a device would be unable to distinguish the boundary between relevant data and pad bits. The Byte Count is not required for a Type 1 frame because there is no pad required; all data in the MAC Client field is relevant.
Table 4 shows the Command/Status codes in hexadecimal format of byte 2 as shown in column 2 of Tables 2 and 3. The entries in the table follow the form code:description, where ‘code’ is the second byte of the two byte hexadecimal number entered in field 622 of previous FIGS. 22B , 22C and 22D. Further explanation of the entries follows.
TABLE 4 | ||
00: Voice Data | ||
01: Character Data (ASCII Data) | ||
02: DTMF Data | ||
03: Video Data | ||
04: Hex Data | ||
05-0F: Reserved | ||
10: Ring (Initiate Call) | ||
11: Ring Transfer | ||
12: Call Ring Back | ||
13: Ring Tone Status (normal ring) | ||
14: Ring while Busy Tone Status | ||
15: Phone Off-hook Status | ||
16: Phone Busy | ||
17: Call Connected | ||
18: Call Transfer | ||
19: Reserved | ||
1A: Call Disconnected (End Command) | ||
1B: Attention (Link) Request | ||
1C: Attention (Link) Acknowledge | ||
1D: Command End | ||
1E: Command Acknowledge | ||
1F: Reserved | ||
20: Phone Number Tryout (broadcast) | ||
21: Phone Number Broadcast | ||
22: Phone Name Broadcast | ||
23: Reserved | ||
24: Reserved | ||
25: Phone Number Already Exists | ||
26: Phone Directory Request | ||
27: Broadcast Phone Directory Request | ||
28: Phone Directory Broadcast | ||
29: Phone Directory Transmit | ||
2A: Phone Directory Received | ||
2B: Reserved | ||
2C: Reserved | ||
2D: Phone Set Inventory Request Broadcast | ||
2E: Device Tally Broadcast | ||
2F: Device Group/Type Request | ||
30: Device Group/Type Status | ||
31: Device Group/Type Configure | ||
32: Device Group/Type (Broadcast by Non Ethernet Phone) | ||
33: Reserved | ||
34: Reserved | ||
35: Data Message Storage Request | ||
36: Voice Message Storage Request | ||
37: Data Message Storage Acknowledge | ||
38: Reserved | ||
39: Retrieve Data Message | ||
3A: Retrieve Voice Message | ||
3B: Retrieve Next Data Message | ||
3C: Retrieve Next Voice Message | ||
3D: Retrieve Previous Data Message | ||
3E: Retrieve Previous Voice Message | ||
3F: Retrieve Data Message N | ||
40: Retrieve Voice Message N | ||
41: Reserved | ||
42: Reserved | ||
43: Data Message Available | ||
44: Voice Message Available | ||
45: Delete Current Data Message | ||
46: Delete Current Voice Message | ||
47: Delete All Data Messages | ||
48: Delete All Voice Messages | ||
49: Reserved | ||
4A: Reserved | ||
4B: Data Message Deleted | ||
4C: Voice Message Deleted | ||
4D: Data Mail Box Empty | ||
4E: Voice Mail Box Empty | ||
4F: Data Mail Box Full | ||
50: Voice Mail Box Full | ||
51: Data Message Ready | ||
52: Reserved | ||
53: Password Request | ||
54: Password Entry | ||
55: Password OK | ||
56: Password not OK | ||
57: Reserved | ||
58: Reserved | ||
59: Remote Call Pickup | ||
5A: Program Call Forward | ||
5B: Paging | ||
5C: Reserved | ||
5D: Reserved | ||
5E: Reserved | ||
5F: Time Transmit | ||
60: Date Transmit | ||
61: Reserved | ||
62: Call Log Request | ||
63: Call Park Retrieve | ||
64: Device Polling | ||
65: Bridge Feature Program | ||
66: Device Activity Request | ||
67: Device Activity Report | ||
68: Device Account Open | ||
69: Device Account Close | ||
6A-DF: Reserved | ||
E0: Retrieve Firmware Version | ||
E1: Retrieve Hardware Version | ||
E2: Reserved | ||
E3: Reserved | ||
E4: Firmware Version/Revision Number | ||
E5: Hardware Version/Revision Number | ||
E6: Reserved | ||
E7: Reserved | ||
E8: Reserved | ||
E9: Transmit Data Loop Back | ||
EA: Echo Data Loop Back | ||
EB: Command Error Status | ||
EC: Command Does not Exist | ||
ED: Request | ||
EE: Acknowledge | ||
EF: Reserved | ||
F0: Firmware Update Download Broadcast | ||
F1: Firmware Update Download Request | ||
F2: Firmware Update Download Transmit | ||
F3: Firmware Download Acknowledge | ||
F4: Key Map Download Request | ||
F5: Key Map Download | ||
F6-FF: Reserved | ||
For
00: Voice Data. Voice Data sent/received by Network Telephone Device. The Network Telephone Device Data Field contains Digital Audio Data (Voice).
01: Character Data. Character (ASCII) Data sent/received by Network Telephone Device. The Network Telephone Device Data Field contains ASCII Data.
02: DTMF Data. Data sent/received by Network Telephone Device. The Network Telephone Device Data Field contains DTMF Data or Key pad Data. Refer to Table 1 for DTMF and Key pad values.
03: Video Data. Data sent/received by Network Telephone Device. The Network Telephone Device Data Field contains Video Data. Used by a USB Network Telephone Video Input Device such Digital Camera or Camera Recorder.
04: Hex Data. Hex Data sent/received by Network Telephone Device. The Network Telephone Device Data Field contains Hex Data.
05–0F: Reserved.
For Type 2
10: Ring Command. Ring sent by Network Telephone Source Device. The Control Data field contains its phone number, name.
11: Ring Transfer Command. Command sent by Network Telephone Source Device to alert the calling device so it transfers its current Ring to a third party. The Control Data field contains MAC Address, Phone number, Name of the third party
12: Call Ring Back. Sent to Network Telephone Destination Phone to instruct it to call back the Network Telephone Source Device as soon as the user of the Destination Phone is off the phone (on-hook).
13: Ring Tone Status. Ring Tone Status sent back by Network Telephone Called Phone. The Control Data field contains its Phone Number, Name.
14: Ring while Busy. Ring while Busy Status sent by Network Telephone Called Phone. The Control Data field contains its Phone Number, Name.
15: Phone Off-hook. Sent by Network Telephone Called Phone that it is Off-hook. The Control Data field contains its Phone Number, Name.
16: Phone Busy. Busy Status sent by Network Telephone Called Phone. The Control Data field contains its Phone Number, Name.
17: Call Connected. The Call is Connected (goes off-hook) by the Called Device. This will signal the start of the Call Connection.
18: Call Transfer. The current Call is transferred to a third party. The Control Data field contains the MAC Address Phone Number, Name of the third party.
19: Reserved.
1A: Call Disconnected. The current Call is disconnected (goes from off-hook to on-hook).
1B: Attention Request. Request the Attention of the Called Device. Used to start a Link or Path to the Called Device.
1C: Attention Acknowledge. Inform the Caller Device that a Link or Connection has been established.
1D: Command End. Inform the Called Device that the current command is terminated.
1E: Command Acknowledge. Inform the Called Device that the current command is acknowledged.
1F: Reserved.
20: Phone Number Tryout (broadcast). Sent by the Network Telephone Source Phone to all Network Telephone Devices with its phone number in its Data Field when it is first hooked up to the LAN network. The Network Telephone Source Phone waits for some ‘time-out’ period to make sure that no same number exists in the network and sends out the broadcast message one more time to be absolutely sure that it can use the number. If there is a ‘Number Already Exists Response’ received, then it waits for the ‘Directory Transmit’ command from the same responding Network Telephone Phone.
21: Phone Number Broadcast. Sent by the Network Telephone Source Phone with its Number to the rest of other Network Telephone Devices in the network so they can store the number in their look-up tables (LUTs) for Number Dialing.
22: Phone Name Broadcast. Sent by the Network Telephone Phone so other Network Devices can update their LUTs for Name Dialing.
23: Reserved.
24: Reserved.
25: Phone Number Already Exists. Sent by Network Telephone Source Phone to indicate that its phone number matches the number of the Network Telephone Destination Phone.
26: Phone Directory Request. Sent by the Network Telephone Device or User to another Network Telephone Device so the user can update the Phone Directory of the his Device. A user who manually configures his phone with a new number uses this command to update the Phone Directory of his phone. Network Telephone Trunk Line Card/Digital Attendant or similar device can use this command to update its Phone Directory.
27: Broadcast Phone Directory Request. Sent by the Network Telephone Trunk Line Card/Digital Attendant to update its Directory or by the Network Telephone Phone when it first tries out its phone number but does not receive any Directory Transmit Command from other device. The Control Data byte determines the t or time count (each count=10 ms; 0–1=10 ms, 2=20 ms, 3=30 ms, . . . n=(30×n) ms. For 100 Mbit/s Ethernet system, the count=2 minimum. For 10 Mbits/s Ethernet system, the count=20 minimum) in milliseconds for the response time of the ‘Phone Directory Broadcast’ command. (See next command below)
28: Phone Directory Broadcast. Control Data Field should be as follows: Group/Type, MAC Address, Phone Number, Name (if any), Group/Type, MAC Address, Phone Number, Name (if any) of n devices. This Command is sent by the Network Telephone Source Device in response to a ‘Phone Directory Request Broadcast’ command (Command 27). This command should be executed only once from a single device to prevent the network from being flooded (since all Phone Directories are identical). In other words, only one device executes this command and the others do not repeat the command when they receive this command from the network. The following formula (n−1)×t applies, where: n is the order number of phone number (from lowest to highest or 1 to N where N=Number of Phone Sets); t, the time in milliseconds (example 30 milliseconds), determines which device should execute this command; and [(n−1)×t] is time out period before a device can issue this command. Device with the order phone number equal to 1 (n=1, number 1) will issue this command right away since its time-out period is 0 ms. If, for some reason, device number 1 is not present, then the device with n=2 and t=30 ms has a 30 ms time out before it can issue this command. Larger timeout times are computed for higher order numbers.
29: Phone Directory Transmit. This command is sent in response to the ‘Phone Directory Request’ command (26). Control Data Field should be as follows: Group/Type, MAC Address, Phone Number, Name (if any), Group/Type, MAC Address, Phone Number, Name (if any) of n devices.
2A: Phone Directory Received. This Status lets the other Device know that its Phone Directory has been received.
2B: Reserved.
2C: Reserved.
2D: Phone Set Inventory Request Broadcast. The Broadcast Command is to request the presence of all the Network Telephone Devices (LAN Phone Sets) in the network. This command is optional and used only to reconcile the Presence of all the Phone Devices with the LUT because some devices may be no longer in service (removed). The Control Data byte determines the t or time (t greater than 0; default minimum 30 ms) in milliseconds for the response of the Phone Directory Broadcast command. (See commands 27 & 2E below)
2E: Device Tally Broadcast. The command is in response to the Phone Set Inventory Request Broadcast above. Each Phone Set should wait for the [(n−1) * t] time out period to expire before issue this command. The formula allows each device to execute this command in an orderly manner and every one of them will have the chance to execute this command. Control Data Field should be as follows: Group/Type, MAC Address, Phone Number, Name (if any).
2F: Device Group/Type Request. Used to request the Device Group/Type of the Network Phone.
30: Device Group/Type Status. This Status is used in response to the Device Group/Type Request Command.
31: Device Group/Type Configure. Sent to Network Destination Phone to configure its Group/Type. Used by the Administrator to configure the Group/Type of the Network Destination device.
32: Device Group/Type. The Broadcast Command is for Non Network Phone Devices such as Mail Box, PSTN Line Card, or similar devices so all the Network Telephone Devices can use its MAC Address to build up their LUTs.
Following is an example of the Network Telephone Trunk Line Card broadcasting the ‘Device Type’ command in an LAN Phone System where users have to dial digit 9 (access code) first in order to get access to the outside call (Dial digit 9 then follows by the telephone number):
0132 000012 01 09
0132←- - - Device Type Command (Command Header)
000012←- - - Trunk Card (Group Type)
01←- - - 1 byte follows (Byte Count)
09←- - - Digit 9 (for Access Code to Trunk Line Card)
33: Reserved.
34: Reserved.
35: Data Message Storage Request. Request to the Network Telephone Destination Device for Data Message Storage. If the control data field is non-blank, then it is for 3rd part network phone device. The control field contains the MAC address, phone number of third party data message storage request if any.
36: Voice Message Storage Request. Request to the Network Telephone Destination Device for Voice Message Storage. If the control data field is non-blank, then it is for 3rd part network phone device. The control field contains the MAC address, phone number of third party voice message storage request, if any.
37: Data Message Storage Acknowledge. Send to the Network Telephone Destination Device for ‘Voice Message Storage’ acknowledgement.
38: Reserved
39: Retrieve Data Message. The Network Telephone Source Phone is requesting the Data Message from Network Telephone Voice Mail Device/Phone.
3A: Retrieve Voice Message. The Network Telephone Source Phone is requesting the Voice Message from Network Telephone Voice Mail Device/Phone.
3B: Retrieve Next Data Message. The Network Telephone Source Phone is requesting the next Data Message from Network Telephone Voice Mail Device/Phone.
3C: Retrieve Next Voice Message. The Network Telephone Source Phone is requesting the next Voice Message from Network Telephone Voice Mail Device/Phone.
3D: Retrieve Previous Data Message. The Network Telephone Source Phone is requesting the previous Data Message from Network Telephone Voice Mail Device/Phone.
3E: Retrieve Previous Voice Message. The Network Telephone Source Phone is requesting the previous Voice Message from Network Telephone Voice Mail Device/Phone.
3F: Retrieve Data Message N. The Network Telephone Source Phone is requesting the Data Message Number (N=1 to n) from Network Telephone Voice Mail Device/Phone.
40: Retrieve Voice Message N. The Network Telephone Source Phone is requesting the Voice Message Number (N=1 to n) from Network Telephone Voice Mail Device/Phone.
41: Reserved.
42: Reserved.
43: Data Message Available. The Network Telephone Source Device (i.e. Voice Mail) informs the Network Telephone Destination Phone that a Data Message is Available in its Mail Box.
44: Voice Message Available. The Network Telephone Source Device (i.e. Voice Mail) informs the Destination Phone that a Voice Message is Available in its Mail Box.
45: Delete Current Data Message. The Network Telephone Source Device requests to the Network Telephone Destination Device (Voice Mail/Phone) that its Current Data Message is to be deleted in its Mail Box.
46: Delete Current Voice Message. The Network Telephone Source Device requests to the Network Telephone Destination Device (Voice Mail/Phone) that its Current Voice Message is to be deleted in its Mail Box.
47: Delete All Data Messages. The Network Telephone Source Device requests to the Network Telephone Destination Device (Voice Mail/Phone) that all of its Data Messages are to be deleted in the Mail Box.
48: Delete All Voice Messages. The Network Telephone Source Device requests to the Network Telephone Destination Device (Voice Mail/Phone) that all of its Voice Messages are to be deleted in the Mail Box.
49: Reserved.
4A: Reserved.
4B: Data Message Deleted. Sent out to inform the Network Telephone Received Phone that the current Data Message is already Deleted.
4C: Voice Message Deleted. Sent out to inform the Network Telephone Received Phone that the current Voice Message is already Deleted.
4D: Data Mail Box Empty. Sent out to inform the Network Telephone Received Phone that its Data Box is Empty.
4E: Voice Mail Box Empty. Sent out to inform the Network Telephone Received Phone that its Voice Box is Empty.
4F: Data Mail Box Full. Sent out to inform the Network Telephone Received Phone that its Data Mail Box is Full.
50: Voice Mail Box Full. Sent out to inform the Network Telephone Received Phone that its Voice Mail Box is Full.
51: Data Message Ready. Informs the Network Telephone Caller Phone that it is ready to accept the Data Message.
52: Reserved.
53: Password Request. Sent to Network Telephone Destination Phone for its Password.
54: Password Entry. Send to Network Telephone Destination Phone with its Password.
55: Password OK Send to Network Telephone Destination Phone to Inform that the Password is OK
56: Password not OK. Send to Network Telephone Destination Phone to Inform that the Password is not OK
57: Reserved.
58: Reserved.
59: Remote Call Pickup. Sent by the Network Telephone Source Phone to a Ringing Network Telephone Destination Phone so the user is able to pick up the call. The Control Data field contains its phone number.
5A: Program Call Forward. Send to the Network Telephone Destination Phone so the Network Telephone Destination Phone will forward all Calls to the third party Phone. The phone number is part of the Network Phone Data Field.
5B: Paging. Send to the Network Telephone Destination Phone (without ringing it first) the Voice Data (Audio) Message.
5C: Reserved.
5D: Reserved.
5E: Reserved.
5F: Time Transmit. Send to the Network Telephone Destination Phone the Time of Day.
60: Date Transmit. Send to the Network Telephone Destination Phone the Month, Day and Year.
61: Reserved.
62: Call Log Request. Send to the Network Telephone Destination Phone for Call Log Information.
63: Call Park Retrieve. Send to the Network Telephone Destination Phone (whose call is parked) for Call Park Retrieval. Upon receiving this command, the called device will transfer the call to the Caller and goes to idle (on-hook).
64: Device Polling. Used by the Trunk Line Card/Attendant to poll each Network Phone device every few seconds so it knows if the device is still present or not and its related status. This command is optional.
65: Bridge Feature Program. Send to the Network Telephone Destination Phones for Bridge Feature Programming. The duration of the bridge feature is determined by the count in the two bytes in the Control Data field. The count decrements every minute and this feature will expire when it reaches zero. The Device programmed with this feature will allow other callers to call in for Conference Meeting, . . . Callers calling in will be asked for correct password and only then will be allowed to connect to this device. When the Bridge Feature expires, the Phone will resort back to its normal Group/Type Feature.
66: Device Activity Request. Send to the Network Telephone Destination Phone for its Activity Information. It is used for Administrating and Accounting Purposes.
67: Device Activity Report. Send to the Network Telephone Destination Device its Activity Information such as call duration, call time, destination number, . . .
68: Device Account Open. Assign the account to the Network Telephone Destination Device for Billing and Accounting purposes.
69: Device Account Close. Close the account to the Network Telephone Destination Device.
6A–DF: Reserved
E0: Retrieve Firmware Version. Retrieve from the Network Telephone Destination Device its Firmware Version Number.
E1: Retrieve Hardware Version. Retrieve from the Network Telephone Destination Device its Hardware Version Number.
E2: Reserved.
E3: Reserved.
E4: Firmware Version/Revision Number. Version/Revision Number of the Current Firmware.
E5: Hardware Version/Revision Number. Version/Revision Number of the Hardware.
E6: Reserved.
E7: Reserved.
E8: Reserved.
E9: Transmit Data Loop Back. Used to Send Loop Back Data to an Network Telephone Destination Device. The Ethernet Control Data field contains the Loop Back Data. It is used mainly for Debugging Purpose.
EA: Echo Data Loop Back. Used to Echo Loop Back Data to an Network Telephone Destination Device. The Ethernet Control Data field contains the Loop Back Data. It is used mainly for Debugging Purpose.
EB: Command Error Status. Used to inform the Network Telephone Destination Device of its Command Error Status
EC: Command Does not Exist. Used to inform the Network Telephone Destination Device that its Command does not Exist.
ED: Request. Used to Send a Request to a Network Telephone Destination Device. It is used mainly for Debugging Purpose.
EE: Acknowledge. Used to Acknowledge the Request Command. It is used mainly for Debugging Purpose.
EF: Reserved
F0: Firmware Update Download Broadcast. Broadcast to all Network Telephone Devices their Updated Firmware Program.
F1: Firmware Update Download Request. Sent to the Network Telephone Destination Device for its Updated Firmware Program.
F2: Firmware Update Download Transmit. Sent to the Network Telephone Destination Device its Updated Firmware Program.
F3: Firmware Download Acknowledge. Sent to the Network Telephone Destination Device that it has received its Firmware Program.
F4: Key Map Download Request. Sent to the Network Telephone Destination Device for its Updated Key Map.
F5: Key Map Download. Sent to the Network Telephone Destination Device its Updated Key Map.
F6–FF: Reserved
Table 5 shows the Group/Type information (field 641 of FIG. 22D ) for various embodiments of the present invention. The Group/Type information is composed of three bytes of information, 24 bits total in binary. The three bytes can be represented in binary form as eeee:dddd:cccc:bbbb:aaaa:aaaa. The code segment aaaa:aaaa represents the Type code, and is shown in the third column in Table 5. The code segment bbb represents the Priority code. The code segment cccc represents the Group code, and is shown, along with the Priority code in column 2 of Table 5. The code segment dddd represents the Paging code, and is shown in the first column of Table 5.
TABLE 5 | |||||
:Page | Group:Priority | Type | Code | Description | |
eeee:dddd | cccc:bbbb | aaaa:aaaa | |||
00000000 | BO | Inter-Building Only | |||
00000001 | LC | Local Call Allowed | |||
00000010 | DC | Long Distance Call Allowed | |||
00000011 | IC | International Call Allowed | |||
00000110 | MC | Microphone for listening only | |||
00000111 | SP | Speaker Phone for Paging only | |||
00001xxx | spare | Spare | |||
00010000 | FM | Fax Machine | |||
00010001 | VM | Voice Mail Device | |||
00010010 | TC | Trunk Line Card/Digital Attendan | |||
00010011 | VC | VPN Line Card | |||
00010100 | |||||
00010101 | USB | USB Device | |||
00010110 | USB | USB Video Input Device | |||
00010111 | USB | USB Video output Device | |||
00011000 | USB | USB Scanner Device | |||
00011001 | USB | USB Printer Device | |||
————:0000 | NP | No Priority | |||
————:0001 | | Priority | 0 Lowest | ||
————:001x | P1 | Priority 1 | |||
————:01xx | P2 | Priority 2 | |||
————: | P3 | Priority | 3 Highest | ||
0000:———— | DL | Direct Line | |||
0001:———— | | Group | 1 | ||
0010:———— | | Group | 2 | ||
0100:———— | | Group | 3 | ||
1000:———— | G4 | Group 4 | |||
————:0000 | Pg0 | Individual Paging Only | |||
————:0001 | | Group | 1 Paging | ||
————:0010 | | Group | 2 Paging | ||
————:0100 | | Group | 3 Paging | ||
————:1000 | | Group | 4 Paging | ||
0000:———— | Reserved | ||||
Explanation of the entries in of the Table 5 above follows:
Type:
BO: Network Phone Calls allowed taking place only within the Company Building, for example, phones located in Reception Lobby area.
LC: Local Call only for phones located in such area as the Lab where more than one person would be using the phones and no long distance is allowed.
DC: Long Distance Call allowed such as individual phones where the user needs to make long distance calls very often.
IC: International Calls allowed such as people in marketing department whose phones have the need for such service.
MC: Microphone Type or the Phone is for listening only. Should not be implemented for Ethic and Legal Reasons.
SP: Speakerphone is used for Paging only in areas such as Cafeteria, Lab, Warehouse,. The Caller dials its number and can start speaking as soon as it makes the connection. If there is a Paging message going on, a Busy Tone will alert the user so he/she can use it later.
FM: Standard Fax Machine.
VM: Voice Mail Device. This could be PC where Voice & Data Messages are stored and retrieved. The Retrieve & Transmit Driver is implemented by its Software Application.
TC: Trunk Line Card/Digital Attendant. The Hardware Device can reside in a PC or Stand Alone one. It allows the Network Telephone Devices to communicate to the PSTN.
VC: VPN Line Card. The Hardware Device can reside in a PC or Stand Alone one. It allows the Network Telephone Devices to communicate to the Data Network
USB: Universal Serial Interface.
Priority:
NP: No priority.
Pn: Any external incoming call will be transmitted by the Attendant (with Extension Option) to the phone with the highest Priority first. Only when it is busy then it will be routed to the next phone. P0 has the lowest priority and P3 the highest. This feature applies only when there are less phone numbers assigned by the Central Office (Phone Company) than the number of phone sets.
Group:
DL: Direct Line indicates that an incoming call will be directed to the phone with the matched number.
G1, G2, G3, G4: Group Line means an incoming call will be directed to the first available phone in the group (since they use one common telephone number). Only when all the phones in the group are used then busy will tone generated. Groups can be overlapped when more than 1 bit is set. When a phone have group overlap feature it will not be rung until one of its group of phone lines are totally busy. Phones with Group Features still can support Direct Line call. Phone with Direct Line Feature will not support Group. Examples of Group Line Phones are in Sale, Customer Support, Warehouse, . . . where only one common Phone Number (group) is needed.
Page:
Pg1, Pg2, Pg3 and Pg4: Paging is applied only for Speaker Phone(s). When Paging happens, every one of the Speakerphones with the same Group Paging bit turned on will be transmitted with the same Paging Command.
If there is a response during the timeout period, as determined in step 710, then the newly connected phone is not the only phone connected to the network. At least one other phone is connected to the network and of these, one of them is the phone that was first connected to the network. That phone, designated Phone # 1, responds to the ‘Phone Number Tryout’ command with a ‘Phone Number Already Number Exists’ message, because the number broadcast in the ‘Phone Number Tryout’ command, i.e., 2000, is the number adopted by the phone first connected to the network. Phone # 1, in step 712, next sends out a ‘Directory Transmit Command’, which includes a directory of numbers for all existing phones on the network, and the newly connected phone responds, in step 714, with the ‘Directory Received’ command. In step 716, the new phone receives the complete directory when phone # 1 sends the ‘End’ command. Otherwise, phone # 1 again sends a ‘Directory Transmit Command’, in step 712.
The newly connected phone now adopts the next available (unassigned) number in the directory, in step 718, and broadcasts a ‘Phone Number Tryout’ command again with the adopted number over the network, to determine whether there is a conflict with another phone. If there is no conflicting number, as determined in step 720, then the newly connected phone broadcasts, in step 722, a ‘Phone Number Transmit’ command that includes the adopted number, to the network. Following this, in step 726, each phone device on the network updates a look-up table (LUT) in that device with the new number. If the adopted number is a conflicting number, as determined in step 720, then there is a network error that needs to be investigated and the process terminates.
Similarly, network phone system 2820 has within it similar network phone devices such as: data network device 2822, digital attendant 2823, network phone with fax and video 2824, network phones 2825, 2829, voice mail device 2827 and trunk line card device 2828. Communication between devices within network 2820 is through LAN connection 2831, which can be wired, wireless, or a combination of both wired and wireless. The trunk line card device 2828 allows network phone devices in network 2820 to make calls to the PSTN 2844 or routes IP calls through the router/switch 2826. Router/switch 2826, which couples to LAN 2831 also routes data from PCs 2830 to the IP network 2819 and vice versa. Data network device 2822 allows network phone devices in network 2820 to make calls through VPN 2818 via router/switch 2821.
Phone line device & digital attendant 2841 provides the PSTN 2844 connection to network phones 2839 and 2840. DSL phone line device & digital attendant 2853 provides the PSTN 2844 connection to network phones 2851 and 2852. It also provides the DSL data connection to PCs 2849 and 2850.
POTS (plain old telephone system) phone 2845 is also coupled to the PSTN 2844 and hence capable of communicating with the network phone devices of Network Phone Systems 2802, 2820, 2838, and 2848.
In network telephone system 2870, the external connection to the premise is through ISDN connection 2877, and includes network phones 2872, 2873 and 2874. ISDN line device & digital attendant 2875 allows external voice communication between network phones 2872, 2873, and 2874 to the ISDN network 2878 via connection 2877, and also facilitates the data communication between PC 2871 with the ISDN network. Internal communication between various network phones and PCs are via LAN connection 2876, which can be wired, wireless, or combination of both wired and wireless.
In network telephone system 2880, the external connection to the premise is through Ethernet connection 2887, and includes network phones 2883 and 2884. Ethernet line device & digital attendant 2885 allows external voice communication between network phones 2883 and 2884 to the Ethernet network 2888 via connection 2887, and also facilitates the data communication between PCs 2881 and 2882 with the Ethernet network 2888. Internal communication between various network phones and PCs are via LAN connection 2886, which can be wired, wireless, or combination of both wired and wireless.
The exemplary network phone systems of FIGS. 28A and 28B illustrate operations in the various communication infrastructure environments (VPN, TCP/IP, PSTN, xDSL, Cable, ISDN, Ethernet line, PBX) with the appropriate interface devices 2808, 220, 2822, 2828, 2841, 2853, 2865, 2875, 2885 and 2893.
TABLE 6 | ||||||
Numeric Key | Control | Control | Variable Key | |||
Description | Key Value, | Function Key | Key Value, | Description | Control Key | |
(ref 3008) | | Description | 66 | Hex | ( |
Value, |
1 | 01 | > | 10 | A | 30 | |
2 | 02 | < | 11 | B | 31 | |
3 | 03 | help | 12 | |
32 | |
4 | 04 | clear | 13 | D | 33 | |
5 | 05 | msg ( |
14 | |
34 | |
6 | 06 | save ( |
15 | F | 35 | |
7 | 07 | send ( |
16 | |||
8 | 08 | brdcast | 17 | |||
9 | 09 | |
18 | |||
0 | 0A | xfer | 19 | |||
* | 0B | conf | 1A | |||
# | 0C | page ( |
1B | |||
spare | 00 | hdfree ( |
1C | |||
pkup ( |
1D | |||||
Hold | 1E | |||||
Prog ( |
1F | |||||
Bridge ( |
20 | |||||
Park | 21 | |||||
Schedule ( |
22 | |||||
Config ( |
23 | |||||
Directory | 24 | |||||
( |
||||||
Yellow Pages | 25 | |||||
( |
||||||
The directory key 3006 m can be used to retrieve a phone number stored locally, i.e., within the network, while the yellow-page key 3006 n can be used to retrieve a phone number from online phone directory(s) via an external Internet connection as shown in FIGS. 33–37 . Users can use keypads 3006 and 3008, or an optional attached keyboard to search by name, business type and/or location, and the resulting information viewed via display 3002. An optional larger display screen provides full page display together with arrow keys and scroll control.
When the caller dials the main number, 555-2000, the trunk line card device 220 connects the caller to the digital attendant 210 through path 3122. When the caller reaches the digital attendant 210, he/she will be asked (by an automatic attendant) to dial an extension or by a human operator for an extension to reach the right phone; i.e. phone extension “2001” for phone # 1, extension “2002” for phone # 2 and so forth, and the call is then transferred to the appropriate phone, after the digital attendant 210 receives the last digit of the extension number. Internal communication between digital attendant 210 and phones # 1 to #80 takes place via LAN connection 3124, which can be wired, wireless, or combination of both wired and wireless.
Referring to FIGS. 31A and 22A , internal communication does not require the intervention of either the trunk line card device 220, or the digital attendant 210. For internal communication, each phone device contains a lookup table (LUT) which includes phone numbers, names & MAC addresses, device type, access code, and where phone numbers of each device are translated into MAC by the source phone when its user dials the phone number (or name) of the destination phone. The translated MAC address is put into the destination MAC address field 606 along with control or voice data into packet data field 620 and the whole Ethernet packet field 600 is sent to the destination phone.
For external PSTN 2844 outgoing calls, when caller dials the access code “9” (or any access code programmed by the trunk line card device), the phone translates it into the trunk line card device 220 (see FIG. 28A ) MAC address, since all outgoing calls go through the trunk line card device. The trunk line card device 220, in turn decodes what is in the received packets into appropriate formats understood by the external telephone network (PSTN). For external PSTN incoming calls, the trunk line card device translates the phone numbers into MAC address of the correspondent phone using its LUT, converts ring voltage levels into ring command packets, audio voltage into audio data packets, and sends them to the intended destination phone.
Referring also to FIG. 28A , for external VPN 2818 outgoing calls, when caller dials a different access code, such as “8” (or any programmed access code to distinguish it from “9”), the phone translates it into the data network device 2808 MAC address since all VPN outgoing calls go through the data network device. The data network device 2808, in turn decodes what is in the received packets into appropriate formats understood by the VPN network. For external VPN incoming calls, the data network device translates the phone numbers into MAC address of the correspondent phone using its LUT, converts ring voltage levels (or ring command from ATM, TCP/IP or any interface format) into ring command packets, audio voltage (or audio data from ATM, TCP/IP, or any interface format) into audio data packets and sends them to the intended destination phone.
Table 7 presents the content of the LUT (look up table) of a network phone. When the user of phone #1 (2nd entry) dials extension “2003” to ring phone #3 (4th entry), phone # 1 uses the LUT in its memory to translate or look up extension “2003” (phone # 3's extension) into 00-0A-E6-41-C0-49 (phone # 3's MAC addresses), as shown in Table 7. It then assembles the ring command packet into data field 620 (see also FIG. 22A ), puts phone # 3's MAC addresses (00-0A-E6-41-C0-49) into the destination MAC address field 606 and the whole Ethernet packet field 600 is sent out to destination phone # 3. Table 7 also shows access codes “9” and “8” are required for internal phones to dial out to trunk line card device and data network device respectively.
Table 8 presents the content of the LUT (look up table) of a trunk line card device 220 or data network device 2808. It looks similar to the one of the network phone except one additional feature: external phone number. The external phone numbers are phone number allocated by the phone company to its customers. For instance, a ten-number allocation, starting at phone number 800-555-2000 is from 800-555-2000 to 800-555-2009. A fifty-number allocation is from 800-555-2000 to 800-555-2049. A one thousand-number is 800-555-2xxx (xxx is 000-999). Each external phone number is mapped directly to each phone, and thus routed by the trunk line card device 220 when there is an external incoming call from the outside into the network. The internal phone number (extension) is preferably the subset of the external number (the extensions match the least significant digits of the external phone numbers), so the trunk line card device does not need to keep two separate sets of number in its LUT. For instance; if the external phone number 555-1000 is assigned to a network phone system, and 100 phone numbers are allocated (555-1000 to 555-1099), then a four-digit internal phone numbers (extensions) are: “1000” to “1099”. The five-digit internal phone numbers (extensions) are: “5-1000” to “5-1099”. Another example; external phone numbers are: 555-6100 to 555-6199, then the three-digit extensions should be: 100 to 199, the four-digit extensions: “6100” to “6199” and the five-digit extensions: “5-6100” to “5-6199”.
TABLE 7 | ||
MAC Addresses | Phone Number | Type |
00-0A-E6-41-48- |
2000 | Digital Attendant |
00-0A-E6-41-C8-D1 | 2001 | Phone (Phone #1) |
00-0A-E6-41-C0-B0 | 2002 | Phone (Phone #2) |
00-0A-E6-41-C0-49 | 2003 | Phone (Phone #3) |
. | ||
. | ||
. | ||
00-0A-E6-41-C0-C0 | 2080 | Phone (Phone #80) |
00-0A-E6-54-CE- |
9 | Trunk Line Card Device |
00-0A-E6-54-CE- |
8 | Data Network Device |
TABLE 8 | ||
MAC Addresses | ||
Internal/External | Phone Number | Type |
00-0A-E6-41-48- |
2000/555-2000 | Digital Attendant |
00-0A-E6-41-C8-D1 | 2001/555-2001 | Phone (Phone #1) |
00-0A-E6-41-C0-B0 | 2002/555-2002 | Phone (Phone #2) |
00-0A-E6-41-C0-49 | 2003/555-2003 | Phone (Phone #3) |
. | ||
. | ||
. | ||
00-0A-E6-41-C0-C0 | 2080/555-2080 | Phone (Phone #80) |
00-0A-E6-54-CE- |
9 | Trunk Line Card Device |
00-0A-E6-54-CE- |
8 | Data Network Device |
In the case where eleven (555-2000 to 555-2010) numbers are allocated to system 3140, then each number can be mapped directly into each phone; number 555-2000 to phone line device & digital attendant 2841, number 555-2001 to phone # 1 3142, number 555-2002 to phone # 2 3144, number 555-2003 to phone # 3 3146, number 555-2004 to phone # 4 3148, and so forth, and finally number 555-2010 to phone # 10 3150. The external caller, then can reach phone # 1 by dialing 555-2001, phone # 2 by dialing 555-2002, phone # 3 by dialing 555-2003, phone # 4 by dialing 555-2004, and so forth and finally, phone # 10 by dialing 555-2010.
Note that depending on the user needs, the various Ethernet busses coupled to the respective Ethernet controllers and switches 3210, 3320 and 3408 of the various embodiments described above can also be point to point connections, and can either be wired or wireless.
In some embodiments of the netphone, the function blocks illustrated by FIG. 40 are implemented using firmware. However these netphone functions can also be implemented using hardware, firmware and/or software or combinations thereof. A description of function blocks of FIG. 40 follows.
Call Processing 4016 include 11 sub-functions described below.
Making call 4017: Making phone call connection
Call forward 4018: Forward current call to another number or accept call forwarded by another phone.
Redial 4019: Redial the last phone number
Call conference 4020: Connecting the current call with another phone for three ways or more conversation.
Bridge conference 4021: Dial in for bridge conference call
Call Park 4022: Park current call
Call Park Retrieve 4023: Retrieve parked call.
Paging 4024: Page another phone number
Call hold 4025: Put current call on hold
Call pick up 4026: Pick up a ring phone from another extension
Others 4027: Future functions
Call Program 4032 include 10 sub-functions described below.
Directory 4033: Phone name and number directory entry and recall.
Text messaging 4034: For example alerting caller why you are not at your phone such as “out to lunch” when caller rings your phone.
Retrieve Mail 4035: Retrieve one's voice mail
Program call forward 4036: Forward all calls to another phone.
Cancel call forward 4037: Cancel call forward
Send voice messages 4038: Allow user to send a voice mail without ringing the destination phone.
Send data messages 4039: Allow user to send a data message without ringing the destination phone.
Call bridge setup 4040: Set up call bridge conference
External control 4041: Allow external phone to have control over network phone and use it as a remote phone. (See FIG. 54 and description below).
Others 4042: Future uses
Video 4057: Video accessory function.
Audio 4058: Audio accessory function.
Fax 4059: Fax accessory function.
Modem 4060: Modem accessory function such as credit card reader function.
PC 4061: PC accessory function.
Keyboard 4062: Keyboard accessory function.
Others 4063: Other accessories
Display 4068: Phone device display
General I/O 4070: General purpose network phone I/O accessory devices
Manual 4012: Manual configuration of network phone devices
Phone 4072: Network phone configuration
Accessories 4073: Network phone accessory device configuration
Trunk line card 4074: Trunk line card configuration
Digital attendant 4075: Digital attendant configuration
Data network device 4076: Data network device configuration
Line device & digital attendant 4077: Line device & digital attendant configuration.
Phone number router 4078: Phone number router configuration.
Others 4079: Other future configurations
Self 4014: Self-configuration of network phone devices.
Phone 4082: Network phone self-configuration
Trunk line card 4083: Trunk line card self-configuration
Digital attendant 4084: Digital attendant self-configuration
Data network device 4085: Data network device self-configuration
Line device & digital attendant 4086: Line device & digital attendant self-configuration.
Phone number router 4087: Phone number router self-configuration.
System 4090: Phone device system related functions
LUT update 4091: Update LUT by the network phone device/user
Password 4092: User's password entry and verification
Firmware update 4093: Receive and program updated version of new firmware
Firmware version 4094: Firmware version number
Account open/close 4095: Create account for new user and close account of current user.
Account activities 4096: Call cost accounting activities requested by administrator
Diagnostic 4097: Firmware self-diagnostic
Others 4098: Future usage.
In the next step 4104, the phone display 3002 indicates a choice of Manual (“1” key) or Self (“2” key) Configuration. In step 4106, the user presses the “1” key for manual selection. In step 4108, the display asks if it is for the phone or accessory configuration. In step 4110, the user presses the “1” key to program the phone. In step 4112, the display asks to pick number or name choice. In step 4114, the user presses “1” the number choice. In step 4116, the display asks if the user wants to use the default number or enter brand-new number. In step 4118, the user presses the “2” key so he/she can enter new number. In step 4120, the display prompts the user to enter the numbers and press the Save key 3006 a in FIG. 30 , when completed. In step 4122, the user presses the “4, 3, 0, 5” keys followed by the Save key. In step 4124, the display instructs the user to wait while the phone checks for phone number conflicts elsewhere on the LAN.
In step 4126, the network phone sends out the ‘Phone Number Tryout’ command to all other network phone devices on the LAN and waits the password verification to take place. If there is no password verification request from an existing phone in the network, this phone is the first phone attempting to connect to the LAN and hence the extension number “4305” can be assigned to the user. If there is a password verification request and the password is not accepted by the phone making the password verification request, then the phone making the password verification request is probably connected to a neighboring LAN and this phone is the first phone attempting to connect to the LAN and extension number “4305” can be assigned to the user. Otherwise, in steps 4128 and 4130, the network phone is waiting for the response from other network phones. If no other phone responds with “Phone Number Exists” command within the timeout period, extension number “4305” is assigned to the user, in step 4132. All other devices will update their look up tables (LUTs) with the new number, such as shown in step 4222, in FIG. 42A . The number will be displayed on the user's phone, in step 4134. Finally the phone goes to idle state as indicated by step 4140. If there is any phone number conflict, then the “phone number already exists message” is shown by the display, in step 4136. The user then enters different phone numbers, in step 4138, and the process starts again, at step 4124. Eventually, a non-conflicting phone number is accepted and steps 4132 and 4134 will reflect the newly assigned and displayed phone number.
If there is a response during the timeout period after password verification, as determined in step 4208, then the newly connected phone is not the first phone attempting to connect to the network. At least one other phone is connected to the network, and of these, one of them is the phone that was first connected to the network. That phone, designated Phone #1 (or digital attendant), responds to the ‘Phone Number Tryout’ command with a ‘Phone Number Already Number Exists’ message, because the number broadcast in the ‘Phone Number Tryout’ command, i.e.,extension “2000”, is the number adopted by the phone (or digital attendant) first connected to the network. Phone #1 (or digital attendant), in step 4210, next sends out a ‘Directory Transmit Command’, which includes a directory of numbers for all existing phones on the network, and the newly connected phone responds, in step 4212, with the ‘Directory Received’ command. In step 4214, the new phone receives the complete directory when phone # 1 sends the ‘End’ command. Otherwise, phone #1 (or digital attendant) again sends a ‘Directory Transmit Command’, in step 4210.
The newly connected phone now adopts the next available (unassigned) number in the directory, in step 4216, and broadcasts a ‘Phone Number Tryout’ command again with the adopted number over the network, to determine whether there is a conflict with another phone. If there is no conflicting number, as determined in step 4218, then the newly connected phone broadcasts, in step 4220, a ‘Phone Number Transmit’ command that includes the adopted number, to the network. Following this, in step 4222, each phone device on the network updates the look-up table (LUT) in that device with the new number. If the adopted number is a conflicting number, as determined in step 4218, then there is a network error, in step 4238 (shown in display), that needs to be investigated and the process terminates.
Password verification is generally not needed in a wired Ethernet network unless the administrator is concerned about the illegal use of his/her network. In the wireless network, password verification can be important since network phone devices can be intentionally or accidentally configured into the system if network hubs/switches are within their operating vicinity. Password request is issued by phone #1 (phone or digital attendant whose phone number having the lowest value). The trunk line card device is the next device to issue the password command if there is no phone # 1 connected to the network.
The digital attendant can be assigned a separate extension manually, as shown step 4408 choice “2”, since it is also a phone with extra features; such as: monitor phone activity, enable/disable phone device, account billing and so forth. If the user picks choice “2”, in step 4408, the digital attendant phone will be configured, as shown starting in step 4116, and ending in step 4140.
If there is no response, then the process ends in step 4612, meaning there are not any other phones in the network. The network device, which fails to receive the phone directory, as shown in step 4612 will send out “Device Type Broadcast” command again as soon as a network phone is plugged in, and finishes its self-configuration on the network. The process is shown starting at step 4604.
Voice Mail/Network Storage Device can also store call history, billing statement, client phone & fax numbers, customer profile, incoming fax and outgoing fax for later retrieval or sending. One application is for customer profile and history based on his/her phone number forwarded to the agent whose PC is connected to the phone as an accessory in order to provide the highest possible service.
Table 9 and Table 10 define the upper 4 bits of byte 1 as device number as indicated by 2nd entry of column 1. Device number allows multiple network phone devices to communicate with other devices via one single RJ45 (wired or wireless) connection. Using 4 bit as the device number, up to 16 devices (15 accessory devices plus network phone) can have their connections take place concurrently via a single network phone.
TABLE 9 | ||
|
|
Description |
xxxx:xxxx | yyyy:yyyy | Binary Bit Code, Command/ |
Status | ||
xxxx:xxxx:yyyy:yyyy | ||
xxxx:———— | device number | |
————:xxx— | accessory | |
————:000— | network phone | |
————:001— | USB port | |
————:010_to———:111— | reserved | |
————:———x | count bit = 0, | |
payload is ≧ 46 bytes for |
||
1 frame | ||
yyyy:yyyy | Command/Status Code. | |
(See Tables 4 & 11) | ||
TABLE 10 | |||
|
|||
|
Command/ | Byte | |
Command/Status | Status | Count | Description |
xxxx:xxxx | yyyy:yyyy | zzzz:zzzz | Binary Bit Code, |
Command/Status | |||
(2 bytes) | |||
xxxx:xxxx | |||
yyyy:yyyy | |||
xxxx:———— | device number | ||
————:xxx— | accessory | ||
————:000— | network phone | ||
————:001— | USB port | ||
————:010_to———:111— | reserved | ||
————:———x | count bit = 1, | ||
payload is < 46 | |||
bytes for Type | |||
1A frame | |||
yyyy:yyyy | Command Code. | ||
(See Tables 4 & | |||
11) | |||
zzzz:zzzz | Byte count | ||
TABLE 11 | ||
00: Voice Data | ||
01: Character Data (ASCII Data) | ||
02: DTMF Data | ||
03: Video Data | ||
04: Hex Data | ||
05: Idle Data | ||
06-0F: Reserved | ||
10: Ring (Initiate Call) | ||
11: Ring Transfer | ||
12: Call Ring Back | ||
13: Ring Tone Status (normal ring) | ||
14: Ring while Busy Tone Status | ||
15: Phone Off-hook Status | ||
16: Phone Busy | ||
17: Call Connected | ||
18: Call Transfer | ||
19: Reserved | ||
1A: Call Disconnected (End Command) | ||
1B: Attention (Link) Request | ||
1C: Attention (Link) Acknowledge | ||
1D: Command End | ||
1E: Command Acknowledge | ||
1F: Call Forward Request | ||
20: Phone Number Tryout (broadcast) | ||
21: Phone Number Broadcast | ||
22: Phone Name Broadcast | ||
23: Phone Number Delete Broadcast | ||
24: Reserved | ||
25: Phone Number Already Exists | ||
26: Phone Directory Request | ||
27: Broadcast Phone Directory Request | ||
28: Phone Directory Broadcast | ||
29: Phone Directory Transmit | ||
2A: Phone Directory Received | ||
2B: Disable Phone Device Broadcast | ||
2C: Enable Phone Device Broadcast | ||
2D: Phone Set Inventory Request Broadcast | ||
2E: Device Tally Broadcast | ||
2F: Device Group/Type Request | ||
30: Device Group/Type Status | ||
31: Device Group/Type Configure | ||
32: Device Group/Type (Broadcast by Non Ethernet Phone) | ||
33: Reserved | ||
34: Reserved | ||
35: Data Message Storage Request | ||
36: Voice Message Storage Request | ||
37: Data Message Storage Acknowledge | ||
38: Reserved | ||
39: Retrieve Data Message | ||
3A: Retrieve Voice Message | ||
3B: Retrieve Next Data Message | ||
3C: Retrieve Next Voice Message | ||
3D: Retrieve Previous Data Message | ||
3E: Retrieve Previous Voice Message | ||
3F: Retrieve Data Message N | ||
40: Retrieve Voice Message N | ||
41: Reserved | ||
42: Reserved | ||
43: Data Message Available | ||
44: Voice Message Available | ||
45: Delete Current Data Message | ||
46: Delete Current Voice Message | ||
47: Delete All Data Messages | ||
48: Delete All Voice Messages | ||
49: Reserved | ||
4A: Reserved | ||
4B: Data Message Deleted | ||
4C: Voice Message Deleted | ||
4D: Data Mail Box Empty | ||
4E: Voice Mail Box Empty | ||
4F: Data Mail Box Full | ||
50: Voice Mail Box Full | ||
51: Data Message Ready | ||
52: Reserved | ||
53: Password Request | ||
54: Password Transmit | ||
55: Password OK | ||
56: Password not OK | ||
57: Call Park Retrieve | ||
58: Call Park Available | ||
59: Remote Call Pickup | ||
5A: Program Call Forward | ||
5B: Paging | ||
5C: Call Park Request | ||
5D: Call Park Acknowledge | ||
5E: Reserved | ||
5F: Time Transmit | ||
60: Date Transmit | ||
61: Reserved | ||
62: Call Log Request | ||
63: Reserved | ||
64: Device Polling | ||
65: Bridge Feature Program | ||
66: Device Activity Request | ||
67: Device Activity Report | ||
68: Device Account Open | ||
69: Device Account Close | ||
6A-DF: Reserved | ||
E0: Retrieve Firmware Version | ||
E1: Retrieve Hardware Version | ||
E2: Reserved | ||
E3: Reserved | ||
E4: Firmware Version/Revision Number | ||
E5: Hardware Version/Revision Number | ||
E6: Reserved | ||
E7: Reserved | ||
E8: Reserved | ||
E9: Transmit Data Loop Back | ||
EA: Echo Data Loop Back | ||
EB: Command Error Status | ||
EC: Command Does not Exist | ||
ED: Request | ||
EE: Acknowledge | ||
EF: Reserved | ||
F0: Firmware Update Download Broadcast | ||
F1: Firmware Update Download Request | ||
F2: Firmware Update Download Transmit | ||
F3: Firmware Download Acknowledge | ||
F4: Key Map Download Request | ||
F5: Key Map Download | ||
F6-FF: Reserved | ||
Table 11 above is another version of table 4 with some of new commands added in and described below (not all commands are listed):
23: Phone Number Delete Broadcast. Broadcasted to all Network Devices by the network phone to inform the destination devices that it abandons its current phone number. All the network devices remove the phone number and the MAC addresses of the network phone from their LUTs. This command is needed in the case where a self-configured phone connects successfully to the network with its default phone number. It then finds out that its number is totally out of bound with the ones in the directory. It then issues this command to abandon its just acquired number and uses the next available number from the phone directory for its new number. It then follows, as shown in FIG. 42A , all the needed steps to complete the new phone number configuration process. As mentioned previously in the description paragraph of Table 8, the internal phone (extension) numbers should be the subset of the external phone numbers. This command allows the network phone configure itself by picking the next available phone number (in the directory) within the range and thus comply with the requirement. In other words, the user should configure the first phone (phone # 1 or digital attendant) in the network manually, so its extension matches the least significant digits of the assigned phone number (by the phone company). Afterward, all other phones can self-configure and assign themselves the next available extensions, which fall within the range allocated by the phone company.
2B: Disable Phone Device. Broadcasted to all Network Devices by the trunk line card device/digital attendant or phone # 1 to all network devices that network phone device (its phone and MAC numbers in the data field) is to be removed from the phone directory (purged from LUTs). It can no longer be configured either manually or automatically into the system.
2C: Enable Phone Device. Broadcasted to all Network Devices by the trunk line card device/digital attendant or phone # 1 to all network devices that network phone device (its phone and MAC numbers in the data field) is to be enabled so it can be configured into the network later. This command is used to enable the previously disabled device.
53: Password Request. Sent by Phone # 1 or Trunk line card device (if there in no phone #1) to destination phone when the later is first plugged online. The destination phone will respond with password transmit command. See explanation below
54: Password Transmit. Send to the Network Telephone Destination Phone who requests the password. This command along with Passwork OK and Password not OK (codes 55 and 56) are part of the password verification protocol so it can prevent unwanted phone devices from configuring into the network. This can happen in the wireless LAN where hubs/switches are within working distance of the neighboring phones.
57: Call Park Retrieve. Send to the Network Telephone Destination Phone Device (where the call is parked) for Call Park Retrieval. Upon receiving this command, the called device will transfer the call to the Caller, if only one parked call is available. If multiple parked calls are available, see code 58 below.
58: Call Park (Retrieve) Available. Send to the Network Telephone Destination Phone who request the call part retrieval if more than one call is parked. The Call Part Retrieve Command is issued again with the line number so the appropriate call is forwarded.
5C: Call Park Request. Send to the network phone device (Phone or digital attendant) for Call Park for later Retrieval. The destination phone device responds with Call Park Acknowledge to Source Phone.
5D: Call Park Acknowledge. Send to the Network Telephone Destination Phone to acknowledge that the call is being parked by the source phone.
The network phone system offers the paging capability, as indicated by steps 4806 of FIG. 48 and 4922 of FIG. 49A so that no separate speaker wiring is needed in the network phone system. In the big or medium sized company, the group paging (i.e. marketing, sale, engineering so forth) feature (see Table 5 first column, Group Paging feature) allows a particular group to be paged so someone from the group can be alerted since he/she will likely be in the vicinity. Lab and cafeteria are network phones whose extensions are already programmed into the feature keys and therefore require no extension (number) dialing in order to page the lab or cafeteria. This feature also replaces paging speaker in buildings, and the intercom for a small business or at home.
Although the present invention has been described in considerable detail with reference to exemplary embodiments, modifications and variations may be made to the disclosed embodiments while remaining within the subject and spirit of the invention. Therefore, the spirit and scope of the appended claims should not be limited to the description of the preferred versions contained herein.
Claims (22)
1. In a distributed directory telephony system, a digital attendant useful in association with at least one netphone, a voicemail device and a local area network, the digital attendant comprising:
a local area network interface configured to be coupled, via the local area network, to the at least one netphone and the voicemail device;
a telephony interface for coupling the at least one netphone to an external telephone system, and wherein each of the at least one netphone includes a netphone directory configured to store and to update network addresses for the digital attendant and the voicemail device, and wherein the voicemail device includes a voicemail directory configured to store and to update network addresses for the digital attendant and the at least one netphone; and
an attendant directory configured to store and to update network addresses for the netphone and the voicemail device.
2. The digital attendant of claim 1 wherein the telephony interface is wireless.
3. The digital attendant of claim 1 wherein the telephony interface is based on a dial-up modem protocol.
4. The digital attendant of claim 1 wherein the telephony interface is based on a cable modem protocol.
5. The digital attendant of claim 1 wherein the telephony interface is based on an ISDN protocol.
6. The digital attendant of claim 1 wherein the telephony interface is based on an xDSL protocol.
7. The digital attendant of claim 1 wherein the telephony interface is based on a VPN protocol.
8. The digital attendant of claim 1 wherein the telephony interface is based on TCP/IP protocol.
9. The digital attendant of claim 1 wherein the external telephone system is a PSTN telephone system.
10. The digital attendant of claim 1 wherein the external telephone system is a PBX telephone system.
11. The digital attendant of claim 1 wherein the local area network is based on an Ethernet protocol.
12. The digital attendant of claim 1 wherein the local area network is wireless.
13. The digital attendant of claim 1 wherein the netphone is coupled to an external device.
14. The digital attendant of claim 13 wherein the external device is a USB device.
15. The digital attendant of claim 13 wherein the external device is a facsimile device.
16. The digital attendant of claim 13 wherein the external device is a video input device.
17. The digital attendant of claim 13 wherein the external device is a video output device.
18. The digital attendant of claim 1 wherein the at least one netphone is configured to schedule a reminder.
19. The digital attendant of claim 1 wherein the at least one netphone is configured to park a call.
20. The digital attendant of claim 19 wherein the at least one netphone is configured to pickup the parked call.
21. The digital attendant of claim 19 wherein the call is parked at the digital attendant.
22. The digital attendant of claim 21 wherein the at least one netphone is configured to pickup the parked call from the digital attendant.
Priority Applications (9)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/644,642 US7092386B2 (en) | 2002-09-11 | 2003-08-20 | Network telephone system and methods therefor |
EP03751992A EP1547333A4 (en) | 2002-09-11 | 2003-09-02 | Network telephone system and methods therefor |
PCT/US2003/027676 WO2004025914A2 (en) | 2002-09-11 | 2003-09-02 | Network telephone system and methods therefor |
AU2003270306A AU2003270306A1 (en) | 2002-09-11 | 2003-09-02 | Network telephone system and methods therefor |
CA002497017A CA2497017A1 (en) | 2002-09-11 | 2003-09-02 | Network telephone system and methods therefor |
JP2004536097A JP2005538646A (en) | 2002-09-11 | 2003-09-02 | Network telephone system and method |
TW092124468A TWI278201B (en) | 2002-09-11 | 2003-09-04 | Network telephone system and methods therefor |
US11/499,900 US7366116B2 (en) | 2002-09-11 | 2006-08-03 | Network telephone system and methods therefor |
US11/982,370 US20080151874A1 (en) | 2002-09-11 | 2007-10-31 | Network telephone system and methods therefor |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/242,291 US7058023B2 (en) | 2002-09-11 | 2002-09-11 | Self-configuring network telephone system and method |
US10/644,642 US7092386B2 (en) | 2002-09-11 | 2003-08-20 | Network telephone system and methods therefor |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/242,291 Continuation-In-Part US7058023B2 (en) | 2002-09-11 | 2002-09-11 | Self-configuring network telephone system and method |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/499,900 Continuation US7366116B2 (en) | 2002-09-11 | 2006-08-03 | Network telephone system and methods therefor |
Publications (2)
Publication Number | Publication Date |
---|---|
US20040091089A1 US20040091089A1 (en) | 2004-05-13 |
US7092386B2 true US7092386B2 (en) | 2006-08-15 |
Family
ID=31991379
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/242,291 Expired - Fee Related US7058023B2 (en) | 2002-09-11 | 2002-09-11 | Self-configuring network telephone system and method |
US10/644,642 Expired - Fee Related US7092386B2 (en) | 2002-09-11 | 2003-08-20 | Network telephone system and methods therefor |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/242,291 Expired - Fee Related US7058023B2 (en) | 2002-09-11 | 2002-09-11 | Self-configuring network telephone system and method |
Country Status (2)
Country | Link |
---|---|
US (2) | US7058023B2 (en) |
CN (1) | CN1306780C (en) |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050135349A1 (en) * | 2003-11-24 | 2005-06-23 | Behrouz Poustchi | Paging between network devices |
US20060007473A1 (en) * | 2004-07-07 | 2006-01-12 | Erin Zhu | Videophone having integrated facsimile machine |
US20060067327A1 (en) * | 2004-09-30 | 2006-03-30 | Behrouz Poustchi | Information distribution system, method and network devices |
US20070146804A1 (en) * | 2005-12-22 | 2007-06-28 | Mehta Pratik M | System and method for redirecting facsimiles through an information handling system network |
WO2008128313A1 (en) * | 2007-04-18 | 2008-10-30 | Bce Inc. | Methods, apparatus and computer-readable media for providing a network-based call park feature |
US20080280639A1 (en) * | 2007-05-10 | 2008-11-13 | Merav Alfia | Multiple Line Cellular Telephone With Individual Features |
US20100020710A1 (en) * | 2008-07-25 | 2010-01-28 | Qualcomm Incorporated | Cell identifier assignment and selection |
US8331358B2 (en) | 2007-07-25 | 2012-12-11 | Actiontec Electronics, Inc. | Systems and methods for connecting a packet-based call to a conventional telephone network |
US8359354B1 (en) * | 2009-03-30 | 2013-01-22 | Shoretel, Inc. | Methods for providing a status to devices in a distributed system |
US8493892B1 (en) | 2009-03-30 | 2013-07-23 | Shoretel, Inc. | Resolving conflicts in distributed systems |
US20150271335A1 (en) * | 2007-09-27 | 2015-09-24 | Cisco Technology, Inc. | Integrating Telephony And Voice Mail Routing |
US9325599B2 (en) | 2009-03-30 | 2016-04-26 | Shoretel, Inc. | Methods for providing a status to devices in a distributed system |
Families Citing this family (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7003040B2 (en) * | 2002-09-24 | 2006-02-21 | Lg Electronics Inc. | System and method for multiplexing media information over a network using reduced communications resources and prior knowledge/experience of a called or calling party |
KR100475879B1 (en) * | 2002-11-11 | 2005-03-11 | 한국전자통신연구원 | An internet phone terminal for wire and wireless communication |
US7328257B2 (en) * | 2003-06-06 | 2008-02-05 | Avaya Technology Corp. | System for automatically assigning a telephone number to an existing telephone after detecting a network connection of a portable computer |
US7260205B1 (en) * | 2003-07-21 | 2007-08-21 | Aol Llc | Call waiting using external notification and presence detection |
US20050100145A1 (en) * | 2003-10-01 | 2005-05-12 | Spencer Bradford L. | Multi-user intelligent call screening |
US7602895B2 (en) * | 2003-10-01 | 2009-10-13 | Aol Llc | Dynamic call response system |
US20050201534A1 (en) * | 2004-03-10 | 2005-09-15 | Ignatin Gary R. | Method for call screening in a voice mail system |
US7929518B2 (en) * | 2004-07-15 | 2011-04-19 | Broadcom Corporation | Method and system for a gigabit Ethernet IP telephone chip with integrated DDR interface |
US7688806B2 (en) * | 2004-07-15 | 2010-03-30 | Broadcom Corporation | Method and system for a gigabit ethernet IP telephone chip |
US7586904B2 (en) * | 2004-07-15 | 2009-09-08 | Broadcom Corp. | Method and system for a gigabit Ethernet IP telephone chip with no DSP core, which uses a RISC core with instruction extensions to support voice processing |
US20080013568A1 (en) * | 2004-11-19 | 2008-01-17 | Poetker John J | Apparatus, Method and Computer Program Product for a Network Node Engine |
US7567662B1 (en) * | 2004-12-01 | 2009-07-28 | Aol Llc | Conference calls via electronic messaging interface |
CN100442706C (en) * | 2005-04-19 | 2008-12-10 | 华为技术有限公司 | Method for making maintaining node labels to match with media visiting controlled addresses |
DE102005029058A1 (en) * | 2005-06-21 | 2006-12-28 | Hertel, Andreas, Dipl.-Ing. | Interface apparatus for data network with network interface(s) for coupling to data network and transceiving network signals according to preset protocol |
US20110306322A1 (en) * | 2005-08-18 | 2011-12-15 | Roach Jr Peter O | Methods and apparatus for providing information services during the normal alert of an outbound communication session |
US8204950B2 (en) * | 2005-09-15 | 2012-06-19 | Qwest Communications International Inc. | Webpage search |
US8170189B2 (en) * | 2005-11-02 | 2012-05-01 | Qwest Communications International Inc. | Cross-platform message notification |
US9323821B2 (en) | 2006-04-05 | 2016-04-26 | Qwest Communications International Inc. | Network repository auto sync wireless handset |
US20070239832A1 (en) * | 2006-04-05 | 2007-10-11 | Qwest Communications International Inc. | Communication presentation in a calendar perspective |
US8078476B2 (en) * | 2006-04-05 | 2011-12-13 | Qwest Communications International Inc. | Cross-platform calendar notifications |
US8320535B2 (en) * | 2006-04-06 | 2012-11-27 | Qwest Communications International Inc. | Selectable greeting messages |
US8214469B2 (en) * | 2006-04-06 | 2012-07-03 | Qwest Communications International Inc. | Multiple use of common perspectives |
US8819751B2 (en) * | 2006-05-16 | 2014-08-26 | Qwest Communications International Inc. | Socially networked television experience |
US8619136B2 (en) * | 2006-12-01 | 2013-12-31 | Centurylink Intellectual Property Llc | System and method for home monitoring using a set top box |
US8363791B2 (en) * | 2006-12-01 | 2013-01-29 | Centurylink Intellectual Property Llc | System and method for communicating medical alerts |
US8073123B2 (en) * | 2006-12-27 | 2011-12-06 | Vonage Network Llc | Method for automated management of a telecommunication service |
US8687626B2 (en) | 2008-03-07 | 2014-04-01 | CenturyLink Intellectual Property, LLC | System and method for remote home monitoring utilizing a VoIP phone |
US9479336B2 (en) * | 2009-02-23 | 2016-10-25 | Xcast Labs, Inc. | Generalized method for authenticating subscribers of a service via a graphical user interface or telephone using the same user name and password |
CN101998690A (en) * | 2009-08-31 | 2011-03-30 | 英华达股份有限公司 | Handheld electronic device and communication method thereof |
JP6490884B2 (en) | 2011-04-28 | 2019-03-27 | 株式会社リコー | Charge management system, charge management method, program, program providing system, and maintenance system |
CN102523537A (en) * | 2011-11-03 | 2012-06-27 | 广东亿迅科技有限公司 | Communication service processing method based on enterprise switchboard system and enterprise switchboard system |
US8872880B1 (en) * | 2011-12-30 | 2014-10-28 | Juniper Networks, Inc. | Video conference service with multiple service tiers |
TWI459758B (en) * | 2012-05-23 | 2014-11-01 | Pixord Corp | Vdsl network system and a vdsl repeater thereof |
FI124165B (en) | 2012-09-26 | 2014-04-15 | Kone Corp | Lift system |
CN104601739A (en) * | 2014-12-15 | 2015-05-06 | 厦门联掌网络有限公司 | Method for performing multi-IP (internet protocol) wireless data interaction between intercom system and hand-held equipment |
CN106850932B (en) * | 2017-03-27 | 2023-07-25 | 天津玺联腾科技发展有限公司 | Digital intelligent voice call system |
Citations (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4837799A (en) | 1987-10-05 | 1989-06-06 | Ambassador College | Telephone line communications control system |
US4914689A (en) * | 1987-12-22 | 1990-04-03 | Bell Mountain States Telephone & Telegraph Co. | Reverse automatic number identification system |
US5625675A (en) | 1994-07-14 | 1997-04-29 | Hitachi, Ltd. | Voice mail communication system |
US5781552A (en) * | 1994-03-16 | 1998-07-14 | Nec Corporation | Automatic address setter capable of determining a network address of a host station |
US5883944A (en) * | 1997-02-28 | 1999-03-16 | Lucent Technologies Inc. | "Plug and play" telephone system |
US5892764A (en) * | 1996-09-16 | 1999-04-06 | Sphere Communications Inc. | ATM LAN telephone system |
US5903724A (en) * | 1995-09-08 | 1999-05-11 | Hitachi, Ltd. | Method of transferring packet data in a network by transmitting divided data packets |
US5943319A (en) | 1996-04-04 | 1999-08-24 | Lucent Technologies Inc. | Packet format interface for telecommunication instruments |
US5953322A (en) * | 1997-01-31 | 1999-09-14 | Qualcomm Incorporated | Cellular internet telephone |
US5978568A (en) * | 1997-03-11 | 1999-11-02 | Sequel Technology Corporation | Method and apparatus for resolving network users to network computers |
US6069888A (en) * | 1997-02-26 | 2000-05-30 | Qualcomm Inc. | Integrated voice mail system for CDMA network |
US6118862A (en) | 1998-10-23 | 2000-09-12 | Toshiba America Information Systems, Inc. | Computer telephony system and method |
US6130893A (en) * | 1997-10-09 | 2000-10-10 | Nortel Networks Corporation | Method and apparatus for multiplexing telephone lines over a common access network |
US6144724A (en) | 1998-05-15 | 2000-11-07 | Nortel Networks Corporation | Communication interface to data networks |
US6181736B1 (en) | 1997-03-25 | 2001-01-30 | Nxi Communications, Inc. | Network communication system |
US6243379B1 (en) * | 1997-04-04 | 2001-06-05 | Ramp Networks, Inc. | Connection and packet level multiplexing between network links |
US20010023458A1 (en) * | 2000-02-24 | 2001-09-20 | Laurent Gavoille | Automatic construction of directories in network terminals |
US20020006137A1 (en) * | 2000-05-08 | 2002-01-17 | Rabenko Theodore F. | System and method for supporting multiple voice channels |
US20020039407A1 (en) * | 1997-11-03 | 2002-04-04 | O'donovan John Joseph | Message transfer system |
US6421425B1 (en) | 1998-08-17 | 2002-07-16 | At&T Corp | Automated communications assistant for the sound-impaired |
US20020103872A1 (en) * | 2001-01-30 | 2002-08-01 | Naoya Watanabe | Communication apparatus and control method of the same |
US6449269B1 (en) | 1998-12-31 | 2002-09-10 | Nortel Networks Limited | Packet voice telephony system and method |
US6456625B1 (en) | 1997-10-16 | 2002-09-24 | Fujitsu Limited | LAN telephone switching system |
US6487200B1 (en) | 1996-04-04 | 2002-11-26 | At&T Corp. | Packet telephone system |
US6498791B2 (en) | 1998-04-03 | 2002-12-24 | Vertical Networks, Inc. | Systems and methods for multiple mode voice and data communications using intelligently bridged TDM and packet buses and methods for performing telephony and data functions using the same |
US6510454B1 (en) | 1998-04-21 | 2003-01-21 | Intel Corporation | Network device monitoring with E-mail reporting |
US20030123636A1 (en) | 1999-10-22 | 2003-07-03 | Bigelow Tim A. | Method of routing telecommunications and data traffic |
US20030179743A1 (en) | 2001-12-18 | 2003-09-25 | Bosik Barry S. | Call management method responsive to network presence |
US20030194071A1 (en) | 2002-04-15 | 2003-10-16 | Artoun Ramian | Information communication apparatus and method |
US20030214930A1 (en) * | 2002-05-17 | 2003-11-20 | Fischer Matthew James | Aggregated fragment acknowledgement in local area network |
US20030227910A1 (en) * | 1994-05-12 | 2003-12-11 | Hitachi, Ltd. | Packet communication system |
US20040029568A1 (en) * | 2002-08-07 | 2004-02-12 | Deluca Peter | System and method for receiving and transferring a telephone directory from one cellular telephone to the same or another |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6330244B1 (en) * | 1996-09-05 | 2001-12-11 | Jerome Swartz | System for digital radio communication between a wireless lan and a PBX |
US20020061100A1 (en) * | 2000-08-07 | 2002-05-23 | Dicamillo Carmen A. | Virtual telephony |
US6498971B2 (en) * | 2001-03-13 | 2002-12-24 | Delphi Technologies, Inc. | Apparatus for determining steer angle of a motor vehicle |
-
2002
- 2002-09-11 US US10/242,291 patent/US7058023B2/en not_active Expired - Fee Related
-
2003
- 2003-08-20 US US10/644,642 patent/US7092386B2/en not_active Expired - Fee Related
- 2003-09-02 CN CNB038238144A patent/CN1306780C/en not_active Expired - Fee Related
Patent Citations (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4837799A (en) | 1987-10-05 | 1989-06-06 | Ambassador College | Telephone line communications control system |
US4914689A (en) * | 1987-12-22 | 1990-04-03 | Bell Mountain States Telephone & Telegraph Co. | Reverse automatic number identification system |
US5781552A (en) * | 1994-03-16 | 1998-07-14 | Nec Corporation | Automatic address setter capable of determining a network address of a host station |
US20030227910A1 (en) * | 1994-05-12 | 2003-12-11 | Hitachi, Ltd. | Packet communication system |
US5625675A (en) | 1994-07-14 | 1997-04-29 | Hitachi, Ltd. | Voice mail communication system |
US5903724A (en) * | 1995-09-08 | 1999-05-11 | Hitachi, Ltd. | Method of transferring packet data in a network by transmitting divided data packets |
US6487200B1 (en) | 1996-04-04 | 2002-11-26 | At&T Corp. | Packet telephone system |
US5943319A (en) | 1996-04-04 | 1999-08-24 | Lucent Technologies Inc. | Packet format interface for telecommunication instruments |
US5892764A (en) * | 1996-09-16 | 1999-04-06 | Sphere Communications Inc. | ATM LAN telephone system |
US5953322A (en) * | 1997-01-31 | 1999-09-14 | Qualcomm Incorporated | Cellular internet telephone |
US6069888A (en) * | 1997-02-26 | 2000-05-30 | Qualcomm Inc. | Integrated voice mail system for CDMA network |
US5883944A (en) * | 1997-02-28 | 1999-03-16 | Lucent Technologies Inc. | "Plug and play" telephone system |
US5978568A (en) * | 1997-03-11 | 1999-11-02 | Sequel Technology Corporation | Method and apparatus for resolving network users to network computers |
US6181736B1 (en) | 1997-03-25 | 2001-01-30 | Nxi Communications, Inc. | Network communication system |
US6243379B1 (en) * | 1997-04-04 | 2001-06-05 | Ramp Networks, Inc. | Connection and packet level multiplexing between network links |
US6130893A (en) * | 1997-10-09 | 2000-10-10 | Nortel Networks Corporation | Method and apparatus for multiplexing telephone lines over a common access network |
US6456625B1 (en) | 1997-10-16 | 2002-09-24 | Fujitsu Limited | LAN telephone switching system |
US20020039407A1 (en) * | 1997-11-03 | 2002-04-04 | O'donovan John Joseph | Message transfer system |
US6498791B2 (en) | 1998-04-03 | 2002-12-24 | Vertical Networks, Inc. | Systems and methods for multiple mode voice and data communications using intelligently bridged TDM and packet buses and methods for performing telephony and data functions using the same |
US6510454B1 (en) | 1998-04-21 | 2003-01-21 | Intel Corporation | Network device monitoring with E-mail reporting |
US6144724A (en) | 1998-05-15 | 2000-11-07 | Nortel Networks Corporation | Communication interface to data networks |
US6421425B1 (en) | 1998-08-17 | 2002-07-16 | At&T Corp | Automated communications assistant for the sound-impaired |
US6118862A (en) | 1998-10-23 | 2000-09-12 | Toshiba America Information Systems, Inc. | Computer telephony system and method |
US6449269B1 (en) | 1998-12-31 | 2002-09-10 | Nortel Networks Limited | Packet voice telephony system and method |
US20030123636A1 (en) | 1999-10-22 | 2003-07-03 | Bigelow Tim A. | Method of routing telecommunications and data traffic |
US20010023458A1 (en) * | 2000-02-24 | 2001-09-20 | Laurent Gavoille | Automatic construction of directories in network terminals |
US20020006137A1 (en) * | 2000-05-08 | 2002-01-17 | Rabenko Theodore F. | System and method for supporting multiple voice channels |
US20020103872A1 (en) * | 2001-01-30 | 2002-08-01 | Naoya Watanabe | Communication apparatus and control method of the same |
US20030179743A1 (en) | 2001-12-18 | 2003-09-25 | Bosik Barry S. | Call management method responsive to network presence |
US20030194071A1 (en) | 2002-04-15 | 2003-10-16 | Artoun Ramian | Information communication apparatus and method |
US20030214930A1 (en) * | 2002-05-17 | 2003-11-20 | Fischer Matthew James | Aggregated fragment acknowledgement in local area network |
US20040029568A1 (en) * | 2002-08-07 | 2004-02-12 | Deluca Peter | System and method for receiving and transferring a telephone directory from one cellular telephone to the same or another |
Non-Patent Citations (1)
Title |
---|
"PCT International Search Report", Application No. PCT/US03/27676, mailed Mar. 1, 2004. |
Cited By (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7940781B2 (en) | 2003-11-24 | 2011-05-10 | Avaya Canada Corp. | Paging between network devices |
US20050135349A1 (en) * | 2003-11-24 | 2005-06-23 | Behrouz Poustchi | Paging between network devices |
US20060007473A1 (en) * | 2004-07-07 | 2006-01-12 | Erin Zhu | Videophone having integrated facsimile machine |
US20060067327A1 (en) * | 2004-09-30 | 2006-03-30 | Behrouz Poustchi | Information distribution system, method and network devices |
US7576882B2 (en) * | 2005-12-22 | 2009-08-18 | Dell Products L.P. | System and method for redirecting facsimiles through an information handling system network |
US20070146804A1 (en) * | 2005-12-22 | 2007-06-28 | Mehta Pratik M | System and method for redirecting facsimiles through an information handling system network |
US20100183127A1 (en) * | 2007-04-18 | 2010-07-22 | Myra Uy | Methods, apparatus and computer-readable media for providing a network-based call park feature |
WO2008128313A1 (en) * | 2007-04-18 | 2008-10-30 | Bce Inc. | Methods, apparatus and computer-readable media for providing a network-based call park feature |
US8358754B2 (en) | 2007-04-18 | 2013-01-22 | Bce Inc. | Methods, apparatus and computer-readable media for providing a network-based call park feature |
US20080280639A1 (en) * | 2007-05-10 | 2008-11-13 | Merav Alfia | Multiple Line Cellular Telephone With Individual Features |
US8331358B2 (en) | 2007-07-25 | 2012-12-11 | Actiontec Electronics, Inc. | Systems and methods for connecting a packet-based call to a conventional telephone network |
US20150271335A1 (en) * | 2007-09-27 | 2015-09-24 | Cisco Technology, Inc. | Integrating Telephony And Voice Mail Routing |
US9300803B2 (en) * | 2007-09-27 | 2016-03-29 | Cisco Technology, Inc. | Integrating telephony and voice mail routing |
US20100020710A1 (en) * | 2008-07-25 | 2010-01-28 | Qualcomm Incorporated | Cell identifier assignment and selection |
US8391158B2 (en) * | 2008-07-25 | 2013-03-05 | Qualcomm Incorporated | Cell identifier assignment and selection |
US8359354B1 (en) * | 2009-03-30 | 2013-01-22 | Shoretel, Inc. | Methods for providing a status to devices in a distributed system |
US8493892B1 (en) | 2009-03-30 | 2013-07-23 | Shoretel, Inc. | Resolving conflicts in distributed systems |
US9325599B2 (en) | 2009-03-30 | 2016-04-26 | Shoretel, Inc. | Methods for providing a status to devices in a distributed system |
Also Published As
Publication number | Publication date |
---|---|
US20040091089A1 (en) | 2004-05-13 |
US7058023B2 (en) | 2006-06-06 |
CN1306780C (en) | 2007-03-21 |
CN1703888A (en) | 2005-11-30 |
US20040047297A1 (en) | 2004-03-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7092386B2 (en) | Network telephone system and methods therefor | |
US7366116B2 (en) | Network telephone system and methods therefor | |
US6118864A (en) | System and method for providing communication on a wide area network | |
US6731642B1 (en) | Internet telephony using network address translation | |
US6697357B2 (en) | Call management messaging system for integrating the internet with the public switched telephone network | |
US5764639A (en) | System and method for providing a remote user with a virtual presence to an office | |
WO1998011704A2 (en) | Dedicated system and process for distributed communication on a packet-switched network | |
US20030008682A1 (en) | Integrated device for integrating the internet with the public switched telephone network | |
US7613288B1 (en) | Method for handling incoming calls directed to a virtual communication service subscriber via a guest PBX | |
MXPA01000781A (en) | Telecommunications system, method and subscriber unit for use therein. | |
EP0875110A1 (en) | Method to provide voice call notification and control messaging over a data path | |
JPH10327250A (en) | Telecommunication system managing method | |
RU2295201C1 (en) | Method and system for routing calls in inter-network interface for transferring speech via internet protocol (voip) | |
CN1476220B (en) | Method and apparatus used for supporting centralized voice message box service in distribution type telephone network | |
EP1169830B1 (en) | Communications controller for providing multiple access using a single telephone line | |
US7729340B2 (en) | IP telephone apparatus | |
US20030059014A1 (en) | Multi-media communication management system with caller managed hold system | |
US7463621B1 (en) | Method and apparatus for network-based telephone communication without a separate call manager unit | |
WO2004049655A1 (en) | System and method for voice over ip communication | |
JP2001094686A (en) | Communication terminal communication with a plurality of communication terminals connected in parallel with same network terminator | |
CA2218231C (en) | Method to provide voice call notification and control messaging over a data path | |
WO2012054012A1 (en) | VoIP MULTIMEDIA TERMINAL ADAPTER SYSTEMS AND METHODS | |
WO2001043380A1 (en) | Psdn cordless telephone system | |
JPH11331381A (en) | Caller identification telephone system | |
AU2731799A (en) | Connection interface |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FPAY | Fee payment |
Year of fee payment: 4 |
|
REMI | Maintenance fee reminder mailed | ||
LAPS | Lapse for failure to pay maintenance fees | ||
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20140815 |