Set-CsLisSwitch -ChassisID <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-CsLisSwitch -ChassisID <String> [-Confirm [<SwitchParameter>]] [-Description <String>] [-WhatIf [<SwitchParameter>]]

Set-CsLisSwitch -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 network switch through which calls will be routed.

The ChassisID parameter is the only required parameter for this cmdlet. If you enter a ChassisID value that already exists, this cmdlet will update the location for that switch based on the location parameters that are supplied. If the ChassisID does not exist, a new switch 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-CsLisSwitch cmdlet does not require or prompt for location parameters, you can create a switch 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 switch may not contain the information required by the emergency operator (depending on whether valid settings are available for a subnet or wireless access point that can be used in place of switch settings). It is recommended that you be as specific as possible with the location parameters and fill in as many as possible.

Note that switch entries can also be created by calling the Set-CsLisPort cmdlet. If Set-CsLisPort is called with a ChassisID value that does not have an existing switch entry, that switch will be created.

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

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

	Copy Code
Set-CsLisSwitch -ChassisID 99-99-99-99-99-99

Example 1 creates or updates a LIS switch location entry. The command in this example includes only one (required) parameter: ChassisID. The value of the ChassisID is the MAC address of the switch, in this case 99-99-99-99-99-99.

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

IMPORTANT. If a LIS switch location with this ChassisID already exists, it will be replaced by the values in this command. That means that if this switch 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 switch.

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

	Copy Code
Set-CsLisSwitch -ChassisID 99-99-99-99-99-99 -Location "30/1000" -HouseNumber 1234 -PreDirectional NE -StreetName First -StreetSuffix Avenue -City Redmond -State WA -Country US -PostalCode 99999

Example 2 updates the switch created in Example 1 by adding address information. (This is actually deleting the existing entry and replacing it with this new entry.) If the address does not exist in the location database, this cmdlet will create that location.

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

	Copy Code
$a = Get-CsLisSwitch | Where-Object {$_.ChassisID -eq "99-99-99-99-99-99"} $a | Set-CsLisSwitch -Location "30/2000"

In Example 2 we modified an existing switch entry by basically doing a delete and create – if an entry with the given ChassisID existed, that entry was deleted and the new entry, with the parameters shown in the example, was created. In this example we’re actually modifying an existing entry. This example modifies the Location property of the switch with the ChassisID 99-99-99-99-99-99 by changing the Location, but leaving all other properties as they were.

The example begins by calling the Get-CsLisSwitch cmdlet. This cmdlet retrieves a collection of all switch location entries. We then pipe this collection to the Where-Object cmdlet, which looks through the collection for any entries with a ChassisID equal to 99-99-99-99-99-99. Because ChassisIDs are unique this will narrow the collection down to, at most, one entry. We assign this entry to the variable $a

In the next line we pipe the contents of variable $a (the switch with the ChassisID 99-99-99-99-99-99) to the Set-CsLisSwitch cmdlet. The only parameter we supply to the cmdlet is Location. This will update the Location property of that switch, and will leave all other properties as they were. For example, if the HouseNumber property had a value of 1234, it still has a value of 1234 after running this command.

-------------------------- Example 4 --------------------------

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

This example updates the postal code of all locations defined for switches that have a City property value of Redmond. The first line in this example begins with a call to Get-CsLisSwitch, which retrieves all the switches that have been defined in the LIS service. That collection of switches 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 switches with the City 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 switches with the City Redmond) to the Set-CsLisSwitch cmdlet. This cmdlet will take each item in that collection and update it with the value passed to the PostalCode parameter. As with Example 3, the entries are not replaced, only the PostalCode property is modified.