DEVELOPERPACK 189a915c-fe4f-4ffa-bde4-85b9628d07a0 OFFICE 365 ENTERPRISE E4 ENTERPRISEWITHSCAL 1392051d-0cb9-4b7a-88d5-621fee5e8711 OFFICE 365 F1 DESKLESSPACK 4b585984-651b-448a-9e53-3b10f069cf7f OFFICE 365 GCC G3 ENTERPRISEPACK_GOV 535a3a29-c5f0-42fe-8215-d3b9e1f38c4a OFFICE 365 SMALL BUSINESS ESSENTIALS SMB_BUSINESS_ESSENTIALS dab7782a-93b1-4074-8bb1-0e61318bea0b OFFICE 365 SMALL BUSINESS PREMIUM SMB_BUSINESS_PREMIUM ac5cef5d-921b-4f97-9ef3-c99076e5470f Spe E3 Rpa1 SPE_E3_RPA1 c2ac2ee4-9bb1-47e4-8541-d689c7e83371 Standardpack Gov STANDARDPACK_GOV 3f4babde-90ec-47c6-995d-d223749065d1 Standardwoffpack Iw Faculty STANDARDWOFFPACK_IW_FACULTY 78e66a63-337a-4a9a-8959-41c6654dfb56 Standardwoffpack Iw Student STANDARDWOFFPACK_IW_STUDENT e82ae690-a2d5-4d76-8d30-7c6e01e6022e Standardwoffpack Student STANDARDWOFFPACK_STUDENT 314c4481-f395-4525-be8b-2ec4bb1e9d91 Phone System or comparable add-on Licenses These must be combined with a non-inclusive license from the list above. Product_Name SKU GUID Mcocap Faculty MCOCAP_FACULTY 420c7602-7f70-4895-9394-d3d679ea36fb Mcocap Gov MCOCAP_GOV

Overview When the Service Provider needs to rectify any issues with the enterprise's tenant, a request can be made to re-establish the consent. From the ConnecttoTeams 2.13.0 release, the Service Provider may now revoke or reset the Microsoft permissions consent on the following Enterprise Admin action items: UserSync Service Contacts Service Presence Monitoring Microsoft Teams CDR Once revoked, the Enterprise Admin will see again a request to grant consents in the Enterprise Dashboard. Revoking a Microsoft Permission Consent The Service Provider must do the following to revoke a Microsoft permission consent: Log in to the Service Portal. From the Reseller Menu, navigate to Reseller > Enterprises . From the Enterprises table, click on the name of subject enterprise. This will lead you to that enterprise’s Dashboard . From the Enterprise Admin Action Items table, click the Revoke hyperlink of the setting to be reset. Results : Once revoked, this

Add ConnecttoTeams to your White List (trusted traffic) Whitelist all core-infrastructure IP addresses. Core Infrastructure ITEM IP ADDRESS PROTOCOL API Gateway 52.184.185.243 HTTPS (Reverse Proxy) Edge Proxy (SIP) 13.68.254.158 TCP/UDP/TLS Edge Proxy (SIP) 20.115.6.243 TCP/UDP/TLS Edge Proxy (SIP) 52.255.184.52 TCP/UDP/TLS Edge Proxy (SIP) 13.68.233.171 TCP/UDP/TLS Edge Proxy (SIP) 20.59.120.227 TCP/UDP/TLS Edge Proxy (SIP) 20.59.124.13 TCP/UDP/TLS Edge Proxy (SIP) 20.124.236.139 TCP/UDP/TLS Edge Proxy (SIP) 40.117.126.112 TCP/UDP/TLS Edge Proxy (SIP) 40.117.126.110 TCP/UDP/TLS Edge Proxy (SIP) 23.29.127.82 TCP/UDP/TLS Port Ranges RTP: 16000-16999. SIP Signalling: 5060.

Overview PBX Users using Microsoft Teams now have the ability to disable incoming calls when they are unavailable on MS Teams. When this Pause Inbound Calling Based on Teams Presence feature is activated, incoming queue calls will not ring through to unavailable users to avoid the call being answered by such users’ Teams voicemail, and thereby allowing the call to reach other users in the queue. With ConnecttoTeams version 2.13 onwards, the system enables an Enterprise to set up their PBX platform to activate the Pause Inbound Calling based on Teams Presence feature for users in their system. Additionally, individual users also have the option to manage this feature using the configuration page of the ConnecttoTeams PBX App on MS Teams. Configuring the Pause Inbound Calling Feature The Pause Inbound Calling based on Teams Presence feature can be enabled right away when adding new PBX. See the PBX Configuration

Important Considerations There are several important considerations when planning for tenants who may want to take advantage of this dynamic emergency calling feature: In the event of an emergency call where the PIDF/LO is provided by Microsoft, the packet size will be too large for UDP transport. Therefore, it is important to select one of the TCP transport options when configuring your PBX or Trunk connection: UDP/TCP (uses TCP when packet size exceeds 1300 bytes), TCP, or TLS. When the tenant has configured the location and policies for a user, any emergency call will have PIDF/LO data incorporated in their SIP INVITE. It is therefore imperative that the customer test to verify that the calling configuration (PBX/SBC/Carrier) supports this additional data and will complete the call to the correct endpoint. End-users can check that Teams has their correct emergency location by looking in the

using SRV here is a more detailed article about using DNS-SRV with the ConnecttoTeams Connector. PBX Outbound Transport Type: UDP, TCP, TLS or UDP/TCP. Most PBXs use UDP. The UDP/TCP option allows SIP traffic to use UDP when possible, but it will use TCP when necessary due to packet size. We will attempt to use UDP for SIP signaling when we are initiating a flow and the initial INVITE is less than 1300 bytes. In some call situations, this limit is exceeded and UDP traffic would likely fragment and lead to failed calls. In these cases, we will attempt to use TCP. Note : If you are using Host lookup, your PBX must support both UDP and TCP on the same endpoint and port. If you are using SRV lookup then you must have both udp and tcp DNS records configured correctly. PBX SIP Domain: The domain you