[Index]

Model: relation/EmergencyLocation

Teams Emergency Locations

Full HTML Help

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

MS Teams Emergency Locations

Full HTML Help

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

  1. In the VOSS Automate Admin Portal, go to (default menus) MS Teams Emergency Management > Teams Emergency Locations.

  2. Click on an item in the list to view or update its details.

  3. To add an emergency location, click the toolbar Plus icon (+), and configure the new record:

    Address tab

    On this tab, configure emergency location details.

    • When adding a physical civic address, a default emergency location is added (the Is Default setting on the Locations tab is enabled and read-only for the location).
    • You can expose additional civic address fields via the field display policy, if required.
    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.

  4. Save your changes.

Model Details: relation/EmergencyLocation

Title Description Details
Address Group Assigned by FDP
  • Field Name: Address
  • Type: Object
Company Name Specifies a company name for the civic address.
  • Field Name: Address.CompanyName
  • Type: String
Description Description
  • Field Name: Address.Description
  • Type: String
Company Tax ID Used to store TaxId for regulatory reasons.
  • Field Name: Address.CompanyTaxId
  • Type: String
Building or House Number Specifies the numeric portion of the civic address.
  • Field Name: Address.HouseNumber
  • Type: String
Street Name Specifies the street name of the civic address.
  • Field Name: Address.StreetName
  • Type: String
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.
  • Field Name: Address.StreetSuffix
  • Type: String
City Specifies a city for the civic address.
  • Field Name: Address.City
  • Type: String
State Or Province Specifies the state or province of the civic address.
  • Field Name: Address.StateOrProvince
  • Type: String
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.
  • Field Name: Address.CountryOrRegion
  • Type: String
  • Choices: ["Afghanistan", "Åland Islands", "Albania", "Algeria", "American Samoa", "Andorra", "Angola", "Anguilla", "Antarctica", "Antigua and Barbuda", "Argentina", "Armenia", "Aruba", "Australia", "Austria", "Azerbaijan", "Bahamas, The", "Bahrain", "Bangladesh", "Barbados", "Belarus", "Belgium", "Belize", "Benin", "Bermuda", "Bhutan", "Bolivia", "Bonaire, Saint Eustatius and Saba", "Bosnia and Herzegovina", "Botswana", "Bouvet Island", "Brazil", "British Indian Ocean Territory", "Brunei", "Bulgaria", "Burkina Faso", "Burundi", "Cabo Verde", "Cambodia", "Cameroon", "Canada", "Cayman Islands", "Central African Republic", "Chad", "Chile", "China", "Christmas Island", "Cocos (Keeling) Islands", "Colombia", "Comoros", "Congo", "Congo (DRC)", "Cook Islands", "Costa Rica", "Côte d’Ivoire", "Croatia", "Curaçao", "Cyprus", "Czech Republic", "Denmark", "Djibouti", "Dominica", "Dominican Republic", "Ecuador", "Egypt", "El Salvador", "Equatorial Guinea", "Eritrea", "Estonia", "Ethiopia", "Falkland Islands (Islas Malvinas)", "Faroe Islands", "Fiji Islands", "Finland", "France", "French Guiana", "French Polynesia", "French Southern and Antarctic Lands", "Gabon", "Gambia, The", "Georgia", "Germany", "Ghana", "Gibraltar", "Greece", "Greenland", "Grenada", "Guadeloupe", "Guam", "Guatemala", "Guernsey", "Guinea", "Guinea-Bissau", "Guyana", "Haiti", "Heard Island and McDonald Islands", "Holy See (Vatican City State)", "Honduras", "Hong Kong SAR", "Hungary", "Iceland", "India", "Indonesia", "Iraq", "Ireland", "Isle of Man", "Israel", "Italy", "Jamaica", "Japan", "Jersey", "Jordan", "Kazakhstan", "Kenya", "Kiribati", "Korea, Republic of", "Kuwait", "Kyrgyzstan", "Laos", "Latvia", "Lebanon", "Lesotho", "Liberia", "Libya", "Liechtenstein", "Lithuania", "Luxembourg", "Macao SAR", "Macedonia, Former Yugoslav Republic of", "Madagascar", "Malawi", "Malaysia", "Maldives", "Mali", "Malta", "Marshall Islands", "Martinique", "Mauritania", "Mauritius", "Mayotte", "Mexico", "Micronesia", "Moldova", "Monaco", "Mongolia", "Montenegro", "Montserrat", "Morocco", "Mozambique", "Myanmar", "Namibia", "Nauru", "Nepal", "Netherlands", "Netherlands Antilles (Former)", "New Caledonia", "New Zealand", "Nicaragua", "Niger", "Nigeria", "Niue", "Norfolk Island", "Northern Mariana Islands", "Norway", "Oman", "Pakistan", "Palau", "Palestinian Authority", "Panama", "Papua New Guinea", "Paraguay", "Peru", "Philippines", "Pitcairn Islands", "Poland", "Portugal", "Puerto Rico", "Qatar", "Reunion", "Romania", "Russia", "Rwanda", "Saint Barthélemy", "Saint Helena, Ascension and Tristan da Cunha", "Saint Kitts and Nevis", "Saint Lucia", "Saint Martin", "Saint Pierre and Miquelon", "Saint Vincent and the Grenadines", "Samoa", "San Marino", "São Tomé and Príncipe", "Saudi Arabia", "Senegal", "Serbia", "Seychelles", "Sierra Leone", "Singapore", "Sint Maarten", "Slovakia", "Slovenia", "Solomon Islands", "Somalia", "South Africa", "South Georgia and the South Sandwich Islands", "South Sudan", "Spain", "Sri Lanka", "Suriname", "Svalbard and Jan Mayen Island", "Swaziland", "Sweden", "Switzerland", "Taiwan", "Tajikistan", "Tanzania", "Thailand", "Timor-Leste", "Togo", "Tokelau", "Tonga", "Trinidad and Tobago", "Tunisia", "Turkey", "Turkmenistan", "Turks and Caicos Islands", "Tuvalu", "U.S. Minor Outlying Islands", "Uganda", "Ukraine", "United Arab Emirates", "United Kingdom", "United States", "Uruguay", "Uzbekistan", "Vanuatu", "Venezuela", "Vietnam", "Virgin Islands, British", "Virgin Islands, U.S.", "Wallis and Futuna", "Western Sahara", "Yemen", "Zambia", "Zimbabwe"]
