SYSTEM AND METHOD FOR CONFIGURING AN IP TELEPHONY DEVICE

• US 20130114589A1
• Filed: 12/28/2012
• Published: 05/09/2013
• Est. Priority Date: 04/03/2001
• Status: Active Grant

• Current Assignee: RPX Corporation
• Original Assignee: VoxPath Networks, Inc (IPNav)
• Inventors: Fangman, Richard E., Preston, Jason D., RYON, Kenneth
• Granted Patent: US 8,804,705 B2
• Time in Patent Office: Days
• US Class Current: 370/352
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 61/2514 between local and global IP addresses
• CPC Class Codes: H04L 61/2517 using port numbers
• CPC Class Codes: H04L 61/2564 for a higher-layer protocol, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 61/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04L 61/5014 using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
• CPC Class Codes: H04L 61/5038 for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 65/1043 Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/65 Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04M 7/1285 Details of finding and selecting a gateway for a particular call

Abstract

A system and method for IP telephony are disclosed. The system includes an IP telephone (IPT) and a Service Gateway (SG). The SG receives an identifier, e.g., a vendor class identifier, included in a DHCP discover message from the IP telephone and determines if the identifier is valid. If so, the SG issues a DHCP offer comprising DHCP lease information to the IP telephone, including a range of port numbers assigned to the IP telephone based on the identifier, where the range of port numbers comprises ports which are not reserved for use by other IP protocols. The DHCP lease information includes information indicating operational software for the IP telephone which the IP telephone executes to enable IP communications. The SG mediates IP communications between the IP telephone and an IP device, where the IP telephone uses at least a subset of the range of port numbers to send or receive IP communications.

Claims

1. A method for configuring an IP telephone, comprising:

receiving an identifier from the IP telephone;

determining if the identifier is valid; and

if the identifier is valid, assigning a range of port numbers to the IP telephone based on the identifier, wherein the IP telephone is operable to use at least a subset of the range of port numbers to send or receive IP communications.

2. The method of claim 1, wherein said range of port numbers comprises ports which are not reserved for use by other IP protocols.

3. The method of claim 1, further comprising:

mediating IP communications between the IP telephone and an IP device, wherein the IP telephone uses at least a subset of the range of port numbers to send or receive said IP communications.

4. The method of claim 3, wherein said mediating the IP communications comprises:

receiving a data packet from the IP telephone,

performing a network address persistent port translation (NAPPT) on the data packet; and

sending the data packet to the IP device.

5. The method of claim 4,

wherein the data packet comprises a private source IP address, a source port number, and destination information associated with the IP device, wherein the private source IP address comprises a private IP address of the IP telephone, and wherein the source port number comprises a port number in the assigned range of port numbers;

and

wherein said performing a network address persistent port translation (NAPPT) on the data packet comprises changing the private source IP address to a public source IP address while leaving the source port number unchanged, and wherein the public source IP address and the source port number may be used to uniquely identify the IP telephone.

6. The method of claim 3, wherein said mediating the IP communications comprises:

receiving a data packet from the IP device;

performing a network address persistent port translation (NAPPT) on the data packet; and

sending the data packet to the IP telephone.

7. The method of claim 6,

wherein the data packet comprises a public destination IP address, a destination port number;

and source information associated with the IP device, wherein the destination port number comprises a port number in the assigned range of port numbers, and wherein the public destination IP address and the destination port number may be used to uniquely identify the IP telephone; and

wherein said performing a network address persistent port translation (NAPPT) on the data packet comprises using the public destination IP address and the destination port number to uniquely identify the IP telephone, and changing the public destination IP address to a private destination IP address while leaving the destination port number unchanged, wherein the private IP address comprises an IP address of the IP telephone.

8. The method of claim 1, wherein the identifier comprises a vendor class identifier.

9. The method of claim 1, wherein said determining comprises:

determining if a MAC ID for the IP telephone is valid.

10. The method of claim 1, wherein said identifier is comprised in a DHCP discover message, the method further comprising:

issuing a DHCP offer to the IP telephone if the identifier is determined to be valid, wherein the DHCP offer comprises DHCP lease information based on the validated identifier;

the IP telephone issuing a DHCP request in response to the issued DHCP offer;

