Abstract: Techniques for location source ranking for determining device location are described. A location source generally refers to a source of position information (e.g., GPS coordinates, latitude and longitude, street addresses, and so forth) that can be used to determine a geographical location of a device. According to one or more embodiments, location sources and/or combinations of location sources can be ranked based on various criteria. Thus, when a location is requested for a particular device, a highest ranking available location source or combination of location sources can be selected to determine a location of the device. Location source rankings, for instance, can be maintained on a client device and/or via a remote location-related service. According to various embodiments, a location of a device can be determined to enable emergency assistance to be provided at the location.

Abstract: Techniques for determining a valid resource string for a resource are described. According to one or more implementations, a particular resource string for accessing a particular resource may be determined to be not valid at a current location of a client device. Accordingly, the particular resource string can be mapped to an active string profile for the client device, and a valid resource string for accessing the resource at the current location can be determined from the active string profile. The valid resource string can be used to initiate communication with an instance of the particular resource.

Abstract: Techniques for policies for selecting sources for resource strings are described. Generally, a resource string refers to a set of characters that can be used to initiate communication with a particular resource. According to one or more embodiments, techniques discussed herein enable resource strings to be determined at different locations, e.g., geographic locations. In at least some embodiments, string source policies are implemented that specify parameters for selecting a source from which to obtain resource strings. According to one or more embodiments, string profiles are implemented that specify resource strings that correspond to particular resources and/or types of resources.

Abstract: Techniques for policies for selecting sources for resource strings are described. Generally, a resource string refers to a set of characters that can be used to initiate communication with a particular resource. According to one or more embodiments, techniques discussed herein enable resource strings to be determined at different locations, e.g., geographic locations. In at least some embodiments, string source policies are implemented that specify parameters for selecting a source from which to obtain resource strings. According to one or more embodiments, string profiles are implemented that specify resource strings that correspond to particular resources and/or types of resources.

Abstract: Techniques for location source ranking for determining device location are described. A location source generally refers to a source of position information (e.g., GPS coordinates, latitude and longitude, street addresses, and so forth) that can be used to determine a geographical location of a device. According to one or more embodiments, location sources and/or combinations of location sources can be ranked based on various criteria. Thus, when a location is requested for a particular device, a highest ranking available location source or combination of location sources can be selected to determine a location of the device. Location source rankings, for instance, can be maintained on a client device and/or via a remote location-related service. According to various embodiments, a location of a device can be determined to enable emergency assistance to be provided at the location.

Abstract: The present invention extends to methods, systems, and computer program products for admitting calls based on endpoint locations. Embodiments of the invention can be used to map (e.g., IP) subnets of an enterprise to the location where the subnets are managed in the network. A call admission control decision is then based on the subnets where endpoints (e.g., IP nodes) are currently located (as opposed to where users that use the endpoints are homed at). Embodiments of the invention can use just in time location detection. That is, endpoint locations can be detected just before a bandwidth policy decision is made. Detecting locations just before a bandwidth policy decision increases the likelihood of making an appropriate bandwidth policy decision.

Abstract: The present invention extends to methods, systems, and computer program products for admitting calls based on endpoint locations. Embodiments of the invention can be used to map (e.g., IP) subnets of an enterprise to the location where the subnets are managed in the network. A call admission control decision is then based on the subnets where endpoints (e.g., IP nodes) are currently located (as opposed to where users that use the endpoints are homed at). Embodiments of the invention can use just in time location detection. That is, endpoint locations can be detected just before a bandwidth policy decision is made. Detecting locations just before a bandwidth policy decision increases the likelihood of making an appropriate bandwidth policy decision.

Abstract: Described herein are embodiments for setting, managing, and monitoring connection policies for a plurality of network paths from a first endpoint to a second endpoint. In embodiments, a set of candidate addresses from a first endpoint and a set of candidate addresses from a second endpoint are received. Each candidate address of the first endpoint is paired with each candidate address of the second endpoint to create a plurality of candidate address pairs. Each candidate address pair has an associated network path. The network path is the route by which data flows to and from the various endpoints. Once all network paths between each candidate address pair have been determined, a connection policy is set for each network address pair and the associated network path.

Abstract: Described herein are embodiments for setting, managing, and monitoring connection policies for a plurality of network paths from a first endpoint to a second endpoint. In embodiments, a set of candidate addresses from a first endpoint and a set of candidate addresses from a second endpoint are received. Each candidate address of the first endpoint is paired with each candidate address of the second endpoint to create a plurality of candidate address pairs. Each candidate address pair has an associated network path. The network path is the route by which data flows to and from the various endpoints. Once all network paths between each candidate address pair have been determined, a connection policy is set for each network address pair and the associated network path.

Abstract: Described herein are embodiments for setting, managing, and monitoring connection policies for a plurality of network paths from a first endpoint to a second endpoint. In embodiments, a set of candidate addresses from a first endpoint and a set of candidate addresses from a second endpoint are received. Each candidate address of the first endpoint is paired with each candidate address of the second endpoint to create a plurality of candidate address pairs. Each candidate address pair has an associated network path. The network path is the route by which data flows to and from the various endpoints. Once all network paths between each candidate address pair have been determined, a connection policy is set for each network address pair and the associated network path.

Abstract: Described herein are embodiments for setting, managing, and monitoring connection policies for a plurality of network paths from a first endpoint to a second endpoint. In embodiments, a set of candidate addresses from a first endpoint and a set of candidate addresses from a second endpoint are received. Each candidate address of the first endpoint is paired with each candidate address of the second endpoint to create a plurality of candidate address pairs. Each candidate address pair has an associated network path. The network path is the route by which data flows to and from the various endpoints. Once all network paths between each candidate address pair have been determined, a connection policy is set for each network address pair and the associated network path.

Abstract: Techniques to manage communications between relay servers are described. A system may include multiple relay servers each having an enhanced relay control module. The enhanced relay control module may be operative to manage communications between private clients communicating over the first relay server and the second relay server. The enhanced relay control module may establish a media channel between control ports for the first and second relay servers when a port range attribute for at least one of the first or second relay servers is turned off. Other embodiments are described and claimed.

Abstract: A relay server authentication service for a relay server is described. An apparatus may include a proxy server to receive an authentication request for client authentication information from a first client to traverse a network address translation device. The apparatus may further include a relay server with a relay server authentication service module. The relay server authentication service module may be arranged to receive the authentication request from the proxy server, generate the client authentication information for the first client, and send an authentication response with the client authentication information to the first client through the proxy server. Other embodiments are described and claimed.