Okay, thank you and sorry for this little issue with my computer, which does die.
Thank you for being here. I know it's late. It's a final presentation of this room for today.
No, the final.
Oh, okay. Sorry.
Very busy day. A lot of people are here and it's nice.
Okay, so now we are here to discuss about how to intuit open source telephony into digital or workplace.
So my name is Jean Monier, I'm part of the lymphoNTIM and I'm with Alexander Jorgensen, which is developing the lymphoNTIM application in Grenoble.
So we are going to discuss about the telephony, maybe just give you some background on how it works.
And in part is how to integrate the telephony into a digital workplace, which is mainly the main topic of this talk.
And give you some explanation on how we can bring this two world, which are historically supported.
And give you an example of integration and to conclude try to explain why telephony is key to the adoption of digital workplace, especially in the open source world.
Okay, so let's introduce the lymphoNTIM project. So lymphoNTIM is at the beginning of soft client developed on Linux based on the SAP protocol.
SAP is the text based protocol developed at the end of the 90s and the very beginning on 2000 and the idea was to place calls over internet.
And so we work on the project starting in 2001 and our further action on Linux and then port on different operating systems.
And in 2010 we started a company with the original source of lymphoNTIM and model.
And the idea was to develop the project to have more functionality and more usage.
Okay, so now the company is based in Grenoble, the main contributor of the project are also based in Grenoble.
We have 22 engineers working in the project, software part, client part, server part and the library if you want to have your own implementation.
And today the application is available on also on iOS and Android and we have around one million downloaded application.
Okay, so it's for the introduction of us. So now digital workplace, what is about it's about mainly bringing all the, all the, the tools which are used on a day to day babies by, by worker to, for their task they want to edit document they need to exchange information by email most of the time.
Share documents, schedule meeting and also place phone calls.
So originally starting in 2001 to, I don't remember exactly when it was, but with the proprietary solution, they started to, to have their software available on the,
on the cloud, I don't remember exactly when office 365 started, but it was in the early 2000.
And many other, many other components were bring together also in the open source world, but the telephony was still not integrated.
And back to the proprietary solution, they all have their own solution for the telephony.
My question is for meetings chat, but also with Microsoft Teams phone, you can place phone calls, zoom is the same and Google as well.
Okay, so the role of the open source is to provide an option to bring an alternative to a proprietary solution like Microsoft.
And so the idea is that we need to have all the part of the functionality.
It's not worth if we only have text editing or spreadsheet or mail what we have is to have all the option, all the tools available together and in an easy way for the user to use them.
So open source standard, have many components which can be bring together to offer an alternative to Microsoft or proprietary solution.
And what we believe is that the telephony is part of this solution.
Okay, so now let's look at how it could be integrated telephony into digital workplaces.
So we will start with the first simple level of integration.
So here we have there on the left digital workplace and so you are connected to it and you have all your contact and for example you have some contacts with phone number.
And we add a button just to be able to call it and then when you click on this button you can open a web client on a news application to do the call directly.
And now let's imagine a more complex integration.
More, that's it.
So here we can imagine to have a dialogue for example to be able to call a phone and maybe when you type it you have the suggestion of your contacts that are machine matching what you are typing.
And also you can have the call directly into the digital workplace and not open another application.
And we can see it on the screen, but here you have the call history because you can maybe want to have the calls that you did.
Okay, so we just show you what what can be done basically easy placing postcode phone calls from a web page.
But the implementation is not so easy because from the beginning the telephony world was fully supported from the computer world, not the same protocol.
Meaning it was even not based on IP and dedicated hardware.
So the first step to bring the telephony into the digital workplace is to get rid of the hardware and to implement software.
So the phone started this work very long time ago.
So now we have the software and the protocol also move from dedicated protocol SS7 for your information, very old protocol.
Now it's based on SIP and it's now possible thanks to the software need to to integrate it in another software.
So based on this evolution from fully hardware dedicated protocol non IP to software need.
But it's not finished.
We have to leverage on different protocol in order to perform the authentication because the key is to have a shared authentication between your digital workplace and the telephony world, which is still not the case.
So thanks to SSO it's going to be possible, sing and sign up, it's going to be possible.
In order to bridge the web page of the digital workplace to either dedicated application or web page we can use on your high and low.
And in the case we want to have really the phone, the web application running the phone calls.
We will use Web Artifi, which is now available, largely available on browser.
And lately the protocol for the final step to which the operator network is to use the SIP protocol.
Okay, so this is the main overview of what could be from a server side, an integrated digital workplace using telephony network.
So the really the key is the single sign on in order to have the same authentication.
And also a couple of servers which are required to bridge the client which can be a browser or an application standard application or a mobile application to the operator world which is based on the SIP protocol.
Okay, single sign on, it's really the first step.
So it's just a remember of the report of the protocol.
So the idea of both is to promote application to ask to an authentication server for the credential for the user, the authentication server.
First of the time open a web page or if you are already logged in your digital workplace, you can gather the authentication information.
So you get back an authentication key and you can end the application then we'll use the authentication key to ask for an access token and this access token can lately be presented to the SIP server.
So now the SIP server that we developed can is compatible with a whole host which is the first step to be able to get access to the telephony from digital workplace.
So to go a little bit more into detail, so the little learn from application first connect to the to the SIP server, telephony server.
And we use the open ID connect which is the derivative from a host to get the access token and this access token has enough information to make the bridge between the digital workplace identity and the SIP and telephony identity, which is basically the phone number.
Okay, so for the old way to integrate then now we are authenticated, so we use the URL under which is basically a way to form an navigator to call an external application.
This is the simpler way and old-fashioned that the phone support, so at the end in the web application, we just ask the system to call a URL which is the SIP URL and the application is launched authenticated thanks to an ID connect and the call is placed.
This is for the first integration but we can also have a more smooth integration using a web app.
So before saying how to do with a web app, we will just have a look of how telephony call is doing over IP.
So we have three steps, first one is establishing the communication then communicate and finally and the communication.
For the first step and the third step, we are using the SIP protocol, so you have maybe a device here and you want to call a phone that is here.
So you first, you're sending a SIP message telling, okay, I want to do a call, I want to audio, this is my IP address and you're doing it to the process, you're sending this message to the proxy server, saying okay.
I need to go to this SIP paste and bridge, that which runs like a little bit of SIP message to be able to do to go on the trunk SIP, the same SIP is like a for example your operator and then this sensing will say, okay, this for number is linked to this device and so the message goes to the device and when you accept the call up, the message will go back, okay, I accept the call with this type of audio codec etc.
And then we are moving on this part, so the second, so the communication step and here you are using RTB real time protocol and I said here you're sending your IP address because we want that your voice goes faster because when you want to when you're speaking, you want that you are the people on the other side,
you reach as fast as possible, so it's keep the process ever and go directly to the SIP paste and bridge and thank you, your phone.
And it will be cool if we can have it on a website, so for that we need to have two parts.
First part is a web app and second part is a gateway. The web app is using web RTC that is a standard to have the communication and to establish it and also website that is a protocol to send and receive messages with a server and this server is doing SIP.
As you can see here there is no SIP, why there is no SIP? Because web RTC and browsers don't know how to speak SIP, so that's why you have this diagram that looks like the first one that I show you on SIP, but here you have the web RTC gateway and it's just to translate our web,
so get messages to SIP messages and in the web, SIP messages to WebSocket.
And then we are going on the RTP mode and you know what, web RTC know how to do it RTP, so we don't need that all the web RTC gateway.
We don't need that all the ZOOP process ever, so we are going like on the SIP code directly to the PSN grid, thanks SIP and to default.
Okay, so this is the way we can bring the telephone into the digital workplace.
It's something that we already done with a digital workplace developed in France, which is called Exagon.
It's not a full open source solution, but it's based on many open source projects, including Leanphone, Ex-Wiki, and many other open source projects.
And we hope that we will be able in the next future to bring this telephone apart into other fully open source digital workplace.
This is our goal now that we have developed the solution for one, many based on open ID Connect.
Okay, so again, I totally believe that if we want to have a full solution in order to complete and to gain more freedom for the today work, which is something important, we have to bring the full solution.
It's okay to have to be able to detect, to send the mail, to chat or to get information about documentation sharing and documents, but we also have to be able to communicate in our own time.
And today, for all the time, I think that the telephone is still mainly used, especially on companies and government office.
Okay, so I think it's a work of this presentation, so if you want to be interested by this topic and you want to go deeper into how to integrate the telephone into a digital workplace.
We are both at quite it, where is the location of the R. Yes, at W. Bill Building. It's changing every year, but now it's very well placed the room is big and we are happy.
Don't hesitate to visit us, we have some friends, the XMPP project, the matrix project and the lymphoen. Okay, so maybe if you have some.
Yes, for a minute, because of my dying piece. Yes?
Okay, the question is, do we have some example of already in suite or already integrating in phone?
As I said, yes, the XMPP project is the name of the French suite, not fully open source, regarding the suite.
We performed some prototype last year for integrating in phone into not directly last suite, but chaps, chaps is part of the suite.
It's the chatting application based on matrix, so we performed some tests and we are also working progress with another open source suite, but it cannot communicate before we launch the solution.
So yes, our goal is to visit, I will say, every digital workplace and propose them here. We know how to have the telephony, are you interested in working with us to bring the telephony to your user?
Yes? The part of the exit.
I would say that 90% of the solution is open source, but the company which developed the last part, I cannot speak for them, so I don't know.
But for us, the phone project or goal is really to also provide our solution and to have a partnership with fully open source digital workplace.
So I think in the coming months, you will see more integration.
Thank you.