I'm not sure this is possible in config, but look at the new functions in tm module: http://www.iptel.org/ser/doc/modules/tm They help you identify what has happened in other branches. What you need is tm_cancel_all() that can be executed in onreply route. Is probably not that difficult to add, if you don't find out, post to serdev. If it's not present, you can provide a patch ;-) g-) Zappasodi Daniele wrote: >Hello, >I need to implement a variation in the parallel forking: in the standard parallel forking SER waits the first 2xx and then sends a CANCELs to all pending branches. If one of the receiver refuses the call, the other destinations >continue ringing until all the branches fail or there is a 2xx. >I need to change this behaviour in order to have SER that stops the forking and sends the CANCELs for each final reply, both 2xx and negative reply. >How can I do? Can I obtain this scenario working only with the config file, maybe with SPIRAL or with two SER instances? > > > >********************************************************************** >The information in this message is confidential and may be legally >privileged. It is intended solely for the addressee. Access to this message >by anyone else is unauthorized. If you are not the intended recipient, any >disclosure, copying, or distribution of the message, or any action or >omission taken by you in reliance on it, is prohibited and may be unlawful. >Please immediately contact the sender if you have received this message inerror. > >********************************************************************** >_______________________________________________ >Serusers mailing list >Serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers > >

_______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers