TITLE: [MUSIC]
ANDRE RINK: Hi guys. Andre Rink from DT.
Today's topic is about the acceleration of
Operator Connect with Azure
based microservices in detail.
Did you know, the Keystone
is the oldest Cloud service in the world?
Having this in mind, we want to show how we
move this Cloud service to the next level.
In the session, we want to copy a few things.
First of all, let's start with the challenge DT face in
the cloudification of voice services
with one important question.
How we define voice as a Cloud service?
Microsoft Teams is the fastest growing UC solution,
running in one of the best hyperscale.
Therefore, it's for sure DT
need a hyperscale voice platform.
How we built that platform and
why we used Azure to run this.
The customer experience is
the most important part in all of our decision.
That's the reason why we have put
a self-service portal on top of this platform,
which we want to show later.
A few years ago,
DT had the challenge for voice cloudification.
Let's have a look at these challenges.
The Classic Telco is focused on delivering
single voice products and not complete voice solutions.
Today customer is expecting more,
starting with the voice services
and ending with incomplete service
offering for UC solutions at Microsoft Teams.
Voice service provisioning is a manual process.
Product delivery took up to six weeks
due to mail order processes.
Voice services are access
bundle products and avoid Cloud based voice trunking.
Therefore, we need to decouple the voice services and
define them as a microservice.
Think this in mind, there are three outcomes.
We need to change the perspective,
think Telco as a platform.
We need to automate provisioning processes end-to-end,
which also means we need to
migrate all our voice networks to an ALL-IP approach.
Last, we need to decouple
the voice services to define them as a microservice.
As we tackle these issues,
we sorted out through findings.
Voice is a microservice,
that's why we need to move
all voice service workloads
to Cloud native architecture.
Microservices needs to be in the Cloud,
and that's the reason why we moved
all hardware based components into the Cloud,
which support as
an automatic and rapid scaling of a species.
We understand voice as an additional API, therefore,
we implement the provisioning of voice into
Google services into our existing DevOps processes.
Let's go a little bit more into details.
Mr. Hyperscale had a vision in mind.
We have develop suite services.
Sip Trunk is a service as voices
Cloud-based service hosts in the DT Data Centers.
We see SBC as a service approach.
We've moved all SBC related services into the Cloud,
which opens the door for an automatic provisioning with
high flexible deployment of SBC service,
that's why our customers need them.
Instead of microservices, we are able
to speed up the deployment and provisioning processes.
As a generic API architecture,
we were able to integrate the operator connect
services within a few weeks.
Let's have a more closer look at this specific services.
Self Service Portal for DT customers
allow the creation of Sip Trunk within a few clicks.
A wizard has customers
creating Sip Trunk without being an expert.
Once the Sip Trunk is created and ready for service,
the customer can purchase Teams voice Add On.
This Add On triggers
a microservice which startup provisioning
services on all DT big end systems
which allows the customers to put
the Sip Trunk into service
for Microsoft Teams within a few minutes.
Let's go over to the most important microservice
, the SBC microservice.
The SBC Microservice configured
with the SBC cluster from DT
and make sure that the configuration and
interworking parameters are set automatically.
Once this is done, the SBC goes into service.
The Voice Interworking between
both worlds is certified by Microsoft
and the DT Test Center and
guarantees the best voice interoperability.
Last but not least,
we have the voice configuration API.
With the Configure Sip Trunk in the SBC services,
we need to manage a phone number of entities
in the M365 Tenant as well.
The microservice is responsible for the provisioning
of the phone numbers through the Operator Connect API.
The Service is controlling the complete lifecycle of
phone numbers and can handle
multiple phone number types like user,
conferencing or voice apps.
Bringing these pieces together,
we have a complete provisioning chain which allows us
to offer Teams Voice Services
as a Cloud native application.
As mentioned, the complete DT and
Teams Voice Service offering is based on
a self-service portal which allows
our customers to have Teams Voice
enabled in a few steps.
The customer don't need more than
a DT Sip Trunk service and a license M365 Tenant.
Now, let's give you a demo how easy it is to get
started with Teams still having DT voice services.
Let's have a look at the DT
self service portal which allow
our customers in very easy onboarding
from Microsoft Teams Operator Connect.
With three steps the customer is ready to go.
The first step we have to create a Sip Trunk,
but this demo, it's already done.
In the second step,
we need to establish to
a provisioning connection between
the DT and Microsoft Services.
The third and last step we need to
book the Teams Operator Connect Voice Add On.
Let's establish the connection
between the DT and Microsoft Services.
What is the customer need
the Admin credentials of M365 Tenant.
Once your log in was successful,
the customer must accept the content.
After this, provisioning connection is
established and we can move over to Step 3.
In the last step, we need to book
the Teams Operator Connect Add On.
After we have selected,
we need to go through the shopping cart.
Once done, we need to wait a few seconds.
Now we see that the trunk is registered
online and the phone numbers are available.
Now let's move over to the Teams setting
center and check if we have phone numbers.
Now we are on the Teams Admin center
and see that there are phone numbers available.
Let's select one of the phone numbers and assign
this phone number to one Licensed M365 user.
Once this step is successfully finished,
the Teams users are able to make phone calls via PSTN.
Now we are at the end of our session.
We hope you enjoyed it.
If you have any further questions,
don't hesitate to contact us.
Thanks for being our guest and stay tuned. Bye.