Re: [OpenSIPS-Users] Drouting relay issue

Hi Bogdan Yes, TCP stack works as anticipated. Thanks Volkan Oransoy On 17 May 2022 16:02 +0100, Bogdan-Andrei Iancu , wrote: > Thanks on the follow up here. I guess you need to switch to TCP, right ? > > Regards, > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer >

Re: [OpenSIPS-Users] Drouting relay issue

Thanks on the follow up here. I guess you need to switch to TCP, right ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS eBootcamp 23rd May - 3rd June 2022 https://opensips.org/training/OpenSIPS_eBootcamp_2022/ On 5/17/22 2:10 PM,

Re: [OpenSIPS-Users] Drouting relay issue

Hi all, For further reference, the issue is related to UDP fragmentation. Digitalocean droplet network doesn’t route fragmented packets. I can see only the first part of the fragmented packet, not the subsequent one. So the destination fails with “ICMP ip reassembly time exceeded, length 556”

Re: [OpenSIPS-Users] Drouting relay issue

I think the screenshot has been discarded by the mailman. The sip traffic is as follows. The proxy tries to retransmit and fails after three more attempts. ──┬─ ──┬─ ──┬─  10:47:32.603828 │ INVITE (SDP) │ │  +0.000347 │ ──>

[OpenSIPS-Users] Drouting relay issue

Hi all, I have an interesting issue with one of my test setups. I have a simple routing script which gets the gateway id directly from the header originating from a Freeswith box. The system finds and sets the request URL as anticipated. But even if I can see the request on the proxy, I can't

Re: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1

No, I think that was the only place. Thank you! Ben Newlin From: Bogdan-Andrei Iancu Date: Friday, November 19, 2021 at 2:39 AM To: OpenSIPS users mailling list , Ben Newlin , pke...@gmail.com Subject: Re: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1 Hi Ben, Fixes what I

Re: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1

for dr_carriers routing. Ben Newlin *From: *Users on behalf of Liviu Chircu *Date: *Thursday, November 18, 2021 at 5:14 AM *To: *pke...@gmail.com *Cc: *OpenSIPS users mailling list *Subject: *Re: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1 On 18.11.2021 12:09, Pete Kelly

Re: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1

Cc: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1 On 18.11.2021 12:09, Pete Kelly wrote: > It looks like there are quite a few inconsistencies on the drouting > documentation page versus the docs here > https://opensips.org/doc

Re: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1

On 18.11.2021 12:09, Pete Kelly wrote: It looks like there are quite a few inconsistencies on the drouting documentation page versus the docs here https://opensips.org/docs/modules/3.2.x/cfgutils.html#func_check_time_rec

Re: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1

Cool, it's not just me then! It looks like there are quite a few inconsistencies on the drouting documentation page versus the docs here https://opensips.org/docs/modules/3.2.x/cfgutils.html#func_check_time_rec - so maybe just a link or reference to check_time_rec would work for consistency?

Re: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1

On 18.11.2021 12:02, Pete Kelly wrote: However the format is documented the same way in both 3.1 and 3.2 within the "More on time recurrence" section 3.1: https://opensips.org/html/docs/modules/3.1.x/drouting.html 3.2:

[OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1

Hi I notice that the timerec format has been updated in 3.2, specifically for the drouting module. The migration document mentions that there are a number of changes to the format. Migration document: https://www.opensips.org/Documentation/Migration-3-1-0-to-3-2-0#toc18 However the format is

Re: [OpenSIPS-Users] drouting gw list

like use_next_gw(). Ben Newlin From: Users on behalf of David Villasmil Date: Wednesday, November 10, 2021 at 11:14 AM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] drouting gw list Thanks again Ben, I'm still not understanding: Setting it to (as is, nothing) would then only

Re: [OpenSIPS-Users] drouting gw list

s.org/docs/modules/2.4.x/drouting.html#idp163040 > > > > Ben Newlin > > > > *From: *Users on behalf of David > Villasmil > *Date: *Wednesday, November 10, 2021 at 7:50 AM > *To: *OpenSIPS users mailling list > *Subject: *Re: [OpenSIPS-Users] drouting gw list >

Re: [OpenSIPS-Users] drouting gw list

