# US 2016/0366093 A1 · Call routing between enhanced and legacy systems

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

- Number: US 2016/0366093 A1
- Document ID: US20160366093A1
- Status: Published application
- Kind: A1
- Application number: 14/739,205
- Filed: 2015-06-15
- Published: 2016-12-15
- Earliest claimed: 2015-06-15
- Assignees: Avaya Inc.
- Applicants: Avaya Inc.
- Inventors: Srinivasan Narayanan; Sanjog Narayan Kotnis
- Web page: https://patentgrep.com/patent/US20160366093A1

## CPC

- H04L 61/106: across networks, e.g. mapping telephone numbers to data network addresses
- H04M 3/42306: {Number translation services, e.g. premium-rate, freephone or vanity number services}
- H04M 7/0066: {Details of access arrangements to the networks (where the access arrangement is a PSTN/ISDN access H04M7/122)}
- H04M 7/0075: {Details of addressing, directories or routing tables}
- H04Q 3/66: Traffic distributors
- H04L 61/4594: Address books, i.e. directories containing contact information about correspondents (telephone directories in user terminals H04M1/27453)
- H04Q 2213/13097: Numbering, addressing
- H04Q 2213/13141: Hunting for free outlet, circuit or channel
- 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)
- H04Q: SELECTING (switches, relays, selectors H01H; wireless communication networks H04W)

## Abstract

Components of a telephone system often do not evolve in lock-step with other system improvements. For a variety of reasons, a component in a system may be operational to enable telephone calls utilizing a particular dialing format but be inoperable for calls utilizing a different format. Telephone number formats were initially numeric. The number of digits and format of the digits was often determined based on a country-specific dialing plan. Many countries have moved to more digits or alphanumeric formats (e.g., URIs). By capturing these enhanced addresses and generating an associated unique identifier, internal networks may utilize legacy numbering systems internally and, once the call reaches an edge device, route them based upon the enhanced address.

## Claims

### Claim 1

A system, comprising:
a contact store configured to maintain a translation record associating an address of an endpoint connected to a second network with a unique identifier used for addressing an endpoint connected to a first network that uses a different addressing scheme than the second network; and
an edge device with access to the contact store thereby enabling the edge device to intercept a call placed by the endpoint connected to the first network and directed toward the endpoint connected to the second network and address the call to the second endpoint connected to the second network even though the endpoint connected to the first network used the different addressing scheme to dial the endpoint connected to the second network.

### Claim 2 (depends on 1)

The system of claim 1, wherein the endpoint connected to the first network is further configured to, upon receiving a user input therein indicating initiation of a call to the unique identifier, access the translation record to retrieve the address of the endpoint connected to the second network utilizing the unique identifier, and route the call utilizing the address of the endpoint connected to the second network to the edge device.

### Claim 3 (depends on 1)

The system of claim 1, wherein the edge device is further configured to receive the call from the endpoint connected to the first network addressed to the unique identifier, access the address of the endpoint connected to the second network from the translation record, and route the call to the address of the endpoint connected to the second network.

### Claim 4 (depends on 1)

The system of claim 1, wherein the edge device, prior to the routing of the call to the address of the endpoint connected to the second network, receives a call from the endpoint connected to the second network, and creates the translation record utilizing the address of the endpoint connected to the second network.

### Claim 5 (depends on 4)

The system of claim 4, wherein the edge device is further configured to determine that at least one component of the first network is inoperable to process the call to the endpoint connected to the second network utilizing and, in response to the determination, causes the creation of the unique identifier.

### Claim 6 (depends on 4)

The system of claim 4, wherein the edge device is further configured to route the received call from the endpoint connected to the second network utilizing the unique identifier as the address of the endpoint connected to the second network.

### Claim 7 (depends on 5)

The system of claim 5, wherein the endpoint connected to the second network is configured to access the contact store to retrieve the address of the endpoint connected to the first network from the translation record accessed utilizing the unique identifier.

### Claim 8 (depends on 1)

The system of claim 1, wherein the second network comprises at least one component inoperable to accommodate calls utilizing an address having a format equivalent to the format of the address utilized by the endpoint connected to the first network.

### Claim 9 (depends on 8)

