4 Replies Last post: May 16, 2009 7:32 PM by jun.wen  
  20 posts since
May 28, 2008

May 7, 2009 4:41 AM

Registration Expiration Discrepancy between OSBC and SIPX


No idea how the discrepancy comes from. My OSBC is in B2BUAReg mode to my SIPX. I set the registration expiration of Eyebeam and SJphone to 1800 seconds and the expiration was well registered in OSBC, whereas, in the SIPX, I found the expiration was always less than the value in OSBC. Therefore, when the expiration in SIPX times out but still alive in OSBC, the call was failed of this UE.

Anything else should I config in OSBC ? I already checked "Send-Options-NAT-Keep-Alive" but seems not work.

Regards,

Jun

Click to view joegen's profile   519 posts since
Apr 28, 2007
1. May 9, 2009 9:12 PM in response to: jun.wen
Re: Registration Expiration Discrepancy between OSBC and SIPX
Would you be able to send the Level 5 Log for the registratio to sipx. I would like to take a look. AFAIK, OpenSBC would simply relay the expires value to the UA.
Click to view ehernaez's profile   67 posts since
Aug 28, 2007
2. May 14, 2009 12:06 AM in response to: jun.wen
Re: Registration Expiration Discrepancy between OSBC and SIPX
If I understand you correctly, this behavior is well documentd in the SIPX mailing list. SIPX always replies with a registration interval that is smaller than the one requested by the UA. If the US does not adhere to the lesser interval by re-registering, then it will become unregistered for a short time.
Click to view ehernaez's profile   67 posts since
Aug 28, 2007
3. May 14, 2009 12:45 AM in response to: ehernaez
Re: Registration Expiration Discrepancy between OSBC and SIPX
Additionally, the kludgy work around for this is to set the MIN and MAX registartion interval in SIPX to be the same value as the interval in the registration request from the UA.