[Index]
VOSS Automate allows you to configure and manage all elements of emergency call routing for Microsoft Teams, from within the VOSS Automate Admin Portal.
There are two approaches to emergency call routing in Microsoft Teams:
The option you choose depends on how your sites are set up, the specific requirements of your organization, and the elements related to each option, which may be grouped as follows:
Emergency Locations | This is a group of details in MS Teams that models the Dynamic Emergency Routing elements - the Civic Address and all the related Location Information Server (LIS) details - Location, Subnet, Port, Wireless Access Point, and Switch. |
Emergency Location Networks | This is for the additional emergency options not related to the Location Information Server (LIS) elements - Network Sites and Network Subnets. This can, for instance, help model routing to local security desks rather than directly to emergency services. This basically relates Network Sites and Subnets elements. This feature provides a read-only view to allow you to see Network Sites and related Subnets in a single view - editing either element is done via the dedicated menu item. |
Trusted IP Addresses | Dedicated menu items in the VOSS Automate GUi allow the addition of IP Addresses or subnets external to the enterprise network that are to be trusted by the MS Teams system for location based services. |
In addition to the basic setup for emergency routing, VOSS Automate allows you to create emergency policies and to assign these to users. The following policies are supported:
Note
See the MS Teams policy management and subscriber management sections in the Core feature guides for further details.
Related Topics
Overview
VOSS Automate provides the ability to support all the elements related to emergency calling setup in Microsoft Teams, including Dynamic Emergency, which allows for the management of Microsoft Teams emergency locations for emergency calling.
You can set up one or more emergency dispatch locations (for example, parts of a building), for your organization's physical location (civic address).
Related Topics
Configure MS Teams Emergency Locations
In the VOSS Automate Admin Portal, go to (default menus) MS Teams Emergency Management > Teams Emergency Locations.
Click on an item in the list to view or update its details.
To add an emergency location, click the toolbar Plus icon (+), and configure the new record:
Address tab | On this tab, configure emergency location details.
|
Locations tab | Add associated locations. Verify requirements according to the selected Country Or Region. For example, if this is set to UK, then it is mandatory to provide HouseNumber. This tab allows you to add more granular, additional locations for an address, as needed. And for each location, you can add relevant data from the Location Information Server (LIS), to identify the location. For example, subnet, port, switch, and wireless access points (WAP). Some details to this tab are mandatory, while others are optional (you can create the base civic address then add locations later), if you don't create a location when adding, MS Teams automatically generates a read-only default location, which you will see when viewing the emergency location later in VOSS Automate. You can add relevant LIS information to that default location. However, you won't be able to update the description or ELIN (Emergency Location Identification Number). You can add additional locations as needed. You can't delete the default location from the list of locations associated with a physical civic address. The default is only removed when the physical civic address is deleted. You can add relevant LIS information to the default location as required, which is useful if you plan to have only a single location for the address. |
Save your changes.
Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Address | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Company Name | Specifies a company name for the civic address. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Description | Description |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Company Tax ID | Used to store TaxId for regulatory reasons. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Building or House Number | Specifies the numeric portion of the civic address. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Street Name | Specifies the street name of the civic address. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Street Suffix | Specifies the modifier of the street name of the civic address. The street suffix will typically be something like street, avenue, way, or boulevard. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
City | Specifies a city for the civic address. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
State Or Province | Specifies the state or province of the civic address. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Country Or Region | Specifies the country or region of the civic address. Needs to be a valid country code as contained in the ISO 3166-1 alpha-2 specification. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Postal Code or Zip Code | Specifies the postal code of the civic address. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Latitude | Specifies the angular distance of a place north or south of the earth's equator. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Longitude | Specifies the angular distance of a place east or west of the meridian at Greenwich, England. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Locations | Group Assigned by FDP |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Locations |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Name | Specifies an administrator defined description of the location. For example, "2nd Floor Cafe", "Main Lobby", or "Office 250". |
|
|||||||||||||||||||||||||||||||||||||||||||||||
ELIN | Specifies the Emergency Location Identification Number. This is used in Direct Routing EGW scenarios. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Is Default |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Ports |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Chassis ID | If ChassisID sub type is a MAC Address then this value must be in a string format in the following representation nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. Otherwise, (different sub type, such as Interface Name), then this value must be in a string format as set on the switch |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Port ID | If PortID sub type is a MAC Address then this value must be in a string format in the following representation nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. Otherwise, (different sub type, such as Interface Name), then this value must be in a string format as set on the switch |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Description | Specifies the administrator defined description of the Location Information Service subnet. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Subnets |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Subnet | The IP address of the subnet. This value can be either IPv4 or IPv6 format. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Description | Specifies the administrator defined description of the Location Information Service subnet. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Switches |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Chassis ID | If ChassisID sub type is a MAC Address then this value must be in a string format in the following representation nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. Otherwise, (different sub type, such as Interface Name), then this value must be in a string format as set on the switch |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Description | Specifies the administrator defined description of the Location Information Service subnet. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Wireless Access Points |
|
||||||||||||||||||||||||||||||||||||||||||||||||
BSS ID | The Basic Service Set Identifier (BSSID) of the wireless access point. This value must be in the form nn-nn-nn-nn-nn-nn, such as 12-34-56-78-90-ab. If an entry with the specified BSSID value does not exist, a new WAP location will be created. If an entry with the specified BSSID already exists, that entry will be replaced. It can be presented in wildcard format. The wildcard '*' can be on either the last one or two character(s). |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Description | Specifies the administrator defined description of the Location Information Service subnet. |
|