Hi...
Normally, dial plans are based on some sort of mask. For example, in
Brazil, local fix destination have all 8 digits and start with [2-5]
(mask [2-5][0-9]{7}), local mobile numbers have also 8 digits, but start
with [6-9] (mask [6-9][0-9]{7}); so all local numbers mask would be
[2-9][0-9]{7}... I could continue but You got the idea... ;)
Well, what I'm trying to find is a way to use this kind of definition in
place of (or as) the 'prefix' field, either from LCR or CR module.
The advantages are that with this, not only prefix are matched, but also
some sanity checks, like length, can be done in a single step.
Is this a new feature or is there a way to accomplish this?
Edson.
what are the possible values of 'type' column of 'domain_attrs' table?
it would be nice if s domain module README would contain a reference to
a file where they are described.
-- juha
Module: sip-router
Branch: master
Commit: 9c77d5329b45a493b741527bc8902456dbf51e7e
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=9c77d53…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: Fri Jul 3 20:19:47 2009 +0200
core: km_parse_avp_spec() update
- fallback to ser style of avp name in $avp(id) if 'id' has no ':' and
there is no avp alias defined
- behavior was changed when I added support for K compatible avp aliases
in pv module
- issue reported by Andrei Pelinscu-Onciul
---
usr_avp.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/usr_avp.c b/usr_avp.c
index 6c06721..53f38e4 100644
--- a/usr_avp.c
+++ b/usr_avp.c
@@ -1041,11 +1041,11 @@ int km_parse_avp_spec( str *name, int *type, int_str *avp_name)
p = (char*)memchr((void*)name->s, ':', name->len);
if (p==NULL) {
- /* it's an avp alias */
- return lookup_avp_galias( name, type, avp_name);
- } else {
- return parse_avp_name( name, type, avp_name, &index);
+ /* might be kamailio avp alias or ser avp name style */
+ if(lookup_avp_galias( name, type, avp_name)==0)
+ return 0; /* found */
}
+ return parse_avp_name( name, type, avp_name, &index);
}
Module: sip-router
Branch: master
Commit: db2eed950c3eba36f14ec5bc256120098fe3c024
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=db2eed9…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: Fri Jul 3 20:18:26 2009 +0200
makefile: removed avpops from exclude modules
- it compiles fine after removing ser version and moving the module in
'modules' folder
---
Makefile | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Makefile b/Makefile
index b7ea63f..a98b596 100644
--- a/Makefile
+++ b/Makefile
@@ -205,7 +205,7 @@ else
exclude_modules+= h350
# excluded because they do not compile (remove them only after they are
# fixed) -- andrei
- exclude_modules+= avpops bdb dbtext iptrtpproxy pa rls
+ exclude_modules+= bdb dbtext iptrtpproxy pa rls
endif
# always exclude the CVS dir
when looking at s mysql tables, i noticed that (unlike k tables) they
don't contain a unique id column. is there some reason for that or, the
other way around, what exactly is the reason why k tables do have this
column?
-- juha
would it be possible to reserve some of the db flags as custom (private)
flags that will not be used officially by sr? for example like this:
/*
* Various database flags shared by modules
*/
#define SRDB_LOAD_SER (1 << 0) /* The row should be loaded by SER */
#define SRDB_DISABLED (1 << 1) /* The row is disabled */
#define SRDB_CANON (1 << 2) /* Canonical entry (domain or uri) */
#define SRDB_IS_TO (1 << 3) /* The URI can be used in To */
#define SRDB_IS_FROM (1 << 4) /* The URI can be used in From */
#define SRDB_FOR_SERWEB (1 << 5) /* Credentials instance can be used by serweb */
#define SRDB_PENDING (1 << 6)
#define SRDB_DELETED (1 << 7)
#define SRDB_CALLER_DELETED (1 << 8) /* Accounting table */
#define SRDB_CALLEE_DELETED (1 << 9) /* Accounting table */
#define SRDB_MULTIVALUE (1 << 10) /* Attr_types table */
#define SRDB_FILL_ON_REG (1 << 11) /* Attr_types table */
#define SRDB_REQUIRED (1 << 12) /* Attr_types table */
#define SRDB_DIR (1 << 13) /* Domain_settings table */
#define CUSTOM_1 (1 << 28) /* Reserved */
#define CUSTOM_2 (1 << 29) /* Reserved */
#define CUSTOM_3 (1 << 30) /* Reserved */
#define CUSTOM_4 (1 << 31) /* Reserved */
i would use them by my management system.
-- juha