after i got rid of syntax errors (except while(1) warning), i'm getting this when sr tries to start:
Jun 1 18:38:38 localhost /usr/sbin/sip-router[9209]: : tm [t_funcs.c:388]: ERROR:tm:init_avp_params: invalid fr_timer AVP specs "$avp(i:705)" Jun 1 18:38:38 localhost /usr/sbin/sip-router[9209]: ERROR: tm [tm.c:772]: ERROR:tm:mod_init: failed to process AVP params
it comes from line
modparam("tm", "fr_timer_avp", "$avp(i:705)")
i tried also "$avp(705)".
the above used to work in k. how to make it work in sr?
strange thing is that the previous line
modparam("tm", "fr_inv_timer_avp", "$avp(i:704)")
is accepted.
-- juha
On 01-06 18:45, Juha Heinanen wrote:
after i got rid of syntax errors (except while(1) warning), i'm getting this when sr tries to start:
Jun 1 18:38:38 localhost /usr/sbin/sip-router[9209]: : tm [t_funcs.c:388]: ERROR:tm:init_avp_params: invalid fr_timer AVP specs "$avp(i:705)" Jun 1 18:38:38 localhost /usr/sbin/sip-router[9209]: ERROR: tm [tm.c:772]: ERROR:tm:mod_init: failed to process AVP params
it comes from line
modparam("tm", "fr_timer_avp", "$avp(i:705)")
i tried also "$avp(705)".
the above used to work in k. how to make it work in sr?
Try "i:705", these parameters of tm module do not parse AVP identifiers like the rest of the code, they assume that the value of the parameter just plain AVP name/identifier.
This is something we will have to address to make it consistent.
strange thing is that the previous line
modparam("tm", "fr_inv_timer_avp", "$avp(i:704)")
is accepted.
This is because both parameters are processed processed at once from mod_init and fr_timer_avp is processed first, regardless of its relative position in the configuration file.
Jan.
Jan Janak writes:
Try "i:705", these parameters of tm module do not parse AVP identifiers like the rest of the code, they assume that the value of the parameter just plain AVP name/identifier.
thanks, "i:705" worked.
by the way, tm README does not know mention about pv values for these parameters:
1.3.2. fr_inv_timer (integer)
Timer which hits if no final reply for an INVITE arrives after a provisional message was received (in milliseconds).
-- juha
On 01-06 19:48, Juha Heinanen wrote:
Jan Janak writes:
Try "i:705", these parameters of tm module do not parse AVP identifiers like the rest of the code, they assume that the value of the parameter just plain AVP name/identifier.
thanks, "i:705" worked.
by the way, tm README does not know mention about pv values for these parameters:
1.3.2. fr_inv_timer (integer)
Timer which hits if no final reply for an INVITE arrives after a provisional message was received (in milliseconds).
Fixed, it turns out that these two parameter were not documented at all and I just added the documentation.
Jan.