WEBVTT

00:00.000 --> 00:13.000
Thank you very much.

00:13.000 --> 00:15.000
Great to be here again.

00:15.000 --> 00:18.000
Last year, I couldn't make it, but this year,

00:18.000 --> 00:20.000
happy really, as I said, to be here.

00:20.000 --> 00:21.000
Yeah, my name is Henning.

00:21.000 --> 00:23.000
I'm going to give you a quick update about the

00:23.000 --> 00:27.000
channel 6.0, which I've released.

00:27.000 --> 00:29.000
That's your agenda.

00:29.000 --> 00:31.000
You want to send us this about me?

00:31.000 --> 00:34.000
What is your channel and case you don't know it?

00:34.000 --> 00:37.000
Of course, this is short, because we don't have much time.

00:37.000 --> 00:40.000
Some statistics for the release.

00:40.000 --> 00:43.000
This shows some highlights, which are particularly important

00:43.000 --> 00:46.000
in my opinion, in our opinion,

00:46.000 --> 00:50.000
highlight development changes, especially for the

00:50.000 --> 00:53.000
channel that work no close to this channel.

00:53.000 --> 00:56.000
Yeah, some important changes, and also

00:56.000 --> 00:59.000
opposition changes.

00:59.000 --> 01:02.000
Okay, yeah, I started 2007 doing this,

01:02.000 --> 01:05.000
also a piece of, yeah, since some years

01:05.000 --> 01:08.000
are also a company doing, yeah, so this is

01:08.000 --> 01:10.000
consulting in this area.

01:10.000 --> 01:15.000
As many people here, yeah, we work with many

01:15.000 --> 01:19.000
people in Europe worldwide for these kind of stuff.

01:19.000 --> 01:21.000
There's canal, canal, yes.

01:21.000 --> 01:23.000
Yeah, one of the plumbing of the internet,

01:23.000 --> 01:26.000
plumbing of terminate cell phone systems.

01:26.000 --> 01:30.000
It used for SPC functions, like security,

01:30.000 --> 01:33.000
low balancing, topology hiding on the edge of the

01:33.000 --> 01:35.000
network, implementing applications,

01:35.000 --> 01:39.000
classical phone registration, proxy,

01:39.000 --> 01:43.000
call routing, classical voice or peak applications,

01:43.000 --> 01:47.000
of course, presence, dialogue state,

01:47.000 --> 01:51.000
voice mail, other information that you might need

01:51.000 --> 01:54.000
and 120 transfer to use.

01:54.000 --> 01:59.000
We just saw a talk about, yeah,

01:59.000 --> 02:02.000
client layer of the RTC, because you want to

02:02.000 --> 02:04.000
also want to have a server for that.

02:04.000 --> 02:06.000
Maybe you have proprietary cloud

02:06.000 --> 02:09.000
confluence, like teams for example,

02:09.000 --> 02:11.000
you want to interact with.

02:11.000 --> 02:14.000
You can come out with a use camera to translate

02:14.000 --> 02:17.000
between cloud environments and your on-premise infrastructure.

02:17.000 --> 02:19.000
And then of course, you have to tell

02:19.000 --> 02:22.000
good word, IP multimedia subsystem,

02:22.000 --> 02:26.000
IMS or NGN, yeah, you want to provide

02:26.000 --> 02:30.000
different IMS functions to interact with

02:30.000 --> 02:36.000
like a mobile corner to work or like an IMS telephone network.

02:36.000 --> 02:38.000
Yeah.

02:38.000 --> 02:40.000
So, can I use time-based release?

02:40.000 --> 02:43.000
So, yeah, last week we released 6.0,

02:43.000 --> 02:46.000
the 27th major release of the 24 years of

02:46.000 --> 02:48.000
project activity, the timeline is here.

02:48.000 --> 02:51.000
So, we have done some iterations over the years,

02:51.000 --> 02:54.000
different names, some quirks in the way.

02:54.000 --> 02:57.000
More than 30 people, more than 40 contributors,

02:57.000 --> 02:59.000
or yeah, contributed more than 1,000,

02:59.000 --> 03:02.000
8,000 changes, almost 40,000 changes,

03:02.000 --> 03:04.000
no, the master branch.

