On Mon, Jan 11, 2010 at 4:33 PM, Scott Lawrence <[email protected]> wrote: > On Mon, 2010-01-11 at 15:53 -0500, M. Ranganathan wrote: >> Hello, >> >> I have found the References header a very handy way of tracking causal >> chains in a B2BUA. I have added a parameter x-sipx-branchid which >> contains the topmost via header of the transaction that triggers the >> request containing the References header. This + call ID allows us to >> nicely tie transactions together. > > Please change that name to 'sipxecs-branchid'. The convention of > requiring that non-standardized ids always start with 'x-' has been > officially abandoned in SIP, and no one else should be using our product > name in their names, so it is unique enough. > >
I would in fact love to see these become standard parameter names with well defined semantics if Dale would agree to include these in his next draft. (i.e. "branchId" and "method" ) Ranga > -- M. Ranganathan _______________________________________________ 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/
