WO2022051896A1

WO2022051896A1 - Providing enhanced voice-over-internet-protocol (voip) services

Info

Publication number: WO2022051896A1
Application number: PCT/CN2020/113992
Authority: WO
Inventors: Rongbin RUAN
Original assignee: Arris Enterprises Llc
Priority date: 2020-09-08
Filing date: 2020-09-08
Publication date: 2022-03-17

Abstract

An electronic device capable of conducting voice-over-Internet-protocol (VOIP) calls in a network is provided that enhances VOIP services. The electronic device includes a network interface, a non-transitory memory having instructions stored thereon, and a hardware processor. The hardware processor is configured to execute the instructions to store a list of other electronic devices connected in the network. Moreover, the hardware processor executes the instructions to initiate a VOIP call from the electronic device using a primary session initiation protocol (SIP) server, and determine whether a failure of the primary SIP server is detected. In rcsponsc to the failure being detected, a notification regarding the detected failure is transmitted to each of the other electronic devices on the list, and a VOIP call is initiated from the electronic device using a secondary SIP server; otherwise, the VOIP call is completed from the electronic device using the primary SIP server.

Description

PROVIDING ENHANCED VOICE-OVER-INTERNET-PROTOCOL (VOIP) SERVICES

Technical Field

The subject matter of the present disclosure relates generally to providing enhanced voice over Internet Protocol (VOIP) services.

Background

With the advent of the Internet, technologies developed to enable conducting telephone calls using computers. Such technologies, known as voice over Internet Protocol (VOIP) , digitize spoken voice into voice data and transmit the digitized voice data as real-time data packets across computer networks and the Internet. Servers capable of running session initiation protocols (i.e., SIP servers) are used to enable VOIP. However, sometimes an SIP server fails.

A SIP server failure is typically detected when a VOIP call is initiated by sending an “INVITE” message to an SIP server but a reply is not received after a predetermined period of time. An “INVITE” message is a message sent to SIP servers to set-up a VOIP call. After the predetermined period of time elapses, an “INVITE” message is sent to a different SIP server to again initiate the VOIP call. However, the time wasted waiting for the predetermined period of time to elapse and initiating another VOIP call is unacceptable to and inconvenient for users. The amount of time wasted is compounded because each user needs to independently detect the SIP server failure and then initiate another VOIP call. Therefore, known techniques for conducting VOIP calls via computer networks and the Internet have drawbacks.

Thus, it would be advantageous and an improvement over the relevant technology to provide an apparatus, method, and computer-readable recording medium capable of reducing the time required to conduct a VOIP call when the primary SIP server fails.

Summary

An aspect of the present disclosure provides an electronic device capable of conducting voice-over-Internet-protocol (VOIP) calls in a network for providing enhanced VOIP services. The electronic device includes a network interface, a non-transitory memory having instructions stored thereon, and a hardware processor.

The hardware processor is configured to execute the instructions to store in the non-transitory memory a list of other electronic devices connected in the network that are capable of conducting VOIP calls. The electronic device is also capable of conducting VOIP calls. Moreover, the hardware processor is configured to execute the instructions to initiate a VOIP call from the electronic device using a primary session initiation protocol (SIP) server and determine in the electronic device whether a failure of the primary SIP server is detected.

In response to the failure being detected, a notification regarding the detected failure is transmitted via the network interface to each of the other electronic devices on the list and a VOIP call is initiated from the electronic device using a secondary SIP server. Otherwise, in response to the failure of the primary SIP server not being detected, the VOIP call is completed from the electronic device using the primary SIP server.

An aspect of the present disclosure provides a method for conducting voice-over-Internet-protocol (VOIP) calls in a network to provide enhanced VOIP services. The method includes storing a list of second electronic devices connected in the network that are capable of conducting VOIP calls in a memory of a first electronic device. The first electronic device is also capable of conducting VOIP calls. Moreover, the method includes initiating a VOIP call from the first electronic device using a primary session initiation protocol (SIP) server and determining in the first electronic device whether a failure of the primary SIP server is detected.

In response to the failure being detected, a notification regarding the failure is transmitted to each of the second electronic devices on the list via a network interface included in the first electronic device, and the VOIP call is initiated from the first electronic device using a secondary SIP server. Otherwise, in response to the failure of the primary SIP server not being detected, the VOIP call is completed from the first electronic device using the primary SIP server.

An aspect of the present disclosure provides a non-transitory computer-readable recording medium in an electronic device capable of conducting voice-over-Internet-protocol (VOIP) calls in a network for providing enhanced VOIP services. The non-transitory computer-readable recording medium stores instructions which when executed by a hardware processor performs the steps of the methods described above.

Brief Description of the Drawings

In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements.

