Re: [reSIProcate-users] Why entries in DialogSetMap stay for a long time?

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

DumTimeout::Registration is used to refresh registrations.  It's duration is based off the registration expiry time, which is typically driven by the registering party (but can be modified by the server).  I'm guessing you are using 3600 seconds as a registration duration, so your refresh timer is set to 3240.  See ClientRegistration.cxx line 525.

ClientRegistration usages will not go away unless you call ClientRegistration::end() (will unregister) or ClientRegistration::stopRegistering().

Scott

On Mon, Jun 22, 2015 at 9:51 AM, Jorge Bustamante <jbustamante@xxxxxxxxxxxxx> wrote:

Hi,

I see entries for registration dialogs staying in DialogSetMap for a long time and I also see this in the logs:

RESIP-Debug: Adding application timer: DumTimeout::Registration: duration=3240 seq=1 ms=3240000

So I assume the timer to remove them is set by default to 3240 seconds.

If this is correct, is there an easy way to change the default timer?

I will look into the code but I am pretty sure it would take me more time to do so if any of you happen to know already.

Regards,

Jorge Bustamante

Learn why you should attend BroadSoft Connections 2015

This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient and have received this email in error, please notify BroadSoft, Inc. immediately by replying to this message, and destroy all copies of this message, along with any attachment, prior to reading, distributing or copying it.

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