Asterisk Project : Asterisk WebRTC Support
This page last changed on Sep 20, 2012 by jcolp.
BackgroundWebRTC/rtcweb is an effort to bring a defined API to JavaScript developers that allows them to venture into the world of real time communications. This may be a click-to-call system or a "softphone" with both delivered as a webpage. No plug-ins are required and as this is a defined specification it can be used across different browsers where supported. Asterisk has had support for WebRTC since version 11. A res_http_websocket module has been created which allows the JavaScript developers to interact and communicate with Asterisk. Support for WebSocket as a transport has been added to chan_sip to allow SIP to be used as the signaling protocol. ICE, STUN, and TURN support has been added to res_rtp_asterisk to allow clients behind NAT to better communicate with Asterisk. SRTP support was added in a previous version but it is also a requirement of WebRTC. Browser SupportThe latest information about browser support is available at http://en.wikipedia.org/wiki/WebRTC SRTPSecure media is a requirement of WebRTC and as a result SRTP must be available. In order for Asterisk to build SRTP support the libsrtp library and development headers must be available. This can be installed using the distribution's package management system or from source. Failure to do this will result in the media offers being rejected. Configuring res_http_websocketThe built-in Asterisk HTTP server is used to provide the WebSocket support. This can be enabled using the following in the general section of the http.conf configuration file. enabled=yes If you would like to change the port from the default value of 8088 this can also be done in the general section. bindport=8088 The res_http_websocket must also be built and loaded by Asterisk. For most individuals this is done by default.
The secure calling tutorial viewable at https://wiki.asterisk.org/wiki/display/AST/Secure+Calling+Tutorial can be used as a basis to configure the built-in HTTP server with HTTPS (and secure WebSocket) support. Configuring chan_sipAll configuration occurs in sip.conf, or a configuration file included by it. To allow a peer, user, or friend access using the WebSocket transport it must be added to their transport options like the following. transport=ws,wss To restrict access to clients using only an HTTPS connection allow the 'wss' transport only. The WebRTC standard has selected AVPF as the audio video profile to use for media streams. This is not the default profile in use by chan_sip. As a result the following must be added to the peer, user, or friend. avpf=yes This will cause AVPF and SAVPF to be used and the media streams to be accepted.
As media encryption is a requirement of rtcweb the following must be added to the peer, user, or friend to enable it. encryption=yes Using WebSocketThe res_http_websocket module provides WebSocket at the /ws sub-directory only. This is an implementation specific detail. Some JavaScript libraries may need to be changed slightly to explicitly use the sub-directory. Symptoms of using the incorrect URL are a 404 Not Found response from the Asterisk HTTP server. JavaScript Libraries1. sipml5 - Provides a WebRTC compatible JavaScript SIP library, requires minor changes to work with Asterisk. This code is still in flux so a patch is not yet provided. IssuesAll SIP responses are sent from Asterisk to the client. HTTP Response: 404 Not FoundThe JavaScript library is using an incorrect URL for WebSocket access. The URL must use the /ws sub-directory. SIP Response: 400 Bad Request received over SIP when registering using WebSocketThe version of chan_sip in use has a bug when registering. Update to a newer version. SIP Response: 488 Not acceptable here received over SIP when placing a call to AsteriskYou have not enabled AVPF support in the peer, user, or friend entry using "avpf=yes" or have not allowed a codec that is supported by the caller. |
![]() |
Document generated by Confluence on Nov 02, 2012 17:42 |