Fig. 1 is a schematic diagram illustrating an exemplary system for providing enhanced voice-over-Internet-protocol (VOIP) services after detecting a session initiation protocol (SIP) server failure;

Fig. 2 is a more detailed schematic diagram illustrating an exemplary gateway device and an exemplary client device in the system of Fig. 1;

Figs. 3 is an exemplary multimedia transfer adapter (MTA) list table according to an embodiment of the present disclosure;

Fig. 4 is an exemplary table illustrating a status of an exemplary primary (SIP) server;

Fig. 5 is an exemplary method and algorithm for providing enhanced voice-over-Internet-protocol (VOIP) services according to an embodiment of the present disclosure; and

Fig. 6 is another exemplary method and algorithm for providing enhanced voice-over-Internet-protocol (VOIP) services according to an embodiment of the present disclosure.

Detailed Description

The following detailed description is made with reference to the accompanying drawings and is provided to assist in a comprehensive understanding of various example embodiments of the present disclosure. The following description includes various details to assist in that understanding, but these are to be regarded merely as examples and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents. The words and phrases used in the following description are merely used to enable a clear and consistent understanding of the present disclosure. In addition, descriptions of well-known structures, functions, and configurations may have been omitted for clarity and conciseness. Those of ordinary skill in the art will recognize that various changes and modifications of the examples described herein can be made without departing from the spirit and scope of the present disclosure.

Fig. 1 is a schematic diagram of an exemplary system for providing enhanced voice-over-Internet-protocol (VOIP) services after detecting the failure of an SIP server. As shown in Fig. 1, the main elements of the system include a primary session initiation protocol (SIP) server 1, a secondary SIP server 2, and an Internet Service Provider (ISP) 3 communicatively connected via the Internet 6, as well as gateway devices 4 communicatively connected to the ISP 3 and different wireless devices such as client devices 5.

The system shown in Fig. 1 includes wireless devices (e.g., client devices 5) that may be connected in one or more wireless networks (e.g., private, guest, iControl, backhaul network, or Internet of things (IoT) networks) within the system. Additionally, there could be some overlap between devices in the different networks. That is, one or more network devices could be located in more than one network.

Starting from the top of Fig. 1, the primary SIP server 1 and the secondary SIP server 2 may be any type of server or computer implemented as a network server or network computer that is capable of running session initiation protocol (SIP) software used for initiating, maintaining, modifying, and terminating real-time sessions that involve video, voice, messaging, and other communication applications and services between two or more endpoints on Internet Protocol (IP) networks. The primary SIP server 1 and the secondary SIP server 2 are also capable of running simple network management protocol (SNMP) software or other software which enables the

SIP servers

1, 2 to support the use of the same or similar protocol such as the SNMP protocol. The primary SIP server 1 and the secondary SIP server 2 may also provide various shared resources to other devices connected to the network via the Internet 6.

In Fig. 1, the ISP 3 can be, for example, a streaming video provider or any computer for connecting the gateway devices 4 to the Internet 6. The connection 7 between the Internet 6 and the ISP 3 and between the Internet 6 and the

SIP servers

1, 2, and the connection 8 between the ISP 3 and the gateway devices 4 can be implemented using a wide area network (WAN) , a virtual private network (VPN) , metropolitan area networks (MANs) , system area networks (SANs) , a DOCSIS network, a fiber optics network (e.g., FTTH (fiber to the home) or FTTX (fiber to the x) , or hybrid fiber-coaxial (HFC) ) , a digital subscriber line (DSL) , a public switched data network (PSDN) , a global Telex network, or a 2G, 3G, 4G or 5G network, for example.

The connection 8 can further include as some portion thereof a broadband mobile phone network connection, an optical network connection, or other similar connections. For example, the connection 8 can also be implemented using a fixed wireless connection that operates in accordance with, but is not limited to, 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) or 5G protocols.

Each gateway device 4 is a hardware electronic device that performs the function of a stand-alone cable modem or a combination modem and gateway device that combines the functions of a modem, access point, and/or a router for providing received content to network devices (e.g., client devices 5) in the system. It is also contemplated by the present disclosure that each gateway device 4 can include the function of, but is not limited to, an Internet Protocol/Quadrature Amplitude Modulator (IP/QAM) set-top box (STB) or smart media device (SMD) that is capable of decoding audio/video content, and playing over-the-top (OTT) or multiple system operator (MSO) provided content.

Each gateway device 4 is connected to the client devices 5 via connection 9. The connection 9 between the gateway devices 4 and the client devices 5 can be implemented using a wireless connection in accordance with any IEEE 802.11 Wi-Fi protocols, Bluetooth protocols, Bluetooth Low Energy (BLE) , or other short range protocols that operate in accordance with a wireless technology standard for exchanging data over short distances using any licensed or unlicensed band such as the citizens broadband radio service (CBRS) band, 2.4 GHz bands, 5 GHz bands, 6 GHz bands or 60 GHz bands.

