Hi,
I know this kind of function exists in Asterisk, but I want to know if Openser can do it as well. Let's say there are two fail-over numbers(DID-b,DID-c) that associates with a DID(DID-a), if the original number(DID-a) that get dailed can't rearch the destination due to BUSY, NO RESPONSE, etc, is there anyway of having Openser to auto-retry with the next DID(DID-b)? If the next one fails, try the next next one(DID-c).
One way I can think of is to do a lookup from DB for the alias in the fail_on_route section, but if I have multiple aliases, then I will have no way of *remembering* which alias has been tried unless I store it in the DB which is not a good solution.
I am wondering if there any other way of doing it?
Thanks in advance for all your kind suggestion.
Regards, Pete
El Monday 26 May 2008 18:52:38 Pete Kay escribió:
Hi,
I know this kind of function exists in Asterisk, but I want to know if Openser can do it as well. Let's say there are two fail-over numbers(DID-b,DID-c) that associates with a DID(DID-a), if the original number(DID-a) that get dailed can't rearch the destination due to BUSY, NO RESPONSE, etc, is there anyway of having Openser to auto-retry with the next DID(DID-b)? If the next one fails, try the next next one(DID-c).
One way I can think of is to do a lookup from DB for the alias in the fail_on_route section, but if I have multiple aliases, then I will have no way of *remembering* which alias has been tried unless I store it in the DB which is not a good solution.
You can insert manually some "contacts" into "location" table with "q" value smaller than others (set default value to 1 and manually set 0.1 to manual entries). Later use LRC module or CPL (in this last case look for the option "location sequential" (or something similar). It works.
Hi Pete,
A simple way to do it to load in AVP all the alternative destinations (in whatever order you want). Later, using failure_route, you will consume one by one the existing AVPs until none is left. This will minimize the DB impact.
Regards, Bogdan
Pete Kay wrote:
Hi,
I know this kind of function exists in Asterisk, but I want to know if Openser can do it as well. Let's say there are two fail-over numbers(DID-b,DID-c) that associates with a DID(DID-a), if the original number(DID-a) that get dailed can't rearch the destination due to BUSY, NO RESPONSE, etc, is there anyway of having Openser to auto-retry with the next DID(DID-b)? If the next one fails, try the next next one(DID-c).
One way I can think of is to do a lookup from DB for the alias in the fail_on_route section, but if I have multiple aliases, then I will have no way of *remembering* which alias has been tried unless I store it in the DB which is not a good solution.
I am wondering if there any other way of doing it?
Thanks in advance for all your kind suggestion.
Regards, Pete
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
Hi Bogdan, If I load the avp before I call do the first call. How do I store that AVP so that during failure_route, openser can still find it even it is stateless?
Thanks, Pete
On Tue, May 27, 2008 at 5:38 PM, Bogdan-Andrei Iancu bogdan@voice-system.ro wrote:
Hi Pete,
A simple way to do it to load in AVP all the alternative destinations (in whatever order you want). Later, using failure_route, you will consume one by one the existing AVPs until none is left. This will minimize the DB impact.
Regards, Bogdan
Pete Kay wrote:
Hi, I know this kind of function exists in Asterisk, but I want to know if Openser can do it as well. Let's say there are two fail-over numbers(DID-b,DID-c) that associates with a DID(DID-a), if the original number(DID-a) that get dailed can't rearch the destination due to BUSY, NO RESPONSE, etc, is there anyway of having Openser to auto-retry with the next DID(DID-b)? If the next one fails, try the next next one(DID-c). One way I can think of is to do a lookup from DB for the alias in the fail_on_route section, but if I have multiple aliases, then I will have no way of *remembering* which alias has been tried unless I store it in the DB which is not a good solution. I am wondering if there any other way of doing it? Thanks in advance for all your kind suggestion. Regards, Pete
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
Hi Pete,
The AVPs are transaction persistent, so they will be automatically available in the failure route.
Regards, Bogdan
Pete Kay wrote:
Hi Bogdan, If I load the avp before I call do the first call. How do I store that AVP so that during failure_route, openser can still find it even it is stateless?
Thanks, Pete
On Tue, May 27, 2008 at 5:38 PM, Bogdan-Andrei Iancu <bogdan@voice-system.ro mailto:bogdan@voice-system.ro> wrote:
Hi Pete, A simple way to do it to load in AVP all the alternative destinations (in whatever order you want). Later, using failure_route, you will consume one by one the existing AVPs until none is left. This will minimize the DB impact. Regards, Bogdan Pete Kay wrote: Hi, I know this kind of function exists in Asterisk, but I want to know if Openser can do it as well. Let's say there are two fail-over numbers(DID-b,DID-c) that associates with a DID(DID-a), if the original number(DID-a) that get dailed can't rearch the destination due to BUSY, NO RESPONSE, etc, is there anyway of having Openser to auto-retry with the next DID(DID-b)? If the next one fails, try the next next one(DID-c). One way I can think of is to do a lookup from DB for the alias in the fail_on_route section, but if I have multiple aliases, then I will have no way of *remembering* which alias has been tried unless I store it in the DB which is not a good solution. I am wondering if there any other way of doing it? Thanks in advance for all your kind suggestion. Regards, Pete ------------------------------------------------------------------------ _______________________________________________ Users mailing list Users@lists.openser.org <mailto:Users@lists.openser.org> http://lists.openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
And of course, the onreply_avp_mode must be properly set: http://www.openser.org/docs/modules/1.3.x/tm#AEN304
Regards, Ovidiu Sas
On Thu, May 29, 2008 at 11:30 AM, Bogdan-Andrei Iancu bogdan@voice-system.ro wrote:
Hi Pete,
The AVPs are transaction persistent, so they will be automatically available in the failure route.
Regards, Bogdan
Pete Kay wrote:
Hi Bogdan, If I load the avp before I call do the first call. How do I store that AVP so that during failure_route, openser can still find it even it is stateless?
Thanks, Pete
On Tue, May 27, 2008 at 5:38 PM, Bogdan-Andrei Iancu <bogdan@voice-system.ro mailto:bogdan@voice-system.ro> wrote:
Hi Pete, A simple way to do it to load in AVP all the alternative destinations (in whatever order you want). Later, using failure_route, you will consume one by one the existing AVPs until none is left. This will minimize the DB impact. Regards, Bogdan Pete Kay wrote: Hi, I know this kind of function exists in Asterisk, but I want to know if Openser can do it as well. Let's say there are two fail-over numbers(DID-b,DID-c) that associates with a DID(DID-a), if the original number(DID-a) that get dailed can't rearch the destination due to BUSY, NO RESPONSE, etc, is there anyway of having Openser to auto-retry with the next DID(DID-b)? If the next one fails, try the next next one(DID-c). One way I can think of is to do a lookup from DB for the alias in the fail_on_route section, but if I have multiple aliases, then I will have no way of *remembering* which alias has been tried unless I store it in the DB which is not a good solution. I am wondering if there any other way of doing it? Thanks in advance for all your kind suggestion. Regards, Pete ------------------------------------------------------------------------ _______________________________________________ Users mailing list Users@lists.openser.org <mailto:Users@lists.openser.org> http://lists.openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
Hi Ovidiu,
not needed - "onreply_avp_mode" is only for reply_route and for doing failure, you use failure_route (as Peter said) - in failure route the AVPS are available all the time (and no switch is needed).
Regards, Bogdan
Ovidiu Sas wrote:
And of course, the onreply_avp_mode must be properly set: http://www.openser.org/docs/modules/1.3.x/tm#AEN304
Regards, Ovidiu Sas
On Thu, May 29, 2008 at 11:30 AM, Bogdan-Andrei Iancu bogdan@voice-system.ro wrote:
Hi Pete,
The AVPs are transaction persistent, so they will be automatically available in the failure route.
Regards, Bogdan
Pete Kay wrote:
Hi Bogdan, If I load the avp before I call do the first call. How do I store that AVP so that during failure_route, openser can still find it even it is stateless?
Thanks, Pete
On Tue, May 27, 2008 at 5:38 PM, Bogdan-Andrei Iancu <bogdan@voice-system.ro mailto:bogdan@voice-system.ro> wrote:
Hi Pete, A simple way to do it to load in AVP all the alternative destinations (in whatever order you want). Later, using failure_route, you will consume one by one the existing AVPs until none is left. This will minimize the DB impact. Regards, Bogdan Pete Kay wrote: Hi, I know this kind of function exists in Asterisk, but I want to know if Openser can do it as well. Let's say there are two fail-over numbers(DID-b,DID-c) that associates with a DID(DID-a), if the original number(DID-a) that get dailed can't rearch the destination due to BUSY, NO RESPONSE, etc, is there anyway of having Openser to auto-retry with the next DID(DID-b)? If the next one fails, try the next next one(DID-c). One way I can think of is to do a lookup from DB for the alias in the fail_on_route section, but if I have multiple aliases, then I will have no way of *remembering* which alias has been tried unless I store it in the DB which is not a good solution. I am wondering if there any other way of doing it? Thanks in advance for all your kind suggestion. Regards, Pete ------------------------------------------------------------------------
-
Bogdan-Andrei Iancu -
Iñaki Baz Castillo -
Ovidiu Sas -
Pete Kay