[reSIProcate] NOTIFY retransmit, bug or feature?
Adam Roach
adam at nostrum.com
Thu Nov 24 17:49:47 CST 2011
On Nov 24, 2011, at 2:22, Robert Szokovacs <robert.szokovacs at gamma.co.uk> wrote:
>
> On the other hand, even if the resiprocate's notifier logic stays the same,
> the application developer should be provided with an API to be able to
> serialize the NOTIFYs. Currently, there is no callback called when the OK
> arrives in response to a NOTIFY (see resip/dum/ServerSubscription.cxx:296)
I would think that what you really want, from an app perspective, is the ability to just keep putting new resource state documents into resip, and have it worry about serialization. Perhaps this is something we would turn on and off in a profile...
/a
More information about the resiprocate-devel
mailing list