AudioCodes Mediant 500 E-SBC, Руководство пользователя

Страница: 422 / 920

User's Manual 422 Document #: LTRT-10437
Mediant 500 E-SBC
For a Lync 2010 client that moves inside the corporate network such as a soft phone
on a laptop that connects wirelessly to the corporate network, Lync Server 2010 can
determine which subnet the phone belongs to or which WAP / SSID is currently
serving the soft-client.
4. The LIS queries the published locations for a location and if a match is found, returns
the location information to the client. The matching order is as follows:
•
WAP BSSID
•
LLDP switch / port
•
LLDP switch
•
Subnet
•
MAC address
This logic ensures that for any client that is connected by a wireless connection, a
match is first attempted based on the hardware address of its connected access point.
The logic is for the match to be based on the most detailed location. The subnet
generally provides the least detail. If no match is found in the LIS for WAP BSSID,
LLDP switch / port, LLDP switch, or subnet, the LIS proxies the MAC address to an
integrated Simple Network Management Protocol (SNMP) scanning application. Using
SNMP may benefit some organizations for the following reasons:
•
LLDP is not supported by Lync Server 2010 so this provides a mechanism for soft
phones to acquire detailed location information.
•
Installed Layer-2 switches may not support LLDP.
If there is no match and the LIS cannot determine the location, the user may be prompted
to manually enter the location. For example, the client may be located in an undefined
subnet, at home, in a coffee shop or anywhere else outside the network. When a user
manually provides a location, the location is mapped based on the MAC address of the
default gateway of the client’s network and stored on the client. When the client returns to
any previously stored location, the client is automatically set to that location. A user can
also manually select any location stored in the local users table and manage existing
entries.
26.5.2.2.2 Adding ELINs to the Location Information Server
As mentioned in the previous section, the Administrator needs to populate the Location
Information Server (LIS) database with a network wire map, which maps the Enterprise's
network elements to civic addresses. Once done, it can automatically locate clients within
a network. You can add addresses individually to the LIS or in a batch using a comma-
separated value (CSV) file containing the column formats listed in the table below.
Table 26-1: Columns in the LIS Database
Network Element Columns
Wireless access
point
<BSSID>,<Description>,<Location>,< CompanyName >,<HouseNumber>,<House
NumberSuffix>,<PreDirectional>,…<StreetName>,<StreetSuffix>,<PostDirectiona
l>,<City>,<State>,<PostalCode>,<Country>
Subnet
<Subnet>,<Description>,<Location>,<CompanyName>,<HouseNumber>,<House
NumberSuffix>,<PreDirectional>,…<StreetName>,<StreetSuffix>,<PostDirectiona
l>,<City>,<State>,<PostalCode>,<Country>
Port
<ChassisID>,<PortIDSubType>,<PortID>,<Description>,<Location>,<CompanyN
ame>,<HouseNumber>,<HouseNumberSuffix>,…<PreDirectional>,<StreetName
>,<StreetSuffix>,<PostDirectional>,<City>,<State>,<PostalCode>,<Country>
Switch
<ChassisID>,<Description>,<Location>,<CompanyName>,<HouseNumber>,<Ho
useNumberSuffix>,<PreDirectional>,…<StreetName>,<StreetSuffix>,<PostDirecti
onal>,<City>,<State>,<PostalCode>,<Country>