[reSIProcate-users] resip stack vs DUM for a RLS implementation
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?
Daniel