/drouting.html#idp163040 Ben Newlin From: Users on behalf of David Villasmil Date: Wednesday, November 10, 2021 at 7:50 AM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] drouting gw list Sorry, it's defined in cr_carriers, that's the list of gws which are then defined on dr_gateways

Re: [OpenSIPS-Users] drouting gw list

ou should set the sort_alg column to N. > > > > https://www.opensips.org/Documentation/Install-DBSchema-3-2#GEN-DB-DR-RULES > > > > Ben Newlin > > > > *From: *Users on behalf of David > Villasmil > *Date: *Tuesday, November 9, 2021 at 7:37 PM > *To: *users@lis

Re: [OpenSIPS-Users] drouting gw list

Villasmil Date: Tuesday, November 9, 2021 at 7:37 PM To: users@lists.opensips.org Subject: [OpenSIPS-Users] drouting gw list Hello folks, i have the following gw_list PrimaryGW=100,SecondaryGW=10 I'm seeing calls going to the SecondaryGW. How should i set this if i only want the SecondaryGW

[OpenSIPS-Users] drouting gw list

Hello folks, i have the following gw_list PrimaryGW=100,SecondaryGW=10 I'm seeing calls going to the SecondaryGW. How should i set this if i only want the SecondaryGW to be used for failover? Regards, David Villasmil email: david.villasmil.w...@gmail.com phone: +34669448337

Re: [OpenSIPS-Users] drouting WARNING

Hello, dr_rules has a prefix and gwlist shows cr2 ;  not #cr2 ... What am I missing here? I think it is what you wrote in the comment. Carrier ids are prefixed by '#' in dr_rules. Without this prefix it use gateways directly without carriers. ___

[OpenSIPS-Users] drouting WARNING

I see a WARNING at opensips start/restart : verion 3.1.5 WARNING:drouting:parse_destination_list: destination ID was not found I check my database and : dr_rules has a prefix and gwlist shows cr2 ;  not #cr2 in dr_carriers I see carrierid cr2 and corresponding gwlist has a gw3 in

Re: [OpenSIPS-Users] DROUTING module flag changes

On 04.10.2021 16:35, Ben Newlin wrote: What’s done is done in this case, but something to think about for future breaking changes, especially relating to the DB. Hi Ben, I totally agree with you on this one -- the shifting of the carrier flags in the /drouting/ module was *completely*

Re: [OpenSIPS-Users] DROUTING module flag changes

: [OpenSIPS-Users] DROUTING module flag changes Liviu, Thank you, I do see it there. So it is confirmed the flags have shifted. It appears the module documentation is still in need of some updates to reflect this change for carriers. Ben Newlin From: Liviu Chircu Date: Friday, October 1, 2021

Re: [OpenSIPS-Users] DROUTING module flag changes

, Ben Newlin Subject: Re: [OpenSIPS-Users] DROUTING module flag changes On 01.10.2021 21:34, Ben Newlin wrote: Can anyone clarify the expected behavior here? Were the values for the flags column changed as part of removing the weight flag? Hey Ben, I believe you're referring to a change from 3.1

Re: [OpenSIPS-Users] DROUTING module flag changes

On 01.10.2021 21:34, Ben Newlin wrote: Can anyone clarify the expected behavior here? Were the values for the flags column changed as part of removing the weight flag? Hey Ben, I believe you're referring to a change from 3.1, where the carrier "W" flag was removed & all other flags were

[OpenSIPS-Users] DROUTING module flag changes

Hello, I need some clarification on the new “sort_alg” columns added to the DROUTING module tables in 3.x. The column was added to the DrRules table, and the documentation has been updated to reflect that the “W” flag passed to do_routing is now deprecated and has been replaced by the value

[OpenSIPS-Users] drouting() enable_restart_persistency problem

Hi everyone I've been reading the blog on this subject: https://blog.opensips.org/2019/04/04/no-downtime-for-opensips-3-0-restarts/ But when I enable the enable_restart_persistency parameter OpenSIPS fails to start. With log level 4 I get: DBG:core:init_mod: initializing module drouting

Re: [OpenSIPS-Users] Drouting failover by carrier only

o skip to the next >>> carrier you just call route_to_carrier again with the next ID in your list. >>> >>> >>> >>> This solved two problem for us: >>> >>> * allows us to fail over by carrier instead of just by gateway >>> >>&

