Hi Keith,
It sort of feels like you want to put functionality into osmo-msc that is already there via osmo-sip-connector and other programs beyond that. I can send a SETUP anytime I like with a random caller MSISDN via a plethora of SIP tools.
well, we already have some basic Call Control functionality in osmo-msc, the internal MNCC handler, which is enough for basic call operation in a lab environment. Having a test call functionality in addition to that would be ideal for me, yes.
Maybe you want to try to keep it in osmo-* land or somehow you don't like SIP.. (and by extension, IMS?) Which is why for you, forking and hacking on LCR is fine, and using osmo-gapk to do a convoluted RTP loopback is fine, but the really simple solution with SEMS is "overkill" :-)
It's not just me saying that using SEMS is an overkill. In the wiki page I linked you also wrote "it is quite some overkill" :P
You're right, I [personally] don't really like SIP. I am not saying it's bad or does not do its job properly, it's just a separate galaxy to me in which I have a very little expertise. And generally I am not a big fan of text based protocols, even though in this case all string manipulations are done by some SIP library (e.g. sofia-sip).
Hacking on LCR is not a simple way to achieve the goal either. I just have some warm memories associated with it (during the 34c3 talk we used it to demonstrate basic voice call functionality, by calling 995), so I tried to get my hands on it again. For the sake of nostalgia.
As I muttered before, I wonder if this has less to do with the merit of any of those solutions, rather it has to do with your own personal familiarity with the tools and capabilities as a C programmer.
Ack.
Of course, maybe there is a reason to have this testing possibility self-contained in the minimum number of daemons that I am not aware of.
Exactly. The less additional components it involves, the better.
Best regards, Vadim.