On Tue, Feb 10, 2009 at 5:50 PM, Benny Prijono <bennylp at teluu.com> wrote: > On Mon, Feb 9, 2009 at 10:19 AM, Gang Liu <gangban.lau at gmail.com> wrote: >> >> Hi benny, >> I am finding a way to save pjsip dialog information to external >> and restore dialogs if needed. >> Like below: >> >> pj_status_t pjsip_dlg_store_connected(pjsip_dialog *dlg, char * >> buf, int * buf_size) >> copies all parameters from a given dialog to a given buffer. This >> buffer should be supplied when restoring the dialog. >> >> pj_status_t pjsip_dlg_restore_connected(pjsip_user_agent *ua, char >> * buf, int buf_size, pjsip_dialog **p_dlg) >> restores all parameters from a given buffer. The dialog will >> assume the connected state. >> >> Could you give me some guideline to implement this? It will be >> great to add HA feature into pjsip stack when using UDP transport. >> > > I think it's quite tedious to add HA (I'm not saying it can't be done). Not > only the dialog, you also need to store/restore the invite session as well. > Then propagate the API all the way up to application. > Today I spent some time to check sofia-sip and resiprocate, it seems they don't have such features too. Maybe it is quite difficult to patch it if not take care of internal data restore in mind when stack start up. > Alternatively, have you considered other approach, such as using > INVITE+Replaces? An entity would monitor the state of the HA agents (saving > the key dialog properties such as Call-Id and tags), and when it detects an > agent is down, it transfer the call (using INVITE+Replaces) to another > agent. > That's a great idea. Thanks. I will have a try. Use transaction level API to build dialog-stateless app and store all high level data into external db may be also another idea. > cheers > Benny > > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > >
