Method and system for transmitting and receiving configuration and registration information for session initiation protocol devices

• US 8,954,542 B2
• Filed: 06/14/2011
• Issued: 02/10/2015
• Est. Priority Date: 06/14/2011
• Status: Active Grant

• Current Assignee: Arlington Technologies, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Avaya Incorporated
• Inventors: Parsons, Shane, Luo, Shaowu, Coutu, Alain, Marshall, John
• Primary Examiner(s): Pollack, Melvin H
• Application Number:
  US13/160,188
• Publication Number:
  US 20120324061A1
• Time in Patent Office: 1,337 Days
• Field of Search: 709/220
• US Class Current: 709/220
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 65/1073 Registration or de-registration
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A system is provided for configuring a Session Initiation Protocol (SIP) device. The system includes at least one SIP server in communication with the SIP device over an Internet Protocol (IP) network. The at least one SIP server includes a database that stores SIP device configuration data and a receiver that receives a first SIP message to initiate SIP device configuration. The at least one SIP server also includes a transmitter that transmits configuration data to the SIP device in response to receiving the first SIP message. The receiver also receives a second message from the SIP device indicating whether the SIP device was successfully configured based on the configuration data.

Claims

1. A system for configuring a Session Initiation Protocol (SIP) device, the system comprising:

at least one SIP server in communication with the SIP device over an Internet Protocol (IP) network, the at least one SIP server having;

a database configured to store SIP device configuration data;

a receiver configured to receive a first SIP INVITE message having a configuration request message to initiate SIP device configuration, the first SIP INVITE message including a uniform resource identifier (URI) identifying one of the at least one SIP server;

a transmitter configured to transmit configuration data to the SIP device in response to receiving the first SIP INVITE message, the SIP device configuration data being in an Extensible Markup Language (XML) format and specifying functionality of the SIP device based on at least one of device location and device identification; and

the receiver configured to receive a second message from the SIP device indicating whether the SIP device was successfully configured based on the configuration data.

2. The system of claim 1, further comprising at least one SIP proxy server configured to route the first SIP INVITE message to the identified one of the at least one SIP server.

3. The system of claim 2, wherein the at least one SIP server includes a primary SIP server and an alternate SIP server, the first SIP INVITE message being routed by the at least one SIP proxy server to the alternate SIP server when the primary SIP server is unavailable.

4. The system of claim 3, wherein the at least one proxy server includes a plurality of SIP proxy servers, the first SIP INVITE message being routed through the plurality of SIP proxy servers.

5. The system of claim 1, wherein the transmitted configuration data is based in part on time of day.

6. The system of claim 1, further comprising transmitting modified configuration data in response to determining the second message indicates the SIP device is not successfully configured.

7. The system of claim 1, wherein the first SIP INVITE message includes at least one identification element corresponding to the SIP device.

8. The system of claim 7, wherein the at least one identification element includes one of a client IP address, primary Terminal Number (TN) and secondary TN.

9. The system of claim 7, wherein the transmitted configuration data includes one of a phone key functionality data and at least one SIP device feature.

16. The system of claim 1, wherein the SIP server compares configuration information contained in the first SIP INVITE message to configuration data stored in the database in order to determine the transmitted configuration data.

10. A Session Initiating Protocol (SIP) device, the device comprising:

a transmitter configured to transmit a configuration request message in an SIP INVITE message that includes a uniform resource identifier (URI) identifying an SIP server, the configuration request message initiating an SIP session;

a receiver configured to receive an SIP configuration message from the identified SIP server, the SIP configuration message including SIP device configuration data, the SIP device configuration data being in an Extensible Markup Language (XML) and specifying functionality of the device based on at least one of device location and device identification;

a processor in communication with the transmitter and receiver, the processor configured to;

process the SIP device configuration data, the processor initiating SIP device configuration based on processed SIP device configuration data; and

determine whether configuration is successful.

11. The SIP device of claim 10, wherein the transmitter is configured to transmit an acknowledgement message indicating whether a configuration is successful.

12. The SIP device of claim 11, wherein transmitting the acknowledgement message precedes closure of the SIP session.

13. The SIP device of claim 10, wherein the SIP device configuration data is based in part on at least one identification element corresponding to the SIP device.

17. The SIP device of claim 10, wherein the transmitted configuration request message includes configuration information for comparison to configuration data stored at an SIP server that receives the transmitted configuration request message.

18. The SIP device of claim 10, wherein the SIP device further periodically checks whether an OK message has been received within a specified period of time.

19. The SIP device of claim 18, wherein an administrator is notified of a configuration problem if the OK message has not been received within the specified time.

14. A method for configuring a Session Initiation Protocol (SIP) device, the method comprising:

storing SIP device configuration data;

receiving an SIP device configuration message in an SIP INVITE message that includes a uniform resource identifier (URI) identifying an SIP server that stores the SIP device configuration data;

establishing via the identified SIP server, an SIP session in response to the received configuration message; and

transmitting SIP device configuration data from the identified SIP server to an SIP device in response to establishing the SIP session, the SIP device configuration data being in an Extensible Markup Language (XML) and specifying functionality of the device based on at least one of device location and device identification.

15. The method of claim 14, wherein the SIP device configuration message includes identification data corresponding to the SIP device, the SIP device configuration data corresponding to the identification data.