Additionally, the connection 9 can be implemented using a wireless connection that operates in accordance with, but is not limited to, IEEE 802.11 protocol, RF4CE protocol, ZigBee protocol, Z-Wave protocol, or IEEE 802.15.4 protocol. It is also contemplated by the present disclosure that the connections 7 can include connections to a media over coax (MoCA) network. One or more of the connections 9 can also be a wired Ethernet connection.

Each of the client devices 5 can be, for example, a hand-held computing device, a personal computer, an electronic tablet, a smart phone, smart speakers, an IoT device, an iControl device, or other similar wireless hand-held consumer electronic device capable of executing and displaying the content received through, for example, one of the gateway devices 4. Additionally, the client devices 5 can be a TV, an IP/QAM STB or an SMD that is capable of decoding audio/video content, and playing over OTT or MSO provided content received through one of the gateway devices 4.

A detailed description of the example internal components of the gateway devices 4 shown in Fig. 1 will be provided in the discussion of Fig 2. However, in general, it is contemplated by the present disclosure that the gateway devices 4 include electronic components or electronic computing devices operable to receive, transmit, process, store, and/or manage data and information associated with the system, which encompasses any suitable processing device adapted to perform computing tasks consistent with the execution of computer-readable instructions stored in a memory or a computer-readable recording medium.

Further, any, all, or some of the computing devices in the gateway devices 4 and the client devices 5 may be adapted to execute any operating system, including Linux, UNIX, Windows, MacOS, DOS, and ChromeOS as well as virtual machines adapted to virtualize execution of a particular operating system, including customized and proprietary operating systems. The gateway devices 4 are further equipped with components to facilitate communication with other computing devices over the one or more network connections to local and wide area networks, wireless and wired networks, public and private networks, and any other communication network enabling communication in the system.

The

respective connections

7, 8 between the ISP 3 and the Internet 6 and between the ISP 3 and the gateway devices 4 shown in Fig. 1 are meant to be exemplary connections and are not meant to indicate all possible connections between the ISP 3, gateway devices 4, and the Internet 6. Additionally, the connections 9 between the gateway devices 4 and the client devices 5 shown in Fig. 1 are meant to be exemplary connections and are not meant to indicate all possible connections between the gateway devices 4 and client devices 5. Moreover, it is contemplated by the present disclosure that the number of ISPs 3, gateway devices 4, and client devices 5 is not limited to the number of ISPs 3, gateway devices 4, and client devices 5 shown in Fig. 1.

Fig. 2 illustrates a more detailed schematic diagram of an example gateway device 4 in the system for providing enhanced voice-over-Internet-protocol (VOIP) services according to an embodiment of the present disclosure. Although Fig. 2 shows one gateway device 4, the gateway device 4 in the figure is meant to be representative of the other gateway devices 4 included in the system shown in Fig. 1.

The gateway device 4 is a hardware electronic device that performs the function of a stand-alone cable modem or a combination modem and gateway device that combines the functions of a modem, access point and/or a router for providing received content to network devices (e.g., client devices 5) in the system. It is also contemplated by the present disclosure that the gateway device 4 can include the function of, but is not limited to, an IP/QAM STB or SMD that is capable of decoding audio/video content, and playing OTT or MSO provided content. As shown in Fig. 2, the gateway device 4 includes a power supply 10, user interface 11, a network interface 12, a multimedia transfer adapter (MTA) 13, a memory 15, a WAN interface 16 and a controller 17.

The power supply 10 supplies power to the internal components of the gateway device 4 through the internal bus 14. The power supply 10 can be a self-contained power source such as a battery pack with an interface to be powered through an electrical charger connected to an outlet (e.g., either directly or by way of another device) .

The user interface 1 l includes, but is not limited to, push buttons, a keyboard, a keypad, a liquid crystal display (LCD) , a thin film transistor (TFT) , a light-emitting diode (LED) , a high definition (HD) or other similar display device including a display device having touch screen capabilities so as to allow interaction between a user and the gateway device 4.

The network interface 12 includes various network cards, and circuitry implemented in software and/or hardware to enable communications using the communication protocols of connections 8 and 9 (e.g., as previously described with reference to Fig. 1) .

The multimedia transfer adapter (MTA) 13 includes circuitry implemented in software and/or hardware to enable converting an analog telephone signal to a digital signal to enable providing VOIP services. The MTA 13 implements media manipulation (e.g. sampling, encoding/decoding) , encapsulation (e.g. encryption, framing) , and call signaling protocols. Although the MTA 13 is in the gateway device 4 as described herein, it is contemplated by the present disclosure that the MTA 13 may alternatively be provided as a separate stand-alone device, or may be in other devices including, but not limited to, access points and wireless extenders (not shown) .