storing the DHCP lease information in response to the issued DHCP request;

the IP telephone storing the DHCP lease information; and

the IP telephone enabling DHCP settings comprised in the DHCP lease information.

11. The method of claim 10, wherein said DHCP lease information includes the range of port numbers and information indicating operational software for the IP telephone, the method further comprising:

the IP telephone executing the indicated operational software to enable said IP communications.

12. The method of claim 10, wherein said DHCP lease information includes the range of port numbers and information indicating operational software for the IP telephone, the method further comprising:

the IP telephone issuing a request for the operational software;

providing the operational software to the IP telephone in response to the issued request; and

the IP telephone executing the provided operational software to enable said IP communications.

13. The method of claim 12, wherein said issuing the request for the operational software comprises issuing a read request to a file transfer server, wherein said file transfer server performs said providing the operational software to the IP telephone.

14. The method of claim 13, wherein the file transfer server comprises a TFTP (Trivial File Transfer Protocol) server.

15. The method of claim 1, wherein the range of port numbers comprises one or more port numbers.

16. A system for performing IP telephony, comprising:

a network;

an IP telephone;

a Service Gateway, wherein the Service Gateway is operable to couple to the IP telephone through the network;

wherein the IP telephone is operable to send an identifier to the Service Gateway;

wherein the Service Gateway is operable to;

receive an identifier from the IP telephone;

determine if the identifier is valid; and

if the identifier is valid, assign a range of port numbers to the IP telephone based on the identifier;

wherein the IP telephone is operable to use at least a subset of the range of port numbers to send or receive IP communications.

17. The system of claim 16, wherein said range of port numbers comprises ports which are not reserved for use by other IP protocols.

18. The system of claim 16, wherein the Service Gateway is further operable to mediate IP communications between the IP telephone and an IP device.

19. The system of claim 18, wherein, in mediating the IP communications the Service Gateway is operable to:

receive a data packet from the IP telephone,

perform a network address persistent port translation (NAPPT) on the data packet; and

send the data packet to the IP device.

20. The system of claim 19,

wherein the data packet comprises a private source IP address, a source port number, and destination information associated with the IP device, wherein the private source IP address comprises a private IP address of the IP telephone, and wherein the source port number comprises a port number in the assigned range of port numbers;

and

wherein said performing a network address persistent port translation (NAPPT) on the data packet comprises changing the private source IP address to a public source IP address while leaving the source port number unchanged, and wherein the public source IP address and the source port number may be used to uniquely identify the IP telephone.

21. The system of claim 18, wherein, in mediating the IP communications the Service Gateway is operable to:

receive a data packet from the IP device;

perform a network address persistent port translation (NAPPT) on the data packet; and

send the data packet to the IP telephone.

22. The system of claim 21,

wherein the data packet comprises a public destination IP address, a destination port number;

and source information associated with the IP device, wherein the destination port number comprises a port number in the assigned range of port numbers, and wherein the public destination IP address and the destination port number may be used to uniquely identify the IP telephone; and

wherein said performing a network address persistent port translation (NAPPT) on the data packet comprises using the public destination IP address and the destination port number to uniquely identify the IP telephone, and changing the public destination IP address to a private destination IP address while leaving the destination port number unchanged, wherein the private IP address comprises an IP address of the IP telephone.

23. The system of claim 16, wherein the identifier comprises a vendor class identifier.

24. The system of claim 16, wherein, in determining if the identifier is valid, the Service Gateway is operable to:

determine if a MAC ID for the IP telephone is valid.

25. The system of claim 16,

wherein said identifier is comprised in a DHCP discover message, wherein the Service Gateway is further operable to:

issue a DHCP offer to the IP telephone if the identifier is determined to be valid, wherein the DHCP offer comprises DHCP lease information based on the validated identifier;

wherein the IP telephone is further operable to;

issue a DHCP request in response to the issued DHCP offer;

store the DHCP lease information; and

enable DHCP settings comprised in the DHCP lease information; and

wherein the Service Gateway is further operable to;

store the DHCP lease information in response to the issued DHCP request.

26. The system of claim 25, wherein said DHCP lease information includes the range of port numbers and information indicating operational software for the IP telephone, wherein the IP telephone is further operable to:

