Hugh Waite writes:
The tm module needs to know the name of the attributes AVP, which is currently passed as a modparam to the usrloc module. Therefore to 'activate' this bugfix, you need to pass the same modparam to the tm module.E.g. `modparam("usrloc|tm", "xavp_contact", "ulattrs")` If the modparam is not given to tm, the system will behave as before. There are no changes to the way the functions are called.
i'm still confused about xavp_contact tm module parameter. when i implemented t_load_contacts(), t_next_contacts() and t_next_contact_flows() functions, contacts_avp and contact_flows_avp defined the xavps that those functions used as described in tm README on those functions.
now there is another variable xavp_contact. tm README tells about it that it is used for storing attributes per contact, but does tell how the xavp gets set. usrloc README tells that xavp gets set at lookup (if i got it right), but is also tells "The tm module parameter xavp_contact must also be set to the same value to use the t_load_contacts and t_next_contacts functions".
does that mean that t_load_contacts()/t_next_contacts() does not anymore work if xavp_contact parameter is not defined for tm and usrloc modules?
-- juha
--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/178#issuecomment-111514198