Setting up a new Enterprise requires the customer’s Global Admin and Level365.
The Global Admin should have Skype for Business Administrator and the Teams Administrator enabled on their Microsoft account.
Preparation Steps:
- Each user will need the correct Microsoft licenses as well as a spare for the Direct Routing setup. For more information on the licenses: https://support.level365.com/hc/en-us/articles/360060509371-Supported-Microsoft-Licenses-for-Teams-Connector
- Level365 will need to Create an Office Manager account in the customer’s domain with the extension being c2t
- Level365 will need to Create an Oauth Account for the customer within NMS.
Name it c2t-DomainName (ex: c2t-acmelevel365.org). Take note of the Client ID and Client Secret
The name of each section indicates which party (Level365 or Global Admin) needs to complete the outlined steps.
Login to https://service.connecttoteams.com/. You will be directed to the Enterprises tab.
Click Add Enterprise to setup a new customer.
- Enterprise Name – Enter the Company Name (exp: Acme Level365).
- Enterprise Admin Email ID – This is the email address of the Global Admin.
- User limit – Sets how many users can be in the Enterprise. Leave blank for Unlimited.
- PBX Music on Hold – Check if you want to have Teams send a SIP Refer request to the platform to invoke the platforms MoH. (New feature that hasn’t been used yet)
- Access SIP Data – Check to have Enterprise Admin to access to the SIP CDR. (Check this box)
- Request Consent for Enterprise Management – Check to have the Enterprise Admins be able to make Provisioning action (adds and changes) without Global admin approval. (Check this Box)
- Billing Reference – Values input here will be available in billing reports.
- SBC Region – Select SBC region, US East 1 is the default that should be put here.
- Service – Select the Service wanted, put PBX. The "PBX Type" will now appear directly below.
- PBX Type – in the unassigned PBX types select Netsapiens and move it to the Assigned PBX Types.
- Add New Extensions – Allows auto provision of new extension by Admin or Enterprise Admin via API (leave unchecked)
- Allow External Number – Allows the Enterprise admin to be able to use external numbers that aren’t on the platform. (check this box)
Once all the information has been entered click the Submit button. This will send out an invitation email to the Customer's Global Administrator.
Once the Global Admin receives their invitation email, they will have to click complete.
They will be taken to the Enterprise Portal https://enterprise.connecttoteams.com/
The Global admin will need to sign into their account and grant Teammate the requested permissions.
During this process, if the customer has multiple user groups, the Global Admin will get a screen to select which user group they want pulled in. If they want all user groups to be pulled in, leave the box blank.
The Global Admin will now be presented with the Enterprise Dashboard.
Ensure the client has the correct Microsoft Office licensing.
They will need to have at least 1 spare UNASSIGNED User license+Phone System, or a comparable add-on license that allows Direct Routing. Available relevant licenses will be displayed on the Direct Routing page.
Navigate to Directing Routing on the Left-hand side.
Under Setup Direct Routing Details, select the desired Gateway. (this will be the SBC Region that is configured during Enterprise Add). Then click the Complete Direct Routing.
The Verify Tenant pop-up will appear. This will verify the connection to the DNS Provider and will also validate licenses.
Click Complete Direct Routing as soon as it is done with the verification.
Direct Routing usually takes a few minutes to be setup. This can also take up to 24-48 hours to be completed.
If the direct routing process completes and the Calling Enabled indicator is still showing as red, initiate the direct routing process by clicking on the “Finish” button on the right side of the Direct Routing page.
When Direct Routing is completed, you will see this on the Dashboard.
Once direct routing is completed the Global Admin can reclaim the user and phone system license from the Direct Routing user.
On the Dashboard, the Global Admin can now press the red Grant Consent buttons for everything requested.
Have the Global Admin do these one by one. Do not move on to the next service until the previous one shows completed.
- Contact Service - This will sync Outlook and Microsoft Organization contacts.
- Presence Monitoring - Approve the use of Presence data from Microsoft Teams to the Teams Application.
- Allow Management by Service Provider – Grant consent for Level365 to perform Enterprise Provisioning actions.
- Microsoft Teams CDR – Allows Debug Calls from the Dashboard.
The Global Admin is done until Level365 configures the Teams PBX Application.
Level365 will now need to add the Netsapiens PBX information, this can be done while the Global Admin is Granting Consent.
Navigate to PBX on the left side and press Add PBX on the right.
You will be taken to PBS Settings Screen.
General Setting Tabs
- PBX Type - Select Netsapiens as the PBX type.
- PBX Location – Name the location based off previously selected SBC Region. (ex. East)
- PBX DNS Lookup type – Leave this as Host.
- PBX Outbound Transport type – Leave this as UDP.
- PBX SIP Domain – make this the Domain of the customer (ex. acmelevel365.org)
- PBX SIP Domain Proxy – set this to be, ind-core3.365sip.com.
- Voicemail Feature Code – leave this as *62
- PBX SIP Domain Proxy Port – leave this as 5060
- Codecs – Leave this as G.711 A-law and G.711 U-law.
- Topology Hiding – Check this box
- Reg Expires – Leave this as 600.
- Delay ACK Relay – Leave this Checked.
- Caller Name Policy – Leave this as Transparent.
- Caller ID on Forwarded Calls – Leave as User’s Caller ID
Advanced Setting Tabs
- Portal Authorization URL – set this to be https://api.365sip.com/ns-api/oauth2/token/
- Client ID – set this to the Oauth Client ID setup earlier. (ex. c2t-acmelevel365.org)
- Client Secret – set this to the Oauth Client Secret setup earlier
- API Access Username – set this to be the Office Manager account username setup earlier. (ex. c2t@acmelevel365.org)
- API Access Password - set this to be the Office Manager account password that was setup earlier
- Autofill SSO Settings – Leave this unchecked
Once all PBX information has been configured you can press Save Settings to finish the PBX setup.
To deploy the PBX Application, navigate to App Management.
Once the page loads scroll down to the bottom of the page and Check 2 of the 3 boxes.
- Show card on Inbound/outbound call – Check
- Show card for new Voicemail – Check
- Show Utility card on the Inbound/Outbound call – Uncheck
Click the Save PBX Application Template.
The PBX application for the Enterprise will now be built out.
This process can take some time to complete. Once it is completed the Global Admin will have a new Sync PBX App button on the Dashboard to activate.
Once the Global Admin clicks Sync PBX App, Teammates will start deploying the application to the client’s MS Teams Tenant. This process can take some time to complete.
Once all steps outlined above are completed, the Global Admin is no longer needed, and users can now be added to the Teammates portal.
For adding users, see the Add Users article: https://support.level365.com/hc/en-us/articles/24093638150811