# US 2008/0186963 A1 · Method and system for supporting cross cluster extension mobility in internet-protocol telephony

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2008/0186963 A1
- Document ID: US20080186963A1
- Status: Published application
- Kind: A1
- Application number: 11/675,739
- Filed: 2007-02-16
- Published: 2008-08-07
- Earliest claimed: 2007-02-01
- Assignees: Cisco Technology, Inc.
- Inventors: Atul Trasi; Daniel Scott Keller; Susan Marie Sauter; Ho Bao; Chunfeng Huang
- Web page: https://patentgrep.com/patent/US20080186963A1

## CPC

- H04L 67/306: User profiles
- H04L 65/1046: Call controllers; Call servers
- H04L 65/1063: Application servers providing network services (systems providing special services to telephonic subscribers H04M3/42)
- H04L 65/1094: Inter-user-equipment sessions transfer or sharing
- H04L 65/1096: Supplementary features, e.g. call forwarding or call holding (systems providing special services or facilities to telephony subscribers H04M3/42)
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04L 69/18: Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
- H04M 7/0075: {Details of addressing, directories or routing tables}
- H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP]
- H04W 8/02: Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W 80/04: Network layer protocols, e.g. mobile IP [Internet Protocol]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A method to support cross cluster extension mobility (CCEM) in a communication network, which includes a plurality of clusters, each of the plurality of clusters including a call manager, the method includes receiving a request for cross cluster extension mobility from a user on a first telephony device located in a first cluster; adding a second telephony device in a home cluster for the user, only if the first cluster is different from the home cluster. The method further includes performing extension mobility login for the user on the first telephony device; and configuring a Trivial File Transfer Protocol (TFTP) service parameter of the call manager in the first cluster.

## Claims

### Claim 1

A method to support cross cluster extension mobility (CCEM) in a communication network, which includes a plurality of clusters, each of the plurality of clusters including a call manager, the method comprising:
receiving a request for cross cluster extension mobility from a user on a first telephony device located in a first cluster;
adding a second telephony device in a home cluster for the user, only if the first cluster is different from the home cluster;
performing extension mobility login for the user on the first telephony device; and
configuring a Trivial File Transfer Protocol (TFTP) service parameter of the call manager in the first cluster.

### Claim 2 (depends on 1)

The method of claim 1, in which receiving a request for cross cluster extension mobility from a user on a first telephony device located in a first cluster comprises receiving a user ID and a PIN from the user.

### Claim 3 (depends on 2)

The method of claim 2, in which adding a second telephony device in a home cluster for the user comprises determining the home cluster using the user ID.

### Claim 4 (depends on 1)

The method of claim 1, in which adding a second telephony device in a home cluster for the user comprises:
creating a configuration file for the second telephony device;
storing the configuration file in a local TFTP path of the call manager in the home cluster.

### Claim 5 (depends on 1)

The method of claim 1, in which adding a second telephony device in a home cluster further comprises:
obtaining a Media Access Control (MAC) address and a phone type for the first telephony device;
adopting a device name for the second telephony device, such that the device name of the second telephony device is the same as an original device name for the first telephony device;
replacing the original device name for the first telephony device with some other name.

### Claim 6 (depends on 1)

The method of claim 1, in which replacing the original device name for the first telephony device with some other name comprises replacing first three characters of the original device name for the first telephony device with ‘CCC’.

### Claim 7 (depends on 1)

The method of claim 1, in which configuring a TFTP service parameter of the call manager in the first cluster comprises:
disabling caching of configuration files in the call manager;
setting an alternate file location to include an IP address and a TFTP path for all other clusters in the communication network.

### Claim 8 (depends on 1)

The method of claim 1, further comprising configuring the first telephony device and the second telephony device to support extension mobility.

### Claim 9 (depends on 1)

The method of claim 1, further comprising performing extension mobility logout.

### Claim 10 (depends on 9)

The method of claim 9, in which performing extension mobility logout comprises removing the second telephony device from the home cluster, if any.

### Claim 11 (depends on 10)

The method of claim 10, in which removing the second telephony device from the home cluster comprises renaming the first telephony device by replacing a name for the first telephony device with a name for the second telephony device, the name for the second telephony device being an original name for the first telephony device.

### Claim 12

Logic encoded in one or more tangible media for execution and when executed operable to:
receive a request for cross cluster extension mobility from a user on a first telephony device located in a first cluster;
add a second telephony device in a home cluster for the user, only if the first cluster is different from the home cluster;
perform extension mobility login for the user on the first telephony device; and
configure a TFTP service parameter of the call manager in the first cluster.

### Claim 13 (depends on 12)

The logic of claim 12, in which adding a second telephony device in a home cluster for the user comprises determining the home cluster using the user ID.

### Claim 14 (depends on 12)

The logic of claim 12, in which adding a second telephony device in a home cluster further comprises:
obtaining a MAC address and a phone type for the first telephony device;
adopting a device name for the second telephony device, such that the device name of the second telephony device is the same as an original device name for the first telephony device;
replacing the original device name for the first telephony device with some other name.

### Claim 15 (depends on 12)

The logic of claim 12, in which configuring a TFTP service parameter of the call manager in the first cluster comprises:
disabling caching of configuration files in the call manager;
setting an alternate file location to include an IP address and a TFTP path for all other clusters in the communication network.

### Claim 16 (depends on 12)

The logic of claim 12, further operable to perform extension mobility logout.

### Claim 17

A system for supporting cross cluster extension mobility (CCEM) in a communication network, which includes a plurality of clusters, each of the plurality of clusters including a call manager, the system comprising:
a first telephony device in a first cluster, the telephony device including:
a user interface operable to receive a user input;
a network interface couple to the user interface and operable to communicate the user input over the communication network;
an application server coupled to the communication network, the application server including:
a network interface operable to receive the user input from the first telephony device;
a CCEM service application coupled to the network interface, the CCEM service application operable to perform extension mobility login for the user on the first telephony device; and
a call manager in the first cluster, the call manager including:
a network interface;
a TFTP service, the TFTP service is configurable to include alternate file location for all other clusters in the communication network.

### Claim 18 (depends on 17)

The system of claim 17, in which the first telephony device is further operable to support extension mobility.

### Claim 19 (depends on 17)

The system of claim 17, in which the first telephony device is an IP phone.

### Claim 20 (depends on 17)

The system of claim 17, in which the CCEM service application is further operable to add a second telephony device in a home cluster for the user, only if the first cluster is different from the home cluster.

### Claim 21 (depends on 17)

The system of claim 17, in which the CCEM service application is further operable to perform cross cluster extension mobility logout.
