locked
How the Skype 2015 client determines it's location? RRS feed

  • Question

  • We're modifying our LIS database after recently upgrading our internal wifi infrastructure.  We have all new AP's with new subnets assigned.  Currently we've configured all the new subnets using set-cslissubnet.  The problem with this method (IP subnets) is that because of how the new AP's work, it's possible that you could maintain the same IP address all over the campus (a very BIG campus) if you were walking around with your laptop.  I don't really understand the mechanics of it but, as it was explained to me, the AP's hand off your leased address as you walk out of ones range and into another's.  This makes the location displayed in the Skype client very unreliable.

    Given this, we decided to add the BSSID's of the new AP's and configure all the wireless access points in the LIS database (i.e. set-CsLisWirelessAccessPoint).  We added them in addition to the previously created subnets.

    The issue we're having is that the clients displayed location is accurate for some users (the ones getting their location from AP's instead of the particular subnet of their address), and others are getting the location defined by the subnet.

    So, we decided to try removing all the wireless subnets (i.e. remove-CsLisSubnet) and rely entirely on the more accurate wireless AP locations (i.e. set-CsLisWirelessAccessPoint).  It didn't work very well unfortunately, and most clients were suddenly being prompted to enter their location manually.

    Is there a prescribed method for configuring the LIS database so that all wireless clients reliably get their location from the AP's and not the subnet?

    Thanks in advance!


    • Edited by blinkyjesus Friday, February 16, 2018 4:46 PM new info
    Friday, February 16, 2018 4:05 PM

Answers

  • Turns out the AP's we deployed had more than one BSSID.  We had setup two different WiFi networks and the last digit of the main BSSID was different for each one.  For example, the BSSID of the AP would be 12-34-56-78-90-10.  However, what the client saw depended on which wifi network they were connecting to.  So, Wifi 1 would be 12-34-56-78-90-1A and Wifi 2 would be 12-34-56-78-90-1B.  The client never saw the main BSSID of the AP, and that's what tripped us up.

    After we figured that part out and plugged in the BSSID's the clients were seeing, everything worked as expected.

    Thanks!


    • Edited by blinkyjesus Monday, February 19, 2018 7:35 PM edit
    • Marked as answer by blinkyjesus Monday, February 19, 2018 7:36 PM
    Monday, February 19, 2018 7:34 PM

All replies

  • The client should run a query, whenever the BSSID changes. Generally speaking, you should be able to use both IP Addresses and BSSIDs. You should be able to use the same IP across the campus. Just make sure that that the LIS database is hosted on SQL Instance with ample processing power. 

    If you have errors, please open a ticket with Microsoft Support

    Friday, February 16, 2018 7:35 PM
  • Turns out the AP's we deployed had more than one BSSID.  We had setup two different WiFi networks and the last digit of the main BSSID was different for each one.  For example, the BSSID of the AP would be 12-34-56-78-90-10.  However, what the client saw depended on which wifi network they were connecting to.  So, Wifi 1 would be 12-34-56-78-90-1A and Wifi 2 would be 12-34-56-78-90-1B.  The client never saw the main BSSID of the AP, and that's what tripped us up.

    After we figured that part out and plugged in the BSSID's the clients were seeing, everything worked as expected.

    Thanks!


    • Edited by blinkyjesus Monday, February 19, 2018 7:35 PM edit
    • Marked as answer by blinkyjesus Monday, February 19, 2018 7:36 PM
    Monday, February 19, 2018 7:34 PM
  • Thanks for your sharing

    Best Regards,
    Leon Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, February 28, 2018 1:16 AM