Commit Graph

5 Commits

Author SHA1 Message Date
Harald Welte 5c0f228e11 tcap_user: correctly resolve DHA/TCO
ets lookups return a tuple, not just the Pid value that we want.
2011-12-17 18:27:28 +01:00
Harald Welte d828cfabba TCAP: resolve DHA / CCO dependencies on TC-U initiated BEGIN
Prior to this patch, DHA needs to know the CCO pid, and CCO needed to
know the DHA pid at startup.  The idea was to start CCO from within the
init() callback in DHA.  However, this caused a deadlock in the
supervisor.

We now use the locally registred process names (tcap_cco_DLGID) to
resolve the process.  However, it might be cleaner to use an ets table
at some later point.  For now it is nice to see the name of each process
in pman for debugging...
2011-12-17 17:06:29 +01:00
Harald Welte 5c1cd340eb make sure tcap_user start tcap_dialogue_sup starts tcap_dha_fsm 2011-12-16 00:36:45 +01:00
Harald Welte 66514a113e add new tcap_user:start_sap() function
This can be used to instantiate the per-SAP tcap_sap_sup and
tcap_tco_server callback module in a simple call like this:

{ok, TcoPid} = tcap_user:start_sap(osmo_sccp_tcap, [7], []).
2011-12-15 23:38:29 +01:00
Harald Welte 6f1e72c678 add new tcap_user module
This is what a user process will call in order to initiate TCAP
transactions.
2011-12-15 16:45:28 +01:00