IP Library Granted Patent US 9,749,296
Granted Patent B1
US 9,749,296 · App. 11/592,599 · Granted Aug 29, 2017

Method and apparatus for modifying address information in signaling messages to ensure in-path devices remain in signaling path between endpoints

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 9,749,296
App. No.
11/592,599
Granted
Aug 29, 2017
Kind
B1
Abstract

Contact information in SIP signaling messages is modified at each in-path network device during the signaling process (along with storage of mapping information) to allow the in-path network devices (and proxy server) to identify the next (or previous) hop device in the path, and thus, maintain the path taken by signaling messages early on during the signaling process. Subsequent request and response signaling messages transmitted during the session follow this path, which ensures that the in-path network devices remain in the SIP signaling path.

Claims (86)

1. A method of modifying a signaling message between an originating endpoint device and a destination endpoint device in a network, the method comprising:

receiving a first signaling message at a first network device from the originating endpoint device, the first signaling message corresponding to a communication session between the originating endpoint device and the destination endpoint device, and having a contact field comprising a first address identifying the originating endpoint device;

storing the first address;

generating and storing a hash identifier;

mapping the hash identifier to the first address;

generating, at the first network device a second signaling message comprising the first signaling message having a modified contact field comprising the hash identifier and a second address identifying the first network device as a contact point to the destination endpoint device; and

transmitting the second signaling message to a second network device;

receiving a third signaling message at the first network device from the second network device, the third signaling message including the second address and the hash identifier;

determining the first address from the received has identifier; and

transmitting the third signaling message to the originating endpoint device.

2. The method in accordance with claim 1 wherein the first signaling message and the second signaling message are Session Initiation Protocol (SIP) signaling messages.

3. The method in accordance with claim 2 wherein the first signaling message and the second signaling message are each INVITE messages.

4. The method in accordance with claim 1 wherein the second address identifying the first network device comprises a network address of the first network device.

5. The method in accordance with claim 4 wherein the first signaling message is a Session Initiation Protocol (SIP) signaling message, and the first network device is a SIP firewall device.

6. The method in accordance with claim 1 further comprising:

receiving the second signaling message at the second network device from the first network device;

generating at the second network device a third signaling message having a contact field comprising a third address identifying the second network device as the contact point to the destination endpoint device, the second address at the second signaling message, and the hash identifier at the second signaling message; and

transmitting the third signaling message to a third network device.

7. The method in accordance with claim 1 further comprising:

receiving a third signaling message at the first network device from the second network device, the third signaling message having a contact field comprising a third address identifying the second network device;

storing the third address;

generating and storing a second hash identifier;

mapping the second hash identifier to the third address;

generating at the first network device, a fourth signaling message comprising the third signaling message having a modified contact field comprising the second hash identifier and a fourth address identifying the first network device; and

transmitting the fourth signaling message to the originating endpoint device.

8. The method in accordance with claim 7 wherein the first signaling message comprises a SIP request message and the third signaling message comprises a SIP response message.

9. The method in accordance with claim 7 further comprising:

receiving a fifth signaling message at the first network device from the originating endpoint device, the fifth signaling message including the fourth address and the second hash identifier;

determining the third address from the received second hash identifier; and

transmitting a sixth signaling message to the second network device.

10. The method in accordance with claim 9 wherein the first signaling message comprises a SIP request message, the third signaling message comprises a SIP response message, and the fifth signaling message comprises a subsequent SIP request message.

11. The method in accordance with claim 1 wherein the first signaling message comprises a SIP request message and the third signaling message comprises a subsequent SIP request message.

12. The method in accordance with claim 1 further comprising:

receiving a third signaling message at the first network device from the second network device, the third signaling message including the second address and the hash identifier;

determining the first address from the received hash identifier;

generating, at the first network device, to a fourth signaling message comprising the third signaling message including the first address identifying the originating endpoint device; and

transmitting the fourth signaling message to the originating endpoint device.

13. A network device configured to be placed in a communication path between an endpoint device and a proxy server in a network, the network device comprising:

a network interface configured to receive and transmit one or more signaling messages;

a memory configured to store data;

processing circuitry configured to process received signaling messages; and

wherein the network device is configured to:

receive a first signaling message from an originating endpoint device, the first signaling message corresponding to a communication session between the originating endpoint device and a destination endpoint device, and having a contact field comprising a first address identifying the originating endpoint device;

store the first address;

generate and store a hash identifier;

map the hash identifier to the first address;

modify the received first signaling message to generate a second signaling message comprising the second first signaling message having a modified contact field comprising the hash identifier and a second address identifying the network device as a contact point to the destination endpoint device;

transmit the second signaling message to another network device;

receive a third signaling message at the network device from another network device, the third signaling message including the second address and the hash identifier;

determine the first address from the received hash identifier; and

transmit the third signaling message to the originating endpoint device.

14. The network device in accordance with claim 13 wherein the first signaling message and the second signaling message are Session Initiation Protocol (SIP) signaling messages.

15. The network device in accordance with claim 13 wherein the first signaling message and the second signaling message are each INVITE messages.

16. The network device in accordance with claim 13 wherein the network device is further configured to:

receive a third signaling message at the network device from another network device, the third signaling message having a contact field comprising a third address identifying another network device;

store the third address;

generate and store a second hash identifier;

map the second hash identifier to the third address;

generate, at the network device, to generate a fourth signaling message comprising the third signaling message having a modified contact field comprising the second hash identifier and a fourth address identifying the network device; and

transmit the fourth signaling message to the originating endpoint device.

