On Wed, 2009-05-27 at 15:57 -0400, Mark Gertsvolf wrote: > However, regardless of the actual specifics of why the pickup is failing > in this case, I think the call pickup conceptually should not follow the > call forward tree. > > People invoke directed call pickup when they hear somebody's phone ring > or when they have a BLF key for another user and they see the call for > that user. The intention is to pick the call that appears on the sets of > a specific user right now. It is irrelevant that the call happens to > also ring phones belonging to 10 other people because of the user's call > forward rules. > Also if the call stops ringing the phone of the user in question and > rolls to the next destination in the forwarding tree - pickup should > fail. If the next target is user Y, then it should be able to pick this > call up using directed call pickup for user Y. > > My proposal is to restrict the target audience of the subscription to > only user's registered sets using "sipx-userforward=false" parameter in > R-URI.
There are a number of overlapping issues. For the moment, let us limit ourselves to the issue that is directly affected by your proposal, which is "When someone dials call pickup, what targets do they intend to query?" This is a product feature question. Off the top of my head, I suspect that you're right, that the common use is when the phone in question is actually ringing. But your change would be user-visible, and could cause annoyance if the call forwards at just the moment that the user invokes pick-up. Do we have produce management advice regarding this? I think the chances of an unexpected side-effect of this change is low, but we should worry about how much testing it will be subjected to before GA. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
