> -----Original Message----- > From: Worley, Dale AVAYA (BL60:9D30) > Sent: Wednesday, February 17, 2010 2:38 PM > To: Joly, Robert AVAYA (CAR:9D30) > Cc: Lawrence, Scott AVAYA (BL60:9D30); sipX-dev > Subject: RE: [sipX-dev] XX-7668 Directed call pickup of a > user doesnot workif he has configured 'User Call Forwarding' > > On Wed, 2010-02-17 at 14:33 -0500, Joly, Robert AVAYA > (CAR:9D30) wrote: > > Why are the 1st and 3rd children being challenged at all? > Are these > > SUBSCRIBEs being routed by dialplans that require permissions? > > I haven't worked through the logic in > SipRouter::proxyMessage, but you can see that it decides that > they need challenging. In attachment fork.txt, those two > forks get messages like this: > > "2010-02-15T11:12:53.418947Z":18448:SIP:DEBUG:jupiter.qantom.i > nt:SipRouter-11:B6D78B90:SipXProxy:"SipRouter::proxyMessage A > bRequestShouldBeAuthorized = 1, > bForwardingRulesShouldBeEvaluated = 1, bMessageWillSpiral = 0"
This just means that the authorization plug-ins will have a look at the request to decide if it needs to be challenged or not. I took a closer look and found that the [205_subscriptionauth] auth plug-in is the one that decides that the request should be challenged. Information is coming back to be now... This plug-in was introduced as a way to prevent a nosy foreign endpoint from using sipXecs as a means of subscribing to the dialog-event package of a local SIP endpoint. This plug-in was added as a privacy enhancement. Prior to the addition of this plug-in, provided that you knew the SIP URI of an endpoint registered with sipXecs, one could register for that phone's dialog-event package and monitor that person's phone activity. See XX-4460. Now that this is understood, there may be an easy way to fix the problem. It seems to be that following the call forwarding rules of a user is pointless in the case of subscribes. If the call pickup plug-in crafted the SUBSCRIBE with a sipx-userforward=false URL parameter in the R-URI, that would likely do the trick unless I'm missing something. _______________________________________________ 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/
