[OpenSIPS-Devel] [ opensips-Bugs-3516034 ] DROUTING - postgresql, routid param in dr_rules

SourceForge.net noreply at sourceforge.net
Mon Apr 9 11:27:04 CEST 2012


Bugs item #3516034, was opened at 2012-04-09 02:27
Message generated for change (Tracker Item Submitted) made by nikbyte
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3516034&group_id=232389

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: 1.8.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nick Altmann (nikbyte)
Assigned to: Nobody/Anonymous (nobody)
Summary: DROUTING - postgresql, routid param in dr_rules

Initial Comment:
I use drouting with postgresql in 1.8 (and 1.7 too).
In documentation written that I should not define this column if I don't like to run route after rule matched.
Here Bogdan wrote that I should leave this column null:
http://lists.opensips.org/pipermail/users/2010-January/010273.html

If I do update dr_rules set routeid='', then in log I see messages like:
Apr  9 13:22:39 opensips opensips[5645]: ERROR:drouting:build_rt_info: failed to parse the destinations
Apr  9 13:22:39 opensips opensips[5645]: ERROR:drouting:dr_load_routing_info: failed to add routing info for rule id 11 -> skipping

If I allow nulls in table (alter table dr_rules alter column routeid drop not null) and do update dr_rules set routeid=null, then I see messages like:
Apr  9 13:23:50 opensips opensips[5844]: ERROR:drouting:parse_destination_list: bad char #000 (-15723487) [8,9;11,12]
Apr  9 13:23:50 opensips opensips[5844]: ERROR:drouting:add_carrier: failed to parse the destinations
Apr  9 13:23:50 opensips opensips[5844]: ERROR:drouting:dr_load_routing_info: failed to add carrier db_id 4 -> skipping
And then opensips exits (without generating core).

If I do update dr_rules set routeid='0', then I see:
Apr  9 13:24:47 opensips opensips[6020]: WARNING:drouting:dr_load_routing_info: route <0> does not exist
I think it's not correct, but in this variant drouting works.
Also I don't understand why it cannot find route 0 if it defined in my script (If it would find it it will be great bug when it will run route[0] after rule matched???)

I think it's not correct and drouting module should accept null value in db.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3516034&group_id=232389



More information about the Devel mailing list