The system of claim 8, wherein the at least one component inoperable to accommodate calls to any address having a format equivalent to the format of the address utilized by the endpoint connected to the second network comprises a private branch exchange (PBX) logically located between the edge device and the endpoint connected to the first network.

### Claim 10 (depends on 8)

The system of claim 8, wherein:
the endpoint connected to the first network is configured to place a call to a new address utilizing the different addressing scheme and cause the unique identifier to be created, place the call via the at least one component inoperable to accommodate calls to any address utilizing the different addressing scheme, and cause the creation of the translation record comprising the new address and the unique identifier; and
the edge device, upon receiving via the at least one component inoperable to accommodate calls to any address utilizing the different addressing scheme, routes the call to the endpoint connected to the second network utilizing the new address retrieved from the contact store associated with the unique identifier.

### Claim 11

A method, comprising:
receiving at an endpoint connected to a first network, a call for an endpoint connected to a second network, the endpoint connected to the first network utilizing a first address scheme different from a second addressing scheme utilized by the endpoint connected to the second network;
creating a unique identifier associated with the address of the endpoint connected to the second network, wherein the at least one component required to route the call from the endpoint connected to the first network to an edge device at the edge of the first network utilizing the unique identifier;
storing a record comprising the unique identifier and the associated address of the endpoint connected to the second network in an accessible contact store.
receiving the call from the endpoint connected to the first network, by the at least one component required to route the call to the edge device is inoperable to route the call from the first endpoint utilizing the address of the endpoint connected to the second network, and routing the call from the address of the endpoint connected to the first network to the edge device utilizing the unique identifier;
receiving the call from the address of the endpoint connected to the first network, by the edge device, and accessing the address of the endpoint connected to the second network from the record in the contact store; and
routing the call from the edge device to the endpoint connected to the second network utilizing the accessed address of the endpoint connected to the second network from the contact store.

### Claim 12 (depends on 11)

The method of claim 11, further comprising determining that at least one component required to route the call from the address of the endpoint connected to the first network to the edge of the first network is inoperable to route the call utilizing the enhanced address.

### Claim 13 (depends on 11)

The method of claim 11, further comprising:
executing an application associated with the address of the endpoint connected to the first network; and
performing the step of creating the unique identifier by the application.

### Claim 14 (depends on 11)

The method of claim 11, further comprising:
receiving, at the edge device, a call from the endpoint connected to the second network; and
in response to receiving the call from the endpoint connected to the second network, performing the steps of creating the unique identifier and storing the record comprising the unique identifier and address of the endpoint connected to the second network in the contact store.

### Claim 15 (depends on 11)

The method of claim 11, further comprising, the step of creating a unique identifier by an application associated with the endpoint connected to the second network.

### Claim 16

A method, comprising:
receiving an call from the second endpoint from an second network at an edge device configured to logically connect the second network to an first network and facilitate calls therebetween;
routing the call from the second endpoint to an first endpoint identified by an address in a first format associated with the second endpoint;
accessing an address in a second format associated with the originator of the call from the second endpoint;
creating a unique identifier;
storing, in a contact store accessible upon the first network, a translation record associating the second address with the unique identifier; and
routing the call from the second endpoint to an first endpoint identified as the destination for the call from the second endpoint, utilizing the unique identifier.

### Claim 17 (depends on 16)

The method of claim 16, further comprising, presenting on a display associated with the first endpoint a caller identification indicia determined from the address in the second format.

### Claim 18 (depends on 16)

The method of claim 16, further comprising:
concluding the call from the second endpoint;
receiving a dialing input on the first endpoint;
determining the dialing input indicates a call from the first endpoint to the unique identifier;
routing the call from the first endpoint to the edge device;
accessing the address in the second format from the translation record associated with the unique identifier; and
routing the call from to the second endpoint utilizing the accessed address in the second format.

### Claim 19 (depends on 18)

The method of claim 18, wherein the first endpoint accesses the address in the second format.

### Claim 20 (depends on 16)

The method of claim 16, further comprising:
determining at least one component of the first network is inoperable to process calls utilizing the address in the second format; and
in response to the determining step, performing the step of creating the unique identifier and storing the translation record.