The memory 15 includes a single memory or one or more memories or memory locations that include, but arc not limited to, a random access memory (RAM) , a dynamic random access memory (DRAM) a memory buffer, a hard drive, a database, an erasable programmable read only memory (EPROM) , an electrically erasable programmable read only memory (EEPROM) , a read only memory (ROM) , a flash memory, logic blocks of a field programmable gate array (FPGA) , a hard disk or any other various layers of memory hierarchy.

The memory 15 can be used to store any type of data, including, but not limited to, the status of the primary SIP server 1, and data regarding MTAs 13 in other gateway devices 4 included in the system. Such data includes, but is not limited to, a name of the MTA 13 and an Internet Protocol (IP) address for each MTA 13. For MTAs in a gateway device 4, the IP address of the MTA is the same as the gateway device 4. However, when the MTA 13 is provided as a separate stand-alone device, the IP address is of the MTA 13 itself. The MTA data may be assembled into a list and stored in any manner, for example, as a table. The list may be created by any person, for example, a system administrator or any user operating the gateway device 4, and entered into the memory 15 in any manner.

The MTA list may be stored in the memory 15 during MTA provisioning. Alternatively, the system administrator or any user operating the gateway device 4 may obtain the MTA list from a configuration file or via Dynamic Host Configuration Protocol (DHCP) . DHCP is a network management protocol used on Internet Protocol (IP) networks in which a DHCP server dynamically assigns an IP address and other network configuration parameters to each device on the network so the devices can communicate with other networks.

Additionally, the memory 15 can be used to store any type of instructions and/or software, for example, simple network management protocol (SNMP) software or other software which enables the gateway device 4 to support the use of the same or similar protocol such as the SNMP protocol. Additionally, the memory 15 can be used to store any type of instructions and/or software associated with algorithms, processes, or operations for controlling the general functions and operations of the gateway device 4.

The WAN interface 16 may include various network cards and circuitry implemented in software and/or hardware to enable communications between the gateway device 4 and the Internet 6 via the ISP 3 using communications protocols in accordance with connections 7 and 8 (e.g., as previously described with reference to Fig. 1) .

The controller 17 controls the general operations of the gateway device 4 and includes, but is not limited to, a central processing unit (CPU) , a hardware microprocessor, a hardware processor, a multi-core processor, a single core processor, a field programmable gate array (FPGA) , a microcontroller, an application specific integrated circuit (ASIC) , a digital signal processor (DSP) , or other similar processing device capable of executing any type of instructions, algorithms, or software for controlling the operation and functions of the gateway device 4. Communication between the components (e.g., 10-13 and 15-17) of the gateway device 4 is established using the internal bus 14.

The client devices 5 can be, for example, a hand-held computing device, a personal computer, an electronic tablet, a smart phone, smart speakers, an IoT device, an iControl device, or other similar wireless hand-held consumer electronic device capable of executing and displaying the content received through, for example, a gateway device 4. Additionally, the client devices 5 can be a TV, an IP/QAM STB or an SMD that is capable of decoding audio/video content, and playing over OTT or MSO provided content received through a gateway device 4.

Sometimes SIP servers fail and cannot enable VOIP calls. An SIP server failure is typically detected when a VOIP call is initiated by sending an “INVITE” message to an SIP server but a reply is not received after a predetermined period of time. An “INVITE” message is a message sent to SIP servers to set-up a VOIP call. After the predetermined period of time expires, an “INVITE” message is sent to a different SIP server to again initiate the VOIP call. However, the time wasted waiting for the predetermined period of time to expire and initiating another VOIP call is unacceptable and inconvenient for users. The amount of time wasted is compounded because each user needs to independently detect the SIP server failure and then initiate another VOIP call.

To address this problem, a list of MTAs is created that includes the name of each MTA in the system and an Internet Protocol (IP) address for each MTA. After one of the gateway devices 4 in the system first detects failure of the primary SIP server 1, the gateway device 4 transmits a message about the failure to each of the MTAs included in the list. For VOIP calls conducted after receiving the message, each listed MTA initiates the VOIP call with the secondary SIP server 2. As a result, each user is not required to waste time detecting the failure of the primary SIP server 1 and initiating another VOIP which enhances VOIP service.

