Adding Elins To The Location Information Server - AudioCodes Mediant 800B User Manual

•
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 Skype for Business 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.

15.8.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.
Network
Element
<BSSID>,<Description>,<Location>,<CompanyName>,<HouseNumber>,<HouseNumber
Wireless
Suffix>,<PreDirectional>,...<StreetName>,<StreetSuffix>,<PostDirectional>,<City>,<State
access point
>,<PostalCode>,<Country>
<Subnet>,<Description>,<Location>,<CompanyName>,<HouseNumber>,<HouseNumber
Subnet Suffix>,<PreDirectional>,...<StreetName>,<StreetSuffix>,<PostDirectional>,<City>,<State
>,<PostalCode>,<Country>
<ChassisID>,<PortIDSubType>,<PortID>,<Description>,<Location>,<CompanyName>,<H
Port ouseNumber>,<HouseNumberSuffix>,...<PreDirectional>,<StreetName>,<StreetSuffix>,<
PostDirectional>,<City>,<State>,<PostalCode>,<Country>
<ChassisID>,<Description>,<Location>,<CompanyName>,<HouseNumber>,<HouseNum
Switch berSuffix>,<PreDirectional>,...<StreetName>,<StreetSuffix>,<PostDirectional>,<City>,<St
ate>,<PostalCode>,<Country>
For the ELIN number to be included in the SIP INVITE (XML-based PIDF-LO message) sent by
the Mediation Server to the ELIN device, the administrator must add the ELIN number to the
<CompanyName> column (shown in the table above in bold typeface). As the ELIN device
supports up to five ELINs per PIDF-LO, the <CompanyName> column can be populated with up
to this number of ELINs, each separated by a semicolon. The digits of each ELIN can be
separated by hyphens (xxx-xxx-xxx) or they can be adjacent (xxxxxxxxx).
When the ELIN device receives the SIP INVITE, it extracts the ELINs from the NAM field in the
PIDF-LO (e.g., <ca:NAM>1111-222-333; 1234567890 </ca:NAM>), which corresponds to the
<CompanyName> column of the LIS.
User's Manual
Table 15-25: Columns in the LIS Database
294
Mediant 800B Gateway & E-SBC
Columns
Document #: LTRT-10298