> and registration refresh time > > On Fri, 2010-04-30 at 14:33 +0300, [email protected] wrote: > > > > > > Do you know why sipxecs has chosen 300 seconds as minimum > by default? > > Registration can create a lot of load on the system - if you > had a few hundred phones re-registering every 30 seconds > that's a lot of messages. > > Unless the IP addresses of your phones change frequently, > long registrations are much better. For wired desk phones, > I'd actually increase the default time to several hours.
The registration interval of non-remote phones is spread between 30 and 60 minutes but the registration interval for remote NATed phones is shortened to an interval of 2.5 to 5 minutes. This is done to make the remote phones more immune to temporary network outages and component resets. Without this measure, a network interruption of a few seconds between the sipXecs and the remote user phone or a sipXproxy reset can cause the NAT pinhole to close, making it impossible for sipXecs to send any further SIP traffic to that phone until it re-registers. Shortening the registration interval for remote workers significantly reduces the window of time that a remote phone may be unreachable. In making that change, I verified that the sipXecs was capable of handling the extra load. Please refer to http://track.sipfoundry.org/browse/XX-5986 for the details. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
