Thanks guys, I was moving down the path of using redis as an alternative to
the dialplan module and it sounds like that is the right direction to go.
Liviu, There were not any additional errors, I'll see if I saved a copy of
the VM I was exploring using dialplan on and look at the MySQL side of
I second this -- strictly discussing implementation, dialplan performs a
simple (and costly) iteration over up-to-all matching rules for each
lookup, while drouting builds an internal trie structure which will
dramatically improve lookup latencies.
Still, regarding the original problem: are
If that's the LCAD or LERG databases, I'd put the data in Redis and query
that. That will give you faster startup times, and won't add much of any
noticeable latency.
Alternatively you could try to do something with the drouting module, which
is designed for very large data sets.
- Jon Abrams
Good Morning,
I am attempting to use dialplan to lookup rate centers on dialed calls to
determine if a caller is dialing outside it's local area.
If I attempt to use the full data set with 167424 rows opensips fails to
start with a failure to query the database.
When I use a smaller data set of
