IP Library Granted Patent US 8,843,601
Granted Patent B1
US 8,843,601 · App. 13/940,674 · Granted Sep 23, 2014

Systems and methods for VOIP communication completion to a mobile device

Inventors: Boaz Zehavi (Jersey City, NJ); Dany Orr (Tel Aviv, IL); Guy Baron (Tel Aviv, IL); Gil Osher (Tel Aviv, IL)
Assignee: Vonage Network, LLC
H04L29/06197
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,843,601
App. No.
13/940,674
Granted
Sep 23, 2014
Kind
B1
Abstract

Systems and methods for establishing an IP telephone call to a called party's telephony device include attempting to send a call setup request directly to the called party's telephony device, and requesting that a push notification be sent to the called party's telephony device. If the direct request does not reach the called party's telephony device, the push notification will result in the called party's telephony device contacting the IP telephony system to setup the requested call. In some embodiments, the request for a push notification is not sent until the direct request is determined to have failed.

Claims (35)

1. A method of establishing a telephony communication with a server of an IP telephony system, comprising:

receiving, from a server of an IP telephony system, a request to setup a telephony communication, wherein the request includes a communication identifier;

receiving, from a third party server, a push notification, wherein the push notification includes a communication identifier; and

failing to respond to the push notification if the communication identifier in the message received from the server of the IP telephony system matches the communication identifier in the push notification received from the third party server.

2. The method of claim 1 , further comprising sending a response message to a server of the IP telephony system if the communication identifier in the request received from the server of the IP telephony system does not match the communication identifier in the push notification received from the third party server.

3. The method of claim 2 , wherein the step of sending a response message to a server of the IP telephony system comprises sending a registration request to the server of the IP telephony system.

4. The method of claim 1 , further comprising:

sending a response to the server of the IP telephony system; and

communicating with the server to setup a telephony communication.

5. The method of claim 1 , wherein the step of receiving, from a server of an IP telephony system, a request to setup a telephony communication comprises receiving a Session Initiation Protocol (SIP) INVITE request from the server of the IP telephony system.

6. The method of claim 5 , further comprising sending a SIP Acknowledgement message to the server of the IP telephony system.

7. The method of claim 1 , further comprising saving, in a memory, the communication identifier in the request received from the server of the IP telephony system.

8. A system for establishing a telephony communication with a server of an IP telephony system, comprising:

means for receiving, from a server of an IP telephony system, a request to setup a telephony communication, wherein the request includes a communication identifier;

means for receiving, from a third party server, a push notification, wherein the push notification includes a communication identifier; and

means for failing to respond to the push notification if the communication identifier in the message received from the server of the IP telephony system matches the communication identifier in the push notification received from the third party server.

9. A system for establishing a telephony communication with a server of an IP telephony system, comprising:

a signaling unit that receives, from a server of an IP telephony system, a request to setup a telephony communication, wherein the request includes a communication identifier; and

a push notification receiving unit that receives, from a third party server, a push notification, wherein the push notification includes a communication identifier, wherein the push notification receiving unit is configured to fail to respond to the push notification if the communication identifier in the message received from the server of the IP telephony system matches the communication identifier in the push notification received from the third party server.

10. The system of claim 9 , further comprising a registration unit that sends a registration message to a server of the IP telephony system if the communication identifier in the request received from the server of the IP telephony system does not match the communication identifier in the push notification received from the third party server.

11. The system of claim 9 , further comprising a registration unit that sends a response to the server of the IP telephony system, and that communicates with the server to setup a telephony communication.

12. The system of claim 9 , wherein the signaling unit receives, from the server of the IP telephony system, a Session Initiation Protocol (SIP) INVITE message, and wherein the signaling unit sends a SIP Acknowledgement message to the server of the IP telephony system.

13. The system of claim 9 , further comprising a memory, wherein when the signaling unit receives a request to setup a telephony communication, the signaling unit stores the communication identifier contained in the received setup request in the memory.

14. A non-transitory computer readable medium containing instructions which, when performed by one or more processors of a telephony device, cause the telephony device to perform a method of establishing a telephony communication with a server of an IP telephony system, the method comprising:

receiving, from a server of an IP telephony system, a request to setup a telephony communication, wherein the request includes a communication identifier;

receiving, from a third party server, a push notification, wherein the push notification includes a communication identifier;

failing to respond to the push notification if the communication identifier in the message received from the server of the IP telephony system matches the communication identifier in the push notification received from the third party server.

15. The non-transitory computer readable medium of claim 14 , wherein the method further comprises sending a response message to a server of the IP telephony system if the communication identifier in the request received from the server of the IP telephony system does not match the communication identifier in the push notification received from the third party server.

16. The non-transitory computer readable medium of claim 15 , wherein the step of sending a response message to a server of the IP telephony system comprises sending a registration request to the server of the IP telephony system.

17. The non-transitory computer readable medium of claim 14 , wherein the method further comprises:

sending a response to the server of the IP telephony system; and

communicating with the server to setup a telephony communication.

18. The non-transitory computer readable medium of claim 14 , wherein the step of receiving, from a server of an IP telephony system, a request to setup a telephony communication comprises receiving a Session Initiation Protocol (SIP) INVITE request from the server of the IP telephony system.

19. The non-transitory computer readable medium of claim 18 , wherein the method further comprises sending a SIP Acknowledgement message to the server of the IP telephony system.

20. The non-transitory computer readable medium of claim 14 , wherein the method further comprises saving, in a memory, the communication identifier in the request received from the server of the IP telephony system.

Assignments (8)
RELEASE OF SECURITY INTEREST Recorded Jul 28, 2022
From: JPMORGAN CHASE BANK, N.A.
To: VONAGE AMERICA INC.; VONAGE HOLDINGS CORP.; VONAGE BUSINESS INC.; NEXMO INC.; TOKBOX, INC.
Reel/Frame 061002/0340 →
CHANGE OF NAME Recorded Jun 8, 2022
From: VONAGE AMERICA INC.
To: VONAGE AMERICA LLC
Reel/Frame 060313/0447 →
SECURITY INTEREST Recorded Nov 12, 2018
From: VONAGE AMERICA INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 047502/0628 →
MERGER Recorded Mar 31, 2016
From: VONAGE NETWORK LLC
To: VONAGE AMERICA INC.
Reel/Frame 038320/0327 →
CORRECTIVE ASSIGNMENT TO CORRECT THE PATENT APPLICATION NUMBER 13966486 PREVIOUSLY RECORDED ON REEL 033545 FRAME 0424. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded Jan 21, 2016
From: VONAGE HOLDINGS CORP.; VONAGE NETWORK LLC; VONAGE BUSINESS SOLUTIONS INC.; VONAGE AMERICA INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 037570/0203 →
SECURITY INTEREST Recorded Jul 29, 2015
From: VONAGE HOLDINGS CORP.; VONAGE AMERICA INC.; VONAGE BUSINESS SOLUTIONS, INC.; VONAGE NETWORK LLC
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 036205/0485 →
SECURITY INTEREST Recorded Aug 14, 2014
From: VONAGE HOLDINGS CORP.; VONAGE NETWORK LLC; VONAGE BUSINESS SOLUTIONS INC.; VONAGE AMERICA INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 033545/0424 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 12, 2013
From: ZEHAVI, BOAZ; ORR, DANY; BARON, GUY; OSHER, GIL
To: VONAGE NETWORK, LLC
Reel/Frame 030788/0396 →