Abstract: Peering partners register with a peering grid for direct broadband routing of call offers. The peering grid terminates call offers on behalf of peering partners, collecting call detail records, summarizing termination usage, and calculating a payment to be provided to the peering partner in return for using the services of the peering grid. A call detail record may be generated for the peering partner, which may include a market value of call traffic, a variable cost of the call traffic, and a determined compensation amount. The market value is based on revenue for terminations of the call traffic from the peering grid, the variable cost is a function of sharing the market value between the peering grid and the peering partner, and the compensation amount due is a function of the variable cost.

Abstract: A routing engine functions to respond to a request for routing options for a communication session from a querying node by providing a list of routing options. The original request includes signaling information that is utilized by the routing engine to determine a preliminary list of routing options that identifies vendors capable of handling the communication session. Pre-defined routing definitions may be applied to alter the list of vendors as identified in the preliminary list. Filtering processes may be applied to remove undesirable vendors from the preliminary routing options, resulting in a list of routing options for the communication session. The preliminary list may be ordered according to some parameter, and when a filtering process is applied the process may end upon reaching a first non-compliant vendor.

Abstract: A peering grid component operates to facilitate connections of call traffic in a peering grid comprised of customers interconnected with peering partners. A switch is configured to receive call traffic from a customer, and a routing engine is configured to analyze parameters of the call traffic to classify the call traffic as wireless or wire-line traffic. The classification of the call traffic is achieved through the provision of updated wireless routing information accessed by the routing engine. With the classification, the switch, for wireless traffic, accepts and transmits the call traffic at a wireless rate to a peering partner via a connection to the peering partner; and, for wire-line traffic, either transmits the call traffic back to the customer or accepts the call traffic for transmission at a wire-line rate. The wire-line rate is different than the wireless rate, and the associated rates are charged to the customer.

Abstract: A routing engine functions to respond to a request for routing options for a communication session from a querying node by providing a list of routing options. The original request includes signaling information that is utilized by the routing engine to determine a preliminary list of routing options that identifies vendors capable of handling the communication session. Pre-defined routing definitions may be applied to alter the list of vendors as identified in the preliminary list. Filtering processes may be applied to remove undesirable vendors from the preliminary routing options, resulting in a list of routing options for the communication session. The preliminary list may be ordered according to some parameter, and when a filtering process is applied the process may end upon reaching a first non-compliant vendor.

Abstract: The present invention relates to systems and methods for performing queries in a cascading logic routing grid comprised of an array of interconnected nodes and at least one root node. At a first root node, one or more adjacent nodes are selected to process a query. The selection is based on the capabilities of the nodes and parameters of the query. Once the nodes are selected, a query is transmitted from the first root node to at least one of the one or more selected nodes. Upon completion of processing the query, a response is received at the first root node from at least one of the one or more selected nodes. The response comprises specifications for routing data. Based on the specifications for routing data received in the response, routing instructions are formed at the first root node.

Abstract: The present invention relates to systems and methods for detecting and terminating a looping condition occurring in a telecommunications network comprising receiving a call offer comprising receiving call identification data associated with the call offer at a switching component, querying a looping engine using the call identification data to detect a looping condition, identifying a number of occurrences of the call identification data within a predetermined time frame, comparing the number of occurrences against a predetermined count, and returning a message to the switching component based on the comparison, the message indicating whether a looping condition exists in the telecommunications network.

Abstract: A peering grid component operates to facilitate connections of call traffic in a peering grid comprised of customers interconnected with peering partners. A switch is configured to receive call traffic from a customer, and a routing engine is configured to analyze parameters of the call traffic to classify the call traffic as wireless or wire-line traffic. The classification of the call traffic is achieved through the provision of updated wireless routing information accessed by the routing engine. With the classification, the switch, for wireless traffic, accepts and transmits the call traffic at a wireless rate to a peering partner via a connection to the peering partner, and, for wire-line traffic, either transmits the call traffic back to the customer or accepts the call traffic for transmisson at a wire-line rate. The wire-line rate is different than the wireless rate, and the associated rates are charged to the customer.

Abstract: A multi-layer stack platform is provided for cloud communication connections and services between devices. The system includes three or more layers, including a directory component, an applications component, and a peering component. An interconnection component may also be provided for communication between the applications component and the peering component. The components operate to provide communication services, such as sessions, according to the functionality of a selected application by adhering to device, user, and routing rules and preferences. The device, user, and routing rules and preferences are maintained in and processed by the directory component. The applications component receives communication session requests and accesses corresponding application scripts to perform the requested session. The peering component receives the device, user, and routing rules and preferences, and establishes connection between devices based on the rules and preferences as defined by the directory component.

Abstract: A multi-layer stack platform is provided for cloud communication connections and services between devices. The system includes three or more layers, including a directory component, an applications component, and a peering component. An interconnection component may also be provided for communication between the applications component and the peering component. The components operate to provide communication services, such as sessions, according to the functionality of a selected application by adhering to device, user, and routing rules and preferences. The device, user, and routing rules and preferences are maintained in and processed by the directory component. The applications component receives communication session requests and accesses corresponding application scripts to perform the requested session. The peering component receives the device, user, and routing rules and preferences, and establishes connection between devices based on the rules and preferences as defined by the directory component.

Abstract: Peering partners register with a peering grid for direct broadband routing of call offers. The peering grid terminates call offers on behalf of peering partners, collecting call detail records, summarizing termination usage, and calculating a payment to be provided to the peering partner in return for using the services of the peering grid.

Abstract: The present invention relates to systems and methods for detecting and terminating a looping condition occurring in a telecommunications network comprising receiving a call offer comprising receiving call identification data associated with the call offer at a switching component, querying a looping engine using the call identification data to detect a looping condition, identifying a number of occurrences of the call identification data within a predetermined time frame, comparing the number of occurrences against a predetermined count, and returning a message to the switching component based on the comparison, the message indicating whether a looping condition exists in the telecommunications network.

Abstract: A call routing decision for connecting a call between source and target devices is based on the traffic type (e.g., facsimile, modem, voice). In some implementations, the traffic type is determined and stored (e.g., in a billing record). The traffic type can be used to connect, block or reroute subsequent calls of the same traffic type.

Abstract: Peering partners register with a peering grid for direct broadband routing of call offers. The peering grid terminates call offers on behalf of peering partners, collecting call detail records, summarizing termination usage, and calculating a payment to be provided to the peering partner in return for using the services of the peering grid. A call detail record may be generated for the peering partner, which may include a market value of call traffic, a variable cost of the call traffic, and a determined compensation amount. The market value is based on revenue for terminations of the call traffic from the peering grid, the variable cost is a function of sharing the market value between the peering grid and the peering partner, and the compensation amount due is a function of the variable cost.

Abstract: A process for routing a call between an ingress point and an egress point is based on an identifier, such as a number, assigned to the egress point and a registry in which identifiers are stored. A routing component receives the call from the ingress point and consults the registry to determine if an entry with the identifier of the egress point being called is stored therein. If a corresponding entry exists, a delivery route for routing the call to the egress point is determined. The delivery route may be a first path to the egress point if available. If the first path is not available, one or more secondary paths are determined, where one is utilized for sending the call to the egress point. The utilized secondary path may be the most optimal path for the call based upon established preferences and call features.

Abstract: Peering partners register with a peering network for direct broadband routing of call offers. The peering network terminates call offers on behalf of peering partners, collecting call detail records, summarizing termination usage, and calculating a payment to be provided to the peering partner in return for using the services of the peering network.

Abstract: When a call offer is received by a telecommunications peering network destined for a telephone number maintained within a peering database, the telecommunications peering network attempts to route the call directly to the peering partner telecommunications (e.g., broadband, voice over internet protocol, etc.) equipment. If the route fails with a corresponding destination unreachable failure code, the telecommunications peering network can attempt to determine whether or not the telephone number has been ported to a different provider. If the telecommunications peering network determines that the telephone number has been ported, the telecommunications peering network removes the telephone number from the peering database.

Abstract: When a call offer is received by a telecommunications peering network destined for a telephone number maintained within a peering database, the telecommunications peering network attempts to route the call directly to the peering partner telecommunications (e.g., broadband, voice over internet protocol, etc.) equipment. If the route fails with a corresponding destination unreachable failure code, the telecommunications peering network can attempt to determine whether or not the telephone number has been ported to a different provider. If the telecommunications peering network determines that the telephone number has been ported, the telecommunications peering network removes the telephone number from the peering database.

Abstract: A multi-layer stack platform is provided for cloud communication connections and services between devices. The system includes three or more layers, including a directory component, an applications component, and a peering component. An interconnection component may also be provided for communication between the applications component and the peering component. The components operate to provide communication services, such as sessions, according to the functionality of a selected application by adhering to device, user, and routing rules and preferences. The device, user, and routing rules and preferences are maintained in and processed by the directory component. The applications component receives communication session requests and accesses corresponding application scripts to perform the requested session. The peering component receives the device, user, and routing rules and preferences, and establishes connection between devices based on, the rules and preferences as defined by the directory component.

Abstract: A unified communication system is disclosed that allows a variety of end point types to participate in a communication event using a common, unified communication system. In some implementations, a calling party interacts with a client application residing on an endpoint to make a communication request to another endpoint. A communication event manager residing in the unified communication system selects a script from a repository of scripts based on the communication event and the capabilities of the endpoints. A communication event execution engine receives a user profile associated with at least one of the endpoints. The user profile can be configured by the user to describe the user's preferences for how the communication should be processed by the unified communication system.