Damian, my and Sen's work us being done on the new models. Can you  
apply the correction for Gabor's bug?

Sent from my iPhone

On Dec 9, 2008, at 10:21 AM, "Gabor Paller" <[EMAIL PROTECTED]>  
wrote:

> We went further after the issue and found the following.
>
> The Cisco 7940/7960 SIP firmware had a parameter introduced in version
> 6.1 to control the re-registration timing.
>
> The parameter name is timer_register_delta
>
> It was discovered that sipXecs incorrectly generates a parameter  
> called
> timer_registry_delta with a default value of 5.
>
> The sipXecs file that seems to controls the creation of the config  
> file
> for the Cisco phone is at: - /etc/sipxpbx/ciscoIp/phone.xml
>
> We can modify this file so that the timer_register_delta is correctly
> named and we have given it a default value of 120 (2 minutes). By
> modifying this control file, the sipXecs web interface that allows the
> phone parameters to be changed also appears to be corrected.
>
> JIRA issue was reported.
> http://track.sipfoundry.org/browse/XECS-1993
>
> Regards,
> Gabor
>
> -----Original Message-----
> From: Dale Worley [mailto:[EMAIL PROTECTED]
> Sent: 20 November 2008 17:00
> To: Gabor Paller
> Cc: Nikolay Kondratyev; [email protected]
> Subject: RE: [sipx-users] Re-registration problem
>
> On Thu, 2008-11-20 at 09:40 +0000, Gabor Paller wrote:
>> The Cisco 7940 (SIP image, P0S3-08-5-00) is a more complicated issue.
>> The phone processes SipX expiration response correctly but it tries  
>> to
>> re-register exactly after that time period. It seems that due to  
>> minor
>> differences between the clock of the PC running SipX and the clock of
>> the Cisco phone, the Cisco phone is regularly late. Not by much, the
>> maximum time it spent unsubscribed was less than 1 minute. It still
>> happens, however, and when it happens, the endpoint is unregistered
> and
>> cannot receive calls.
>
> This problem has been understood for a very long time, at least since
> DHCP was devised.  And RFC 3261 gives explicit instructions that the  
> UA
> must re-register before its registration expires:
>
>   10.2.4 Refreshing Bindings
>
>   [...]  The UA then issues a REGISTER request for each
>   of its bindings before the expiration interval has elapsed.  [...]
>
> Dale
>
>
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users

Reply via email to