Fig. 3 is an exemplary multimedia transfer adapter (MTA) table 18 according to an embodiment of the present disclosure. The MTA table 18 may be stored in the memory 15 of each gateway device 4 included in the system (e.g., as previously described herein with reference to Fig. 1) . The MTA table 18 includes a list of multimedia transfer adapters (MTAs) 19. The MTA list may be stored in the memory 15 of each gateway device 4 during MTA provisioning. Alternatively, a system administrator or any user operating a respective gateway device 4 may obtain the MTA list in a configuration file or via Dynamic Host Configuration Protocol (DHCP) and may store the list in the memory 15 at any time other than during provisioning. DHCP is a network management protocol used on Internet Protocol (IP) networks in which a DHCP server dynamically assigns an IP address and other network configuration parameters to each device on the network so the devices can communicate with other networks.

More specifically, the MTAs 19 include, but are not limited to, MTA1, MTA2, MTA3 and MTA4. Although four MTAs are included in the table 18, it is contemplated by the present disclosure that any number of MTAs may be included in the table 18. However, the number of MTAs in the table 18 should match the number of MTAs in the system (e.g., as previously described herein with reference to Fig. 1) . Each MTA in the system should be included in the list.

Each MTA 19 is associated with a corresponding Internet Protocol (IP) address 20. For example, MTA1 is associated with IP address 10.16.08.15, MTA2 is associated with IP address 15.20.12.30, MTA3 is associated with IP address 110.16.181.19, and MTA4 is associated with IP address 12.160.18.55. An IP address is a numerical label assigned to each device connected to a computer network that uses the Internet Protocol for communication. An IP address serves two main functions: host or network interface identification and location addressing.

As described herein, each MTA 19 is in a different one of the gateway devices 4 included in the system. Thus, the IP address 20 associated with each MTA corresponds to the gateway device 4 in which the respective MTA is included. For example, the IP address 20 for MTA1 is the IP address of the gateway device 4 which includes MTA1, the IP address 20 for MTA2 is the IP address of the gateway device 4 which includes MTA2, the IP address 20 for MTA3 is the IP address of the gateway device 4 which includes MTA3, and the IP address 20 for MTA4 is the IP address of the gateway device 4 which includes MTA4.

It is contemplated by the present disclosure that at least one of the MTAs 19 may not be in a gateway device 4 and instead may be a stand-alone MTA device. When an MTA is a stand-alone device, the IP address 20 is the IP address of the MTA itself, not the IP address ora gateway device 4.

It is contemplated by the present disclosure that any one of the gateway devices 4 included in the system (e.g., as previously described herein with reference to Fig. 1) may initiate a VOIP call by sending an “INVITE” message to the primary SIP server 1. It is equally likely that any one of the gateway devices 4 in the system may initiate the VOIP call. When a reply is not received after a predetermined period of time, failure of the primary SIP server 1 is detected and the gateway device 4 initiates another VOIP call by sending an “INVITE” message to the secondary SIP server 2. An “INVITE” message is a message sent to SIP servers to set-up a VOIP call. Additionally, the gateway device 4 sends a notification message to each of the IP addresses 20 indicating that the primary SIP server 1 failed. For VOIP calls conducted after receiving the message, each MTA 19 initiates the VOIP call by sending an “INVITE” message to the secondary SIP server 2 instead of the primary SIP server 1. As a result, VOIP service is enhanced to be faster and thus more convenient for users.

Fig. 4 is an exemplary table 21 according to an embodiment of the present disclosure. The table 21 may be stored in the memory 15 of each gateway device 4 included in the system (e.g., as previously described herein with reference to Fig. 1) and indicates a status of the primary SIP server 1. The status may be failed or not failed. When indicated as true the primary SIP server 1 has failed. When indicated as false the primary SIP server 1 has not failed and is functioning properly.

As shown in the table 21, the failed status is false 23 so a notification message is not sent and the MTAs 19 listed in table 18 initiate VOIP calls with the primary SIP server 1. However, when the failed status is indicated as true the primary SIP server 1 failed and a notification message is sent to the MTAs 19 listed in the table 18. However, an MTA 19 included in the table 18 does not send a notification message to itself.

Fig. 5 is an exemplary method and algorithm for conducting voice-over-Internet-protocol (VOIP) calls in a network for providing enhanced VOIP services in accordance with an embodiment of the present disclosure. As shown in Fig. 5, the gateway devices 4, the primary SIP server 1, and the secondary SIP server 2 are included in the system (e.g., as previously described with reference to Fig. 1) . Each gateway device 4 includes a MTA. In the description of Fig. 5, the exemplary operations may be performed by any one of the gateway devices 4 in the system that attempts to conduct a VOIP call using the primary SIP server 1. Each gateway device 4 is equally likely to conduct the VOIP call using the primary SIP server 1.

Fig. 5 illustrates exemplary operations performed when any one of the gateway devices 4 attempts to conduct a VOIP call using the primary SIP server 1 and detects a failure of the SIP server 1. Additionally, the exemplary method and algorithm of Fig. 5 includes operations that are performed by the software executed by the controller 17 of each gateway device 4 in the system.

