9680882

Automatic Configuration of Endpoint Communication Devices to Set Up a Voip Network

PublishedJune 13, 2017
Assigneenot available in USPTO data we have
Technical Abstract

Patent Claims
19 claims

Legal claims defining the scope of protection, as filed with the USPTO.

1

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

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

3

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

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

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

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

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

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

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

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

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

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

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

14

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

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

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

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

18

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

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.

Patent Metadata

Filing Date

Unknown

Publication Date

June 13, 2017

Inventors

Sounak SINHA
Subhankar DEY

Want to explore more patents?

Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.

Citation & reuse

Analysis on this page is generated by Patentable — an AI-powered patent intelligence platform. AI-generated summaries, explanations, and analysis may be reused with attribution and a visible link back to the canonical URL below. Patent abstracts and claims are USPTO public domain.

Cite as: Patentable. “AUTOMATIC CONFIGURATION OF ENDPOINT COMMUNICATION DEVICES TO SET UP A VOIP NETWORK” (9680882). https://patentable.app/patents/9680882

© 2026 Patentable. All rights reserved.

Patentable is a research and drafting-assistant tool, not a law firm, and does not provide legal advice. Documents we generate are drafts for review by a licensed patent attorney.