Hi all
I noticed that the desc_time_order parameter of the registrar module (in ser.cfg) doesn't seem to work as it should (according to the description in the registrar manual). If I understood correctly, if desc_time_order = 1 (using modparam) the newest contact should be used among those of same priority (I'm using the append_branches parameter equal to 0).
Another doubt is whether it is possible or not to use append_branches=1 to do priority-driven forking (all contacts are receiving the request, no matter which is their priority; is it possible to limit the forking just to those of same priority (q)? or even something better? :-) ) thanks a lot Jimes Vasco Milanez Diretoria de Sistemas de Nova Geração CPqD Telecom & IT Solutions Tel.: +55 19 3705-4879 jimes@cpqd.com.br www.cpqd.com.br
On 16-06 16:53, Jimes Vasco Milanez wrote:
Hi all
I noticed that the desc_time_order parameter of the registrar module (in ser.cfg) doesn't seem to work as it should (according to the description in the registrar manual). If I understood correctly, if desc_time_order = 1 (using modparam) the newest contact should be used among those of same priority (I'm using the append_branches parameter equal to 0).
What exactly does not work, could you give me an example ?
Another doubt is whether it is possible or not to use append_branches=1 to do priority-driven forking (all contacts are receiving the request, no matter which is their priority; is it possible to limit the forking just to those of same priority (q)? or even something better? :-) )
No.
Jan.
-
Jan Janak -
Jimes Vasco Milanez