Abstract: Systems and methods for clustering emergency services routing proxies are provided. The described features allow a group of ESRPs running as individual servers or a group of virtual servers, to be referenced using a single URI. In one implementation, an emergency services routing proxy device includes an emergency services routing proxy node configured to route a call to a downstream entity, the call received from an upstream entity. The device further includes a cluster manager configured to receive registration information from the emergency services routing proxy node, the registration information including a routing service identifier. The cluster manager may be further configured to identify the emergency services routing proxy node for call routing based on a comparison of an identifier included in the call with the routing service identifier.

Abstract: Systems and methods for clustering emergency services routing proxies are provided. The described features allow a group of ESRPs running as individual servers or a group of virtual servers, to be referenced using a single URI. In one implementation, an emergency services routing proxy device includes an emergency services routing proxy node configured to route a call to a downstream entity, the call received from an upstream entity. The device further includes a cluster manager configured to receive registration information from the emergency services routing proxy node, the registration information including a routing service identifier. The cluster manager may be further configured to identify the emergency services routing proxy node for call routing based on a comparison of an identifier included in the call with the routing service identifier.

Abstract: Systems and methods for clustering emergency services routing proxies are provided. The described features allow a group of ESRPs running as individual servers or a group of virtual servers, to be referenced using a single URI. In one implementation, an emergency services routing proxy device includes an emergency services routing proxy node configured to route a call to a downstream entity, the call received from an upstream entity. The device further includes a cluster manager configured to receive registration information from the emergency services routing proxy node, the registration information including a routing service identifier. The cluster manager may be further configured to identify the emergency services routing proxy node for call routing based on a comparison of an identifier included in the call with the routing service identifier.

Abstract: Systems, apparatus, and methods for collaborative and distributed emergency multimedia data management are described. In one aspect, a system includes a packet data reception interface. The system further includes a rules engine coupled with the packet data reception interface and configured to select a processing profile for packet data received, the rules engine further configured to associate packet data received with stored packet data. The system also includes a policy engine coupled with the rules engine and configured to execute the processing profile for packet data received.

Abstract: Systems and methods for clustering emergency services routing proxies are provided. The described features allow a group of ESRPs running as individual servers or a group of virtual servers, to be referenced using a single URI. In one implementation, an emergency services routing proxy device includes an emergency services routing proxy node configured to route a call to a downstream entity, the call received from an upstream entity. The device further includes a cluster manager configured to receive registration information from the emergency services routing proxy node, the registration information including a routing service identifier. The cluster manager may be further configured to identify the emergency services routing proxy node for call routing based on a comparison of an identifier included in the call with the routing service identifier.

Abstract: Systems, apparatus, and methods for collaborative and distributed emergency multimedia data management are described. In one aspect, a system includes a packet data reception interface. The system further includes a rules engine coupled with the packet data reception interface and configured to select a processing profile for packet data received, the rules engine further configured to associate packet data received with stored packet data. The system also includes a policy engine coupled with the rules engine and configured to execute the processing profile for packet data received.

Abstract: Systems and methods for clustering emergency services routing proxies are provided. The described features allow a group of ESRPs running as individual servers or a group of virtual servers, to be referenced using a single URI. In one implementation, an emergency services routing proxy device includes an emergency services routing proxy node configured to route a call to a downstream entity, the call received from an upstream entity. The device further includes a cluster manager configured to receive registration information from the emergency services routing proxy node, the registration information including a routing service identifier. The cluster manager may be further configured to identify the emergency services routing proxy node for call routing based on a comparison of an identifier included in the call with the routing service identifier.

Abstract: Systems, apparatus, and methods for collaborative and distributed emergency multimedia data management are described. In one aspect, a system includes a packet data reception interface. The system further includes a rules engine coupled with the packet data reception interface and configured to select a processing profile for packet data received, the rules engine further configured to associate packet data received with stored packet data. The system also includes a policy engine coupled with the rules engine and configured to execute the processing profile for packet data received.

Abstract: Systems and methods for clustering emergency services routing proxies are provided. The described features allow a group of ESRPs running as individual servers or a group of virtual servers, to be referenced using a single URI. In one implementation, an emergency services routing proxy device includes an emergency services routing proxy node configured to route a call to a downstream entity, the call received from an upstream entity. The device further includes a cluster manager configured to receive registration information from the emergency services routing proxy node, the registration information including a routing service identifier. The cluster manager may be further configured to identify the emergency services routing proxy node for call routing based on a comparison of an identifier included in the call with the routing service identifier.

Abstract: Systems and methods for clustering emergency services routing proxies are provided. The described features allow a group of ESRPs running as individual servers or a group of virtual servers, to be referenced using a single URI. In one implementation, an emergency services routing proxy device includes an emergency services routing proxy node configured to route a call to a downstream entity, the call received from an upstream entity. The device further includes a cluster manager configured to receive registration information from the emergency services routing proxy node, the registration information including a routing service identifier. The cluster manager may be further configured to identify the emergency services routing proxy node for call routing based on a comparison of an identifier included in the call with the routing service identifier.

Abstract: Systems and methods for emergency call-center session routing in an all-active cluster formation are provided. Each node in a cluster receives sessions through load balanced distribution. Nodes in the cluster may be configured to use a common database. The database is synchronized across the cluster ensuring that data is accessible by any node in the cluster. Session state is maintained in the database, such that any session can be managed by any node in the cluster.

Abstract: Systems, apparatus, and methods for collaborative and distributed emergency multimedia data management are described. In one aspect, a system includes a packet data reception interface. The system further includes a rules engine coupled with the packet data reception interface and configured to select a processing profile for packet data received, the rules engine further configured to associate packet data received with stored packet data. The system also includes a policy engine coupled with the rules engine and configured to execute the processing profile for packet data received.