Media/WebRTC/SIPCCMessaging: Difference between revisions

Jump to navigation Jump to search
Line 3: Line 3:
SIPCC uses a bunch of message queues so it can be complicated to figure out how to add a new subroutine call at the CC API layer and have it make it all the way to the GSM layer. The following is just a checklist of the things you will have to change.
SIPCC uses a bunch of message queues so it can be complicated to figure out how to add a new subroutine call at the CC API layer and have it make it all the way to the GSM layer. The following is just a checklist of the things you will have to change.


* Add the new API to the abstract <code>CC_Call</code> interface in <code>media/webrtc/signaling/include/CC_Call.h</code>. Example:
* Add the new API to the abstract <code>CC_Call</code> interface in <code>media/webrtc/signaling/include/CC_Call.h</code>.  
   virtual void setPeerConnection(const std::string& handle) = 0;
   virtual void setPeerConnection(const std::string& handle) = 0;
* Add the new API to the the concrete <code>CC_SIPCall</code> implementation in <code>media/webrtc/signaling/src/softphonewrapper.h</code>:
        virtual void setPeerConnection(const std::string& handle);
And <code>media/webrtc/signaling/src/softphonewrapper.cpp</code>:
  void CC_SIPCCCall::setPeerConnection(const std::string& handle)
  {
    CSFLogDebug(logTag, "setPeerConnection");
   
    CCAPI_SetPeerConnection(callHandle, handle.c_str());
  }




Confirmed users
214

edits

Navigation menu