Skip to content

implement new registration retry mechanism in failure cases, REF14471

Wenpeng Song requested to merge 14471-registration-retry into asterisk_rdkb
  • cherry-pick the following changes from devel
- When SIP response 408/503/500 is received for SIP Register requests
  to all server addresses, the failover retry will be scheduled
  with certain time interval.

- If number of continuous failed retries reached 'failover_max_retries',
  the SIP registraion will be given up. By default, the number is '-1',
  i.e. unlimited.

- 'failover_interval1' is used between normal failover retries, which
  is 10 seconds by default.

- 'failover_interval2' is used once after every 3 continuous retries,
  which is 60 seconds by default.
  • 4.2.7.3.2, timer(T1,T2,T4,TD/TB) configuration added from asterisk to pjsip
  • add the following requirement (requirement 4.2.7.3.3/4/5 )

Priority after this changes:

  • retry_after (if received, as above diagram)
  • failover_max_retries (if have non-zero values, -1 as infinitive)
  • retry_interval (if set, default 1 if not set)
  • above diagram base on RFC.

Change default uci config: failover_max_retries=0; and retry_interval=0; to enable the above mechanism.(https://dev.iopsys.eu/rdk-factory/provider/oem/askey/meta-rdk-askey/-/merge_requests/61)

Edited by Wenpeng Song

Merge request reports