But as we humans aren’t too good with binary we represent it as multiple 8 bit numbers. Any bits set to 1 in the subnet mask are network bits and any bits set to 0 are host bits. To calculate the NetworkID of a user, the Skype4B client simply grabs the current IPAddress and Subnet mask of the client machine, discards the host bits and is left with the NetworkID. What are the host bits? That’s what you tell windows when defining a Subnet mask. This NetworkID is calculated by doing some simple math on the users IP address and Subnet mask at the client side and has no regard for routers or even the networking teams map of IP addresses.įor those not of a networking background a NetworkID is the first address of a subnet and it is unusable The LIS database doesn’t maintain a list of Networks and Subnet masks like CAC and other applications in Skype do, when using IP addresses it relies entirely on the NetworkID of a user to figure out where a user is located.

Note: if you know how LIS and supernetting work, skip ahead, but for the rest of us. You know that little thing that automatically updates your location based on where you are? it doesn’t? Maybe you need to check your LIS config!Īs a Skype4B admin setting the LIS up can be a bit of a pain as it requires detailed information from the networking team on each individual subnet in the customers topology and what I find more often than not is that the data provided by the networking team is SuperNetted.

I don’t know about you, but I love the Skype for Business location database.

Database requirements for skype