execute the indicated operational software to enable said IP communications.

27. The system of claim 25, wherein said DHCP lease information includes the range of port numbers and information indicating operational software for the IP telephone,

wherein the IP telephone is further operable to:

issue a request for the operational software;

wherein the Service Gateway is further operable to;

provide the operational software to the IP telephone in response to the issued request; and

wherein the IP telephone is further operable to;

execute the provided operational software to enable said IP communications.

28. The system of claim 27, wherein, in issuing the request for the operational software, the IP telephone is operable to issue a read request to a file transfer server, wherein said file transfer server is operable to provide the operational software to the IP telephone.

29. The system of claim 28, wherein the file transfer server comprises a TFTP (Trivial File Transfer Protocol) server.

30. The system of claim 16, wherein the range of port numbers comprises one or more port numbers.

31. A memory medium, wherein the memory medium stores program instructions which are executable to perform:

receiving an identifier from the IP telephone;

determining if the identifier is valid; and

if the identifier is valid, assigning a range of port numbers to the IP telephone based on the identifier, wherein the IP telephone is operable to use at least a subset of the range of port numbers to send or receive IP communications.

32. The memory medium of claim 31, wherein said range of port numbers comprises ports which are not reserved for use by other IP protocols.

33. The memory medium of claim 31, wherein the program instructions are further executable to perform:

mediating IP communications between the IP telephone and an IP device, wherein the IP telephone uses at least a subset of the range of port numbers to send or receive said IP communications.

34. The memory medium of claim 33, wherein said mediating the IP communications comprises:

receiving a data packet from the IP telephone,

performing a network address persistent port translation (NAPPT) on the data packet; and

sending the data packet to the IP device.

35. The memory medium of claim 34,

wherein the data packet comprises a private source IP address, a source port number, and destination information associated with the IP device, wherein the private source IP address comprises a private IP address of the IP telephone, and wherein the source port number comprises a port number in the assigned range of port numbers;

and

wherein said performing a network address persistent port translation (NAPPT) on the data packet comprises changing the private source IP address to a public source IP address while leaving the source port number unchanged, and wherein the public source IP address and the source port number may be used to uniquely identify the IP telephone.

36. The memory medium of claim 33, wherein said mediating the IP communications comprises:

receiving a data packet from the IP device;

performing a network address persistent port translation (NAPPT) on the data packet; and

sending the data packet to the IP telephone.

37. The memory medium of claim 36,

wherein the data packet comprises a public destination IP address, a destination port number;

and source information associated with the IP device, wherein the destination port number comprises a port number in the assigned range of port numbers, and wherein the public destination IP address and the destination port number may be used to uniquely identify the IP telephone; and

wherein said performing a network address persistent port translation (NAPPT) on the data packet comprises using the public destination IP address and the destination port number to uniquely identify the IP telephone, and changing the public destination IP address to a private destination IP address while leaving the destination port number unchanged, wherein the private IP address comprises an IP address of the IP telephone.

38. The memory medium of claim 31, wherein the identifier comprises a vendor class identifier.

39. The memory medium of claim 31, wherein said determining comprises:

determining if a MAC ID for the IP telephone is valid;

40. The memory medium of claim 31, wherein said identifier is comprised in a DHCP discover message, wherein the program instructions are further executable to perform:

issuing a DHCP offer to the IP telephone if the identifier is determined to be valid, wherein the DHCP offer comprises DHCP lease information based on the validated identifier;

receiving a DHCP request from the IP telephone in response to the issued DHCP offer; and

storing the DHCP lease information in response to the issued DHCP request;

wherein said program instructions comprise IP telephone program instructions which are executable to;

store the DHCP lease information; and

enable DHCP settings comprised in the DHCP lease information.

41. The memory medium of claim 40, wherein said DHCP lease information includes the range of port numbers and information indicating operational software for the IP telephone, wherein the indicated operational software is executable by the IP telephone to enable said IP communications.

42. The memory medium of claim 40, wherein said DHCP lease information includes the range of port numbers and information indicating operational software for the IP telephone, wherein the program instructions are further executable to perform:

receiving a request for the operational software from the IP telephone;

providing the operational software to the IP telephone in response to the issued request; and

