On Tue, 2010-02-16 at 14:51 -0500, Dale Worley wrote: > I think we're going to have to fix XX-7668 for version 4.2. It seems to > be due to some anomaly in how the proxy decides when to challenge a > SUBSCRIBE -- the initial pass through the proxy is not challenged, but > two of three child forks are. The fork that succeeds masks that two of > the forks do not, and it messes up call pick-up. I suspect it messes up > other processing, too.
Did you find why those SUBSCRIBE forks are challenged? I can't see any obvious reason that they should have been... _______________________________________________ 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/
