I am splitting the work on this issue. The sipx-userforward parameter I will apply for version 4.2. This will eliminate the observed problem and be quite safe otherwise. The deeper problem of handling SUBSCRIBEs that might be challenged I've documented in XX-7706, and I will leave it for after 4.2.
On Thu, 2010-02-18 at 11:12 -0500, Dale Worley wrote: > There are two interlocking problems. > > One is that we don't apply "sipx-userforward=false" to the SUBSCRIBE for > call pickup. Doing this would improve the user experience. (Which > reminds me that I need to vet the change on sipx-users.) This change > would also make the symptom disappear. > > The second problem is that we've started demanding authentication of > SUBSCRIBEs under certain circumstances. But most of our security > architecture presumes that SUBSCRIBEs are never challenged, and so > things don't work right. _______________________________________________ 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/
