IP Library Granted Patent US 9,680,882
Granted Patent B2
US 9,680,882 · App. 14/338,273 · Granted Jun 13, 2017

Automatic configuration of endpoint communication devices to set up a VoIP network

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,680,882
App. No.
14/338,273
Granted
Jun 13, 2017
Kind
B2
Abstract

Implementations relate to automatic configuration of endpoint communication devices to set up a communication network such as a VOIP network. In some implementations, a method includes a server receiving an extension request for device extension from an endpoint communications device connected to a communication network, mapping an identifier for the endpoint communications device to a device extension, and transmitting the device extension to the endpoint communications device.

Claims (61)

1. A method comprising:

receiving a device extension request at a server from an endpoint communications device connected to a communication network;

parsing the device extension request to determine an identifier for the endpoint communications device;

determining if a device extension has been mapped to the identifier for the endpoint communications device, wherein the determining includes comparing the identifier for the endpoint communications device against a binding store, and wherein the binding store includes mappings between identifiers and associated device extension values;

if a previously stored device extension has been mapped to the identifier for the endpoint communications device:

retrieving the previously stored device extension mapped to the endpoint communications device; and

providing the previously stored device extension to the endpoint communications device in response to the device extension request;

if a device extension has not been mapped to the identifier for the endpoint communications device:

creating a unique device extension for the endpoint communication device, wherein the unique device extension is unique in that the device extension is not used by any other endpoint communication devices on the communication network; and

storing a mapping of the created unique device extension and the identifier included in the request in the binding store; and

providing the created unique device extension to the endpoint communications device in response to the device extension request.

2. The method according to claim 1 , wherein the device extension is a session initiation protocol (SIP) extension.

3. The method according to claim 2 , wherein the transmitted SIP extension is included in a DHCPOFFER response that also includes an IP address for the endpoint communications device, an IP address for an SIP server, authentication information, and an extension number.

4. The method according to claim 2 , further comprising enabling one or more DHCP options on an IP address that may be used by an endpoint communications device to request the SIP extension.

5. The method according to claim 1 , wherein the identifier includes at least one of a media access control address, an Internet protocol address, a personal identification number, a serial number, and an integrated circuit card ID, and wherein the identifier further includes an international mobile equipment identity number, an international mobile subscriber identity, and a mobile equipment identifier.

6. The method according to claim 1 , further comprising:

evaluating the device extension request to determine the identifier; and

evaluating the device extension request to determine if the endpoint communications device is configured to receive the device extension.

7. The method according to claim 6 wherein evaluating the device extension request to determine if the endpoint communications device is configured to receive the device extension includes checking for one or more particular options included in the device extension request.

8. The method according to claim 1 , further comprising:

establishing a pool of IP addresses for local area network ports on an SIP server;

establishing a router management address;

enabling a DHCP server on the router management address;

enabling an SIP server on the router management address; and

programming one or more DHCP options on the router management address, wherein one of the one or more DHCP options provides an SIP domain, the device extension for the endpoint communications device as an SIP extension, and authentication information.

9. The method according to claim 1 , wherein the extension request comprises a discover message or request message provided in an address allocation protocol to an address allocation server operative to provide the device extension that is operative for use in a communication session protocol.

10. The method according to claim 1 , wherein the created unique device extension is derived from a port number to which the endpoint communications device is currently connected and an endpoint device type of the endpoint communications device.

11. The method according to claim 1 , further comprising storing the mapped device extension for the endpoint communications device in a binding store which resides in a non-volatile memory.

12. A device comprising:

a memory for storing executable instructions; and

at least one processor operative to access the memory and execute the instructions to perform operations comprising:

receiving a device extension request from an endpoint communications device connected to a communication network;

parsing the device extension request to determine an identifier for the endpoint communications device;

determining if a device extension has been mapped to the identifier for the endpoint communications device, wherein the determining includes comparing the identifier for the endpoint communications device against a binding store, and wherein the binding store includes mappings between identifiers and associated device extension values;

