JsSIP: SIP in your browser

Video in TIB AV-Portal: JsSIP: SIP in your browser

Formal Metadata

Title
JsSIP: SIP in your browser
Title of Series
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
2018
Language
English
Production Year
2017

Content Metadata

Subject Area
Abstract
JsSIP allows you to create WebRTC applications using SIP within your browser. The talk will go through the beginning of its development along with thestandarization process of the WebSocket as a transport for SIP, the use cases,the present and the future of JsSIP.
Loading...
Session Initiation Protocol Web 2.0 Server (computing) Hypermedia Multiplication sign Website Web browser Stack (abstract data type) Software maintenance Library (computing)
Standard deviation Software developer Moment (mathematics) Web browser System call Session Initiation Protocol Revision control Medical imaging Hypermedia Bus (computing) Website Right angle Library (computing)
Ocean current Server (computing) Standard deviation Internettelefonie Multiplication sign Electronic mailing list System call Web 2.0 Session Initiation Protocol Word Hypermedia Order (biology) Communications protocol
Point (geometry) Functional (mathematics) Socket-Schnittstelle Direction (geometry) Expert system Cartesian coordinate system System call Session Initiation Protocol Arithmetic mean Message passing Computer configuration Telecommunication Network socket Order (biology) Configuration space Object (grammar) Communications protocol
Point (geometry) Group action Message passing Digital electronics Decimal Object (grammar) Attribute grammar Element (mathematics)
Aliasing Slide rule State observer Implementation Group action Server (computing) Digital electronics Streaming media Web browser Mereology Attribute grammar Web 2.0 Session Initiation Protocol Hypermedia Different (Kate Ryan album) Network socket Core dump Social class Computer architecture Authentication Module (mathematics) Default (computer science) Multiplication Demo (music) Information Cellular automaton Interface (computing) Database transaction Cartesian coordinate system Connected space Message passing Uniform resource locator Software Personal digital assistant Telecommunication Order (biology) Musical ensemble Object (grammar) Abstraction Library (computing)
Touchscreen
Musical ensemble
Mereology
Heegaard splitting Source code Musical ensemble
Scripting language Default (computer science) Common Language Infrastructure Game controller Mobile app Functional (mathematics) Service (economics) Information Multiplication sign Water vapor Cartesian coordinate system Cursor (computers) Distance Dynamic Host Configuration Protocol Session Initiation Protocol Revision control Order (biology) Configuration space Software testing
Demo (music) Link (knot theory) Key (cryptography) Multiplication sign Web browser Web application Sieve of Eratosthenes Message passing Uniform resource locator Process (computing) Hypermedia Telecommunication HTTP cookie
Software Demo (music) Internettelefonie Codec Transcodierung
yes hi everyone my name is jose luis million I'm coming here today to talk you about PSE the Superstock library
well I'm currently based in Berlin I'm working for a company called propose where we build cheap and media server which is actually in SBC and it also has web RTC capabilities yes it is CP stack it's also an odious library even though you can also find Debian packages and bubble packages as well I have seen before the Debian package maintainer here david Pocock and one huge feature for me is that it's a few lead fully documented you can find the documentation in the web site yes sure okay so what's the motivation behind the Ieyasu there was a trigger in time which was the WebSocket transport when WebSocket Transport came to play into the playground we saw a huge opportunity to make browsers sip devices in such a way that that the this these devices should be as not not only a soft phones
like not Howard would be needed but it's so simple to use and to upgrade as reload in a website so by making a JavaScript library not only you can have a sip stack and make a new sip in you in your browser but you can upgrade to the
new version bus but by just upgrading your the website you download again the javascript file and you've got a new version of of the a sip so it was also a nice excuse to learn C and JavaScript more deeply and I really think we were in the right moment at the right at the right place when WebSocket was starting becoming an standard looking back we started in 2011 that's where the development started and in that that year we could already be able to make a sip call from from browser to browser or from browser to a to a legacy UDP or TCP simple device of course not with media because whoever TC was not yet already so we started also writing a draft to make a WebSocket standard transport for sale in that same year WebSocket became a standard tank so everything was clear I mean once we were able to have WebSocket as a standard transport for sip then it was it was the the the image was was perfectly we could perfectly see
see that it was it would be easier once the being the standard the WebSocket protocol then current voice over IP servers could adapt and create a new transport in order to be able to communicate these two words the web and the sick world then 2011 the first sip call with media thanks to web RTC and in 2014 the C / WebSocket became in the standard so there was no excuse anymore for sip server vendors to implement the
transport there's a list of implemented RFC's there are many many more in the in the sip ground but I think these are no more nor less yes those that we needed at that time and indeed right now the
API well there were several points that were quite clear we wanted to provide an API easy to use that could abstract the user from sip internals we didn't we were really aware about the fact that users making sip applications with jessep
didn't need to be experts so we wanted to abstract them from the SIP protocol internals that's why it wasn't masked that the API should be as simple as as possible so it's quite expressive as you can see we can create a sip user ient by passing a basic configuration which which only mandatory options are the same URI and a socket a server socket to connect to then we can start the the user agent register and register how can we call okay just call call how can we send a message just call send a message okay also it is called driven a API meaning that the communication between the a sip objects and the and the user are the callbacks so you define your callback functions in order to set yogic when a new RTC session comes then you set a new RTC session callback function you can then in the in the callback object in inspect who is usually the direction is just is quite a
common attribute of the leadership and callback object with which tells you who is doing this action is this this local this new RTC session being locally
generated is it an alcohol is it remotely generated is it is it any would call then answer check it draw react to whatever you need so at a glance this is the Dec market sector I think yeah it's quite well represents the decor we've got everything all of these points are stand over the user agent who holds the transport that holds many circuits also dialogues who on top of which RTC sessions are created you can also do I am miss achieve message we have a race traitor attached to the user Alliant so the user island can't register and register and this basically is so as you can see it looks like a modular design it was also a must since the beginning we wanted its element to take care of its things and abstract the others from its internals
as an example we've got the transport as
we can see in the previous slide we see a transport and multiple circuits okay then why don't we see WebSockets because actually you don't need to use WebSocket
to use the asset we provide socket interface which which is really simple which needs to implement three me dots connect disconnect and send which will be called by the alias avoid when necessary also three callbacks on connect on this connect on data so yes it is aware of whether it is able to send data to this transport or not and it's it's got some mandatory attributes well which go got their default of values which are via transport URL zip URI who helps for some - helps create in the sip messages and setting certain non-standard values that some cells observer vendors require this way you can I mean you are not attached to to use WebSocket of course we provide a WebSocket built-in implementation we also have WebSocket node module so you can use leadership in node of course we are talking about signaling not media and yeah that's all so you could send your CV messages over HTTP or over some application over HTTP or over any other kind of transport that respects this and implements the interface another example of the this is the communication internal communication of the object we can see here this onion architecture where we abstract objects from others implementation so a requester could be I am a message sender or a dialogue or a registrar who wants to send in this case a sip message so it delegates to the request sender who creates a sick transaction and delegates the sending of the of the packet to the transport who uses the socket and everyone does its thing so there for example the request sender in case there is a need to make a digest authentication we don't deliver it to the original requester but we absorb and consume it on the request sender making this this more modular and even cleaner another important part is the RTC session why's this important when we are talking about media we need to look at this class this is the one that deals with WebRTC API the one that adds and removes streams to the web RTC engine the one that requests the SDP so we can later send the SDP through a simple message and as well once we civilian SDP it fits the the WebRTC engine with this information so we can magically thanks to WebRTC establish a media connection apart from those actions this is a these are the typical sip actions that we could expect from a session that are hold and hold muta mu transpose D TM ACB info we can we also offer some callbacks so you can modify your sleepy before when you receive it from the network before you feel it to the WebRTC core or after you are sending dsdp to you to your sip server so you can adapt it to some circumstances or for example at data channel information whatever you need in order to communicate with the WebRTC engine we use WebRTC adapter which solves the incompatibility between naming mostly of API is offered by different browser vendors this way we just abstract we just use the standard naming and we don't care which browser we are talking to this library solves this issue for us okay go for a demo okay this is this demo you say double them the aim of the first part is soand that we can we can build a node application in order to use data sip for signaling and the other one will make a media demonstration [Music] Oh so this pollution stop heat up and I'd
know a little monitor
blue screen of death
show me reactions where are the new Renault shoes [Music] well okay
I kind of this bleep so I cannot split the I need you to split well okay okay
so I will go for the second part then gross acting to me
yes yes what's the command yeah they didn't show there I don't know where the they are they're merely specks tell
you okay sorry for the inconveniences
okay I will need to do it in a single [Music] okay I wanted to have a split displayed
so we could see the the execution of the app in one less side and decoding the other side but I will it would have made things a lot easier so please if you are interested pay attention because they will not happen at the same time so you can see that my cursor we are required in a asleep as well as the note the asleep WebSocket because we are creating the abuser agent using the node WebSocket transport so mainly this is the in order to show how easy can we use it this is the main function we just create water kept node WebSocket creates a user I end with this whoops WebSocket and starts the user agent there are two callbacks predefined with just the back some information the application allows us to be inside this this script so we will be able to control the user agent by executing commands okay first of all okay so I have enabled the C blogging because I thought this was interesting for the first time okay we can see here that the DAC piece is 13 we can see the configuration and its outer registering because by default it's out register we are registering in a testing service that we have and tragedy a signet okay now I will go out I will disable DHCP I just wanted to show you the SIP traffic here okay now we are in application I made a very simple CLI where you can kind of control this user ID and distance we have already seen and well we can see the status we are using this version we are connected registered and I will establish a remote peer okay here I will connect to my colleague Nikki I will try to establish a shot here hi there hi okay so yep okay oh I'm sorry okay let's go yep hi
there hi how are you doing okay Nicki's Esther Thanks yep okay so
let me just tell you what just happened here we did we did we did a kind of trick here so we were the chat is based on Cygnus it's request from one to another and there was a cookie phrase which is invite plus something where we send in a key link URL URL to add to the job ask tragedy a zip demo web application which actually runs on top of the browser so sending this invitation through a sieve message and he received this message and opened his browser with that with the with the given link at the same time I opened as well the browser so we could make the the media communication
and that is it I'm sorry for the committee inconveniences on the demo I hope everyone and I'm willing to answer any question you may have well since they're in WebRTC there are mandatory codecs if you are talking with WebRTC endpoints you don't need to bother about transcoding because they should share at least the common codec otherwise if you are trying to communicate with the legacy voice over IP network then you should take care of Adam and transcode accordingly yes so it was it [Applause]
Loading...
Feedback

Timings

 1049 ms - page object

Version

AV-Portal 3.20.2 (36f6df173ce4850b467c9cb7af359cf1cdaed247)
hidden