Monday, July 23, 2012

Location Information Service (LIS) Lync 2010/ 2013

Lync 2010 with CU1 introduced the LIS for identifying the Users Location for E-9-1-1 call and internal information too. The E-9-1-1 Service must be supported by a) SIP Trunk Provider or/and b) Law. What does Law mean?  Simply explained, if you are for example in Germany, so need to ensure you can make Emergency Calls also during Power Interruption. This cannot be done with Computer based Systems. A PABX is different, there are service ensuring the phones availability.

So let look into LIS itself:
The information will be stored in the LIS Database for Lync, which is the same for Lync 2010 and 2013.
Lync identifies 4 different Location Types:
1.     Switch Ports
2.     Switches
3.     IP Subnets
4.     Wireless Access Points

All associated commands here are:
  • Get-CsLisSubnet
  • Set-CsLisSubnet
  • Remove-CsLisSubnet
  • Get-CsLisWirelessAccessPoint
  • Set-CsLisWirelessAccessPoint
  • Remove-CsLisWirelessAccessPoint
  • Get-CsLisSwitch
  • Set-CsLisSwitch
  • Remove-CsLisSwitch
  • Get-CsLisPort
  • Set-CsLisPort
  • Remove-CsLisPort

It is important to remember that LIS Networks have nothing in common with the Lync Networks, which you mainly use for Region and Site consolidation.
Wireless, Switches and Port will be identified with their ChassisID, which is equivalent to the MAC address (Layer-2 Switch), managed Ethernet switches that support Link Layer Discovery Protocol-Media Endpoint Discover (LLDP-MED)

Just not enough here, that’s when I talked about the Service Provider, here are several things you need to check and configure:
Before publishing the location database, you must validate new locations against the Master Street Address Guide (MSAG) maintained by your SIP trunk or public switched telephone network (PSTN) E9-1-1 service provider.

Remember for Planning (MSFT):
hen you use ELIN gateways, you populate the Location Information service database with the civic address and at least one ELIN for each Emergency Response Location (ERL). During the planning phase, it is a good idea to decide how you want to name the locations and how you want to assign ELINs.

Planning Location Names

The Location Information service Location field has a maximum length of 20 characters (including spaces). Within that limited length, try to include the following:
  • An easy-to-understand name that identifies the location of the 911 caller to help ensure that emergency responders find the specific location promptly when they arrive at the civic address. This location name may include a building number, floor number, wing designator, room number, and so on. Avoid nicknames known only to employees, which might cause emergency responders to go to the wrong location.
  • A location identifier that helps users to easily see that their Lync client picked up the correct location. The Lync 2010 client automatically concatenates and displays the discovered Location and City fields in its header, while the Lync 2013 client ONLY displays the discovered Location information. A good practice is to add the street address of the building to each location identifier (for example, "1st Floor <street number>"). Without the street address, a generic location identifier such as "1st Floor" could apply to any building in the city.
  • If the location is approximate because it’s determined by a wireless access point, you may want to add the word Near (for example, "Near 1st Floor 1234").

Planning ELINs

ERLs define specific locations at a street address. You need to decide how you want to divide your building space into ERLs and how many ELINs to assign to each ERL. For example, in a multifloor or multitenant building, different areas in the building can be assigned different ERL zones. Typically, each floor in a building is designated as an ERL. Each ERL is then assigned one or more ELINs, which are used as the calling number(s) during an emergency call. Contact your PSTN carrier for phone numbers that you can use for ELINs. The following table provides an example of ERLs for a specific street address.

After we have designed the LIS, it’s part for the Service Provider to be integrated as well.
There are two steps necessary:

1.     Setup the Service Provider
2.     Validate the Addresses in your LIS DB against the Master Street Address Guide (MSAG)
3.     Publish the Location DB

Set-CsLisServiceProvider -ServiceProviderName Provider1 -ValidationServiceUrl <URL provided by provider> -CertFileName <location of certificate provided by provider> -Password $pwd
Get-CsLisCivicAddress | Test-CsLisCivicAddress -UpdateValidationStatus
Publish-csLisConfiguration


Note:
CsLisCivicAddress is only for receiving and testing the Civic Addresses against the Master Street Address Guid. The configuration is still part of CsLisLocation, where you create, modify or read the Location Configuration Database entries.

If you have remote user, you still need to configure a Client Policy, which makes it recommended for user entering a Location.

There are a lot more blog’s where you can see how you configure the above commands, so I’m not repeating this here, but its more how the service work and necessary to know about LIS.



11 comments:

  1. Hi Thomas, the Lync 2013 client do not concatenate Location and City filed, it use only Location field. This is a problem when some user have 2010 clients and some other 2013 client. Do you have some tips to help us?
    Thanks

    ReplyDelete
  2. Hi, very good you asked.
    During publishing there was an unknown behavior with Lync Client 2013.
    It's now corrected in the Blog here thanx.

    Lync Client 2010: displays the discovered Location and City fields in its header

    Lync Client 2013: and displays the discovered Location field in its header ONLY.

    ReplyDelete
  3. Can we define LIS for REMOTE users coming VIA EDGE? If yes how?

    ReplyDelete
  4. Hi, I have to disappoint you. LIS cannot be used via Edge Server, this is due to the possibility of overlapping network segments. so it would make any sense.
    Say you configure 172.31.1.0/24 as remote network, but you are in New York in a Hotel with this range, but you configured it for Sydney home office users, it is more clear that it cant work.

    But LIS (manual) will work, your use must type it themselves.
    an other option is, if you enforce VPN for Lync, than you can define granular ranges, for where a user, for what location a user can dial in. So this would than be part of LIS too.

    I hope the suggested ideas can help you.

    ReplyDelete
  5. HI,

    Is there any way where I can statically assign Location from GPO or Registry, disallowing users to change it.

    ReplyDelete
    Replies
    1. There are no GPO setting, it is and must be based on LIS, meaning network/ subnet information

      Delete
  6. Hi,
    I assume LIS is only available for Lync on premise and not for Lync online.
    Is this correct? And are there any alternatives for Lync Online?

    ReplyDelete
    Replies
    1. you are right, this is not available.
      you only can ask your user typing those information manually

      Delete
    2. hello how can remove location from lync 2013 ?

      Delete
    3. Hi Tahir,
      analog to the NEW-CSLISxxx command, you find the REMOVE-CSLISxx commands. So you have to remove the config from the LIS database using this remove commands. hope this finds you well.

      Delete
  7. Sorry to revive such an old thread but one of your comments makes no sense to me and I'm looking for clarification.

    "A good practice is to add the street address of the building to each location identifier (for example, "1st Floor "). Without the street address, a generic location identifier such as "1st Floor" could apply to any building in the city."

    Does this imply that the address I filled out in the other fields does not get sent to emergency services and that I have to rely solely on the "location" field? If so, how does including the "street number" help in any way if I don't include the street name? The street number can apply to many buildings in the city just as the "1st floor" does.

    My assumption was that the "location" field was just used as a description to display to other Lync (now SfB) clients and that the rest of the fields would be sent on to EMS.

    ReplyDelete