2 What WebRTC Does NOT Do: “No Numbers” No rendezvous – “no addressing” at all Not like SIPMore islands? Yes, but it is adding high quality real-time communication where we already are in contact.What WebRTC Does:Sets up media directly between browsers (SDP/RTP like SIP) – typically on same web application.“Handles” NAT/FW traversal (ICE, STUN, TURN) – fooling firewalls (like Skype).VoiceVideoData“For free!”
4 The WebRTC & SIP PBX Companion LANCompanyWeb ServerSIPWSmediaLANCompanyWeb ServermediaAdding WebRTC capabilities to the enterprise PBX / UC-solution This is for an enhanced Ingate platform, running on existing HW, on virtual machines and even ported on to embedded CPEs. It is considered as a PBX vendor OEM-product and as service provider deployed access device.
5 E-SBC WebRTC Gateway The is in the Companion SIP Trunking Q-TURN Web ServerQ-TURN
6 Clicking on the Website and or Passing a Link Should Both Go Into the Enterprise PBX/UC InfrastructureYou can also pass your WebRTC link over IM or an and ask to click for calling you.And the call should reach you via the SIP PBX/UC infrastructure with all its features.LANCompanyWeb ServerSIPWSmediaThe WebRTC & SIP WebRTC PBX Companion will bring the PBX/UC infrastructure back into WebRTC callsmediaCompanyWeb ServerDEMO 4) Audio/Video link Webex invitation: Click igconf linkLAN
7 The WebRTC Browser as a Softphone and More Having the PBX/UC Softphone available everywhere, on every device having a browser, without any plug-in and not just for plain voice phone calls, but potentially also for HiFi HD telepresence quality, is of course a dream.The Ingate PBX Companion will bring into a PBXThe browser becomes your Softphone by surfing to a simple webpageInterfaces to the PBX via the SIP Trunk Interface if other not available.The Registrar can be in the PBX or in the Ingate (numbers can still be integrated)All proven Ingate E-SBC functions included and is the interface to SIPSIP E-SBC authentication and security available in addition to web page loginSimple Websocket interface to the SIP UA in the Ingate, as well as a SIP proxy interface for building a full SIP ClientAny Web Server can be used. There will be one in the Ingate, if preferredE-SBC, SIP Trunking as well as Q- TURN QoS and AccountingDEMO: Register as call and reverse direction (show VP8 video compatibility)
8 The WebRTC Browser as a Local Softphone Browser becomes your Softphone by surfing to a webpageCan be a full SIP Client in JS in the browser, or just “a page of JS” where the SIP UA is in the Ingate (recommended)Any Web Server can be used. There will be one in the Ingate, if preferred.SIP interface to the PBX via SIP Trunk Interface if other not available.The Registrar can be in the PBX or in the Ingate. “Numbers” can be integrated via the Ingate SIP Trunk page then.Authenticated WS or WSS interface to the PBX Companion, running Ingate’s RTCgate protocol and CONFgate protocolThe WS or WSS interface also includes the SIP protocol, Ingate’s full SIP Proxy interface as if accessed as via UPD, TCP or TLS(Any)Web ServermediaWSSIPHTTP2LAN1media
9 The WebRTC Browser for Remote Users Use an external Web Server, or open port 80 or 443 in the Enterprise Firewall to use a local Web ServerAny Web Server can be used. There will be one in the Ingate, if preferred.The Registrar can be in the PBX or in the Ingate. “Numbers” can be integrated via the SIP Trunk page then.Q-TURN in the Ingate can be the STUN/TURN server to traverse the remote NAT/FirewallThe Ingate PBX Companion includes the full SIParator® E-SBC and can work in parallel with the enterprise firewall or be the data firewall as well2(Opt) Web ServerHTTPSIP TRUNKWSmedia(Any)Web ServermediaWSSIPBORTHTTPmediaLAN1
11 Manage the PBX Companion From the PBX GUI The PBX companion, the SBC and the Firewall – all configuration is available via the Websocket connection using the CONFgate protocol.The CONFgate protocolThe client webpage can use a proprietary protocol called CONFgate to communicate with the IXNX unit through a Websocket. The CONFgate protocol allows access to the same command line interface (CLI) as telnet connections.To access the CLI the webpage can open a Websocket connection to IXNX's Websocket server and specify protocol ”CONFgate”. Then supply a valid login and password (same as for the configuration web pages and Telnet).User root is by default not allowed to be logged in. Non-root users are by default logged in to the CLIsh command line interface, not the regular Linux shell. The Websocket server is by default not enabled. CONFgate is by default not enabled. Accessing through CONFgate can be granted/denied individually for different users.Once logged in, the webpage can send CLI commands to read and write configuration using CLI configuration commands like ”uci set sipadv.sip_fent_udp_time=60” and some other commands like ”netstat”, ”ifconfig” and ”fwlog” and receive the command output through the Websocket connection. For a complete list of commands available see CLIsh documentation.As for all user access to the unit, file /etc/config/access/username specifies what parameters a specific user is allowed to read and write, regardless of if she logs in through web interface, telnet, or CONFgate.WS: CONFgateWeb ServerHTTPIf the PBX has web based configuration, you can therein build web pages for the PBX Companion. You simply let the browser code open a Websocket and execute the appropriate configuration CLI commands in the PBX Companion.
12 WebRTC Hooks to the Ingate SIP Proxy E-SBC The WebRTC traffic comes as (i) SIP from the browser (which has got its SIP client code from some webpage) OR (ii) according to the simple Ingate RTCgate protocol (Where the SIP UA, the client, is in the Ingate product). In both cases the transport is via websockets (WS or WSS). All Ingate SIP and SBC features becomes available.The WebRTC client Java Script code may be on any web server (also in the Ingate). The server executing the RTCgate protocol runs on the Ingate.There is more than just SIP, e.g. PBX extensions available through the RTCgate protocol.With Ingate’s Q-TURN (more about that later), important features such as Security, QoS and Accounting (Billing) becomes available also for WebRTC end-to-end (not converting to SIP).