03:04.000 --> 03:07.000
I think it also has the project is going well,

03:07.000 --> 03:11.000
that I'll bring a little high continued pace over the years.

03:11.000 --> 03:14.000
Yeah.

03:14.000 --> 03:16.000
Then it was also here.

03:16.000 --> 03:18.000
The first topic was especially developed

03:18.000 --> 03:20.000
from him, I think.

03:20.000 --> 03:22.000
One of the major highlights in my opinion is that

03:22.000 --> 03:25.000
we have now UDP receiver mode for

03:25.000 --> 03:29.000
multitreading on the past or currently

03:29.000 --> 03:31.000
camera uses a more classical,

03:31.000 --> 03:33.000
traditional process model for

03:34.000 --> 03:36.000
especially interesting for MS.

03:36.000 --> 03:38.000
The first point we support now,

03:38.000 --> 03:41.000
aka version one, MD5,

03:41.000 --> 03:44.000
for interacting with MS systems.

03:44.000 --> 03:46.000
You don't need an HSS server,

03:46.000 --> 03:48.000
just server and more.

03:48.000 --> 03:51.000
If you deploy your server and container

03:51.000 --> 03:52.000
environments, for example,

03:52.000 --> 03:55.000
you make it much more easy to template.

03:55.000 --> 03:58.000
Yes, it's a configuration.

03:58.000 --> 04:00.000
You can now interact more easily with

04:00.000 --> 04:04.000
the configuration by templates.

04:04.000 --> 04:06.000
The zip device is still used.

04:06.000 --> 04:08.000
Unfortunately, MD5 in

04:08.000 --> 04:10.000
Yeah, authentication algorithms,

04:10.000 --> 04:12.000
so we have now the possibility to

04:12.000 --> 04:16.000
yeah, specify on a pair device level.

04:16.000 --> 04:20.000
Authentication algorithm to use.

04:20.000 --> 04:23.000
Yeah, many variables, many new transformation

04:23.000 --> 04:25.000
were added as well to make the language

04:25.000 --> 04:27.000
the configuration language more powerful.

04:27.000 --> 04:29.000
And of course, there are many, many changes

04:29.000 --> 04:31.000
to existing modules,

04:31.000 --> 04:33.000
that are too much, I cannot list them all.

04:33.000 --> 04:35.000
I put the link to the

04:35.000 --> 04:37.000
change lock or the

04:37.000 --> 04:41.000
description of all the new model features

04:41.000 --> 04:43.000
here on this slide.

04:43.000 --> 04:45.000
Important for developers,

04:45.000 --> 04:48.000
in particular is a switch to C-Make.

04:48.000 --> 04:50.000
This was a large effort.

04:50.000 --> 04:53.000
Handled from Xenophon in the project mainly

04:53.000 --> 04:56.000
with help of packaging colleagues, of course,

04:56.000 --> 04:59.000
such a Victor.

04:59.000 --> 05:02.000
In the past we used, we still used

05:02.000 --> 05:04.000
make files in the existing releases.

05:04.000 --> 05:06.000
We see make it's now much easier to

05:06.000 --> 05:08.000
integrate this modern integrated

05:08.000 --> 05:11.000
development into modern development environments.

05:11.000 --> 05:13.000
Some people don't like to develop

05:13.000 --> 05:14.000
an common line.

05:14.000 --> 05:16.000
Maybe they want to have something like visual

05:16.000 --> 05:18.000
studio or something like that.

05:18.000 --> 05:20.000
And of course, it's also easier to

05:20.000 --> 05:23.000
extend the code base now and

05:24.000 --> 05:26.000
develop new modules and the

05:26.000 --> 05:27.000
like.

05:27.000 --> 05:29.000
Again, I put the link to the tutorials

05:29.000 --> 05:30.000
here.

05:30.000 --> 05:32.000
Here you find more information in

05:32.000 --> 05:34.000
case you are interested how to build

05:34.000 --> 05:35.000
with C-Make, how to extend

05:35.000 --> 05:38.000
with C-Make systems etc.

05:38.000 --> 05:41.000
Some generic infrastructure, mostly important

05:41.000 --> 05:43.000
if you develop modules and we move

05:43.000 --> 05:44.000
the libraries, the libraries we are