wherein the provided operational software is executable by the IP telephone to enable said IP communications.

43. The memory medium of claim 42,

wherein the IP telephone program instructions are executable to issue a read request to a file transfer server;

wherein said program instructions further comprise file transfer server program instructions executable to perform said providing the operational software to the IP telephone.

44. The memory medium of claim 43, wherein the file transfer server comprises a TFTP (Trivial File Transfer Protocol) server.

45. The memory medium of claim 31, wherein the range of port numbers comprises one or more port numbers.

46. A service gateway for use in an IP telephony network, wherein the service gateway is configured to:

couple one or more IP telephones to the network;

receive an identifier from an IP telephone;

determine if the identifier is valid; and

if the identifier is valid, assign a range of port numbers to the IP telephone based on the identifier;

wherein at least a subset of the range of port numbers are usable by the IP telephone to send or receive IP communications.

47. The service gateway of claim 46, wherein said range of port numbers comprises ports which are not reserved for use by other IP protocols.

48. The service gateway of claim 46, wherein the service gateway is further configured to mediate IP communications between the IP telephone and an IP device.

49. The service gateway of claim 48, wherein, in mediating the IP communications the service gateway is further configured to:

receive a data packet from the IP telephone,

perform a network address persistent port translation (NAPPT) on the data packet; and

send the data packet to the IP device.

50. The service gateway of claim 49,

wherein the data packet comprises a private source IP address, a source port number, and destination information associated with the IP device, wherein the private source IP address comprises a private IP address of the IP telephone, and wherein the source port number comprises a port number in the assigned range of port numbers;

and

wherein said performing a network address persistent port translation (NAPPT) on the data packet comprises changing the private source IP address to a public source IP address while leaving the source port number unchanged, and wherein the public source IP address and the source port number may be used to uniquely identify the IP telephone.

51. The service gateway of claim 48, wherein, in mediating the IP communications, the service gateway is further configured to:

receive a data packet from the IP device;

perform a network address persistent port translation (NAPPT) on the data packet; and

send the data packet to the IP telephone.

52. The service gateway of claim 51,

wherein the data packet comprises a public destination IP address, a destination port number;

and source information associated with the IP device, wherein the destination port number comprises a port number in the assigned range of port numbers, and wherein the public destination IP address and the destination port number may be used to uniquely identify the IP telephone; and

wherein said performing a network address persistent port translation (NAPPT) on the data packet comprises using the public destination IP address and the destination port number to uniquely identify the IP telephone, and changing the public destination IP address to a private destination IP address while leaving the destination port number unchanged, wherein the private IP address comprises an IP address of the IP telephone.

53. The service gateway of claim 46, wherein the identifier comprises a vendor class identifier.

54. The service gateway of claim 46,

wherein said identifier is comprised in a DHCP discover message, wherein the service gateway is further configured to:

issue a DHCP offer to the IP telephone if the identifier is determined to be valid, wherein the DHCP offer comprises DHCP lease information based on the validated identifier;

wherein the IP telephone is further operable to;

issue a DHCP request in response to the issued DHCP offer;

store the DHCP lease information; and

enable DHCP settings comprised in the DHCP lease information; and

wherein the service gateway is further configured to;

store the DHCP lease information in response to the issued DHCP request.

55. The service gateway of claim 54, wherein said DHCP lease information includes the range of port numbers and information indicating operational software for the IP telephone, wherein the IP telephone is further operable to:

execute the indicated operational software to enable said IP communications.

56. The service gateway of claim 54, wherein said DHCP lease information includes the range of port numbers and information indicating operational software for the IP telephone,

wherein the IP telephone is further operable to issue a request for the operational software;

wherein the service gateway is further operable to provide the operational software to the IP telephone in response to the issued request; and

wherein the IP telephone is further operable to execute the provided operational software to enable said IP communications.

57. The service gateway of claim 56, wherein, in issuing the request for the operational software, the IP telephone is operable to issue a read request to a file transfer server, wherein said file transfer server is operable to provide the operational software to the IP telephone.

58. The service gateway of claim 57, wherein the file transfer server comprises a TFTP (Trivial File Transfer Protocol) server.

59. The service gateway of claim 46, wherein the range of port numbers comprises one or more port numbers.