In steps S1, S2 and S3 the software executed by the controller 17 of each gateway device 4 causes the respective gateway device 4 to store a list of multimedia transfer adapters (MTAs) that are each capable of conducting VOIP calls. The MTAs on the list include, but are not limited to, MTA1, MTA2, MTA3 and MTA4. Storing the list of MTAs can be initiated by, for example, a system administrator or any user operating any of the gateway devices 4. The MTA list may be stored in the memory 15 of each gateway device 4 during MTA provisioning. Alternatively, the system administrator or user operating a respective gateway device 4 may obtain the MTA list from a configuration file or via Dynamic Host Configuration Protocol (DHCP) and may store the list in the memory 15 at any time other than during provisioning. DHCP is a network management protocol used on Internet Protocol (IP) networks in which a DHCP server dynamically assigns an IP address and other network configuration parameters to each device on the network so the devices can communicate with other networks.

Although four MTAs are included on the list, it is contemplated by the present disclosure that any number of MTAs may be on the list. It should be understood that the MTA in each of the gateway devices 4 is on the list. Each MTA on the list is associated with a corresponding Internet Protocol (IP) address 20. For example, as shown in Fig. 3, MTA1 is associated with IP address 10.16.08.15, MTA2 is associated with IP address 15.20.12.30, MTA3 is associated with IP address 110.16.181.19, and MTA4 is associated with IP address 12.160.18.55. An IP address is a numerical label assigned to each device connected to a computer network that uses the Internet Protocol for communication.

As described herein, each MTA on the list is in a different one of the gateway devices 4 in the system. Thus, the IP address 20 associated with each MTA corresponds to the gateway device 4 which includes the respective MTA. For example, the IP address 20 for MTA1 is the IP address for the gateway device 4 which includes MTA1, the IP address 20 for MTA2 is the IP address for the gateway device 4 which includes MTA2, the IP address 20 for MTA3 is the IP address for the gateway device 4 which includes MTA3, and the IP address 20 for MTA4 is the IP address for the gateway device 4 which includes MTA4.

It is contemplated by the present disclosure that at least one of the MTAs on the list may not be in a gateway device 4 and is instead a stand-alone MTA. When an MTA on the list is a stand-alone device the IP address 20 is the IP address of the MTA itself, not the IP address of a gateway device 4.

In step S4, the software executed by the controller 17 of the gateway device 4 including MTA1 initiates a VOIP call using the network interface 12 and the

connections

7, 8. It is equally likely that the VOIP call can alternatively be initiated by any other MTA on the list. For example, the gateway device 4 including MTA2 or MTA3 may initiate the VOIP call.

The gateway device 4 including MTA1 initiates a VOIP call by transmitting an “INVITE” message to the primary SIP server 1 using the network interface 12 and the

connections

7, 8. An “INVITE” message is a message sent to SIP servers to set-up a VOIP call. Ifa reply is not received after a predetermined period of time, in step S5, the gateway device 4 determines that a failure of the primary SIP server 1 has been detected. The predetermined period of time may be any time, for example, thirty (30) seconds that enables detecting failure of the primary SIP server 1.

Next, in steps S6 and S7, the gateway device 4 transmits a notification message regarding the failure to each MTA on the list using the network interface 12 and connection 8. Because each MTA on the list is in a different gateway device 4, a notification message is transmitted to each different gateway device 4.

In step S8, the software executed by the controller 17 causes the gateway device 4 to initiate a VOIP call by transmitting an “INVITE” message to the secondary SIP server 2 using the network interface 12 and the

connections

7, 8. Because the secondary SIP server 2 is functioning properly, in step S9, the secondary SIP server 2 transmits a reply to the “INVITE” message and in step S10, the VOIP call is conducted by the gateway device 4 including MTA1.

For VOIP calls conducted after receiving the notification message, in steps S11 and S14, the gateway devices 4 including MTA2 and MTA3 may initiate VOIP calls by transmitting an “INVITE” message to the secondary SIP server 2 using their respective network interfaces 12 and the

connections

7 and 8. Because the secondary SIP server 2 is functioning properly, in steps S12 and S15, the secondary SIP server 2 transmits a reply to the “INVITE” message and in steps S13 and S16, the VOIP call is conducted.

Fig. 6 is another exemplary method and algorithm for conducting voice-over-Internet-protocol (VOIP) calls in a network for providing enhanced VOIP services in accordance with an embodiment of the present disclosure. This alternative method and algorithm is similar to that shown in Fig. 5. However, Fig. 6 illustrates exemplary operations performed when any one of the gateway devices 4 attempts to conduct a VOIP call using the primary SIP server 1, and the primary SIP server 1 is functioning properly. Additionally, the exemplary method and algorithm of Fig. 6 includes operations that are performed by the software executed by the controller 17 of each gateway device 4 in the system.

