Location Information Database

Lync identifies an endpoint’s physical location by examining the network subnet, switch, and wireless access point the client uses. This collection of network objects is referred to as the Location Information Service (LIS) database and must be populated by administrators in advance of enabling E911. The LIS database is completely separate from the Lync network configuration of sites and subnets discussed separately. The LIS database function is only to provide a mapping of network objects to physical addresses that can be sent to the service provider or ELIN gateway.

This database can be populated manually or can be linked to a secondary location information database if one already exists. For Lync Server 2013 to use a secondary location information database, the service must adhere to the Lync Server 2013 Request/Response schema.

If manually populating the location database, start by identifying each of the network access points, switches, and subnets within the organization and the physical location associated with each object. When determining an endpoint’s location, Lync Server 2013 first uses the wireless access point, and then the switch ID, and lastly a subnet to determine location. This is because each of these items can potentially span multiple rooms or floors in a building, so none is an exact location.

After the location information database is populated, it should be validated with the Emergency Services Service Provider. This validation process compares the addresses associated to each network object with the database maintained by the provider to ensure that each location entered in Lync Server 2013 can be correctly routed to a PSAP, which can respond to the request. Alternatively, any ELINs must be entered in the telephony provider’s Automatic Location Identification (ALI) database.