05:44.000 --> 05:46.000
moved into the core, directly,

05:46.000 --> 05:48.000
makes it easier for packaging and

05:48.000 --> 05:50.000
particular on DBR and we had some issues

05:50.000 --> 05:51.000
there.

05:52.000 --> 05:55.000
And so overhauled the module interface.

05:55.000 --> 05:58.000
Some memory management changes

05:58.000 --> 05:59.000
where done.

05:59.000 --> 06:02.000
Some module interface changes

06:02.000 --> 06:04.000
where done with some naming

06:04.000 --> 06:06.000
some refactoring just to make

06:06.000 --> 06:09.000
it easier to develop modules to

06:09.000 --> 06:11.000
and then unnecessary steps.

06:11.000 --> 06:16.000
Five new modules for

06:16.000 --> 06:17.000
edit in this release.

06:17.000 --> 06:19.000
I already talked about

06:19.000 --> 06:21.000
NG HPP2.

06:21.000 --> 06:23.000
Then there's a new IMF module,

06:23.000 --> 06:25.000
IMF QS and PM.

06:25.000 --> 06:27.000
It's an enhanced version of the IMF QS

06:27.000 --> 06:29.000
standard.

06:29.000 --> 06:31.000
Then there's presence on the

06:31.000 --> 06:32.000
GF QS.

06:32.000 --> 06:35.000
It's a special presence protocol for

06:35.000 --> 06:38.000
the particular phones, which use

06:38.000 --> 06:40.000
this for device key.

06:40.000 --> 06:42.000
Synchronization.

06:42.000 --> 06:44.000
There's PVT, PL,

06:44.000 --> 06:46.000
template files.

06:46.000 --> 06:50.000
You can install your data from

06:50.000 --> 06:53.000
top-quality hiding into an

06:53.000 --> 06:55.000
H-table.

06:55.000 --> 06:58.000
If you don't like to use, for example,

06:58.000 --> 07:01.000
my secret database on the latest database.

07:01.000 --> 07:04.000
Also, some of the modules were moved to

07:04.000 --> 07:06.000
archive repository in case you

07:06.000 --> 07:07.000
are missing or not.

07:07.000 --> 07:09.000
For several reasons, we moved them to

07:09.000 --> 07:15.000
an archive repository just to

07:15.000 --> 07:18.000
clean up the code base a bit a bit.

07:18.000 --> 07:20.000
For operations,

07:20.000 --> 07:21.000
some important changes.

07:21.000 --> 07:23.000
This picture, I think, also

07:23.000 --> 07:25.000
Daniel implemented that is now

07:25.000 --> 07:28.000
supports an overload control of

07:28.000 --> 07:30.000
C7339.

07:30.000 --> 07:32.000
You can load the

07:32.000 --> 07:33.000
communication information from files.

07:33.000 --> 07:35.000
For example, if you have an air gap

07:35.000 --> 07:36.000
infrastructure in some

07:36.000 --> 07:37.000
environments.

07:37.000 --> 07:40.000
It has better statistics for

07:41.000 --> 07:44.000
accessibility and databases on the

07:44.000 --> 07:45.000
demand.

07:45.000 --> 07:48.000
The old module and you load with

07:48.000 --> 07:52.000
PVT, PVT, you can

07:52.000 --> 07:53.000
basically load directly.

07:53.000 --> 07:54.000
This is good.

07:54.000 --> 07:55.000
For example, don't need to

07:55.000 --> 07:57.000
pour database tables just

07:57.000 --> 07:58.000
do it on your side.

07:58.000 --> 08:00.000
You can do it by

08:00.000 --> 08:01.000
this not in the old

08:01.000 --> 08:02.000
DVD.

08:02.000 --> 08:03.000
You have to use old module

08:03.000 --> 08:05.000
plus the scalops to fetch the

08:05.000 --> 08:06.000
field you own.

08:06.000 --> 08:07.000
It's possible.

08:08.000 --> 08:10.000
You can load your own

08:10.000 --> 08:11.000
off.

08:11.000 --> 08:13.000
OK.

08:13.000 --> 08:15.000
Other questions?

08:15.000 --> 08:16.000
No.

08:16.000 --> 08:17.000
OK.

08:17.000 --> 08:19.000
Then, thank you very much.