MOD DIALPLAN v2.1.2: New Dialplan Features (same as pull request #794)

[Parantido]

• Rules preload/translate alghoritm reworked: no more needs to have different buckets for REGEXP and BEST MATCH ones. All rules belong from same bucket. This way opens to many different scenarios and future development without afflicting performances (this rework will also fix issue Wrong rule selected in dialplan translation when both string and regexp rules are matched #696 Wrong rule selected in dialplan translation when both string and regexp rules are matched #696).

• New "match_var" database column introduced. This column will override "src/dest" dp_translate parameter when filled. It respects same syntax (wrong syntax will cause rule to being discarded at preload time).

• New "matched_pvar" AVP introduced. It will be filled with last matched rule id. AVP name can be set by modparam directive:

  modparam("dialplan", "matched_pvar", "$avp(dp_ruleid)")
  

• New "continue_search" database column introduced. When filled to "1", rule matching will continue through other rules. ATTRS and MATCHED_PVAR will be updated as soon as rule matches (next rule match will works on PVAR updated values). After a dp_translate ATTRS and MATCHED_PVAR will be updated with last rule match values.

[Parantido]

Sorry I totally missed database schema

CREATE TABLE IF NOT EXISTS dialplan (
id int(10) unsigned NOT NULL AUTO_INCREMENT,
dpid int(11) unsigned DEFAULT NULL,
pr int(11) NOT NULL,
match_op int(11) NOT NULL,
match_exp char(64) NOT NULL,
match_flags int(11) DEFAULT NULL,
match_len int(11) NOT NULL,
subst_exp char(64) NOT NULL,
repl_exp char(32) NOT NULL,
disabled int(11) NOT NULL DEFAULT '0',
attrs char(32) DEFAULT NULL,
timerec varchar(255) NOT NULL DEFAULT '',
match_var char(32) DEFAULT NULL,
continue_search tinyint(1) NOT NULL DEFAULT '0',
PRIMARY KEY (id),
);

[Parantido]

Hi staff,

sorry for bugging you, I just would to know if logical approach used in related code relase was good for you.

If so I've other features to add.

Thank you

[bogdan-iancu]

Hi @Parantido, does this PR obsolete #794 ?

[Parantido]

Hi @bogdan-iancu I made same changes done in 2.2 (dev) in 2.1 also (stable).
Is this wrong?

[bogdan-iancu]

@Parantido , 2.1 is a stable version only bug fixes are accepted. New features or improvements go only into devel version.
So we need to close this PR and follow only the one for 2.2 devel version

[Parantido]

Ok, understood.