On Tue, 2008-09-16 at 11:06 -0400, Robert Joly wrote: > #1- Modifications to error handling: Currently, the lookUp() method can > report two kinds of errors; request errors and server errors. This > proposal will only use a single error code and lookUp() will pass an > 'ErrorDescriptor' object to be filled in by the redirector reporting the > error. This object lets a redirector specify the response status code, > optional reason phrase, optional Warning code and text to be used by the > redirect server when constructing the error response. This object could > also contain a flag that indicates whether or not a copy of the > offending request message should be added as a body of the response.
All this sounds good. > Also, unlike the current implementation, the plug-in chain is aborted on > the first error reported (with proper suspended plug-ins clean-up). I think (per a private discussion with Robert) that the fact that the current implementation does not do this was an oversight. > #3- Restrict redirector plug-ins capabilities to redirection only: > Currently, the redirect plugins have full access to SIP Responses which > would in theory allow them to do much more than just perform look-ups > which opens the door for misuse and abuse. In order to limit redirector > capabilities to look-ups only, the lookUp() will no longer supply a > response SipMessage and will instead pass a editable Contact List that > the redirect server will add to the 302 response upon success. Now that the interface provides explicit access to all of SIP's error reporting facilities, this sounds like a good idea. 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
