SIP Re-Registration & 403 Forbidden

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

 



I hope to hear anything from the pros .

Hi Guys , 

Attached full log that hopefully will help highlighting my case .
Again in brief , if registration attempt ended up with CC i.e. 503 ,
Re-Registration is scheduled normally but in case CC 403 Forbidden ( after
allowing it explicitly )   Re-Registration is bypassed .

So what is the need of this code 

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

/* 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);
    }

Yes with CC 403 it does not make any sense to re-register but pls consider
my Question just for studying the entire project .

BR
JK
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: symbian_ua_Log_01.txt
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20120404/2cbdf3e1/attachment.txt>


[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