Set-CsLisSubnet -Subnet <String> [-City <String>] [-CompanyName <String>] [-Confirm [<SwitchParameter>]] [-Country <String>] [-Description <String>] [-HouseNumber <String>] [-HouseNumberSuffix <String>] [-Location <String>] [-PostalCode <String>] [-PostDirectional <String>] [-PreDirectional <String>] [-State <String>] [-StreetName <String>] [-StreetSuffix <String>] [-WhatIf [<SwitchParameter>]]

Set-CsLisSubnet -Subnet <String> [-Confirm [<SwitchParameter>]] [-Description <String>] [-WhatIf [<SwitchParameter>]]

Set-CsLisSubnet -City <String> -CompanyName <String> -Country <String> -HouseNumber <String> -HouseNumberSuffix <String> -Location <String> -PostalCode <String> -PostDirectional <String> -PreDirectional <String> -State <String> -StreetName <String> -StreetSuffix <String> [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]]

Parameters

Enhanced 911 allows an emergency operator to identify the location of a caller without having to ask the caller for that information. In the case where a caller is calling from a Voice over IP (VoIP) connection that information must be extracted based on various connection factors. The VoIP administrator must configure a location map (called a wiremap) that will determine a caller’s location. This cmdlet allows the administrator to map physical locations to the subnet through which calls will be routed.

The Subnet parameter is the only required parameter for this cmdlet. If you enter a Subnet value that already exists, this cmdlet will update the location for that subnet based on the location parameters that are supplied. If the Subnet does not exist, a new subnet location will be created.

If a location with an address exactly matching the address parameters entered here (including null values) does not exist in the location database, a new address will be created based on the parameters entered with this cmdlet. (You can retrieve a list of locations by calling the Get-CsLisLocation cmdlet.) The Set-CsLisSubnet cmdlet does not require or prompt for location parameters, you can create a subnet entry without associating it with a location. It’s also possible to create an invalid location with this cmdlet. A valid location consists of, at minimum, a Location, HouseNumber, StreetName, City, State, and Country. If you do not supply all these parameters, calls that are routed through the specified subnet may not contain the information required by the emergency operator (depending on whether valid settings are available for a switch, port, or wireless access point that can be used in place of subnet settings). It is recommended that you be as specific as possible with the location parameters and fill in as many as possible.

This cmdlet creates or modifies an object of type System.Management.Automation.PSCustomObject.

-------------------------- Example 1 --------------------------

	Copy Code
Set-CsLisSubnet -Subnet 192.10.10.0

Example 1 creates or updates a LIS subnet location entry. The command in this example includes only one (required) parameter: Subnet. The value of the Subnet in this example is an IPv4 address, 192.10.10.0.

Notice that this example does not include any address information. It’s possible to create a subnet entry on the Location Information Server without associating it with an address. However, emergency calls routed through this subnet may not (depending on port or switch locations that have been defined) contain enough information for the emergency operator to identify a location.

IMPORTANT. If a LIS subnet location with this Subnet value already exists, it will be replaced by the values in this command. That means that if this port were associated with an address (a physical location), that association would no longer exist because we didn’t include any location information in this command. The location will still exist in the location database, but it will not be associated with this subnet.

-------------------------- Example 2 --------------------------

	Copy Code
Set-CsLisSubnet -Subnet 2001:00:10:AAAA:0:0:0:0 -Location "30/1000" -HouseNumber 1234 -PreDirectional NE -StreetName First -StreetSuffix Avenue -City Redmond -State WA -Country US -PostalCode 99999

This example creates or modifies the subnet with the IPv6 address 2001:00:10:AAAA:0:0:0:0. If that subnet already has an entry in the LIS service then this cmdlet updates that subnet location information; if it does not have an entry, a new entry is created with the given location information. That location information is provided in the rest of the parameters to this command.

-------------------------- Example 3 --------------------------

	Copy Code
$a = Get-CsLisSubnet | Where-Object {$_.City -eq "Redmond"} $a | Set-CsLisSubnet -PostalCode 99998

This example updates all locations defined for subnets associated with a location in the city of Redmond. The first line in this example begins with a call to Get-CsLisSubnet, which retrieves all the subnets that have been defined in the LIS service. That collection of subnets is piped to the Where-Object cmdlet, which finds all the items in the collection with a City equal to (-eq) Redmond. This collection of subnets with the City property value of Redmond is assigned to the variable $a.

In the second line of this example, we pipe the contents of variable $a (the collection of LIS subnets with the City value Redmond) to the Set-CsLisSubnet cmdlet. This cmdlet will take each item in that collection and update the PostalCode property of each with the value 99998. Note that this will not change any other properties of the subnet locations, only the PostalCode property will be modified.