Re: [reSIProcate] ClientRegistration refresh problem

["Meir Elberg" <elbergm@xxxxxxxxx>]

I have the same problem when designing a B2B.

Is there an no option to add a stopRefreshing method the same way as there is the stopRegistering method ?

 

On 5/8/06, ventego networks <ventego@xxxxxxxxx> wrote:

Hi all,

 

Is there an easy way to disable the automatic REGISTER refresh mechanism without killing the Dialog?

Currently what I saw is that ClientRegistration:: requestRefresh updates the timer that makes automatic re-registrations,

I want to use my own timer for it – change requestRefresh to simply send a REGISTER request (that will contain the same dialog ID and authentication header as the last REGISTER sent). I don't want to send these messages twice (once by me and once by the automatic DUM mechanism).

 

What may be the consequences of me disabling the lines of code that handle the refresh timer?

Thanks in advance

Kate

_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel