Abstract: Techniques for configuring shared routing tables for network devices are provided. In some embodiments, a shared routing context is configured to include common routes across several local routing contexts. When a first packet is received at a first local routing context that is to be routed using one of the common routes, NAT operations may be performed on the first packet and then the shared routing context is used to process the first packet. Similarly, when a second packet is received at a second local routing context that is to be routed using the same common route, NAT operations may be performed on the second packet and then the shared routing context is used to process the second packet.

Abstract: Techniques for implementing history-based connection-server affinity on a network load balancer are provided. In one set of embodiments, the network load balancer can receive a network packet destined for a service, where the service is associated with a plurality of servers, and where the packet is part of a network connection between a client device and one of the plurality of servers. The network load balancer can further compute, using a portion of the packet, a bucket identifier of a bucket for the network connection, identify a first server in the plurality of servers that is currently mapped to the bucket identifier in a hash table, and send the packet to the first server. If the network load balancer receives the packet back from the first server, the network load balancer can determine, based on local history information, a second server that was previously mapped to the bucket identifier in the hash table and send the packet to that second server.

Abstract: Techniques for configuring shared routing tables for network devices are provided. In some embodiments, a shared routing context is configured to include common routes across several local routing contexts. When a first packet is received at a first local routing context that is to be routed using one of the common routes, NAT operations may be performed on the first packet and then the shared routing context is used to process the first packet. Similarly, when a second packet is received at a second local routing context that is to be routed using the same common route, NAT operations may be performed on the second packet and then the shared routing context is used to process the second packet.

Abstract: Techniques for implementing resilient hashing with multiple hashes are provided. In one set of embodiments, a network device can maintain a first hash table comprising mappings between a first set of hash indices and a set of bit values. The network device can also maintain a second hash table comprising mappings between a second set of hash indices and active next-hop destinations. Upon receiving a network packet, the network device can compute a first hash and can match the first hash value to a first mapping in the first hash table based on the first mapping's hash index. When the first mapping's bit value indicates that the first mapping's hash index corresponds to an active next-hop destination, the network device can further match the first hash value to a second mapping in the second hash table and send the network packet to the second mapping's active next-hop destination.

Abstract: Techniques for implementing history-based connection-server affinity on a network load balancer are provided. In one set of embodiments, the network load balancer can receive a network packet destined for a service, where the service is associated with a plurality of servers, and where the packet is part of a network connection between a client device and one of the plurality of servers. The network load balancer can further compute, using a portion of the packet, a bucket identifier of a bucket for the network connection, identify a first server in the plurality of servers that is currently mapped to the bucket identifier in a hash table, and send the packet to the first server. If the network load balancer receives the packet back from the first server, the network load balancer can determine, based on local history information, a second server that was previously mapped to the bucket identifier in the hash table and send the packet to that second server.

Abstract: Techniques for implementing resilient hashing with multiple hashes are provided. In one set of embodiments, a network device can maintain a first hash table comprising mappings between a first set of hash indices and a set of bit values. The network device can also maintain a second hash table comprising mappings between a second set of hash indices and active next-hop destinations. Upon receiving a network packet, the network device can compute a first hash and can match the first hash value to a first mapping in the first hash table based on the first mapping's hash index. When the first mapping's bit value indicates that the first mapping's hash index corresponds to an active next-hop destination, the network device can further match the first hash value to a second mapping in the second hash table and send the network packet to the second mapping's active next-hop destination.

Abstract: A distributed call routing system and method are used to provide higher quality VoIP connections with flexible codec choices and simplified NAT and firewall traversal. An analog telephone adapter (ATA) communicates a call destination to a network information server (NIS), which provides multiple routes. The ATA uses this information and local and/or non-NIS information to initiate the call using the preferred routing.

Abstract: An exemplary system and method for providing virtual multiple lines in a communication system is provided. The exemplary system allows a plurality of simultaneous phone calls to be conducted via a single access identifier (e.g., phone number). In exemplary embodiments, the system comprises a hub configured to route calls via PSTN and VoIP. The determination as to how the call should be routed may be performed by the hub, a call services server, or a combination of both. At least one client device may be coupled in communication with the hub and configured to enable placement or receipt of a second or subsequent call when a first call is active. The client device is coupled to a communication device which places or receives the second or subsequent call.

Abstract: A distributed call routing system and method are used to provide higher quality VoIP connections with flexible codec choices and simplified NAT and firewall traversal. An analog telephone adapter (ATA) communicates a call destination to a network information server (NIS), which provides multiple routes. The ATA uses this information and local and/or non-NIS information to initiate the call using the preferred routing.

Abstract: An exemplary system and method for providing virtual multiple lines in a communication system is provided. The exemplary system allows a plurality of simultaneous phone calls to be conducted via a single access identifier (e.g., phone number). In exemplary embodiments, the system comprises a hub configured to route calls via PSTN and VoIP. The determination as to how the call should be routed may be performed by the hub, a call services server, or a combination of both. At least one client device may be coupled in communication with the hub and configured to enable placement or receipt of a second or subsequent call when a first call is active. The client device is coupled to a communication device which places or receives the second or subsequent call.

Abstract: Exemplary systems and methods for auto-configuring a network device are provided. In exemplary embodiments, the network device receives network data, which is used to determine identification data for a client. A version of the client identification data is then sent to an ISP by the network device. In response, a public IP address is returned from the ISP. The network device then translates the public IP address into an internal IP address for use with the client. In some embodiments, the network device is verified by a central data center. In some embodiments, the network device may be provisioned for PSTN and/or VoIP calls.