Emergency services routing proxy cluster management

1. A cluster management system comprising:

a computer-readable memory storing executable instructions; and

one or more computer processors in communication with the computer-readable memory, wherein the one or more computer processors are configured to execute the executable instructions to at least:

receive first registration information from a first emergency services routing proxy node, the first registration information including a routing service identifier for an emergency service provider;

receive second registration information from a second emergency services routing proxy node for an emergency service provider, the second registration information including the routing service identifier, wherein the first emergency services routing proxy node and the second emergency services routing proxy node are included in a clustered emergency services routing proxy managed by a cluster manager, and wherein the clustered emergency services routing proxy is configured to route a call received from an upstream entity to a downstream entity via one of the first emergency services routing proxy node or the second emergency services routing proxy node;

receive node status information from nodes included in the clustered emergency services routing proxy associated with the routing service identifier, the nodes including the first emergency services routing proxy node and the second emergency services routing proxy node;

generate a service status message for the clustered emergency services routing proxy based on: (i) the received node status information for the nodes included in the clustered emergency services routing proxy associated with the routing service identifier, and (ii) a status policy; and

transmit the service status message to the upstream entity.

2. The system of claim 1 , wherein the downstream entity includes at least one of another emergency services routing proxy or a public safety answering point.

3. The system of claim 1 , wherein the routing service identifier and the identifier included in the call include a uniform resource identifier (URI).

4. The system of claim 1 , wherein the upstream entity includes at least one of a call originating device or another emergency services routing proxy.

5. The system of claim 1 wherein the one or more computer processors are configured to execute the executable instructions to at least identify a node to receive a call based on a load balancing policy.

6. The system of claim 1 , further comprising:

a first database server associated with the first emergency services routing proxy node, the first database server including routing policy data; and

a second database server associated with the second emergency services routing proxy node, the second database server including the routing policy data,

wherein the first database server and the second database server are configured to replicate routing policy data such that the routing policy data included in database servers is identical.

7. The system of claim 1 , wherein the one or more computer processors are configured to execute the executable instructions to at least:

identify the first emergency services routing proxy node and the second emergency services proxy node to provide the routing service for a call based at least in part on a correspondence between a service identifier included in the call and the routing service identifier; and

select one of the first emergency services routing proxy node and the second emergency services proxy node based on a comparison between the first registration information and the second registration information.

8. The system of claim 7 , wherein the call is a session initiation protocol call.

9. The system of claim 7 , wherein the call comprises mixed media data.

10. The system of claim 1 , wherein the node status information includes at least one of node load, a number of active calls for the node, node memory usage, node network bandwidth, and node routing time.

11. The system of claim 10 , wherein the status policy associates a service status with aggregated node status information values, and wherein the service status message includes the service status.

12. A method of managing a cluster of emergency services routing proxy nodes, the method comprising:

receiving, at an electronic device including a cluster management processor, first registration information from a first emergency services routing proxy node, the first registration information including a routing service identifier for an emergency service provider;

receiving second registration information from a second emergency service routing proxy node for an emergency service provider, the second registration information including the routing service identifier, wherein the first emergency services routing proxy node and the second emergency services routing proxy node are included in a clustered emergency services routing proxy managed by a cluster manager, and wherein the clustered emergency services routing proxy is configured to route a call received from an upstream entity to a downstream entity via one of the first emergency services routing proxy node or the second emergency services routing proxy node;

receiving node status information from nodes included in the clustered emergency services routing proxy associated with the routing service identifier, the nodes including the first emergency services routing proxy node and the second emergency services routing proxy node;

generating the service status message for the clustered emergency services routing proxy based on: (i) the received node status information for the nodes included in the clustered emergency services routing proxy associated with the routing service identifier, and (ii) a status policy; and

transmitting the service status message to an upstream entity.

13. The method of claim 12 , further comprising providing the call to the identified one of the first emergency services routing proxy node or the second emergency services proxy node.

14. The method of claim 12 , wherein the node status information includes at least one of node load, a number of active calls for the node, node memory usage, node network bandwidth, and node routing time.

15. The method of claim 12 , wherein the status policy associates a service status with aggregated node status information values, and wherein the service status message includes the service status.

16. The method of claim 12 , wherein the routing service identifier comprises a uniform resource identifier (URI).

17. The method of claim 12 , wherein identifying the first emergency services routing proxy node or the second emergency services proxy node to provide the routing service for the call comprises:

receiving a load balancing policy;

receiving node information from one or more of the first emergency services routing proxy node and the second emergency services proxy node; and

identifying the first emergency services routing proxy node or the second emergency services proxy node further based on the load balancing policy and the received node information.

18. The method of claim 12 , wherein a first routing service identifier is received from the first emergency services routing proxy node, the first routing service identifier associated with a first tenant of the first emergency services routing proxy node, and

wherein a second routing service identifier is received from the first emergency services routing proxy node, the second routing service identifier associated with a second tenant of the first emergency services routing proxy node.

19. The method of claim 12 further comprising:

identifying the first emergency services routing proxy node and the second emergency services proxy node to provide the routing service for a call based at least in part on a correspondence between a service identifier included in the call and the routing service identifier; and

selecting one of the first emergency services routing proxy node and the second emergency services proxy node based on a comparison between the first registration information and the second registration information.

20. A cluster management system comprising:

means for receiving registration information from a plurality of means for routing calls to a downstream entity, the calls received from an upstream entity, wherein registration information for a first means for routing calls includes a routing service identifier and registration information for a second means for routing calls includes the routing service identifier, and wherein the first means for routing calls and the second means for routing calls are included in a clustered emergency services routing proxy maintained by a cluster manager, and wherein the clustered emergency services routing proxy is configured to route a call from the upstream entity via one of the first means for routing calls or the second means for routing calls;

means for receiving node status information from nodes included in the clustered emergency services routing proxy associated with the routing service identifier, the nodes including the first emergency services routing proxy node and the second emergency services routing proxy node;

means for generating the service status message for the clustered emergency services routing proxy based on: (i) the received node status information for the nodes included in the clustered emergency services routing proxy associated with the routing service identifier, and (ii) a status policy; and

means for transmitting the service status message to an upstream entity.