The receive message are called as needed by all kinds of things you simply
have to do what they want and return success or fail
when the world sends your protocol a message you just have to find the
channel like the last email described and call api calls on it depending
what the situation is.
Th
Thank'you Anthony!
Some more questions, maybe they're just misled:
The event/signals sent by the core to the channel are automatically
processed by the channel_receive_message() and channel_receive_event()
functions.
So, during a call, we have the signaling thread loop (that listen and
act on si
The general jist of your overview seems sound.
To answer your question:
Typically you would have the protocol specific side create some sort of
table of all the calls with something to tie it to the freeswitch channel.
To be threadsafe you can keep the channels uuid string in a table and
whenever
First things first: when I'll understand, I'll write the wiki page on
endpoints inner working and development.
I'm now beginning to rewrite the skypiax implementation, and I would
like to do it in the most "accepted" way.
skypiax (and celliax in the future) will have multiple interfaces (eg:
mult
