Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#1375 closed enhancement (fixed)

Option to control first re-registration retry interval

Reported by: bennylp Owned by: bennylp
Priority: normal Milestone: release-1.12
Component: pjsua-lib Version: 1.x-branch
Keywords: Cc:
Backport to 1.x milestone: Backported:

Description (last modified by bennylp)

Ticket #1044 adds pjsua_acc_config.reg_retry_interval to control account interval to retry registration in case it failed. However when the registration is disconnected because of transport failure (e.g. TCP transport closure), the initial retry would happen immediately.

This ticket adds new setting, pjsua_acc_config.reg_first_retry_interval, to control the interval of the first retry. The default value is zero, which means registration retry will be done immediately after failure.

Note that in case there are calls active when the TCP transport is disconnected, these calls will be hung up only after the first registration retry fails, hence it is recommended to set pjsua_acc_config.reg_first_retry_interval to low value.

This ticket also adds random +/- 10 seconds to the interval, so that clients wouldn't re-register at the same time thus causing high load to server.

Change History (4)

comment:1 Changed 13 years ago by bennylp

  • Description modified (diff)

comment:2 Changed 13 years ago by bennylp

  • Resolution set to fixed
  • Status changed from new to closed

(In [3762]) Added option to control first re-registration retry interval. This closes #1375

comment:3 Changed 13 years ago by bennylp

(In [3769]) More re #1375: added log showing the interval when scheduling the registration retry

comment:4 Changed 13 years ago by bennylp

(In [3770]) More re #1375: fixed bug, the reg_first_retry interval is not copied to account config with pjsua_acc_modify()!

Note: See TracTickets for help on using tickets.