Postal Code or Zip Code Specifies the postal code of the civic address.
  • Field Name: Address.PostalCode
  • Type: String
Latitude Specifies the angular distance of a place north or south of the earth's equator.
  • Field Name: Address.Latitude
  • Type: String
Longitude Specifies the angular distance of a place east or west of the meridian at Greenwich, England.
  • Field Name: Address.Longitude
  • Type: String
Locations Group Assigned by FDP
  • Field Name: Locations
  • Type: Object
Locations
  • Field Name: locations.[n]
  • Type: Array
Name Specifies an administrator defined description of the location. For example, "2nd Floor Cafe", "Main Lobby", or "Office 250".
  • Field Name: Locations.locations.[n].Location
  • Type: String
ELIN Specifies the Emergency Location Identification Number. This is used in Direct Routing EGW scenarios.
  • Field Name: Locations.locations.[n].Elin
  • Type: String
Is Default
  • Field Name: Locations.locations.[n].IsDefault
  • Type: Boolean
Ports
  • Field Name: ports.[n]
  • Type: Array
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
  • Field Name: Locations.locations.[n].ports.[n].ChassisId
  • Type: String
  • Target: device/msteamsonline/CsOnlineLisSwitch
  • Target attr: ChassisId
  • Format: uri
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
  • Field Name: Locations.locations.[n].ports.[n].PortId
  • Type: String
Description Specifies the administrator defined description of the Location Information Service subnet.
  • Field Name: Locations.locations.[n].ports.[n].Description
  • Type: String
Subnets
  • Field Name: subnets.[n]
  • Type: Array
Subnet The IP address of the subnet. This value can be either IPv4 or IPv6 format.
  • Field Name: Locations.locations.[n].subnets.[n].Subnet
  • Type: String
  • Pattern: ((^\s*((([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]|25[0-5])\.){3}([0-9]|[1-9][0-9]|1[0-9]{2}|2[0-4][0-9]|25[0-5]))\s*$)|(^\s*((([0-9A-Fa-f]{1,4}:){7}([0-9A-Fa-f]{1,4}|:))|(([0-9A-Fa-f]{1,4}:){6}(:[0-9A-Fa-f]{1,4}|((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3})|:))|(([0-9A-Fa-f]{1,4}:){5}(((:[0-9A-Fa-f]{1,4}){1,2})|:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3})|:))|(([0-9A-Fa-f]{1,4}:){4}(((:[0-9A-Fa-f]{1,4}){1,3})|((:[0-9A-Fa-f]{1,4})?:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(([0-9A-Fa-f]{1,4}:){3}(((:[0-9A-Fa-f]{1,4}){1,4})|((:[0-9A-Fa-f]{1,4}){0,2}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(([0-9A-Fa-f]{1,4}:){2}(((:[0-9A-Fa-f]{1,4}){1,5})|((:[0-9A-Fa-f]{1,4}){0,3}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(([0-9A-Fa-f]{1,4}:){1}(((:[0-9A-Fa-f]{1,4}){1,6})|((:[0-9A-Fa-f]{1,4}){0,4}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(:(((:[0-9A-Fa-f]{1,4}){1,7})|((:[0-9A-Fa-f]{1,4}){0,5}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:)))(%.+)?\s*$))
Description Specifies the administrator defined description of the Location Information Service subnet.
  • Field Name: Locations.locations.[n].subnets.[n].Description
  • Type: String
Switches
  • Field Name: switches.[n]
  • Type: Array
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
  • Field Name: Locations.locations.[n].switches.[n].ChassisId
  • Type: String
Description Specifies the administrator defined description of the Location Information Service subnet.
  • Field Name: Locations.locations.[n].switches.[n].Description
  • Type: String
Wireless Access Points
  • Field Name: waps.[n]
  • Type: Array
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).
  • Field Name: Locations.locations.[n].waps.[n].BssId
  • Type: String
Description Specifies the administrator defined description of the Location Information Service subnet.
  • Field Name: Locations.locations.[n].waps.[n].Description
  • Type: String