Re: [Sip] Diagnostic idea

[Dean Willis <dean.willis at softarmor.com>]

On Feb 23, 2009, at 3:37 PM, Dale Worley wrote:

> I've been considering the following idea for a diagnostic tool, and  
> I'd
> like to get some feedback on it.
>
> The goal is to be able to trace the progress of a SIP request through
> the network, including seeing the forking structure.  We first need to
> pick a provisional response codes.  It appears that "170" is not
> currently used.  This response code is also used as an option-tag for
> this feature.  The processing is that whenever a SIP element  
> receives a
> request that contains "Supported: 170", the element will immediately  
> (in
> addition to anything else that it would do with the request) send a  
> 170
> response upstream, containing the request as its body (media type
> message/sipfrag).


Your idea has merit. I believe Jiri Kuthan was working on something  
like this a few years ago.

I've also previously suggested a similar provisional response to  
inform the UAC about retargeting being done by a proxy. In addition to  
debugging, this helps avoid the unanticipated respondent problem.

--
Dean