US7450574B1 - IP telephony network using a configuration map for organizing sites in a tree-like hierarchy - Google Patents
IP telephony network using a configuration map for organizing sites in a tree-like hierarchy Download PDFInfo
- Publication number
- US7450574B1 US7450574B1 US10/424,491 US42449103A US7450574B1 US 7450574 B1 US7450574 B1 US 7450574B1 US 42449103 A US42449103 A US 42449103A US 7450574 B1 US7450574 B1 US 7450574B1
- Authority
- US
- United States
- Prior art keywords
- site
- network
- telephony
- server
- switch
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/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
- H04M7/0081—Network operation, administration, maintenance, or provisioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/60—Router architectures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/22—Arrangements for supervision, monitoring or testing
- H04M3/2254—Arrangements for supervision, monitoring or testing in networks
- H04M3/2263—Network management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/48—Routing tree calculation
Definitions
- the present invention relates to an IP telephony network using a configuration map for organizing sites in a tree-like hierarchy.
- the present invention specifically relates to the management of the addition to, removal from and movement of IP telephony elements within an IP telephony network.
- the present invention further relates to the locating of services and IP telephony elements within the IP telephony network.
- An IP telephony network may generally be composed of a number sites or “campuses.” Each site may have any number of interconnected servers, switches, extensions and/or trunks, all of which make up the network. Managing these sites, servers, switches, extensions and/or trunks (“IP telephony elements”) in an IP telephony network can be difficult and time and resource intensive, especially as the number of IP telephony elements expands. Managing a network requires the ability to, among other things, handle the addition, removal and movement of sites, servers, switches, extensions and/or trunks within an IP telephony network in such a manner so that services and IP telephony elements may be located when needed within the network.
- the mere addition of an extension to the network involves much greater administrative efforts and resources. Specifically, any time an extension is added to the network, all switches and servers in the network have to be updated to reflect the addition of the new extension. This requires significant memory, computational resources and administrative efforts to manage. Further, as the number of IP telephony elements in the network expands, the network does not easily scale.
- not all switches and servers have to be updated as a result of an addition of a new extension.
- locating an extension within the network requires use of router services located at a single (primary) server located at a headquarter site. Because all switches in the network have to consult the single primary server in order to locate an extension or trunk, the result is often a bottleneck at the headquarter site. Even worse, if the connection to the headquarter site is down or if the primary server is down, the network becomes inoperable since locator services are only provided by the single primary server located at the headquarter site. Further, as the number of IP telephony elements increases, the prior art implementation is not scalable since there is a limit to the number of switches a single primary server can support.
- the present invention overcomes the deficiencies and limitations of the prior art by providing an IP telephony network using a configuration map for organizing sites in a tree-like hierarchy.
- a configuration map for organizing sites in a tree-like hierarchy.
- having servers distributed throughout the network capable of providing services to the switches, extensions and trunks and accessible by tracing the tree-like hierarchy in a configuration map minimizes bottleneck in the system, makes the system scalable and more robust. For example, if the connection to the headquarter site is down, the rest of the system can still function because a large portion of the services can be provided locally. Also, if a local server is down, the configuration map with its organization of sites in a tree-like hierarchy can be traced to locate an alternate server to provide backup services (e.g., voicemail services, auto attendant services, etc.).
- backup services e.g., voicemail services, auto attendant services, etc.
- a further advantage of a configuration map for organizing sites in tree-like hierarchy is that it may be used to assign (or associate) a server to a switch in an efficient and easy-to-use manner. Specifically, when a switch is added to the network, a server needs to be assigned to it in order to service the needs of the extensions and trunks connected to the switch. By consulting the configuration map and tracing the tree-like hierarchy to find a server, the system will automatically locate a server that is located near the switch.
- IP telephony network system containing IP telephony elements that is easier, more efficient and less expensive to manage and to locate services and other IP telephony elements.
- FIG. 1 is a block diagram of an IP telephony network.
- FIG. 2 is a sample implementation of the IP telephony network of FIG. 1 .
- FIG. 3 is a block diagram illustrating an embodiment of a server.
- FIG. 4 is a block diagram illustrating modules in the main memory of a primary server at a headquarter site.
- FIG. 5 is a block diagram illustrating modules in the main memory of a server other than a primary server at a headquarter site.
- FIG. 6 is a block diagram illustrating a sample organization of sites in a tree-like hierarchy in a configuration map.
- FIG. 7 is an embodiment of a switch.
- FIG. 8 is an overview of a sample IP telephony network organized in a tree-like hierarchy.
- FIG. 9 is a diagram illustrating a sample addition of an extension to an IP telephony network.
- FIG. 10 is a diagram illustrating a sample addition of a trunk to an IP telephony network.
- FIG. 11 is a diagram illustrating a sample addition of a switch to an IP telephony network.
- FIG. 12 is a diagram illustrating a sample addition of a server to an IP telephony network.
- FIG. 13 is a diagram illustrating a sample addition of a site to an IP telephony network.
- FIG. 14 is a diagram illustrating a sample removal of an extension from an IP telephony network.
- FIG. 15 is a diagram illustrating a sample removal of a trunk from an IP telephony network.
- FIG. 16 is a diagram illustrating a sample removal of a switch from an IP telephony network.
- FIG. 17 is a diagram illustrating a sample removal of a server from an IP telephony network.
- FIG. 18 is a diagram illustrating a sample removal of a site from an IP telephony network.
- FIG. 19 is a diagram illustrating a sample movement of an extension within an IP telephony network.
- FIG. 20 is a diagram illustrating a sample movement of a trunk within an IP telephony network.
- FIG. 21 is a diagram illustrating a sample movement of a switch within an IP telephony network.
- FIG. 22 is a diagram illustrating a sample movement of a server within an IP telephony network.
- FIG. 23 is a diagram illustrating a sample movement of a site within an IP telephony network.
- FIG. 24 is a flow diagram of a preferred method for adding an extension to an IP telephony network.
- FIG. 25 is a flow diagram of a preferred method for adding a trunk to an IP telephony network.
- FIG. 26 is a flow diagram of a preferred method for adding a switch to an IP telephony network.
- FIG. 27 is a flow diagram of a preferred method for assigning a server to provide services to a switch.
- FIG. 28 is a flow diagram of a preferred method for adding a server to an IP telephony network.
- FIG. 30 is a flow diagram of a preferred method for removing an extension from an IP telephony network.
- FIG. 31 is a flow diagram of a preferred method for removing a trunk from an IP telephony network.
- FIG. 32 is a flow diagram of a preferred method for removing a switch from an IP telephony network.
- FIG. 33 removing a server from an IP telephony network.
- FIG. 34 is a flow diagram of a preferred method for updating a switch at the site of the removal of the server at the site.
- FIG. 35 is a flow diagram of a preferred method for updating all switches at a younger generation site of the removal of the server.
- FIG. 36 is a flow diagram of a preferred method for finding an alternate server to provide services to the switch.
- FIG. 37 is a flow diagram of a preferred method for removing a site from an IP telephony network.
- FIG. 38 is a flow diagram of a preferred method for moving an extension within an IP telephony network.
- FIG. 39 is a flow diagram of a preferred method for moving a trunk within an IP telephony network.
- FIG. 40 is a flow diagram of a preferred method for moving a switch within an IP telephony network.
- FIG. 41 is a flow diagram of a preferred method for moving a server within an IP telephony network.
- FIG. 42 is a flow diagram of a preferred method for moving a site within an IP telephony network.
- FIG. 43 is a flow diagram of a preferred method for locating a second extension or trunk from a first extension within an IP telephony network.
- FIG. 44 is a flow diagram of a preferred method for locating a second extension or trunk from a first trunk within an IP telephony network.
- FIG. 1 is a block diagram illustrating a sample IP telephony network 100 that has five sites, 105 , 110 , 115 , 120 and 125 , called “Headquarters,” “Campus 2 ,” “Campus 3 ,” “Campus 4 ” and “Campus 5 ” respectively.
- Each site 105 , 110 , 115 , 120 and 125 is connected to a network 130 which may be the Internet, WAN, LAN or other network known in the art.
- FIG. 2 is a sample implementation of the IP telephony network of FIG. 1 , shown in more detail.
- the headquarter site 105 for example, is composed of a server 205 , a primary server 210 , three switches 260 , 265 and 270 , seven telephone extensions 215 , 220 , 225 , 245 , 250 and 255 and three trunks 230 , 235 and 240 .
- Campus 3 115 is composed of no servers, two switches 275 and 280 and six telephone extensions 285 , 290 , 291 , 292 , 293 and 294 . Each extension or trunk is connected to a switch, and each site is coupled to the network.
- Each extension, trunk, switch and server is located at a site in the network.
- a site may or may not have a server, switch, trunk or extension located at the site.
- An extension need not be limited to a telephone extension.
- Extensions may include any type of extensions known in the IP telephony art including, but not limited to, the following types: user extension, auto attendant, backup auto attendant, voicemail extension, voicemail login extension, nightbell, paging, menu, workgroup, broadcast, distribution list, route point, audio messaging interface specification (“AMIS”) test mailbox, local auto attendant, local voicemail extension, local voicemail login extension and account code extension.
- AMIS audio messaging interface specification
- FIG. 3 is a block diagram illustrating an embodiment of a server 303 .
- a server 303 consists of a main memory 304 , a data storage device 307 , a processor 302 , a display 300 , a keyboard 322 , a cursor control 323 , a network controller 324 and an I/O (audio) device 325 , all coupled via and communicating over a bus 301 .
- FIG. 4 is a block diagram of some of the modules in the main memory 304 of a primary server 210 located at a headquarter site 105 in an IP telephony network 100 .
- the main memory 304 for the primary server 210 includes:
- other servers in the IP telephony network would not contain in their main memory 304 a configuration map or routines for adding, removing or moving an extension, trunk, switch, server or site. Instead, the other servers would contain modules for providing services, such as routing services provided by a router 505 , voicemail services provided by a voicemail module 510 and auto attendant services provided by an auto attendant module 515 .
- modules (not shown) that may be included in the main memory 304 of a server include, but are not limited to, modules for providing the following services: client/server internet services, event watch server services, java server services, voicemail message server services, voicemail port manager services, software telephony switch services, distributed routing services and telephony management server services.
- modules for providing the following services client/server internet services, event watch server services, java server services, voicemail message server services, voicemail port manager services, software telephony switch services, distributed routing services and telephony management server services.
- other modules (not shown) that may be included in the main memory 304 of the primary server 210 include: account code collection services, call accounting services, IP phone configuration services, IP phone display services, workgroup services and database management services. As shown in FIGS. 4 and 5 , each of the modules in the main memory 304 of a server is coupled to the other modules.
- FIG. 6 illustrates a sample organization of sites in an IP telephony network in a tree-like hierarchy in a configuration map. Note that, except for the headquarter site 105 located at the root of the tree-like hierarchy, each site has a parent site associated with it. A parent site is the site directly connected to a site, but located one level closer to the headquarter site 105 (i.e., at an older generation site). A site may also have associated with it one or more “child sites.” A child site is a site that is connected directly to the site at issue, but is located one level further away from the headquarter site 105 than the site at issue. For example, referring to FIG.
- Campus 2 110 has one parent site, which is the headquarter site 105 , and two children sites, which are Campus 4 120 and Campus 5 125 .
- the headquarter site 105 is an older generation site relative to Campus 2 110
- Campus 4 120 and Campus 5 125 are younger generation sites relative to Campus 2 110 . If Campus 5 125 had a child site, this child site would be a younger generation site relative to Campus 2 110 and Campus 5 125 .
- no site in the tree-like hierarchy may have as a child a site located at an older generation site or a site at the same generation.
- Campus 2 110 and Campus 3 115 are sites at the same generation (i.e., both are one level removed from or younger than the headquarter site). Hence, Campus 2 110 cannot be a child of Campus 3 115 . Nor can the headquarter site 105 be the child of Campus 2 110 or Campus 3 115 .
- FIG. 7 is a block diagram illustrating a preferred embodiment of a switch 700 .
- a switch has associated with it a server 705 and any number of backup servers 710 .
- a switch has associated with it a site map 715 .
- the site map 715 keeps track of the location of all extensions, trunks and switches at a site and may be used to locate any of these IP telephony elements at the site. Any type of extension or trunk may be connected to a switch.
- a switch may be a physical switch implemented in hardware or a virtual switch implemented in software on a server (sometimes also referred to as a “soft switch”).
- FIG. 8 is an overview of another sample IP telephony network, with the sites organized in a tree-like hierarchy. Note that this tree-like hierarchy is the preferred structure used by the configuration map to organize the sites. The sites need not be physically connected in a tree-like hierarchy.
- FIGS. 9-23 diagrammatically illustrate the effects of an addition, removal or movement of an IP telephony element in an IP telephony network in an embodiment of the invention. Additions are shown in bold and deletions in shaded, dotted lines. Modifications or updates to an item (such as the configuration map, routers, site maps, etc.) are indicated in bold as well.
- FIGS. 24-43 illustrate a preferred method for adding, removing and moving an extension, trunk, switch, server or site in an IP telephony network.
- FIGS. 44 and 45 illustrate a preferred method for locating a second extension or trunk from a first extension or trunk, respectively.
- FIG. 9 illustrates a preferred embodiment and FIG. 24 a preferred method for adding an extension 905 to an IP telephony network.
- a preferred method for adding an extension 905 to an IP telephony network begins by updating 2410 a configuration map 910 stored in a primary server 915 located at a headquarter site as to the location of the extension 905 , updating 2415 all servers 915 , 916 , 920 and 925 in the network as to the location of the extension 905 added and updating 2420 all switches 930 and 935 at the site 946 (“Campus 2 ”) in the network to which the extension 905 is added.
- a configuration map 910 stored in a primary server 915 located at a headquarter site as to the location of the extension 905
- updating 2415 all servers 915 , 916 , 920 and 925 in the network as to the location of the extension 905 added
- updating a server may be performed by updating a router located in the server.
- the configuration map need not be stored in a primary server located at a headquarter site. It can be stored anywhere in the network, provided the other IP telephony elements have access to it. Moreover, not all servers or switches need be updated as to the location of the extension 905 .
- all servers in the network and all switches at the site to which the extension is added are updated because updating a greater number of servers and/or switches helps to minimize bottleneck when locating other IP telephony elements or providing services to the IP telephony elements.
- updating a server and/or updating a switch helps to improve the robustness and reliability of the system.
- the routers in the servers would contain most (if not all) of the information stored in the configuration map, which information is required to locate IP telephony elements and services in the network.
- Updating a server in the network involves: (i) updating the server 925 associated with the extension 905 , the location of the associated server 925 determined by consulting the configuration map 910 (or, in an alternative embodiment, the site map in the switch 935 to which the extension 905 is connected); or (ii) updating a server (e.g., 915 , 916 or 920 ) other than a server associated with the extension 905 , the location of the server may be determined from the configuration map 910 (or, in an alternative embodiment, a router in a server, such as the router in server 915 ).
- updating 2420 a switch 930 or 935 at the site 946 involves updating a site map associated with the switch.
- the configuration map 910 (or, in an alternative embodiment, the site map for the switch 935 to which the extension 905 is connected) may be consulted in order to determine the location of the other switches 930 at the site 946 for purposes of updating 2420 .
- the configuration map 910 may also be used to determine a server in which to store a voicemail box associated with the extension 905 .
- the method of adding an extension 905 would further include determining from the configuration map 910 a server to host a voicemail box associated with the extension 905 by tracing the tree-like hierarchy, then storing the voicemail box at the server determined from the configuration map 910 .
- An advantage of this method of determining a server in which to store the voicemail box is that tracing the tree-like hierarchy from a given location in the tree tends to identify IP telephony elements (including servers, switches, etc.) that are located at or nearby the site. Hence, the result is a more efficient use and allocation of IP telephony elements within the network.
- FIG. 10 illustrates a preferred embodiment and FIG. 25 a preferred method for adding a trunk 1005 to an IP telephony network.
- the preferred method includes the steps of updating 2510 a configuration map 1010 stored in a primary server 1015 located at a headquarter site as to the location of the trunk 1005 , updating 2515 all servers 1015 , 1016 , 1020 and 1025 in the network as to the location of the trunk 1005 added and updating 2520 all switches 1030 , 1035 and 1040 in the network at the site 1045 of the trunk 1005 .
- Updating a server in the network may involve updating a server associated with the trunk 1005 (in the embodiment shown in FIG. 10 , server 1015 ), the location of the associated server 1015 determined by consulting the configuration map 1010 (or, in an alternative embodiment, the switch S HQ2 1035 to which the trunk 1005 is connected), or updating a server other than a server associated with the trunk 1005 (e.g., 1016 , 1020 or 1025 ), the location of such other server determined from the configuration map 1010 (or, in an alternative embodiment, a router in a server, such the router in server 1016 ).
- FIG. 11 shows a preferred embodiment and FIG. 26 a preferred method for adding a switch 1105 to an IP telephony network.
- a switch 1105 can be added to the network by providing 2610 the switch 1105 with a site map 1106 , assigning 2615 a server in the network to provide services to the switch 1105 (as shown in FIG. 11 , server 31 is assigned as server to switch S 34 ), assigning 2620 a backup server to provide services to the switch 1105 (as shown in FIG.
- servers HQ 1 and HQ 2 are assigned as backup servers), updating 2625 a configuration map 1110 stored in a primary server 1115 located at a headquarter site, updating 2630 all servers 1115 , 1116 , 1120 and 1125 in the network as to the location of the switch 1105 added and updating 2635 all switches 1130 , 1135 and 1140 in the network at the site 1145 of the switch 1105 .
- all site maps at a site are the same, and switches and servers have IP addresses that are stored in the configuration map 1110 and the site maps.
- FIG. 27 illustrates a preferred method for assigning 2615 a server to provide services to a switch involving determining 2705 from the configuration map 1110 (or, in an alternative embodiment, the site map for the switch) if a server is located at the site. If the IP telephony network 100 determines that a server is located at the site, the IP telephony network 100 assigns 2710 the server located at the site to provide services to the switch.
- the IP telephony network 100 determines 2715 from the configuration map (or, in an alternative embodiment, from any router in a server) an alternate site located at an older generation site by tracing the tree-like hierarchy, then assigns 2720 the server from the alternate site to the switch.
- assigning 2710 and 2720 a server to a switch involves storing information about the server in the memory of the switch so that the switch can access the server and services provided by such server.
- the server assigned to switch S 34 1105 is server 31 1120 since server 31 1120 is located at the same site 1145 as switch S 34 1105 . If, however, there were no servers at the site 1145 of switch S 34 (i.e., “Campus 3 ”), then the server assigned to switch S 34 1105 would be a server located at an older generation site relative to Campus 3 , in this case either servers HQ 1 or HQ 2 . Servers HQ 1 and HQ 2 are found by tracing the tree-like hierarchy in the configuration map or by consulting a router in a server in the network 100 .
- FIG. 12 shows a preferred embodiment and FIG. 28 a preferred method for adding a server 1205 to an IP telephony network by providing 2810 services and a router to the server 1205 , updating 2815 a configuration map 1210 as to the location of the server 1205 , updating 2820 all other servers 1215 , 1216 , 1220 and 1225 in the network as to the location of the server 1205 and updating 2825 all switches 1230 and 1235 at the site 1245 as to the location of the server 1205 , including site maps and server and backup server assignments associated with the switches 1230 and 1235 .
- the router provided 2810 to the server 1205 is identical to the router contained in the other servers 1215 , 1216 , 1220 and 1225 in the network. Referring to FIG. 12 , if Campus 4 1245 has connected to it younger generation sites, the IP telephony elements in these sites may need to be updated to reflect the addition of the server 1205 , particularly if these younger generation sites do not have servers at their own sites.
- FIG. 13 illustrates a preferred embodiment and FIG. 29 a preferred method for adding a site 1305 to an IP telephony network.
- the preferred method begins by receiving 2910 a parent site for the site 1305 from the system administrator or other source and updating 2915 a configuration map 1310 as to the location of the site 1305 .
- the location of the site 1305 is determined from the parent site provided by the system administrator. If site 1305 were added as a child of Campus 2 and the parent of Campus 5 , then the parent information for Campus 5 would need to be updated to reflect site 1305 as the new parent site.
- FIG. 14 shows a preferred embodiment and FIG. 30 a preferred method for removing an extension 1405 from an IP telephony network by updating 3110 a configuration map 1410 of the removal of the extension 1405 , updating 3115 all servers 1415 , 1416 , 1420 and 1425 in the network of the removal of the extension 1405 and updating 3120 all switches 1430 , 1435 and 1440 at the site 1445 of the removal of the extension 1405 .
- FIG. 15 illustrates a preferred embodiment and FIG. 31 a preferred method for removing a trunk 1505 from an IP telephony network by updating 3210 a configuration map 1510 of the removal of the trunk 1505 , updating 3215 all servers 1515 , 1516 , 1520 and 1525 in the network of the removal of the trunk 1505 and updating 3220 all switches 1530 , 1535 and 1540 at the site 1545 (“Headquarters”) of the removal of the trunk 1505 .
- FIG. 16 shows a preferred embodiment and FIG. 32 a preferred method for removing a switch 1605 from an IP telephony network.
- the preferred method begins by updating 3315 a configuration map 1610 of the removal of the switch 1605 and any IP telephony elements connected to the switch (e.g., extensions 1601 and 1602 ), updating 3320 all servers 1615 , 1616 , 1620 and 1625 in the network of the removal of the switch 1605 and any IP telephony elements connected to the switch and updating 3325 all other switches (as shown in FIG. 16 , only switch S 41 1630 ) at the site 1645 of the removal of the switch 1605 and any IP telephony elements connected to the switch.
- any IP telephony elements connected to the switch e.g., extensions 1601 and 1602
- updating 3320 all servers 1615 , 1616 , 1620 and 1625 in the network of the removal of the switch 1605 and any IP telephony elements connected to the switch updating 3325 all other switches (as shown in
- FIG. 17 illustrates a preferred embodiment and FIG. 33 a preferred method for removing a server 1705 from an IP telephony network.
- the preferred method begins by updating 3410 a configuration map 1710 of the removal of the server 1705 , updating 3415 all other servers 1715 , 1716 and 1725 in the network of the removal of the server 1705 , updating 3420 all switches 1730 , 1735 and 1740 at the site 1745 of the removal of the server 1705 and updating 3425 all switches located at a younger generation site in the tree-like hierarchy of the removal of the server 1705 .
- updating a switch involves updating the site map, server and backup server associated with the site.
- FIG. 34 illustrates a preferred method for updating a switch at a site of the removal of a server from the site by determining 3505 if the server was assigned to provide services to the switch. If the server was assigned to provide services to the switch, the IP telephony network 100 finds 3510 an alternate server to provide services to the switch and determines 3511 if the found alternate server was assigned to provide backup services to the switch at the site. If the found alternate server was assigned to provide backup services to the switch, the IP telephony network 100 finds 3520 an alternate server to provide backup services to the switch.
- the IP telephony network 100 determines 3515 if the server at the site was assigned to provide backup services to the switch at the site. If the server was assigned to provide backup services to the switch, the IP telephony network 100 finds 3520 an alternate server to provide backup services to the switch. In order to update a switch at the site, a site map associated with any of the switches at the site, a configuration map or a router in any server in the network may be used to locate each switch in the site for updating.
- FIG. 35 illustrates a preferred embodiment for updating 3425 switches located at a younger generation site in the tree-like hierarchy of the removal of the server by identifying 3605 all younger generation sites in the network by referring to the configuration map 1710 , and updating 3610 the switches and their associated servers and backup servers located at each identified younger generation site.
- FIG. 36 illustrates a preferred method for finding 3510 (or 3520 ) an alternate server to provide services (or backup services) to a switch by determining 3705 from the configuration map 1710 (or, in an alternative embodiment, a switch) if there are any other servers at the site. If the IP telephony network 100 determines 3705 that there are other servers at the site, the IP telephony network 100 assigns 3710 one of the other servers at the site to the switch. If the IP telephony network 100 determines 3705 there is more than one server at the site, the network 100 uses any algorithm known in the art to select one of the servers including random selection or selection based upon server load. If no other servers are at the site, the IP telephony network 100 determines 3715 from the configuration map 1710 the closest older generation site having a server by tracing the tree-like hierarchy, then assigns 3720 the server at the older generation site to the switch.
- Campus 3 1745 has no other servers after removal of server 31 1705 .
- the IP telephony network 100 traces the tree-like hierarchy in the configuration map and finds servers HQ 1 and HQ 2 at the headquarter site, which servers are then assigned to switches S 31 , S 32 and S 33 .
- FIG. 18 illustrates a preferred embodiment and FIG. 37 a preferred method for removing a site 1805 from an IP telephony network.
- the preferred method for removing a site 1805 from the network begins by updating 3815 a configuration map 1810 of the removal of the site 1805 and any IP telephony elements at the site 1805 and updating 3820 IP telephony elements (including sites along with their assigned parent site, servers and switches) located at a younger generation in the tree-like hierarchy of the removal of the site 1805 and any IP telephony elements at the site 1805 .
- updating 3820 may require updates to the servers only or to servers, switches and/or sites.
- the IP telephony network 100 of the present invention traces the tree-like hierarchy in the configuration map 1810 in order to determine which servers to assign to the switches at Campus 6 .
- FIG. 19 illustrates a preferred embodiment and FIG. 38 a preferred method for moving an extension 1905 from switch S 31 1930 in Campus 3 in the network to switch S 22 1935 in Campus 2 .
- the extension 1905 is moved from switch S 3 , 1930 in Campus 3 to switch S 22 1935 in Campus 2 by updating 3915 a configuration map 1910 of the movement of the extension 1905 from Campus 3 to Campus 2 and updating 3920 the IP telephony elements in the network of the movement of the extension 1905 .
- updating 3920 includes updating all site maps located at the sites of the first location (i.e., Campus 3 ) and the second location (i.e., Campus 2 ) and updating all servers in the network, specifically the router in the servers.
- not all switches nor all servers need be updated in the present invention.
- moving an extension 1905 from a first location to a second location can be accomplished by removing the extension 1905 from the first location and adding a new extension to the second location. Preferred methods for how to accomplish these two steps are described above.
- FIG. 20 illustrates a preferred embodiment and FIG. 39 a preferred method for moving a trunk from switch S HQ2 2030 in the headquarter site 2045 to switch S 22 2035 in Campus 2 in the network.
- the trunk is moved from switch SH HQ2 2030 in the headquarter site 2045 to switch S 22 2035 in Campus 2 by updating 4010 a configuration map 2010 of the removal of the trunk 2005 a from switch S HQ2 2030 at the headquarter site, updating 4020 a configuration map 2010 as to the addition of a new trunk 2005 b in the IP telephony network and updating 4025 the IP telephony elements in the network of the movement of the trunk from switch S HQ2 2030 in the headquarter site to switch S 22 2035 in Campus 2 2050 .
- updating 4025 the IP telephony elements includes updating all servers 2015 , 2016 , 2020 and 2025 in the network, specifically the router in a server, and updating the switches, particularly the site maps, located at the sites from which 2045 and to which 2050 the trunk is moved.
- moving a trunk from a first location to a second location need not be accomplished by removing the trunk from the first location and adding a new trunk to the second location. Instead, it is possible to use the same trunk, moving it from the first location to the second location. The details of how to accomplish this would be known to one of ordinary skill in the art in light of the prior discussion above.
- FIG. 21 illustrates a preferred embodiment and FIG. 40 a preferred method for moving a switch from Campus 4 to Campus 3 in the network.
- the switch is moved by updating 4115 a configuration map 2110 of the removal of the switch 2105 a and any IP telephony elements connected to the switch 2105 a from Campus 4 , providing 4125 the new switch 2105 b with a site map, assigning 4130 a server in the network to provide services for the new switch 2105 b , updating 4135 the configuration map 2110 as to the new switch 2105 b and the location of the new switch 2105 b and updating 4140 the IP telephony elements in the network of the movement of the switch from Campus 4 to Campus 3 .
- updating 4140 the IP telephony elements includes updating all servers in the network, specifically the routers and updating all switches, particularly the site maps, located at the sites from which 2145 and to which 2150 the switch is moved.
- moving a switch from a first location to a second location need not be accomplished by removing the switch from the first location and adding a new switch to the second location. Instead, it is possible to use the same switch. The details of how to accomplish this would be known to one of ordinary skill in the art in light of the discussion above.
- the server and/or backup servers for switches S 31 , S 32 and S 33 in Campus 3 , switches S HQ1 , S HQ2 and S HQ3 at the headquarter site, switches S 21 and S 22 in Campus 2 , switches S 41 and S 42 in Campus 4 , and switches S 51 and S 52 in Campus 5 have been updated in light of the movement of server 31 from Campus 3 to the headquarter site.
- the servers in the network specifically the router, have also been updated, particularly the routers, as shown in bold font in FIG. 22 .
- FIG. 23 illustrates a preferred embodiment and FIG. 42 a preferred method for moving a site 2305 from Campus 4 , a child site of Campus 2 , in the IP telephony network to Campus 4 , a child site of Campus 3 , in the network.
- the site 2305 is moved from child site of Campus 4 to a child site of Campus 3 by re-assigning 4315 a parent site (in the case illustrated in FIG.
- updating 4325 includes updating all the servers in the network, specifically the router in the servers.
- moving a site 2305 from a first location to a second location can be accomplished by removing the site 2305 from the first location and adding a new site to the second location.
- the details of how to accomplish this would be known to one of ordinary skill in the art in light of the discussions above.
- FIG. 43 illustrates a preferred method for locating a second extension or trunk from a first extension by determining 4405 from a site map of the switch to which the first extension is connected (or, in an alternative embodiment, from the configuration map) if the second extension or trunk is located at the same site as the first extension. If yes, the second extension or trunk, as applicable, has been located. If no, the IP telephony network 100 determines 4410 from a router in a server, either the server assigned to the switch to which the extension is connected or any other server in the network, (or, in an alternative embodiment, the configuration map) the location of the second extension or trunk, as applicable. As illustrated in FIG. 44 , the same method may be used to locate a second extension or trunk from a first trunk.
Abstract
Description
-
- (a) modules for providing services, such as routing services provided by a router 405 (sometimes referred to also as “distributed routing services”), conventional voicemail services provided by a
voicemail module 485 and conventional auto attendant services provided by anauto attendant module 490; - (b) a
configuration map 499; and - (c) routines for (i) adding an
extension 410,trunk 415,switch 420,server 425 andsite 430, (ii) removing anextension 435,trunk 440,switch 445,server 450 andsite 455, and (iii) moving anextension 460,trunk 465,switch 470,server 475 andsite 480.
- (a) modules for providing services, such as routing services provided by a router 405 (sometimes referred to also as “distributed routing services”), conventional voicemail services provided by a
Claims (13)
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/424,491 US7450574B1 (en) | 2003-04-25 | 2003-04-25 | IP telephony network using a configuration map for organizing sites in a tree-like hierarchy |
US12/247,798 US7924823B2 (en) | 2003-04-25 | 2008-10-08 | IP telephony network using a configuration map for organizing sites in a tree-like hierarchy |
US13/014,536 US8897172B1 (en) | 2003-04-25 | 2011-01-26 | IP telephony network using a configuration map for organizing sites in a tree-like hierarchy |
US14/455,704 US9641691B1 (en) | 2003-04-25 | 2014-08-08 | IP telephony network using a configuration map for organizing sites |
US15/581,256 US10230850B2 (en) | 2003-04-25 | 2017-04-28 | IP telephony network using a configuration map for organizing sites |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/424,491 US7450574B1 (en) | 2003-04-25 | 2003-04-25 | IP telephony network using a configuration map for organizing sites in a tree-like hierarchy |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/247,798 Continuation US7924823B2 (en) | 2003-04-25 | 2008-10-08 | IP telephony network using a configuration map for organizing sites in a tree-like hierarchy |
Publications (1)
Publication Number | Publication Date |
---|---|
US7450574B1 true US7450574B1 (en) | 2008-11-11 |
Family
ID=39940863
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/424,491 Active 2026-09-04 US7450574B1 (en) | 2003-04-25 | 2003-04-25 | IP telephony network using a configuration map for organizing sites in a tree-like hierarchy |
US12/247,798 Expired - Lifetime US7924823B2 (en) | 2003-04-25 | 2008-10-08 | IP telephony network using a configuration map for organizing sites in a tree-like hierarchy |
US13/014,536 Expired - Lifetime US8897172B1 (en) | 2003-04-25 | 2011-01-26 | IP telephony network using a configuration map for organizing sites in a tree-like hierarchy |
US14/455,704 Expired - Lifetime US9641691B1 (en) | 2003-04-25 | 2014-08-08 | IP telephony network using a configuration map for organizing sites |
US15/581,256 Expired - Lifetime US10230850B2 (en) | 2003-04-25 | 2017-04-28 | IP telephony network using a configuration map for organizing sites |
Family Applications After (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/247,798 Expired - Lifetime US7924823B2 (en) | 2003-04-25 | 2008-10-08 | IP telephony network using a configuration map for organizing sites in a tree-like hierarchy |
US13/014,536 Expired - Lifetime US8897172B1 (en) | 2003-04-25 | 2011-01-26 | IP telephony network using a configuration map for organizing sites in a tree-like hierarchy |
US14/455,704 Expired - Lifetime US9641691B1 (en) | 2003-04-25 | 2014-08-08 | IP telephony network using a configuration map for organizing sites |
US15/581,256 Expired - Lifetime US10230850B2 (en) | 2003-04-25 | 2017-04-28 | IP telephony network using a configuration map for organizing sites |
Country Status (1)
Country | Link |
---|---|
US (5) | US7450574B1 (en) |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070211868A1 (en) * | 2006-03-12 | 2007-09-13 | Netdevices, Inc. | Integrated System Providing Proxy Voice mail and Switching Functionality |
US20090034435A1 (en) * | 2003-04-25 | 2009-02-05 | Miller Thomas E | Ip telephony network using a configuration map for organizing sites in a tree-like hierarchy |
US8233381B1 (en) | 2008-12-23 | 2012-07-31 | Shoretel, Inc. | VoIP telephone system with distributed account codes |
US20140099922A1 (en) * | 2012-10-09 | 2014-04-10 | Cellco Partnership D/B/A Verizon Wireless | Interface for synchronizing automated replies between different messaging systems |
US8982902B1 (en) | 2012-06-28 | 2015-03-17 | Shoretel, Inc. | Backup server architecture in a VoIP system |
US9158525B1 (en) * | 2010-10-04 | 2015-10-13 | Shoretel, Inc. | Image upgrade |
US9674242B1 (en) | 2012-06-28 | 2017-06-06 | Shoretel, Inc. | Mesh conferencing |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106331997B (en) * | 2015-07-03 | 2019-06-14 | 普天信息技术有限公司 | A method of group membership registers to a group main control server when classification networking |
CN109587361B (en) * | 2018-12-27 | 2020-09-25 | 武汉职业技术学院 | Campus local area network VoIP system based on IBX1000 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6460025B1 (en) * | 1999-07-27 | 2002-10-01 | International Business Machines Corporation | Intelligent exploration through multiple hierarchies using entity relevance |
US20030012182A1 (en) * | 2001-07-12 | 2003-01-16 | Takayuki Sato | Management method for network device |
US20040143428A1 (en) * | 2003-01-22 | 2004-07-22 | Rappaport Theodore S. | System and method for automated placement or configuration of equipment for obtaining desired network performance objectives |
US7055107B1 (en) * | 2000-09-22 | 2006-05-30 | Wireless Valley Communications, Inc. | Method and system for automated selection of optimal communication network equipment model, position, and configuration |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5002286A (en) * | 1989-05-01 | 1991-03-26 | Wade Bill R | Hand projectile, method of manufacture and game played therewith |
CA2137385C (en) * | 1994-01-03 | 2000-01-25 | Gary Len Griffith | Switching arrangement for wireless terminals connected to a switch via a digital protocol channel |
US5541911A (en) * | 1994-10-12 | 1996-07-30 | 3Com Corporation | Remote smart filtering communication management system |
JP3507270B2 (en) * | 1997-02-20 | 2004-03-15 | 株式会社日立製作所 | Network management system, network equipment, network management method, and network management tool |
US7046778B2 (en) * | 2000-03-31 | 2006-05-16 | Coppercom, Inc. | Telecommunications portal capable of interpreting messages from an external device |
JP2004508772A (en) * | 2000-09-05 | 2004-03-18 | オペラックス アクチーボラゲット | Topology-aware resource manager and method in IP telephony systems |
US7107594B1 (en) * | 2002-06-27 | 2006-09-12 | Siebel Systems, Inc. | Method and system for providing a version-independent interface to a computer resource |
US6909992B2 (en) * | 2002-11-05 | 2005-06-21 | Sun Microsystems, Inc. | Automatically identifying replacement times for limited lifetime components |
US7450574B1 (en) | 2003-04-25 | 2008-11-11 | Shoretel, Inc. | IP telephony network using a configuration map for organizing sites in a tree-like hierarchy |
-
2003
- 2003-04-25 US US10/424,491 patent/US7450574B1/en active Active
-
2008
- 2008-10-08 US US12/247,798 patent/US7924823B2/en not_active Expired - Lifetime
-
2011
- 2011-01-26 US US13/014,536 patent/US8897172B1/en not_active Expired - Lifetime
-
2014
- 2014-08-08 US US14/455,704 patent/US9641691B1/en not_active Expired - Lifetime
-
2017
- 2017-04-28 US US15/581,256 patent/US10230850B2/en not_active Expired - Lifetime
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6460025B1 (en) * | 1999-07-27 | 2002-10-01 | International Business Machines Corporation | Intelligent exploration through multiple hierarchies using entity relevance |
US7055107B1 (en) * | 2000-09-22 | 2006-05-30 | Wireless Valley Communications, Inc. | Method and system for automated selection of optimal communication network equipment model, position, and configuration |
US20030012182A1 (en) * | 2001-07-12 | 2003-01-16 | Takayuki Sato | Management method for network device |
US7277935B2 (en) * | 2001-07-12 | 2007-10-02 | Allied Telesis Holdings K.K. | Management method for network device |
US20040143428A1 (en) * | 2003-01-22 | 2004-07-22 | Rappaport Theodore S. | System and method for automated placement or configuration of equipment for obtaining desired network performance objectives |
US7295960B2 (en) * | 2003-01-22 | 2007-11-13 | Wireless Valley Communications, Inc. | System and method for automated placement or configuration of equipment for obtaining desired network performance objectives |
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090034435A1 (en) * | 2003-04-25 | 2009-02-05 | Miller Thomas E | Ip telephony network using a configuration map for organizing sites in a tree-like hierarchy |
US7924823B2 (en) * | 2003-04-25 | 2011-04-12 | Shoretel Inc. | IP telephony network using a configuration map for organizing sites in a tree-like hierarchy |
US10230850B2 (en) | 2003-04-25 | 2019-03-12 | Mitel Networks, Inc. | IP telephony network using a configuration map for organizing sites |
US8897172B1 (en) | 2003-04-25 | 2014-11-25 | Shoretel, Inc. | IP telephony network using a configuration map for organizing sites in a tree-like hierarchy |
US9641691B1 (en) | 2003-04-25 | 2017-05-02 | Shoretel, Inc. | IP telephony network using a configuration map for organizing sites |
US20070211868A1 (en) * | 2006-03-12 | 2007-09-13 | Netdevices, Inc. | Integrated System Providing Proxy Voice mail and Switching Functionality |
US8233381B1 (en) | 2008-12-23 | 2012-07-31 | Shoretel, Inc. | VoIP telephone system with distributed account codes |
US9600268B1 (en) | 2010-10-04 | 2017-03-21 | Shoretel, Inc. | Image upgrade for devices in a telephony system |
US9158525B1 (en) * | 2010-10-04 | 2015-10-13 | Shoretel, Inc. | Image upgrade |
US10095507B1 (en) | 2010-10-04 | 2018-10-09 | Mitel Networks, Inc. | Image upgrade for devices in a telephony system |
US8982902B1 (en) | 2012-06-28 | 2015-03-17 | Shoretel, Inc. | Backup server architecture in a VoIP system |
US9674242B1 (en) | 2012-06-28 | 2017-06-06 | Shoretel, Inc. | Mesh conferencing |
US10506000B2 (en) | 2012-06-28 | 2019-12-10 | Mitel Networks, Inc. | Mesh conferencing |
US9060275B2 (en) * | 2012-10-09 | 2015-06-16 | Cellco Partnership | Interface for synchronizing automated replies between different messaging systems |
US20140099922A1 (en) * | 2012-10-09 | 2014-04-10 | Cellco Partnership D/B/A Verizon Wireless | Interface for synchronizing automated replies between different messaging systems |
Also Published As
Publication number | Publication date |
---|---|
US20170230508A1 (en) | 2017-08-10 |
US7924823B2 (en) | 2011-04-12 |
US20090034435A1 (en) | 2009-02-05 |
US10230850B2 (en) | 2019-03-12 |
US9641691B1 (en) | 2017-05-02 |
US8897172B1 (en) | 2014-11-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10230850B2 (en) | IP telephony network using a configuration map for organizing sites | |
US10824398B2 (en) | System and method for generating an application structure for an application in a computerized organization | |
KR100951257B1 (en) | Computerized system, method and program product for managing an enterprise storage system | |
US6839815B2 (en) | System and method for storage on demand service in a global SAN environment | |
US6789103B1 (en) | Synchronized server parameter database | |
EP0616713B1 (en) | Method and system for creating and maintaining multiple document versions in a data processing system library | |
US6868444B1 (en) | Server configuration management and tracking | |
EP1473872B1 (en) | Method and apparatus for discovering network devices | |
US8370470B2 (en) | System and method for managing server configurations | |
US6751627B2 (en) | Method and apparatus to facilitate accessing data in network management protocol tables | |
US7822766B2 (en) | Referential integrity across a distributed directory | |
US20080168566A1 (en) | Group access management system | |
WO2023024629A1 (en) | Service access across kubernetes clusters | |
US20180089243A1 (en) | Bloom filter index for device discovery | |
US20210281637A1 (en) | Management for a load balancer cluster | |
US6629105B1 (en) | Facilitating user administration of directory trees | |
US20040117621A1 (en) | System and method for managing resource sharing between computer nodes of a network | |
US20080320563A1 (en) | System and program product for associating event categorization and routing with security authorization roles | |
US7484243B2 (en) | Heterogenous domain-based routing mechanism for user authentication | |
CN114745757A (en) | Cluster switching method, device, equipment and medium | |
JPH10303963A (en) | Transmission system | |
US6281892B1 (en) | System and method of table-driven computer interface | |
US20080037445A1 (en) | Switch name, IP address, and hardware serial number as part of the topology database | |
KR20180120499A (en) | Method for synchronizing of database and private branch exchange for the same | |
US20210250263A1 (en) | Load balancing across bandwidth carrying circuits |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SHORELINE COMMUNICATIONS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MILLER, THOMAS E.;NADIMPALLI, KISHORE;TONOGAI, DALE C.;AND OTHERS;REEL/FRAME:014014/0280 Effective date: 20030424 |
|
AS | Assignment |
Owner name: SHORETEL, INC., CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:SHORELINE COMMUNICATIONS, INC.;REEL/FRAME:016448/0683 Effective date: 20040414 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: PAT HOLDER NO LONGER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: STOL); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
REFU | Refund |
Free format text: REFUND - SURCHARGE, PETITION TO ACCEPT PYMT AFTER EXP, UNINTENTIONAL (ORIGINAL EVENT CODE: R2551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: SILICON VALLEY BANK, CALIFORNIA Free format text: SECURITY INTEREST;ASSIGNOR:SHORETEL, INC.;REEL/FRAME:034038/0741 Effective date: 20141022 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
SULP | Surcharge for late payment |
Year of fee payment: 7 |
|
AS | Assignment |
Owner name: CITIZENS BANK, N.A., AS ADMINISTRATIVE AGENT, MASSACHUSETTS Free format text: SECURITY INTEREST;ASSIGNOR:SHORETEL, INC.;REEL/FRAME:043829/0711 Effective date: 20170925 Owner name: CITIZENS BANK, N.A., AS ADMINISTRATIVE AGENT, MASS Free format text: SECURITY INTEREST;ASSIGNOR:SHORETEL, INC.;REEL/FRAME:043829/0711 Effective date: 20170925 Owner name: SHORETEL, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:043993/0430 Effective date: 20170925 |
|
AS | Assignment |
Owner name: SHORETEL, INC., CALIFORNIA Free format text: MERGER AND CHANGE OF NAME;ASSIGNORS:SHORETEL, INC.;MITEL NETWORKS, INC.;REEL/FRAME:046857/0384 Effective date: 20171229 Owner name: MITEL NETWORKS, INC., ARIZONA Free format text: CHANGE OF NAME;ASSIGNOR:SHORETEL, INC.;REEL/FRAME:046957/0381 Effective date: 20171229 |
|
AS | Assignment |
Owner name: SHORETEL, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CITIZENS BANK, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:047713/0843 Effective date: 20181130 |
|
AS | Assignment |
Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:MITEL NETWORKS, INC.;REEL/FRAME:047909/0814 Effective date: 20181207 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:MITEL NETWORKS, INC.;REEL/FRAME:047988/0478 Effective date: 20181207 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLAT Free format text: SECURITY INTEREST;ASSIGNOR:MITEL NETWORKS, INC.;REEL/FRAME:047909/0814 Effective date: 20181207 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLAT Free format text: SECURITY INTEREST;ASSIGNOR:MITEL NETWORKS, INC.;REEL/FRAME:047988/0478 Effective date: 20181207 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |
|
AS | Assignment |
Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNORS:MITEL (DELAWARE), INC.;MITEL NETWORKS, INC.;MITEL COMMUNICATIONS, INC.;REEL/FRAME:061830/0760 Effective date: 20221018 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNORS:MITEL (DELAWARE), INC.;MITEL NETWORKS, INC.;MITEL COMMUNICATIONS, INC.;REEL/FRAME:061830/0715 Effective date: 20221018 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNORS:MITEL (DELAWARE), INC.;MITEL NETWORKS, INC.;MITEL COMMUNICATIONS, INC.;REEL/FRAME:061830/0643 Effective date: 20221018 |