Re: [reSIProcate-users] resip stack vs DUM for a RLS implementation

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

Hi Daniel,

I think starting with the DUM framework makes the most sense.  It already has a bunch of the logic you will need (DialogSet, Dialog and subscription tracking).  It sounds like all of the extra's you need (saving subscription state and reconstructing dialog state) are all great enhancements to have in DUM.  It makes sense that the logic required to reconstruct dialog state be implemented within dum itself, however any persistence of data (ie:  DB or otherwise) should probably be handled at the application level (ie: RLS server).  

It would be great (for the resip community) if you were able to implement the RLS server itself in resip's SVN repository as sever based on resip/dum in a similar manner to how repro exists in the project.

Please contact me directly if you would like to discuss SVN commit access - we can create a branch in SVN for you to do development in.

Regards,

Scott Godin

On Mon, Oct 7, 2013 at 11:55 AM, Daniel Tacalau <dtacalau@xxxxxxxxx> wrote:

Hello All,

This is my  first post to the mailing list, I'd like to say congrats to this project and all devs.

I'm planning to develop a high availability RLS using resiprocate. The server should be able to reconstruct subscriptions state in case of restarts after crashes or on demand restarts. My first option for this project was to use DUM but then I realized DUM doesn't offer API to save subscription state nor reconstruction of DialogSets. I am new to resiprocate so I could be missing something. Would it be possible to extend DUM to support this? If possible I'd like to contribute back to this project by working on the required implementation.

My other option would be to use the resip stack layer and implement additional subscription management and reconstruction on top of it.

In your opinion, what would be the best solution?

Thank You,

Daniel

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/