[VOIPSEC] Mapping SIP networks?

[Shawn Merdinger]

Hi Dustin,

On Tue, Mar 25, 2008 at 2:46 PM, Dustin D. Trammell
<dtrammell at bpointsys.com> wrote:
>  I just found this document which focuses on using 483 responses to
>  diagnose SIP routing problems and such.  The draft indicates that there
>  isn't enough information in the standard 483 response to diagnose
>  routing loops and things of that nature, so you may not be able to use
>  this method after all.  It looks like the biggest problem is that the
>  403 doesn't contain any indication of what server returned the error:
>
>  http://tools.ietf.org/html/draft-ietf-sip-hop-limit-diagnostics-03

I had come across the limitations of 483 responses in that RFC, and of
course there's the vendor implementation variable, which led me to
focus on the other methods of doing traceroute at differing layers,
during an established TCP connection, etc.  Oh, and I didn't mention
layer four traceroute in my earlier post, but I'm experimenting with
it as well - http://pwhois.org/lft/.

Btw, an interesting RFC on SIP loop detection that you might find
interesting :) http://www.ietf.org/internet-drafts/draft-ietf-sip-fork-loop-fix-06.txt

Thanks!
--scm

Shawn Merdinger