Re: [OpenSIPS-Users] Drouting failover by carrier only

n with the next ID in your list. >> >> >> >> This solved two problem for us: >> >> * allows us to fail over by carrier instead of just by gateway >> >> * allows us to call do_routing multiple times for a call with >different >> groups and aggr

Re: [OpenSIPS-Users] Drouting failover by carrier only

/docs/modules/3.0.x/drouting.html#param_carrier_id_avp > > [2] - > https://opensips.org/docs/modules/3.0.x/drouting.html#func_route_to_carrier > > > > > > Ben Newlin > > > > *From: *Users on behalf of Alex A < > ale...@gtanetworkconsulting.com> > *Reply-To

Re: [OpenSIPS-Users] Drouting failover by carrier only

tworkconsulting.com> Reply-To: OpenSIPS users mailling list <mailto:users@lists.opensips.org> Date: Wednesday, April 29, 2020 at 2:40 PM To: users <mailto:users@lists.opensips.org> Subject: [OpenSIPS-Users] Drouting failover by carrier only   Hi Everyone,   Is it possible to failove

Re: [OpenSIPS-Users] Drouting failover by carrier only

orkconsulting.com> Reply-To: OpenSIPS users mailling list <mailto:users@lists.opensips.org> Date: Wednesday, April 29, 2020 at 2:40 PM To: users <mailto:users@lists.opensips.org> Subject: [OpenSIPS-Users] Drouting failover by carrier only   Hi Everyone,   Is it possible

Re: [OpenSIPS-Users] Drouting failover by carrier only

Hi Bogdan, Will "use only the first gateway from the carrier"  allow for round-robin for the regular calls (ie. does it choose the first gw randomly ) ? Thank you. Alex On Thu, 30 Apr 2020 03:40:21 -0400 Bogdan-Andrei Iancu wrote Hi Alex, Have you

Re: [OpenSIPS-Users] Drouting failover by carrier only

Hi Alex, Have you tried the "use only the first GW" flag in the carrier definition? See https://opensips.org/html/docs/modules/3.0.x/drouting.html#idp25339408, "Carriers" subsection: flags : 0x1 - use weight for sorting the list and not definition order; 0x2 - use only the first gateway

Re: [OpenSIPS-Users] Drouting failover by carrier only

/drouting.html#func_route_to_carrier Ben Newlin From: Users on behalf of Alex A Reply-To: OpenSIPS users mailling list Date: Wednesday, April 29, 2020 at 2:40 PM To: users Subject: [OpenSIPS-Users] Drouting failover by carrier only Hi Everyone, Is it possible to failover to next carrier

[OpenSIPS-Users] Drouting failover by carrier only

Hi Everyone, Is it possible to failover to next carrier (instead next gateway) while using drouting? I got the below to work; however currently, use_next_gw gets the next gateway in the list, so if gwlist= #0,#3  and one of the carriers has multiple gateway IPs, the retry happens

Re: [OpenSIPS-Users] drouting probe_mode in active/passive cluster

You are 100% right Alexey, I was just to lure Jeff to go for 3.0 ;) Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit, Amsterdam, May 2020 https://www.opensips.org/events/Summit-2020Amsterdam/ On 4/13/20 6:11 PM, Alexey Vasilyev

Re: [OpenSIPS-Users] drouting probe_mode in active/passive cluster

Hi Bogdan, Yes, of course, in 3.0 you have implemented full support for the sharing tags. But when these commits were made, the sharing tags were only in process of discussion. So it's absolutely temporarily solution only for 2.4 branch. And for Jeff, there is no modparam. Just call

Re: [OpenSIPS-Users] drouting probe_mode in active/passive cluster

Hi guys, actually 3.0 provides a better approach to the problem, by using the sharing tags provided by the clustering layer [1]. Only the OpenSIPS instance having the tag active will perform the pinging/probing and broadcast the status changes into the cluster. Unfortunately 2.4 does not

Re: [OpenSIPS-Users] drouting probe_mode in active/passive cluster

Hi Alexey, I see the "dr_enable_probing" MI command; that's great! Is there an equivalent modparam I can add to default to 0, so that it will only probe when we know it has the IP (when enabled by MI)? It will be some time until I'm able to cherry-pick and test. The two proxies are currently

