Ooops and I was very happy some minutes ago:))) Ok, will wait an options.
Thank you! From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Monday, August 24, 2015 12:58 PM To: dpa; 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] opensips1.11 dr_routing Hold on ! none of the options are available now . I suggested them as options for a fix ;) Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 24.08.2015 12:55, dpa wrote: Second point seems interesting. I will test it. From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Monday, August 24, 2015 12:49 PM To: dpa; 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] opensips1.11 dr_routing Hi Denis, Currently you cannot do this, but I see 2 options: 1) allow a carrier definition to contain other carriers (max 3 levels) 2) have a more complex syntax in destination set definition, with brackets, like: #14,(#34=50,#35=50),#2881 Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 24.08.2015 10:42, dpa wrote: Hello Bogdan! Yes, you are right, I want use only carriers in routing. For example. I have for providers #14, #34, #35, #2881. Let`s say that the goal of some prefix is Prefix "9087": #14 - 1$, #34-2$, #35 - 2$, #2881 - 3$ Prefix "8765": #34-1$, #35-2$, #14-3$, #2881 - 3$ In ideal I want to see in routing table: 9087 #14,#34=50,#35=50,#2881 8765 #34,#35,#14=50,#2881=50 First Opensips make serial routing and then parallel. In method you gave I must create carriers: 34=50, 35=50 34=33, 35=33, 2881=33 an so on. And all these carriers I must remember in another system (which forms routing table) and using it during forming routing table. From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Friday, August 21, 2015 4:35 PM To: dpa; 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] opensips1.11 dr_routing Denis, So what you want to do is to be able to serial and parallel (combined) having carriers as elements in the list (and not GWs). With the solution I gave you cannot do it as you cannot use carriers in the definition of another carrier (when doing the parallel group), right ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 21.08.2015 16:14, dpa wrote: No, Bogdan, everything fine. You wright understand my question. I wanted "do a combination between serial and parallel selection" but method you suggest doesn`t fit to me. The main reason I have many providers and using carrier for "sharing" doesn`t convenient, because I must have all possible combination of carriers and using (remember) it for making routing table (contents of routing table formed by another system, and I do not want complicate it). Thank you. From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Friday, August 21, 2015 3:52 PM To: dpa; 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] opensips1.11 dr_routing Denis, I had the impression that I haven't managed to answer to your question. Maybe because I do not fully understand the question. Could you detail why the solution I gave does not fit you? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 21.08.2015 15:35, dpa wrote: Hello Bogdan! I understand and I thought about it before. But it doesn`t fit to me, because I have many prefix which can "sharing" different carriers. Anyway, thank you for help. From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Friday, August 21, 2015 3:29 PM To: OpenSIPS users mailling list; denis7...@mail.ru Subject: Re: [OpenSIPS-Users] opensips1.11 dr_routing Hi Denis, If you use weights alg and the GW has no weight, a 0 weight will be assumed, so it will never match (unless after a failover). Using weights, the selection is over all the GW in the set. If you want do a combination between serial and parallel selection , you need to use carriers: Make carrier X with wights flags and set for it destinations 34=50,35=50 and in the rule have the destination set "14,#X" (and do not use the W flag anymore) Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 21.08.2015 12:16, dpa wrote: Hello! There is one question about dr_routing module. Example 1. I have such gw_list "#14,#34=50,#35=50,#2881" Example 2. I have such gw_list "#14,#34,#35,#2881" I am using d_routing() with W flag. In Example 1 a call first had been sent to sharing between #34 and #35 and only then to #14. In Example 2 a call first had been sent to #14, then #34, then #35 and #2881. Is there any way to tell Opensips in Example 1 first sends calls to #14 and only then to sharing between #34 and #35? Thank you for any help. _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users