pre-requisite that will be detailed on SIP Manager shortly, but isn’t yet on
the list above, is that there must be a ‘spare’ Microsoft 365 licence that can
be used during the initial configuration as you complete the wizard. By ‘spare’ we mean that at Stage 7 of the
purchase wizard it will not be available to you to assign to a user. The detail
of how you use this licence during the configuration of your tenant is listed
in the help guide in Stage 4 - ’Domain Verification’. After the initial configuration has been
completed this licence can be recycled to be assigned to a user.
In the Microsoft 365 Admin centre it is possible to see all
active users and the licences assigned to them.
Viewing a single user <See Screenshot below and the licences assigned to them
also allows an administrator to confirm that there an unassigned, ‘spare’
licence available. In this example above
we can see that there are 2 x ‘Microsoft 365 Business Basic’ and 2 x ‘Microsoft
365 Business Standard’ licences available.
Issues that have meant the Purchase wizard was not completed successfully include:
o Not meeting all the pre-requisites.
o The correct licences (with phone system) assigned to users but they have had a Microsoft Calling Plan assigned.
The last bullet in the list of pre-requisites above is to say that Teams is configured in Azure correctly. Sometimes, as per the pre-requisite, Teams has been successfully used by a User but it is still not configured. We recommend a period of at least 24 hours from when a user sends the first message or making the first Teams-to-Teams call on a fresh Teams tenant before setting up Direct Routing via the purchase wizard
o ‘Name’ – A reference that means something to you (you can add anything that you want)
‘Number Source’ NB – The only option currently
available in the Teams section of SIP Manager is ‘New Numbers’. Porting
numbers in via
SIP Manager and using them for Teams Direct Routing is a
simple process (* – see below for
Port Numbers from a
Microsoft Calling Plan
Port Numbers from
The reason that there are 2 porting
options is because numbers that are being used against a Microsoft calling plan
need to be treated differently to numbers that are with any other provider. This is to avoid an interruption in service.
o ‘Admin Domain’ – The default domain within your Microsoft 365 tenant
‘Select Calling Plans’ – This is where
you select the type and quantity of the calling plans you want to order
These are for
‘User Accounts’ (i.e. users making and receiving calls) as well as ‘resource
accounts’ (Call Queues and Auto-Attendants).
As per the highlighted part of the screenshot above, a
description of each plan appears when you select it. For full details and pricing of each option
on this dropdown please visit the Jola extranet price list here and use
the filter to select ‘6. Microsoft Teams’.
**** If the
Product you want to order is not listed (e.g. one of the Unlimited
International local calls packages) please contact your Jola AM *****
The following is an explanation of
the process to follow in SIP Manager if porting in numbers to be used with
As you can see, there is a separate
Porting section on SIP Manager <See Screenshot below>. The pages that you complete here will be the
same as the ones that you will use when porting is incorporated into the Teams
The steps to follow are:
1) In the Teams section of SIP Manager complete the Purchase wizard (i.e. all 8 stages) purchasing new number(s) in Section 2 - ‘Tenant Details’.
Purchasing just a
single new number (or as many numbers as you want to configure with calling
plans whilst the port completes) will allow you to complete the Teams Purchase
wizard. This means you can test Teams Direct Routing and avoids the risk of
there being issues configuring the tenant when you want to start using the
2) After completing the Teams Purchase wizard (Stage 8 of the guide) move to the Porting section of SIP Manager (highlighted in pink - screenshot above) and then click on the ‘NEW’ sub-section. Complete the pages here to initiate the port. You will later receive confirmation that the port has been authorised and the date that the port will complete.
**** You can choose when to do the
next steps ****
When you get confirmation
that the port has been authorised.
After the port has
because the ported numbers will be available in the ‘Manage Tenants’ section
from when the port has been authorised. You can Synch the users before the port
completes without impacting the phone system the customer is using prior to the
port completion date.
3) When the port is authorised the numbers will be available in the ‘MANAGE TENANTS’ sub-section of the Teams section of SIP Manager <See Screenshot below>
4) You can add as many Users and Resource accounts (Auto Attendants & Call Queues) as you have purchased Calling Plans and have available numbers. As you add each row you will see the synch status is an amber ‘Pending’ warning label.
5) This is also where you can remove any users with temporary new numbers that you want to replace with a ported number. To do so click on the red box on the right for this user. You can then add them again, by filling in the row with empty fields and clicking on the green ‘+’ button.
When you have added as
many rows as you need, click on the ‘Log in to Microsoft’ button. When you are logged in you will then see the
option in SIP Manager to ‘Synch’. After
clicking ‘Synch’ it may take a couple of minutes to complete after which the
Amber ‘!’ warning symbols will change to green ticks.
If you are
porting numbers that are being used with Microsoft Calling Plans
Each port has a user with
a MS calling plan attached.
This calling plan must
be removed from the user to allow them to have a Jola Direct Routing calling
Once the MS Calling Plan
has been removed the service will cease to be available and so it is
recommended that this is only done as a final step (when the port completes just
before you synch Users in SIP Manager as per the instructions above).
The customer should be
informed that there will be minor down time during the removal of calling
plans, creation of users and port completion.
To reduce downtime if
you have lots of users, you can add them in the ‘Manage Tenant section once the
port has been approved (see previous screenshot) but DO NOT synch the
tenant with Microsoft at this stage as this will automatically remove the
o Sync the users when the ports have completed AND the calling plan has been removed from each user.
o The FQDN (Fully Qualified Domain Name) has been automatically generated by SIP Manager at this stage and is displayed on this screen (it is shown again on the next screen). This is used to authenticate the trunk / Direct Routing connection between the Jola Teams Direct Routing platform and the Microsoft Teams platform.
o The hyperlink takes you to the ‘Jolaphone, Teams Direct Routing, SIP trunks, broadband, PSTN, Terms & Conditions document on the Jola extranet should you wish to review before ticking the box to confirm you agree to these Terms & Conditions.
The ‘Next’ box appears when you have agreed to
the T&Cs and when you click this the box below appears to inform you that
SIP Manager is performing tasks <See Screenshot below>
There is a slight delay whilst SIP Manager configures the Jola Microsoft
approved SBC (Session Border Controllers).
NB – The warning message on this screen states:
‘Due to increased demand it might take up to 24 hours to fully set up user in Teams. Until then, you won’t be able to assign Teams policies to them, and they might not have access to Teams features like calling and audio conferencing’.
You will then reach the screen below which is where SIP Manager is automatically executing the Powershell commands <See Screenshot below> .
Below is the final screen. Teams Direct Routing is now configured for the Users and Resource accounts that you have specified. You can test that they work however, as per the message below, if Direct Routing does not work straight away keep testing for the next 24 hours. It would be unusual for there to be a delay of anything close to 24 hours.