In steps S17, S18 and S19 the software executed by the controller 17 of each gateway device 4 causes the respective gateway device 4 to store a list of multimedia transfer adapters (MTAs) that are each capable of conducting VOIP calls. The MTAs on the list include, but are not limited to, MTA1, MTA2, MTA3 and MTA4. Storing the list of MTAs can be initiated by, for example, a system administrator or any user operating any of the gateway devices 4. The MTA list may be stored in the memory 15 of each gateway device 4 during MTA provisioning. Alternatively, the system administrator or user operating a respective gateway device 4 may obtain the MTA list from a configuration file or via Dynamic Host Configuration Protocol (DHCP) and may store the list in the memory 15 at any time other than during provisioning. DHCP is a network management protocol used on Internet Protocol (IP) networks in which a DHCP server dynamically assigns an IP address and other network configuration parameters to each device on the network so the devices can communicate with other networks.

In step S20, the software executed by the controller 17 of the gateway device 4 including MTA1 initiates a VOIP call using the network interface 12 and the

connections

7, 8. It is equally likely that any listed MTA 19 may alternatively initiate the VOIP call. For example, the gateway device 4 including MTA2 or MTA3 may initiate the VOIP call.

The gateway device 4 initiates a VOIP call by transmitting an “INVITE” message to the primary SIP server 1 using the network interface 12 and the

connections

7, 8. An “INVITE” message is a message sent to SIP servers to set-up a VOIP call.

In step S21 a reply is received by the gateway device 4 using the network interface 12 and the

connections

7, 8. Because a reply is received, the primary SIP server 1 is functioning properly and has not failed. As a result, in step S22, the gateway device 4 conducts the VOIP call using the network interface 12 and the

connections

7, 8.

After storing the list of MTAs in the gateway devices 4 in steps S18 and S19, in steps S23 and S26, the other gateway devices 4 in the system may initiate VOIP calls by transmitting an “INVITE” message to the primary SIP server 1 using their respective network interface 12 and the

connections

7, 8. In steps S24 and S27, the primary SIP server 1 transmits a reply to the “INVITE” message and in steps S25 and S28, VOIP calls are conducted using the other gateway devices 4.

Using the methods and algorithms for conducting voice-over-Internet-protocol (VOIP) calls in a network after detecting an SIP server failure facilitates reducing the time wasted by users and frustration experienced by users attempting to conduct VOIP calls when a SIP server fails and thus enhance VOIP service.

The present disclosure may be implemented as any combination of an apparatus, a system, an integrated circuit, and a computer program on a non-transitory computer readable recording medium. The one more processors may be implemented as an integrated circuit (IC) , an application specific integrated circuit (ASIC) , or large scale integrated circuit (LSI) , system LSI, super LSI, or ultra LSI components that perform a part or all of the functions described in the present disclosure.

The present disclosure includes the use of software, applications, computer programs, or algorithms. The software, applications, computer programs, or algorithms can be stored on a non-transitory computer-readable medium for causing a computer, such as the one or more processors, to execute the steps described in Figs. 5 and 6. For example, the one or more memories stores software or algorithms with executable instructions and the one or more processors can execute a set of instructions of the software or algorithms in association with onboarding of wireless extenders in the wireless residential network.

The software and computer programs, which can also be referred to as programs, software applications, applications, components, or code, include machine instructions for a programmable processor, and can be implemented in a high-level procedural language, an object-oriented programming language, a functional programming language, a logical programming language, or an assembly language or machine language. The term computer-readable recording medium refers to any computer program product, apparatus or device, such as a magnetic disk, optical disk, solid-state storage device, memory, and programmable logic devices (PLDs) , used to provide machine instructions or data to a programmable data processor, including a computer-readable recording medium that receives machine instructions as a computer-readable signal.

By way of example, a computer-readable medium can comprise DRAM, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired computer-readable program code in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Disk or disc, as used herein, include compact disc (CD) , laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

Use of the phrases “capable of, ” “capable to, ” “operable to, ” or “configured to” in one or more embodiments, refers to some apparatus, logic, hardware, and/or element designed in such a way to enable use of the apparatus, logic, hardware, and/or element in a specified manner. The subject matter of the present disclosure is provided as examples of apparatus, systems, methods, and programs for performing the features described in the present disclosure. However, further features or variations are contemplated in addition to the features described above. It is contemplated that the implementation of the components and functions of the present disclosure can be done with any newly arising technology that may replace any of the above implemented technologies.

Additionally, the above description provides examples, and is not limiting of the scope, applicability, or configuration set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the spirit and scope of the disclosure. Various embodiments may omit, substitute, or add various procedures or components as appropriate. For instance, features described with respect to certain embodiments may be combined in other embodiments.

