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> | * Add the new API to the abstract <code>CC_Call</code> interface in <code>media/webrtc/signaling/include/CC_Call.h</code>. Example: | ||
virtual void setPeerConnection(const std::string& handle) = 0; | |||
Revision as of 16:52, 26 June 2012
Notes on how to add a new message to SIPCC
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
CC_Callinterface inmedia/webrtc/signaling/include/CC_Call.h. Example:
virtual void setPeerConnection(const std::string& handle) = 0;