That or replication would work, but I need it for redundancy. If the triggered/replicated table would no longer be available due to an outage of the database, then I would lose logging.
Would have been a cool feature to have the messages duplicated to multiple capture servers or tables. -----Original Message----- From: sr-users-boun...@lists.sip-router.org [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Alex Balashov Sent: Thursday, November 21, 2013 4:49 PM To: sr-users@lists.sip-router.org Subject: Re: [SR-Users] siptrace & sipcapture - write to multiple tables It seems to me that this could be accomplished with triggers on the single receiving table. -- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ _______________________________________________ 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 _______________________________________________ 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
