----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviewboard.asterisk.org/r/3598/ -----------------------------------------------------------
(Updated June 10, 2014, 1:21 p.m.) Review request for Asterisk Developers. Repository: Asterisk Description ------- This change adds persistence support to res_pjsip_pubsub. What does this mean? As subscriptions are created and destroyed their state is kept in sorcery. By default this uses the local astdb but realtime support is also possible. If Asterisk goes down and is restarted these subscriptions are retrieved and recreated as if nothing had happened. Diffs (updated) ----- /branches/12/res/res_pjsip_pubsub.exports.in 415169 /branches/12/res/res_pjsip_pubsub.c 415169 /branches/12/res/res_pjsip_mwi.c 415169 /branches/12/res/res_pjsip_exten_state.c 415169 /branches/12/res/res_pjsip.c 415169 /branches/12/include/asterisk/res_pjsip_pubsub.h 415169 /branches/12/include/asterisk/res_pjsip.h 415169 /branches/12/contrib/ast-db-manage/config/versions/c6d929b23a8_create_pjsip_subscription_persistence_.py PRE-CREATION Diff: https://reviewboard.asterisk.org/r/3598/diff/ Testing ------- Did "core stop now" and "core restart now" multiple times. Confirmed, via wireshark, that the expected NOTIFY was sent out upon startup as if nothing had happened. Tested using the default persistence of going to astdb and also configured it to persist through realtime -> ODBC -> MySQL. Thanks, Joshua Colp
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