if a previously stored device extension has been mapped to the identifier for the endpoint communications device:

retrieving the previously stored device extension mapped to the endpoint communications device; and

providing the previously stored device extension to the endpoint communications device in response to the device extension request;

if a device extension has not been mapped to the identifier for the endpoint communications device:

creating a unique device extension for the endpoint communication device, wherein the unique device extension is unique in that the device extension is not used by any other endpoint communication devices on the communication network; and

storing a mapping of the created unique device extension and the identifier included in the request in the binding store;

providing the created unique device extension to the endpoint communications device in response to the device extension request.

13. The device according to claim 12 , wherein the device extension is a session initiation protocol (SIP) extension.

14. The device according to claim 12 , further comprising operations of:

evaluating the extension request to determine an identifier; and

evaluating the extension request to determine if the endpoint communications device is configured to receive the SIP extension.

15. The device according to claim 14 wherein evaluating the device extension request to determine if the endpoint communications device is configured to receive the device extension includes checking for one or more particular options included in the device extension request.

16. The device according to claim 12 further comprising an operation of creating the device extension for the endpoint communication device, wherein the device extension is not being used by any other endpoint communication devices on a communication network of the endpoint communication device.

17. The device according to claim 12 , further comprising retrieving a previously stored device extension mapped to the endpoint communications device.

18. The device according to claim 12 , further comprising storing the mapped device extension for the endpoint communications device in a binding store which resides in a non-volatile memory coupled to the device.

19. A method comprising:

receiving a device extension request from an endpoint communications device;

parsing the device extension request for to determine an identifier for the endpoint communications device;

determining if a device extension has been mapped to the identifier for the endpoint communications device, wherein the determining includes comparing the identifier for the endpoint communications device against a binding store, and wherein the binding store includes mappings between identifiers and associated device extension values;

if a previously stored device extension has been mapped to the identifier for the endpoint communications device:

retrieving the previously stored device extension mapped to the endpoint communications device; and

providing the previously stored device extension to the endpoint communications device in response to the device extension request;

if a device extension has not been mapped to the identifier for the endpoint communications device:

creating a unique device extension for the endpoint communication device, wherein the unique device extension is unique in that the device extension is not used by any other endpoint communication devices on the communication network, and wherein the unique device extension is a session initiation protocol (SIP) extension; and

storing a mapping of the created unique device extension and the identifier included in the request in the binding store; and

providing the created unique device extension to the endpoint communications device in response to the device extension request, wherein if the endpoint communications device is configured to receive the SIP extension, providing the endpoint communications device with a response that includes

configuration parameters that allow the endpoint communications device to communicatively couple with an SIP server.

Assignments (13)
AMENDED SECURITY AGREEMENT Recorded Aug 18, 2023
From: EXTREME NETWORKS, INC.; AEROHIVE NETWORKS, INC.
To: BANK OF MONTREAL
Reel/Frame 064782/0971 →
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 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 →
SECURITY INTEREST Recorded May 1, 2018
From: EXTREME NETWORKS, INC.
To: BANK OF MONTREAL
Reel/Frame 046050/0546 →
RELEASE OF SECURITY INTEREST Recorded May 1, 2018
From: SILICON VALLEY BANK
To: EXTREME NETWORKS, INC.
Reel/Frame 046051/0775 →
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 →
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 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 →
THIRD AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT Recorded Oct 31, 2017
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 044639/0300 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 15, 2017
From: AVAYA INC.; AVAYA COMMUNICATION ISRAEL LTD; AVAYA HOLDINGS LIMITED
To: EXTREME NETWORKS, INC.
Reel/Frame 043569/0047 →
SECOND AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT Recorded Jul 14, 2017
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 043200/0614 →
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 20, 2017
From: DEY, SUBHANKAR
To: AVAYA INC.
Reel/Frame 041026/0455 →