Merging inbound/outbound methods

[Netzvamp]

There are not that many differences between both socket connections.

• sendmsg: Inbound needs the channels uuid as parameter while outbound assumes it from the sockets call uuid
• myevents: I would not use this on outbound connections, cause there is no function to deactivate this behavior. You can't add events from other legs after you called myevents. So no DTMF from the b-leg for example. Instead i manually set filters for the uuids of each leg. That way i also can also originate a third call/leg and also get these events.
• filter: Inbound can be also cut down with filter to behave like a outbound connection (just to show that there is no huge difference between these sockets)
• bgapi/api is independent from sessions or specific inbound/outbound sockets
• linger: You could turn a outbound socket into a inbound socket with that, when you don't close the connection. (Useless, but shows how interchangeable they are)

With that said, it's absolutely possible to handle everything you do in a outbound socket also in an inbound socket.

It might makes sense to handle calls over inbound connections, when you can keep the call state synced across multi nodes. That way you could crash one node and another node would continue the call without interruption (with some redis backend/rabbitmq/clustering in the background). With outbound sockets the call would be lost if the socket gets interrupted. It would create a call cluster that couldn't fail on any call if done right.

I suggest to no longer separate inbound and outbound, instead find a way to work with both interchangeable.

I'm currently bound in a project, after that (maybe in 3 weeks) i could try to implement something that shows how it could look.

What do you think about that?

[Otoru]

The idea seems good to me, if we maintain compatibility with the interfaces already used there is no reason not to try.
My concern is that it will make the management of this in the code too complex without any real gain in performance or practical features.

[Netzvamp]

My hope is that this could simplify connection management, when we can handle them both the same way.
For me the killer feature is that we can handle calls like greenswitch but also like switchio (https://github.com/friends-of-freeswitch/switchio) the same time. That may help when i scale up the freeswitch and genesis instances.
But yes, i'm not sure how it will look for now. I'll build something and then we can think about it again. Maybe it's beatiful and simple or just pain 😉
Low priority for now, so don't hold your breath.

[Otoru]

Something like the switchio would be really cool to see. I’ve looked into a few ways to implement an event semaphore that would offer similar control to what it does there, but I haven’t come across one that’s abstract enough to be useful in various cases while still being simple enough for others to understand how to use.

In fact, a new approach to connection control might be the way forward.