The tcap_invocation_sup is cretaed at the same time the tcap_cco_server
is created. Once TR requests BEGIN components, the tcap_invocation_sup
is requested to start a new tcap_ism_fsm child.
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...