SIP 2012 :: ICE – finding the best media path between two phones
Edvina continues the work to define a new SIP reference profile, updated to fit current networks and implementations. SIP 2.0 is over 10 years old and the RFC does no longer cover enough to fit the needs of the enterprise. Networking has changed and much has been added to SIP by the IETF in cooperation with the SIP Forum, the 3GPP and the PacketCable consortium. Unfortunately, when purchasing SIP solutions, most customers still only refer to RFC 3261 as the reference specification. This is what SIP2012 is trying to change.
With ICE the best media path – and a working one – is always selected for the call
ICE – Interactive Connectivity Establishment – is now added to SIP2012. It’s a solution for always finding the best media path between two devices – regardless if it’s private or public addresses or if it’s an IPv4 or an IPv6 address. For a SIP call, the caller and callee needs to know that there is a working media path. If not, the call should fail. This is the promise of ICE.
ICE is also part of WebRTC
ICE is also part of the developing standard for adding interactive media – audio and video – to web browsers. With SIP in the web browser on your tablet, you want to connect over 3G or 4G, wifi enterprise networks as well as to the Wifi in a hotel or in a café. ICE handles finding the best media path in these environments, so it’s a natural part of the WebRTC standard. In that project, many additional requirements to ICE has been added, which will show up as new RFCs soon.
Read more about ICE on our SIP2012 project web and watch our presentation of ICE! Follow us on Twitter or Facebook to engage in the debate!
The new Edvina SIP Masterclass – Stockholm and Miami this fall!
Edvina today launches a new training class, based on years of experience of inhouse and public classes in SIP, Asterisk and Kamailio/OpenSER. The new class focuses on the SIP protocol and the Kamailio Open Source SIP server. By combining lessons on the core SIP standard with the Kamailio implementation and labs, the students will learn interactively and get real configurations to bring home. The new class will launch in October in Stockholm, Sweden and in December in Miami, Florida, USA.
– “We’ve updated the training materials during a series of in-house trainings during 2011 and 2012, which means that the material is almost totally new compared with the original class held seven years ago.” says Olle E. Johansson, Edvina’s founder and the teacher in the classes. “We’ve added more labs and more information about SIP presence and security. For students, this is an upgrade that fits everyone that has worked with Asterisk, FreeSwitch or Yate for many years and wants to learn how to scale and add new SIP services to their solutions.”
Experienced teacher guiding the way
Olle has many years of experience in trainings. He wrote the first Asterisk Bootcamp trainings in 2005 and was the author behind the Digium dCAP certification for Asterisk. Prior to that, he has been doing years of training in TCP/IP networks, from network basics to LDAP directories and SSL/TLS solutions. In addition he’s working as a consultant building large platforms with Kamailio and Asterisk as the primary tools. He has been involved in both Open Source projects since 2002, as a contributor, documentation writer, coder and project member.
From SIP to scalable realtime platforms with Kamailio
This class is built for persons that have used the PBX-class tools like Asterisk, Yate and FreeSwitch and wants to learn how to scale and add new applications like presense and instant messaging to their solution.
The class will spend a lot of time on the SIP standards, then move on to how to implement them using Kamailio – the Open Source SIP server – in combination with other tools. After the class, you will not only know how to operate Kamailio – you will also have a lot of knowledge about how the SIP standard works, what to expect from devices and how to troubleshoot your realtime network.
PS: A special thank you to Redfone Communications in Miami that hosts our training in December!
SIP2012 :: Redefining SIP
Edvina today launched SIP2012 – a project to try to redefine SIP in the eyes of all customers to our industry. We need to go beyond the 10-year old RFC and use all the solutions developed by the IETF and the SIP Forum during 10 years of SIP version 2.0. We’re not defining SIP 3.0 – but trying to combine a set all the specifications added during this time into a reference profile that customers can refer to and use when buying SIP devices – phones, servers, chat clients, PBXs and much more.
What’s the current state?
It’s very hard for customers to clearly specify functionality required. If they refer to RFC 3261 as a base RFC, that would include S/MIME which is almost never implemented. RFC is updated by 13 RFCs, added to by quite a lot of RFCs and there are 5 verified bug reports (ERRATA) against the text in the RFC.
An example: A large bid for a new telephony platform
Let’s start the discussion with an example. One large bid from last year specified the following standards as requirements:
- RFC 3261: SIP version 2.0
- RFC 3263: Locating SIP Servers
- RFC 3550: Real-time Transport Protocol (RTP)
- RFC 3551: RTP Profile for Audio and Video Conferences with minimal control
- RFC 3487: Priority mechanisms for SIP
- RFC 2833 or 4733: DTMF signalling
- RFC 4855/4856: Media Type Registration of RTP Payload Formats
- RFC 3611: RTP Control Protocol Extended Reports
- RFC 5391: RTP Payload format for G711.1
- RFC 3711: The secure Real-time Transport Protocol
- RFC 5246: The Transport Layer Security (TLS) Protocol
- RFC 2475: Diffserv
What is your opinion? Do you have a good specification that could be useful for other people? Please share!
Reference implementations are important!
We encourage Open Source projects to support the profile and take some extra steps to build reference implementations and test them at the SIPit test events, organized by the SIP forum. Edvina will participate and help tests by building self-test platforms where possible, as we’ve done for TLS, SIP Identity, early media and much more during earlier SIPit events.
Kamailio and OverSIP Open Source SIP Servers are working on implementing SIP Outbound, the first part of SIP2012. We need clients that support it so we can test it for interoperability. Please join this effort!
To find out more – click here for the SIP2012 web with a presentation of SIP Outbound – the first part of the SIP2012 profile.
Is SIP the new WebRTC infrastructure?
SIP celebrates 10 years this summer. When it was created, it was created to become the new infrastructure for Internet-wide realtime communication and collaboration. Based on domains, like e-mail, SIP was built for the Internet. But neither the Internet nor corporate networks was ready for it. Many problems was discovered, like NAT traversal, firewall handling and the quality of the existing networks. They where built for store-and-forward networking, getting a file, sending a file – but not realtime communication.
10 years later we see that most of the SIP installations ended up as PSTN-over-IP solutions. SIP addresses are equal to E.164 phone numbers and domain based federations across the Internet is rarely used. We have ended up in a world with VoIP islands that have no interoperability that call each other over the old switch phone network. That was not the vision, that was not the idea driving the development of SIP.
Webrtc- where all the fun happens today!
During this year, we’ve seen a lot of activity around a new communication technology named WebRTC. The idea is to add realtime media – audio, video, file transfer – to every web browser. With a few lines of Javascript you can create an application that calls other browser users. This is of course fun and removes the need to install a soft phone in your device – the cell phone, the tablet or the computer. Every device with a web browser will have realtime communication capabilities. The browser can ask for permission to use the webcam and the audio system and bootstrap communication.
WebRTC – joint development by W3C and the IETF
WebRTC is a joint project between the IETF and the World Wide Web consortium. The W3C defines the Javascript extensions and the IETF the underlying protocols and mechanics. Microsoft, Google, Ericsson and many other companies are involved in the process, like most web browser developer teams – Firefox, Safari, Chrome. The work is progressing quickly, but is not yet done. Many browsers are releasing beta implementations. Google Chrome has invited developers to play with the new API’s and have many interesting projects based on just the simple fact that the webcam is now part of the toolset in the browser. Caleidoscopes, face recognition, games and much more has been developed during Google hacker meetings.
Will WebRTC make SIP a dying system?
There will be millions of WebRTC applications, from games to business communication. As soon as you want to communicate across server borders, there is still the issue of finding the other person and setting up a communication session. You need a protocol to do this. WebRTC only involves setting up the media and describing media capabilities – but there still needs to be a way to exchange these attributes in order to set up a session. If the users are using the same web application, the application will be able to manage the exchange of media attributes. This will work for many applications that wants to enhance the existing service with realtime audio and video. As soon as you want to scale beyond that and communicate with users somewhere else, on a SIP phone or a PSTN device, you need a protocol that opens up for reaching out and setting up a session. SIP is exactly such a protocol, a protocol that operates on a session – finds the other party (or multiple users), sets up the session, manage the session and end the session. SIP and WebRTC are perfect buddies. From a SIP standpoint, there’s not a lot of difference between using the multimedia system in a computer than using it in a browser. From the users standpoint, they’ve already installed the browser. It’s there and simple to use.
SIP with WebRTC fulfills the SIP vision
SIP and WebRTC have the possibility of bringing SIP back to it’s root. We can now build a federated global network, like E-mail. And add security that did not exist in e-mail, so that we can trust the network and use it everywhere we connect our devices. There are already many solutions that will take you beyond telephony-style number-based calls, like the Kamailio SIP proxy and the Zoiper and Blink soft phones that support SIP presence and instant messaging.
Edvina stays on top of these new technologies and are happy to help new and existing customers to navigate in this new communications world!
World IPv6 Launch is today!
Today is the World IPv6 Launch. This means that thousands of web sites across the world will enable IPv6 access and keep it on. It’s an important start of a change that will mean that IPv6 will be just normal work and hopefully integrated into all projects. At Edvina, we will from now on integrate IPv6 support in our platforms by default. IPv6 support is no longer an extra add-on or something that we only install if the customer asks for it. Building new platforms for TCP/IP means IPv6 included.
The World IPv6 Launch is a big step forward for the Internet. Our blog, IPv6 Friday, has covered many aspects of the World IPv6 Launch, what it is and how you should prepare for it.
- May 25, 2012: Oh no! June 6th is coming up faster than expected!
- Apr 13, 2012: No need to go backwards in time, use a reverse web proxy
- Mar 23, 2012: Get ready in time for the World IPv6 Launch
- Jan 20, 2012: Your new goal: The world IPv6 Launch
The blog at IPv6Friday.org keeps getting more readers and generates discussion.