WEBVTT 00:00.000 --> 00:13.000 Okay, thank you and sorry for this little issue with my computer, which does die. 00:13.000 --> 00:21.000 Thank you for being here. I know it's late. It's a final presentation of this room for today. 00:21.000 --> 00:24.000 No, the final. 00:24.000 --> 00:29.000 Oh, okay. Sorry. 00:29.000 --> 00:33.000 Very busy day. A lot of people are here and it's nice. 00:33.000 --> 00:43.000 Okay, so now we are here to discuss about how to intuit open source telephony into digital or workplace. 00:43.000 --> 00:56.000 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. 00:56.000 --> 01:04.000 So we are going to discuss about the telephony, maybe just give you some background on how it works. 01:04.000 --> 01:15.000 And in part is how to integrate the telephony into a digital workplace, which is mainly the main topic of this talk. 01:15.000 --> 01:26.000 And give you some explanation on how we can bring this two world, which are historically supported. 01:26.000 --> 01:44.000 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. 01:44.000 --> 01:56.000 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. 01:56.000 --> 02:09.000 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. 02:09.000 --> 02:22.000 And so we work on the project starting in 2001 and our further action on Linux and then port on different operating systems. 02:22.000 --> 02:31.000 And in 2010 we started a company with the original source of lymphoNTIM and model. 02:31.000 --> 02:40.000 And the idea was to develop the project to have more functionality and more usage. 02:40.000 --> 02:51.000 Okay, so now the company is based in Grenoble, the main contributor of the project are also based in Grenoble. 02:51.000 --> 03:05.000 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. 03:05.000 --> 03:17.000 And today the application is available on also on iOS and Android and we have around one million downloaded application. 03:17.000 --> 03:46.000 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. 03:46.000 --> 03:58.000 Share documents, schedule meeting and also place phone calls. 03:58.000 --> 04:15.000 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, 04:15.000 --> 04:25.000 on the cloud, I don't remember exactly when office 365 started, but it was in the early 2000. 04:25.000 --> 04:37.000 And many other, many other components were bring together also in the open source world, but the telephony was still not integrated. 04:37.000 --> 04:45.000 And back to the proprietary solution, they all have their own solution for the telephony. 04:45.000 --> 04:59.000 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. 05:00.000 --> 05:17.000 Okay, so the role of the open source is to provide an option to bring an alternative to a proprietary solution like Microsoft. 05:17.000 --> 05:24.000 And so the idea is that we need to have all the part of the functionality. 05:24.000 --> 05:40.000 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. 05:40.000 --> 05:53.000 So open source standard, have many components which can be bring together to offer an alternative to Microsoft or proprietary solution. 05:53.000 --> 06:02.000 And what we believe is that the telephony is part of this solution. 06:02.000 --> 06:13.000 Okay, so now let's look at how it could be integrated telephony into digital workplaces. 06:13.000 --> 06:19.000 So we will start with the first simple level of integration. 06:19.000 --> 06:34.000 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. 06:34.000 --> 06:50.000 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. 06:50.000 --> 06:57.000 And now let's imagine a more complex integration. 06:57.000 --> 07:01.000 More, that's it. 07:01.000 --> 07:15.000 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. 07:15.000 --> 07:27.000 And also you can have the call directly into the digital workplace and not open another application. 07:27.000 --> 07:40.000 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. 07:40.000 --> 07:50.000 Okay, so we just show you what what can be done basically easy placing postcode phone calls from a web page. 07:50.000 --> 08:05.000 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. 08:05.000 --> 08:11.000 Meaning it was even not based on IP and dedicated hardware. 08:11.000 --> 08:21.000 So the first step to bring the telephony into the digital workplace is to get rid of the hardware and to implement software. 08:21.000 --> 08:26.000 So the phone started this work very long time ago. 08:26.000 --> 08:40.000 So now we have the software and the protocol also move from dedicated protocol SS7 for your information, very old protocol. 08:40.000 --> 08:53.000 Now it's based on SIP and it's now possible thanks to the software need to to integrate it in another software. 08:53.000 --> 09:03.000 So based on this evolution from fully hardware dedicated protocol non IP to software need. 09:03.000 --> 09:08.000 But it's not finished. 09:08.000 --> 09:24.000 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. 09:24.000 --> 09:30.000 So thanks to SSO it's going to be possible, sing and sign up, it's going to be possible. 09:30.000 --> 09:43.000 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. 09:43.000 --> 09:51.000 And in the case we want to have really the phone, the web application running the phone calls. 09:51.000 --> 09:58.000 We will use Web Artifi, which is now available, largely available on browser. 09:58.000 --> 10:09.000 And lately the protocol for the final step to which the operator network is to use the SIP protocol. 10:10.000 --> 10:23.000 Okay, so this is the main overview of what could be from a server side, an integrated digital workplace using telephony network. 10:23.000 --> 10:30.000 So the really the key is the single sign on in order to have the same authentication. 10:31.000 --> 10:54.000 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. 10:54.000 --> 10:58.000 Okay, single sign on, it's really the first step. 10:58.000 --> 11:06.000 So it's just a remember of the report of the protocol. 11:06.000 --> 11:19.000 So the idea of both is to promote application to ask to an authentication server for the credential for the user, the authentication server. 11:19.000 --> 11:28.000 First of the time open a web page or if you are already logged in your digital workplace, you can gather the authentication information. 11:28.000 --> 11:45.000 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. 11:45.000 --> 12:03.000 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. 12:03.000 --> 12:15.000 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. 12:15.000 --> 12:41.000 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. 12:41.000 --> 12:59.000 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. 12:59.000 --> 13:24.000 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. 13:24.000 --> 13:36.000 This is for the first integration but we can also have a more smooth integration using a web app. 13:36.000 --> 13:45.000 So before saying how to do with a web app, we will just have a look of how telephony call is doing over IP. 13:45.000 --> 13:53.000 So we have three steps, first one is establishing the communication then communicate and finally and the communication. 13:53.000 --> 14:03.000 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. 14:03.000 --> 14:17.000 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. 14:17.000 --> 14:44.000 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. 14:44.000 --> 15:12.000 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, 15:12.000 --> 15:25.000 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. 15:25.000 --> 15:35.000 And it will be cool if we can have it on a website, so for that we need to have two parts. 15:35.000 --> 16:01.000 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. 16:01.000 --> 16:28.000 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, 16:28.000 --> 16:35.000 so get messages to SIP messages and in the web, SIP messages to WebSocket. 16:35.000 --> 16:46.000 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. 16:46.000 --> 17:01.000 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. 17:01.000 --> 17:09.000 Okay, so this is the way we can bring the telephone into the digital workplace. 17:09.000 --> 17:20.000 It's something that we already done with a digital workplace developed in France, which is called Exagon. 17:20.000 --> 17:36.000 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. 17:36.000 --> 17:49.000 And we hope that we will be able in the next future to bring this telephone apart into other fully open source digital workplace. 17:49.000 --> 18:00.000 This is our goal now that we have developed the solution for one, many based on open ID Connect. 18:00.000 --> 18:27.000 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. 18:27.000 --> 18:47.000 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. 18:47.000 --> 19:03.000 And today, for all the time, I think that the telephone is still mainly used, especially on companies and government office. 19:03.000 --> 19:19.000 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. 19:19.000 --> 19:44.000 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. 19:44.000 --> 20:02.000 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. 20:02.000 --> 20:23.000 Yes, for a minute, because of my dying piece. Yes? 20:24.000 --> 20:32.000 Okay, the question is, do we have some example of already in suite or already integrating in phone? 20:32.000 --> 20:42.000 As I said, yes, the XMPP project is the name of the French suite, not fully open source, regarding the suite. 20:42.000 --> 20:53.000 We performed some prototype last year for integrating in phone into not directly last suite, but chaps, chaps is part of the suite. 20:53.000 --> 21:13.000 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. 21:13.000 --> 21:34.000 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? 21:34.000 --> 21:44.000 Yes? The part of the exit. 21:44.000 --> 21:57.000 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. 21:57.000 --> 22:13.000 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. 22:13.000 --> 22:21.000 So I think in the coming months, you will see more integration. 22:21.000 --> 22:31.000 Thank you.