[Serusers] parallel forking best practice?

Jev jev at ecad.org
Wed Feb 23 19:17:04 CET 2005


Hi Vitaly,

Thank you for your reply,

But do you have parallel forking working this way? So two or more phones 
ring at once. As opposed to one phone ringing for N seconds, and then 
another ringing (sequential forking).

Is it possible to do parallel forking with exec_dset()? I did not think 
that it was.


Thanks,
-Jev

Vitaly Nikolaev wrote:
> Hi,
> 
> I do not know that it is best, I even sure that it is not :) but it very
> useful and very flexible to execute external application that will return
> list of URI.
> 
> Why it flexible - because you can do, for example, balancing of whatever you
> use for termination all (in my case b2bua) plus I use nagios that testing my
> b2buas/gws/voicemails and then my "routing" script uses this info to avoid
> bad destinations
> 
> Plus different features like, call return, redial, call forward, step by
> step routing (like first call ring on your SIP device, if it fail it ring on
> your office phone and if it fail goes to your cell phone and same time to
> your gf cell phone :)) My script taking all this info from MSSQL database,
> of course it add some delay to your call (PDD) but that the price, you can
> always use few boxes with this setup in parallel (replicate) and do
> redundant SQL server for fast answer
> 
> 
> 
> 
> 
> 
> -----Original Message-----
> From: serusers-bounces at iptel.org [mailto:serusers-bounces at lists.iptel.org] On
> Behalf Of Jev
> Sent: Wednesday, February 23, 2005 11:01 AM
> To: serusers at lists.iptel.org
> Subject: [Serusers] parallel forking best practice?
> 
> Hi All,
> 
> For the 0_9_0 branch, what is the 'best practice' for implementing 
> parallel forking?
> 
> We used to be able to point one alias at several accounts, but that 
> feature has regressed.
> 
> 
> Thanks,
> -Jev
> 
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
> 
> 




More information about the sr-users mailing list