> On Tue, 2010-05-11 at 14:17 -0400, WORLEY, Dale R (Dale) wrote: > > > The sipXecs Registrar executes a call pickup by sending a SUBSCRIBE > > message to the targeted extension. It then waits a > configured period > > of time (default 2 seconds), then examines all of the > NOTIFY responses > > it got to the SUBSCRIBE to determine what calls are ringing > on the UAs > > for the targeted extension. Among those calls, the > Registrar chooses > > the call that has been ringing the longest to be picked up. > > > > As issue XX-8372 shows, this strategy does not work well in an HA > > environment: if the SUBSCRIBE goes to a proxy which is down, the > > Registrar's SIP stack takes 2.5 seconds to fail over to the other > > proxy. By that time, the Registrar has given up waiting > for NOTIFYs > > from the SUBSCRIBE, and reports the pickup as failing. > Conversely, if > > we raise the wait time to 4.5 seconds, all pickup operations are > > unduly delayed. > > If the pickup redirector sends the SUBSCRIBE to the proxy > using tcp, shouldn't you be able to detect the failure much > faster than 2.5 seconds?
How long does it take of a socket connection to time out if the other end is not responding at all? I thought that this could take a while. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
