[Serusers] How to execute failure_route block by the same child process.

Bogdan-Andrei Iancu bogdan at voice-system.ro
Fri Jun 10 19:26:59 CEST 2005


you can either use avpops to populate the fork_list (use avp_write or 
avp_load to read from db), either there is a function (not sure about 
the name) in lcr module (also to read from db).

bogdan

Dmitry Isakbayev wrote:

> Hi Marian,
>
> Thank you taking the time to answer my question.  The serial forking 
> example is exactly what I need.  Is there a sample "set_fork_list()" 
> function that you can point me to?
>
> Regards,
> Dmitry
>
>
>
> ----- Original Message ----- From: "Marian Dumitru" 
> <marian.dumitru at voice-sistem.ro>
> To: "Dmitry Isakbayev" <isakdim at gmail.com>
> Cc: <serusers at lists.iptel.org>
> Sent: Friday, June 10, 2005 6:16 AM
> Subject: Re: [Serusers] How to execute failure_route block by the same 
> child process.
>
>
>> Hi Dimitry,
>>
>> you don't need to implement anything else for serial forking - it's 
>> already there. Take a look to this example which shows a way to do it:
>>
>> http://www.voice-system.ro/docs/avpops/ar01s08.html#ex_serial_forking
>>
>> about your question - no, is not possible. If you want to store some 
>> information from main route and used in failure_route use AVPs. (see 
>> avpops module)
>> http://www.voice-system.ro/docs/avpops/
>>
>> regards,
>> Marian
>>
>> Dmitry Isakbayev wrote:
>>
>>> Hello,
>>>  I am trying to implement sequential forking using to_on_failure and 
>>> failure_route blocks.  Is there a way to configure SER or tm module 
>>> to execute the 'failure-route' blocks using the same process as was 
>>> used for executing the main route script?  If it was possible, I 
>>> would not need to share state information between different SER 
>>> processes
>>>  Thank you in advance,
>>>  Dmitry
>>>
>>
>> -- 
>> Voice System
>> http://www.voice-system.ro 
>
>
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>




More information about the sr-users mailing list