IP Library Granted Patent US 11,677,792
Granted Patent B2
US 11,677,792 · App. 17/161,142 · Granted Jun 13, 2023

IP tolerance and signaling interworking

Inventors: Tibor Lukac (Superior, CO); Harsh V. Mendiratta (East Brunswick, NJ)
Assignee: Avaya Inc.
H04L65/1104H04L61/4535H04L61/5007H04L65/1045H04L65/1073H04L67/14H04L61/251H04L2101/30H04L2101/385H04L2101/659H04L2101/686
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 11,677,792
App. No.
17/161,142
Granted
Jun 13, 2023
Kind
B2
Abstract

In an attempt to establish a communication session between a first communication entity and a second communication entity, a first message is received. For example, the first message may be a SIP INVITE message. A determination is made, based on a registration message from the first communication entity and/or the second communication entity, that at least one of the first communication entity or the second communication entity is Internet Protocol (IP) version intolerant. In response to determining that the at least one of the first communication entity or the second communication entity is IP version intolerant, one or more IP addresses are adapted in messages (e.g., the SIP INVITE message) for establishing the communication session. The adaption changes/removes the one or more IP addresses to a different IP version to ensure proper IP compatibility.

Claims (32)

1. A method comprising:

receiving, by a microprocessor, a first Session Initiation Protocol (SIP) REGISTER message for registering a first communication endpoint to be registered with one or more other communication endpoints using an address of record for a user;

determining, by the microprocessor, that an Internet Protocol (IP) version of at least one of the one or more other communication endpoints does not match an IP version of the first communication endpoint;

in response to determining that the IP version of the at least one of the one or more other communication endpoints does not match the first communication endpoint's IP version, removing, by the microprocessor, in a SIP 200 OK response message, an IP address for each of the at least one of the one or more other communication endpoints whose IP version does not match the first communication endpoint's IP version; and

forking a SIP INVITE message into a plurality of SIP INVITE messages, wherein the forking is based on forking the plurality of SIP INVITE messages to only communication entities that use the same IP version as the address of record for the user.

2. The method of claim 1 , further comprising:

replacing each removed IP address with an IP address of a compatible IP version.

3. The method of claim 1 , wherein at least one of the one or more other communication endpoints comprises a Back-to-Back User Agent (B2BUA).

4. The method of claim 3 , wherein the B2BUA registers two separate SIP dialogs.

5. The method of claim 1 , wherein determining, by the microprocessor, that the Internet Protocol (IP) version of the at least one of the one or more other communication endpoints does not match the first communication endpoint's IP version comprises processing a SIP intolerance parameter in a SIP contact header.

6. The method of claim 1 , wherein the first communication endpoint is IPv4 intolerant and supports IPv6 only.

7. The method of claim 1 , wherein the first communication endpoint is IPv6 intolerant and supports IPv4 only.

8. The method of claim 1 , wherein removing, by the microprocessor, in the SIP 200 OK response message the IP address of each of the at least one of the one or more other communication endpoints whose IP version does not match the first communication endpoint's IP version comprising stripping SIP Record-Route headers including the IP address of each of the at least one of the one or more other communication endpoints whose IP version does not match the first communication endpoint's IP version with an IP address of a compatible IP version.

9. The method of claim 1 , wherein removing, by the microprocessor, in the SIP 200 OK response message the IP address of each of the at least one of the one or more other communication endpoints whose IP version does not match the first communication endpoint's IP version comprising stripping SIP Via headers including the IP address of each of the at least one of the one or more other communication endpoints whose IP version does not match the first communication endpoint's IP version with an IP address of a compatible IP version.

10. A system comprising:

a microprocessor; and

a computer readable medium, coupled with the microprocessor and comprising microprocessor readable and executable instructions that cause the microprocessor to:

receive, by athe microprocessor, a first Session Initiation Protocol (SIP) REGISTER message for registering a first communication endpoint to be registered with one or more other communication endpoints using an address of record for a user;

determine, by the microprocessor, that an Internet Protocol (IP) version of at least one of the one or more other communication endpoints does not match an IP version of the first communication endpoint; and

in response to determining that the IP version of the at least one of the one or more other communication endpoints does not match the first communication endpoint's IP version, remove, by the microprocessor, in a SIP 200 OK response message, an IP address of each of the at least one of the one or more other communication endpoints whose IP version does not match the first communication endpoint's IP version, and fork a SIP INVITE message into a plurality of SIP INVITE messages, wherein the forking is based on forking the plurality of SIP INVITE messages to only communication entities that use the same IP version as the address of record for the user.

11. The system of claim 10 , wherein instructions further cause the microprocessor to:

replace the removed IP address of each of the at least one of the one or more other communication endpoints whose IP version does not match the first communication endpoint's IP version with an IP address of a compatible IP version.

12. The system of claim 10 , wherein one of the one or more other communication endpoints comprises a Back-to-Back User Agent (B2BUA).

13. The system of claim 12 , wherein the B2BUA registers two separate SIP dialogs.

14. The system of claim 10 , wherein instructions further cause the microprocessor to:

process a SIP intolerance parameter in a SIP contact header to determine that the at least one of the one or more other communication endpoint's IP version does not match the first communication endpoint's IP version.

15. The system of claim 10 , wherein the first communication endpoint is IPv4 intolerant and supports IPv6 only.

16. The system of claim 10 , wherein the first communication endpoint is IPv6 intolerant and supports IPv4 only.

17. The method system of claim 10 , wherein instructions further cause the microprocessor to:

strip SIP Record-Route headers including the IP address of each of the at least one of the one or more other communication endpoints whose IP version does not match the first communication endpoint's IP version with an IP address of a compatible IP version.

18. The system of claim 10 , wherein instructions further cause the microprocessor to:

strip SIP Via headers including the IP address of each of the at least one of the one or more other communication endpoints whose IP version does not match the first communication endpoint's IP version with an IP address of a compatible IP version.

Assignments (8)
INTELLECTUAL PROPERTY SECURITY AGREEMENT – SUPPLEMENT NO. 1 Recorded May 29, 2024
From: AVAYA LLC (FORMERLY KNOWN AS AVAYA INC.); AVAYA MANAGEMENT L.P.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB, AS COLLATERAL AGENT
Reel/Frame 067559/0284 →
(SECURITY INTEREST) GRANTOR'S NAME CHANGE Recorded Sep 21, 2023
From: AVAYA INC.
To: AVAYA LLC
Reel/Frame 065019/0231 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Jul 31, 2023
From: AVAYA LLC (FORMERLY KNOWN AS AVAYA INC.); AVAYA MANAGEMENT L.P.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 064431/0001 →
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 →
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 28, 2021
From: LUKAC, TIBOR; MENDIRATTA, HARSH V.
To: AVAYA INC.
Reel/Frame 056066/0269 →
Continuity (2)
Division 15617605 · Jun 8, 2017
Related Publication 20210152612A1 · May 20, 2021