17. The network device in accordance with claim 16 wherein the first signaling message comprises a Session Initiation Protocol (SIP) request message and the third signaling message comprises a SIP response message.

18. The network device in accordance with claim 16 wherein the network device is further configured to:

receive a fifth signaling message at the network device from the originating endpoint device, the fifth signaling message including the fourth address and the second hash identifier;

determine the third address from the received second hash identifier; and

transmit a sixth signaling message to another network device.

19. The network device in accordance with claim 18 wherein the first signaling message comprises a Session Initiation Protocol (SIP) request message, the third signaling message comprises a SIP response message, and the fifth signaling message comprises a subsequent SIP request message.

20. The method in accordance with claim 13 wherein the network device is further configured to:

receive a third signaling message at the network device from another network device, the third signaling message including the second address and the hash identifier;

determine the first address from the received hash identifier; and

transmit the third signaling message to the originating endpoint device.

21. The network device in accordance with claim 13 wherein the first signaling message comprises a Session Initiation Protocol (SIP) request message and the third signaling message comprises a subsequent SIP request message.

22. The network device in accordance with claim 13 wherein the network device is further configured to:

receive a third signaling message at the first network device from another network device, the third signaling message including the second address and the hash identifier;

determine the first address from the received hash identifier;

generate at the first network device, a fourth signaling message comprising the third signaling message including the first address identifying the originating endpoint device; and

transmit the fourth signaling message to the originating endpoint device.

23. A computer program embodied on a non-transitory computer readable medium and operable to be executed by a processor, the computer program comprising computer readable program code for:

receiving a first signaling message at a first network device from an originating endpoint device, the first signaling message corresponding to a communication session between the originating endpoint device and a destination endpoint device, and having a contact field comprising a first address identifying the originating endpoint device;

storing the first address;

generating and storing a hash identifier;

mapping the hash identifier to the first address;

generating, at the first network device, a second signaling message comprising the second first signaling message having a modified contact field comprising the hash identifier and a second address identifying the first network device as a contact point to the destination endpoint device; and

transmitting the second signaling message to a second network device;

receiving a third signaling message at the network device from another network device, the third signaling message including the second address and the hash identifier;

determine the first address from the received hash identifier; and

transmit the third signaling message to the originating endpoint device.

Assignments (25)
(SECURITY INTEREST) GRANTOR'S NAME CHANGE Recorded Sep 21, 2023
From: AVAYA INC.
To: AVAYA LLC
Reel/Frame 065019/0231 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 53955/0436) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063705/0023 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001) Recorded May 18, 2023
From: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
To: ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.); AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; HYPERQUALITY, INC.; HYPERQUALITY II, LLC; CAAS TECHNOLOGIES, LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 063779/0622 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 61087/0386) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063690/0359 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 4, 2023
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 063542/0662 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 3, 2023
From: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; KNOAHSOFT INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB [COLLATERAL AGENT]
Reel/Frame 063742/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026 Recorded Apr 26, 2023
From: CITIBANK, N.A., AS COLLATERAL AGENT
To: AVAYA HOLDINGS CORP.; AVAYA INC.; AVAYA MANAGEMENT L.P.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063457/0001 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Aug 5, 2022
From: AVAYA INC.; INTELLISIST, INC.; AVAYA MANAGEMENT L.P.; AVAYA CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 061087/0386 →
SECURITY INTEREST Recorded Sep 25, 2020
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 053955/0436 →
SECURITY INTEREST Recorded Jan 23, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 045124/0026 →
RELEASE OF SECURITY INTEREST Recorded Jan 11, 2018
From: CITICORP USA, INC.
To: AVAYA, INC.; SIERRA HOLDINGS CORP.
Reel/Frame 045045/0564 →
SECURITY INTEREST Recorded Jan 10, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 045034/0001 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 023892/0500 Recorded Dec 15, 2017
From: CITIBANK, N.A.
To: AVAYA INC.
Reel/Frame 044891/0564 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 030083/0639 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 045012/0666 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 029608/0256 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 044891/0801 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 025863/0535 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST, NA
To: AVAYA INC.
Reel/Frame 044892/0001 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001 Recorded Dec 15, 2017
From: CITIBANK, N.A.
To: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION); VPNET TECHNOLOGIES, INC.
Reel/Frame 044893/0531 →
SECURITY INTEREST Recorded Jan 27, 2017
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS CORPORATION; VPNET TECHNOLOGIES, INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 041576/0001 →
SECURITY AGREEMENT Recorded Mar 13, 2013
From: AVAYA, INC.
To: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE
Reel/Frame 030083/0639 →
SECURITY AGREEMENT Recorded Jan 10, 2013
From: AVAYA, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 029608/0256 →
SECURITY AGREEMENT Recorded Feb 22, 2011
From: AVAYA INC., A DELAWARE CORPORATION
To: BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLATERAL AGENT, THE
Reel/Frame 025863/0535 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 26, 2010
From: NORTEL NETWORKS LIMITED
To: AVAYA INC.
Reel/Frame 023998/0878 →
SECURITY AGREEMENT Recorded Feb 5, 2010
From: AVAYA INC.
To: CITICORP USA, INC., AS ADMINISTRATIVE AGENT
Reel/Frame 023905/0001 →
SECURITY AGREEMENT Recorded Feb 4, 2010
From: AVAYA INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 023892/0500 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 3, 2006
From: KAUSHIK, MEENAKSHI; AUDET, FRANCOIS; SRIVASTAVA, SAMIR
To: NORTEL NETWORKS LIMITED
Reel/Frame 018569/0649 →