Claims

An electronic device capable of conducting voice-over-Internet-protocol (VOIP) calls in a network for providing enhanced VOIP services, the electronic device comprising:

a network interface;

a non-transitory memory having instructions stored thereon; and

a hardware processor configured to execute the instructions to:

store in the non-transitory memory a list of other electronic devices connected in the network that are capable of conducting VOIP calls;

initiate a VOIP call from the electronic device using a primary session initiation protocol (SIP) server;

determine in the electronic device whether a failure of the primary SIP server is detected;

in response to the failure being detected, transmit, via the network interface, to each of the other electronic devices on the list a notification regarding the detected failure, and initiate the VOIP call from the electronic device using a secondary SIP server; and

in response to the failure of the primary SIP server not being detected, complete the VOIP call from the electronic device using the primary SIP server.
The electronic device according to claim 1, wherein the hardware processor further executes the instructions to wait a predetermined time for the electronic device to connect to the primary SIP server.
The electronic device according to claim 2, wherein the electronic device is a gateway device.
The electronic device according to claim 1, wherein the other electronic devices on the list receive the notification and conduct VOIP calls using the secondary SIP server.
The electronic device according to claim 1, wherein the hardware processor further executes the instructions to transmit, via the network interface, a message to the primary SIP server to set-up a VOIP call.
The electronic device according to claim 1, wherein the list of other electronic devices includes a list of multimedia transfer adapters included in gateway devices.
The electronic device according to claim 1, wherein the electronic device is included in the list of other electronic devices.
A method for conducting voice-over-Internet-protocol (VOIP) calls in a network to provide enhanced VOIP services, the method comprising:

storing a list of second electronic devices connected in the network that are capable of conducting VOIP calls, thc list being stored in a memory of a first electronic device, the first electronic device also being capable of conducting VOIP calls;

initiating a VOIP call from the first electronic device using a primary session initiation protocol (SIP) server;

determining in the first electronic device whether a failure of the primary SIP server is detected;

in response to the failure being detected, transmitting a notification regarding the failure to each of the second electronic devices on the list via a network interface included in the first electronic device, and initiating the VOIP call from the first electronic device using a secondary SIP server; and

in response to the failure of the primary SIP server not being detected, completing the VOIP call from the first electronic device using the primary SIP server.
The method according to claim 8, wherein the determining in the first electronic device whether a failure of the primary SIP server is detected comprises waiting a predetermined time for the first electronic device to connect to the primary SIP server.
The method according to claim 8, wherein the first electronic device is a gateway device.
The method according to claim 8, further comprising:

receiving, by a network interface of each second listed electronic device, the notification; and

conducting, by each listed second electronic device, VOIP calls using the secondary SIP server.
The method according to claim 8, the initiating the VOIP call from the first electronic device using a primary SIP server comprises transmitting, via the network interface, a message to the primary SIP server to set-up a VOIP call.
The method according to claim 8, wherein the list of second electronic devices includes a list of multimedia transfer adapters included in gateway devices.
Thc method according to claim 8, wherein the first electronic device is included on the list of second electronic devices.
A non-transitory computer-readable recording medium in a first electronic device capable of conducting voice-over-Internet-protocol (VOIP) calls in a network for providing enhanced VOIP services, the network communicatively connecting the first electronic device and one or more second electronic devices, the non-transitory computer-readable recording medium storing instructions which when executed by a hardware processor cause the non-transitory recording medium to perform steps comprising:

storing a list of second electronic devices connected in the network that arc capable of conducting VOIP calls, the list being stored in a memory of the first electronic device;

initiating a VOIP call from the first electronic device using a primary session initiation protocol (SIP) server;

determining in the first electronic device whether a failure of the primary SIP server is detected;

in response to the failure being detected, transmitting to each of the second electronic devices on the list a notification regarding the detected failure, and initiating the VOIP call from the first electronic device using a secondary SIP server; and

in response to the failure of the primary SIP server not being detected, completing the VOIP call from the first electronic device using the primary SIP server.
The non-transitory computer-readable recording medium according to claim 15, further comprising waiting a predetermined time for the first electronic device to connect to the primary SIP server.
The non-transitory computer-readable recording medium according to claim 15, wherein the first electronic device is a gateway device.
The non-transitory computer-readable recording medium according to claim 15, further comprising receiving the notification and conducting VOIP calls using the secondary SlP server.
The non-transitory computer-readable recording medium according to claim 15, further comprising transmitting a message to the primary SIP server to set-up a VOIP call.
The non-transitory computer-readable recording medium according to claim 15, wherein the list of second electronic devices includes a list of multimedia transfer adapters included in gateway devices.