This part deals with WebRTC client communication through call control logic in Service Control Point (INSCP) of an IN. The use of this setup is that the operator does not need to introduce services such as call screening, forwarding, or VPN separately for WebRTC clients, as they can utilize the existing logic. If, however, there is a requirement for introducing logic in the form of an application program that resides on the telecom core, then there arise the following two cases:

As we have embedded SIP as our signaling protocol in our instance of the WebRTC client, it is mandatory to either convert from SIP to the GSM protocol or provide the IMS core for any further processing of the call. Once a steadfast WebRTC-to-IMS system is set up and working, it is not a tough job to establish backward compatibility...