12 Nov
2004
12 Nov
'04
12:55 a.m.
Hello,
comments inline ...
Girish wrote:
Hello,
--- Elena Ramona Modroiu <ramona(a)voice-system.ro> wrote:
I don't know how is your implementation, with this approach you can load
the destination addresses from database as well as specifying them
directly in config file or from a module. Otherwise the failure route
mechanism should be the same.
Hello,
some serial forking can be implemented using the AVPOPS module with CVS
head SER version. Take a look at the example from
http://www.voice-system.ro/docs/avpops/ar01s08.html#ex_serial_forking
It may help you.
Thanks for this info. I read only the serial forking section. A few questions...
From the code snippet given in the above mentioned doc, i can see that the different
addresses can
be set for forking initially. But it again uses failure routes. We implement serial
forking using
the existing failure routing mechanisms. Is there any advantage of using this new approach
apart
from setting the initial fork list?
I guess it will make processing faster, in case the
records
are taken from DB or they are set using a custom-built module. Am i correct?
yes, but as I said above you can set them also directly in the config file.
The document says that "There are no
limitations", but in your mail you have stated that "some serial forking can be
implemented". Can you explain that a bit?
The "no limitations" statement is about the way of setting or resetting
the destination set. I said "some serial forking" because, for example,
it doesn't support explicitly priorities for destination addresses (from
database the records are loaded in the order returned by a query after
the name).
Then, pardon me for my ignorance... but what is
'Salutari' ??
"salutari" is the Romanian word for "regards". You can check it
at
www.dictionare.com .
Salutari :),
Ramona