[Index]

Model: device/msteamsonline/CsTenantTrustedIPAddress

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

Model Details: device/msteamsonline/CsTenantTrustedIPAddress

Title Description Details
IP Address * This must be a unique and valid IPv4 or IPv6 address. If no mask is provided the maskbits is set to 32 by default
  • Field Name: Identity
  • 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*$))
Mask IPv4 format subnet accepts maskbits from 0 to 32 inclusive. IPv6 format subnet accepts maskbits from 0 to 128 inclusive.
  • Field Name: MaskBits
  • Type: Integer
  • Maximum: 128
Description
  • Field Name: Description
  • Type: ["String", "Null"]