Re: [OpenSIPS-Users] drouting probe_mode in active/passive cluster

Hi Jeff. I made one solution for 2.4. You can cherry-pick https://github.com/OpenSIPS/opensips/commit/05ca54a37d82c605e2cd6d10e5a62fb4f7c35b78 And may be this: https://github.com/OpenSIPS/opensips/commit/94a3ede1e276984a91f93f6ece832d174b071ab8 There is documentation in commits. - ---

[OpenSIPS-Users] drouting probe_mode in active/passive cluster

Hello, On v2.4.7 I have a two-node cluster configured as active/standby with keepalived managing which side has the IP. I want to use drouting probe_mode=2, but I don't see how to prevent the passive side from trying to ping the gateways even when it doesn't have the IP. And, of course, it

Re: [OpenSIPS-Users] drouting gateway status with route_to_gw()

Hi Jeff, Yeah, the route_to_gw() gives you raw, low level access to the routing, so the whole soring and filtering mechanisms are skipped. This is why the status is not checked, but it makes sense, as time as you can specify a list of GWs. Could you open a bug report on this please ? About

[OpenSIPS-Users] drouting gateway status with route_to_gw()

Hello, On v2.4.7 I'm using route_to_gw() to load routing for a particular gateway. It works well. It also works when the gateway is in an "Inactive" status, which surprises me. I would expect the function to return with an error code in that scenario, or at least have the option to achieve

Re: [OpenSIPS-Users] [Drouting] failed to add rule id 176415 -> skipping, add_prefix: is not decimal digit

Please, ignore this. My application was indeed putting special characters and opensips was correcting pointing it. Ryan. On Sat, 19 Oct 2019 at 15:12, Ryan embgrets wrote: > Good day, > > Whenever I do a restart/reload of opensips/drouting records, my opensips > gives below logs. > > Oct 19

[OpenSIPS-Users] [Drouting] failed to add rule id 176415 -> skipping, add_prefix: is not decimal digit

Good day, Whenever I do a restart/reload of opensips/drouting records, my opensips gives below logs. Oct 19 09:53:11 home /usr/sbin/opensips[30138]: ERROR:drouting:add_prefix: is not decimal digit Oct 19 09:53:11 home /usr/sbin/opensips[30138]: ERROR:drouting:add_rule: failed to add prefix route

Re: [OpenSIPS-Users] drouting() number matching

