Juha,
it can be a configuration option, a compilation switch or a patch - all
are ok from my point of view. Depends how the SEMS's guys see the
integration form their point of view.
MI support is already in TM (not intensively tested, but it passed most
my tests :) ), but for the moment it can be used only via fifo or xmlrpc
(not sure if SEMS supports this).
Thanks for the help,
bogdan
Juha Heinanen wrote:
Bogdan-Andrei Iancu writes:
> So, for SEMS point of view, the affected ones will be the internal
> functions exported by TM:
> t_uac_dlg
> t_uac_cancel
> t_hash
> t_reply
>
> I guess all are used by SEMS excepting t_hash function.
yes, sems uses all except t_hash. it should not be a big deal to add to
sems a configuration or compilation option that tells if ser or sems
version of these functions is in use. it is all in
core/AmSipDialog.cpp. i can take a look at it once i have the new mi
based tm running and tested.
-- juha
_______________________________________________
Devel mailing list
Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
