Why would you go through the trouble of encapsulating that in some sort of presence layer? Just query Redis directly with redis_cmd() from the ndb_redis module.
Whether you need an SQL database or can get by with Redis is a complex topic. It's ultimately a question of how complicated a feature set you need and the structure of your data and workflow as a whole. When viewed in isolation, as a single objective, routing with Redis appears to be much more performant. But most call routing platforms consist of a lot more database interactions than just a single route lookup. That's where the added value of a full-on RDBM becomes relevant. -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ Sent from my BlackBerry. _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