Hi Mark, Using the group support in drouting is optional. You can directly supply the routing group as parameter to the do_routing() function - this gives you the possibility to use more flexible way to determine the routing group, like using the dialplan module (which does regexp based

Re: [OpenSIPS-Users] drouting() number matching

OK I think I realised my mistake - rules are matched on longest prefix. So I think my question should be: Can I use the same principle for usernames in groups? On a side note, is it possible to match the group based on the destination domain instead of the source domain? Thanks Mark. On Mon,

[OpenSIPS-Users] drouting() number matching

Hi everyone, can I use pattern matching in drouting groups and rules? So for example I'd like to match on +4412345678*@example.com In Asterisk dialplan I would do _+4412345678X Many thanks Mark. -- Mark Farmer farm...@gmail.com ___ Users mailing

[OpenSIPS-Users] drouting() Function Availability

Hi everyone I am confused about when drouting() functions become available. I resolved an issue using is_from_gw() & goes_to_gw() by using them after do_routing(). But looking at my trunking script I see that is_from_gw() is being used before do_routing() to check if the call is coming from a

Re: [OpenSIPS-Users] drouting module in opensips 2.4

Hi Kirill, Starting with 2.4 there is a change in how the initial load is done by drouting (and other modules). If previously the the initial load was part of the module init sequence (and delaying the whole opensips init with this load), now the load is done after the init sequence, so

[OpenSIPS-Users] drouting module in opensips 2.4

Hi all I migrate from 2.3 to in 2.4 on Centos 7.4. OpenSIPS 2.3 starts without going to background, while drouting module fetches all rules from DB into memory. OpenSIPS 2.4 goes to background immediately, and fetches rules only after that. If you try opensipsctl fifo dr_number_routing mts 0

Re: [OpenSIPS-Users] DROUTING: order and priority

Now, the script remains as it was (no changes): if( $(rU{s.len}) > 3 ) { set_dlg_profile("callout"); if(!do_routing("", "W")) { sl_send_reply("500", "DRouting Error"); exit; } } But I

[OpenSIPS-Users] DROUTING: order and priority

Hi list! Last days I'm trying to master DROUTING module usage. This is a piece of script: if( $(rU{s.len}) > 3 ) { set_dlg_profile("callout"); if(!do_routing("", "W")) { sl_send_reply("500", "DRouting Error");

Re: [OpenSIPS-Users] drouting rule_id is empty

Hi Bogdan. Thanks a lot. Everything right now. 2018-05-22 13:33 GMT+03:00 Bogdan-Andrei Iancu : > Hi Kirill, > > I see you use partitions, and your lookup is over partition "1". So, in > the dr_partitions table, when defining the partition "1", have you set the >

Re: [OpenSIPS-Users] drouting rule_id is empty

Hi Kirill, I see you use partitions, and your lookup is over partition "1". So, in the dr_partitions table, when defining the partition "1", have you set the "|rule_id_avp" field to "|$avp(dr_rule_id)" ? http://www.opensips.org/Documentation/Install-DBSchema-2-3#GEN-DB-DR-PARTITIONS

[OpenSIPS-Users] drouting rule_id is empty

Hi i use opensips 2.3 (OpenSIPS (2.3.3 (x86_64/linux)) drouting And I need rule_id variable to store in CDR. modparam("drouting", "use_partitions", 1) modparam("drouting", "carrier_id_avp", '$avp(carrier_id)') modparam("drouting", "partition_id_pvar", "$var(matched_partition)")

Re: [OpenSIPS-Users] drouting: need more information about a feature

Hi, I hope, it will be completed in the future. Thank you for your feedback. Abdoul OSSENI Ingénieur DevOps chez Néo-Soft Co-Fondateur de ON SERVICES Tél : +33 601 135 167 Le jeu. 12 avr. 2018 à 22:03, Bogdan-Andrei Iancu a écrit : > Hi, > > This module was never

Re: [OpenSIPS-Users] drouting: need more information about a feature

Hi, This module was never completed and never pushed to the public tree. Maybe in the future :) Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com OpenSIPS Summit 2018 http://www.opensips.org/events/Summit-2018Amsterdam On 04/09/2018

[OpenSIPS-Users] drouting: need more information about a feature

Hello Dear list, According to this email https://opensips.org/pipermail/users/2014-September/029817.html, drouting can reorder the gateways according PDD, ASR and ACD stats. Can you explain me how it works and how can I enable this feature? Thank you for your works. Abdoul.

Re: [OpenSIPS-Users] drouting module -- How to use registered gatewayas outbound gateway

opensips.org>; "Jeffrey Zhao"<chunyong.z...@qq.com>; Subject: Re: [OpenSIPS-Users] drouting module -- How to use registered gatewayas outbound gateway You could also put the AoR that the gateways will use to register as an attribute on the rule/carrier/gateway in D

Re: [OpenSIPS-Users] drouting module -- How to use registered gateway as outbound gateway

oun...@lists.opensips.org> on behalf of Bogdan-Andrei Iancu <bog...@opensips.org> Reply-To: OpenSIPS users mailling list <users@lists.opensips.org> Date: Friday, December 15, 2017 at 11:35 AM To: OpenSIPS users mailling list <users@lists.opensips.org>, Jeffrey Zhao <chunyong.z...@qq.com>

Re: [OpenSIPS-Users] drouting module -- How to use registered gateway as outbound gateway

Hi Jeffrey, To do something like that, you need to have in DR (as gateway) the AOR used by the GW to register with. And after you do do_routing() you do lookup(location). Now the tricky part is to link them, as Drouting is IP/domain driven while user location is AOR driven. So, in DR use

[OpenSIPS-Users] drouting module -- How to use registered gateway as outbound gateway

Dear all We are using drouting module for dialplan routing, for NAT issues, we need to register outbound voice gateway to opensips, instead of fixed static IP. Is there any way to use registered gateway as routing destination? Thanks. ___ Users

Re: [OpenSIPS-Users] drouting (opensips 1.11.x) - maximum number of gateways?

Thanks for the hint. I will keep an eye on it. BR Max M. Von: Bogdan-Andrei Iancu <bog...@opensips.org> Gesendet: Montag, 3. Juli 2017 12:49:21 An: Max Mühlbronner; OpenSIPS users mailling list Betreff: Re: AW: [OpenSIPS-Users] drouting (opensips

Re: [OpenSIPS-Users] drouting (opensips 1.11.x) - maximum number of gateways?

25 *An:* OpenSIPS users mailling list *Betreff:* [OpenSIPS-Users] drouting (opensips 1.11.x) - maximum number of gateways? Hi, I've never noticed this until i came across it recently. I got a weird issue with drouting, it turned out that even though the gatewaylist ("carrier") contains

Re: [OpenSIPS-Users] drouting (opensips 1.11.x) - maximum number of gateways?

ag, 3. Juli 2017 12:18:42 An: OpenSIPS users mailling list; Max Mühlbronner Betreff: Re: [OpenSIPS-Users] drouting (opensips 1.11.x) - maximum number of gateways? Hi Max, Yes, a transaction cannot have more than 12 branches used. But this does not limit how many GWs you can put in Dynamic Routi

Re: [OpenSIPS-Users] drouting (opensips 1.11.x) - maximum number of gateways?

mediately. *Von:* Users <users-boun...@lists.opensips.org> im Auftrag von Max Mühlbronner <max.muehlbron...@42com.com> *Gesendet:* Montag, 3. Juli 2017 10:38:25 *An:* OpenSIPS users mailling list *Betreff:* [OpenSIPS-Users] drou

Re: [OpenSIPS-Users] drouting (opensips 1.11.x) - maximum number of gateways?

t;users-boun...@lists.opensips.org> im Auftrag von Max Mühlbronner <max.muehlbron...@42com.com> Gesendet: Montag, 3. Juli 2017 10:38:25 An: OpenSIPS users mailling list Betreff: [OpenSIPS-Users] drouting (opensips 1.11.x) - maximum number of gateways? Hi, I've never noticed this until i came

[OpenSIPS-Users] drouting (opensips 1.11.x) - maximum number of gateways?

Hi, I've never noticed this until i came across it recently. I got a weird issue with drouting, it turned out that even though the gatewaylist ("carrier") contains a total of 20 gateways, only 12 are being used. (all gateways got the same weight) E.g. if all gws are rejecting the calls, it

Re: [OpenSIPS-Users] DRouting in v2.2.3 is not overwriting the R-URI

Update - problem solved. It was bad data. I had a value of 1 in the dr_rules.routeid field which caused do_routing to call route[1] which contained a t_relay statement. This mistake was made after following the example for adding a new rule shown in opensipsctl help: dr addrule '10,20' '+1'

Re: [OpenSIPS-Users] DRouting in v2.2.3 is not overwriting the R-URI

Hi, John! The do_routing() function is not adding a branch so it must be added by someone/something else. What branch is first sent? The one to the gateway, or the one? Can you provide a trace for such a call? If privacy is a concern, send it privately. Best regards, Răzvan Crainea OpenSIPS

[OpenSIPS-Users] DRouting in v2.2.3 is not overwriting the R-URI

Hello, While testing with v2.2.3 it looks like the behaviour of the do_routing() function in the DROUTING module has changed. From packet captures, I can see the call is parallel forking to the original R-URI *and* to the first choice gateway destination from DRouting. OpenSIPS sends two INVITE's

[OpenSIPS-Users] Drouting use next gateway adding too many vias

Hi, I'm testing out new carrier which has 3 different endpoits for us to connect to. I've setup the 3 addresses in the DR_Rules table and the first call or calls to a different address directly work. however, when a call fails ad I select the next gateway the originating asteris box failed

Re: [OpenSIPS-Users] drouting

Ok Bogdan. I'll try 2016-09-20 22:57 GMT+03:00 Bogdan-Andrei Iancu : > Hi Kirill, > > The logs says that a rule was found, but now GW (destination) was selected > to be used. > > I see you checked the status of the GWs, but please check the status of the > carriers also: >

Re: [OpenSIPS-Users] drouting

Hi Kirill, The logs says that a rule was found, but now GW (destination) was selected to be used. I see you checked the status of the GWs, but please check the status of the carriers also: http://www.opensips.org/html/docs/modules/2.2.x/drouting.html#id296588 Regards, Bogdan-Andrei Iancu

Re: [OpenSIPS-Users] drouting

Sorry ...do_routing(1) Thanks Jeff Wilkie USIP Communications On Sep 20, 2016 8:45 AM, "Kirill Galinurov" wrote: > Hello Bogdan. I try drouting() without any parameters. > > 2016-09-20 14:20 GMT+03:00 Bogdan-Andrei Iancu : > > Hello Kirill, > > > >

Re: [OpenSIPS-Users] drouting

Use the group 1 you created in the command drouting(1) to send out using group 1. Thanks Jeff Wilkie USIP Communications On Sep 20, 2016 8:45 AM, "Kirill Galinurov" wrote: > Hello Bogdan. I try drouting() without any parameters. > > 2016-09-20 14:20 GMT+03:00

Re: [OpenSIPS-Users] drouting

Hello Bogdan. I try drouting() without any parameters. 2016-09-20 14:20 GMT+03:00 Bogdan-Andrei Iancu : > Hello Kirill, > > I see the MI command succeeded, right? but the scrip do_routing() fails ? > what are the parameters you pass to do_routing() ? > > Best regards, > >

Re: [OpenSIPS-Users] drouting

Hello Kirill, I see the MI command succeeded, right? but the scrip do_routing() fails ? what are the parameters you pass to do_routing() ? Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 19.09.2016 15:50, Kirill Galinurov wrote: Hi all

[OpenSIPS-Users] drouting

Hi all I try to use drouting module. Sep 19 17:18:28 [37245] DBG:drouting:do_routing: using dr group 1, rule_idx 0, username 79632780099 Sep 19 17:18:28 [37245] DBG:drouting:internal_check_rt: found rgid 1 (rule list 0x7fe60616b800) Sep 19 17:18:28 [37245] INFO:drouting:do_routing: no destination

Re: [OpenSIPS-Users] Drouting memory usage

Yes, it makes sense as the crash (on bogus mem ops) was related to an invalid Contact URI in the SIP request. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 18.05.2016 17:06, John Nash wrote: OK. will update.Thank you. SIP message validate in

Re: [OpenSIPS-Users] Drouting memory usage

OK. will update.Thank you. SIP message validate in the script seemed to have stopped this crash or its not related to that? On Wed, May 18, 2016 at 5:51 PM, Bogdan-Andrei Iancu wrote: > Hi John, > > Thanks for the info, I managed to find the bug and have it fixed: > >

Re: [OpenSIPS-Users] Drouting memory usage

Hi John, Thanks for the info, I managed to find the bug and have it fixed: https://github.com/OpenSIPS/opensips/commit/4b0fca533cd7be4a45c1381c78f2b37aaba6152b Please update from GIT and let me know if you still have the problem. Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and

Re: [OpenSIPS-Users] Drouting memory usage

Hello Bogdan, The version is Server:: OpenSIPS (2.1.2 (x86_64/linux)) Since this is live we do not have detailed debug. Below is what happened before crash (We had multiple such entries). I figured it might be related to malformed SIP message so I applied sipmsg_validate() function even for so

Re: [OpenSIPS-Users] Drouting memory usage

Hi Nash, What version of OpenSIPS are you using ? also, before that CRITICAL message, do you see any other error messages in the logs ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 12.05.2016 08:46, John Nash wrote: Actually crash happened

Re: [OpenSIPS-Users] Drouting memory usage

Actually crash happened shortly after we uploaded 11000 codes but looks like it is not related to drouting. I see following message CRITICAL:topology_hiding:build_encoded_contact_suffix: #012>>> pkg_free() on non-pkg ptr 0x18 - aborting!#012#012It seems you have hit a programming bug.#012Please

[OpenSIPS-Users] Drouting memory usage

I have been using drouting module with just 200 entries from 8 months yesterday we had need of adding around 11000 entries in rules table but after that opensips started to crash. I am currently using -m 2048 -M 1024 isn't it enough memory? How can I anticipate memory usage? John

Re: [OpenSIPS-Users] Drouting stripping and adding prefix

Thank you. It works that way for me. On Wed, Nov 18, 2015 at 3:45 PM, Bogdan-Andrei Iancu wrote: > Hi John, > > Simply redefine the gateway multiple times, same IP, but different ID, > strip and prefix > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and

Re: [OpenSIPS-Users] Drouting stripping and adding prefix

Hi John, Simply redefine the gateway multiple times, same IP, but different ID, strip and prefix Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 17.11.2015 08:34, John Nash wrote: I am using Drouting module and quite happy with it. I have

[OpenSIPS-Users] Drouting stripping and adding prefix

I am using Drouting module and quite happy with it. I have some new requirement where I need to be able to strip some digits from "incoming" number and add some prefix at dr_rule level. I know I can do that at dr_gateway wise but as per my new requirement I need to use same gateway for routing for

[OpenSIPS-Users] Drouting Probing broken 1.11.1

Hi All, when implementing gateway probing type (2) - probing all the time. If disabled, the destination will be automatically re-enabled when the probing will succeed next time; If a gateway fails it does not come back automatically. I have to go into the DB, set state to 0 and reload drouting.

Re: [OpenSIPS-Users] DRouting and Range of numbers

Hi, Ali! Unfortunately drouting works only prefix based, so unless you write specific rules for the 5 numbers (i.e. add rules for each number from 8881231231 to 8881231235 in the table), you cannot achieve this. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On

Re: [OpenSIPS-Users] DRouting and Range of numbers

Hi Razvan. Thank you for the response. Regards, Ali Pey On Fri, Mar 27, 2015 at 4:29 AM, Răzvan Crainea raz...@opensips.org wrote: Hi, Ali! Unfortunately drouting works only prefix based, so unless you write specific rules for the 5 numbers (i.e. add rules for each number from

[OpenSIPS-Users] DRouting and Range of numbers

Hello, Is it possible to have a rule with a range of numbers in Dynamic routing? For instance I want 8881231231 to 5 to be routed to a specific gw. Can I do this with one rule only? I don't want 8881231236 to 9 to be routed to that gateway. Thanks, Ali Pey

Re: [OpenSIPS-Users] DROUTING module changing Carrier IDs

Hi Ben, If you run the dr_carrier_status MI command, do you see the same #012 in the ID of the carrier ? #012 is '\n' - are you sure you do not have it by mistake in DB ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 25.03.2015 21:53,

Re: [OpenSIPS-Users] DROUTING module changing Carrier IDs

in the right direction. Ben Newlin *From:*users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] *On Behalf Of *Newlin, Ben *Sent:* Thursday, March 26, 2015 10:54 AM *To:* Bogdan-Andrei Iancu; OpenSIPS users mailling list *Subject:* Re: [OpenSIPS-Users] DROUTING module changing

Re: [OpenSIPS-Users] DROUTING module changing Carrier IDs

-Andrei Iancu [mailto:bog...@opensips.org] Sent: Thursday, March 26, 2015 10:02 AM To: OpenSIPS users mailling list; Newlin, Ben Subject: Re: [OpenSIPS-Users] DROUTING module changing Carrier IDs Hi Ben, If you run the dr_carrier_status MI command, do you see the same #012 in the ID of the carrier

Re: [OpenSIPS-Users] DROUTING module changing Carrier IDs

, 2015 10:54 AM To: Bogdan-Andrei Iancu; OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] DROUTING module changing Carrier IDs Bogdan, It did occur to me that the code seemed to be the octal for newline, but I don't know what the significance of that could be. The MI command output

[OpenSIPS-Users] DROUTING module changing Carrier IDs

I am using OpenSIPS 1.11 and I am recently getting some weird behavior from the DROUTING module. The module is corrupting the Carrier ID that is being returned via AVP. This behavior is occurring only with the Carrier ID, not the gateway or rule IDs, and only when it is returned from the

Re: [OpenSIPS-Users] Drouting error All the gateways are disabled

Hi, Satish! Do you have any rules provisioned in the DB that use the gateway? Is the gateway pinging turned on? Can you trace the SIP messages between OpenSIPS and gateway to check if the GW replies with a positive code (or replies at all)? Best regards, Răzvan Crainea OpenSIPS Solutions

  1   2   3   >