SIP Re-Registration & 403 Forbidden

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear All ,

In a scenario where we have a pool of independent Proxy servers , Pjsip 1.x
SVN latest trunk - Symbian Build - S60-FP2 - Symbian_ua_gui we found that
Pjsip never initiate re-registration upon receiving 403 Forbidden while
working properly in case any of the Pre-configured disconnect codes in
pjsua_acc.c file happen to get received in the final response of the Reg
Transaction .

I tried to the following 2 configurations with no change .
Searched the entire code flow associated with Reg process and found nothing
.

I really appreciate Admins help .

/* Check if we need to auto retry registration. Basically, registration
     * failure codes triggering auto-retry are those of temporal failures
     * considered to be recoverable in relatively short term.
     */
    if (acc->cfg.reg_retry_interval && 
    		(!PJSIP_IS_STATUS_IN_CLASS(param->code, 200)))    {
	schedule_reregistration(acc);
    }


+++++++++++++++++++++++++++++++

/* Check if we need to auto retry registration. Basically, registration
     * failure codes triggering auto-retry are those of temporal failures
     * considered to be recoverable in relatively short term.
     */
    if (acc->cfg.reg_retry_interval && 
	(param->code == PJSIP_SC_REQUEST_TIMEOUT ||
	 param->code == PJSIP_SC_INTERNAL_SERVER_ERROR ||
	 param->code == PJSIP_SC_BAD_GATEWAY ||
	 param->code == PJSIP_SC_SERVICE_UNAVAILABLE ||
	 param->code == PJSIP_SC_SERVER_TIMEOUT ||
       param->code == PJSIP_SC_FORBIDDEN ||
	 PJSIP_IS_STATUS_IN_CLASS(param->code, 600))) /* Global failure */
    {
	schedule_reregistration(acc);
    }




[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux